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

[W. Scott Lockwood III]

1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu.

Description: Ubuntu lucid (development branch)
Release: 10.04

2) The version of the package you are using, via 'apt-cache policy packagename' or by checking in Synaptic.

linux:
  Installed: 2.6.32.19.20
  Candidate: 2.6.32.19.20
  Version table:
 *** 2.6.32.19.20 0
        500 http://us.archive.ubuntu.com/ubuntu/ lucid/main Packages
        100 /var/lib/dpkg/status

3) What you expected to happen

On occasion, after bringing up the system and logging in, the option to connect to the CDMA network via my CDMA card is missing from the network manager icon. I expected that to be there. Running pppd manually works, so it's not the card.

4) What happened instead

If I slide the wifi switch on the side of my Dell D-630 into the off position, wait a few moments, and then turn it back on, the crash happens. This switch is only supposed to disable or enable the antenna.

ProblemType: KernelOops
DistroRelease: Ubuntu 10.04
Package: linux-image-2.6.32-19-generic 2.6.32-19.28
Regression: Yes
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1
Uname: Linux 2.6.32-19-generic i686
NonfreeKernelModules: openafs nvidia
AlsaVersion:
 Advanced Linux Sound Architecture Driver Version 1.0.22.1.
 Compiled on Apr 1 2010 for kernel 2.6.32-19-generic (SMP).
Annotation: Your system might become unstable now and might need to be restarted.
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: scott 2160 F.... pulseaudio
 /dev/snd/seq: timidity 2064 F.... timidity
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf6ffc000 irq 29'
   Mixer name : 'SigmaTel STAC9205'
   Components : 'HDA:838476a0,102801f9,00100204'
   Controls : 20
   Simple ctrls : 12
Date: Mon Apr 5 07:40:15 2010
Failure: oops
HibernationDevice: RESUME=UUID=82c561af-7c82-4509-a97d-3eec549d8b43
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
MachineType: Dell Inc. Latitude D630
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-19-generic root=UUID=24e105f5-a650-48a0-8645-8fffe413b77e ro quiet splash
RelatedPackageVersions: linux-firmware 1.33
SourcePackage: linux
Title: BUG: scheduling while atomic: swapper/0/0x10010000
dmi.bios.date: 11/24/2008
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A15
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA15:bd11/24/2008:svnDellInc.:pnLatitudeD630:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Latitude D630
dmi.sys.vendor: Dell Inc.

[W. Scott Lockwood III (wsl3)]

dmesg.log

[W. Scott Lockwood III (wsl3)]

lsb_release-rd.log

[W. Scott Lockwood III (wsl3)]

lspci-vnvn.log

[W. Scott Lockwood III (wsl3)]

policy-pkg-output.log

[W. Scott Lockwood III (wsl3)]

uname -a

Linux scott-d630 2.6.32-19-generic #28-Ubuntu SMP Wed Mar 31 17:46:20 UTC 2010 i686 GNU/Linux

[W. Scott Lockwood III (wsl3)]

version

Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1

[Chase Douglas (chasedouglas)]

@Scott:

The oops text normally contains data we need to debug the issue. However, for these bugs the data is useless. To get the data we need, please do the following:

$ sudo sh -c "echo function > /sys/kernel/debug/tracing/current_tracer"

Trigger the bug, then capture the trace output:

$ cat /sys/kernel/debug/tracing/trace | bzip2 -c > trace.bz2

Then upload trace.bz2 to this bug report.

Thanks

[W. Scott Lockwood III (wsl3)]

On Tue, 2010-04-06 at 19:24 +0000, Chase Douglas wrote:
> $ cat /sys/kernel/debug/tracing/trace | bzip2 -c > trace.bz2

It hangs at the command line and doesn't return.

--
OOC:
W. Scott Lockwood III / US2009033817 / IL 013-D Chicago
Mage VST / aDC Web Monkey / GL aRST Forsaken
Cam Wiki Admin (Awakening)

[Chase Douglas (chasedouglas)]

@Scott:

Try this instead:

$ cat /sys/kernel/debug/tracing/trace > trace
$ bzip2 trace

Then upload the resulting trace.bz2 file

Thanks

[W. Scott Lockwood III (wsl3)]

Got it - here's the trace.

[Chase Douglas (chasedouglas)]

@Scott:

Great! The trace gives me good information. Unfortunately, I forgot one important step: enabling the proper trace format. To make sure I don't repeat the same mistake again, I wrote up the process on a wiki page. Can you follow it and attach a new trace with the correct latency-format?

https://wiki.ubuntu.com/KernelTeam/DebuggingSchedulingWhileAtomic

Thanks

[W. Scott Lockwood III (wsl3)]

lol - ok. It will have to wait until later today when I get off work
(busy at the moment). Also, if you will need anything else, let me know
as I am about to rebuild the affected machine.

On Wed, 2010-04-07 at 13:55 +0000, Chase Douglas wrote:
> @Scott:
>
> Great! The trace gives me good information. Unfortunately, I forgot one
> important step: enabling the proper trace format. To make sure I don't
> repeat the same mistake again, I wrote up the process on a wiki page.
> Can you follow it and attach a new trace with the correct latency-
> format?
>
> https://wiki.ubuntu.com/KernelTeam/DebuggingSchedulingWhileAtomic
>
> Thanks
>

--
W. Scott Lockwood III <email address hidden>

[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 development release http://cdimage.ubuntu.com/daily-live/current/ . 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.]