I didn't get version 2.6.20-rc6 to compile with selinux. well the last working version for me is 2.6.20-rc5. I use 2.6.20-rc6-mm3 #2 Wed Jan 31 09:04:12 CET 2007 i686 Intel(R) Celeron(R) CPU 2.53GHz GenuineIntel GNU/Linux On ASUS P5LD2-WM ( Intel 945g + ich7 ) After boot i get flowing error: PCI: Setting latency timer of device 0000:00:1f.1 to 64 ata1: PATA max UDMA/133 cmd 0x1F0 ctl 0x3F6 bmdma 0xFFA0 irq 14 ata2: PATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0xFFA8 irq 15 scsi0 : ata_piix ACPI Error (dsopcode-0481): Attempt to CreateField of length zero [20070126] ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.PCI0.IDE0.RATA] (Node c18da888), AE_AML_OPERAND_VALUE ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.PCI0.IDE0.CHN0.DRV1._GTF] (Node c18daa68), AE_AML_OPERAND_VALUE ata1.01: ATAPI, max UDMA/33 ACPI Error (dsopcode-0481): Attempt to CreateField of length zero [20070126] ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.PCI0.IDE0.RATA] (Node c18da888), AE_AML_OPERAND_VALUE ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.PCI0.IDE0.CHN0.DRV1._GTF] (Node c18daa68), AE_AML_OPERAND_VALUE ata1.01: configured for UDMA/33 scsi1 : ata_piix
Created attachment 10236 [details] dsdt
Created attachment 10237 [details] dmesg
Created attachment 10238 [details] lspci
Created attachment 10241 [details] dmesg 2.6.20-rc7 kernel 2.6.20-rc7 working for me without error.
Do you get the same warning if you apply the latest ACPI patch to latest Linux git tree (ie. exclude the rest of -mm?) The latest ACPI patch is available here: http://ftp.kernel.org/pub/linux/kernel/people/lenb/acpi/patches/test/2.6.20/
Alternatively, if you are working with the -mm tree, consider reverting the two patches outside the git-acpi.patch that touch _GTF: git-libata-all.patch ide-ide-acpi-support.patch:adapter
I don't get this warning with latest git 2.6.20-rc7-dirty + acpi-test-20070126-2.6.20-rc6 patch.
Thanks for confirming that the latest ACPI patch isn't (by itself) causing the issue. Can you isolate the problem to one of these two patches? http://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.20- rc6/2.6.20-rc6-mm3/broken-out/git-libata-all.patch http://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.20- rc6/2.6.20-rc6-mm3/broken-out/ide-ide-acpi-support.patch
i forgot to say: i don't use drivers/ide/* , i use libata for my pata and sata interfaces. It should not be ide-ide-acpi-support.patch .. but i will test it anyway.
From examining the AML, the failure of method RATA and its parent _GTF (Get Task File) can happen if the device _STM method has not been called first to initialize the data structures. ACPI spec states "_GTF must be called after calling _STM". Although ambiguous, it means that _GTF can only be called after _STM has been called.
For Len. I confirm, the git-libata-all.patch is broken for me.
*** Bug 7958 has been marked as a duplicate of this bug. ***
> ACPI spec states "_GTF must be called after calling _STM". Although > ambiguous, it means that _GTF can only be called after _STM has been called. Sorry for reading that one so late... I also stumbled over this. It's easy to reproduce with acpiexec tools calling _STM and _GTM in wrong order. Tejun might know more about that.
Another error message, but the same bug: https://bugzilla.novell.com/show_bug.cgi?id=216853
This issue is still or again present on 2.6.21-rc3
this goes away with libata.noacpi=1?
*** Bug 8046 has been marked as a duplicate of this bug. ***
*** Bug 8095 has been marked as a duplicate of this bug. ***
> this goes away with libata.noacpi=1? yes it goes away.
For me too, ACPI errors goes away with libata.noacpi=1 kernel parameter.
Created attachment 10663 [details] kernel log from 2.6.21-rc3-git4 patch Always acpi errors related libata acpi (pata_via for me).
Created attachment 10664 [details] kernel log from 2.6.21-rc3-git4 patch with libata.noacpi=1 No acpi errors related to libata acpi (pata_via for me) with the boot kernel parameter libata.noacpi=1 .
Created attachment 10667 [details] quick and dirty libata PATA acpi fix This patch will prevent execution of GTF on PATA devices. Longer term we should implement ACPI support for PATA devices in libata.
Would you mind giving this patch a test? I do not have a machine which can duplicate the problem. for now (2.6.21) I was thinking we should just not allow GTF for PATA devices, since to implement ACPI support for PATA would require more extensive changes and probably should live in -mm for a while first.
Created attachment 10668 [details] quick and dirty libata PATA acpi fix This patch will prevent execution of GTF on PATA devices
patch in comment #25 applied to acpi-test
Thank you. This patch working for me.
Works for me too. Thank you. 2.6.21-rc3-git6 patch successfully tested.