> With latest cdparanoia git-^H^H^H^Hsvn, the problem still happens. > After applying the patch below, there's no more crash thanks to your last > commit, and It Just Works(tm): Then I will be doing some headscratching over a copy of the kernel. Oh-- what *exact* kernel are you using? non-x86 trees don't always sync often with the 'official' mainline and I want to be sure I'm reading the correct thing. I was a longtime PPC user until about two years ago, and I'm used to there being several substantially different PPC kernel trees [just making sure]. OTOH, if the kernel isn't even servicing the device as a block device until the drive returns a ready status and O_NONBLOCK thwarts waiting for that.... sigh. Nothing like a passthrough interface that still isn't a passthrough interface after fifteen years of dicking around. I'm not willing to cripple cdparanoia on more-than-one-cdrom systems because of an edge case due to yet another ill-considered block layer 'feature'. For one thing *I* need to be able to scan devices without blocking on my own multiple drive systems. If there's a workaround to get both, I will find it. But it's too early to say for sure. I'll check again. (May I ask-- why the hard starting/stopping of the interface? Power saving?] Monty -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
