> With a 2.5.7-pre1 kernel, "uhci", that pci_pool patch I sent around > recently (which is in 2.5.7 fyi, and applies to 2.4.19-pre except for > the very last chunk), and with CONFIG_DEBUG_SLAB, I got an > OOPS too. I couldn't ksymoops in this setup.
And just FYI, "usb-uhci" worked here ... but after enumerating (including descriptor fetches), after "modprobe hid" I saw several "host controller halted, trying to restart" messages. Same sort of thing when I actually used the trackball ... it actually reported events through /dev/input/mice, but before each event it restarted the controller five times. Since I've never seen oopses or "controller halted" before when using this trackball, I wonder if anyone really tried to use that poisoning capability with the UHCI drivers before. If not, what I'm seeing here could easily be latent bugs in QH/TD handling ... uhci accessing freed ones, and usb-uhci telling the HC to access freed ones. - Dave _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
