Skip to contentSkip to conversation

USB oops Linux 2.4.2ac6

DISCUSSION Peter Zaitcev 3 participants 3 messages Feb 28, 2001 – Mar 22, 2001

lore
Share & tools
lore
#0 lore raw
Quoted 10 lines
Quoted 2 lines

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 [email protected] may be able to help. Or may be not :)

-- Pete

#1 lore raw
Quoted 12 lines · Peter Zaitcev
Quoted 11 lines
Quoted 3 lines

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

Quoted 4 lines

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 [email protected] 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

#2 lore raw
In reply to Peter Zaitcev
Quoted 6 lines

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.

Quoted 2 lines

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