Hi, Mike Castle wrote: > Has the drive displayed this behavior since you turned on the machine, > or just you just start to notice it after a while?
I noticed it on the day when i got the machine. > Maybe it only starts to happen after it's been on for a while, and > <snark>Window machines don't stay booted long enough</snark>. Under other circumstances i would happily support this theory. > Ok, really maybe it only starts to happen after some specific event, > which could be any thing you'd done while working on libburn, or some > internal timer kicked off, or something like that. Some delayed action came to my mind too. But my own experience with the MMC specs and the statement of the manufacturer make this improbable. If there was a command sequence which causes such a delayed action, then it must be in effect for more than one pull-in. Normally i would expect that such a delayed action is not repeated without new commands. But my drive pulls in without any commands shown by btrace between two experiments. > It wasn't clear if your stability testing revolved around libburn or > not. All dangerous tests are made with burners in USB boxes. (Linux still has the best behavior when it comes to get rid of a stuck USB drive.) The burner in question is attached via SATA directly. It gets no SCSI commands from libburn, which the other four burners did not get. Have a nice day :) Thomas -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/16833554831973457...@scdbackup.webframe.org
