From: Robert Hancock <hancockrwd@gmail.com>
To: Heinz Diehl <htd@fancy-poultry.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.28.[5,6] _GTF unexpected object type 0x1
Date: Wed, 18 Feb 2009 21:22:05 -0600 [thread overview]
Message-ID: <499CD05D.2000505@gmail.com> (raw)
In-Reply-To: <20090218132835.GA7253@fancy-poultry.org>
Heinz Diehl wrote:
> Hi,
>
> did switch to 2.6.28.6 from 2.6.25 today on my Lenovo 3000 N200 Laptop,
> and noticed this error while booting (which wasn't there with 2.6.25):
>
> [....]
> <6>ata3: SATA max UDMA/133 abar m2048@0xfc504000 port 0xfc504200 irq 507
> <6>ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> <4>ACPI Warning (nspredef-0852): \_SB_.PCI0.SATA.PRT0._GTF: Return type mismatch - found Integer, expected Buffer [20080926]
> <4>ata1.00: _GTF unexpected object type 0x1
> <6>ata1.00: ATA-7: WDC WD1600BEVS-08RST2, 08.01G08, max UDMA/133
> <6>ata1.00: 312581808 sectors, multi 16: LBA48 NCQ (depth 31/32)
> <4>ata1.00: _GTF unexpected object type 0x1
> <6>ata1.00: configured for UDMA/133
> [....]
>
> So far, all seems to work properly, but I haven't used the machine any
> longer yet.
>
> Is this a serial issue which I have to worry about, and what can I do to avoid it?
It means your BIOS returns an incorrect object from the ACPI _GTF method
which is used to figure out what ATA commands should be used to resume
the hard drive properly. In this case the kernel just doesn't send such
BIOS-provided commands. Usually these aren't necessary as the kernel
knows how to re-initialize the drive itself, so it's likely not a
serious problem.
prev parent reply other threads:[~2009-02-19 3:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-18 13:28 2.6.28.[5,6] _GTF unexpected object type 0x1 Heinz Diehl
2009-02-19 3:22 ` Robert Hancock [this message]
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=499CD05D.2000505@gmail.com \
--to=hancockrwd@gmail.com \
--cc=htd@fancy-poultry.org \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.