BUG: soft lockup detected on CPU#0! (on PCMCIA eject)

[Luka Renko]

Binary package hint: linux-source-2.6.20

HW: HP nw8240
SW: Kubuntu Feisty, up-to-date
Kernel: Linux version 2.6.20-12-generic (root@palmer) (gcc version 4.1.2 (Ubuntu 4.1.2-0ubuntu4)) #2 SMP Wed Mar 21 20:55:46 UTC 2007

While I was testing if the bug 85905 is fixed, I have loaded my Compact Flash PCMCIA adapter loaded with Sandisk 2 GB card. It has properly detected the card:

[35310.708000] pccard: PCMCIA card inserted into slot 0
[35310.708000] cs: memory probe 0xc8400000-0xc87fffff: excluding 0xc8400000-0xc843ffff
[35310.720000] pcmcia: registering new device pcmcia0.0
[35310.956000] ata3: PATA max PIO0 cmd 0x00014100 ctl 0x0001410e bmdma 0x00000000 irq 3
[35310.956000] scsi2 : pata_pcmcia
[35311.116000] ata3.00: CFA: SanDisk SDCFH-2048, HDX 4.04, max PIO4
[35311.116000] ata3.00: 4001760 sectors, multi 0: LBA
[35311.116000] ata3.00: configured for PIO0
[35311.116000] scsi 2:0:0:0: Direct-Access ATA SanDisk SDCFH-20 HDX PQ: 0 ANSI: 5
[35311.120000] SCSI device sdb: 4001760 512-byte hdwr sectors (2049 MB)
[35311.120000] sdb: Write Protect is off
[35311.120000] sdb: Mode Sense: 00 3a 00 00
[35311.120000] SCSI device sdb: write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[35311.120000] SCSI device sdb: 4001760 512-byte hdwr sectors (2049 MB)
[35311.120000] sdb: Write Protect is off
[35311.120000] sdb: Mode Sense: 00 3a 00 00
[35311.120000] SCSI device sdb: write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[35311.120000] sdb: sdb1
[35311.128000] sd 2:0:0:0: Attached scsi removable disk sdb
[35311.128000] sd 2:0:0:0: Attached scsi generic sg2 type 0

When I was using the card (downloading cca 512 MB of photos with Digikam), I have noticed that my mouse movements got jerky and also general desktop response was a bit slow. I have not experience this kind of responses from desktop (at least Ubuntu ;-)) for years. But everything worked.

Then I have ejected the PCMCIA card and the system locked up. First it did not respond to anything, then I have tried to switch consoles and finally pressed Ctrl-Alt-Del which have responded with Kubuntu shotdown dialog. I have checked dmesg output and got this:

[35638.192000] ACPI Exception (exoparg2-0442): AE_AML_PACKAGE_LIMIT, Index (0FFFFFFFE) is beyond end of object [20060707]
[35638.192000] ACPI Error (psparse-0537): Method parse/execution failed [\_TZ_.C250] (Node df8412c0), AE_AML_PACKAGE_LIMIT
[35638.192000] ACPI Error (psparse-0537): Method parse/execution failed [\_TZ_.C24F] (Node df8412d4), AE_AML_PACKAGE_LIMIT
[35638.192000] ACPI Error (psparse-0537): Method parse/execution failed [\_TZ_.TZ1_._TMP] (Node df841824), AE_AML_PACKAGE_LIMIT
[35710.852000] ACPI Exception (exoparg2-0442): AE_AML_PACKAGE_LIMIT, Index (0FFFFFFFE) is beyond end of object [20060707]
[35710.852000] ACPI Error (psparse-0537): Method parse/execution failed [\_TZ_.C250] (Node df8412c0), AE_AML_PACKAGE_LIMIT
[35710.852000] ACPI Error (psparse-0537): Method parse/execution failed [\_TZ_.C24F] (Node df8412d4), AE_AML_PACKAGE_LIMIT
[35710.852000] ACPI Error (psparse-0537): Method parse/execution failed [\_TZ_.TZ1_._TMP] (Node df841824), AE_AML_PACKAGE_LIMIT
[35807.568000] ACPI Exception (exoparg2-0442): AE_AML_PACKAGE_LIMIT, Index (0FFFFFFFE) is beyond end of object [20060707]
[35807.568000] ACPI Error (psparse-0537): Method parse/execution failed [\_TZ_.C250] (Node df8412c0), AE_AML_PACKAGE_LIMIT
[35807.568000] ACPI Error (psparse-0537): Method parse/execution failed [\_TZ_.C24F] (Node df8412d4), AE_AML_PACKAGE_LIMIT
[35807.568000] ACPI Error (psparse-0537): Method parse/execution failed [\_TZ_.TZ1_._TMP] (Node df841824), AE_AML_PACKAGE_LIMIT
[37097.200000] pccard: card ejected from slot 0
[37097.200000] ata3.00: disabled
[37102.436000] ipw2200: Firmware error detected. Restarting.
[37102.916000] ipw2200: Firmware error detected. Restarting.
[37106.872000] BUG: soft lockup detected on CPU#0!
[37106.872000] [<c015348c>] softlockup_tick+0x9c/0xf0
[37106.872000] [<c0130583>] update_process_times+0x33/0x80
[37106.872000] [<c01154b0>] smp_apic_timer_interrupt+0x70/0x80
[37106.872000] [<c01042f8>] apic_timer_interrupt+0x28/0x30
[37106.872000] [<c02ee072>] _spin_lock_irqsave+0x32/0x50
[37106.872000] [<f8a28c4e>] ata_port_flush_task+0xe/0xc0 [libata]
[37106.872000] [<f8a34aba>] ata_scsi_error+0x1a/0x5a0 [libata]
[37106.872000] [<f8a0310e>] scsi_device_put+0x3e/0x40 [scsi_mod]
[37106.872000] [<f8a06dc6>] scsi_error_handler+0xa6/0xb40 [scsi_mod]
[37106.872000] [<c011e4f0>] complete+0x40/0x60
[37106.872000] [<f8a06d20>] scsi_error_handler+0x0/0xb40 [scsi_mod]
[37106.872000] [<c013ab8a>] kthread+0xba/0xf0
[37106.872000] [<c013aad0>] kthread+0x0/0xf0
[37106.872000] [<c01044c7>] kernel_thread_helper+0x7/0x10
[37106.872000] =======================

