--- http://lxr.linux.no/source/drivers/usb/storage/transport.c?v=2.6.8.1
...
967 US_DEBUGP("Bulk Command S 0x%x T 0x%x L %d F %d Trg %d LUN
%d CL %d\n",
...
1035 US_DEBUGP("Bulk Status S 0x%x T 0x%x R %u Stat 0x%x\n",
---
I think those are among the first and last dmesg we want, near the time
of trouble. Giving us an extra paragraph before and afterwards probably
wouldn't hurt either.
Yes, these lines exist in my 2.6.9-sources. But how do I get these debugs shown in the logfiles without turning verbose usb-storage debugging on? Otherwise the debug-logfiles would be too big.
The available configurations of usb-storage printk being either too concise or too verbose is a known problem, volunteers welcome ...
You can edit the statements. Change
US_DEBUGP("...
to
printk(KERN_DEBUG "usb-storage: ...
Me, I'm voting that, for this problem, as for most read/ write failures, we want to collect the CBW and CSW quoted above but also the CDB of:
http://lxr.linux.no/source/drivers/usb/storage/debug.c?v=2.6.8.1
146 US_DEBUGP("Command %s (%d bytes)\n", what, srb->cmd_len);
147 US_DEBUGP("");
148 for (i = 0; i < srb->cmd_len && i < 16; i++)
149 US_DEBUGPX(" %02x", srb->cmnd[i]);
150 US_DEBUGPX("\n");Beyond converting to printk(KERN_DEBUG, we might need a further patch to make sure that code gets compiled and called.
Would be nice to have a print of the plain hex of sense data, but I suppose that's impractically out of reach.
Pat LaVarre
-------------------------------------------------------
This Newsletter Sponsored by: Macrovision For reliable Linux application installations, use the industry's leading
setup authoring tool, InstallShield X. Learn more and evaluate today. http://clk.atdmt.com/MSI/go/ins0030000001msi/direct/01/
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-users
