Am Sonntag, den 19.07.2020, 12:55 +0100 schrieb Tj (Elloe Linux): > On 19/07/2020 12:09, Greg KH wrote: > > On Sun, Jul 19, 2020 at 11:22:10AM +0100, Tj (Elloe Linux) wrote: > > Where is an error here? Those looks ok to me. > > These repeated 'zaps' and resets every 30 seconds or so are not errors? They are errors. But whose errors? 0x28 looks like a READ10 to me. In other words at least Test Unit Ready and READ_CAPACITY have already worked at this stage. Without a trace it is not clear what exactly this read is for. Is it always the same READ? This looks like the error handling UAS does when a command times out. > They never stop even though the devices are not mounted nor being > accessed (by users). > > > > [ 199.939976] blk_update_request: I/O error, dev sda, sector 500117464 > > > op 0x0:(READ) flags 0x80700 phys_seg 5 prio class 0 > > > > So only the block layer is reporting errors, not the USB layer? Any usb > > controller errors? The error is from the SCSI layer strictly speaking. It notices that a command is taking longer than allowed and directs UAS to do error handling. SUbsequently an error is reported up to the block layer. The problem is that we have a lot of unusual stuff being tested. Regards Oliver
