Joerg Schilling <[email protected]> wrote:
> I am not sure if the log from the OP includes all information.
>
> I've seen already messages like this:
>
> cdrecord: Input/output error. Cannot set SG_SET_TIMEOUT.
>
> This should be something that I would never to expect to happen.
>
> If the OP does not see a similar message, it seems that the call is
> accepted but later ignored. I have no idea why this happens.
Let me add some notes:
Some drives do not support (or correctly support) the 'read buffer' command.
As I don't have all drives, I cannot tell how the drive from the OP behaves on
Solaris. All drives I've seen so far return an error on Solaris - not a timeout,
so it is not clear, whether the hang on Linux would result in a timeout on Solaris.
It may be that the /dev/hd* interface ignores timeouts, but it may also be that
the bus situation did cause a kernel hang. As my experience shows that all
drives behave always the same, it should be simple to trace the problem for the
owner of a drive.
Jörg
--
EMail:[email protected] (home) Jörg Schilling D-13353 Berlin
[email protected] (uni)
[email protected] (work) Blog: http://schily.blogspot.com/
URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
