linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: kernel test robot <lkp@intel.com>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	LKML <linux-kernel@vger.kernel.org>,
	"open list:SERIAL DRIVERS" <linux-serial@vger.kernel.org>,
	lkp@lists.01.org
Subject: Re: [serial] 679193b7ba: BUG:spinlock_bad_magic_on_CPU
Date: Sun, 2 Aug 2020 12:58:08 +0200	[thread overview]
Message-ID: <20200802105808.GA164531@kroah.com> (raw)
In-Reply-To: <CAHp75Vcdwz2RynZ0KVCDMFyO_GPREgGdCNVNGqosjf6iV0_uog@mail.gmail.com>

On Sun, Aug 02, 2020 at 01:50:29PM +0300, Andy Shevchenko wrote:
> On Sun, Aug 2, 2020 at 8:54 AM kernel test robot <lkp@intel.com> wrote:
> >
> > Greeting,
> >
> > FYI, we noticed the following commit (built with gcc-9):
> >
> > commit: 679193b7baf8d88e41cbeb397ca17f797654947d ("serial: 8250: Let serial core initialise spin lock")
> > https://git.kernel.org/cgit/linux/kernel/git/gregkh/tty.git tty-next
> >
> >
> > in testcase: boot
> >
> > on test machine: qemu-system-x86_64 -enable-kvm -cpu SandyBridge -smp 2 -m 16G
> >
> > caused below changes (please refer to attached dmesg/kmsg for entire log/backtrace):
> >
> >
> > +-------------------------------+------------+------------+
> > |                               | f3af1b68fc | 679193b7ba |
> > +-------------------------------+------------+------------+
> > | boot_successes                | 4          | 0          |
> > | boot_failures                 | 0          | 4          |
> > | BUG:spinlock_bad_magic_on_CPU | 0          | 4          |
> > +-------------------------------+------------+------------+
> >
> >
> > If you fix the issue, kindly add following tag
> > Reported-by: kernel test robot <lkp@intel.com>
> 
> Thanks for the report. I didn't see it on real hardware though. Maybe
> because of timing (race?) differences.
> 
> Greg, I think the best is to revert the change until I will have better one.

Can you send me a revert patch with the reported-by: set up?

thanks,

greg k-h

  reply	other threads:[~2020-08-02 10:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-02  5:48 [serial] 679193b7ba: BUG:spinlock_bad_magic_on_CPU kernel test robot
2020-08-02 10:50 ` Andy Shevchenko
2020-08-02 10:58   ` Greg Kroah-Hartman [this message]
2020-08-02 11:16     ` Andy Shevchenko

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=20200802105808.GA164531@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=lkp@lists.01.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;
as well as URLs for NNTP newsgroup(s).