Skip to contentSkip to conversation

Kernel 2.5.55 failed to boot with ACPI support

DISCUSSION Alessandro Suardi 2 participants 2 messages Jan 12, 2003 1 message not in the archive

lore
Share & tools
lore
#0 lore raw
Quoted 9 lines · Andrew Grover
Quoted 7 lines

From: Ole J. Hagen [mailto:[email protected]] I just wanted to inform that kernel-2.5.55 failes to boot when ACPI support is
compiled in the kernel.

I have following configuration; Dell Optiplex GX-240, Pentium 4 (1.5 GHz), ATI RAGE 128.

How exactly does it fail?

My brand new Dell Latitude C640 oopses on boot in 2.5.56 if I
have CPU_FREQ config'd in. ACPI without CPU_FREQ is okay - well, it screws my framebuffer screen (what 2.4.21-pre3 doesn't) when the ACPI code does its bootup printk's, but after that the screen recovers.

Another thing is that /proc/acpi/fan is empty despite my setting
of CONFIG_ACPI_FAN=y.

Oh, and one more - /proc/acpi/battery/BAT0/state claims

charging state: unknown

as well as

present rate:       0 mA
remaining capacity: 0 mAh
present voltage:    0 mV

and the info file, when cat'd, prints a few times

dsobject-0188: *** Warning: Buffer created with zero length in AML

Back on topic, if you're interested I can rebuild my 2.5.56 with
CPU_FREQ and write down the backtrace of the oops.

--alessandro

#2 lore raw
In reply to a message not in the archive
Quoted 18 lines · Alessandro Suardi
Quoted 9 lines · Andrew Grover
Quoted 7 lines

From: Ole J. Hagen [mailto:[email protected]] I just wanted to inform that kernel-2.5.55 failes to boot when ACPI support is
compiled in the kernel.

I have following configuration; Dell Optiplex GX-240, Pentium 4 (1.5 GHz), ATI RAGE 128.

How exactly does it fail?

My brand new Dell Latitude C640 oopses on boot in 2.5.56 if I
have CPU_FREQ config'd in. ACPI without CPU_FREQ is okay - well, it screws my framebuffer screen (what 2.4.21-pre3 doesn't) when the ACPI code does its bootup printk's, but after that the screen recovers.

Quoted 4 lines

...

Back on topic, if you're interested I can rebuild my 2.5.56 with
CPU_FREQ and write down the backtrace of the oops.

Would be great if you could do that - and tell what oops it is (NULL pointer dereference etc.), in case you still see that on your screen.

Dominik