BUG: scheduling while atomic: bash/12031/0x10000001

[Lucian Adrian Grijincu]

I have nothing to add. I wasn't aware of the bug, but apport yelled at me that something went wrong.

ProblemType: KernelOops
DistroRelease: Ubuntu 10.10
Package: linux-image-2.6.35-16-generic 2.6.35-16.22
Regression: Yes
Reproducible: No
ProcVersionSignature: Ubuntu 2.6.35-16.22-generic 2.6.35.2
Uname: Linux 2.6.35-16-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
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: gringo-alpha 1476 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xefebc000 irq 45'
   Mixer name : 'SigmaTel STAC9200'
   Components : 'HDA:83847690,102801cc,00102201'
   Controls : 12
   Simple ctrls : 7
Date: Fri Aug 20 21:24:44 2010
Failure: oops
Frequency: I don't know.
HibernationDevice: RESUME=UUID=c351140f-10f1-42e4-ab70-0af1449e367e
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha i386 (20100803.1)
MachineType: Dell Inc. Latitude D820
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-16-generic root=UUID=16d46cf5-c652-42dc-bd06-541bad35c1d2 ro quiet splash
RelatedPackageVersions: linux-firmware 1.38
SourcePackage: linux
Title: BUG: scheduling while atomic: bash/12031/0x10000001
dmi.bios.date: 10/13/2006
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A04
dmi.board.name: 0GF470
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA04:bd10/13/2006:svnDellInc.:pnLatitudeD820:pvr:rvnDellInc.:rn0GF470:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Latitude D820
dmi.sys.vendor: Dell Inc.

[Lucian Adrian Grijincu (lucian.grijincu)]

The relevant stack trace (also in CurrentDmesg.txt http://launchpadlibrarian.net/54082134/CurrentDmesg.txt):

[ 515.665089] Pid: 1561, comm: dbus-daemon Not tainted 2.6.35-16-generic #22-Ubuntu
[ 515.665093] Call Trace:
[ 515.665103] [<c013e642>] __schedule_bug+0x62/0x70
[ 515.665110] [<c05c4340>] schedule+0x760/0x7a0
[ 515.665115] [<c05c44c2>] _cond_resched+0x32/0x50
[ 515.665120] [<c01fac3e>] anon_vma_prepare+0x1e/0x130
[ 515.665124] [<c01f62ad>] expand_downwards+0x1d/0x170
[ 515.665130] [<c01df709>] ? __alloc_pages_nodemask+0xd9/0x1c0
[ 515.665134] [<c01f640d>] expand_stack+0xd/0x10
[ 515.665139] [<c01f032b>] do_anonymous_page+0x2fb/0x310
[ 515.665143] [<c05c60fd>] ? _raw_spin_lock+0xd/0x10
[ 515.665147] [<c01f4170>] handle_mm_fault+0x340/0x400
[ 515.665150] [<c01f4339>] __get_user_pages+0x109/0x3f0
[ 515.665154] [<c01f46c5>] get_user_pages+0x55/0x70
[ 515.665159] [<c021d3d2>] get_arg_page+0x52/0xb0
[ 515.665165] [<c035996b>] ? strnlen_user+0x2b/0x60
[ 515.665169] [<c021d500>] copy_strings+0xd0/0x180
[ 515.665173] [<c021d5d9>] copy_strings_kernel+0x29/0x40
[ 515.665177] [<c021efba>] do_execve+0x19a/0x2c0
[ 515.665181] [<c05c6d37>] ? error_code+0x73/0x78
[ 515.665185] [<c0359a9a>] ? strncpy_from_user+0x3a/0x70
[ 515.665192] [<c0109d97>] sys_execve+0x37/0x70
[ 515.665196] [<c010316e>] ptregs_execve+0x12/0x18
[ 515.665200] [<c05c6634>] ? syscall_call+0x7/0xb

[Lucian Adrian Grijincu (lucian.grijincu)]

It seems 2.6.35-17.23 has been published.

I believe all the duplicates of this bug were running 2.6.35-16.22

You should upgrade the kernel and check whether this triggers there too.

[Lindinaldo (lindinaldo)]

Ok. Thank you.

Lindinaldo Marinho | João Pessoa | Paraíba | Brasil

2010/8/20 Lucian Adrian Grijincu <email address hidden>

> It seems 2.6.35-17.23 has been published.
>
> I believe all the duplicates of this bug were running 2.6.35-16.22
>
> You should upgrade the kernel and check whether this triggers there too.
>
> --
> BUG: scheduling while atomic: bash/12031/0x10000001
> https://bugs.launchpad.net/bugs/621371
> You received this bug notification because you are a direct subscriber
> of a duplicate bug (621358).
>

[Ritz (jonas-ritz)]

I can confirm this issue is solved with the new kernel

[Lindinaldo (lindinaldo)]

Yes, it's ok.

Lindinaldo Marinho | João Pessoa | Paraíba | Brasil

2010/8/21 Ritz <email address hidden>

> I can confirm this issue is solved with the new kernel
>
> ** Changed in: linux (Ubuntu)
> Status: Confirmed => Fix Released
>
> --
> BUG: scheduling while atomic: bash/12031/0x10000001
> https://bugs.launchpad.net/bugs/621371
> You received this bug notification because you are a direct subscriber
> of a duplicate bug (621358).
>

[dino99 (9d9)]

ive got this issue on my system too with 35-16-generic-pae kernel, but what its strange is that even booting on the next kernel 35-17 (which have not this issue) and having 35-16 still installed , produce this error. So ive uninstalled 35-16 from synaptic and now this error is gone.

when we search "scheduling" or "atomic" on launchpad bug , a bunch of report are daily reported and seem to be related to this new D+ service: bug report 617757 617988

[Lucian Adrian Grijincu (lucian.grijincu)]

I think you're mistaking.

This is an internal kernel issue and has nothing to do with DC++, or linuxdcpp.

[Florent Delayen (tnedel)]

I still have the message with the new kernel

[Vsevolod Velichko (torkvemada)]

Reproduced this bug on 2.6.35-17 i386 (linux-image-2.6.35-17-generic 2.6.35-17.23).
The humour of the "fix" is the following: -17 kernel doesn't catch any stack trace so I can't collect any debug info - there're no information in logs after reboot.

[Florent Delayen (tnedel)]

Now that's okay !

[Monfort Florian (florian-monfort)]

Thanks ;)

