Summary: | nvidia drivers 1.0.5336 w/ SiS 746 and AGP -> system lockup on vanilla 2.6.X, but second try succeeds!! | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Björn Michaelsen <bjoern.michaelsen> |
Component: | [OLD] Core system | Assignee: | x86-kernel (DEPRECATED) <x86-kernel> |
Status: | RESOLVED UPSTREAM | ||
Severity: | normal | CC: | steel300 |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
URL: | http://forums.gentoo.org/viewtopic.php?t=132960&highlight= | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Björn Michaelsen
2004-02-08 15:11:50 UTC
Oh, and BTW the results are independant of the 2.6 kernel version and they are independant of the nvidia driver version. It seems like X and AGPGART locking each other while registering AGP-devices. If anybody knows how to get useful additional debug info, please please tell me! Maybe this is a kernel bug and not a xfree bug? The system locks too sometimes, if I do a "shutdown -h now" from a xterm - again with full CPU-load... However sending a SysRq+k kills X and the system then shuts down normally. These messages accompany the locks (sometimes): Feb 15 20:21:45 [kernel] 0: nvidia: trying to map 0xbfe4d000 to kernel space, but we're in an interrupt or holding a spinlock Feb 15 20:23:10 [kernel] 0: nvidia: trying to map 0xbfe43c00 to kernel space, but we're in an interrupt or holding a spinlock Feb 15 20:24:34 [kernel] 0: nvidia: trying to map 0xbfc59000 to kernel space, but we're in an interrupt or holding a spinlock Feb 16 00:05:23 [kernel] 0: nvidia: trying to map 0xbfad4800 to kernel space, but we're in an interrupt or holding a spinlock Feb 16 00:10:31 [kernel] 0: nvidia: trying to map 0xbfac6800 to kernel space, but we're in an interrupt or holding a spinlock Feb 16 00:11:21 [kernel] 0: nvidia: trying to map 0xbf7a7f00 to kernel space, but we're in an interrupt or holding a spinlock Feb 16 00:19:19 [kernel] 0: nvidia: trying to map 0xbf7a7f00 to kernel space, but we're in an interrupt or holding a spinlock Feb 16 00:33:28 [kernel] 0: nvidia: trying to map 0xbf7a7f00 to kernel space, but we're in an interrupt or holding a spinlock Feb 16 00:45:34 [kernel] 0: nvidia: trying to map 0xbd9a3f00 to kernel space, but we're in an interrupt or holding a spinlock This patch by Oliver Schoett: http://lkml.org/lkml/2004/2/22/102 solved the problem. The patch is for the SiS 648 but worked also for my SiS 746. I applied the patch manually against vanilla 2.6.4-rc1. If the patch is not in the gentoo-kernel maybe it should be added? reopening bug to give to the kernel team I just found this patch seems also to be in the love-sources, so it it already tested a bit: http://forums.gentoo.org/viewtopic.php?t=140586&highlight=sis+lovesources BTW, I posted a link to this bug to the lkml. There is a bug open for this on bugzilla.kernel.org: http://bugzilla.kernel.org/show_bug.cgi?id=2327 A more extense patch is proposed there. Bugfix is implemented in vanilla 2.6.5. The changes in 2.6.5 only apply for the SiS 648, but *NOT* for the SiS 746. I wrote a patch against vanilla 2.6.5 to fix this and posted it here: http://bugzilla.kernel.org/show_bug.cgi?id=2327 This is something that should be pushed upstream. Please file a bug at http://bugme.osdl.org. I already contacted Dave Jones on LKML and this is under heavy development. Although it is broken for the SiS 746 in 2.6.5 it seems to be fixed in the current 2.6.6 rc. http://testing.lkml.org/slashdot.php?mid=465593 |