boot: "Error attaching device data"
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
In /var/log/messages I get the following error at startup.
I'm not sure for how long I get this error, but I think it's since using hardy 64-bit on my new system (Intel E8400, ...)
PS: it's probably this bug: http://<email address hidden>
May 12 19:22:07 tux kernel: [ 22.165175] ACPI: Core revision 20070126
May 12 19:22:07 tux kernel: [ 22.165204] ACPI: Looking for DSDT in initramfs... error, file /DSDT.aml not found.
May 12 19:22:07 tux kernel: [ 22.207853] Using local APIC timer interrupts.
May 12 19:22:07 tux kernel: [ 22.241157] Detected 20.833 MHz APIC timer.
May 12 19:22:07 tux kernel: [ 22.241216] SMP alternatives: switching to SMP code
May 12 19:22:07 tux kernel: [ 22.241698] Booting processor 1/2 APIC 0x1
May 12 19:22:07 tux kernel: [ 22.252256] Initializing CPU#1
May 12 19:22:07 tux kernel: [ 22.329083] Calibrating delay using timer specific routine.. 5999.94 BogoMIPS (lpj=11999895)
May 12 19:22:07 tux kernel: [ 22.329087] CPU: L1 I cache: 32K, L1 D cache: 32K
May 12 19:22:07 tux kernel: [ 22.329088] CPU: L2 cache: 6144K
May 12 19:22:07 tux kernel: [ 22.329089] CPU 1/1 -> Node 0
May 12 19:22:07 tux kernel: [ 22.329090] CPU: Physical Processor ID: 0
May 12 19:22:07 tux kernel: [ 22.329091] CPU: Processor Core ID: 1
May 12 19:22:07 tux kernel: [ 22.329095] CPU1: Thermal monitoring enabled (TM1)
May 12 19:22:07 tux kernel: [ 22.329682] Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz stepping 06
May 12 19:22:07 tux kernel: [ 22.329730] checking TSC synchronization [CPU#0 -> CPU#1]: passed.
May 12 19:22:07 tux kernel: [ 22.349728] Brought up 2 CPUs
May 12 19:22:07 tux kernel: [ 22.349975] net_namespace: 120 bytes
May 12 19:22:07 tux kernel: [ 22.350241] Time: 19:21:48 Date: 05/12/08
May 12 19:22:07 tux kernel: [ 22.350257] NET: Registered protocol family 16
May 12 19:22:07 tux kernel: [ 22.350368] ACPI: bus type pci registered
May 12 19:22:07 tux kernel: [ 22.350411] PCI: Using configuration type 1
May 12 19:22:07 tux kernel: [ 22.356380] ACPI: Interpreter enabled
May 12 19:22:07 tux kernel: [ 22.356381] ACPI: (supports S0 S1 S3 S4 S5)
May 12 19:22:07 tux kernel: [ 22.356390] ACPI: Using IOAPIC for interrupt routing
May 12 19:22:07 tux kernel: [ 22.356512] Error attaching device data
May 12 19:22:07 tux kernel: [ 22.356537] Error attaching device data
May 12 19:22:07 tux kernel: [ 22.356561] Error attaching device data
May 12 19:22:07 tux kernel: [ 22.356587] Error attaching device data
May 12 19:22:07 tux kernel: [ 22.361729] ACPI: PCI Root Bridge [PCI0] (0000:00)
May 12 19:22:07 tux kernel: [ 22.363948] PCI: Transparent bridge - 0000:00:10.0
May 12 19:22:07 tux kernel: [ 22.372743] ACPI: PCI Interrupt Link [LNKA] (IRQs 16 17 18 19) *11
May 12 19:22:07 tux kernel: [ 22.372879] ACPI: PCI Interrupt Link [LNKB] (IRQs 16 17 18 19) *5
May 12 19:22:07 tux kernel: [ 22.373015] ACPI: PCI Interrupt Link [LNKC] (IRQs 16 17 18 19) *0, disabled.
May 12 19:22:07 tux kernel: [ 22.373152] ACPI: PCI Interrupt Link [LNKD] (IRQs 16 17 18 19) *10
May 12 19:22:07 tux kernel: [ 22.373287] ACPI: PCI Interrupt Link [LNEA] (IRQs 16 17 18 19) *10
May 12 19:22:07 tux kernel: [ 22.373421] ACPI: PCI Interrupt Link [LNEB] (IRQs 16 17 18 19) *0, disabled.
May 12 19:22:07 tux kernel: [ 22.373556] ACPI: PCI Interrupt Link [LNEC] (IRQs 16 17 18 19) *10
May 12 19:22:07 tux kernel: [ 22.373691] ACPI: PCI Interrupt Link [LNED] (IRQs 16 17 18 19) *0, disabled.
May 12 19:22:07 tux kernel: [ 22.373826] ACPI: PCI Interrupt Link [LUB0] (IRQs 20 21 22 23) *5
May 12 19:22:07 tux kernel: [ 22.373961] ACPI: PCI Interrupt Link [LUB2] (IRQs 20 21 22 23) *7
May 12 19:22:07 tux kernel: [ 22.374101] ACPI: PCI Interrupt Link [LMAC] (IRQs 20 21 22 23) *10
May 12 19:22:07 tux kernel: [ 22.374235] ACPI: PCI Interrupt Link [LAZA] (IRQs 20 21 22 23) *5
May 12 19:22:07 tux kernel: [ 22.374377] ACPI: PCI Interrupt Link [LACI] (IRQs 20 21 22 23) *0, disabled.
May 12 19:22:07 tux kernel: [ 22.374514] ACPI: PCI Interrupt Link [LMC9] (IRQs 20 21 22 23) *0, disabled.
May 12 19:22:07 tux kernel: [ 22.374649] ACPI: PCI Interrupt Link [LSMB] (IRQs 20 21 22 23) *11
May 12 19:22:07 tux kernel: [ 22.374784] ACPI: PCI Interrupt Link [LPMU] (IRQs 20 21 22 23) *0, disabled.
May 12 19:22:07 tux kernel: [ 22.374919] ACPI: PCI Interrupt Link [LSA0] (IRQs 20 21 22 23) *10
May 12 19:22:07 tux kernel: [ 22.375058] ACPI: PCI Interrupt Link [LSA1] (IRQs 20 21 22 23) *11
May 12 19:22:07 tux kernel: [ 22.375222] ACPI: PCI Interrupt Link [LATA] (IRQs 20 21 22 23) *0, disabled.
May 12 19:22:07 tux kernel: [ 22.375299] Linux Plug and Play Support v0.97 (c) Adam Belay
May 12 19:22:07 tux kernel: [ 22.375316] pnp: PnP ACPI init
May 12 19:22:07 tux kernel: [ 22.375320] ACPI: bus type pnp registered
May 12 19:22:07 tux kernel: [ 22.377813] pnp: PnP ACPI: found 11 devices
May 12 19:22:07 tux kernel: [ 22.377815] ACPI: ACPI bus type pnp unregistered
description: | updated |
Hi,
I can confirm this bug on my LG E500 laptop. I use a Intel core 2 duo T8100 @2.1GHz. ACPI is not working correctly. To be able to boot I needed to fix an error in the DSDT table and use the boot option acpi_no_auto_ssdt.
When I boot I still get this error messages in the kernel ring buffer with dmesg:
[ 49.521990] Time: 17:12:52 Date: 06/22/08
[ 49.522055] NET: Registered protocol family 16
[ 49.522275] ACPI: bus type pci registered
[ 49.522384] PCI: Using configuration type 1
[ 49.524173] ACPI: EC: EC description table is found, configuring boot EC
[ 49.525723] ACPI: Interpreter enabled
[ 49.525764] ACPI: (supports S0 S1 S3 S4 S5)
[ 49.525977] ACPI: Using IOAPIC for interrupt routing
[ 49.526188] Error attaching device data
[ 49.526269] Error attaching device data
[ 49.527424] ACPI: EC: non-query interrupt received, switching to interrupt mode
[ 49.530611] ACPI: EC: GPE = 0x17, I/O: command/status = 0x66, data = 0x62
[ 49.530653] ACPI: EC: driver started in poll mode
[ 49.530826] ACPI: PCI Root Bridge [PCI0] (0000:00)
[ 49.531598] ACPI: EC: non-query interrupt received, switching to interrupt mode
The complete power management and the thermal management are not working correctly. I can confirm this behaviour for both, i386 and am64 distributions.