From: Kuninori Morimoto <firstname.lastname@example.org>
Cc: Yves-Alexis Perez <email@example.com>, Greg KH <firstname.lastname@example.org>,
Subject: Re: [3.2+] BUG: scheduling while atomic: swapper/0/0/0x10000100
Date: Thu, 26 Jan 2012 16:27:39 -0800 (PST) [thread overview]
Message-ID: <email@example.com> (raw)
> > > Specially when you consider the fact that
> > > it's very recently that we dropped the ARCH dependency with commit
> > > d242c110c43b55aaf3ebb3ceac1eeab0d452a177
> > >
> > > > Kuninori, any thoughts about this? Should I revert this from the
> > > > tree?
> > >
> > > I don't think so, I think this was a bad bisection.
> > >
> > Maybe (especially since the first bad commit is a merge commit, so I'm
> > not completely sure I did correctly the second bisect). But I'm puzzled
> > why reverting the commit on top of 3.2.1 fixes that. And now that Felipe
> > mentions it, USB Gadget is not even compiled, so I'm completely lost.
> Hehehe :-) That's fun... Maybe it's some other instability and it just
> didn't kick when you reverted that commit. It could be that the problem
> is somewhere completely different and you just didn't fully debug it yet
I was very much surprised at this issue.
As Felipe explained, renesas_usbhs was for SuperH system.
x86 can not use it,
but, if your PC has "renesas_usbhs.ko" as kernel module,
and loaded it somehow...
next prev parent reply other threads:[~2012-01-27 0:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-26 14:22 [3.2+] BUG: scheduling while atomic: swapper/0/0/0x10000100 Yves-Alexis Perez
2012-01-26 16:15 ` Greg KH
2012-01-26 16:20 ` Yves-Alexis Perez
2012-01-26 16:31 ` Felipe Balbi
2012-01-26 16:36 ` Yves-Alexis Perez
2012-01-26 16:45 ` Felipe Balbi
2012-01-27 0:27 ` Kuninori Morimoto [this message]
2012-01-27 6:36 ` Yves-Alexis Perez
2012-01-30 8:51 ` Yves-Alexis Perez
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).