2.6.28.[5,6] _GTF unexpected object type 0x1

2.6.28.[5,6] _GTF unexpected object type 0x1

[Heinz Diehl]

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?

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

[Robert Hancock]

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.