BUG: scheduling while atomic: mmcqd/46/0x00000002

[Tobin Davis]

apport auto-generated bug report on omap4.

This oops message is reproducible on my system, by simply rebooting this image (20100713).

ProblemType: KernelOops
DistroRelease: Ubuntu 10.10
Package: linux-image-2.6.34-901-omap4 2.6.34-901.4
Uname: Linux 2.6.34-901-omap4 armv7l
Annotation: Your system might become unstable now and might need to be restarted.
Architecture: armel
Date: Tue Jul 13 15:51:49 2010
Failure: oops
SourcePackage: linux-ti-omap4
Title: BUG: scheduling while atomic: mmcqd/46/0x00000002

[Lee Jones (lag)]

Tobin,

I'm not seeing this. Can you confirm that this is still an issue?

[Lee Jones (lag)]

Apparently this bug only appears when swap is active.

I'll create a swap file and see what we find.

[Lee Jones (lag)]

For the life of me, I can not seem to replicate this bug.

As the USB is broken on my board, I can fire-up a desktop system to test.

I will endeavour to test more vigorously when the replacement gets here next week.

[Lee Jones (lag)]

s/can/can't

[Ricardo Salveti (rsalveti)]

Tobin, can you check if this is still happening with latest kernel (903)?

[Tobin Davis (gruemaster)]

Have not seen this, but testing recently has been a real pain. Also, swap is turned off on the images currently.

[Tobin Davis (gruemaster)]

Meant to say that I have not seen this in 903 kernel.

[Leann Ogasawara (leannogasawara)]

Per the following quick chat on IRC in #ubuntu-kernel with Oliver and Tobin, we're going to close this bug for now. If it re-appears we'll reopen this. Thanks.

[07:47:42] <GrueMaster> I'm pulling today's images. If I can get them to work somewhat, I will reenable swap and test this.
[07:47:46] <ogasawara> ogra: so would you consider if ok to close the bug for now? or would you rather we leave it open into better testing can be done.
[07:48:08] <ogra> close it and lets see if it comes up again ... we can always re-open
[07:48:17] <ogasawara> ogra: ack, thanks
[07:48:35] <ogasawara> GrueMaster: if it re-appears after your testing, re-open the bug.