BUG: scheduling while atomic: swapper

Possible dupes are bugs 917977, 917975, and 917971, when someone gets around to tracing this.

Other possible duplicates:
bug 918221
bug 918221

Meant to post:
bug 918111

Do you know which kernel version introduced this bug?

Would it be possible for you to test the latest upstream kernel?

Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . If possible, please test the latest v3.2 kernel[1] (Not a kernel in the daily directory). Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag(Only that one tag, please leave the other tags). 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.

[1] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.2-precise/

I'd like to perform a bisect to figure out what commit caused this regression. It would be very helpful to know the earliest kernel where the issue started happening as well as the latest kernel that did not have this issue.

In addition to the latest mainline kernel, would it be possible for you to test the v3.1.0-2.3 kernel? It is available at:
https://launchpad.net/ubuntu/precise/i386/linux-image-3.1.0-2-generic/3.1.0-2.3

Ok, I just tried the 3.2.1-030201-generic #201201121644 SMP Thu Jan 12 21:45:24 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux and the same constant crashes. This doesn't seem to occur in 11.10. I'll test the other kernels as well. Thanks.

Same results. 3.2.0-030200-generic #201201042035 SMP Thu Jan 5 01:36:31 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

Same. Linux james-Inspiron-1121 3.1.0-2-generic #3-Ubuntu SMP Sat Oct 29 00:48:30 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux

To bisect and identify which commit introduced this regression, we need to figure out which kernel first started having this issue.

I'd like to have you test the earliest 3.1 mainline kernel, which is:

v3.1-rc2
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.1-rc2-oneiric/

I'd also like to have you test the latest 3.0 mainline kernel, which is:
v3.0.17
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.0.17-oneiric/

It would be great if you could test those two kernels and report back.

Thanks for all you help testing!

Ok, this kernel, 3.1.0-0301rc2-generic, seems good so far.

Linux james-Inspiron-1121 3.0.17-030017-generic #201201121555 SMP Thu Jan 12 20:56:58 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
is fine too.

Hi James,

Thanks for taking the time to test. So far it appears the regression was introduced in one of the v3.1 release candidates. You confirmed that rc2 does not have the bug, and the final version of v3.1 does have the bug.

Would it be possible for you to test some of the v3.1 release candidates(rc3 -> rc10) on the following page:
http://kernel.ubuntu.com/~kernel-ppa/mainline/

It may be quicker to skip release candidates to find the bad version faster. For example, we know that rc2 is good, so maybe test rc4. If it is good test rc6. Once you find an rc that is bad, you can then test the prior rc.

If we can identify which rc introduced the regression, I can bisect that version and identify the exact commit.

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

Hey,

I have the same issue even with vanilla kernel. I tried to run a bisect log which I'm not exactly sure of:

