On Monday 27 July 2009, Pavel Roskin wrote: > > But I think you may be getting something when the freeze happen. But to > see it, you need to be on a text console. There are other ways to > capture the kernel messages, which are described in the file > Documentation/oops-tracing.txt in the Linux sources. I've taken some photos of the screen from the insertion of the card through to ejecting it, and uploaded them to imageshack: They can be viewed at: http://img145.imageshack.us/img145/8741/xdscn0647.jpg http://img170.imageshack.us/img170/1954/xdscn0648.jpg http://img195.imageshack.us/img195/807/xdscn0649.jpg http://img195.imageshack.us/img195/9625/xdscn0650.jpg http://img195.imageshack.us/img195/2717/xdscn0651.jpg http://img170.imageshack.us/img170/6103/xdscn0652.jpg http://img170.imageshack.us/img170/5844/xdscn0653.jpg Between them they should show all the output to the console, although some do overlap a little. I hope they are helpful in tracking down this problem. Thanks, Chris -- No, Sir; there is nothing which has yet been contrived by man, by which so much happiness is produced as by a good tavern or inn - Doctor Samuel Johnson -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
