On Tue, 30 Sep 2008, Monty Montgomery wrote: > > 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]. It happens on anything after 2.6.24 (cfr. http://bugzilla.kernel.org/show_bug.cgi?id=10974). E.g. mainline 2.6.27-rc8. > 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. The difficult part is who's to blame: Linux commit 38582a62ecd337de4212004c7d4844899dc57890 or cdparanoia? > (May I ask-- why the hard starting/stopping of the interface? Power saving?] Which hard starting/stopping do you mean? Thanks! With kind regards, Geert Uytterhoeven Software Architect Sony Techsoft Centre Europe The Corporate Village  Da Vincilaan 7-D1  B-1935 Zaventem  Belgium Phone: +32 (0)2 700 8453 Fax: +32 (0)2 700 8622 E-mail: Geert.Uytterhoeven@xxxxxxxxxxx Internet: http://www.sony-europe.com/ A division of Sony Europe (Belgium) N.V. VAT BE 0413.825.160  RPR Brussels Fortis  BIC GEBABEBB  IBAN BE41293037680010