2010/9/2 Florent Delayen <email address hidden>

> Now that's okay !
>
> --
> BUG: scheduling while atomic: bash/12031/0x10000001
> https://bugs.launchpad.net/bugs/621371
> You received this bug notification because you are a direct subscriber
> of a duplicate bug (622124).
>
> Status in “linux” package in Ubuntu: Fix Released
>
> Bug description:
> I have nothing to add. I wasn't aware of the bug, but apport yelled at me
> that something went wrong.
>
> ProblemType: KernelOops
> DistroRelease: Ubuntu 10.10
> Package: linux-image-2.6.35-16-generic 2.6.35-16.22
> Regression: Yes
> Reproducible: No
> ProcVersionSignature: Ubuntu 2.6.35-16.22-generic 2.6.35.2
> Uname: Linux 2.6.35-16-generic i686
> AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
> 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: gringo-alpha 1476 F.... pulseaudio
> CRDA: Error: [Errno 2] No such file or directory
> Card0.Amixer.info:
> Card hw:0 'Intel'/'HDA Intel at 0xefebc000 irq 45'
> Mixer name : 'SigmaTel STAC9200'
> Components : 'HDA:83847690,102801cc,00102201'
> Controls : 12
> Simple ctrls : 7
> Date: Fri Aug 20 21:24:44 2010
> Failure: oops
> Frequency: I don't know.
> HibernationDevice: RESUME=UUID=c351140f-10f1-42e4-ab70-0af1449e367e
> InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha i386
> (20100803.1)
> MachineType: Dell Inc. Latitude D820
> ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-16-generic
> root=UUID=16d46cf5-c652-42dc-bd06-541bad35c1d2 ro quiet splash
> RelatedPackageVersions: linux-firmware 1.38
> SourcePackage: linux
> Title: BUG: scheduling while atomic: bash/12031/0x10000001
> dmi.bios.date: 10/13/2006
> dmi.bios.vendor: Dell Inc.
> dmi.bios.version: A04
> dmi.board.name: 0GF470
> dmi.board.vendor: Dell Inc.
> dmi.chassis.type: 8
> dmi.chassis.vendor: Dell Inc.
> dmi.modalias:
> dmi:bvnDellInc.:bvrA04:bd10/13/2006:svnDellInc.:pnLatitudeD820:pvr:rvnDellInc.:rn0GF470:rvr:cvnDellInc.:ct8:cvr:
> dmi.product.name: Latitude D820
> dmi.sys.vendor: Dell Inc.
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/621371/+subscribe
>

[Vsevolod Velichko (torkvemada)]

Unfortunately, I can't say the same :(
2.6.35-19.28 i386 generic kernel, all possible updates are installed — but system just went frozen at once and nothing could be found in logs.

[zertyz (zertyz)]

I believe this issue is not yet solved and I also believe that the bug #760082 is a duplicate of this, although there are more details: this only happens when we have a dual monitor with a second VGA display connected -- although, in my case, it is not always reproducible. If you are still affected by this bug, you may consider consulting the mentioned bug report.

[Monfort Florian (florian-monfort)]

On lun., 2011-04-18 at 17:18 +0000, zertyz wrote:
> I believe this issue is not yet solved and I also believe that the bug
> #760082 is a duplicate of this, although there are more details: this
> only happens when we have a dual monitor with a second VGA display
> connected -- although, in my case, it is not always reproducible. If you
> are still affected by this bug, you may consider consulting the
> mentioned bug report.
>

Except I've never had a second display connected ...

[Monfort Florian (florian-monfort)]

LinkedIn
------------

Bug,

I'd like to add you to my professional network on LinkedIn.

- Florian

Florian Monfort
Student at Saint Sébastien Landerneau Private School.
Brest Area, France

Confirm that you know Florian Monfort
https://www.linkedin.com/e/kk64co-go5y88na-5z/isd/3015125166/o4MJSQ-8/

--
(c) 2011, LinkedIn Corporation