Greg KH wrote:
I saw this once when debugging the usb code, but could never reproduce
it, so I attributed it to an incomplete build at the time, as a reboot
fixed it.
Is this easy to trigger for you?
This is the same oops as I posted yesterday: "2.6.17-mm1: oops in
Bluetooth stuff, usbdev_open". I haven't seen it since...
J
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]