From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
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 12:45:53 +0530 [thread overview]
Message-ID: <20150807071553.GA28337@sudip-pc> (raw)
In-Reply-To: <20150807022812.GI25067@kroah.com>
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.
regards
sudip
next prev parent reply other threads:[~2015-08-07 7:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-01 5:12 [lkp] [staging] 68905a14e49: kernel BUG at drivers/base/driver.c:153! kernel test robot
2015-08-07 2:28 ` Greg Kroah-Hartman
2015-08-07 7:15 ` Sudip Mukherjee [this message]
2015-08-07 18:01 ` Greg Kroah-Hartman
2015-08-08 5:10 ` 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=20150807071553.GA28337@sudip-pc \
--to=sudipm.mukherjee@gmail.com \
--cc=david.kershner@unisys.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.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