From: Borislav Petkov <bp@alien8.de>
To: Alessandro Rubini <rubini@gnudd.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: fmc: BUG: scheduling while atomic: swapper/0/1/0x00000002
Date: Mon, 14 Oct 2013 17:23:39 +0200 [thread overview]
Message-ID: <20131014152339.GI4009@pd.tnic> (raw)
In-Reply-To: <20131014151017.GA13363@mail.gnudd.com>
On Mon, Oct 14, 2013 at 05:10:17PM +0200, Alessandro Rubini wrote:
> Hello.
>
> > I'm getting the following with randconfig testing in kvm, config is
> > .attached.
>
> I acknowledge this is a bug of mine, and your .config shows your are
> testing v3.11.
>
> I posted the fix on Jul 16th 2013, and it is now in master as
> v3.11-rc2-11-g783c2fb. However it is not an ancestor of v3.11, which
> still has the bug. "git tag --contains 783c2fb" reports v3.12-rc1 as
> the first "official" kernel with the fix,
Right, I found that bug report from July but didn't find the fix to it.
Thanks for letting me know.
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
prev parent reply other threads:[~2013-10-14 15:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-14 12:34 fmc: BUG: scheduling while atomic: swapper/0/1/0x00000002 Borislav Petkov
2013-10-14 15:10 ` Alessandro Rubini
2013-10-14 15:23 ` Borislav Petkov [this message]
Reply instructions:
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20131014152339.GI4009@pd.tnic \
--to=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rubini@gnudd.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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