Those were problems with the usb_id program, not problems in the
kernel. How up-to-date is your udev installation?
>> a few
>> dozen urb status -32 messages by powering off the sound card while it
>> was in use (log2),
Nothing wrong with that. You should expect that removing a device
while it is use would produce a few error messages.
>> but no crashes there. It did finally crash (log3),
>> though, after about three hours of coding + listening to music on text
>> console (no Nvidia drivers nor any other external modules). Apparently
>> it reset all USB buses, including the one that my system disk is
>> connected to (there is nothing else on the same port), effectively
>> killing the system, even though technically it didn't crash.
There's no indication in the log that the disk problem was at all
related to the sound card. Nor is there any indication that all your
USB buses were affected; only the disk drive got messed up. The card
reader, the hub, the keyboard, and the mouse all seem to have survived.
>> It also seems that .23-rc5 no longer exposes bConfigurationValue and a
>> few other settings under /sys/bus/usb/devices/*/,
Sure it does.
>> so I couldn't test if
>> switching the bConfigurationValue of the sound card still causes
>> crashesthere (it has been a reliable way to do that in the past).>
> I could not reproduce the excessive log flood of urb status -32,>
> mentioned in my original message.>
> The logs are here:>
> I gather that usb_id is something related to udev. It does not cras>
> with .22 kernels, only with the .23 series>
> OOPSes, to be specific, IIRC.
The events in your logs are not oopses. The program segfaults, which
means that the crash occurs in userspace, not while the program is
running in the kernel.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to XXXX@XXXXX.COM
More majordomo info at http://www.yqcomputer.com/
Please read the FAQ at http://www.yqcomputer.com/