linux-kernel - Re: 2.6.28.[5,6] _GTF unexpected object type 0x1

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <499CD05D.2000505@gmail.com>
Date:	Wed, 18 Feb 2009 21:22:05 -0600
From:	Robert Hancock <hancockrwd@...il.com>
To:	Heinz Diehl <htd@...cy-poultry.org>
CC:	linux-kernel@...r.kernel.org
Subject: Re: 2.6.28.[5,6] _GTF unexpected object type 0x1

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@...c504000 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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/