Messages in this thread | | | Date | Sun, 17 Oct 2004 09:42:37 +0000 | From | Nigel Kukard <> | Subject | Re: 2.6.9-rc4-bk2 bug report |
| |
Andrew Morton wrote:
>>>>While booting with 2.6.9rc4-bk2 I seem to get the below OOPS, I copied >>>>the modules & System.map file over to another box of mine where i used >>>>serial-console to grab the oops. >>>> >>>> >>Could it be caused by loading a module? >> >> >Yes. Or by unloading a module. The oops will happen some time _after_ the >buggy module has done its buggy thing. Maybe you could change your >modprobe command to be: > > echo running modprobe $* > modprobe.old $* > sleep 5 > echo finished modprobe $* > >or something like that. > > Ok, it seems to be related to specific hardware. I tried loading the exact same modules on another box in the exact same order, no crash. The box is actually running nicely.
I'm busy compiling the kernel again, this time with a few debug options ticked.
As far as I saw 2 days ago, its when I load uhci-hcd that the problem manifests itself... this is the order the modules are loaded in...
snd, snd_als4000, crc32, sis900, psmouse, evdev, tsdev, agpgart, sis_agp, pci_hotplug, usbcore, ohci_hcd, ub, ehci_hcd, ieee1394, ohci1394, uhci_hcd
The OOPS is triggered from loading uhci_hcd, so it could be ohci1394 that creates the corruption. I've had problems with ohci1394 in 26.8.1 aswell, I cannot load it, unload it, and reload it... generates a D state for the modprobe.
Any tips on how i can track down the offending line in source?
Regards Nigel Kukard
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |