>
> 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.
CD blanking only takes "one" command for the whole operation, as
e.g. compared to CD writing where you always have to push out data packets.
Why I think it's just one (note the quotes): You can interrupt/kill
cdrecord in the midst of blanking a CD, and blanking will continue to the
'end' (either fast blank or full blank, whichever was sent)
As mentioned some time earlier, I had similar, but not the same issues. I
could continue accessing the harddrive - otherwise mplayer would have
stopped immediately, but it played at least until EOF.
> 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.
Jan Engelhardt
--
-
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]