After this, the system is responding normally and I do not see any side effects of this lockup.

[Tim Gardner (timg-tpi)]

I can't decide if this is a problem with ipw2200 or with ACPI.

[Luka Renko (lure)]

I doubt it is ipw2200: I have seen similar Firmware error messages before, but wifi works here all the time.

I think the lockup is on sata/scsi stack trace, so I would expect that is one lead.

[Ankit Jain (luckyankit)]

I am having same problem with ipw2200 on Dell 600m though I don't know if it is an ipw2200 problem or some other problem.

[Ankit Jain (luckyankit)]

BTW I am using 2.6.20-14-generic and the lockup seems random (at least right now) to me.

[Ankit Jain (luckyankit)]

Same thing happens even if I blacklist module ipw2200. So I suspect this might not be related to ipw2200.

[gashad (pschmitt-gmail)]

I get this problem without inserting or ejecting a PCMCIA card, but my dmesg log would suggest otherwise:

[19919.104000] pccard: PCMCIA card inserted into slot 1
[19919.104000] pcmcia: registering new device pcmcia1.0
[19919.464000] input: Lid Switch as /class/input/input13
[19919.480000] ACPI: Lid Switch [LID]
[19919.524000] input: Power Button (CM) as /class/input/input14
[19919.536000] ACPI: Power Button (CM) [PBTN]
[19919.576000] input: Sleep Button (CM) as /class/input/input15
[19919.580000] agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
[19919.580000] agpgart: Putting AGP V2 device at 0000:00:00.0 into 1x mode
[19919.580000] agpgart: Putting AGP V2 device at 0000:01:00.0 into 1x mode
[19919.580000] [drm] Loading R200 Microcode
[19919.600000] ACPI: Sleep Button (CM) [SBTN]
[19919.760000] ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
[19920.652000] ACPI: CPU0 (power states: C1[C1] C2[C2] C3[C3] C4[C3])
[19920.652000] ACPI: Processor [CPU0] (supports 8 throttling states)
[19920.664000] ACPI: Thermal Zone [THM] (56 C)
[19920.756000] ACPI: AC Adapter [AC] (on-line)
[19921.048000] ACPI: Battery Slot [BAT0] (battery present)
[19921.048000] ACPI: Battery Slot [BAT1] (battery absent)
[19927.848000] ieee80211_crypt: registered algorithm 'WEP'
[19930.628000] eth1: no IPv6 routers present
[19940.224000] ADDRCONF(NETDEV_UP): eth1: link is not ready
[19941.600000] ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
[19956.652000] eth1: no IPv6 routers present
[21945.736000] BUG: soft lockup detected on CPU#0!

