|
Bugzilla – Full Text Bug Listing |
| Summary: | e100 crashing | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE Linux 10.1 | Reporter: | Terje Bergström <terje.bergstrom> |
| Component: | Kernel | Assignee: | Karsten Keil <karsten.keil> |
| Status: | RESOLVED INVALID | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | ||
| Version: | Beta 2 | ||
| Target Milestone: | --- | ||
| Hardware: | x86 | ||
| OS: | SUSE Other | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
Hardware info taken with SUSE 10.0
boot.msg from a working 10.0 install boot.msg from a 10.0 updated to 10.1 Beta 2. e100 crashes later. boot.msg taken from a fresh install of 10.1 Beta 2 |
||
|
Description
Terje Bergström
2006-01-28 19:05:57 UTC
Hmm, then the reason maybe different boot options or some different module settings/usage. In the working configuration does it also use IRQ 11 and the e100 driver ? Please also attach a hwinfo for your HW. Created attachment 65549 [details]
Hardware info taken with SUSE 10.0
Hardware info taken with working 10.0 install
Created attachment 65550 [details]
boot.msg from a working 10.0 install
Created attachment 65551 [details]
boot.msg from a 10.0 updated to 10.1 Beta 2. e100 crashes later.
Created attachment 65553 [details]
boot.msg taken from a fresh install of 10.1 Beta 2
I attached three boot.msg's. In each IRQ 11 was assigned to e100. The default boot options are used, and they're the same in each case. The difference was that in 10.1 fresh install a resume= option is added. No module options are provided for e100. It seems that the fresh install do not use e100 but eepro100, can you try to load eepro100 ? I have already downgraded the non-working 10.1 upgrade. This line: <6>e100: eth0: e100_probe: addr 0xfe8ff000, irq 11, MAC addr 00:03:0D:03:7A:B6 makes me think that it's actually e100 that took over the card, and not eepro100. The message doesn't signal a crash, but says an interrupt arrived and was handled neither by e100 nor by the USB stack. Please compare your modules.conf files and attach hwinfo output for both configurations. It may not be the e100 driver that's broken - could also be USB. Note the many USB errors in the non-working case. Try disabling ehci_hcd (by moving the module out of /lib/modules, or by blacklisting it in modules.conf), reboot. Then reenable ehci_hcd, disable, e100, reboot. This should tell us more. There's a fix for the ehci bios issue that could cause this irq issue (but it should show up when the ehci driver is being loaded). It's in the kernel of the day, if you could try that. I removed uhci_hcd and ehci_hcd, rebooted. I got the same stray irq 11 message, except that the usb_hcd_irq line was missing. I put the modules back, and removed e100. Still the same message, except of course usb_hcd_irq line was back, but e100 line wasn't there. It seems this got stuck in NEEDINFO. :-( I don't have this system installed anymore (replaced with a fresh install of OpenSUSE), so I cannot provide any more logs/info. Ok, will close this bug then, thanks for letting us know. |