Kernel-module "ipw2200" causes total kernel lockup on my notebook (Thinkpad R31)

Bug #114329 reported by Stefan Glasenhardt on 2007-05-12
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
linux-source-2.6.20 (Ubuntu)

Bug Description

Binary package hint: linux-source-2.6.20

When i'm using my Intel Pro/Wireless 2200BG mini-PCI wireless LAN-card, my notebook (Thinkpad R31) totally lockups after a few minutes of surfing.

I'm using Ubuntu 7.04 with the latest kernel version (2.6.20-15-generic). There is absolutely no entry in the syslog or messages-file and the magic Sysrq-keys don't work after the lockup.

The machine lockup seems only to happen when i'm logged into GNOME. When i'm using the text console without X11 the lockup has never appeared (1 hour of stress testing with multiple downloads and uploads).

Under GNOME the lockup can be caused by clicking a link in a browser, but the i cannot reproduce the bug directly. The lockups appear totally randomly (1 to 45 minutes of using the notebook). It makes no difference if i use WEP or WPA-encryption, using the network-manager, wpa_supplicant or the wireless-tools directly.

Because the Thinkpad has no serial port (i do not own a port replicator) if have no chance of using the serial console.

I'm trying to reproduce the lockup under different situations (e.g. naked X11 with only a windowmanager and a browser running) and trying to get a debug message.

gyp (gyp-impulzus) wrote :

The same happens to me on a Thinkpad R61: random lockups under heavy network traffic, although it happens much more rarely (once or twice a week while continuously running a torrent client).

I use:
- the latest Gutsy as of today
- stock Ubuntu 2.6.22-14.52 kernel
- ipw3495 network driver
- KDE 3.5.8
- (k)networkmanager connecting to a WPA-PSK network

There're no relevant entries in the syslog and MagicSysRQ-keys don't work either. After the lock-up, the computer is not reachable from it's network interfaces -- and I also don't have a port replicator to try a serial console.

I know it's very little information but it's a really annoying problem so I'm willing to put a lot of energy into helping you debug it if you provide me with some tips what to look for. (Remember that I can't do anything but turn off and on the computer after the lock-up and there's nothing in the logs. Also, the problem cannot be triggerred directly, it happens randomly once in every couple of days. Doesn't sound to promising, I know :))

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.


2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Michele Mangili (mangilimic) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in linux:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers