Re: 599.58 KASSERT kernel panic i386

[Nat Sloss <nathanialsloss%yahoo.com.au@localhost>]

Hi,

I've found the problem.

umass.c doesn't acquire a kernel lock before calling usbd_transfer in usbdi.c.

Locks would be required for every driver calling usbd_transfer and similar 
functions in usbdi.c that have a kernel assertion on locks.

So my question is would every driver need to be modified? or is it possible to 
have the kernel locking function in usbd_transfer and similar and still be MP 
safe?

Regards,

Nat.