Bug 42615
Summary: | BUG: scheduling while atomic: swapper | ||
---|---|---|---|
Product: | Process Management | Reporter: | Yves-Alexis Perez (corsac) |
Component: | Scheduler | Assignee: | Ingo Molnar (mingo) |
Status: | RESOLVED CODE_FIX | ||
Severity: | normal | CC: | jrnieder, kenyon |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | 3.2 | Subsystem: | |
Regression: | No | Bisected commit-id: |
Description
Yves-Alexis Perez
2012-01-20 16:07:55 UTC
Further debugging and test on bisected kernels can be found on https://bugs.launchpad.net/linux/+bug/917962 too. I've bisected a bit more and found the guilty commit: a2c76b83fdd763c826f38a55127ccf25708099ce is the first bad commit commit a2c76b83fdd763c826f38a55127ccf25708099ce Author: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com> 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 <dan.carpenter@oracle.com> Signed-off-by: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de> :040000 040000 08d80fa06121151b36ae17dc693c14d58c0d5db3 86b920618ceb575cebf610798c24a104dea36a2c M drivers I've confirmed that reverting this one on top of 3.2.1 removes the BUG(). (does someone reads this bugzilla?) (In reply to comment #2) > usb: renesas_usbhs: fixup inconsistent return from usbhs_pkt_push() [...] > I've confirmed that reverting this one on top of 3.2.1 removes the BUG(). > > (does someone reads this bugzilla?) No, nobody reads bugzilla. :) It's way better to contact subsystem mailing lists, cc-ing people in the sign-off chain and linux-kernel@vger for regressions. Could you attach your .config? I'm puzzled that the relevant code does not seem to have even been loaded when you got the BUG (renesas_usbhs did not appear in the module list), so I'm worried that the bisection result might not be reproducible. "scheduling while atomic" points to a driver bug. I hear that for historical reasons idle tasks are named 'swapper' and the name does not signify more than that. I can confirm that there have been several reports of 3.1 -> 3.2 regressions involving "scheduling while atomic", and the only relevant fix I know about is commit b3ef051db763 (USB: Realtek cr: fix autopm scheduling while atomic, 2012-01-26). See <http://bugs.debian.org/656724>, <http://bugs.debian.org/657526>, <http://bugs.debian.org/657612> for some examples. Yeah, in the end I tried to mail linux-kernel and in the end it was indeed the realtek issue, thanks for replying and sorry for not adding a comment here when I got the solution. |