[ 2.5.70 + ehci-0613 patch, log output sent, "Subject:" wrong ]
Just to summarize for the peanut gallery: the logs showed no problems at all ... until the PCI files spontaneously vanished from sysfs. That's not allowed to happen, something's deeply wrong outside USB on that system if PCI goes that bad.
Isn't it only in the last ehci-* directory that files are missing?
Yes, only the PCI files -- but not ones added by the EHCI driver. Though the usb5/* directory was there, without its USB files; and without the subdirectory indicating any device plugged in.
That is probably because cp fails to obtain these files after the actual crash/freeze, I guess, and also the reason why cp can't be killed (it's stuck in kernel mode).
There was also the problem that there were only usb-storage messages, while a misbehavior of that magnitude should have been spewing *all sorts* of informative messages. You can use Alt-SysRq-T to find out the kernel stack info, too. ("echo t > /proc/sysrq*" maybe.)
- Dave
------------------------------------------------------- This SF.NET email is sponsored by: eBay Great deals on office technology -- on eBay now! Click here: http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
