BUG: scheduling while atomic: swapper/0/0x00000100

[vincebusam]

Console output captured over serial port, the machine is completely dead after this:
[658752.042329] BUG: scheduling while atomic: swapper/0/0x00000100
[658752.048466] bad: scheduling from the idle thread!
[658821.141246] BUG: soft lockup - CPU#1 stuck for 61s! [swapper:0]
<last line repeats 50 more times>

No PPP! This happens about once a week.

Before installing the serial line, I saw these errors:
BUG: scheduling while atomic: ksoftirqd/1/7/0x0000100
BUG: soft lockup - CPU#1 stuck for 61s! events/1:10

And a partial stack trace that looked like this:
enqueue_task
activate_task
try_to_wake_up
default_wake_function
__wake_up_common
complete
firmware_loading_store
dev_attr_store
sysfs_write_file
vfs_write
sys_write
system_call_fastpath

I'll update with more prints/traces as they come in.

ProblemType: Bug
AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory
AplayDevices: Error: [Errno 2] No such file or directory
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
Date: Tue Feb 9 20:53:03 2010
DistroRelease: Ubuntu 9.10
MachineType: Dell Inc. PowerEdge T100
Package: linux-image-2.6.31-19-server 2.6.31-19.56
PciMultimedia:

ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.31-19-server root=/dev/mapper/hostname-root ro quiet console=tty0 console=ttyS0,115200n8
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-19.56-server
SourcePackage: linux
Uname: Linux 2.6.31-19-server x86_64
dmi.bios.date: 08/03/2009
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.4.1
dmi.board.name: 0T065F
dmi.board.vendor: Dell Inc.
dmi.board.version: A04
dmi.chassis.type: 7
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr1.4.1:bd08/03/2009:svnDellInc.:pnPowerEdgeT100:pvr:rvnDellInc.:rn0T065F:rvrA04:cvnDellInc.:ct7:cvr:
dmi.product.name: PowerEdge T100
dmi.sys.vendor: Dell Inc.

[vincebusam (vince-sixpak)]

Just saw this:
BUG: scheduling while atomic: swapper/0/0x10000100

I'm trying the newest upstream kernel now...

[vincebusam (vince-sixpak)]

This is reproducible in the upstream kernel as well (2.6.32-02063207-generic), so this is probably not an Ubuntu bug, I'll take this upstream. I'm also switching to an ethernet port on a free IRQ to see if that helps.

[425147.010006] ------------[ cut here ]------------
[425147.014726] WARNING: at /home/kernel-ppa/mainline/build/net/sched/sch_generic.c:261 d
[425147.024832] Hardware name: PowerEdge T100
[425147.028930] NETDEV WATCHDOG: eth1 (starfire): transmit queue 0 timed out
[425147.035725] Modules linked in: ip6t_LOG nf_conntrack_ipv6 ip6table_filter ip6_tables
[425147.072161] Pid: 0, comm: swapper Not tainted 2.6.32-02063207-generic #02063207
[425147.079567] Call Trace:
[425147.082116] <IRQ> [<ffffffff8145771f>] ? dev_watchdog+0x25f/0x270
[425147.088486] [<ffffffff81062157>] warn_slowpath_common+0x87/0xb0
[425147.094590] [<ffffffff81062204>] warn_slowpath_fmt+0x64/0x70
[425147.100430] [<ffffffff81018c00>] ? native_sched_clock+0x20/0x80
[425147.106524] [<ffffffff81288f4f>] ? strlcpy+0x4f/0x70
[425147.111673] [<ffffffff810187d9>] ? sched_clock+0x9/0x10
[425147.117074] [<ffffffff8143cfc3>] ? netdev_drivername+0x43/0x50
[425147.123090] [<ffffffff8145771f>] dev_watchdog+0x25f/0x270
[425147.128664] [<ffffffff81084fc5>] ? sched_clock_local+0x15/0x80
[425147.134681] [<ffffffff810725b9>] run_timer_softirq+0x189/0x2e0
[425147.140693] [<ffffffff814574c0>] ? dev_watchdog+0x0/0x270
[425147.146267] [<ffffffff8108dc3e>] ? tick_dev_program_event+0x3e/0xc0
[425147.152717] [<ffffffff8106939f>] __do_softirq+0xbf/0x1d0
[425147.158203] [<ffffffff8108dd25>] ? tick_program_event+0x25/0x30
[425147.164305] [<ffffffff8101312c>] call_softirq+0x1c/0x30
[425147.169704] [<ffffffff81014b85>] do_softirq+0x65/0xa0
[425147.174938] [<ffffffff810686a7>] irq_exit+0x77/0x80
[425147.179992] [<ffffffff8102d435>] smp_apic_timer_interrupt+0x45/0x60
[425147.186441] [<ffffffff81012af3>] apic_timer_interrupt+0x13/0x20
[425147.192538] <EOI> [<ffffffff8101a089>] ? mwait_idle+0x69/0xc0
[425147.198560] [<ffffffff81536c11>] ? atomic_notifier_call_chain+0x11/0x20
[425147.205358] [<ffffffff810107f7>] ? cpu_idle+0x97/0xe0
[425147.210591] [<ffffffff8152ec0e>] ? setup_APIC_timer+0x7e/0x90
[425147.216509] [<ffffffff8152e584>] ? start_secondary+0x94/0xc0
[425147.222351] ---[ end trace f7c602e50ac6e61c ]---
[425147.227057] eth1: Transmit timed out, status 0x00000000, resetting...
[425147.233600] ------------[ cut here ]------------
[425147.238307] WARNING: at /home/kernel-ppa/mainline/build/kernel/irq/manage.c:842 __fre
[425147.247890] Hardware name: PowerEdge T100
[425147.251995] Trying to free IRQ 19 from IRQ context!
[425147.256961] Modules linked in: ip6t_LOG nf_conntrack_ipv6 ip6table_filter ip6_tables
[425147.293392] Pid: 0, comm: swapper Tainted: G W 2.6.32-02063207-generic #02063
[425147.301585] Call Trace:
[425147.304124] <IRQ> [<ffffffff810bdfa2>] ? __free_irq+0x172/0x180
[425147.310325] [<ffffffff81062157>] warn_slowpath_common+0x87/0xb0
[425147.316418] [<ffffffff81062204>] warn_slowpath_fmt+0x64/0x70
[425147.322261] [<ffffffff81063297>] ? printk+0x67/0x70
[425147.327313] [<ffffffff810bdfa2>] __free_irq+0x172/0x180
[425147.332723] [<fffffff...

[Jeremy Foshee (jeremyfoshee)]

Hi vincebusam,

This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 519643

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]