Hi.
When I'm trying to suspend to mem one machine, it wakes immediatly back with
nothing notable in dmesg:
Stopping tasks:
==========================================================================================================================================================|
Suspending console(s)
ACPI: PCI interrupt for device 0000:02:0c.0 disabled
NVRM: RmPowerManagement: 3
ACPI: PCI interrupt for device 0000:00:1d.7 disabled
ACPI: PCI interrupt for device 0000:00:1d.3 disabled
ACPI: PCI interrupt for device 0000:00:1d.2 disabled
ACPI: PCI interrupt for device 0000:00:1d.1 disabled
ACPI: PCI interrupt for device 0000:00:1d.0 disabled
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
CPU0: Intel P4/Xeon Extended MCE MSRs (12) available
Back to C!
ACPI: PCI Interrupt 0000:00:1d.0[A] -> Link [LNKA] -> GSI 11 (level, low) -> IRQ 11
PCI: Setting latency timer of device 0000:00:1d.0 to 64
usb usb2: root hub lost power or was reset
ACPI: PCI Interrupt 0000:00:1d.1[B] -> Link [LNKD] -> GSI 11 (level, low) -> IRQ 11
PCI: Setting latency timer of device 0000:00:1d.1 to 64
usb usb3: root hub lost power or was reset
ACPI: PCI Interrupt 0000:00:1d.2[C] -> Link [LNKC] -> GSI 5 (level, low) -> IRQ 5
PCI: Setting latency timer of device 0000:00:1d.2 to 64
usb usb4: root hub lost power or was reset
ACPI: PCI Interrupt 0000:00:1d.3[A] -> Link [LNKA] -> GSI 11 (level, low) -> IRQ 11
PCI: Setting latency timer of device 0000:00:1d.3 to 64
usb usb5: root hub lost power or was reset
ACPI: PCI Interrupt 0000:00:1d.7[D] -> Link [LNKH] -> GSI 10 (level, low) -> IRQ 10
PCI: Setting latency timer of device 0000:00:1d.7 to 64
PM: Writing back config space on device 0000:00:1e.0 at offset 9 (was fff0,
writing 30003000)
PCI: Setting latency timer of device 0000:00:1e.0 to 64
PM: Writing back config space on device 0000:00:1f.1 at offset 9 (was 0, writing
30100000)
PM: Writing back config space on device 0000:00:1f.1 at offset 1 (was 2800005,
writing 2880007)
NVRM: RmPowerManagement: 4
eth0: link down
eth1: link down
PM: Writing back config space on device 0000:02:0c.0 at offset 1 (was 2900105,
writing 2900101)
ACPI: PCI Interrupt 0000:02:0c.0[A] -> Link [LNKE] -> GSI 5 (level, low) -> IRQ 5
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
usbdev2.3_ep00: PM: resume from 0, parent 2-2 still 2
usb 2-2:1.0: PM: resume from 2, parent 2-2 still 2
usbdev2.3_ep81: PM: resume from 0, parent 2-2:1.0 still 2
usbdev3.3_ep00: PM: resume from 0, parent 3-2 still 2
usbhid 3-2:1.0: PM: resume from 2, parent 3-2 still 2
usbdev3.3_ep81: PM: resume from 0, parent 3-2:1.0 still 2
Restarting tasks...<6>usb 2-2: USB disconnect, address 3
done
usb 2-2: new full speed USB device using uhci_hcd and address 4
usb 2-2: configuration #1 chosen from 1 choice
usb 3-2: USB disconnect, address 3
usb 3-2: new low speed USB device using uhci_hcd and address 4
usb 3-2: configuration #1 chosen from 1 choice
input: KYE Genius USB Wheel Mouse as /class/input/input5
input: USB HID v1.00 Mouse [KYE Genius USB Wheel Mouse] on usb-0000:00:1d.1-2
hub 1-0:1.0: over-current change on port 5
hub 1-0:1.0: over-current change on port 6
hub 1-0:1.0: over-current change on port 7
hub 1-0:1.0: over-current change on port 8
Note, that this is try after removing of ohci1394 and dvb_usb_dtt200u since:
dvb_usb_dtt200u 1-3:1.0: no suspend for driver dvb_usb_dtt200u?
dvb_usb_dtt200u 1-3:1.1: no suspend for driver dvb_usb_dtt200u?
ohci1394 does not fully support suspend and resume yet
I also tried to remove completely nvidia.ko from /lib/modules to not load it and
reboot to init level 2 (no X, no net, only few processes) with the very same result.
It's nosmp nohigmem configuration with this cpu:
processor : 0
vendor_id : GenuineIntel
cpu family : 15
model : 2
model name : Intel(R) Celeron(R) CPU 2.20GHz
stepping : 7
cpu MHz : 2199.095
cache size : 128 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 2
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe cid xtpr
bogomips : 4401.41
with this hardware:
PCIs
00:00.0 Host bridge: Intel Corporation 82865G/PE/P DRAM Controller/Host-Hub
Interface (rev 02)
00:01.0 PCI bridge: Intel Corporation 82865G/PE/P PCI to AGP Controller (rev 02)
00:1d.0 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI
Controller #1 (rev 02)
00:1d.1 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI
Controller #2 (rev 02)
00:1d.2 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI
Controller #3 (rev 02)
00:1d.3 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI
Controller #4 (rev 02)
00:1d.7 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB2 EHCI
Controller (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev c2)
00:1f.0 ISA bridge: Intel Corporation 82801EB/ER (ICH5/ICH5R) LPC Interface
Bridge (rev 02)
00:1f.1 IDE interface: Intel Corporation 82801EB/ER (ICH5/ICH5R) IDE Controller
(rev 02)
00:1f.5 Multimedia audio controller: Intel Corporation 82801EB/ER (ICH5/ICH5R)
AC'97 Audio Controller (rev 02)
01:00.0 VGA compatible controller: nVidia Corporation NV28 [GeForce4 Ti 4200 AGP
8x] (rev a1)
02:05.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL-8139/8139C/8139C+ (rev 10)
02:09.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL-8139/8139C/8139C+ (rev 10)
02:0c.0 Multimedia audio controller: Creative Labs SB Audigy (rev 04)
02:0c.1 Input device controller: Creative Labs SB Audigy Game Port (rev 04)
02:0c.2 FireWire (IEEE 1394): Creative Labs SB Audigy FireWire Port (rev 04)
USBs
Bus 001 Device 006: ID 14aa:0226 AVerMedia (again) or C&E
Bus 001 Device 001: ID 0000:0000
Bus 002 Device 004: ID 046d:0920 Logitech, Inc. QuickCam Express
Bus 002 Device 001: ID 0000:0000
Bus 004 Device 001: ID 0000:0000
Bus 005 Device 001: ID 0000:0000
Bus 003 Device 004: ID 0458:000e KYE Systems Corp. (Mouse Systems) VideoCAM Web
Bus 003 Device 001: ID 0000:0000
modules currently in:
dvb_usb_dtt200u 12804 0
vfat 13184 1
fat 52764 1 vfat
sunrpc 159164 1
nvidia 4714324 32
ipv6 227296 18
ipt_MASQUERADE 3584 1
iptable_nat 6788 1
ip_nat 18348 2 ipt_MASQUERADE,iptable_nat
ip_conntrack 49260 3 ipt_MASQUERADE,iptable_nat,ip_nat
nfnetlink 7064 2 ip_nat,ip_conntrack
iptable_filter 3200 0
ip_tables 12872 2 iptable_nat,iptable_filter
x_tables 15748 3 ipt_MASQUERADE,iptable_nat,ip_tables
binfmt_misc 11528 1
ntfs 104564 2
ieee1394 95668 0
usbhid 32132 0
ide_cd 39456 0
8139too 24832 0
mii 5888 1 8139too
cdrom 37152 1 ide_cd
dvb_usb 21644 1 dvb_usb_dtt200u
dvb_core 80680 1 dvb_usb
dvb_pll 14852 1 dvb_usb
i2c_core 22160 3 nvidia,dvb_usb,dvb_pll
rtc 12212 0
on this kernel
Linux Privat 2.6.19-bygep #8 Sun Feb 4 01:12:37 CET 2007 i686 i686 i386 GNU/Linux
(-bygep is only naming, no patches or something)
I also tried to remove "external irq generators" -- net links, usb mouse...
Complete config:
http://www.fi.muni.cz/~xslaby/sklad/hwsusp-config
dmesgs:
http://www.fi.muni.cz/~xslaby/sklad/dmesg.txt
http://www.fi.muni.cz/~xslaby/sklad/dmesg1.txt
Will PM_DEBUG or ACPI_DEBUG help somehow? Or later kernel?
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
Hi,
On Sunday, 4 February 2007 14:12, Jiri Slaby wrote:
> Hi.
>
> When I'm trying to suspend to mem one machine, it wakes immediatly back with
> nothing notable in dmesg:
[--snip--]
>
> Will PM_DEBUG or ACPI_DEBUG help somehow? Or later kernel?
Later kernel might help, some important fixes have gone in since 2.6.19,
PCI quirks-related etc.
Please try 2.6.20-rc7 and if that doesn't help, try the latest -mm.
Greetings,
Rafael
--
If you don't have the time to read,
you don't have the time or the tools to write.
- Stephen King
Rafael J. Wysocki napsal(a):
> Hi,
>
> On Sunday, 4 February 2007 14:12, Jiri Slaby wrote:
>> Hi.
>>
>> When I'm trying to suspend to mem one machine, it wakes immediatly back with
>> nothing notable in dmesg:
> [--snip--]
>> Will PM_DEBUG or ACPI_DEBUG help somehow? Or later kernel?
>
> Later kernel might help, some important fixes have gone in since 2.6.19,
> PCI quirks-related etc.
>
> Please try 2.6.20-rc7 and if that doesn't help, try the latest -mm.
Yes, I'll try it next week (maybe 2.6.20 will be out) and will keep you informed.
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
On 4 February 2007, at 07:12, Jiri Slaby wrote:
>
> Back to C!
This is a bit off topic, but what does this message mean? Is it
referring to the programming language?
Also, when I swsusp my machine, why does it print "Linu" at the top
of the screen? Not "Linux," but "Linu..."
--
hackmiester (Hunter Fuller)
<badaboom> who can help me ? i'm french and i don't know irc
<Paladine> can't help you with the being french part, you are screwed
their mate
Phone
Voice: +1 251 589 6348
Fax: Call the voice number and ask.
Email
General chat: [email protected]
Large attachments: [email protected]
SPS-related stuff: [email protected]
IM
AIM: hackmiester1337
Skype: hackmiester31337
YIM: hackm1ester
Gtalk: hackmiester
MSN: [email protected]
Xfire: hackmiester
Hi.
On Mon, 2007-02-05 at 19:10 -0600, hackmiester (Hunter Fuller) wrote:
> On 4 February 2007, at 07:12, Jiri Slaby wrote:
>
> >
> > Back to C!
>
> This is a bit off topic, but what does this message mean? Is it
> referring to the programming language?
It's just saying that the lowlevel assembly stuff succeeded to the point
that we got back to compiled C code.
> Also, when I swsusp my machine, why does it print "Linu" at the top
> of the screen? Not "Linux," but "Linu..."
That's Pavel's evil plan to take over the world with a microkernel based
version of Linux - he's going to call it Linu :)
Regards,
Nigel
Rafael J. Wysocki napsal(a):
> Hi,
>
> On Sunday, 4 February 2007 14:12, Jiri Slaby wrote:
>> Hi.
>>
>> When I'm trying to suspend to mem one machine, it wakes immediatly back with
>> nothing notable in dmesg:
> [--snip--]
>> Will PM_DEBUG or ACPI_DEBUG help somehow? Or later kernel?
>
> Later kernel might help, some important fixes have gone in since 2.6.19,
> PCI quirks-related etc.
>
> Please try 2.6.20-rc7 and if that doesn't help, try the latest -mm.
2.6.20 from init 2 is no go either, -mm (-rc6-mm3) with minimal config [1]
suspends, no key was able to resume it back, only power button, but monitor
doesn't wake (actually I've this problem on another machine when X is not
running) -- how to debug both of this? Do not suspend consoles? PM_TRACE (this
won't help since it completely resumes, I guess)?
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
$ 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? Should I test 2.6.20 with minimal config?
[1]
http://www.fi.muni.cz/~xslaby/sklad/config-mm
[2]
http://www.fi.muni.cz/~xpapiez/test/dmesg-mm.txt
regards,
--
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
Jiri Slaby napsal(a):
> monitor doesn't wake (actually I've this problem on another machine when
Ah, oh. Monitor over DVI on
01:00.0 VGA compatible controller: nVidia Corporation NV28 [GeForce4 Ti 4200 AGP
8x] (rev a1) (prog-if 00 [VGA])
Subsystem: ASUSTeK Computer Inc. Unknown device 807b
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: 248 (1250ns min, 250ns max)
Interrupt: pin A routed to IRQ 11
Region 0: Memory at fd000000 (32-bit, non-prefetchable) [size=16M]
Region 1: Memory at e8000000 (32-bit, prefetchable) [size=128M]
[virtual] Expansion ROM at fe9e0000 [disabled] [size=128K]
Capabilities: [60] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [44] AGP version 3.0
Status: RQ=32 Iso- ArqSz=0 Cal=3 SBA+ ITACoh- GART64- HTrans-
64bit- FW+ AGP3+ Rate=x4,x8
Command: RQ=32 ArqSz=2 Cal=0 SBA+ AGP+ GART64- 64bit- FW- Rate=x8
00: de 10 81 02 07 00 b0 02 a1 00 00 03 00 f8 00 00
10: 00 00 00 fd 08 00 00 e8 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 43 10 7b 80
30: 00 00 00 00 60 00 00 00 00 00 00 00 0b 01 05 01
40: 43 10 7b 80 02 00 30 00 1b 0e 00 1f 02 43 00 1f
50: 01 00 00 00 01 00 00 00 ce d6 23 00 0f 00 00 00
60: 01 44 02 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
regards,
--
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
On Tuesday, 6 February 2007 12:18, Jiri Slaby wrote:
> Rafael J. Wysocki napsal(a):
> > Hi,
> >
> > On Sunday, 4 February 2007 14:12, Jiri Slaby wrote:
> >> Hi.
> >>
> >> When I'm trying to suspend to mem one machine, it wakes immediatly back with
> >> nothing notable in dmesg:
> > [--snip--]
> >> Will PM_DEBUG or ACPI_DEBUG help somehow? Or later kernel?
> >
> > Later kernel might help, some important fixes have gone in since 2.6.19,
> > PCI quirks-related etc.
> >
> > Please try 2.6.20-rc7 and if that doesn't help, try the latest -mm.
>
> 2.6.20 from init 2 is no go either, -mm (-rc6-mm3) with minimal config [1]
> suspends, no key was able to resume it back, only power button, but monitor
> doesn't wake (actually I've this problem on another machine when X is not
> running) -- how to debug both of this? Do not suspend consoles? PM_TRACE (this
> won't help since it completely resumes, I guess)?
First, you can try s2ram if you haven't done it already (http://en.opensuse.org/s2ram).
It may help to get your video back after the resume.
If you have a COM port, it is also possible to use a serial console throughout the
suspend/resume cycle.
> 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. ;-)
> Should I test 2.6.20 with minimal config?
I think it's better to try the -mm with the minimal config.
Greetings,
Rafael
--
If you don't have the time to read,
you don't have the time or the tools to write.
- Stephen King
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
For acpi issues, please enter bug into bugzilla.kernel.org with dmesg,
acpidump output .
On 2/7/07, Jiri Slaby <[email protected]> wrote:
> 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 [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
Luming Yu napsal(a):
> For acpi issues, please enter bug into bugzilla.kernel.org with dmesg,
> acpidump output .
Ok:
http://bugzilla.kernel.org/show_bug.cgi?id=7958
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
Rafael J. Wysocki napsal(a):
> On Tuesday, 6 February 2007 12:18, Jiri Slaby wrote:
>> running) -- how to debug both of this? Do not suspend consoles? PM_TRACE (this
>> won't help since it completely resumes, I guess)?
>
> First, you can try s2ram if you haven't done it already (http://en.opensuse.org/s2ram).
> It may help to get your video back after the resume.
Yes. s2ram -a 1 with minimal -mm does the job perfectly. Now, I'm going to
involve the rest of modules world.
> If you have a COM port, it is also possible to use a serial console throughout the
> suspend/resume cycle.
Only monitor didn't go up -- dmesg was able to be grabbed without monitor :).
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