[Bug 10265] New: yenta_socket IRQ woes w/ NetGear WG511T ("IRQ#11: nobody cared" either, but a different one)
bugzilla-daemon at bugzilla.ubuntu.com
bugzilla-daemon at bugzilla.ubuntu.com
Thu Apr 28 22:03:51 UTC 2005
Please do not reply to this email. You can add comments at
http://bugzilla.ubuntu.com/show_bug.cgi?id=10265
Ubuntu (patch) | linux
Summary: yenta_socket IRQ woes w/ NetGear WG511T ("IRQ#11: nobody
cared" either, but a different one)
Product: Ubuntu
Version: unspecified
Platform: i386
URL: http://lkml.org/lkml/2005/3/19/11
OS/Version: Linux
Status: NEW
Keywords: patch
Severity: major
Priority: P2
Component: linux
AssignedTo: fabbione at ubuntu.com
ReportedBy: dom at kilimandjaro.dyndns.org
QAContact: kernel-bugs at lists.ubuntu.com
I have the exact same configuration and symptoms as discussed on the LKML and solved
by Daniel Ritz a few days ago (see this bug's title URL for the thread): Medion
laptop, Netgear WG511T CardBus wifi card in yenta_socket PCMCIA controller => no Wifi
joy on a random basis about 9 cold boots out of 10, card appears to hang halfway
through the WLAN hooking process and "IRQ#11: nobody cared" shows up in dmesg.
NOTE: this appears related to, but NOT a duplicate of bug #5234, as my problem +
solution is CardBus-specific. I'm no IRQ routing expert though, and I could be wrong.
Anyway, to solve my problem, I need to *both* boot with the irqpoll option *and* apply
the two patches recommended by Daniel Ritz in the aforementioned thread. I am
attaching said (consolidated) patch against Ubuntu's 2.6.10-5-686 kernel source base
(one should apply it to the sources after everything in debian/patches).
Please (oh, please! :-) apply the patch to Hoary's kernel, even if you do not intend
to make irqpoll the default in order to solve #5234: as you'll understand, no Wifi
means that this Ubuntu zealot's preaching mission is jeopardized :-)
--
Configure bugmail: http://bugzilla.ubuntu.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
More information about the kernel-bugs
mailing list