2.6.2 Kernel Badness with 1.0-5336 NVIDIA driver
Hi to all,
Pls cc me as I am not subscribing.
I know that the kernel is tainted so pls don't flame ;)
The kernel is 2.6.2 from www.kernel.org and I use AGPGART for AGP (_not_ NvAGP). Fast Writes and SBA are enabled. FC1 is the distro. The mobo is Abit KG7 and the video card an FX5600.
X stopped responding out of the blue, at a KDE 3.2 desktop, and it could not be killed either. The following messages were uncovered in
my /var/log/messages:
Feb 17 07:35:15 thunderbird kernel: Badness in pci_find_subsys at drivers/pci/search.c:167 Feb 17 07:35:15 thunderbird kernel: Call Trace: Feb 17 07:35:15 thunderbird kernel: [<c01ec168>] pci_find_subsys+0xe8/0xf0 Feb 17 07:35:15 thunderbird kernel: [<c01ec19f>] pci_find_device+0x2f/0x40 Feb 17 07:35:15 thunderbird kernel: [<c01ebfa8>] pci_find_slot+0x28/0x50 Feb 17 07:35:15 thunderbird kernel: [<e0e1222a>] os_pci_init_handle+0x39/0x68 [nvidia] Feb 17 07:35:15 thunderbird kernel: [<e0ca685f>] _nv001243rm+0x1f/0x24 [nvidia] Feb 17 07:35:15 thunderbird kernel: [<e0ded115>] _nv000816rm+0x2f5/0x384 [nvidia] Feb 17 07:35:15 thunderbird kernel: [<e0d5592c>] _nv003801rm+0xd8/0x100 [nvidia] Feb 17 07:35:15 thunderbird kernel: [<e0decc4f>] _nv000809rm+0x2f/0x34 [nvidia] Feb 17 07:35:15 thunderbird kernel: [<e0d84b48>] _nv003606rm+0xe4/0x114 [nvidia] Feb 17 07:35:15 thunderbird kernel: [<e0d846b8>] _nv003564rm+0x688/0x908 [nvidia] Feb 17 07:35:15 thunderbird kernel: [<e0cbf267>] _nv004046rm+0x3a3/0x3b0 [nvidia] Feb 17 07:35:15 thunderbird kernel: [<e0dc0b03>] _nv001476rm+0x1d3/0x45c [nvidia] Feb 17 07:35:15 thunderbird kernel: [<e0ca939a>] _nv000896rm+0x4a/0x64 [nvidia] Feb 17 07:35:15 thunderbird kernel: [<e0caabb4>] rm_isr_bh+0xc/0x10 [nvidia] Feb 17 07:35:15 thunderbird kernel: [<e0e0fab1>] nv_kern_isr_bh+0xf/0x13 [nvidia] Feb 17 07:35:15 thunderbird kernel: [<c01208b6>] tasklet_action+0x46/0x70 Feb 17 07:35:15 thunderbird kernel: [<c01206d0>] do_softirq+0x90/0xa0 Feb 17 07:35:15 thunderbird kernel: [<c010b56d>] do_IRQ+0xfd/0x130 Feb 17 07:35:15 thunderbird kernel: [<c01098b4>] common_interrupt+0x18/0x20 Feb 17 07:35:15 thunderbird kernel: Feb 17 07:35:15 thunderbird kernel: Badness in pci_find_subsys at drivers/pci/search.c:167 Feb 17 07:35:15 thunderbird kernel: Call Trace: Feb 17 07:35:15 thunderbird kernel: [<c01ec168>] pci_find_subsys+0xe8/0xf0 Feb 17 07:35:15 thunderbird kernel: [<c01ec19f>] pci_find_device+0x2f/0x40 Feb 17 07:35:15 thunderbird kernel: [<c01ebfa8>] pci_find_slot+0x28/0x50 Feb 17 07:35:15 thunderbird kernel: [<e0e1222a>] os_pci_init_handle+0x39/0x68 [nvidia] Feb 17 07:35:15 thunderbird kernel: [<e0ca685f>] _nv001243rm+0x1f/0x24 [nvidia] Feb 17 07:35:15 thunderbird kernel: [<e0d57a5d>] _nv003797rm+0xa9/0x128 [nvidia] Feb 17 07:35:15 thunderbird kernel: [<e0dc44a1>] _nv001490rm+0x55/0xe4 [nvidia] Feb 17 07:35:15 thunderbird kernel: [<e0ded154>] _nv000816rm+0x334/0x384 [nvidia] Feb 17 07:35:15 thunderbird kernel: [<e0d5592c>] _nv003801rm+0xd8/0x100 [nvidia] Feb 17 07:35:15 thunderbird kernel: [<e0decc4f>] _nv000809rm+0x2f/0x34 [nvidia] Feb 17 07:35:15 thunderbird kernel: [<e0d84b48>] _nv003606rm+0xe4/0x114 [nvidia] Feb 17 07:35:15 thunderbird kernel: [<e0d846b8>] _nv003564rm+0x688/0x908 [nvidia] Feb 17 07:35:15 thunderbird kernel: [<e0cbf267>] _nv004046rm+0x3a3/0x3b0 [nvidia] Feb 17 07:35:15 thunderbird kernel: [<e0dc0b03>] _nv001476rm+0x1d3/0x45c [nvidia] Feb 17 07:35:15 thunderbird kernel: [<e0ca939a>] _nv000896rm+0x4a/0x64 [nvidia] Feb 17 07:35:15 thunderbird kernel: [<e0caabb4>] rm_isr_bh+0xc/0x10 [nvidia] Feb 17 07:35:15 thunderbird kernel: [<e0e0fab1>] nv_kern_isr_bh+0xf/0x13 [nvidia] Feb 17 07:35:15 thunderbird kernel: [<c01208b6>] tasklet_action+0x46/0x70 Feb 17 07:35:15 thunderbird kernel: [<c01206d0>] do_softirq+0x90/0xa0 Feb 17 07:35:15 thunderbird kernel: [<c010b56d>] do_IRQ+0xfd/0x130 Feb 17 07:35:15 thunderbird kernel: [<c01098b4>] common_interrupt+0x18/0x20 Feb 17 07:35:15 thunderbird kernel:
Thanks,
Thanos
More then likely this is Nvidia's fault. You'll have to take it up with them and not the ppl here at the lkml.
Matt H.
Quoted 94 lines · Athanasios Leontaris
Hi to all,
Pls cc me as I am not subscribing.
I know that the kernel is tainted so pls don't flame ;)
The kernel is 2.6.2 from www.kernel.org and I use AGPGART for AGP (_not_ NvAGP). Fast Writes and SBA are enabled. FC1 is the distro. The mobo is Abit KG7 and the video card an FX5600.X stopped responding out of the blue, at a KDE 3.2 desktop, and it could not be killed either. The following messages were uncovered in my
/var/log/messages:Feb 17 07:35:15 thunderbird kernel: Badness in pci_find_subsys at drivers/pci/search.c:167 Feb 17 07:35:15 thunderbird kernel: Call Trace: Feb 17 07:35:15 thunderbird kernel: [<c01ec168>] pci_find_subsys+0xe8/0xf0 Feb 17 07:35:15 thunderbird kernel: [<c01ec19f>] pci_find_device+0x2f/0x40 Feb 17 07:35:15 thunderbird kernel: [<c01ebfa8>] pci_find_slot+0x28/0x50 Feb 17 07:35:15 thunderbird kernel: [<e0e1222a>] os_pci_init_handle+0x39/0x68 [nvidia] Feb 17 07:35:15 thunderbird kernel: [<e0ca685f>] _nv001243rm+0x1f/0x24 [nvidia] Feb 17 07:35:15 thunderbird kernel: [<e0ded115>] _nv000816rm+0x2f5/0x384 [nvidia] Feb 17 07:35:15 thunderbird kernel: [<e0d5592c>] _nv003801rm+0xd8/0x100 [nvidia] Feb 17 07:35:15 thunderbird kernel: [<e0decc4f>] _nv000809rm+0x2f/0x34 [nvidia] Feb 17 07:35:15 thunderbird kernel: [<e0d84b48>] _nv003606rm+0xe4/0x114 [nvidia] Feb 17 07:35:15 thunderbird kernel: [<e0d846b8>] _nv003564rm+0x688/0x908 [nvidia] Feb 17 07:35:15 thunderbird kernel: [<e0cbf267>] _nv004046rm+0x3a3/0x3b0 [nvidia] Feb 17 07:35:15 thunderbird kernel: [<e0dc0b03>] _nv001476rm+0x1d3/0x45c [nvidia] Feb 17 07:35:15 thunderbird kernel: [<e0ca939a>] _nv000896rm+0x4a/0x64 [nvidia] Feb 17 07:35:15 thunderbird kernel: [<e0caabb4>] rm_isr_bh+0xc/0x10 [nvidia] Feb 17 07:35:15 thunderbird kernel: [<e0e0fab1>] nv_kern_isr_bh+0xf/0x13 [nvidia] Feb 17 07:35:15 thunderbird kernel: [<c01208b6>] tasklet_action+0x46/0x70 Feb 17 07:35:15 thunderbird kernel: [<c01206d0>] do_softirq+0x90/0xa0 Feb 17 07:35:15 thunderbird kernel: [<c010b56d>] do_IRQ+0xfd/0x130 Feb 17 07:35:15 thunderbird kernel: [<c01098b4>] common_interrupt+0x18/0x20 Feb 17 07:35:15 thunderbird kernel: Feb 17 07:35:15 thunderbird kernel: Badness in pci_find_subsys at drivers/pci/search.c:167 Feb 17 07:35:15 thunderbird kernel: Call Trace: Feb 17 07:35:15 thunderbird kernel: [<c01ec168>] pci_find_subsys+0xe8/0xf0 Feb 17 07:35:15 thunderbird kernel: [<c01ec19f>] pci_find_device+0x2f/0x40 Feb 17 07:35:15 thunderbird kernel: [<c01ebfa8>] pci_find_slot+0x28/0x50 Feb 17 07:35:15 thunderbird kernel: [<e0e1222a>] os_pci_init_handle+0x39/0x68 [nvidia] Feb 17 07:35:15 thunderbird kernel: [<e0ca685f>] _nv001243rm+0x1f/0x24 [nvidia] Feb 17 07:35:15 thunderbird kernel: [<e0d57a5d>] _nv003797rm+0xa9/0x128 [nvidia] Feb 17 07:35:15 thunderbird kernel: [<e0dc44a1>] _nv001490rm+0x55/0xe4 [nvidia] Feb 17 07:35:15 thunderbird kernel: [<e0ded154>] _nv000816rm+0x334/0x384 [nvidia] Feb 17 07:35:15 thunderbird kernel: [<e0d5592c>] _nv003801rm+0xd8/0x100 [nvidia] Feb 17 07:35:15 thunderbird kernel: [<e0decc4f>] _nv000809rm+0x2f/0x34 [nvidia] Feb 17 07:35:15 thunderbird kernel: [<e0d84b48>] _nv003606rm+0xe4/0x114 [nvidia] Feb 17 07:35:15 thunderbird kernel: [<e0d846b8>] _nv003564rm+0x688/0x908 [nvidia] Feb 17 07:35:15 thunderbird kernel: [<e0cbf267>] _nv004046rm+0x3a3/0x3b0 [nvidia] Feb 17 07:35:15 thunderbird kernel: [<e0dc0b03>] _nv001476rm+0x1d3/0x45c [nvidia] Feb 17 07:35:15 thunderbird kernel: [<e0ca939a>] _nv000896rm+0x4a/0x64 [nvidia] Feb 17 07:35:15 thunderbird kernel: [<e0caabb4>] rm_isr_bh+0xc/0x10 [nvidia] Feb 17 07:35:15 thunderbird kernel: [<e0e0fab1>] nv_kern_isr_bh+0xf/0x13 [nvidia] Feb 17 07:35:15 thunderbird kernel: [<c01208b6>] tasklet_action+0x46/0x70 Feb 17 07:35:15 thunderbird kernel: [<c01206d0>] do_softirq+0x90/0xa0 Feb 17 07:35:15 thunderbird kernel: [<c010b56d>] do_IRQ+0xfd/0x130 Feb 17 07:35:15 thunderbird kernel: [<c01098b4>]
common_interrupt+0x18/0x20Feb 17 07:35:15 thunderbird kernel:Thanks,
Thanos
-
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 · you
Hi to all,
Pls cc me as I am not subscribing.
I know that the kernel is tainted so pls don't flame ;)
The kernel is 2.6.2 from www.kernel.org and I use AGPGART for AGP (_not_ NvAGP). Fast Writes and SBA are enabled. FC1 is the distro. The mobo is Abit KG7 and the video card an FX5600.X stopped responding out of the blue, at a KDE 3.2 desktop, and it could not be killed either. The following messages were uncovered in my
/var/log/messages:
[snip]
Please first check to see if /etc/X11/XF86Config or /etc/X11/XF86Config-4 contains the string:
Option "RenderAccel" "1"
If it does, either remove the line or replace it with:
Option "RenderAccel" "0"
Render acceleration is still not working with the proprietary driver. I'm not saying it's definitely this, it just might not be related to the messages in syslog.
I occasionally see these badness messages in syslog, but my machine never locks up. I was under the impression that these were only warnings.
Signature · 8 lines
Cheers,
Alistair.
personal: alistair()devzero!co!uk
university: s0348365()sms!ed!ac!uk
student: CS/AI Undergraduate
contact: 7/10 Darroch Court,
University of Edinburgh.I checked it. "RenderAccel" is not set.
Maybe FW and SBA have something to do with it, but that's just a guess. Thanks.
Quoted 30 lines · Alistair John Strachan
Quoted 11 lines · you
Hi to all,
Pls cc me as I am not subscribing.
I know that the kernel is tainted so pls don't flame ;)
The kernel is 2.6.2 from www.kernel.org and I use AGPGART for AGP (_not_ NvAGP). Fast Writes and SBA are enabled. FC1 is the distro. The mobo is Abit KG7 and the video card an FX5600.X stopped responding out of the blue, at a KDE 3.2 desktop, and it could not be killed either. The following messages were uncovered in my
/var/log/messages:[snip]
Please first check to see if
/etc/X11/XF86Configor/etc/X11/XF86Config-4contains the string:Option "RenderAccel" "1"
If it does, either remove the line or replace it with:
Option "RenderAccel" "0"
Render acceleration is still not working with the proprietary driver. I'm not saying it's definitely this, it just might not be related to the messages in syslog.
I occasionally see these badness messages in syslog, but my machine never locks up. I was under the impression that these were only warnings.
I had the same problems with NVidia 1.0-5336 but there was no hint in /var/log/* that the NVidia driver caused the freeze. It wasn't necessary that X was running, loading the nvidia Module was sufficient to freeze the complete system after an unspecified amount of time.
For me, it worked to use the 1.0-5328 version with patches from www.minion.de. Since then, everything is working without problems.
I'm not on the list.
Thomas
Quoted 41 lines
I checked it. "RenderAccel" is not set.
Maybe FW and SBA have something to do with it, but that's just a guess. Thanks.Quoted 22 lines · Alistair John Strachan
Quoted 11 lines · you
Hi to all,
Pls cc me as I am not subscribing.
I know that the kernel is tainted so pls don't flame ;)
The kernel is 2.6.2 from www.kernel.org and I use AGPGART for AGP (_not_ NvAGP). Fast Writes and SBA are enabled. FC1 is the distro. The mobo is Abit KG7 and the video card an FX5600.X stopped responding out of the blue, at a KDE 3.2 desktop, and it could not be killed either. The following messages were uncovered in my
/var/log/messages:[snip]
Please first check to see if
/etc/X11/XF86Configor/etc/X11/XF86Config-4contains the string:Option "RenderAccel" "1"
If it does, either remove the line or replace it with:
Quoted 8 lines
Option "RenderAccel" "0"
Render acceleration is still not working with the proprietary driver. I'm not saying it's definitely this, it just might not be related to the messages in syslog.
I occasionally see these badness messages in syslog, but my machine never locks up. I was under the impression that these were only warnings.
-
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/
Indeed it shows up on my /var/log/messages* on two other occasions without hanging the system then. _But_ I had 5328 then. At least this badness shows up through 5328 and 5336, if that could provide a pointer to somebody (NVIDIA are you listening?)...
Quoted 54 lines · Thomas Weich
I had the same problems with NVidia 1.0-5336 but there was no hint in
/var/log/*that the NVidia driver caused the freeze. It wasn't necessary that X was running, loading the nvidia Module was sufficient to freeze the complete system after an unspecified amount of time.For me, it worked to use the 1.0-5328 version with patches from www.minion.de. Since then, everything is working without problems.
I'm not on the list.
Thomas
Quoted 42 lines
I checked it. "RenderAccel" is not set.
Maybe FW and SBA have something to do with it, but that's just a guess. Thanks.Quoted 24 lines · Alistair John Strachan
Quoted 11 lines · you
Hi to all,
Pls cc me as I am not subscribing.
I know that the kernel is tainted so pls don't flame ;) The kernel is 2.6.2 from www.kernel.org and I use AGPGART for AGP (_not_ NvAGP). Fast Writes and SBA are enabled. FC1 is the distro. The mobo is Abit KG7 and the video card an FX5600.X stopped responding out of the blue, at a KDE 3.2 desktop, and it could not be killed either. The following messages were uncovered in my
/var/log/messages:[snip]
Please first check to see if
/etc/X11/XF86Configor/etc/X11/XF86Config-4contains the string:Option "RenderAccel" "1"
If it does, either remove the line or replace it with:
Option "RenderAccel" "0"
Quoted 7 lines
Render acceleration is still not working with the proprietary driver. I'm not saying it's definitely this, it just might not be related to the messages in syslog.
I occasionally see these badness messages in syslog, but my machine never locks up. I was under the impression that these were only warnings.
-
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/