On Fri, Feb 10, 2006 at 04:26:01PM -0500, Phillip Susi wrote:
> If that is what is going on, there is nothing linux can do about it;
> it's a limitation of the hardware. The IDE controller can only accept
> one command at a time, so if that command takes a while to complete, the
> other drive on the same channel can not be accessed until the first
> command completes.
>
> If the system doesn't come back though after sufficient time has gone by
> for the burn to complete, then this is probably not what is happening.
> I'd suggest using magic-sysreq to force an unmount and reboot, then see
> if there's anything in the logs.
Perhaps a good test would be to try cdrecord from the command line to
blank the cd, to avoid issues to do with X, xcdroast, etc. Just the
minimum you can have.
Also what command line does xcdroast generate for the blanking?
Len Sorensen
-
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]