git bisect start
# bad: [b8ed9e5b8c34dc9fb1882669e45b21e3d0194881] Linux 3.2.1
git bisect bad b8ed9e5b8c34dc9fb1882669e45b21e3d0194881
# good: [c3b92c8787367a8bb53d57d9789b558f1295cc96] Linux 3.1
git bisect good c3b92c8787367a8bb53d57d9789b558f1295cc96
# bad: [68d99b2c8efcb6ed3807a55569300c53b5f88be5] Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound
git bisect bad 68d99b2c8efcb6ed3807a55569300c53b5f88be5
# bad: [efb8d21b2c6db3497655cc6a033ae8a9883e4063] Merge branch 'tty-next' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty
git bisect bad efb8d21b2c6db3497655cc6a033ae8a9883e4063
# good: [094daf7db7c47861009899ce23f9177d761e20b0] Merge branch 'master' of git://git.infradead.org/users/linville/wireless-next into for-davem
git bisect good 094daf7db7c47861009899ce23f9177d761e20b0
# good: [1be025d3cb40cd295123af2c394f7229ef9b30ca] Merge branch 'usb-next' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb
git bisect good 1be025d3cb40cd295123af2c394f7229ef9b30ca
# good: [4e7e2a2008f5d8c49791c412849d5b0232d39bb3] Merge branch 'for-linus' of git://opensource.wolfsonmicro.com/regmap
git bisect good 4e7e2a2008f5d8c49791c412849d5b0232d39bb3
# good: [1442d1678ca7e53574fd403ba7bee6f4125d920c] Merge branch 'for-3.2' of git://linux-nfs.org/~bfields/linux
git bisect good 1442d1678ca7e53574fd403ba7bee6f4125d920c
# good: [3cb603284b3d256ae9ae9e65887cee8416bfef15] Merge branch 'hwmon-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging
git bisect good 3cb603284b3d256ae9ae9e65887cee8416bfef15
# good: [51808f051ede81865b7af351d6c230a1ac244a22] max3110: add sysrq support
git bisect good 51808f051ede81865b7af351d6c230a1ac244a22
# good: [f37ac5a144027cddfcf1dfab30eb7c2ba765f5ca] tty/n_gsm: fix a bug in gsm_dlci_data_output (adaption = 2 case)
git bisect good f37ac5a144027cddfcf1dfab30eb7c2ba765f5ca
# good: [1177c0efc04d032644895b8d757f55b433912596] TTY: pty, release tty in all ptmx_open fail paths
git bisect good 1177c0efc04d032644895b8d757f55b433912596
# good: [4cbf9f4864bd4fb2e64d555aacb93c24478e4e8d] tty/serial: atmel_serial: auto-enumerate ports
git bisect good 4cbf9f4864bd4fb2e64d555aacb93c24478e4e8d
# good: [a0340703981baa6cc1e9c7c768095a0a4e718daf] Revert "TTY: call tty_driver_lookup_tty unconditionally"
git bisect good a0340703981baa6cc1e9c7c768095a0a4e718daf
# good: [d208a3bf77f902283894f546b6b5383202cf7882] TTY: serial_core: Fix crash if DCD drop during suspend
git bisect good d208a3bf77f902283894f546b6b5383202cf7882

