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: <45C9C0B6.9090704@gmail.com>
Date:	Wed, 07 Feb 2007 13:06:14 +0100
From:	Jiri Slaby <jirislaby@...il.com>
To:	"Rafael J. Wysocki" <rjw@...k.pl>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Pavel Machek <pavel@...e.cz>, linux-acpi@...r.kernel.org
Subject: Re: hwsusp defunct

Cc: linux-acpi
not-cc: linux-pm

Rafael J. Wysocki napsal(a):
> On Tuesday, 6 February 2007 12:18, Jiri Slaby wrote:
>> This is blindly written dmesg after resume. See it whole at [2]:
>> Suspending device 0.0
>> ACPI Exception (exoparg2-0442): AE_AML_PACKAGE_LIMIT, Index (000000007) is beyon
>> d end of object [20070126]
>> ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.PCI0.IDE0.GTM_]
>> (Node dfe64fcc), AE_AML_PACKAGE_LIMIT
>> ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.PCI0.IDE0.CHN0._
>> GTM] (Node dfe649f0), AE_AML_PACKAGE_LIMIT
>> ...
>> hda: selected mode 0x45
>> ACPI Error (dsopcode-0481): Attempt to CreateField of length zero [20070126]
>> ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.PCI0.IDE0.RATA]
>> (Node dfe64ec8), AE_AML_OPERAND_VALUE
>> ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.PCI0.IDE0.CHN0.D
>> RV1._GTF] (Node dfe64964), AE_AML_OPERAND_VALUE
>> do_drive_get_GTF: Run _GTF error: status = 0x3006
> 
> This looks like an ACPI-vs-IDE problem.  You can try to use libata drivers instead
> of the "old IDE" ones.
> 
>> $ ls -l /sys/block/hda/device
>> lrwxrwxrwx 1 root root 0 úno  6 12:14 /sys/block/hda/device -> 
>> ../../devices/pci0000:00/0000:00:1f.1/ide0/0.0
>> $ ls -l /sys/block/hda/device/driver
>> lrwxrwxrwx 1 root root 0 úno  6 12:15 /sys/block/hda/device/driver -> 
>> ../../../../../bus/ide/drivers/ide-disk
>> $ ls -l /sys/block/hda/device/driver/0.0
>> lrwxrwxrwx 1 root root 0 úno  6 12:16 /sys/block/hda/device/driver/0.0 -> 
>> ../../../../devices/pci0000:00/0000:00:1f.1/ide0/0.0
>> # lspci -vvvxxs 0000:00:1f.1
>> 00:1f.1 IDE interface: Intel Corporation 82801EB/ER (ICH5/ICH5R) IDE Controller 
>> (rev 02) (prog-if 8a [Master SecP PriP])
>>          Subsystem: ASUSTeK Computer Inc. P5P800-MX Mainboard
>>          Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
>> Stepping- SERR- FastB2B-
>>          Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
>> <TAbort- <MAbort- >SERR- <PERR-
>>          Latency: 0
>>          Interrupt: pin A routed to IRQ 5
>>          Region 0: I/O ports at 01f0 [size=8]
>>          Region 1: I/O ports at 03f4 [size=1]
>>          Region 2: I/O ports at 0170 [size=8]
>>          Region 3: I/O ports at 0374 [size=1]
>>          Region 4: I/O ports at fc00 [size=16]
>>          Region 5: Memory at 30100000 (32-bit, non-prefetchable) [size=1K]
>> 00: 86 80 db 24 07 00 80 02 02 8a 01 01 00 00 00 00
>> 10: 01 00 00 00 01 00 00 00 01 00 00 00 01 00 00 00
>> 20: 01 fc 00 00 00 00 10 30 00 00 00 00 43 10 a6 80
>> 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 01 00 00
>>
>> Do you want acpidump?
> 
> I'm not an ACPI expert, it won't tell me a lot, but perhaps you should add
> linux-acpi to the Cc list. ;-)
[...]
 > [1]
 >   http://www.fi.muni.cz/~xslaby/sklad/config-mm
 > [2]
 >   http://www.fi.muni.cz/~xpapiez/test/dmesg-mm.txt

Ok, acpi folks, any suggests?

thanks,
-- 
http://www.fi.muni.cz/~xslaby/            Jiri Slaby
faculty of informatics, masaryk university, brno, cz
e-mail: jirislaby gmail com, gpg pubkey fingerprint:
B674 9967 0407 CE62 ACC8  22A0 32CC 55C3 39D4 7A7E
-
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