From: Ross Zwisler <ross.zwisler@linux.intel.com>
To: lkp@lists.01.org
Subject: Re: [ppdev] e7223f1860: kernel BUG at drivers/base/driver.c:153!
Date: Thu, 03 Mar 2016 08:36:05 -0700 [thread overview]
Message-ID: <20160303153605.GA23797@linux.intel.com> (raw)
In-Reply-To: <20160303055133.GA4152@sudip-pc>
[-- Attachment #1: Type: text/plain, Size: 1257 bytes --]
On Thu, Mar 03, 2016 at 11:21:33AM +0530, Sudip Mukherjee wrote:
> On Wed, Mar 02, 2016 at 02:24:22PM -0700, Ross Zwisler wrote:
> > On Mon, Feb 15, 2016 at 4:50 AM, Sudip Mukherjee
> > <sudipm.mukherjee@gmail.com> wrote:
> > > On Mon, Feb 15, 2016 at 04:20:45PM +0800, kernel test robot wrote:
> > >> Greetings,
> > >>
> > >> 0day kernel testing robot got the below dmesg and the first bad commit is
> > >>
> > >> https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc.git char-misc-testing
> > >>
> > >> commit e7223f18603374d235d8bb0398532323e5f318b9
> > >> Author: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
> > >> AuthorDate: Fri Feb 12 18:33:45 2016 +0530
> > >> Commit: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> > >> CommitDate: Sun Feb 14 17:43:50 2016 -0800
> > >>
> <snip>
> >
> > I've been hitting this error on my KVM system as well, and bisected to
> > the same commit.
> >
> > The patch you have here solved the issue for me.
>
> I will submit the patch today. I am sorry for the delay, i got held up
> in some other things. Since you have tested this can I add your
> Tested-by: to the patch?
>
> regards
> sudip
Sure.
Tested-by: Ross Zwisler <ross.zwisler@linux.intel.com>
WARNING: multiple messages have this Message-ID (diff)
From: Ross Zwisler <ross.zwisler@linux.intel.com>
To: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Cc: Ross Zwisler <zwisler@gmail.com>,
Ross Zwisler <ross.zwisler@linux.intel.com>,
kernel test robot <fengguang.wu@intel.com>, LKP <lkp@01.org>,
LKML <linux-kernel@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
wfg@linux.intel.com
Subject: Re: [ppdev] e7223f1860: kernel BUG at drivers/base/driver.c:153!
Date: Thu, 3 Mar 2016 08:36:05 -0700 [thread overview]
Message-ID: <20160303153605.GA23797@linux.intel.com> (raw)
In-Reply-To: <20160303055133.GA4152@sudip-pc>
On Thu, Mar 03, 2016 at 11:21:33AM +0530, Sudip Mukherjee wrote:
> On Wed, Mar 02, 2016 at 02:24:22PM -0700, Ross Zwisler wrote:
> > On Mon, Feb 15, 2016 at 4:50 AM, Sudip Mukherjee
> > <sudipm.mukherjee@gmail.com> wrote:
> > > On Mon, Feb 15, 2016 at 04:20:45PM +0800, kernel test robot wrote:
> > >> Greetings,
> > >>
> > >> 0day kernel testing robot got the below dmesg and the first bad commit is
> > >>
> > >> https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc.git char-misc-testing
> > >>
> > >> commit e7223f18603374d235d8bb0398532323e5f318b9
> > >> Author: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
> > >> AuthorDate: Fri Feb 12 18:33:45 2016 +0530
> > >> Commit: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> > >> CommitDate: Sun Feb 14 17:43:50 2016 -0800
> > >>
> <snip>
> >
> > I've been hitting this error on my KVM system as well, and bisected to
> > the same commit.
> >
> > The patch you have here solved the issue for me.
>
> I will submit the patch today. I am sorry for the delay, i got held up
> in some other things. Since you have tested this can I add your
> Tested-by: to the patch?
>
> regards
> sudip
Sure.
Tested-by: Ross Zwisler <ross.zwisler@linux.intel.com>
next prev parent reply other threads:[~2016-03-03 15:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-15 8:20 [ppdev] e7223f1860: kernel BUG at drivers/base/driver.c:153! kernel test robot
2016-02-15 8:20 ` kernel test robot
2016-02-15 11:50 ` Sudip Mukherjee
2016-02-15 11:50 ` Sudip Mukherjee
2016-03-02 21:24 ` Ross Zwisler
2016-03-03 5:51 ` Sudip Mukherjee
2016-03-03 5:51 ` Sudip Mukherjee
2016-03-03 15:36 ` Ross Zwisler [this message]
2016-03-03 15:36 ` Ross Zwisler
2016-03-24 14:41 ` Petr Mladek
2016-03-24 14:41 ` Petr Mladek
2016-03-25 16:12 ` Linus Torvalds
2016-03-25 16:12 ` Linus Torvalds
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=20160303153605.GA23797@linux.intel.com \
--to=ross.zwisler@linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.