From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: "Huang, Ying" <ying.huang@intel.com>
Cc: Sudip Mukherjee <sudip@vectorindia.org>,
Mark Brown <broonie@kernel.org>,
lkp@01.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [LKP] [lkp] [spi] 2baed30cb3: BUG: scheduling while atomic: systemd-udevd/134/0x00000002
Date: Thu, 21 Jan 2016 11:36:52 +0530 [thread overview]
Message-ID: <20160121060652.GA5697@sudip-pc> (raw)
In-Reply-To: <87oacfqyap.fsf@yhuang-dev.intel.com>
On Thu, Jan 21, 2016 at 01:47:10PM +0800, Huang, Ying wrote:
> Sudip Mukherjee <sudipm.mukherjee@gmail.com> writes:
>
> > On Wed, Jan 20, 2016 at 01:00:40PM +0800, Huang, Ying wrote:
> >> Sudip Mukherjee <sudipm.mukherjee@gmail.com> writes:
> >>
> >> > On Wed, Jan 20, 2016 at 08:44:37AM +0800, kernel test robot wrote:
<snip>
> >
> > I am not able to reproduce this. Tested just with the kernel and
> > yocto-minimal-i386.cgz filesystem and it booted properly.
> >
> > I guess I need atleast your job file to reproduce this.
>
> This is a boot test so I did not attached the job file. But the test
> result may depends on specific root file system. For example, the
> process when BUG report is always systemd-udevd. Maybe you need a
> systemd based root file system.
So silly of me. Since you said 2baed30cb3, so i kept looking at that
patch.
Can you please test again after reverting:
ebd43516d387 ("Staging: panel: usleep_range is preferred over udelay")
If it solves the problem then I will submit a formal patch.
regards
sudip
next prev parent reply other threads:[~2016-01-21 6:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-20 0:44 [lkp] [spi] 2baed30cb3: BUG: scheduling while atomic: systemd-udevd/134/0x00000002 kernel test robot
2016-01-20 4:42 ` Sudip Mukherjee
2016-01-20 5:00 ` [LKP] " Huang, Ying
2016-01-21 5:33 ` Sudip Mukherjee
2016-01-21 5:47 ` Huang, Ying
2016-01-21 6:06 ` Sudip Mukherjee [this message]
2016-01-23 6:39 ` Sudip Mukherjee
2016-01-25 2:15 ` Huang, Ying
2016-01-25 4:40 ` Sudip Mukherjee
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=20160121060652.GA5697@sudip-pc \
--to=sudipm.mukherjee@gmail.com \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=sudip@vectorindia.org \
--cc=ying.huang@intel.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;
as well as URLs for NNTP newsgroup(s).