** Description changed:
+ SRU Justification:
+
+ Impact: Booting with the Senao NL-2511CD (PRISM II compatible) wireless
+ card can generate a kernel oops in the hostap interrupt handler.
+
+ Spurious shared interrupts or early probing interrupts can cause the
+ hostap interrupt handler to oops before the driver has fully configured
+ the IO base port addresses. In some cases the oops can be because the
+ hardware shares an interrupt line, on other cases it is due to a race
+ condition between probing for the hardware and configuring the IO base
+ port. The latter occurs because the probing is required to determine the
+ hardware port address which is only determined when the probe can
+ interrupt the hardware (catch 22).
+
+ Fix: This patch catches this pre-configured condition in the interrupt
+ handler to avoid the oops.
+
+ Testcase: Without the patch a kernel oops occurs on boot when the card
+ is installed. With the patch, there is no kernel oops and the wireless
+ card works.
+
+ ---
+
Binary package hint: linux-image-2.6.26-5-generic
Hello,
I have a Senao NL-2511CD Plus Ext2 on a Dell Inspiron 4150 notebook running
Ubuntu Intrepid (development release) with the latest kernel 2.6.26-5. I have
observed this behavior in kernel releases since Gutsy (when I started using
linux on this laptop with this card).
Whenever the card is inserted on boot, a kernel panic occurs on the hostap_cs
drivers (see screenshot).
If I insert the card once all the modules are loaded, it detects, works and
acts normally with no errors in dmesg.
I am aware of the existing bug where the orinoco drivers are loaded
along with the hostap drivers when detecting these cards, and I have
blacklisted the orinoco drivers. Regardless, this happens with or
without the orinoco drivers blacklisted.
Here is the output from hostap_diag:
NICID: id=0x800c v1.0.0 (PRISM II (2.5) PCMCIA (SST parallel flash))
PRIID: id=0x0015 v1.1.1
STAID: id=0x001f v1.8.2 (station firmware)
I had the stock firmware on the card and flashed it to see if it made a
difference, and it doesn't.
What REALLY threw me for a loop was when I was trying to get console
output via serial to post the debugging output of this crash (booting
with linux option console=ttyS0,9600,8,n,1), it would detect the card
and not crash while booting! But, I got a framebuffer driver working
nicely and managed to snap a picture.
** Also affects: linux (Ubuntu Jaunty)
Importance: Undecided
Status: New
** Also affects: linux-ubuntu-modules-2.6.24 (Ubuntu Jaunty)
Importance: Undecided
Status: New
** Changed in: linux-ubuntu-modules-2.6.24 (Ubuntu)
Status: New => Invalid
** Changed in: linux-ubuntu-modules-2.6.24 (Ubuntu Jaunty)
Status: New => Invalid
** Changed in: linux (Ubuntu Jaunty)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Jaunty)
Status: New => Fix Committed
** Changed in: linux (Ubuntu Jaunty)
Assignee: (unassigned) => Colin King (colin-king)
** Changed in: linux (Ubuntu)
Status: Incomplete => In Progress
--
hostap_cs causes kernel oops on 2.6.26 with senao nl-2511cd
https://bugs.launchpad.net/bugs/254837
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
