[Bug 89464] [NEW] Keyboard killed when using hostap_pci with NetworkManager

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Binary package hint: linux-source-2.6.20

Description of the problem:
Reloading the hostap_pci module while in GNOME and using NetworkManager eventually stops all keyboard input (bar sysrq) from being registered.

Steps to reproduce:
1. Boot the machine into GNOME .
2. Start a gnome-terminal .
3. Become root using
/usr/bin/sudo -s
4. Run the following:
modprobe -r prism2_pci orinoco_pci hostap_pci && modprobe hostap_pci
5. Wait for NetworkManager to attach to a previously chosen network (or go to the NetworkManager applet and enter an ESSID to connect to.

Expected results:
To connect to access point specified. Computer to have a working network connection and keyboard input to continue to be accepted (e.g. respond to caps lock).

Actual results:
NetworkManager spends longer trying to connect than it does when using orinoco_pci drivers. When it brings up /sbin/wpa_supplicant keyboard seemingly stops working accept for sysrq keys (assuming sysrq is enabled). Computer does not respond to power button request to shut down. Can't swap to a virtual console. Mouse input continues to work.

Bizarrely I was able to do a safe shutdown by copying and pasting the individual letters of
shutdown -r now
along with a newline into a gnome-terminal that happened to already have root. The computer took over five minutes to get to the "Halting computer" stage and did not power off.

How reproducible is this bug?
This bug is reproducible every time.

Version Information
Ubuntu Feisty (Herd 5)
linux-image-2.6.20-9-generic

** Affects: linux-meta (Ubuntu)
     Importance: Medium
     Assignee: Ubuntu Kernel Team (ubuntu-kernel-team)
         Status: Confirmed

-- 
Keyboard killed when using hostap_pci with NetworkManager
https://bugs.launchpad.net/bugs/89464
You received this bug notification because you are a member of Kernel Bugs, which is subscribed to linux-meta in ubuntu.