On Tue, 14 Nov 2006, David Relson wrote: > Nothing interesting deleted. The first log entry I sent to you (and > its immediate predecessor) are: > > Nov 13 10:01:01 osage cron[32083]: (root) CMD (nice -n 19 > run-parts /etc/cron.hourly) > Nov 13 10:45:46 osage hub 1-0:1.0: state 7 ports 6 chg 0000 evt 0004
This suggests that the problem exists at the hardware or firmware level, not in the kernel. The message means that the computer's USB controller saw the drive disconnect. Maybe the drive really did disconnect, or maybe there was some sort of signalling problem in the USB cable, or maybe the USB controller itself is flaky. No easy way to know which, although you can try using a different cable and searching for sources of EM interference. > I'm running a kernel built yesterday with CONFIG_USB_DEBUG=y and > CONFIG_LOG_BUF_SHIFT=17 but, as luck would have it, last night's full > dump took 9 hrs and encountered no trouble. > > When I have new, interesting info, I'll send it along. Okay, we'll see what happens. Alan Stern ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Linux-usb-users@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
