Yeah, I understand that. Sorry, I use squirrelmail. Pretty limited... I'll get you a "raw" dmseg output when I replicate the problem. Let me clarify on khubd: There is such an entry in my process table, but there was no kernel thread stack trace for it when I dumped the traces. I don't know if that is a bad sign... Right now I thought it would be best to verify my hardware, so I'm working with the new hubs and cables, writing a large file to each of seven attached (non-md) flash drives and diff-ing the usb drive contents against the original file. If I have dead cables, connectors, or flash drives that would save you all a lot of hassle. When I'm done with that, I'll again replicate my problem, grab the logs straight from dmesg, and post another entry here. I'll even fire up kmail or mutt to avoid bad formatting. Thanks again. -- Michael Schwarz > On Sat, 17 Mar 2007, Michael Schwarz wrote: > >> Nasty big stack trace set follows: > > This format is kind of awkward. For one thing, a lot of lines were > wrapped by your email program. > > For another, you copied the stack trace from the syslog log file. That is > not a good way to do it; syslogd is liable to miss bits and pieces of > the kernel log when a lot of information comes along all at once. You're > much better off getting the stack trace data directly from dmesg. (And > when you do, you don't end up with 30 columns of wasted data added to the > beginning of each line.) > > Alan Stern > > - To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