I get the "BUG: soft lockup detected on CPU#0!" bug very randomly while doing nothing, coding python in konsole, playing with firefox, thunderbird and rhythmbox. It will sometimes happen 30 seconds after booting my computer up, and other times happen several hours after working on my laptop. When the "BUG: soft lockup detected on CPU#0!" starts, the computer is pretty much unresponsive for 10 seconds... then I can interact with the computer for about 3 seconds, then the "BUG: soft lockup detected on CPU#0!" is output again and I lose control for 10 seconds, repeat ad infinium

The first time this happened was in Ubuntu 6.10 about 1 week ago, so I reformatted my drive and installed a fresh copy of ubuntu feisty 7.04... same problem persists.

$ uname -a
Linux pokey 2.6.20-16-generic #2 SMP Thu Jun 7 20:19:32 UTC 2007 i686 GNU/Linux

[gashad (pschmitt-gmail)]

Oh, and just so you know, this is a Dell Inspiron 600m with ipw2100 wireless card, and ati radeon mobility 9000 (using the software "ati" driver in my xorg configuration... I'm /NOT/ running fglrx. When I was running ubuntu 6.10 and had this problem, blacklisting the ipw2100 did not fix the problem...

[gashad (pschmitt-gmail)]

It just happened about 1/3 of the way through rebooting into recovery mode... see attached dmesg log

[gashad (pschmitt-gmail)]

I rebooted my machine using the Ubuntu 7.04 LiveCD, connected to a wireless network, surfed for a while... then the "BUG: Soft Lockup on CPU#0!" messages came... If i'm reading things right, the dmesg log would suggest it may be a problem with ipw2100:

[ 848.528000] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 956.052000] atkbd.c: Unknown key pressed (translated set 2, code 0x88 on isa0060/serio0).
[ 956.052000] atkbd.c: Use 'setkeycodes e008 <keycode>' to make it known.
[ 957.552000] ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
[ 967.900000] eth1: no IPv6 routers present
[ 1001.732000] ipw2100: Fatal interrupt. Scheduling firmware restart.
[ 1023.400000] ipw2100: Fatal interrupt. Scheduling firmware restart.
[ 1043.304000] ipw2100: Fatal interrupt. Scheduling firmware restart.
[ 1062.268000] ipw2100: Fatal interrupt. Scheduling firmware restart.
[ 1084.128000] ipw2100: Fatal interrupt. Scheduling firmware restart.
[ 1092.036000] ipw2100: Fatal interrupt. Scheduling firmware restart.
[ 1104.512000] BUG: soft lockup detected on CPU#0!
[ 1104.512000] [<c015353c>] softlockup_tick+0x9c/0xf0
[ 1104.512000] [<c0130633>] update_process_times+0x33/0x80
[ 1104.512000] [<c0106c45>] timer_interrupt+0x85/0xb0
[ 1104.512000] [<c01538c0>] handle_IRQ_event+0x30/0x60
[ 1104.512000] [<c015516d>] handle_level_irq+0x8d/0x120
[ 1104.512000] [<f08c8db0>] tg3_timer+0x0/0x810 [tg3]
[ 1104.512000] [<c0105b70>] do_IRQ+0x40/0x80
[ 1104.512000] [<f08c8db0>] tg3_timer+0x0/0x810 [tg3]
[ 1104.512000] [<c0104233>] common_interrupt+0x23/0x30
[ 1104.512000] [<f08c8db0>] tg3_timer+0x0/0x810 [tg3]
[ 1104.512000] [<f08c00d8>] tg3_chip_reset+0x168/0x630 [tg3]
[ 1104.512000] [<c011c112>] native_read_tsc+0x2/0x10
[ 1104.512000] [<c01f17d8>] delay_tsc+0x18/0x30
[ 1104.512000] [<c01f1836>] __delay+0x6/0x10
[ 1104.512000] [<f08bb2f6>] tg3_readphy+0x66/0x100 [tg3]
[ 1104.512000] [<f08be16b>] tg3_setup_copper_phy+0x1bb/0xc00 [tg3]
[ 1104.512000] [<c02a0e7c>] ip_rcv+0x2bc/0x500
[ 1104.512000] [<f08c8db0>] tg3_timer+0x0/0x810 [tg3]
[ 1104.512000] [<f08bed68>] tg3_setup_phy+0x1b8/0xe70 [tg3]
[ 1104.512000] [<c013f43a>] clocksource_get_next+0x3a/0x40
[ 1104.512000] [<c012fb54>] do_timer+0x234/0x820
[ 1104.512000] [<f08c8db0>] tg3_timer+0x0/0x810 [tg3]
[ 1104.512000] [<f08c943c>] tg3_timer+0x68c/0x810 [tg3]
[ 1104.512000] [<c0284cb3>] process_backlog+0x93/0x130
[ 1104.512000] [<c012f73f>] run_timer_softirq+0x12f/0x1a0
[ 1104.512000] [<c012b422>] __do_softirq+0x82/0x100
[ 1104.512000] [<c012b4f5>] do_softirq+0x55/0x60
[ 1104.512000] [<c0105b75>] do_IRQ+0x45/0x80
[ 1104.512000] [<c0219e2e>] acpi_hw_register_write+0x154/0x187
[ 1104.512000] [<c0104233>] common_interrupt+0x23/0x30
[ 1104.512000] [<f08317e2>] acpi_processor_idle+0x225/0x3f7 [processor]
[ 1104.512000] [<c0101409>] cpu_idle+0x49/0xd0
[ 1104.512000] [<c03d77f5>] start_kernel+0x365/0x420
[ 1104.512000] [<c03d7230>] unknown_bootoption+0x0/0x260
[ 1104.512000] =======================

