Re: 2.6.0-test4 - lost ACPI

[Andrew Morton]

Tomasz Torcz <zdzichu@xxxxxx> wrote:
>
> On Sat, Aug 23, 2003 at 02:55:45PM -0700, Andrew Morton wrote:
> > Tomasz Torcz <zdzichu@xxxxxx> wrote:
> > 
> > >  ACPI disabled because your bios is from 00 and too old
> > >  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> > 
> > Add "acpi=force" to your kernel boot command line and everything should work
> > as before.
> 
> It does not work. It halts in beetween ps/2 mouse init and serio init.
> Adding "acpi=force pci=noacpi" solves that.
> 

OK.  Please send a full report to linux-acpi@xxxxxxxxxx  Here is Len's
how-to-report-ACPI problems recipe:


 Regarding how to field these in general...
 Bugzilla would be really helpful, because we've got multiple bugs and
 multiple people working on them and bugzilla is better than e-mail at
 keeping the relevant bits together.  bugzilla with component=ACPI and
 owner len.brown@xxxxxxxxx or andrew.grover@xxxxxxxxx should do the
 trick.

 The dmesg output of the failing case is really helpful,
 As is the output of acpidmp to examine the ACPI tables on the system.
 (Red Hat includes both of these in their severn beta1, acpidmp is also
 in pmtools on intel's ACPI web page)
 dmidecode output is useful to identify the BIOS version.

 Of course the 1st thing to check with ACPI failures is that the BIOS
 version shown by dmidmp is the latest provided by the vendor...  Plus,
 if we determine the BIOS is toast, DMI provides what we need to add the
 system to the DMI or acpi blacklists.

 We're seeting the most problems on VIA chip-sets with no IO-APIC.
 The one below is unusual because it is a 2-way system with 3 IO-APICs.

 The latest code in linus' tree includes ACPICA 20030813, which is
 slightly newer than the one below, it might be a good idea to try that
 with CONFIG_ACPI_DEBUG.  Note that it will spit out the DMI info upon
 the mount root failure automatically.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/