From: Fengguang Wu <fengguang.wu@intel.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: LKP <lkp@01.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [Revert "ppdev] 1701f68040: genirq: Flags mismatch irq 4. 00000000 (serial) vs. 00000080 (goldfish_pdev_bus)
Date: Mon, 30 May 2016 03:23:29 +0800 [thread overview]
Message-ID: <20160529192329.GA29119@wfg-t540p.sh.intel.com> (raw)
In-Reply-To: <CA+55aFyvxUJV+uSKVbfhf_BFmDoBwth=HXqC+oZ-V0j7A2xACA@mail.gmail.com>
On Sun, May 29, 2016 at 09:25:28AM -0700, Linus Torvalds wrote:
> On Sun, May 29, 2016 at 8:28 AM, kernel test robot
> <fengguang.wu@intel.com> wrote:
> >
> > 0day kernel testing robot got the below dmesg and the first bad commit is
>
> This bisection seems unlikely.
>
> I *think* what is going on is that the previous kernels ended up with
> boot failures:
>
> > +------------------------------------------------------------+------------+------------+-------------+
> > | | 3b3b3bd977 | 1701f68040 | v4.6_052910 |
> > +------------------------------------------------------------+------------+------------+-------------+
> > | kernel_BUG_at_drivers/base/driver.c | 92 | | |
>
> and then when that went away (thanks to the commit you bisected to),
> the "genirq: Flags mismatch" warning showed up because it now got past
> that original bug.
That's right. It's a bug fix that discloses a less serious warning.
> I'm not sure what the fix to the 0day bisection should be. Maybe add
> some test that the last "good" kernel actually booted?
Yes, we do have tests on whether the parent boots fine or has more
serious boot errors, however they are wrongly bypassed when we
recently try to add a new test to report out errors which look
relevant to the code change.
I'll fix it up, sorry for the noise!
Boot tests are pretty noisy and often a commit and its parent commit
both have error/warnings. A better long term solution would be to
compare their time stamps to get the clue whether it's a bug fix that
makes the kernel live longer to produce another warning.
Thanks,
Fengguang
next prev parent reply other threads:[~2016-05-29 19:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-29 15:28 kernel test robot
2016-05-29 16:25 ` Linus Torvalds
2016-05-29 19:23 ` Fengguang Wu [this message]
2016-05-31 10:11 ` Alan
2016-05-31 10:51 ` Fengguang Wu
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=20160529192329.GA29119@wfg-t540p.sh.intel.com \
--to=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=torvalds@linux-foundation.org \
/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
all inboxes | Powered by JetHome®