BUG: Scheduling while atomic in fuse_notify_inval_entry

Bug #687599 reported by Nikolaus Rath
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Linux
Fix Released
Medium
linux (Ubuntu)
Incomplete
Medium
Unassigned

Bug Description

This happens randomly about once a day since upgrading from Lucid to Maverick. Sometimes it causes the system to freeze, sometimes only a specific application. In this very instance, it completely froze mplayer (even though the logs talk about Python).

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: linux-image-2.6.35-23-generic 2.6.35-23.41
Regression: Yes
Reproducible: No
ProcVersionSignature: Ubuntu 2.6.35-23.41-generic 2.6.35.7
Uname: Linux 2.6.35-23-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: nikratio 2743 F.... pulseaudio
 /dev/snd/pcmC0D0p: nikratio 2743 F...m pulseaudio
 /dev/snd/controlC1: nikratio 2743 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xfe9f8000 irq 46'
   Mixer name : 'Realtek ALC662 rev1'
   Components : 'HDA:10ec0662,10280285,00100101'
   Controls : 27
   Simple ctrls : 16
Card1.Amixer.info:
 Card hw:1 'Webcam'/'OmniVision Technologies, Inc.538-2640-08.09.09.1 Monitor Webcam at usb-0000:00:'
   Mixer name : 'USB Mixer'
   Components : 'USB05a9:2649'
   Controls : 4
   Simple ctrls : 3
Card2.Amixer.info:
 Card hw:2 'HDMI'/'HDA ATI HDMI at 0xfeaec000 irq 46'
   Mixer name : 'ATI R6xx HDMI'
   Components : 'HDA:1002aa01,00aa0100,00100100'
   Controls : 4
   Simple ctrls : 1
Card2.Amixer.values:
 Simple mixer control 'IEC958',0
   Capabilities: pswitch pswitch-joined penum
   Playback channels: Mono
   Mono: Playback [on]
Date: Wed Dec 8 18:28:25 2010
EcryptfsInUse: Yes
Frequency: Once a day.
HibernationDevice: RESUME=/dev/mapper/vg0-swap_crypt
IwConfig: Error: [Errno 2] No such file or directory
MachineType: Dell Inc. Vostro 220s Series
ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.35-23-generic root=/dev/mapper/vg0-root ro quiet splash
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.utf8
 SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.38
RfKill: Error: [Errno 2] No such file or directory
SourcePackage: linux
UdevDb: Error: [Errno 2] No such file or directory
WpaSupplicantLog:

dmi.bios.date: 10/24/2008
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.0.3
dmi.board.name: 0P301D
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr1.0.3:bd10/24/2008:svnDellInc.:pnVostro220sSeries:pvr:rvnDellInc.:rn0P301D:rvrA00:cvnDellInc.:ct3:cvr:
dmi.product.name: Vostro 220s Series
dmi.sys.vendor: Dell Inc.

Revision history for this message
Nikolaus Rath (nikratio) wrote :
Revision history for this message
Nikolaus Rath (nikratio) wrote :

I have learned that the following is useful for debugging "scheduling while
atomic" bugs. The respective files are attached:

$ sudo sh -c "echo 1 > /sys/kernel/debug/tracing/options/latency-format"
$ sudo sh -c "echo 1 > /sys/kernel/debug/tracing/tracing_enabled"
$ sudo sh -c "echo 1 > /sys/kernel/debug/tracing/tracing_on"
$ sudo sh -c "echo function > /sys/kernel/debug/tracing/current_tracer"

(reproduced bug)

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

Revision history for this message
Nikolaus Rath (nikratio) wrote :
summary: - BUG: scheduling while atomic: python/3715/0x10000001
+ BUG: Scheduling while atomic in fuse_notify_inval_entry
Revision history for this message
Nikolaus Rath (nikratio) wrote :

The problem disappears when using the 2.6.37-020637rc2 mainline kernel.

Changed in linux:
status: Unknown → Confirmed
Changed in linux:
importance: Unknown → Medium
Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Confirmed
Changed in linux:
status: Confirmed → Fix Released
Revision history for this message
penalvch (penalvch) wrote :

Nikolaus Rath, thank you for reporting this and helping make Ubuntu better. Maverick reached EOL on April 10, 2012.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We were wondering if this is still an issue in a supported release? If so, could you please test for this 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 please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the kernel in the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested and remove the tag:
needs-upstream-testing

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 text:
needs-upstream-testing

If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested.

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested.

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested.

Please let us know your results. Thank you for your understanding.

Helpful Bug Reporting Tips:
https://help.ubuntu.com/community/ReportingBugs

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
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.