2.6.11-mm2 + Radeon crash
Hi,
I wanted to try 2.6.11-mm2 for the low latency/realtime lsm stuff and I've run into a severe
problem.
When I try to start X, my machine reboots. The screen goes dark as usual when setting the video mode, but then I get a beep and I'm greeted with the BIOS boot messages. This happened 4/5 times i've tried, and once the video mode was actually set (at least I saw the usual X b/w pattern with some random framebuffer garbage), the machine didn't reboot but after that nothing happened. My keyboard was still responsive (ie NumLock LED would still go on/off), but i could neither kill X with CTRL-ALT-BACKSPACE nor could i switch back to console, so I ended up pressing reset.
After the crashes I booted with a rescue CD to examine the logs, but I could not find any obvious errors.
Everything works nicely on 2.6.10 and earlier kernels. I'm in the process of building 2.6.11.2 to see if the crash occurs there.
Here is some info on my system:
I've got an Athlon 1000C on a VIA KT133 chipset and a Radeon 7200 (the original Radeon with 32MB SDR RAM). I'm running Debian/sid.
homer:/home/chrissi# X -version X: warning; /dev/dri has unusual mode (not 755) or is not a directory. XFree86 Version 4.3.0.1 (Debian 4.3.0.dfsg.1-12.0.1 20050223080930 [email protected]) Release Date: 15 August 2003 X Protocol Version 11, Revision 0, Release 6.6 Build Operating System: Linux 2.6.9 i686 [ELF] Build Date: 23 February 2005
lspci -vv says bout the Radeon:
0000:01:00.0 VGA compatible controller: ATI Technologies Inc Radeon R100 QD [Radeon 7200] (prog-if 00 [VGA])
Subsystem: ATI Technologies Inc Radeon 7000/Radeon
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping+ SERR- FastB2B-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium
Quoted 1 line
TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 32 (2000ns min), Cache Line Size: 0x08 (32 bytes)
Interrupt: pin A routed to IRQ 5
Region 0: Memory at d0000000 (32-bit, prefetchable) [size=64M]
Region 1: I/O ports at c000 [size=256]
Region 2: Memory at d7000000 (32-bit, non-prefetchable) [size=512K]
Capabilities: [58] AGP version 2.0
Status: RQ=48 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64-
HTrans- 64bit- FW- AGP3- Rate=x1,x2,x4
Command: RQ=1 ArqSz=0 Cal=0 SBA+ AGP- GART64- 64bit-FW- Rate=<none>
Capabilities: [50] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mAPME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Please let me know what more data is needed to figure this one out.
Thanks,
Christian Henz
PS: If you reply, please CC me as I'm not subscribed.
Quoted 16 lines · Christian Henz
Hi,
I wanted to try 2.6.11-mm2 for the low latency/realtime lsm stuff and I've run into a severe
problem.When I try to start X, my machine reboots. The screen goes dark as usual when setting the video mode, but then I get a beep and I'm greeted with the BIOS boot messages. This happened 4/5 times i've tried, and once the video mode was actually set (at least I saw the usual X b/w pattern with some random framebuffer garbage), the machine didn't reboot but after that nothing happened. My keyboard was still responsive (ie NumLock LED would still go on/off), but i could neither kill X with CTRL-ALT-BACKSPACE nor could i switch back to console, so I ended up pressing reset.
Quoted 5 lines
After the crashes I booted with a rescue CD to examine the logs, but I could not find any obvious errors.
Everything works nicely on 2.6.10 and earlier kernels. I'm in the process of building 2.6.11.2 to see if the crash occurs there.
So ?
Ben.
Quoted 1 line · Benjamin Herrenschmidt
On Wed, 2005-03-09 at 21:12 +0100, Christian Henz wrote:
[...]
Quoted 5 lines
Quoted 2 lines
Everything works nicely on 2.6.10 and earlier kernels. I'm in the process of building 2.6.11.2 to see if the crash occurs there.
So ?
2.6.11.2 works fine, too. I'll probably try some older versions of the -mm tree later today.
cheers,
Christian
PS: If you reply, please CC me as I'm not subscribed.
Quoted 5 lines · Christian Henz
Hi,
I wanted to try 2.6.11-mm2 for the low latency/realtime lsm stuff and I've run into a severe
problem.
There is absolutely no reason to use the -mm kernel anymore for low latency audio. The -mm kernels were never stable enough to work well for audio users anyway.
The latest version of Ingo's realtime preempt patch is against 2.6.11-rc4. Supposedly it applies and works with 2.6.11 vanilla, you just have to edit the patch not to expect -rc4 as the EXTRAVERSION.
Lee
Quoted 7 lines · Lee Revell
Quoted 5 lines · Christian Henz
Hi,
I wanted to try 2.6.11-mm2 for the low latency/realtime lsm stuff and I've run into a severe
problem.
Quoted 7 lines
There is absolutely no reason to use the -mm kernel anymore for low latency audio. The -mm kernels were never stable enough to work well for audio users anyway.
The latest version of Ingo's realtime preempt patch is against 2.6.11-rc4. Supposedly it applies and works with 2.6.11 vanilla, you just have to edit the patch not to expect -rc4 as the EXTRAVERSION.
Sorry, I thought this was an LAU post ;-) People on LKML already know the above of course.
Lee
Quoted 4 lines · Christian Henz
Quoted 1 line · Benjamin Herrenschmidt
On Wed, 2005-03-09 at 21:12 +0100, Christian Henz wrote:
[...]
Quoted 9 lines
Quoted 5 lines
Quoted 2 lines
Everything works nicely on 2.6.10 and earlier kernels. I'm in the process of building 2.6.11.2 to see if the crash occurs there.
So ?
2.6.11.2 works fine, too. I'll probably try some older versions of the -mm tree later today.
I've tried 2.6.11-mm1 and it doesn't reboot, I always (4/4 times I've tried) get the behaviour I reported before where the video mode is set and after that the screen just keeps displaying the garbled framebuffer and nothing happens. The system doesn't hang though, as I've found out by running "sleep 90; reboot" before starting X - after the timeout my machine properly shut down. I inserted a "ps ax > foo.txt" before the "reboot", and it showed that the X server was not running. Then I found this in /var/log/messages:
Mar 10 22:26:21 homer kernel: [drm] Initialized drm 1.0.0 20040925 Mar 10 22:26:21 homer kernel: ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 5 Mar 10 22:26:21 homer kernel: PCI: setting IRQ 5 as level-triggered Mar 10 22:26:21 homer kernel: ACPI: PCI interrupt 0000:01:00.0[A] -> GSI 5 (level, low) -> IRQ 5 Mar 10 22:26:21 homer kernel: [drm] Initialized radeon 1.14.0 20050125 on minor 0: ATI Technologies Inc Radeon R100 QD [Radeon 7200] Mar 10 22:26:21 homer kernel: agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0. Mar 10 22:26:21 homer kernel: agpgart: Putting AGP V2 device at 0000:00:00.0 into 1x mode Mar 10 22:26:21 homer kernel: agpgart: Putting AGP V2 device at 0000:01:00.0 into 1x mode Mar 10 22:26:21 homer kernel: 34244c89 Mar 10 22:26:21 homer kernel: PREEMPT Mar 10 22:26:21 homer kernel: Modules linked in: radeon drm lp autofs4
ipt_limit ipt_state ipt_LOG ipt_REJECT ip_conntrack_irc ip_conntrack _ftp ip_conntrack iptable_filter ip_tables 8139too via_rhine mii nls_iso8859_1 nls_cp437 vfat fat floppy parport_pc parport grip gameport j
oydev psmouse mousedev via_agp agpgart genrtc unix
Mar 10 22:26:21 homer kernel: CPU: 0 Mar 10 22:26:21 homer kernel: EIP: 0060:[<34244c89>] Not tainted VLI Mar 10 22:26:21 homer kernel: EFLAGS: 00013296 (2.6.11-mm1) Mar 10 22:26:21 homer kernel: EIP is at 0x34244c89 Mar 10 22:26:21 homer kernel: eax: dcc9dde8 ebx: dcc9b400 ecx: 0000007b edx: 00000000 Mar 10 22:26:21 homer kernel: esi: 00000000 edi: 34244c89 ebp: dcc9deb4 esp: dcc9dde4 Mar 10 22:26:21 homer kernel: ds: 007b es: 007b ss: 0068 Mar 10 22:26:21 homer kernel: Process XFree86 (pid: 2008, threadinfo=dcc9c000 task=de62c080) Mar 10 22:26:21 homer kernel: Stack: c0103cfb dcc9b400 dea10460 00002710 00000000 00000000 dcc9deb4 e09a0000 Mar 10 22:26:21 homer kernel: 0000007b 0000007b ffffffff e09e5a4b 00000060 00003287 00000040 dcc9b400 Mar 10 22:26:21 homer kernel: dcc9b400 e09e534d dc1db800 dcc9b400 00000000 e09e6340 dc1db800 dcc9b400 Mar 10 22:26:21 homer kernel: Call Trace: Mar 10 22:26:21 homer kernel: [<c0103cfb>] error_code+0x2b/0x30 Mar 10 22:26:21 homer kernel: [<e09e5a4b>] radeon_cp_init_ring_buffer+0x14b/0x320 [radeon] Mar 10 22:26:21 homer kernel: [<e09e534d>] radeon_cp_load_microcode+0x1d/0x130 [radeon] Mar 10 22:26:21 homer kernel: [<e09e6340>] radeon_do_init_cp+0x690/0xc30 [radeon] Mar 10 22:26:21 homer kernel: [<c0140590>] __alloc_pages+0x300/0x480 Mar 10 22:26:21 homer kernel: [<e09e6da0>] radeon_cp_init+0x0/0xb0 [radeon] Mar 10 22:26:21 homer kernel: [<e09e6e3a>] radeon_cp_init+0x9a/0xb0 [radeon] Mar 10 22:26:21 homer kernel: [<c01f8b53>] capable+0x23/0x50 Mar 10 22:26:21 homer kernel: [<e09ff205>] drm_ioctl+0xd5/0x1ae [drm] Mar 10 22:26:21 homer kernel: [<c016f8ef>] do_ioctl+0x6f/0xa0 Mar 10 22:26:21 homer kernel: [<c016fad5>] vfs_ioctl+0x65/0x1d0 Mar 10 22:26:21 homer kernel: [<c016fca7>] sys_ioctl+0x67/0xc0 Mar 10 22:26:21 homer kernel: [<c010324d>] syscall_call+0x7/0xb Mar 10 22:26:21 homer kernel: Code: Bad EIP value. Mar 10 22:26:21 homer kernel: <3>[drm:drm_release] *ERROR* Device busy: 1 0
tail /var/log/XFree86.0.log.old says:
(II) RADEON(0): Acceleration enabled
(==) RADEON(0): Backing store disabled
(==) RADEON(0): Silken mouse enabled
(II) RADEON(0): Using hardware cursor (scanline 866) (II) RADEON(0): Largest offscreen area available: 1152 x 7317 (**) Option "dpms"
(**) RADEON(0): DPMS enabled
(II) RADEON(0): X context handle = 0x00000001
(II) RADEON(0): [drm] installed DRM signal handler (II) RADEON(0): [DRI] installation complete
cheers,
Christian
PS: If you reply, please CC me as I'm not subscribed.
Quoted 14 lines
When I try to start X, my machine reboots. The screen goes dark as usual when setting the video mode, but then I get a beep and I'm greeted with the BIOS boot messages. This happened 4/5 times i've tried, and once the video mode was actually set (at least I saw the usual X b/w pattern with some random framebuffer garbage), the machine didn't reboot but after that nothing happened. My keyboard was still responsive (ie NumLock LED would still go on/off), but i could neither kill X with CTRL-ALT-BACKSPACE nor could i switch back to console, so I ended up pressing reset.
After the crashes I booted with a rescue CD to examine the logs, but I could not find any obvious errors.
Quoted 8 lines
Everything works nicely on 2.6.10 and earlier kernels. I'm in the process of building 2.6.11.2 to see if the crash occurs there.
Here is some info on my system:
I've got an Athlon 1000C on a VIA KT133 chipset and a Radeon 7200 (the original Radeon with 32MB SDR RAM). I'm running Debian/sid.
A copy of /var/log/XFree86.0.log and a copy of dmesg and copy of your .config if you could .. main things of interest whether you have fb drivers and drm drivers..
Dave.
Quoted 7 lines · Dave Airlie
A copy of
/var/log/XFree86.0.logand a copy of dmesg and copy of your .config if you could .. main things of interest whether you have fb drivers and drm drivers..Dave.
Here we go. I've attached the files for both -mm1 and -mm2. Note that for -mm2 dmesg was run before starting X, and the XFree86 logfile is missing since it wasn't created.
cheers,
Christian
Quoted 6 lines · Christian Henz
Hi,
I wanted to try 2.6.11-mm2 for the low latency/realtime lsm stuff and I've run into a severe
problem.
Christian, some fixes have bene made in this area. Could you please test 2.6.12-rc1-mm1?
Quoted 70 lines
When I try to start X, my machine reboots. The screen goes dark as usual when setting the video mode, but then I get a beep and I'm greeted with the BIOS boot messages. This happened 4/5 times i've tried, and once the video mode was actually set (at least I saw the usual X b/w pattern with some random framebuffer garbage), the machine didn't reboot but after that nothing happened. My keyboard was still responsive (ie NumLock LED would still go on/off), but i could neither kill X with CTRL-ALT-BACKSPACE nor could i switch back to console, so I ended up pressing reset.
After the crashes I booted with a rescue CD to examine the logs, but I could not find any obvious errors.
Everything works nicely on 2.6.10 and earlier kernels. I'm in the process of building 2.6.11.2 to see if the crash occurs there.
Here is some info on my system:
I've got an Athlon 1000C on a VIA KT133 chipset and a Radeon 7200 (the original Radeon with 32MB SDR RAM). I'm running Debian/sid.
homer:/home/chrissi# X -version X: warning; /dev/dri has unusual mode (not 755) or is not a directory. XFree86 Version 4.3.0.1 (Debian 4.3.0.dfsg.1-12.0.1 20050223080930 [email protected]) Release Date: 15 August 2003 X Protocol Version 11, Revision 0, Release 6.6 Build Operating System: Linux 2.6.9 i686 [ELF] Build Date: 23 February 2005lspci -vv says bout the Radeon:
0000:01:00.0 VGA compatible controller: ATI Technologies Inc Radeon R100 QD [Radeon 7200] (prog-if 00 [VGA])
Subsystem: ATI Technologies Inc Radeon 7000/Radeon
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping+ SERR- FastB2B-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=mediumQuoted 1 line
TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 32 (2000ns min), Cache Line Size: 0x08 (32 bytes) Interrupt: pin A routed to IRQ 5 Region 0: Memory at d0000000 (32-bit, prefetchable) [size=64M] Region 1: I/O ports at c000 [size=256] Region 2: Memory at d7000000 (32-bit, non-prefetchable) [size=512K] Capabilities: [58] AGP version 2.0 Status: RQ=48 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- HTrans- 64bit- FW- AGP3- Rate=x1,x2,x4 Command: RQ=1 ArqSz=0 Cal=0 SBA+ AGP- GART64- 64bit-FW- Rate=<none>
Capabilities: [50] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mAPME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-Please let me know what more data is needed to figure this one out.
Thanks,
Christian HenzPS: If you reply, please CC me as I'm not subscribed.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Quoted 11 lines · Andrew Morton
Quoted 6 lines · Christian Henz
Hi,
I wanted to try 2.6.11-mm2 for the low latency/realtime lsm stuff and I've run into a severe
problem.Christian, some fixes have bene made in this area. Could you please test 2.6.12-rc1-mm1?
I've only tried once so far and again it immediately rebooted after running startx. I will try later today to catch that condition where only X crashes but the XFree68.log gets written.
cheers,
Christian
Quoted 6 lines · Christian Henz
Hi,
I wanted to try 2.6.11-mm2 for the low latency/realtime lsm stuff and I've run into a severe
problem.
Christian, can you please retest 2.6.12-rc5?
Quoted 70 lines
When I try to start X, my machine reboots. The screen goes dark as usual when setting the video mode, but then I get a beep and I'm greeted with the BIOS boot messages. This happened 4/5 times i've tried, and once the video mode was actually set (at least I saw the usual X b/w pattern with some random framebuffer garbage), the machine didn't reboot but after that nothing happened. My keyboard was still responsive (ie NumLock LED would still go on/off), but i could neither kill X with CTRL-ALT-BACKSPACE nor could i switch back to console, so I ended up pressing reset.
After the crashes I booted with a rescue CD to examine the logs, but I could not find any obvious errors.
Everything works nicely on 2.6.10 and earlier kernels. I'm in the process of building 2.6.11.2 to see if the crash occurs there.
Here is some info on my system:
I've got an Athlon 1000C on a VIA KT133 chipset and a Radeon 7200 (the original Radeon with 32MB SDR RAM). I'm running Debian/sid.
homer:/home/chrissi# X -version X: warning; /dev/dri has unusual mode (not 755) or is not a directory. XFree86 Version 4.3.0.1 (Debian 4.3.0.dfsg.1-12.0.1 20050223080930 [email protected]) Release Date: 15 August 2003 X Protocol Version 11, Revision 0, Release 6.6 Build Operating System: Linux 2.6.9 i686 [ELF] Build Date: 23 February 2005lspci -vv says bout the Radeon:
0000:01:00.0 VGA compatible controller: ATI Technologies Inc Radeon R100 QD [Radeon 7200] (prog-if 00 [VGA])
Subsystem: ATI Technologies Inc Radeon 7000/Radeon
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping+ SERR- FastB2B-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=mediumQuoted 1 line
TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 32 (2000ns min), Cache Line Size: 0x08 (32 bytes) Interrupt: pin A routed to IRQ 5 Region 0: Memory at d0000000 (32-bit, prefetchable) [size=64M] Region 1: I/O ports at c000 [size=256] Region 2: Memory at d7000000 (32-bit, non-prefetchable) [size=512K] Capabilities: [58] AGP version 2.0 Status: RQ=48 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- HTrans- 64bit- FW- AGP3- Rate=x1,x2,x4 Command: RQ=1 ArqSz=0 Cal=0 SBA+ AGP- GART64- 64bit-FW- Rate=<none>
Capabilities: [50] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mAPME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-Please let me know what more data is needed to figure this one out.
Thanks,
Christian HenzPS: If you reply, please CC me as I'm not subscribed.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Quoted 10 lines · Andrew Morton
Quoted 6 lines · Christian Henz
Hi,
I wanted to try 2.6.11-mm2 for the low latency/realtime lsm stuff and I've run into a severe
problem.Christian, can you please retest 2.6.12-rc5?
2.6.12-rc5 and -mm1 seem to work fine!
Thanks :-)
cheers,
Christian