udev errors in Sid; wake on lan problems in 2.6.15

[djhobo9]

Well first I should probably update you on my saga. I'm a defector from FreeBSD and installed Sarge about a week ago, got all my video and sound drivers happy, etc. Two days ago I decide that I can't handle the downgrade that going from FreeBSD to Debian Stable produced (although the increased hardware support was well worth it anyway), so I did a dist-upgrade all the way to Sid, and I absolutely love it.

Except for one/two things:

-PART 1:
On bootup, I get a nasty long string of errors (about 20) in the form of
udevd_event[xxxx]: failed to execute /lib/udev/udev_run_devd and
udevd_event[xxxx]: failed to execute /lib/udev/udev_run_hotplugd

Where xxxx is some PID that keeps increasing until some point where it just stops. I don't remember the text exactly, but that's pretty close and I can't reboot as I'm typing this message on the machine in question.

Before and after that the boot looks fine, and is quite fast. When I log in, udevd is running, and there seems to be no loss of functionality (still mounts/unmounts my iPod, etc). So should I be worried about this, and if so, how do I fix it??

-PART 2:
In the upgrade process I took my kernel up from 2.6.8-2-686-smp to 2.6.15-1-686-smp, and now I can't wake my machine up remotely. ethtool stil says that Wake-on-LAN is enabled. I retained the 2.6.8 kernel image, and if I power down from that I can wake it up with no problem, so how come it doesn't work in 2.6.15? My ethernet is an nForce onboard on an ASUS P5ND2-SLI mobo.

I don't think these two problems are related, and the first one is more of just an annoyance with no visible side effects. I'd much appreciate an answer to the second one, though.

Thanks!

[gruven]

The udev problems you are having are happening with the new kernel upgrade. I just got it too.

I fixed it by building the initrd with yaird instead of initramfs-tools. If you want to do that, you can. They may have it fixed in a few days though.

With the other problem, I can't help, sorry.

[djhobo9]

That makes me feel better--- not that it was affecting functionality, anyway.

Thanks.

[michan]

I affected by this issue too, at two computers.
gruven, does that you are saying mean that I must build the kernel on my own? Can't I just use "apt-get install [latest kernel]" (appearantly not, since that was what I did)? The thing is that I always fail while building it on my own.

[djhobo9]

I, too, have never been successful in building a custom 2.6.15 kernel... so for now I guess I'll just leave it-- it's still just as fast or faster than the 2.6.8 kernel.

Pardon me for being such a newbie, but should I be submitting a bug report or something similar (if so where do I go)? It's obviously not unique to me anymore. Or has someone already made the developers aware of this? I'm still getting the feel for how the Debian devel process works...

EDIT: I've just found it in the bug reports.... nevermind.

[gruven]

It is relatively easy to build and install your own custom kernel, just follow the documentation in the debian handbook on how to do it. I found that it works best to do it as a regular user though.

And no, you don't have to build and install a custom kernel to stop this from happening. All you have to do is switch to yaird, and it isn't that big of a deal.

apt-get install yaird
apt-get remove initramfs-tools
dpkg-reconfigure linux-image-`uname -r`

That is all I did, and the udev errors went away.

I am sure the debian devs will have it fixed before to long though, so that fix is completely optional. As far as I know, the errors don't hinder functionality.

[michan]

Yay, it worked. Arigatou Gonzaimazu.