Ubuntu
linux-ubuntu-modules-2.6.22 package

booting with iwl4965 enabled (via the kill switch) crashes the kernel on Thinkpad T61P

Bug #133239 reported by Michael R. Head
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux-ubuntu-modules-2.6.22 (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

I just got a brand new Thinkpad T61P and I've installed Ubuntu on it (after working through some troubles). In hopes of getting wireless working (the hardware is iwl4965-based), I upgraded to gutsy. Unfortunately, the kernel crashes during boot when the wireless is enabled via the "kill switch." The kernel trace doesn't appear to be dumped into any files, presumably because it kills the kernel so abruptly.

The symptoms are that a little way through the initial boot, the progress bar stops, and the caps lock LED blinks on and off.

If I boot in "rescue mode," after exiting the prompt to allow the boot to continue, it gets a ways through the process then dumps a bunch of kernel crash data, more than a screenfull.

Under feisty, of course, there were no 4965 drivers, so there's no crash when using the 2.6.20 kernel.

Revision history for this message
Michael R. Head (burner) wrote :
Revision history for this message
Michael R. Head (burner) wrote :
Revision history for this message
Michael R. Head (burner) wrote :

It appears that switching the kill switch back on after a successful boot does not lead to a crash.

Revision history for this message
Michael R. Head (burner) wrote :

And I can confirm that wireless is working with network-manager under these circumstances (kill switch positioned "off" during boot and switched "on" after boot)

Revision history for this message
Michael R. Head (burner) wrote :

After some time, the driver stops working:
Aug 17 18:57:11 phoenix kernel: [ 2507.880000] [<f88b3690>] (usb_hcd_irq+0x0/0x60 [usbcore])
Aug 17 18:57:11 phoenix kernel: [ 2507.880000] Disabling IRQ #23
Aug 17 18:59:07 phoenix kernel: [ 2623.068000] iwl4965: ipw going down
Aug 17 18:59:09 phoenix kernel: [ 2625.300000] iwl4965: Unhandled INTA bits 0x04000000
Aug 17 18:59:09 phoenix kernel: [ 2625.300000] iwl4965: Disabled INTA bits 0x04000000 were pending
Aug 17 18:59:09 phoenix kernel: [ 2625.300000] iwl4965: with FH_INT = 0x00010000
Aug 17 18:59:09 phoenix kernel: [ 2625.304000] iwl4965: REPLY_CT_KILL_CONFIG_CMD succeeded
Aug 17 18:59:13 phoenix NetworkManager: <WARN> request_and_convert_scan_results(): card took too much time scanning. Get a better one.
Aug 17 19:00:13 phoenix NetworkManager: <debug> [1187391613.440923] nm_device_802_11_wireless_get_activation_ap(): Forcing AP 'CourtStreetWireless'
Aug 17 19:00:13 phoenix NetworkManager: <info> User Switch: /org/freedesktop/NetworkManager/Devices/wlan0 / CourtStreetWireless
Aug 17 19:00:13 phoenix NetworkManager: <info> Deactivating device wlan0.
Aug 17 19:00:13 phoenix dhclient: There is already a pid file /var/run/dhclient.wlan0.pid with pid 14478
Aug 17 19:00:13 phoenix dhclient: killed old client process, removed PID file
Aug 17 19:00:13 phoenix dhclient: wmaster0: unknown hardware address type 801
Aug 17 19:00:13 phoenix dhclient: wmaster0: unknown hardware address type 801
Aug 17 19:00:13 phoenix dhclient: DHCPRELEASE on wlan0 to 192.168.51.1 port 67
Aug 17 19:00:13 phoenix avahi-daemon[7133]: Withdrawing address record for 192.168.51.246 on wlan0.
Aug 17 19:00:13 phoenix avahi-daemon[7133]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.51.246.
Aug 17 19:00:13 phoenix avahi-daemon[7133]: Interface wlan0.IPv4 no longer relevant for mDNS.
Aug 17 19:00:14 phoenix NetworkManager: <info> SUP: sending command 'DISABLE_NETWORK 0'
Aug 17 19:00:14 phoenix kernel: [ 2690.740000] wlan0: disassociate(reason=3)
Aug 17 19:00:14 phoenix NetworkManager: <info> SUP: response was 'OK'
Aug 17 19:00:14 phoenix avahi-daemon[7133]: Withdrawing address record for fe80::213:e8ff:fe83:7a2f on wlan0.

Note that this happened shortly after the trigger of bug 126369

Revision history for this message
Michael R. Head (burner) wrote :

I don't know if there's been an update, but I booted today with wireless enabled and didn't experience a kernel lockup. I've also been using the wireless card for a while now without the deactivation. I suggest keeping this open for a while longer to see if the problem is solved or if it is just non-deterministic.

Revision history for this message
Michael R. Head (burner) wrote :

Hmph... must have been a one time fluke somehow, because I can't get the machine to boot with wireless enabled again.

Revision history for this message
Michael R. Head (burner) wrote :

Ok, 2.6.22-10-generic appears to fix it, since it includes version 1.0.0-1k of the iwl4965 driver.

Cheers!

Changed in linux-ubuntu-modules-2.6.22:
status: New → Fix Released
Revision history for this message
Adrianus (adrianus-kurnadi) wrote :

I still experience kernel crash (caps lock blinking) on my Acer Travelmate 6292 using Ubuntu 8.04.
I have updated the kernel to the latest in Ubuntu main repository, but the issue still happens.
I notice that when I don't have wireless access point nearby this issue didn't appear.
If 2.6.22-10-generic has fix it then there must be a regression since I believe I now has higher kernel version.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.