mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "Torsten Kaiser" <just.for.lkml@googlemail.com>
Cc: "Jeff Garzik" <jeff@garzik.org>,
	linux-ide@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	linux-scsi@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: [git patches] libata update
Date: Sun, 14 Oct 2007 13:21:57 +0100	[thread overview]
Message-ID: <20071014132157.5646ac17@the-village.bc.nu> (raw)
In-Reply-To: <64bb37e0710140335g648a86ebmebdf32a6068abcf8@mail.gmail.com>

> ACPI Exception (exoparg2-0442): AE_AML_PACKAGE_LIMIT, Index
> (0FFFFFFFF) is beyond end of object [20070126]
> ACPI Error (psparse-0537): Method parse/execution failed
> [\_SB_.PCI0.IDE0.GTM_] (Node ffff810100318a20), AE_AML_PACKAGE_LIMIT
> ACPI Error (psparse-0537): Method parse/execution failed
> [\_SB_.PCI0.IDE0.CHN0._GTM] (Node ffff8101003187c0),
> AE_AML_PACKAGE_LIMIT
> ata9: ACPI get timing mode failed (AE 0x300d)

Looks like an ACPI BIOS problem. In that situation we'll just give up on
using ACPI information

Not much else we can do as Nvidia don't document how to do a reliable
40/80 wire test and just told us to use the BIOS.

  reply	other threads:[~2007-10-14 12:18 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-12 19:40 Jeff Garzik
2007-10-13  0:06 ` Luben Tuikov
2007-10-13  1:42 ` Bartlomiej Zolnierkiewicz
2007-10-15 22:31   ` Jeff Garzik
2007-10-13  7:05 ` Andrey Borzenkov
2007-10-13 10:55   ` Jeff Garzik
2007-10-26  3:02     ` Tejun Heo
2007-10-14 10:35 ` Torsten Kaiser
2007-10-14 12:21   ` Alan Cox [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-09-24 16:29 Jeff Garzik
2006-07-06  3:07 Jeff Garzik
2006-06-27  1:24 Jeff Garzik
2006-06-28  1:23 ` Linus Torvalds
2006-06-28  1:34   ` Jeff Garzik
2005-09-05  9:33 Jeff Garzik

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=20071014132157.5646ac17@the-village.bc.nu \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=jeff@garzik.org \
    --cc=just.for.lkml@googlemail.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®