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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
