Bug#649033: linux-image-3.1.0-1-amd64: boot sometimes stuck with "waiting for /dev to be fully populated."
Package: linux-2.6
Version: 3.1.1-1
Severity: important
The boot sometimes freezes with the message:
"waiting for /dev to be fully populated."
There was a bug report against udev (bug #606192), which is closed,
suggesting a kernel bug if the timeout doesn't occur, which is the
case here (with linux-image-3.1.0-1-amd64 3.1.1-1).
"If the boot does not continue then it looks like that udev loaded a
module which crashed your system (so this would be a kernel bug)."
I'm not the only one who has this problem:
http://identi.ca/conversation/84449449
Note that even though this problem doesn't occur very often, it can be
very problematic if one wants to reboot the machine remotely, as there
is no way to redo a reboot.
-- Package-specific info:
** Version:
Linux version 3.1.0-1-amd64 (Debian 3.1.1-1) (ben@decadent.org.uk) (gcc version 4.6.2 (Debian 4.6.2-4) ) #1 SMP Mon Nov 14 08:02:25 UTC 2011
** Kernel log:
[ 11.653828] [drm] nouveau 0000:01:00.0: 0: memory 100MHz core 169MHz shader 338MHz voltage 900mV fanspeed 100% timing 0
[ 11.653832] [drm] nouveau 0000:01:00.0: 1: memory 250MHz core 275MHz shader 550MHz voltage 900mV fanspeed 100% timing 1
[ 11.653836] [drm] nouveau 0000:01:00.0: 2: memory 400MHz core 500MHz shader 1000MHz voltage 1090mV fanspeed 100% timing 2
[ 11.653840] [drm] nouveau 0000:01:00.0: 3: memory 400MHz core 580MHz shader 1450MHz voltage 1170mV fanspeed 100% timing 3
[ 11.653869] [drm] nouveau 0000:01:00.0: Register 0x00004030 not found in PLL limits table
[ 11.653982] [drm] nouveau 0000:01:00.0: c: memory 249MHz core 275MHz shader 550MHz voltage 900mV
[ 11.656429] [TTM] Zone kernel: Available graphics memory: 2024866 kiB.
[ 11.656432] [TTM] Initializing pool allocator.
[ 11.656443] [drm] nouveau 0000:01:00.0: Detected 256MiB VRAM
[ 11.656449] mtrr: type mismatch for e0000000,10000000 old: write-back new: write-combining
[ 11.656474] [drm] nouveau 0000:01:00.0: 512 MiB GART (aperture)
[ 11.670404] [drm] nouveau 0000:01:00.0: ACPI backlight interface available, not registering our own
[ 11.671776] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
[ 11.671778] [drm] No driver support for vblank timestamp query.
[ 11.699932] ieee80211 phy0: Selected rate control algorithm 'iwl-agn-rs'
[ 11.707286] input: DualPoint Stick as /devices/platform/i8042/serio1/input/input9
[ 11.724092] input: AlpsPS/2 ALPS DualPoint TouchPad as /devices/platform/i8042/serio1/input/input10
[ 11.877392] [drm] nouveau 0000:01:00.0: allocated 1440x900 fb: 0x310000, bo ffff88011a388400
[ 11.877466] fbcon: nouveaufb (fb0) is primary device
[ 11.952017] dell_wmi: Received unknown WMI event (0x11)
[ 13.218625] Console: switching to colour frame buffer device 180x56
[ 13.221576] fb0: nouveaufb frame buffer device
[ 13.221577] drm: registered panic notifier
[ 13.221587] [drm] Initialized nouveau 0.0.16 20090420 for 0000:01:00.0 on minor 0
[ 13.244484] dell_wmi: Received unknown WMI event (0x11)
[ 13.383201] snd_hda_intel 0000:00:1b.0: PCI INT A -> GSI 21 (level, low) -> IRQ 21
[ 13.383266] snd_hda_intel 0000:00:1b.0: irq 47 for MSI/MSI-X
[ 13.383297] snd_hda_intel 0000:00:1b.0: setting latency timer to 64
[ 13.493888] input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:1b.0/input/input11
[ 13.509229] input: HDA Intel Mic at Sep Left Jack as /devices/pci0000:00/0000:00:1b.0/sound/card0/input12
[ 13.509324] input: HDA Intel Mic at Ext Right Jack as /devices/pci0000:00/0000:00:1b.0/sound/card0/input13
[ 13.509405] input: HDA Intel Line Out at Sep Left Jack as /devices/pci0000:00/0000:00:1b.0/sound/card0/input14
[ 13.509485] input: HDA Intel HP Out at Ext Right Jack as /devices/pci0000:00/0000:00:1b.0/sound/card0/input15
[ 13.860800] WARNING! power/level is deprecated; use power/control instead
[ 13.998220] Linux media interface: v0.10
[ 14.002163] Linux video capture interface: v2.00
[ 14.014492] uvcvideo: Found UVC 1.00 device Laptop_Integrated_Webcam_0.3M (0c45:63f8)
[ 14.028812] input: Laptop_Integrated_Webcam_0.3M as /devices/pci0000:00/0000:00:1a.7/usb1/1-6/1-6:1.0/input/input16
[ 14.028902] usbcore: registered new interface driver uvcvideo
[ 14.028904] USB Video Class driver (1.1.1)
[ 14.121270] usb 3-1.3: new full speed USB device number 5 using uhci_hcd
[ 14.251270] usb 3-1.3: New USB device found, idVendor=413c, idProduct=8156
[ 14.251274] usb 3-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 14.251278] usb 3-1.3: Product: Dell Wireless 370 Bluetooth Mini-card
[ 14.251281] usb 3-1.3: Manufacturer: Dell Computer Corp
[ 14.352418] Bluetooth: Core ver 2.16
[ 14.352439] NET: Registered protocol family 31
[ 14.352441] Bluetooth: HCI device and connection manager initialized
[ 14.352443] Bluetooth: HCI socket layer initialized
[ 14.352445] Bluetooth: L2CAP socket layer initialized
[ 14.352450] Bluetooth: SCO socket layer initialized
[ 14.365187] Bluetooth: Generic Bluetooth USB driver ver 0.6
[ 14.373380] usbcore: registered new interface driver btusb
[ 16.162538] EXT3-fs (dm-1): using internal journal
[ 16.508528] loop: module loaded
[ 17.025483] Adding 9928700k swap on /dev/mapper/xvii-swap_1. Priority:-1 extents:1 across:9928700k
[ 22.453211] RPC: Registered named UNIX socket transport module.
[ 22.453214] RPC: Registered udp transport module.
[ 22.453215] RPC: Registered tcp transport module.
[ 22.453217] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 22.483570] FS-Cache: Loaded
[ 22.508024] FS-Cache: Netfs 'nfs' registered for caching
[ 22.520363] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[ 23.650366] fuse init (API version 7.17)
[ 25.721850] input: ACPI Virtual Keyboard Device as /devices/virtual/input/input17
[ 36.167579] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 36.167581] Bluetooth: BNEP filters: protocol multicast
[ 36.288116] Bluetooth: RFCOMM TTY layer initialized
[ 36.288121] Bluetooth: RFCOMM socket layer initialized
[ 36.288123] Bluetooth: RFCOMM ver 1.11
[ 38.360618] lp: driver loaded but no devices found
[ 38.363474] ppdev: user-space parallel port driver
[ 54.203801] ip_tables: (C) 2000-2006 Netfilter Core Team
[ 56.128313] e1000e 0000:00:19.0: irq 44 for MSI/MSI-X
[ 56.184099] e1000e 0000:00:19.0: irq 44 for MSI/MSI-X
[ 56.184665] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 57.744902] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: None
[ 57.744907] e1000e 0000:00:19.0: eth0: 10/100 speed: disabling TSO
[ 57.745342] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 57.958376] device eth0 entered promiscuous mode
[ 63.689262] iwlagn 0000:0c:00.0: L1 Enabled; Disabling L0S
[ 63.692273] iwlagn 0000:0c:00.0: Radio type=0x0-0x2-0x0
[ 63.844592] iwlagn 0000:0c:00.0: L1 Enabled; Disabling L0S
[ 63.847574] iwlagn 0000:0c:00.0: Radio type=0x0-0x2-0x0
[ 63.902111] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 67.960937] device eth0 left promiscuous mode
[ 68.272247] eth0: no IPv6 routers present
[ 211.090115] process `sysctl' is using deprecated sysctl (syscall) net.ipv6.neigh.default.retrans_time; Use net.ipv6.neigh.default.retrans_time_ms instead.
[ 354.864284] iwlagn 0000:0c:00.0: RF_KILL bit toggled to disable radio.
[ 354.864288] keyboard: can't emulate rawmode for keycode 240
[ 354.864301] keyboard: can't emulate rawmode for keycode 240
[ 354.886089] iwlagn 0000:0c:00.0: Not sending command - RF KILL
[ 354.886093] iwlagn 0000:0c:00.0: Error sending REPLY_RXON: enqueue_hcmd failed: -5
[ 354.886097] iwlagn 0000:0c:00.0: Error clearing ASSOC_MSK on BSS (-5)
[ 355.040088] usb 3-1: USB disconnect, device number 2
[ 355.040092] usb 3-1.1: USB disconnect, device number 3
[ 355.120165] usb 3-1.2: USB disconnect, device number 4
[ 355.120256] usb 3-1.3: USB disconnect, device number 5
[ 355.120481] Bluetooth: hci0 urb ffff8801176e3440 submission failed
[ 465.348053] CE: hpet increased min_delta_ns to 20113 nsec
** Model information
sys_vendor: Dell Inc.
product_name: Latitude E6400
product_version:
chassis_vendor: Dell Inc.
chassis_version:
bios_vendor: Dell Inc.
bios_version: A12
board_vendor: Dell Inc.
board_name: 0K672N
board_version:
0c:00.0 Network controller [0280]: Intel Corporation Ultimate N WiFi Link 5300 [8086:4235]
Subsystem: Intel Corporation Device [8086:1121]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 46
Region 0: Memory at f1ffe000 (64-bit, non-prefetchable) [size=8K]
Capabilities: <access denied>
Kernel driver in use: iwlagn
** USB devices:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 004: ID 0c45:63f8 Microdia Sonix Integrated Webcam
Bus 005 Device 002: ID 0a5c:5800 Broadcom Corp. BCM5880 Secure Applications Processor
Kernel: Linux 3.1.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages linux-image-3.1.0-1-amd64 depends on:
ii debconf [debconf-2.0] 1.5.41
ii initramfs-tools [linux-initramfs-tool] 0.99
ii linux-base 3.4
ii module-init-tools 3.16-1
Versions of packages linux-image-3.1.0-1-amd64 recommends:
ii firmware-linux-free 3
Versions of packages linux-image-3.1.0-1-amd64 suggests:
ii grub-pc | extlinux | lilo <none>
ii linux-doc-3.1 3.1.1-1
Versions of packages linux-image-3.1.0-1-amd64 is related to:
pn firmware-bnx2 <none>
pn firmware-bnx2x <none>
pn firmware-ipw2x00 <none>
pn firmware-ivtv <none>
pn firmware-iwlwifi 0.34
pn firmware-linux <none>
pn firmware-linux-nonfree <none>
pn firmware-qlogic <none>
pn firmware-ralink <none>
pn xen-hypervisor <none>
--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20111117002908.GA8771@xvii.vinc17.org">http://lists.debian.org/20111117002908.GA8771@xvii.vinc17.org
11-16-2011, 11:52 PM
Ben Hutchings
Bug#649033: linux-image-3.1.0-1-amd64: boot sometimes stuck with "waiting for /dev to be fully populated."
On Thu, Nov 17, 2011 at 01:29:08AM +0100, Vincent Lefevre wrote:
> Package: linux-2.6
>
> Version: 3.1.1-1
> Severity: important
>
> The boot sometimes freezes with the message:
>
> "waiting for /dev to be fully populated."
>
> There was a bug report against udev (bug #606192), which is closed,
> suggesting a kernel bug if the timeout doesn't occur, which is the
> case here (with linux-image-3.1.0-1-amd64 3.1.1-1).
[...]
Please start the kernel without 'quiet' (the GRUB 'rescue mode'
entries will do this) so the kernel logs more to the console, and
send us the resulting messages (a photograph with readable text
is fine).
Ben.
--
Ben Hutchings
We get into the habit of living before acquiring the habit of thinking.
- Albert Camus
--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20111117005218.GG3366@decadent.org.uk">http://lists.debian.org/20111117005218.GG3366@decadent.org.uk
11-23-2011, 10:54 AM
Mauro Meloni
Bug#649033: linux-image-3.1.0-1-amd64: boot sometimes stuck with "waiting for /dev to be fully populated."
I've had a similar problem with 3.0.0, in my case the processor module hung the system on every boot. Although it wasn't a real solution, adding processor.nocst=1 as a boot parameter did the trick.
However, it is true that in many cases the freeze is not a problem of udev but of a kernel module that udev loads during boot. Sometimes it helps to grab a list of loaded modules when/if the system boots properly with another kernel, then boot the problematic kernel in single mode (or using init=/bin/bash) and try loading one module at a time. That's how I found the culprit in my case.
--
Mauro
--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 1322049260.81182.YahooMailNeo@web38005.mail.mud.ya hoo.com">http://lists.debian.org/1322049260.81182.YahooMailNeo@web38005.mail.mud.ya hoo.com
11-23-2011, 01:03 PM
Vincent Lefevre
Bug#649033: linux-image-3.1.0-1-amd64: boot sometimes stuck with "waiting for /dev to be fully populated."
On 2011-11-23 03:54:20 -0800, Mauro Meloni wrote:
> However, it is true that in many cases the freeze is not a problem
> of udev but of a kernel module that udev loads during boot.
> Sometimes it helps to grab a list of loaded modules when/if the
> system boots properly with another kernel, then boot the problematic
> kernel in single mode (or using init=/bin/bash) and try loading one
> module at a time. That's how I found the culprit in my case.
This is possible when the freeze occurs at each boot. But in my case,
it seems to occur completely randomly (I would have thought more often
shortly after installing a new kernel, but I'm not sure), and not very
often.
I've removed the quiet option and rebooted a few times, but the
machine didn't freeze. I'll try a few more times. But I wonder
whether the freeze can occur without the quiet option (for instance,
configuring udev as verbose always resulted in a freeze).
--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20111123140331.GM3117@xvii.vinc17.org">http://lists.debian.org/20111123140331.GM3117@xvii.vinc17.org
11-27-2011, 08:39 AM
Uwe Kleine-König
Bug#649033: linux-image-3.1.0-1-amd64: boot sometimes stuck with "waiting for /dev to be fully populated."
Hello,
On Thu, Nov 17, 2011 at 01:29:08AM +0100, Vincent Lefevre wrote:
> Package: linux-2.6
>
> Version: 3.1.1-1
> Severity: important
>
> The boot sometimes freezes with the message:
>
> "waiting for /dev to be fully populated."
>
> There was a bug report against udev (bug #606192), which is closed,
> suggesting a kernel bug if the timeout doesn't occur, which is the
> case here (with linux-image-3.1.0-1-amd64 3.1.1-1).
>
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=606192#98
>
> "If the boot does not continue then it looks like that udev loaded a
> module which crashed your system (so this would be a kernel bug)."
>
> I'm not the only one who has this problem:
>
> http://identi.ca/conversation/84449449
>
Occasionally I see this, too. Today I waited a bit longer and got more
output after some time:
udevd[422]: timeout: killing '/sbin/modprobe -b acpi:SMO1200:PNP0C31:' [444] (repeated many times)
--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20111127093915.GC17668@pengutronix.de">http://lists.debian.org/20111127093915.GC17668@pengutronix.de
12-12-2011, 08:04 PM
Andrea Bolognani
Bug#649033: linux-image-3.1.0-1-amd64: boot sometimes stuck with "waiting for /dev to be fully populated."
I’m seeing this too on my ThinkPad X201i. The kernel I’m
running is linux-image-3.1.0-1-686-pae version 3.1.1-1.
It happens quite frequently, most often when first booting in the
morning; forcing a shutdown and trying booting again usually results
in a normal boot.
If there’s some debug output I can can collect to help track this
down, please let me know.
--
Andrea Bolognani <eof@kiyuko.org>
Resistance is futile, you will be garbage collected.
01-04-2012, 07:48 AM
Vincent Lefevre
Bug#649033: linux-image-3.1.0-1-amd64: boot sometimes stuck with "waiting for /dev to be fully populated."
Hi,
On 2011-11-17 00:52:18 +0000, Ben Hutchings wrote:
> On Thu, Nov 17, 2011 at 01:29:08AM +0100, Vincent Lefevre wrote:
> > The boot sometimes freezes with the message:
> >
> > "waiting for /dev to be fully populated."
> >
> > There was a bug report against udev (bug #606192), which is closed,
> > suggesting a kernel bug if the timeout doesn't occur, which is the
> > case here (with linux-image-3.1.0-1-amd64 3.1.1-1).
> [...]
>
> Please start the kernel without 'quiet' (the GRUB 'rescue mode'
> entries will do this) so the kernel logs more to the console, and
> send us the resulting messages (a photograph with readable text
> is fine).
It happened yeaterday, for the first time after I removed the 'quiet'
option. There were a few lines about the wifi chipset, and the last
message was:
iwlagn 0000:0c:00.0: Refused to change power state, currently in D3
--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20120104084848.GA24759@xvii.vinc17.org">http://lists.debian.org/20120104084848.GA24759@xvii.vinc17.org
01-05-2012, 09:38 PM
Vincent Lefevre
Bug#649033: linux-image-3.1.0-1-amd64: boot sometimes stuck with "waiting for /dev to be fully populated."
On 2012-01-04 09:48:48 +0100, Vincent Lefevre wrote:
> It happened yeaterday, for the first time after I removed the 'quiet'
> option. There were a few lines about the wifi chipset, and the last
> message was:
>
> iwlagn 0000:0c:00.0: Refused to change power state, currently in D3
This has occurred another time. Since this bug was too generic (other
users posted different causes), I've opened a new one: bug #654822
--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20120105223852.GA3689@xvii.vinc17.org">http://lists.debian.org/20120105223852.GA3689@xvii.vinc17.org