then it said that efb8d21b2c6db3497655cc6a033ae8a9883e4063 was the first bad commit (which puzzles me a little since it's a merge commit but looks pretty much unrelated.

Thanks for all the work bisecting, Yves-Alexis!

So it looks like the following commit caused the regression:

efb8d21b2c6db3497655cc6a033ae8a9883e4063 Merge branch 'tty-next' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty

I can build a test kernel with commits up to:
3cb603284b3d256ae9ae9e65887cee8416bfef15 Merge branch 'hwmon-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging

That was the commit just before efb8d21b2c6db3497655cc6a033ae8a9883e4063

I'll post the location of the test kernel shortly. It would be great if folks affected by this bug can test the kernel and provide feed back.

There are some test kernels available at:
http://people.canonical.com/~jsalisbury/lp917962/

Can folks affected by this bug test these kernels, and report back?

I am experiencing the same crashes.

Linux james-Inspiron-1121 3.1.0-030100-generic #201201201806 SMP Fri Jan 20 18:08:42 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

Thanks for the update, James. That test kernel was up to commit:
3cb603284b3d256ae9ae9e65887cee8416bfef15

I'll build a test kernel up to the last reported good kernel in Yves-Alexis' bisect:
094daf7db7c47861009899ce23f9177d761e20b0

If that kernel does not have the issue, I'll bisect further between these two commits.

There are some more new test kernels available at:
http://people.canonical.com/~jsalisbury/lp917962/

These kernels are built up until commit:
094daf7db7c47861009899ce23f9177d761e20b0

Can folks affected by this bug test these kernels, and report back?

So far, so good. No crashes.

Linux james-Inspiron-1121 3.1.0-030100rc9-generic #201201202123 SMP Fri Jan 20 21:25:10 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

Yes, all is good on this kernel.

I have a new test kernel building now. It will be built up to commit:
1be025d3cb40cd295123af2c394f7229ef9b30ca

There are some more new test kernels available at:
http://people.canonical.com/~jsalisbury/lp917962/

These kernels are built up until commit:
1be025d3cb40cd295123af2c394f7229ef9b30ca

Can you test this kernel to see if the bug still exists?

I've further debugged inside the merged branch, and got:

corsac@scapa: git bisect log
# bad: [a2c76b83fdd763c826f38a55127ccf25708099ce] usb: renesas_usbhs: fixup inconsistent return from usbhs_pkt_push()
# good: [2d03423b2319cc854adeb28a03f65de5b5e0ab63] Merge branch 'driver-core-next' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core
git bisect start 'a2c76b8' '2d03423'
# good: [c6a389f123b9f68d605bb7e0f9b32ec1e3e14132] Linux 3.1-rc4
git bisect good c6a389f123b9f68d605bb7e0f9b32ec1e3e14132
# good: [a8b43c00ef06aec49b9fe0a5bad8a6a320e4d27b] USB: Fix runtime wakeup on OHCI
git bisect good a8b43c00ef06aec49b9fe0a5bad8a6a320e4d27b
# good: [1d749f9afa657f6ee9336b2bc1fcd750a647d157] USB: ftdi_sio.c: Use ftdi async_icount structure for TIOCMIWAIT, as in other drivers
git bisect good 1d749f9afa657f6ee9336b2bc1fcd750a647d157
# good: [55b5a624a0cc5aa4b350fd50d78cf3415f795bfe] usb: renesas_usbhs: tidyup for smatch warnings
git bisect good 55b5a624a0cc5aa4b350fd50d78cf3415f795bfe
# good: [0889551267e7b6b4d27dc9f726f3d0cb0d976105] USB: gadget: midi: fix range check in f_midi_out_open()
git bisect good 0889551267e7b6b4d27dc9f726f3d0cb0d976105
# good: [3a7655fcb210b349111251689d0a56b7250885ea] usb/isp1760: Allow to optionally trigger low-level chip reset via GPIOLIB.
git bisect good 3a7655fcb210b349111251689d0a56b7250885ea

with:

a2c76b83fdd763c826f38a55127ccf25708099ce is the first bad commit
commit a2c76b83fdd763c826f38a55127ccf25708099ce
Author: Kuninori Morimoto <email address hidden>
Date: Tue Oct 18 20:05:50 2011 -0700

    usb: renesas_usbhs: fixup inconsistent return from usbhs_pkt_push()

    usbhs_pkt_push() had inconsistent return under spin lock.
    This patch fix it up.
    Special thanks to Dan

    Cc: Dan Carpenter <email address hidden>
    Signed-off-by: Kuninori Morimoto <email address hidden>
    Signed-off-by: Greg Kroah-Hartman <email address hidden>

:040000 040000 08d80fa06121151b36ae17dc693c14d58c0d5db3 86b920618ceb575cebf610798c24a104dea36a2c M drivers

So I'll try to rebuild a 3.2.1 with this commit reverted and report back.

Yup, seems to work fine.

Thanks for identifying that commit, Yves-Alexis!

I'll build a test kernel with that commit reverted. I'll post a link to that new kernel for other folks to test.

There is a new test kernel available at:
http://people.canonical.com/~jsalisbury/lp917962/

This kernel was built with the following commit reverted:
a2c76b83fdd763c826f38a55127ccf25708099ce

If you are affected by this bug, please test this kernel and report back if it resolves your issue.

Thanks in advance.

Ok, I may have done something wrong during bisecting, because the relevant bad commit touches something not for x86. Unfortunately, redoing the whole bisect is a bit too long, especially since I need to keep the full debian .config now, since I don't exactly know from where this happens.

Th new kernel did not correct the problem here (tested on a CR-48).

Still having prob [touchsmart tx2]

Sorry at time of posting [#31] I had not yet tried kernel in post [#27]. Now tried it and cannot say if it fixes it or not - simply because it won't boot anymore with that kernel installed (last thing that appears on screen are some apparmor messages, but they don't look like errors)

Should be fixed in 3.3 with http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commit;h=b3ef051db763b640d1ff724b616ffba940896b44 (note the tag for -stable).

Thanks for posting the link to the upstream fix, Julian.

It looks like the patch has been added to Linus' tree:
b3ef051db763b640d1ff724b616ffba940896b44 USB: Realtek cr: fix autopm scheduling while atomic

If you are affected by this but, can you test the latest mainline kernel, which is available at:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.3-rc1-precise/

Details on how to test the mainline kernel can be found at:
https://wiki.ubuntu.com/KernelMainlineBuilds

@Julian,

When you refer to the -stable tag, are you referring to:
Cc: <email address hidden> # 3.2+

Have you seen any activity upstream to indicate this patch will make it into the 3.2 stable release?

It's in Greg's queue for the next 3.2-stable release, so yes.

Note that the patch didn't land in time for 3.3-rc1, so when testing the mainline builds please pick -rc2 (the packages are not available yet, it was tagged just an hour ago).

Hi Julian,

Just curious how you can tell this is in Greg's queue for the next 3.2-stable release, for future reference. Is it reported in some LKML threads, or maybe on the stable mailing list?

There should be an automatic mail to the stable-commits list, but imo it's easier to check the corresponding tree at kernel.org [0].

[0] git://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git

Thanks, Julian!

This Bug affects me too on a Dell Inspiron 1012 Mini NetBook Computer. As far as I know, the hardware on the Netbook is everything Intel Integrated Hardware: EM64T Intel Atom N450 Processor and Chipset (Not Sure Which One However), Intel Inegrated Video Card (Not Sure Which One However), Intel Integrated Sound Card (Again Not Sure Which One). Affected Software: 64 Bit Ubuntu 12.04 Nightly Builds including Yesterdays Nightly Build with Today's Updates and NO Artificial Kernel Modifications.

By the way: for me this bug started occuring when the KernelOpps file was updated to the latest version. It was NOT a Kernel Update that started the problem for me but a Kernel Opps File Update that started the problem for me. Hope this helps.

I've cherry-pick the patch noted in comment #33 and applied it to the Precise Ubuntu kernel git repo. The fix should be available in the next kernel upload. Thanks.

This bug was fixed in the package linux - 3.2.0-13.22

---------------
linux (3.2.0-13.22) precise; urgency=low

  [ Alex Deucher ]

  * (pre-stable): drm/radeon/kms: move panel mode setup into encoder mode
    set
    - LP: #925538
  * (pre-stable): drm/radeon/kms: rework modeset sequence for DCE41 and
    DCE5
    - LP: #925538

  [ Andy Whitcroft ]

  * [Config] review IPv6 configuration options and enable

  [ David Henningsson ]

  * SAUCE: ALSA: HDA: Remove quirk for Toshiba Qosmio G50
    - LP: #923316
  * SAUCE: ALSA: HDA: Fix jack creation for codecs with front and rear Line
    In
    - LP: #923409

  [ James M. Leddy ]

  * SAUCE: Bluetooth: Add support for BCM20702A0 [0a5c:21e6]
    - LP: #906832

  [ Manoj Iyer ]

  * SAUCE: Bluetooth: Add support for BCM20702A0 [0a5c:21e1]
    - LP: #906832
  * SAUCE: Add vendor specific ID (0a5c 21f3) for BCM20702A0.
    - LP: #925552

  [ Seth Forshee ]

  * (pre-stable): drm/radeon/kms: disable output polling when suspended
    - LP: #925570

  [ Tim Gardner ]

  * [Config] CONFIG_BLK_DEV_PCIESSD_MTIP32XX=m
    - LP: #922221
  * [Config] Add mtip32xx to d-i block modules
    - LP: #922221
  * [Config] Enable USB3.0 in d-i

  [ Upstream Kernel Changes ]

  * block: Add driver for Micron RealSSD pcie flash cards
    - LP: #922221
  * mtip32xx: fix warnings/errors on 32-bit compiles
    - LP: #922221
  * mtip32xx: cleanup compat ioctl handling
    - LP: #922221
  * mtip32xx: ensure that all local functions are static
    - LP: #922221
  * mtip32xx: mark a few more items static
    - LP: #922221
  * mtip32xx: add module.h include to avoid conflict with moduleh tree
    - LP: #922221
  * mtip32xx: update to new ->make_request() API
    - LP: #922221
  * mtip32xx: updates based on feedback
    - LP: #922221
  * mtip32xx: uninitialized variable in mtip_quiesce_io()
    - LP: #922221
  * mtip32xx: do rebuild monitoring asynchronously
    - LP: #922221
  * watchdog: iTCO_wdt: add Intel Lynx Point DeviceIDs
    - LP: #900119
  * drm/i915: mask transcoder select bits before setting them on LVDS
    - LP: #924989
  * (pre-stable) USB: Realtek cr: fix autopm scheduling while atomic
    - LP: #917962
  * nouveau: properly check for _DSM function support
    - LP: #925608
  * nouveau: Support Optimus models for vga_switcheroo
    - LP: #925608
 -- Leann Ogasawara <email address hidden> Thu, 02 Feb 2012 13:26:59 -0800