Re: USB oops Linux 2.4.2ac6

Re: USB oops Linux 2.4.2ac6

[Peter Zaitcev]

> > 2.4.2-ac6 
> > o USB hub kmalloc wrong size corruption fix (Peter Zaitcev) 

> The first line of the oops is 
> 
> ----
> kernel BUG at slab.c:1398!
> ----
> Any other ideas to try?
>         -Thomas

I did not break it, honest! I will be looking in a USB mouse
problem though. If you need an immediate resolution, nice
folks at linux-usb@lists.sourceforge.net may be able to help.
Or may be not :)

-- Pete

Re: USB oops Linux 2.4.2ac6

[Thomas Dodd]

Peter Zaitcev wrote:
> 
> > > 2.4.2-ac6
> > > o USB hub kmalloc wrong size corruption fix (Peter Zaitcev)
> 
> > The first line of the oops is
> >
> > ----
> > kernel BUG at slab.c:1398!
> > ----
> > Any other ideas to try?
> >         -Thomas
> 
> I did not break it, honest! I will be looking in a USB mouse
> problem though. If you need an immediate resolution, nice
> folks at linux-usb@lists.sourceforge.net may be able to help.
> Or may be not :)

I found the problem.
CONFIG_DEBUG_SLAB "Debug memory allocation"
in the 2.4.2-ac series doesn't work with USB.

2.4.2-ac5 just booted and found the mouse correctly.
On to ac-21 now...

Did David Brownell's patch to disable OHCI loading
on the AMD-756 make it into the source trees?

	-Thomas

Re: [linux-usb-devel] Re: USB oops Linux 2.4.2ac6

[David Brownell]

> I found the problem.
> CONFIG_DEBUG_SLAB "Debug memory allocation"
> in the 2.4.2-ac series doesn't work with USB.
> 
> 2.4.2-ac5 just booted and found the mouse correctly.
> On to ac-21 now...

I just glanced at Alan's change list, it didn't have patches
that seemed to cover that (vs ac20).

You might see what sort of luck you have with the patches
I posted to linux-usb-devel earlier today.  At least both
usb-ohci and usb-uhci enumerated even after configuring
in slab debugging ... but there are bugs yet to be found.
Maybe it deserves a CONFIG_DEBUG_PCI_POOL to
decouple autopoisoning from CONFIG_DEBUG_SLAB.


> Did David Brownell's patch to disable OHCI loading
> on the AMD-756 make it into the source trees?

It's been sent to Linus.  Unless/until someone learns the
vendor fix and implements it, it seems to be the best way
to prevent the 756-specific USB problems (happening
most with lowspeed devices like mice).

- Dave