Your message dated Wed, 5 Sep 2012 10:30:13 +0200
with message-id <[email protected]>
and subject line Re: Bug#686707: Can not boot up after upgrade udev from 175-3
to 175-7
has caused the Debian Bug report #686707,
regarding Can not boot up after upgrade udev from 175-3 to 175-7
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
686707: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686707
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: udev
Version: 157-7
After I upgraded udev from 175-3 to 175-7, I got the following error
message during boot up:
/*************************************************************************************************************************/
udevd[39]: error getting socket: Address family not supported by protocol
error initializing udev control socketudevd[39]: error initializing udev
control socket
error getting socket: Address family not supported by protocol
udevadm[49]: error getting socket: Address family not supported by protocol
Gave up waiting for root device. Common problems:
- Boot args (cat /proc/cmdline)
- Check rootdelay= (did the system wait long enough?)
-Check root= (did the system wait for the right device?)
-Missing modules (cat /proc/modules; ls /dev)
ALERT! /dev/disk/by-uuid/f504ba73-7092-4632-a1c1-fc2b2466fe52 does not
exist.
Dropping to a shell!
...
/*************************************************************************************************************************/
Thanks,
Wei
--- End Message ---
--- Begin Message ---
On Sep 05, wei sun <[email protected]> wrote:
> Yes, I am using a self-compiled kernel. It is debian testing with 3.2.23
As documented in README.Debian, this is not supported.
CONFIG_UNIX=m
--
ciao,
Marco
--- End Message ---
