On Tuesday 09 November 2004 22:12, Tim Beauregard wrote: > There is a recognised fault with the 2.6.8 kernel when using cdrecord, > leading to a oops. I've tried 2.6.9 and found my CPU usage to be 100%, > and with the flag driveropts-burnfree, this was used 10 times, and burn > time was double that in 2.6.7. I'm sticking with 2.6.7 for now.
I don't get an oops - I just get a subprocess of cdrecord stuck in the D state (uninterruptable sleep). I have no idea why is gets into that state, but it does it every time what ever I do. -- Alan Chandler [EMAIL PROTECTED] First they ignore you, then they laugh at you, then they fight you, then you win. --Gandhi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
