You are not logged in.
I finally did an update to my system, and now with 2.6.28, No matter which nvidia drivers I use, things work fine in Xorg for an indeterminent amount of time, then all the sudden, my screens blank and the box is completely unresponsive to ping. At this point, touching the keyboard causes beeps. Presumably the kernel has paniced.
I've tried nvidia-180.29-3, nvidia-173xx (173.14.17-2) nvidia-96xx(96.43.11-2) as well as getting nvidia drivers directly from nvidia's site, doing an uninstall through here, etc. I know the issue is related to nvidia, since when I switch to vesa, the problem goes away.
Interestingly, the crash always seems to happen as a result of me typing on the keyboard. For example, I will be using mutt in an mrxvt terminal, and as soon as I hit 'j' or 'backspace' the box crashes. It never crashes when just using the mouse or not as the result of typing. Of course, this only happens after around 30 minutes or so, as I am using this setup right now and typing is working fine.
Presumably the rest of the Arch community isn't hitting this or it would have been addressed by now. My device is:
01:00.0 VGA compatible controller: nVidia Corporation NV44 [Quadro NVS 285] (rev a1) (prog-if 00 [VGA controller])
Subsystem: nVidia Corporation Device 0334
Flags: bus master, fast devsel, latency 0, IRQ 16
Memory at ed000000 (32-bit, non-prefetchable) [size=16M]
Memory at d0000000 (64-bit, prefetchable) [size=256M]
Memory at ee000000 (64-bit, non-prefetchable) [size=16M]
[virtual] Expansion ROM at efe00000 [disabled] [size=128K]
Capabilities: [60] Power Management version 2
Capabilities: [68] MSI: Mask- 64bit+ Count=1/1 Enable-
Capabilities: [78] Express Endpoint, MSI 00
Capabilities: [100] Virtual Channel <?>
Capabilities: [128] Power Budgeting <?>
Kernel driver in use: nvidia
Kernel modules: nvidia, nvidiafb
Edit: This looks like the same problem being hit here:
http://bbs.archlinux.org/viewtopic.php?id=66425
My last log messages before the reboot are also:
Mar 18 11:46:47 dev1 acpid: client 3458[0:201] has disconnected
Mar 18 11:46:47 dev1 acpid: client 3458[0:201] has disconnected
Mar 18 11:46:47 dev1 acpid: client 3458[0:201] has disconnected
Mar 18 11:46:47 dev1 acpid: client 5140[0:201] has disconnected
Mar 18 11:46:47 dev1 acpid: client 5140[0:201] has disconnected
Mar 18 11:46:47 dev1 acpid: client 5140[0:201] has disconnected
Mar 18 11:46:47 dev1 acpid: client 7496[0:201] has disconnected
Mar 18 11:46:47 dev1 acpid: client 7553[0:201] has disconnected
Mar 18 11:46:47 dev1 acpid: client 8837[0:201] has disconnected
Mar 18 11:46:47 dev1 acpid: client 8837[0:201] has disconnected
Last edited by randy80016 (2009-03-18 21:54:34)
Offline
Is there a supported way to downgrade to an older ARCH kernel as a workaround? I can roll my own kernel, but would prefer to just use an older default one. I guess what I am asking is, what is the arch equivalent to gentoo's:
/etc/portage/package.mask:
>=kernel26-2.6.28
Offline
Actually I was wrong, this isn't a kernel panic, and may not even be related to Nvidia.
Xorg just plain crashes, and it does seem to be in keyboard handling code:
Backtrace:
0: /usr/bin/X(xorg_backtrace+0x26) [0x4f00a6]
1: /usr/bin/X(xf86SigHandler+0x39) [0x49c149]
2: /lib/libc.so.6 [0x7f5f4382a150]
3: /usr/bin/X(miPointerWarpCursor+0x8b) [0x4da17b]
4: /usr/bin/X [0x478050]
5: /usr/bin/X [0x4d9dcc]
6: /usr/bin/X [0x53499f]
7: /usr/bin/X [0x454f14]
8: /usr/bin/X(CheckMotion+0x2af) [0x45925f]
9: /usr/bin/X(ProcessOtherEvent+0x2d9) [0x53e559]
10: /usr/bin/X(XkbHandleActions+0x21b) [0x5653db]
11: /usr/bin/X(XkbProcessKeyboardEvent+0x3c1) [0x565ec1]
12: /usr/bin/X(AccessXFilterPressEvent+0x10c) [0x55db0c]
13: /usr/bin/X(mieqProcessInputEvents+0x34e) [0x4d0b9e]
14: /usr/bin/X(ProcessInputEvents+0x9) [0x49cc99]
15: /usr/bin/X(Dispatch+0x71) [0x44d6c1]
16: /usr/bin/X(main+0x3bd) [0x4338ad]
17: /lib/libc.so.6(__libc_start_main+0xe6) [0x7f5f43816546]
18: /usr/bin/X [0x432d39]
Where can I get symbols to debug this? Or is there way to just run Xorg inside gdb from the start?
Offline
Were you ever able to resolve this error? This sounds exactly like what I'm facing now. I have tracked the cause of X crashing to be when I hold down a non-modifier key within X.org. For example, just holding down the letter "a" will cause X to crash.
I just recently upgraded to kernel 2.6.28 and nvidia drivers 150.52.
Thanks,
Neoxic
http://digital-drip.com
Offline