A module deregistered incorrectly, or has a race between
post-load activities and unload. One way or another it left
a dangling proc entry.
The oops does not provide off-stack information, so it's impossible
to tell what particular modules is the culprit.
> May 23 02:46:24 localhost kernel: hub.c: USB new device connect on
> bus1/2, assigned device number 2
> May 23 02:46:24 localhost kernel: usb.c: USB device 2 (vend/prod
> 0x4a9/0x2204) is not claimed by any active driver.
What is this thing you have on USB? Try to run without it.
-- Pete
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/