> But the cd would not eject.
>
> I looked at the listing fuser /dev/cdrom gave to me, it showed a few of
> the xmms prosesses (it launches 4-5) were using the device. Nobody else.
>
> So I kill -HUP'ed the xmms prosesses. I killed them. I even killall
> -KILL'ed xmms as root dozens of times. One xmms process was still using
> the device, and another xmms process was in zombie state. eject -f or
> hitting the eject button on the drive anything I tried did not help.
>
> So basicly I could not get the cd out without reboot.
>
> This time, though, I don't think it was the drives fault, since it happily
> ejected the cd as soon as I rebooted the machine.
Yes, it can also be the drives fault! I once owned a CD-ROM
drive, which was able to put every IDE-CD driver (tried Linux
2.0.33, OS/2 Warp, Win95, PC-DOS with MSCDEX-Interface) into a
locked state. It spinned up and down and I couldn't eject, too.
But it also didn't serve any data.
Under Warp: Process accessing drive hung, others slowed down a
bit
Under Win95: Machine hang
Under Linux 2.0.33: Processes acessing drive hung, others in
normal operation (even the ones accessing the
master device of this drive)
Other behavior, was same you described. I think it was a
BTXXXXX-Drive (can't remember that crap).
Regards
Ingo Oeser
-- Feel the power of the penguin - run linux@your.pc <esc>:x
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/