public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Fengguang Wu <fengguang.wu@intel.com>
To: Alessandro Rubini <rubini@gnudd.com>
Cc: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org
Subject: Re: [FMC] BUG: scheduling while atomic: swapper/1/0x10000002
Date: Wed, 3 Jul 2013 15:36:58 +0800	[thread overview]
Message-ID: <20130703073658.GA27303@localhost> (raw)
In-Reply-To: <20130703073249.GA27110@mail.gnudd.com>

Hi Alessandro,

On Wed, Jul 03, 2013 at 09:32:49AM +0200, Alessandro Rubini wrote:
> Hello.
> 
> > I got the below dmesg and the first bad commit is
> > 
> > commit 4debfe409b6e550032bfef9733e9f6f7c5613617
> > Author: Alessandro Rubini <rubini@gnudd.com>
> > Date:   Tue Jun 18 23:48:07 2013 +0200
> > 
> >     FMC: add a char-device mezzanine driver
> 
> thank you for your report. I already got a problem report with
> built-in FMC subsystem, but I couldn't reproduce it.  Actually, I use
> drivers/fmc daily (I'm currently finalizing an ADC driver), but I run
> the whole subsystem as module; it never happens in that case.
> 
> Thank you for bisecting, I'll take a deeper look as soon as possible
> (hopefully today).  Meanwhile, please disable FMC or build as modules.

No problem for me. I actually run the tests in KVM which does not have
real FMC hardware at all.

Thanks,
Fengguang

  reply	other threads:[~2013-07-03  7:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-03  7:15 [FMC] BUG: scheduling while atomic: swapper/1/0x10000002 Fengguang Wu
2013-07-03  7:32 ` Alessandro Rubini
2013-07-03  7:36   ` Fengguang Wu [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-04-09  3:32 Jet Chen
2014-04-09  5:08 ` Alessandro Rubini
2014-04-09  5:26   ` Jet Chen
2014-04-09  5:28   ` Fengguang Wu
2014-04-09 16:44     ` Jet Chen
2014-04-09 16:46   ` Jet Chen

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=20130703073658.GA27303@localhost \
    --to=fengguang.wu@intel.com \
    --cc=gregkh@linuxfoundation.org \
    --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