From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: lkp@lists.01.org
Subject: Re: [staging] 68905a14e49: kernel BUG at drivers/base/driver.c:153!
Date: Fri, 07 Aug 2015 11:01:13 -0700 [thread overview]
Message-ID: <20150807180113.GC10282@kroah.com> (raw)
In-Reply-To: <20150807071553.GA28337@sudip-pc>
[-- Attachment #1: Type: text/plain, Size: 1256 bytes --]
On Fri, Aug 07, 2015 at 12:45:53PM +0530, Sudip Mukherjee wrote:
> On Thu, Aug 06, 2015 at 07:28:12PM -0700, Greg Kroah-Hartman wrote:
> >
> >
> > On Sat, Aug 01, 2015 at 01:12:05PM +0800, kernel test robot wrote:
> <snip>
> > > [ 12.276231] RIP
> > > [ 12.276231] RIP [<ffffffff81b68e78>] driver_register+0xa8/0xe0
> > > [<ffffffff81b68e78>] driver_register+0xa8/0xe0
> > > [ 12.276231] RSP <ffff8800001a3e30>
> > > [ 12.276231] RSP <ffff8800001a3e30>
> > > [ 12.403330] ---[ end trace 075c805d53b02836 ]---
> > > [ 12.403330] ---[ end trace 075c805d53b02836 ]---
> >
> > David, any ideas of what needs to be done to fix this?
>
> Hi Greg,
> I was having a quick look and it looks like visorchipset is not yet
> initialised and the bus is not yet registered. If you remember we had a
> loooong discussion in another thread "usb: ulpi: don't register drivers
> if bus doesn't exist", I sent a proposed patch also. For your reference:
> "http://www.spinics.net/lists/linux-usb/msg125368.html".
> I think this one is the perfect example of that case here.
Great, then it needs to be fixed in the unisys driver code, like I said
should be done for busses to prevent this type of issue :)
thanks,
greg k-h
WARNING: multiple messages have this Message-ID (diff)
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Cc: kernel test robot <ying.huang@intel.com>,
David Kershner <david.kershner@unisys.com>,
lkp@01.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [lkp] [staging] 68905a14e49: kernel BUG at drivers/base/driver.c:153!
Date: Fri, 7 Aug 2015 11:01:13 -0700 [thread overview]
Message-ID: <20150807180113.GC10282@kroah.com> (raw)
In-Reply-To: <20150807071553.GA28337@sudip-pc>
On Fri, Aug 07, 2015 at 12:45:53PM +0530, Sudip Mukherjee wrote:
> On Thu, Aug 06, 2015 at 07:28:12PM -0700, Greg Kroah-Hartman wrote:
> >
> >
> > On Sat, Aug 01, 2015 at 01:12:05PM +0800, kernel test robot wrote:
> <snip>
> > > [ 12.276231] RIP
> > > [ 12.276231] RIP [<ffffffff81b68e78>] driver_register+0xa8/0xe0
> > > [<ffffffff81b68e78>] driver_register+0xa8/0xe0
> > > [ 12.276231] RSP <ffff8800001a3e30>
> > > [ 12.276231] RSP <ffff8800001a3e30>
> > > [ 12.403330] ---[ end trace 075c805d53b02836 ]---
> > > [ 12.403330] ---[ end trace 075c805d53b02836 ]---
> >
> > David, any ideas of what needs to be done to fix this?
>
> Hi Greg,
> I was having a quick look and it looks like visorchipset is not yet
> initialised and the bus is not yet registered. If you remember we had a
> loooong discussion in another thread "usb: ulpi: don't register drivers
> if bus doesn't exist", I sent a proposed patch also. For your reference:
> "http://www.spinics.net/lists/linux-usb/msg125368.html".
> I think this one is the perfect example of that case here.
Great, then it needs to be fixed in the unisys driver code, like I said
should be done for busses to prevent this type of issue :)
thanks,
greg k-h
next prev parent reply other threads:[~2015-08-07 18:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-01 5:12 [staging] 68905a14e49: kernel BUG at drivers/base/driver.c:153! kernel test robot
2015-08-01 5:12 ` [lkp] " kernel test robot
2015-08-07 2:28 ` Greg Kroah-Hartman
2015-08-07 2:28 ` [lkp] " Greg Kroah-Hartman
2015-08-07 7:15 ` Sudip Mukherjee
2015-08-07 7:15 ` [lkp] " Sudip Mukherjee
2015-08-07 18:01 ` Greg Kroah-Hartman [this message]
2015-08-07 18:01 ` Greg Kroah-Hartman
2015-08-08 5:10 ` Sudip Mukherjee
2015-08-08 5:10 ` [lkp] " 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=20150807180113.GC10282@kroah.com \
--to=gregkh@linuxfoundation.org \
--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.