Keyboard killed when using hostap_pci with NetworkManager

Unfortunately, this is a very difficult bug for us to reproduce without the same hardware. Can you please attach the kern.log after you've done this and shutdown -r now?

(Also, does the problem still occur if after you modprobe you do a "sudo iwconfig wlan0 mode managed"?)

Thanks!
  Kyle

Please find kern.log attached.

I ran
sudo iwconfig wlan0 mode managed
but that command just wound up hanging.

Interestingly I did a
watch cat /proc/interrupts
and
1: 1003 XT-PIC-XT i8042
which appears to be my PS/2 keyboard continued to increase only when I pressed keys on the keyboard. However the input was never registered by X (and I could not switch to a virtual terminal).

Wifi card is a Netgear MA311:
00:0f.0 Network controller: Intersil Corporation Prism 2.5 Wavelan chipset (rev 01)

I will also add that is running the 1.8.4 firmware.

I have same problem on an IBM Thinkpad T30 with Prism2 (internal IBM "mini PCI" card) running hostap driver.

I see that NM disconnects from my WPA network with "sudo iwconfig wlan0 essid x mode managed", but then fails to connect to an unencrypted network -- in fact, it pretty much freezes the desktop. I lose keyboard, and notice that the Gnome system monitor status applets also freeze, I cannot open new windows (using Gnome applets). Only the mouse appears to work.

I can sometimes turn the system off, but not always. In those cases when it failed to shut off after 30 seconds, I have not had the patience to wait to see if it will eventually turn off by itself. Actual system shutoff does not happen -- it says it will shutdown in the console after unmounting drives -- but this perhaps an unrelated bug:

https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.15/+bug/43961

https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/104741

The same happens to me with hostap_cs and NetworkManager. NetworkManager scans and sees all APs but fails to associate or get an IP address when I select my AP. After ~60 seconds the NM swirling icon freezes and keyboard input does not work at all though I can still use the mouse (programs don't run however the logout prompt comes up) and the system monitor on the panel showing CPU usage still scrolls by. Once, whilst trying to find out what was happening, I ran a watch on the end of syslog or messages and I seem to remember something coming up along the lines of 'Unrecognised keycode 0x#### on serio i8042'... or something like this as soon as the keyboard locked up. I have unfortunately not been able to reproduce this yet. Perhaps the keyboard is losing it's interrupt? The only way I can shut down my laptop is to manually power off - clicking shutdown on the logout prompt does not work. I'm using Prism station firmware 1.7.4.

Also, this bug might be related:
<a href="https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/57146">bug #57146</a>

Hi Kyle -

I experienced the same issue using Ubuntu Gutsy Gibbon (7.10) while attempting to configure my wireless network with a Hannstar MV-4WL-138G V2 R3.01 PCI wireless card. This card is surplus to my requirements but may be useful to you to help diagnose the cause of the issue. Contact me at ben ta fluid logic tod org or via skype at reverse(nesaalkneb) to arrange for me to send you this card with my compliments.

Kudos to Sitsofe for an excellent bug report.

This issue no longer seems reproducible for me in Hardy beta.

Ubuntu hardy (development branch)
linux-image-2.6.24-12-generic 2.6.24-12.22

I take it back. This just happened to me although the steps to reproduce it are no longer so straightforward.

Version information:
Ubuntu hardy (development branch)
linux-image-2.6.24-12-generic 2.6.24-12.22

Using Hardy, I have encountered this several times.
Once or twice, I was able to copy-paste existing letters to do a chvt 1. That terminal worked, and I was able to kill some running NetworkManager processes, which ultimately allowed use of the keyboard to resume back in X.
So, is this a NM issue? Or is it possible that something in the UI-Framework is allowing NM to capture the Keyboard and prevent other apps from getting it? A GTK+ problem??

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

This is not a bug in the linux-meta package, moving to the linux package.

Let's close this bug as invalid as I haven't used the hardware that caused it for several years.