Re: [OOPS] Linux-2.6.0-test5-bk

[Greg KH <greg@kroah.com>]

On Wed, Sep 10, 2003 at 05:36:51PM -0700, Ranjeet Shetye wrote:
> On Wed, 2003-09-10 at 17:24, Greg KH wrote:
> > On Wed, Sep 10, 2003 at 05:19:05PM -0700, Ranjeet Shetye wrote:
> > > 
> > > Your changes fixed the issue. Thanks a lot for your help. I still get
> > > this call trace, but no more OOPS on bootup.
> > > 
> > > kobject_register failed for Ensoniq AudioPCI (-17)
> > > Call Trace:
> > >  [<c026f45c>] kobject_register+0x50/0x59
> > >  [<c02f8003>] bus_add_driver+0x4c/0xaf
> > >  [<c02f8453>] driver_register+0x31/0x35
> > >  [<c027c3bf>] pci_populate_driver_dir+0x29/0x2b
> > >  [<c027c491>] pci_register_driver+0x5e/0x83
> > >  [<c06a145f>] alsa_card_ens137x_init+0x15/0x41
> > >  [<c068475a>] do_initcalls+0x2a/0x97
> > >  [<c012e920>] init_workqueues+0x12/0x2a
> > >  [<c01050a3>] init+0x39/0x196
> > >  [<c010506a>] init+0x0/0x196
> > >  [<c0108f31>] kernel_thread_helper+0x5/0xb
> > 
> > Odds are that the pci driver is trying to register 2 drivers with the
> > pci core with the same name.  What does /sys/bus/pci/drivers show?
> > 
> > thanks,
> > 
> > greg k-h
> 
> Hi Greg,
> 
> I didn't find a /proc/sys/bus/pci/drivers, but I did find a
> /proc/bus/pci/devices - which is what I am guessing you meant. If you
> did in fact mean '/proc/sys/bus/pci/drivers' then I dont have any such
> file. In fact I dont have a bus sub-directory under /proc/sys/

No, look at what I asked for above, "/sys/bus/pci..."  I don't care about
/proc at all :)

sysfs is mounted at /sys.

thanks,

greg k-h