On Wed, Apr 13, 2005 at 10:09:00AM +0200, Marco d'Itri wrote: > On Apr 13, Horms <[EMAIL PROTECTED]> wrote: > > > That is certainly true. But as the udev maintainer do > > you have any interest in helping to track down kernel-bugs > > related to udev? > Yes, but this does not mean that I have the skills to do it or that > kernel bugs triggered by udev should not be assigned to the kernel. > > > You probably work a lot more closely > > with the code than many members of the kernel-team, > Not with kernel code. > > > and any hints to what to look for would be very useful. > You have an oops with two clear stack traces, what else do you need? > I'm not a kernel hacker so I cannot explain what is happening, but I > expect that a kernel maintainer should be able to.
Ok, I assumed that you were a bit more familiar with the kernel code that relates to udev than you are. Thats all. The bug definately is a kernel bug, and you are right, we do have an oops to work from. -- Horms -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]