Soft lockup when starting iwlwifi

Bug #121285 reported by Kjetil Kjernsmo
4
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-image-2.6.20-16-generic

Since ipw3945 doesn't work on my Compal HGL30
 (due to the wireless kill switch issue http://ubuntuforums.org/showthread.php?t=246074 ), I've been experimenting with the new iwlwifi driver, which I found to be in the 2.6.20 Ubuntu kernels (nice!)

I've seen this problem twice now, the last time just after bootup. I go

modprobe -r ipw3945
modprobe -r iwlwifi

to start from scratch. When I go

modprobe iwlwifi

After a few seconds, iwlwifi takes 100% CPU, the computer becomes unresponsive to keyboard input, then after a while becomes unresponsive to anything.

This is written to the kern.log:
Jun 20 07:46:26 owl kernel: [ 225.844000] ACPI: PCI interrupt for device 0000:02:00.0 disabled
Jun 20 07:46:26 owl kernel: [ 225.852000] ieee80211_crypt: unregistered algorithm 'NULL'
Jun 20 07:47:00 owl kernel: [ 260.480000] iwlwifi: Intel(R) Wireless Link driver for Linux, 0.0.11
Jun 20 07:47:00 owl kernel: [ 260.480000] iwlwifi: Copyright(c) 2003-2006 Intel Corporation
Jun 20 07:47:00 owl kernel: [ 260.484000] ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 16
Jun 20 07:47:00 owl kernel: [ 260.484000] PCI: Setting latency timer of device 0000:02:00.0 to 64
Jun 20 07:47:00 owl kernel: [ 260.484000] iwlwifi: Detected Intel PRO/Wireless 3945ABG Network Connection
Jun 20 07:47:10 owl kernel: [ 270.056000] BUG: soft lockup detected on CPU#0!
Jun 20 07:47:10 owl kernel: [ 270.056000] [softlockup_tick+156/240] softlockup_tick+0x9c/0xf0
Jun 20 07:47:10 owl kernel: [ 270.056000] [update_process_times+51/128] update_process_times+0x33/0x80
Jun 20 07:47:10 owl kernel: [ 270.056000] [smp_apic_timer_interrupt+112/128] smp_apic_timer_interrupt+0x70/0x80
Jun 20 07:47:10 owl kernel: [ 270.056000] [apic_timer_interrupt+40/48] apic_timer_interrupt+0x28/0x30
Jun 20 07:47:10 owl kernel: [ 270.056000] [acpi_unmap_lsapic+43/112] acpi_unmap_lsapic+0x2b/0x70
Jun 20 07:47:10 owl kernel: [ 270.056000] [<f8a83068>] ipw_read32+0x8/0x10 [iwlwifi]
Jun 20 07:47:10 owl kernel: [ 270.056000] [<f8a8ace2>] ipw_bg_alive_start+0x162/0x10f0 [iwlwifi]
Jun 20 07:47:10 owl kernel: [ 270.056000] [schedule+765/2704] __sched_text_start+0x2fd/0xa90
Jun 20 07:47:10 owl kernel: [ 270.056000] [<f8a8312f>] ipw_clear_bit+0x1f/0x40 [iwlwifi]
Jun 20 07:47:10 owl kernel: [ 270.056000] [__wake_up+56/80] __wake_up+0x38/0x50
Jun 20 07:47:10 owl kernel: [ 270.056000] [run_workqueue+148/320] run_workqueue+0x94/0x140
Jun 20 07:47:10 owl kernel: [ 270.056000] [<f8a8ab80>] ipw_bg_alive_start+0x0/0x10f0 [iwlwifi]
Jun 20 07:47:10 owl kernel: [ 270.056000] [worker_thread+327/368] worker_thread+0x147/0x170
Jun 20 07:47:10 owl kernel: [ 270.056000] [default_wake_function+0/16] default_wake_function+0x0/0x10
Jun 20 07:47:10 owl kernel: [ 270.056000] [worker_thread+0/368] worker_thread+0x0/0x170
Jun 20 07:47:10 owl kernel: [ 270.056000] [kthread+186/240] kthread+0xba/0xf0
Jun 20 07:47:10 owl kernel: [ 270.056000] [kthread+0/240] kthread+0x0/0xf0
Jun 20 07:47:10 owl kernel: [ 270.056000] [kernel_thread_helper+7/16] kernel_thread_helper+0x7/0x10
Jun 20 07:47:10 owl kernel: [ 270.056000] =======================

Here, I think that removing ipw happened at 07:46:26, starting iwlwifi at 07:47:00 and the lockup at 07:47:10.

Revision history for this message
Launchpad Janitor (janitor) wrote : This bug is now reported against the 'linux' package

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 - http://www.ubuntu.com/testing . 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!

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

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.

--or--

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 http://www.ubuntu.com/testing 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.

Revision history for this message
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  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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