$uname -a
Linux ubuntu 2.6.20-15-generic #2 SMP Sun Apr 15 07:36:31 UTC 2007 i686 GNU/Linux

Attaching relevant livecd dmesg, lspci, lsmod logs...

[gashad (pschmitt-gmail)]

I have started a related thread on the ubuntu forums:
http://ubuntuforums.org/showthread.php?t=483444

So far, nothing is fixing this problem... Please let me know what I can do to help resolve this problem ASAP... Unfortunately, I might have to switch distros if I can't this figured out reasonably soon... :-(

[Joshua (vauxje)]

I have the same laptop and the same issue. Adding 'noacpi noapic nolapic' to kernel boot options doesn't fix it. Swapping out the wireless card for a rt2500 chipset (using either the stock driver or ndiswrapper) doesn't fix it, either. It happens in both ubuntu and kubuntu - wiping the hard drive and installing from scratch. It doesn't happen in XP.

I'd been running a stock Feisty install with no extra repos and all apt-get updates as of Sunday (6/24/07). Since then I've been running XP to see if there's a hardware issue - and so far nothing. I'll be installing kubuntu again tonight and will post dmesg and lspci outputs once it happens.

[Joshua (vauxje)]

Here's the output from dmesg

[Joshua (vauxje)]

...and lsmod

[Joshua (vauxje)]

...and lspci

[Joshua (vauxje)]

...and uname -a

[Ankit Jain (luckyankit)]

I have a feeling that there might be something wrong with my laptop hardware. Have you guys tried another linux distributon or windows? I feel like its not a kernel problem as I have tried different kernels ranging from 2.6.15 to kernel from kernel.org and he same problem persists.

[gashad (pschmitt-gmail)]

I noticed that when I get the error, a bunch of references to "tg3" are made... For example:
[ 1104.512000] [<f08c8db0>] tg3_timer+0x0/0x810 [tg3]
[ 1104.512000] [<c0105b70>] do_IRQ+0x40/0x80
[ 1104.512000] [<f08c8db0>] tg3_timer+0x0/0x810 [tg3]
[ 1104.512000] [<c0104233>] common_interrupt+0x23/0x30
[ 1104.512000] [<f08c8db0>] tg3_timer+0x0/0x810 [tg3]
[ 1104.512000] [<f08c00d8>] tg3_chip_reset+0x168/0x630 [tg3]

The tg3 module is for my wired ethernet connection. Removing the "tg3" module from the kernel seems to have fixed my problem... I don't get the "BUG: Soft lockup detected" error anymore, but now I can't use wired ethernet on my laptop :(

[Leann Ogasawara (leannogasawara)]

Hi Luka,

Can you confirm if this is still an issue in the latest Hardy Alpha release? We'll keep this report open against the actively developed kernel but will close this against 2.6.20. Thanks.

[Leann Ogasawara (leannogasawara)]

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.

[gashad (pschmitt-gmail)]

I no longer use Ubuntu, so I cannot perform this test now.

When I was still using Ubuntu, it seems like 8.04 fixed my "soft lockup
detected" bug anyway.

On Thu, Aug 28, 2008 at 7:38 PM, Leann Ogasawara <email address hidden> 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.
>
> ** Tags added: cft-2.6.27
>
> --
> BUG: soft lockup detected on CPU#0! (on PCMCIA eject)
> https://bugs.launchpad.net/bugs/95143
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Pete

[Launchpad Janitor (janitor)]

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

[etali (etali)]

This bug report is being closed due to your last comment regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status . Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.