It looks like some of our hardware is not recognised at boot time.
similar to my external hard drive, sometimes, it just hangs there until i
unplug my hard drive, then it works fine.




2008/12/22 André Neves <andrechale...@gmail.com>

> Hi,
>
> For several months now I've had my laptop boot delayed because udev likes
> to hang for 30 seconds after its execution on startup. I have a Dell Vostro
> 1500 laptop and am currently using Lenny.
>
> My rcS.d is:
>
> S01glibc.sh
> S02hostname.sh
> S02mountkernfs.sh
> S03udev
> S04hibernate
> ... others ...
>
> The "critical" part startup goes like this:
>
> [    9.437162] ACPI: PCI Interrupt 0000:00:1f.3[B] -> GSI 17 (level, low)
> -> IRQ 17
> [    9.466025] ACPI: Video Device [VID2] (multi-head: yes  rom: no  post:
> no)
> [    9.517276] input: PC Speaker as /class/input/input9
> [    9.726175] ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 21 (level, low)
> -> IRQ 21
> [    9.732487] PCI: Setting latency timer of device 0000:00:1b.0 to 64
> [    9.853371] b43-phy0: Broadcom 4311 WLAN found
> [    9.921371] phy0: Selected rate control algorithm 'pid'
> [   10.096229] Broadcom 43xx driver loaded [ Features: PMLR, Firmware-ID:
> FW13 ]
> [   10.099699] udev: renamed network interface wmaster0 to eth2
> [   10.267144] Synaptics Touchpad, model: 1, fw: 6.3, id: 0x1a0b1, caps:
> 0xa04793/0x300000
> [   10.267144] serio: Synaptics pass-through port at isa0060/serio1/input0
> [   10.305299] input: SynPS/2 Synaptics TouchPad as /class/input/input10
>
> HANGS FOR ~30s
>
> Invalidating stale software suspend images...
>
> Pressing Ctrl+C when it's hanged does make it go.
>
> Any thoughts?
>
> André
>



-- 
Yiyong Lin

Simplicity:

There's an infinite number of ways to make a simple problem seem difficult;
only a handful to make a difficult problem seem simple

    — Crenshaw's Law #1
KISS (Keep it Simple, Sydney)

    — Crenshaw's Law #2
Simplify, and add lightness

    — Race car designer George Miller (oft attributed to others)

Reply via email to