linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Tomasz Torcz <zdzichu@irc.pl>
Cc: linux-kernel@vger.kernel.org, linux-acpi@intel.com
Subject: Re: 2.6.0-test4 - lost ACPI
Date: Sat, 23 Aug 2003 15:24:37 -0700	[thread overview]
Message-ID: <20030823152437.59ed9c3e.akpm@osdl.org> (raw)
In-Reply-To: <20030823220438.GB1155@irc.pl>

Tomasz Torcz <zdzichu@irc.pl> wrote:
>
> On Sat, Aug 23, 2003 at 02:55:45PM -0700, Andrew Morton wrote:
> > Tomasz Torcz <zdzichu@irc.pl> 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@intel.com.  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@intel.com or andrew.grover@intel.com 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.


  reply	other threads:[~2003-08-23 22:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-23 10:52 Tomasz Torcz
2003-08-23 21:55 ` Andrew Morton
2003-08-23 22:04   ` Tomasz Torcz
2003-08-23 22:24     ` Andrew Morton [this message]
2003-08-24 21:27     ` Wes Janzen
2003-08-23 16:47 Brown, Len
2003-08-23 16:59 ` Tomasz Torcz
2003-08-23 20:58 Brown, Len
2003-08-23 22:31 Brown, Len
2003-08-24  2:07 Felipe Alfaro Solana

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030823152437.59ed9c3e.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=linux-acpi@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zdzichu@irc.pl \
    --subject='Re: 2.6.0-test4 - lost ACPI' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).