Kernel-module "ipw2200" causes total kernel lockup on my notebook (Thinkpad R31)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
linux-source-2.6.20 (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned |
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-
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.
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 :))