On Sun, 2007-11-25 at 17:10 +0100, Marco d'Itri wrote: > On Nov 25, Carlos Moffat <[EMAIL PROTECTED]> wrote: > > > Can't be. It worked perfectly fine before I upgraded to udev 113+, and > > it is working perfectly fine now that I've downgraded to udev 105. > Can't be an udev problem either, you are reporting kernel errors. >
I tried with kernels 2.6.18, 2.6.20. 2.6.21 and 2.6.22. Only the new udev triggers this issue. I'm not saying you're wrong here, but I think other users might benefit from this bug report, given the udev upgrade *is* triggering this bug. If you think this is a kernel issue, shouldn't the bug be forwarded to the kernel package instead of closed? Carlos -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
