Problem with resuming ATI SATA on HPC nx6325

public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed

* Problem with resuming ATI SATA on HPC nx6325
@ 2006-09-04 11:32 Rafael J. Wysocki
  2006-09-05  6:24 ` Pavel Machek
  0 siblings, 1 reply; 21+ messages in thread
From: Rafael J. Wysocki @ 2006-09-04 11:32 UTC (permalink / raw)
  To: Linux ACPI; +Cc: Pavel Machek, Alan Cox

Hi,

I've just installed SUSE 10.1 on a HPC 6325 notebook (x86_64, dual_core) with
an ATI chipset.  It generally works just fine (well, except for some minor
glitches), but I'm having problems with suspending it which seem to be ACPI
related.

Namely, on the 2.6.18-rc5-mm1 kernel the hard drive is not accessible after
a resume of device drivers (eg. in the resume-during-suspend phase of swsusp).
On 2.6.18-rc5 swsusp works with the following drivers loaded:

cpufreq_ondemand
powernow_k8
freq_table
af_packet
ip6t_REJECT
xt_tcpudp
ipt_REJECT
xt_state
iptable_filter
ip_conntrack
nfnetlink
ip_tables
ip6table_filter
ip6_tables
x_tables
ipv6
ext3
jbd
fan
thermal
processor
sg
atiixp
sata_sil
libata
ide_disk
ide_core

but if ohci_hcd and ehci_hcd are loaded additionally, the SATA thing doesn't
resume properly (if only one of ehci_hcd or ohci_hcd is loaded, it works).

The SATA controller is:
00:12.0 IDE interface: ATI Technologies Inc ATI 4379 Serial ATA Controller (rev 80)

If you need any additional information, please let me know.

Greetings,
Rafael

-- 
You never change things by fighting the existing reality.
		R. Buckminster Fuller

-- 
VGER BF report: U 0.5

^ permalink raw reply	[flat|nested] 21+ messages in thread

* Re: Problem with resuming ATI SATA on HPC nx6325
  2006-09-04 11:32 Problem with resuming ATI SATA on HPC nx6325 Rafael J. Wysocki
@ 2006-09-05  6:24 ` Pavel Machek
  2006-09-05 11:38   ` Rafael J. Wysocki
  0 siblings, 1 reply; 21+ messages in thread
From: Pavel Machek @ 2006-09-05  6:24 UTC (permalink / raw)
  To: Rafael J. Wysocki; +Cc: Linux ACPI, Alan Cox

Hi!

> I've just installed SUSE 10.1 on a HPC 6325 notebook (x86_64, dual_core) with
> an ATI chipset.  It generally works just fine (well, except for some minor
> glitches), but I'm having problems with suspending it which seem to be ACPI
> related.
> 
> Namely, on the 2.6.18-rc5-mm1 kernel the hard drive is not accessible after
> a resume of device drivers (eg. in the resume-during-suspend phase of swsusp).
> On 2.6.18-rc5 swsusp works with the following drivers loaded:
> 
> cpufreq_ondemand
> powernow_k8
> freq_table
> af_packet
> ip6t_REJECT
> xt_tcpudp
> ipt_REJECT
> xt_state
> iptable_filter
> ip_conntrack
> nfnetlink
> ip_tables
> ip6table_filter
> ip6_tables
> x_tables
> ipv6
> ext3
> jbd
> fan
> thermal
> processor
> sg
> atiixp
> sata_sil
> libata
> ide_disk
> ide_core
> 
> but if ohci_hcd and ehci_hcd are loaded additionally, the SATA thing doesn't
> resume properly (if only one of ehci_hcd or ohci_hcd is loaded, it works).

So situation is:

2.6.18-rc5: works in any config

2.6.18-rc5-mm1: if ohci+ehci+sata are loaded, SATA breaks during
resume

, right? How does it breaks? Are interrupts shared between the two?

									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

^ permalink raw reply	[flat|nested] 21+ messages in thread

* Re: Problem with resuming ATI SATA on HPC nx6325
  2006-09-05  6:24 ` Pavel Machek
@ 2006-09-05 11:38   ` Rafael J. Wysocki
  2006-09-06 10:42     ` Pavel Machek
  0 siblings, 1 reply; 21+ messages in thread
From: Rafael J. Wysocki @ 2006-09-05 11:38 UTC (permalink / raw)
  To: Pavel Machek; +Cc: Linux ACPI, Alan Cox

[-- Attachment #1: Type: text/plain, Size: 2748 bytes --]

Hi,

On Tuesday, 5 September 2006 08:24, Pavel Machek wrote:

]--snip--[
> 
> So situation is:
> 
> 2.6.18-rc5: works in any config

No.  It works with init=/bin/bash plus some additional modules loaded
(see below).
 
> 2.6.18-rc5-mm1: if ohci+ehci+sata are loaded, SATA breaks during
> resume

2.6.18-rc5-mm1 also works with init=/bin/bash plus some additional modules
loaded, but only if sata_sil is directly compiled in.

I've done some more testing on 2.6.18-rc6 with sata_sil and libata compiled in
and the results are the following:

1) swsusp works with init=/bin/bash, in which case the following modules are
loaded (from the initrd)

ext3
jbd
fan
thermal
processor
atiixp
ide_disk
ide_core
sg

2) it also works with some combinations of additional modules loaded, but
generally the following modules break either the resume-during-suspend stage
of the final resume:

bcm43xx
powernow_k8
sdhci
snd_hda_intel
tg3
yenta_socket

in some combinations with the other modules or by themselves.  For example,
snd_had_intel and powernow_k8 always break the resume-during-suspend phase.
tg3 also breaks it if ehci_hcd and ohci_hcd are loaded and the network interface
is up.  sdhci breaks the resume-during-suspend phase if it is loaded along with
ohci1394 etc.

Now, the output of /proc/interrupts with everything loaded is

           CPU0       CPU1       
  0:     511683          0  local-APIC-edge  timer
  1:       6164          0    IO-APIC-edge  i8042
  8:          0          0    IO-APIC-edge  rtc
 12:        148          0    IO-APIC-edge  i8042
 14:      18053          0    IO-APIC-edge  ide0
169:        140          0   IO-APIC-level  acpi
177:          4          0   IO-APIC-level  yenta, ohci1394, sdhci:slot0
217:      48306          0   IO-APIC-level  libata, HDA Intel
225:      22528          0   IO-APIC-level  ehci_hcd:usb1, ohci_hcd:usb2, ohci_hcd:usb3
233:      30024          0   IO-APIC-level  eth0
NMI:        682       1125 
LOC:     511687     511654 
ERR:          0
MIS:          0

so it looks like the problems are related to the drivers of interrupt vectors
above 14.  However, powernow_k8 doesn't seem to fit.

3) when it breaks, the kernel reports:

sd 0:0:0:0 SCSI error, return code = 0x00070000
end_request: I/O error, dev sda, sector <sector_number>
lost page write due to I/O error on sda

for each sector that is attempted to be read from/written to.  Interestingly
enough, when this happens, the other devices seem to work (eg. the tg3 driver
evidently works).

I'm attaching the output of dmesg after a fresh boot (I think I'll create a
bugzilla entry and put all of the information in there).

Greetings,
Rafael


-- 
You never change things by fighting the existing reality.
		R. Buckminster Fuller

[-- Attachment #2: dmesg.log --]
[-- Type: text/x-log, Size: 25199 bytes --]

Bootdata ok (command line is root=/dev/sda3 vga=792 resume=/dev/sda1)
Linux version 2.6.18-rc6 (rafael@albercik) (gcc version 4.1.0 (SUSE Linux)) #3 SMP PREEMPT Mon Sep 4 22:31:52 CEST 2006
BIOS-provided physical RAM map:
 BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
 BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
 BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
 BIOS-e820: 0000000000100000 - 0000000037fd0000 (usable)
 BIOS-e820: 0000000037fd0000 - 0000000037fe5600 (reserved)
 BIOS-e820: 0000000037fe5600 - 0000000037ff8000 (ACPI NVS)
 BIOS-e820: 0000000037ff8000 - 0000000040000000 (reserved)
 BIOS-e820: 00000000e0000000 - 00000000f0000000 (reserved)
 BIOS-e820: 00000000fec00000 - 00000000fec02000 (reserved)
 BIOS-e820: 00000000ffbc0000 - 00000000ffcc0000 (reserved)
 BIOS-e820: 00000000fff00000 - 0000000100000000 (reserved)
DMI 2.4 present.
ACPI: RSDP (v002 HP                                    ) @ 0x00000000000f7d30
ACPI: XSDT (v001 HP     0944     0x06070620 HP   0x00000001) @ 0x0000000037fe57b4
ACPI: FADT (v004 HP     0944     0x00000003 HP   0x00000001) @ 0x0000000037fe5684
ACPI: MADT (v001 HP     0944     0x00000001 HP   0x00000001) @ 0x0000000037fe5808
ACPI: MCFG (v001 HP     0944     0x00000001 HP   0x00000001) @ 0x0000000037fe586c
ACPI: TCPA (v002 HP     0944     0x00000001 HP   0x00000001) @ 0x0000000037fe58a8
ACPI: SSDT (v001 HP       HPQNLP 0x00000001 MSFT 0x0100000e) @ 0x0000000037ff4756
ACPI: SSDT (v001 HP     PSSTBLID 0x00000001 HP   0x00000001) @ 0x0000000037ff47af
ACPI: DSDT (v001 HP        SB400 0x00010000 MSFT 0x0100000e) @ 0x0000000000000000
No mptable found.
On node 0 totalpages: 224966
  DMA zone: 2813 pages, LIFO batch:0
  DMA32 zone: 222153 pages, LIFO batch:31
ACPI: PM-Timer IO Port: 0x8008
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
Processor #0 15:8 APIC version 16
ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
Processor #1 15:8 APIC version 16
ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
IOAPIC[0]: apic_id 2, version 33, address 0xfec00000, GSI 0-23
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 21 low level)
ACPI: IRQ0 used by override.
ACPI: IRQ2 used by override.
Setting APIC routing to physical flat
Using ACPI (MADT) for SMP configuration information
Allocating PCI resources starting at 50000000 (gap: 40000000:a0000000)
SMP: Allowing 2 CPUs, 0 hotplug CPUs
Built 1 zonelists.  Total pages: 224966
Kernel command line: root=/dev/sda3 vga=792 resume=/dev/sda1
Initializing CPU#0
PID hash table entries: 4096 (order: 12, 32768 bytes)
Disabling vsyscall due to use of PM timer
time.c: Using 3.579545 MHz WALL PM GTOD PM timer.
time.c: Detected 1995.070 MHz processor.
Console: colour dummy device 80x25
Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes)
Inode-cache hash table entries: 65536 (order: 7, 524288 bytes)
Checking aperture...
CPU 0: aperture @ 8308000000 size 32 MB
Aperture too small (32 MB)
No AGP bridge found
Memory: 893136k/917312k available (2018k kernel code, 23440k reserved, 1627k data, 176k init)
Calibrating delay using timer specific routine.. 3995.12 BogoMIPS (lpj=7990243)
Security Framework v1.0.0 initialized
Mount-cache hash table entries: 256
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 512K (64 bytes/line)
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 0
SMP alternatives: switching to UP code
ACPI: Core revision 20060707
..MP-BIOS bug: 8254 timer not connected to IO-APIC
Using local APIC timer interrupts.
result 12469202
Detected 12.469 MHz APIC timer.
SMP alternatives: switching to SMP code
Booting processor 1/2 APIC 0x1
Initializing CPU#1
Calibrating delay using timer specific routine.. 3990.21 BogoMIPS (lpj=7980439)
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 512K (64 bytes/line)
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 1
AMD Turion(tm) 64 X2 Mobile Technology TL-60 stepping 02
CPU 1: Syncing TSC to CPU 0.
CPU 1: synchronized TSC with CPU 0 (last diff 0 cycles, maxerr 501 cycles)
Brought up 2 CPUs
testing NMI watchdog ... OK.
migration_cost=357
checking if image is initramfs... it is
Freeing initrd memory: 4695k freed
PM: Adding info for No Bus:platform
NET: Registered protocol family 16
ACPI: bus type pci registered
PCI: Using MMCONFIG at e0000000
PCI: No mmconfig possible on device 0:18
ACPI: Interpreter enabled
ACPI: Using IOAPIC for interrupt routing
PM: Adding info for acpi:acpi
ACPI: PCI Root Bridge [C074] (0000:00)
PCI: Probing PCI hardware (bus 00)
PM: Adding info for No Bus:pci0000:00
ACPI: Assume root bridge [\_SB_.C074] bus is 0
PCI: Ignoring BAR0-3 of IDE controller 0000:00:14.1
Boot video device is 0000:01:05.0
PCI: Transparent bridge - 0000:00:14.4
PCI: Bus #03 (-#06) is hidden behind transparent bridge #02 (-#03) (try 'pci=assign-busses')
Please report the result to linux-kernel to fix this permanently
ACPI: PCI Interrupt Routing Table [\_SB_.C074._PRT]
PM: Adding info for pci:0000:00:00.0
PM: Adding info for pci:0000:00:01.0
PM: Adding info for pci:0000:00:04.0
PM: Adding info for pci:0000:00:05.0
PM: Adding info for pci:0000:00:06.0
PM: Adding info for pci:0000:00:12.0
PM: Adding info for pci:0000:00:13.0
PM: Adding info for pci:0000:00:13.1
PM: Adding info for pci:0000:00:13.2
PM: Adding info for pci:0000:00:14.0
PM: Adding info for pci:0000:00:14.1
PM: Adding info for pci:0000:00:14.2
PM: Adding info for pci:0000:00:14.3
PM: Adding info for pci:0000:00:14.4
PM: Adding info for pci:0000:00:18.0
PM: Adding info for pci:0000:00:18.1
PM: Adding info for pci:0000:00:18.2
PM: Adding info for pci:0000:00:18.3
PM: Adding info for pci:0000:01:05.0
PM: Adding info for pci:0000:30:00.0
PM: Adding info for pci:0000:02:01.0
PM: Adding info for pci:0000:02:04.0
PM: Adding info for pci:0000:02:04.1
PM: Adding info for pci:0000:02:04.2
PM: Adding info for pci:0000:02:04.3
ACPI: PCI Interrupt Routing Table [\_SB_.C074.C075._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.C074.C0DF._PRT]
ACPI: Power Resource [C223] (off)
ACPI: Embedded Controller [C149] (gpe 17) interrupt mode.
ACPI: Power Resource [C1FE] (off)
ACPI: Power Resource [C217] (on)
ACPI: PCI Interrupt Link [C125] (IRQs 10 11) *0, disabled.
ACPI: PCI Interrupt Link [C126] (IRQs 10 11) *0, disabled.
ACPI: PCI Interrupt Link [C127] (IRQs 10 11) *0, disabled.
ACPI: PCI Interrupt Link [C128] (IRQs 10 11) *0, disabled.
ACPI: PCI Interrupt Link [C129] (IRQs 10 11) *0, disabled.
ACPI: PCI Interrupt Link [C12A] (IRQs 9) *0, disabled.
ACPI: PCI Interrupt Link [C12B] (IRQs 10 11) *0, disabled.
ACPI: PCI Interrupt Link [C12C] (IRQs *10 11)
ACPI: Power Resource [C34B] (off)
ACPI: Power Resource [C34C] (off)
ACPI: Power Resource [C34D] (off)
ACPI: Power Resource [C34E] (off)
SCSI subsystem initialized
PCI: Using ACPI for IRQ routing
PCI: If a device doesn't work, try "pci=routeirq".  If it helps, post a report
PCI: Cannot allocate resource region 0 of device 0000:00:14.2
PCI-DMA: Disabling IOMMU.
PCI: Bridge: 0000:00:01.0
  IO window: 6000-6fff
  MEM window: d4300000-d43fffff
  PREFETCH window: c0000000-c7ffffff
PCI: Bridge: 0000:00:04.0
  IO window: 4000-5fff
  MEM window: d0000000-d3ffffff
  PREFETCH window: disabled.
PCI: Bridge: 0000:00:05.0
  IO window: 2000-3fff
  MEM window: cc000000-cfffffff
  PREFETCH window: disabled.
PCI: Bridge: 0000:00:06.0
  IO window: disabled.
  MEM window: c8000000-c80fffff
  PREFETCH window: disabled.
PCI: Bus 3, cardbus bridge: 0000:02:04.0
  IO window: 00001000-000010ff
  IO window: 00001400-000014ff
  PREFETCH window: 50000000-51ffffff
  MEM window: 54000000-55ffffff
PCI: Bridge: 0000:00:14.4
  IO window: 1000-1fff
  MEM window: d4000000-d42fffff
  PREFETCH window: 50000000-51ffffff
PCI: Setting latency timer of device 0000:00:04.0 to 64
PCI: Setting latency timer of device 0000:00:05.0 to 64
PCI: Setting latency timer of device 0000:00:06.0 to 64
GSI 16 sharing vector 0xB1 and IRQ 16
ACPI: PCI Interrupt 0000:02:04.0[A] -> GSI 20 (level, low) -> IRQ 177
NET: Registered protocol family 2
IP route cache hash table entries: 32768 (order: 6, 262144 bytes)
TCP established hash table entries: 131072 (order: 9, 2097152 bytes)
TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
TCP: Hash tables configured (established 131072 bind 65536)
TCP reno registered
PM: Adding info for platform:pcspkr
audit: initializing netlink socket (disabled)
audit(1157453631.956:1): initialized
Total HugeTLB memory allocated, 0
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Initializing Cryptographic API
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
PCI: Setting latency timer of device 0000:00:04.0 to 64
pcie_portdrv_probe->Dev[5a36:1002] has invalid IRQ. Check vendor BIOS
assign_interrupt_mode Found MSI capability
Allocate Port Service[0000:00:04.0:pcie00]
PM: Adding info for pci_express:0000:00:04.0:pcie00
Allocate Port Service[0000:00:04.0:pcie01]
PM: Adding info for pci_express:0000:00:04.0:pcie01
Allocate Port Service[0000:00:04.0:pcie03]
PM: Adding info for pci_express:0000:00:04.0:pcie03
PCI: Setting latency timer of device 0000:00:05.0 to 64
pcie_portdrv_probe->Dev[5a37:1002] has invalid IRQ. Check vendor BIOS
assign_interrupt_mode Found MSI capability
Allocate Port Service[0000:00:05.0:pcie00]
PM: Adding info for pci_express:0000:00:05.0:pcie00
Allocate Port Service[0000:00:05.0:pcie01]
PM: Adding info for pci_express:0000:00:05.0:pcie01
Allocate Port Service[0000:00:05.0:pcie03]
PM: Adding info for pci_express:0000:00:05.0:pcie03
PCI: Setting latency timer of device 0000:00:06.0 to 64
pcie_portdrv_probe->Dev[5a38:1002] has invalid IRQ. Check vendor BIOS
assign_interrupt_mode Found MSI capability
Allocate Port Service[0000:00:06.0:pcie00]
PM: Adding info for pci_express:0000:00:06.0:pcie00
Allocate Port Service[0000:00:06.0:pcie01]
PM: Adding info for pci_express:0000:00:06.0:pcie01
Allocate Port Service[0000:00:06.0:pcie03]
PM: Adding info for pci_express:0000:00:06.0:pcie03
PM: Adding info for platform:vesafb.0
vesafb: framebuffer at 0xc0000000, mapped to 0xffffc20010100000, using 4608k, total 16384k
vesafb: mode is 1024x768x24, linelength=3072, pages=6
vesafb: scrolling: redraw
vesafb: Truecolor: size=0:8:8:8, shift=0:16:8:0
Console: switching to colour frame buffer device 128x48
fb0: VESA VGA frame buffer device
Real Time Clock Driver v1.12ac
Non-volatile memory driver v1.2
Linux agpgart interface v0.101 (c) Dave Jones
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
PM: Adding info for platform:serial8250
RAMDISK driver initialized: 16 RAM disks of 128000K size 1024 blocksize
libata version 2.00 loaded.
sata_sil 0000:00:12.0: version 2.0
GSI 17 sharing vector 0xD9 and IRQ 17
ACPI: PCI Interrupt 0000:00:12.0[A] -> GSI 16 (level, low) -> IRQ 217
ata1: SATA max UDMA/100 cmd 0xFFFFC2000000C080 ctl 0xFFFFC2000000C08A bmdma 0xFFFFC2000000C000 irq 217
ata2: SATA max UDMA/100 cmd 0xFFFFC2000000C0C0 ctl 0xFFFFC2000000C0CA bmdma 0xFFFFC2000000C008 irq 217
scsi0 : sata_sil
PM: Adding info for No Bus:host0
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata1.00: ATA-7, max UDMA/100, 156301488 sectors: LBA48 
ata1.00: ata1: dev 0 multi count 16
ata1.00: configured for UDMA/100
scsi1 : sata_sil
PM: Adding info for No Bus:host1
ata2: SATA link down (SStatus 0 SControl 300)
PM: Adding info for No Bus:target0:0:0
  Vendor: ATA       Model: FUJITSU MHV2080B  Rev: 892C
  Type:   Direct-Access                      ANSI SCSI revision: 05
PM: Adding info for scsi:0:0:0:0
SCSI device sda: 156301488 512-byte hdwr sectors (80026 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
SCSI device sda: 156301488 512-byte hdwr sectors (80026 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
 sda: sda1 sda2 sda3 sda4 < sda5 sda6 sda7 sda8 >
sd 0:0:0:0: Attached scsi disk sda
PM: Adding info for platform:i8042
i8042.c: Detected active multiplexing controller, rev 1.1.
serio: i8042 AUX0 port at 0x60,0x64 irq 12
serio: i8042 AUX1 port at 0x60,0x64 irq 12
PM: Adding info for serio:serio0
PM: Adding info for serio:serio1
serio: i8042 AUX2 port at 0x60,0x64 irq 12
PM: Adding info for serio:serio2
serio: i8042 AUX3 port at 0x60,0x64 irq 12
PM: Adding info for serio:serio3
serio: i8042 KBD port at 0x60,0x64 irq 1
PM: Adding info for serio:serio4
mice: PS/2 mouse device common for all mice
input: PC Speaker as /class/input/input0
input: AT Translated Set 2 keyboard as /class/input/input1
md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: bitmap version 4.39
NET: Registered protocol family 1
swsusp: Resume From Partition /dev/sda1
PM: Checking swsusp image.
PM: Resume from disk failed.
ACPI: (supports S0 S3 S4 S5)
Freeing unused kernel memory: 176k freed
Write protecting the kernel read-only data: 414k
synaptics reset failed
synaptics reset failed
synaptics reset failed
Synaptics Touchpad, model: 1, fw: 6.2, id: 0x25a0b1, caps: 0xa04793/0x300000
serio: Synaptics pass-through port at isa0060/serio4/input0
input: SynPS/2 Synaptics TouchPad as /class/input/input2
Losing some ticks... checking if CPU frequency changed.
PM: Adding info for serio:serio5
sd 0:0:0:0: Attached scsi generic sg0 type 0
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
ATIIXP: IDE controller at PCI slot 0000:00:14.1
ACPI: PCI Interrupt 0000:00:14.1[A] -> GSI 16 (level, low) -> IRQ 217
ATIIXP: chipset revision 128
ATIIXP: not 100% native mode: will probe irqs later
    ide0: BM-DMA at 0x7040-0x7047, BIOS settings: hda:DMA, hdb:pio
ATIIXP: simplex device: DMA disabled
ide1: ATIIXP Bus-Master DMA disabled (BIOS)
Probing IDE interface ide0...
hda: HL-DT-ST DVDRAM GMA-4082N, ATAPI CD/DVD-ROM drive
PM: Adding info for No Bus:ide0
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
PM: Adding info for ide:0.0
Probing IDE interface ide1...
ACPI: Processor [C000] (supports 8 throttling states)
ACPI: Processor [C001] (supports 8 throttling states)
ACPI: Thermal Zone [TZ1] (56 C)
ACPI: Thermal Zone [TZ2] (48 C)
ACPI: Thermal Zone [TZ3] (28 C)
ACPI: Transitioning device [C34F] to D3
ACPI: Transitioning device [C34F] to D3
ACPI: Fan [C34F] (off)
ACPI: Transitioning device [C350] to D3
ACPI: Transitioning device [C350] to D3
ACPI: Fan [C350] (off)
ACPI: Fan [C351] (on)
ACPI: Fan [C352] (on)
Attempting manual resume
swsusp: Resume From Partition 8:1
PM: Checking swsusp image.
PM: Resume from disk failed.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda3, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
usbcore: registered new driver usbfs
Yenta: CardBus bridge found at 0000:02:04.0 [103c:30b0]
Yenta: Enabling burst memory read transactions
usbcore: registered new driver hub
Yenta: Using INTVAL to route CSC interrupts to PCI
GSI 18 sharing vector 0xE1 and IRQ 18
Yenta: Routing CardBus interrupts to PCI
Yenta TI: socket 0000:02:04.0, mfunc 0x01a11002, devctl 0x64
ACPI: PCI Interrupt 0000:00:13.2[A] -> GSI 19 (level, low) -> IRQ 225
ehci_hcd 0000:00:13.2: EHCI Host Controller
ehci_hcd 0000:00:13.2: new USB bus registered, assigned bus number 1
ohci_hcd: 2005 April 22 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)
ehci_hcd 0000:00:13.2: irq 225, io mem 0xd4403000
ehci_hcd 0000:00:13.2: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
PM: Adding info for usb:usb1
PM: Adding info for No Bus:usbdev1.1_ep00
usb usb1: configuration #1 chosen from 1 choice
PM: Adding info for usb:1-0:1.0
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 8 ports detected
hda: ATAPI 24X DVD-ROM DVD-R-RAM CD-R/RW drive, 2048kB Cache, DMA
Yenta: ISA IRQ mask 0x0ef8, PCI irq 177
Uniform CD-ROM driver Revision: 3.20
Socket status: 30000006
PM: Adding info for No Bus:usbdev1.1_ep81
Yenta: Raising subordinate bus# of parent bus (#02) from #03 to #06
pcmcia: parent PCI bridge I/O window: 0x1000 - 0x1fff
pcmcia: parent PCI bridge Memory window: 0xd4000000 - 0xd42fffff
pcmcia: parent PCI bridge Memory window: 0x50000000 - 0x51ffffff
ieee80211_crypt: registered algorithm 'NULL'
ACPI: PCI Interrupt 0000:00:13.0[A] -> GSI 19 (level, low) -> IRQ 225
ohci_hcd 0000:00:13.0: OHCI Host Controller
ohci_hcd 0000:00:13.0: new USB bus registered, assigned bus number 2
ohci_hcd 0000:00:13.0: irq 225, io mem 0xd4401000
ieee80211: 802.11 data/management/control stack, git-1.1.13
ieee1394: Initialized config rom entry `ip1394'
ieee80211: Copyright (C) 2004-2005 Intel Corporation <jketreno@linux.intel.com>
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
PM: Adding info for usb:usb2
PM: Adding info for No Bus:usbdev2.1_ep00
usb usb2: configuration #1 chosen from 1 choice
PM: Adding info for usb:2-0:1.0
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 4 ports detected
PM: Adding info for No Bus:usbdev2.1_ep81
ACPI: PCI Interrupt 0000:00:13.1[A] -> GSI 19 (level, low) -> IRQ 225
ohci_hcd 0000:00:13.1: OHCI Host Controller
ohci_hcd 0000:00:13.1: new USB bus registered, assigned bus number 3
ohci_hcd 0000:00:13.1: irq 225, io mem 0xd4402000
PM: Adding info for usb:usb3
PM: Adding info for No Bus:usbdev3.1_ep00
usb usb3: configuration #1 chosen from 1 choice
PM: Adding info for usb:3-0:1.0
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 4 ports detected
Floppy drive(s): fd0 is 1.44M
PM: Adding info for No Bus:usbdev3.1_ep81
tg3.c:v3.65 (August 07, 2006)
piix4_smbus 0000:00:14.0: Found 0000:00:14.0 device
GSI 19 sharing vector 0xE9 and IRQ 19
ACPI: PCI Interrupt 0000:02:01.0[A] -> GSI 23 (level, low) -> IRQ 233
PM: Adding info for No Bus:i2c-0
sdhci: Secure Digital Host Controller Interface driver, 0.12
sdhci: Copyright(c) Pierre Ossman
bcm43xx driver
eth0: Tigon3 [partno(BCM95788A50) rev 3003 PHY(5705)] (PCI:33MHz:32-bit) 10/100/1000BaseT Ethernet 00:17:08:2e:2e:f3
eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] Split[0] WireSpeed[0] TSOcap[1] 
eth0: dma_rwctrl[763f0000] dma_mask[32-bit]
ACPI: PCI Interrupt 0000:00:14.2[A] -> GSI 16 (level, low) -> IRQ 217
usb 2-2: new full speed USB device using ohci_hcd and address 2
ACPI: PCI Interrupt 0000:02:04.1[A] -> GSI 20 (level, low) -> IRQ 177
PM: Adding info for ieee1394:fw-host0
PM: Adding info for usb:2-2
PM: Adding info for No Bus:usbdev2.2_ep00
usb 2-2: configuration #1 chosen from 1 choice
PM: Adding info for usb:2-2:1.0
PM: Adding info for No Bus:usbdev2.2_ep81
PM: Adding info for No Bus:usbdev2.2_ep82
PM: Adding info for No Bus:usbdev2.2_ep02
PM: Adding info for usb:2-2:1.1
PM: Adding info for No Bus:usbdev2.2_ep83
PM: Adding info for No Bus:usbdev2.2_ep03
PM: Adding info for usb:2-2:1.2
PM: Adding info for No Bus:usbdev2.2_ep84
PM: Adding info for No Bus:usbdev2.2_ep04
PM: Adding info for usb:2-2:1.3
ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[177]  MMIO=[d4011000-d40117ff]  Max Packet=[2048]  IR/IT contexts=[4/8]
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
sdhci: SDHCI controller found at 0000:02:04.3 [104c:803c] (rev 0)
ACPI: PCI Interrupt 0000:02:04.3[A] -> GSI 20 (level, low) -> IRQ 177
mmc0: SDHCI at 0xd4019000 irq 177 PIO
GSI 20 sharing vector 0x32 and IRQ 20
ACPI: PCI Interrupt 0000:30:00.0[A] -> GSI 18 (level, low) -> IRQ 50
PCI: Setting latency timer of device 0000:30:00.0 to 64
bcm43xx: Chip ID 0x4311, rev 0x1
bcm43xx: Number of cores: 4
bcm43xx: Core 0: ID 0x800, rev 0x11, vendor 0x4243, enabled
usb 3-1: new full speed USB device using ohci_hcd and address 2
bcm43xx: Core 1: ID 0x812, rev 0xa, vendor 0x4243, disabled
bcm43xx: Core 2: ID 0x817, rev 0x3, vendor 0x4243, disabled
bcm43xx: Core 3: ID 0x820, rev 0x1, vendor 0x4243, enabled
bcm43xx: PHY connected
bcm43xx: Detected PHY: Version: 4, Type 2, Revision 8
bcm43xx: Detected Radio: ID: 2205017f (Manuf: 17f Ver: 2050 Rev: 2)
bcm43xx: Radio turned off
bcm43xx: Radio turned off
Bluetooth: Core ver 2.10
PM: Adding info for platform:bluetooth
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
PM: Adding info for usb:3-1
PM: Adding info for No Bus:usbdev3.2_ep00
usb 3-1: configuration #1 chosen from 1 choice
PM: Adding info for usb:3-1:1.0
PM: Adding info for No Bus:usbdev3.2_ep81
PM: Adding info for No Bus:usbdev3.2_ep02
Bluetooth: HCI USB driver ver 2.9
usb 3-4: new low speed USB device using ohci_hcd and address 3
PM: Adding info for ieee1394:00023f9929613f0c
ieee1394: Host added: ID:BUS[0-00:1023]  GUID[00023f9929613f0c]
PM: Adding info for ieee1394:00023f9929613f0c-0
PM: Adding info for usb:3-4
PM: Adding info for No Bus:usbdev3.3_ep00
usb 3-4: configuration #1 chosen from 1 choice
PM: Adding info for usb:3-4:1.0
PM: Adding info for No Bus:usbdev3.3_ep81
PM: Removing info for No Bus:usbdev2.2_ep83
PM: Removing info for No Bus:usbdev2.2_ep03
PM: Adding info for No Bus:usbdev2.2_ep83
PM: Adding info for No Bus:usbdev2.2_ep03
PM: Adding info for No Bus:hci0
usbcore: registered new driver hci_usb
usbcore: registered new driver hiddev
input: Logitech USB Receiver as /class/input/input3
input: USB HID v1.10 Mouse [Logitech USB Receiver] on usb-0000:00:13.1-4
usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.6:USB HID core driver
floppy0: no floppy controllers found
device-mapper: ioctl: 4.7.0-ioctl (2006-06-24) initialised: dm-devel@redhat.com
loop: loaded (max 8 devices)
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda2, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda7, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda8, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda5, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda6, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
Floppy drive(s): fd0 is 1.44M
Adding 1052216k swap on /dev/sda1.  Priority:-1 extents:1 across:1052216k
floppy0: no floppy controllers found
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
IPv6 over IPv4 tunneling driver
ip6_tables: (C) 2000-2006 Netfilter Core Team
ip_tables: (C) 2000-2006 Netfilter Core Team
Netfilter messages via NETLINK v0.30.
ip_conntrack version 2.4 (3583 buckets, 28664 max) - 304 bytes per conntrack
ACPI: AC Adapter [C1BD] (on-line)
ACPI: Battery Slot [C1BF] (battery present)
ACPI: Battery Slot [C1BE] (battery absent)
ACPI: Power Button (FF) [PWRF]
ACPI: Sleep Button (CM) [C25A]
ACPI: Lid Switch [C25B]
BIOS EDD facility v0.16 2004-Jun-25, 1 devices found
PM: Writing back config space on device 0000:02:01.0 at offset b (was 3ed173b, writing 30b0103c)
PM: Writing back config space on device 0000:02:01.0 at offset 3 (was 0, writing 4010)
PM: Writing back config space on device 0000:02:01.0 at offset 2 (was 2000000, writing 2000003)
PM: Writing back config space on device 0000:02:01.0 at offset 1 (was 2b00000, writing 2b00006)
PM: Writing back config space on device 0000:02:01.0 at offset 0 (was 3ed173b, writing 169c14e4)
ADDRCONF(NETDEV_UP): eth0: link is not ready
NET: Registered protocol family 17
tg3: eth0: Link is up at 100 Mbps, full duplex.
tg3: eth0: Flow control is on for TX and on for RX.
ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
powernow-k8: Found 2 AMD Turion(tm) 64 X2 Mobile Technology TL-60 processors (version 2.00.00)
powernow-k8:    0 : fid 0xc (2000 MHz), vid 0x13
powernow-k8:    1 : fid 0xa (1800 MHz), vid 0x15
powernow-k8:    2 : fid 0x8 (1600 MHz), vid 0x17
powernow-k8:    3 : fid 0x0 (800 MHz), vid 0x1e
powernow-k8: ph2 null fid transition 0xc
eth0: no IPv6 routers present
hda-intel: Invalid position buffer, using LPIB read method instead.
SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=00:17:08:2e:2e:f3:00:20:48:04:f1:bd:08:00 SRC=193.0.81.21 DST=193.0.83.66 LEN=84 TOS=0x00 PREC=0x00 TTL=255 ID=58993 DF PROTO=UDP SPT=62839 DPT=111 LEN=64 
SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=00:17:08:2e:2e:f3:00:20:48:04:f1:bd:08:00 SRC=193.0.81.21 DST=193.0.83.66 LEN=84 TOS=0x00 PREC=0x00 TTL=255 ID=58994 DF PROTO=UDP SPT=62839 DPT=111 LEN=64 
SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=00:17:08:2e:2e:f3:00:20:48:04:f1:bd:08:00 SRC=193.0.81.21 DST=193.0.83.66 LEN=84 TOS=0x00 PREC=0x00 TTL=255 ID=58995 DF PROTO=UDP SPT=62839 DPT=111 LEN=64 
SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=00:17:08:2e:2e:f3:00:20:48:04:f1:bd:08:00 SRC=193.0.81.21 DST=193.0.83.66 LEN=84 TOS=0x00 PREC=0x00 TTL=255 ID=58996 DF PROTO=UDP SPT=62845 DPT=111 LEN=64 
SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=00:17:08:2e:2e:f3:00:20:48:04:f1:bd:08:00 SRC=193.0.81.21 DST=193.0.83.66 LEN=84 TOS=0x00 PREC=0x00 TTL=255 ID=58997 DF PROTO=UDP SPT=62845 DPT=111 LEN=64 
SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=00:17:08:2e:2e:f3:00:20:48:04:f1:bd:08:00 SRC=193.0.81.21 DST=193.0.83.66 LEN=84 TOS=0x00 PREC=0x00 TTL=255 ID=58998 DF PROTO=UDP SPT=62845 DPT=111 LEN=64 

^ permalink raw reply	[flat|nested] 21+ messages in thread

* Re: Problem with resuming ATI SATA on HPC nx6325
  2006-09-05 11:38   ` Rafael J. Wysocki
@ 2006-09-06 10:42     ` Pavel Machek
  2006-09-06 20:47       ` Rafael J. Wysocki
  0 siblings, 1 reply; 21+ messages in thread
From: Pavel Machek @ 2006-09-06 10:42 UTC (permalink / raw)
  To: Rafael J. Wysocki; +Cc: Linux ACPI, Alan Cox

Hi!

> Now, the output of /proc/interrupts with everything loaded is
> 
>            CPU0       CPU1       
>   0:     511683          0  local-APIC-edge  timer
>   1:       6164          0    IO-APIC-edge  i8042
>   8:          0          0    IO-APIC-edge  rtc
>  12:        148          0    IO-APIC-edge  i8042
>  14:      18053          0    IO-APIC-edge  ide0
> 169:        140          0   IO-APIC-level  acpi
> 177:          4          0   IO-APIC-level  yenta, ohci1394, sdhci:slot0
> 217:      48306          0   IO-APIC-level  libata, HDA Intel
> 225:      22528          0   IO-APIC-level  ehci_hcd:usb1, ohci_hcd:usb2, ohci_hcd:usb3
> 233:      30024          0   IO-APIC-level  eth0
> NMI:        682       1125 
> LOC:     511687     511654 
> ERR:          0
> MIS:          0
> 
> so it looks like the problems are related to the drivers of interrupt vectors
> above 14.  However, powernow_k8 doesn't seem to fit.

Its possible that pn_k8 has some separate problem...

> 3) when it breaks, the kernel reports:
> 
> sd 0:0:0:0 SCSI error, return code = 0x00070000
> end_request: I/O error, dev sda, sector <sector_number>
> lost page write due to I/O error on sda
> 
> for each sector that is attempted to be read from/written to.  Interestingly
> enough, when this happens, the other devices seem to work (eg. the tg3 driver
> evidently works).

That actually points to interrupt problems.

> I'm attaching the output of dmesg after a fresh boot (I think I'll create a
> bugzilla entry and put all of the information in there).

Yes please. Big question is who to assign it to...
									Pavel

-- 
Thanks, Sharp!

^ permalink raw reply	[flat|nested] 21+ messages in thread

* Re: Problem with resuming ATI SATA on HPC nx6325
  2006-09-06 10:42     ` Pavel Machek
@ 2006-09-06 20:47       ` Rafael J. Wysocki
  2006-09-06 21:12         ` Pavel Machek
  0 siblings, 1 reply; 21+ messages in thread
From: Rafael J. Wysocki @ 2006-09-06 20:47 UTC (permalink / raw)
  To: Pavel Machek; +Cc: Linux ACPI, Alan Cox

Hi,

On Wednesday, 6 September 2006 12:42, Pavel Machek wrote:
> Hi!
> 
> > Now, the output of /proc/interrupts with everything loaded is
> > 
> >            CPU0       CPU1       
> >   0:     511683          0  local-APIC-edge  timer
> >   1:       6164          0    IO-APIC-edge  i8042
> >   8:          0          0    IO-APIC-edge  rtc
> >  12:        148          0    IO-APIC-edge  i8042
> >  14:      18053          0    IO-APIC-edge  ide0
> > 169:        140          0   IO-APIC-level  acpi
> > 177:          4          0   IO-APIC-level  yenta, ohci1394, sdhci:slot0
> > 217:      48306          0   IO-APIC-level  libata, HDA Intel
> > 225:      22528          0   IO-APIC-level  ehci_hcd:usb1, ohci_hcd:usb2, ohci_hcd:usb3
> > 233:      30024          0   IO-APIC-level  eth0
> > NMI:        682       1125 
> > LOC:     511687     511654 
> > ERR:          0
> > MIS:          0
> > 
> > so it looks like the problems are related to the drivers of interrupt vectors
> > above 14.  However, powernow_k8 doesn't seem to fit.
> 
> Its possible that pn_k8 has some separate problem...
> 
> > 3) when it breaks, the kernel reports:
> > 
> > sd 0:0:0:0 SCSI error, return code = 0x00070000
> > end_request: I/O error, dev sda, sector <sector_number>
> > lost page write due to I/O error on sda
> > 
> > for each sector that is attempted to be read from/written to.  Interestingly
> > enough, when this happens, the other devices seem to work (eg. the tg3 driver
> > evidently works).
> 
> That actually points to interrupt problems.
> 
> > I'm attaching the output of dmesg after a fresh boot (I think I'll create a
> > bugzilla entry and put all of the information in there).
> 
> Yes please. Big question is who to assign it to...

Actually, I won't for now, because there's some progress. :-)

Namely, on a non-preemptible 2.6.18-rc5-mm1 the only module that causes
problems is snd_hda_intel.  Unfortunately I can't unload it before suspend,
because the kernel oopses on every attempt to do so, but I'll report this
in a separate thread.

I'll experiment with the preemptible kernel when the snd_hda_intel issue gets
resolved.

Greetings,
Rafael


-- 
You never change things by fighting the existing reality.
		R. Buckminster Fuller

^ permalink raw reply	[flat|nested] 21+ messages in thread

* Re: Problem with resuming ATI SATA on HPC nx6325
  2006-09-06 20:47       ` Rafael J. Wysocki
@ 2006-09-06 21:12         ` Pavel Machek
  2006-09-07  7:03           ` Rafael J. Wysocki
  0 siblings, 1 reply; 21+ messages in thread
From: Pavel Machek @ 2006-09-06 21:12 UTC (permalink / raw)
  To: Rafael J. Wysocki; +Cc: Linux ACPI, Alan Cox

On Wed 2006-09-06 22:47:37, Rafael J. Wysocki wrote:
> Hi,
> 
> On Wednesday, 6 September 2006 12:42, Pavel Machek wrote:
> > Hi!
> > 
> > > Now, the output of /proc/interrupts with everything loaded is
> > > 
> > >            CPU0       CPU1       
> > >   0:     511683          0  local-APIC-edge  timer
> > >   1:       6164          0    IO-APIC-edge  i8042
> > >   8:          0          0    IO-APIC-edge  rtc
> > >  12:        148          0    IO-APIC-edge  i8042
> > >  14:      18053          0    IO-APIC-edge  ide0
> > > 169:        140          0   IO-APIC-level  acpi
> > > 177:          4          0   IO-APIC-level  yenta, ohci1394, sdhci:slot0
> > > 217:      48306          0   IO-APIC-level  libata, HDA Intel
> > > 225:      22528          0   IO-APIC-level  ehci_hcd:usb1, ohci_hcd:usb2, ohci_hcd:usb3
> > > 233:      30024          0   IO-APIC-level  eth0
> > > NMI:        682       1125 
> > > LOC:     511687     511654 
> > > ERR:          0
> > > MIS:          0
> > > 
> > > so it looks like the problems are related to the drivers of interrupt vectors
> > > above 14.  However, powernow_k8 doesn't seem to fit.
> > 
> > Its possible that pn_k8 has some separate problem...
> > 
> > > 3) when it breaks, the kernel reports:
> > > 
> > > sd 0:0:0:0 SCSI error, return code = 0x00070000
> > > end_request: I/O error, dev sda, sector <sector_number>
> > > lost page write due to I/O error on sda
> > > 
> > > for each sector that is attempted to be read from/written to.  Interestingly
> > > enough, when this happens, the other devices seem to work (eg. the tg3 driver
> > > evidently works).
> > 
> > That actually points to interrupt problems.
> > 
> > > I'm attaching the output of dmesg after a fresh boot (I think I'll create a
> > > bugzilla entry and put all of the information in there).
> > 
> > Yes please. Big question is who to assign it to...
> 
> Actually, I won't for now, because there's some progress. :-)
> 
> Namely, on a non-preemptible 2.6.18-rc5-mm1 the only module that causes
> problems is snd_hda_intel.  Unfortunately I can't unload it before suspend,
> because the kernel oopses on every attempt to do so, but I'll report this
> in a separate thread.
> 
> I'll experiment with the preemptible kernel when the snd_hda_intel issue gets
> resolved.

What about not loading snd_hda_intel in the first place?

(Just for the record, suspend with snd_hda_intel seems to work
here...)

								Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

^ permalink raw reply	[flat|nested] 21+ messages in thread

* Re: Problem with resuming ATI SATA on HPC nx6325
  2006-09-06 21:12         ` Pavel Machek
@ 2006-09-07  7:03           ` Rafael J. Wysocki
  2006-09-07 10:34             ` Rafael J. Wysocki
  0 siblings, 1 reply; 21+ messages in thread
From: Rafael J. Wysocki @ 2006-09-07  7:03 UTC (permalink / raw)
  To: Pavel Machek; +Cc: Linux ACPI, Alan Cox

On Wednesday, 6 September 2006 23:12, Pavel Machek wrote:
> On Wed 2006-09-06 22:47:37, Rafael J. Wysocki wrote:
> > Hi,
> > 
> > On Wednesday, 6 September 2006 12:42, Pavel Machek wrote:
> > > Hi!
> > > 
> > > > Now, the output of /proc/interrupts with everything loaded is
> > > > 
> > > >            CPU0       CPU1       
> > > >   0:     511683          0  local-APIC-edge  timer
> > > >   1:       6164          0    IO-APIC-edge  i8042
> > > >   8:          0          0    IO-APIC-edge  rtc
> > > >  12:        148          0    IO-APIC-edge  i8042
> > > >  14:      18053          0    IO-APIC-edge  ide0
> > > > 169:        140          0   IO-APIC-level  acpi
> > > > 177:          4          0   IO-APIC-level  yenta, ohci1394, sdhci:slot0
> > > > 217:      48306          0   IO-APIC-level  libata, HDA Intel
> > > > 225:      22528          0   IO-APIC-level  ehci_hcd:usb1, ohci_hcd:usb2, ohci_hcd:usb3
> > > > 233:      30024          0   IO-APIC-level  eth0
> > > > NMI:        682       1125 
> > > > LOC:     511687     511654 
> > > > ERR:          0
> > > > MIS:          0
> > > > 
> > > > so it looks like the problems are related to the drivers of interrupt vectors
> > > > above 14.  However, powernow_k8 doesn't seem to fit.
> > > 
> > > Its possible that pn_k8 has some separate problem...
> > > 
> > > > 3) when it breaks, the kernel reports:
> > > > 
> > > > sd 0:0:0:0 SCSI error, return code = 0x00070000
> > > > end_request: I/O error, dev sda, sector <sector_number>
> > > > lost page write due to I/O error on sda
> > > > 
> > > > for each sector that is attempted to be read from/written to.  Interestingly
> > > > enough, when this happens, the other devices seem to work (eg. the tg3 driver
> > > > evidently works).
> > > 
> > > That actually points to interrupt problems.
> > > 
> > > > I'm attaching the output of dmesg after a fresh boot (I think I'll create a
> > > > bugzilla entry and put all of the information in there).
> > > 
> > > Yes please. Big question is who to assign it to...
> > 
> > Actually, I won't for now, because there's some progress. :-)
> > 
> > Namely, on a non-preemptible 2.6.18-rc5-mm1 the only module that causes
> > problems is snd_hda_intel.  Unfortunately I can't unload it before suspend,
> > because the kernel oopses on every attempt to do so, but I'll report this
> > in a separate thread.
> > 
> > I'll experiment with the preemptible kernel when the snd_hda_intel issue gets
> > resolved.
> 
> What about not loading snd_hda_intel in the first place?

Of course if it don't load it, the suspend works.  Otherwise I wouldn't have
known it's the only module causing problems.  ;-)

Still in a practically useful setup I'd like it to be unloaded before the
suspend and loaded back again after the resume.

> (Just for the record, suspend with snd_hda_intel seems to work
> here...)

The problem seems to be related to the MSI.  Andrew and Greg KH say the
MSI code have been rewritten recently, so there's some hope.

Greetings,
Rafael


-- 
You never change things by fighting the existing reality.
		R. Buckminster Fuller

^ permalink raw reply	[flat|nested] 21+ messages in thread

* Re: Problem with resuming ATI SATA on HPC nx6325
  2006-09-07  7:03           ` Rafael J. Wysocki
@ 2006-09-07 10:34             ` Rafael J. Wysocki
  2006-09-07 22:08               ` Pavel Machek
  0 siblings, 1 reply; 21+ messages in thread
From: Rafael J. Wysocki @ 2006-09-07 10:34 UTC (permalink / raw)
  To: Pavel Machek; +Cc: Linux ACPI, Alan Cox

On Thursday, 7 September 2006 09:03, Rafael J. Wysocki wrote:
> On Wednesday, 6 September 2006 23:12, Pavel Machek wrote:
> > On Wed 2006-09-06 22:47:37, Rafael J. Wysocki wrote:
> > > Hi,
> > > 
> > > On Wednesday, 6 September 2006 12:42, Pavel Machek wrote:
> > > > Hi!
> > > > 
> > > > > Now, the output of /proc/interrupts with everything loaded is
> > > > > 
> > > > >            CPU0       CPU1       
> > > > >   0:     511683          0  local-APIC-edge  timer
> > > > >   1:       6164          0    IO-APIC-edge  i8042
> > > > >   8:          0          0    IO-APIC-edge  rtc
> > > > >  12:        148          0    IO-APIC-edge  i8042
> > > > >  14:      18053          0    IO-APIC-edge  ide0
> > > > > 169:        140          0   IO-APIC-level  acpi
> > > > > 177:          4          0   IO-APIC-level  yenta, ohci1394, sdhci:slot0
> > > > > 217:      48306          0   IO-APIC-level  libata, HDA Intel
> > > > > 225:      22528          0   IO-APIC-level  ehci_hcd:usb1, ohci_hcd:usb2, ohci_hcd:usb3
> > > > > 233:      30024          0   IO-APIC-level  eth0
> > > > > NMI:        682       1125 
> > > > > LOC:     511687     511654 
> > > > > ERR:          0
> > > > > MIS:          0
> > > > > 
> > > > > so it looks like the problems are related to the drivers of interrupt vectors
> > > > > above 14.  However, powernow_k8 doesn't seem to fit.
> > > > 
> > > > Its possible that pn_k8 has some separate problem...
> > > > 
> > > > > 3) when it breaks, the kernel reports:
> > > > > 
> > > > > sd 0:0:0:0 SCSI error, return code = 0x00070000
> > > > > end_request: I/O error, dev sda, sector <sector_number>
> > > > > lost page write due to I/O error on sda
> > > > > 
> > > > > for each sector that is attempted to be read from/written to.  Interestingly
> > > > > enough, when this happens, the other devices seem to work (eg. the tg3 driver
> > > > > evidently works).
> > > > 
> > > > That actually points to interrupt problems.
> > > > 
> > > > > I'm attaching the output of dmesg after a fresh boot (I think I'll create a
> > > > > bugzilla entry and put all of the information in there).
> > > > 
> > > > Yes please. Big question is who to assign it to...
> > > 
> > > Actually, I won't for now, because there's some progress. :-)
> > > 
> > > Namely, on a non-preemptible 2.6.18-rc5-mm1 the only module that causes
> > > problems is snd_hda_intel.  Unfortunately I can't unload it before suspend,
> > > because the kernel oopses on every attempt to do so, but I'll report this
> > > in a separate thread.
> > > 
> > > I'll experiment with the preemptible kernel when the snd_hda_intel issue gets
> > > resolved.
> > 
> > What about not loading snd_hda_intel in the first place?
> 
> Of course if it don't load it, the suspend works.  Otherwise I wouldn't have
> known it's the only module causing problems.  ;-)
> 
> Still in a practically useful setup I'd like it to be unloaded before the
> suspend and loaded back again after the resume.
> 
> > (Just for the record, suspend with snd_hda_intel seems to work
> > here...)
> 
> The problem seems to be related to the MSI.  Andrew and Greg KH say the
> MSI code have been rewritten recently, so there's some hope.

I've just learnt that it's possible to disable the MSI in snd_hda_intel and I
can suspend and resume the box now (with the non-preemptible 2.6.18-rc5-mm1
:-) ).

Greetings,
Rafael


-- 
You never change things by fighting the existing reality.
		R. Buckminster Fuller

^ permalink raw reply	[flat|nested] 21+ messages in thread

* Re: Problem with resuming ATI SATA on HPC nx6325
  2006-09-07 10:34             ` Rafael J. Wysocki
@ 2006-09-07 22:08               ` Pavel Machek
  2006-09-07 22:22                 ` Rafael J. Wysocki
  0 siblings, 1 reply; 21+ messages in thread
From: Pavel Machek @ 2006-09-07 22:08 UTC (permalink / raw)
  To: Rafael J. Wysocki; +Cc: Linux ACPI, Alan Cox

Hi!

> > > (Just for the record, suspend with snd_hda_intel seems to work
> > > here...)
> > 
> > The problem seems to be related to the MSI.  Andrew and Greg KH say the
> > MSI code have been rewritten recently, so there's some hope.
> 
> I've just learnt that it's possible to disable the MSI in snd_hda_intel and I
> can suspend and resume the box now (with the non-preemptible 2.6.18-rc5-mm1
> :-) ).

So result is

1) we have preempt problem

2) we have MSI problem

? Do we have powernow-k8 problem?
								Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

^ permalink raw reply	[flat|nested] 21+ messages in thread

* Re: Problem with resuming ATI SATA on HPC nx6325
  2006-09-07 22:08               ` Pavel Machek
@ 2006-09-07 22:22                 ` Rafael J. Wysocki
  2006-09-08 14:14                   ` Rafael J. Wysocki
                                     ` (8 more replies)
  0 siblings, 9 replies; 21+ messages in thread
From: Rafael J. Wysocki @ 2006-09-07 22:22 UTC (permalink / raw)
  To: Pavel Machek; +Cc: Linux ACPI, Alan Cox, Takashi Iwai

Hi,

On Friday, 8 September 2006 00:08, Pavel Machek wrote:
> Hi!
> 
> > > > (Just for the record, suspend with snd_hda_intel seems to work
> > > > here...)
> > > 
> > > The problem seems to be related to the MSI.  Andrew and Greg KH say the
> > > MSI code have been rewritten recently, so there's some hope.
> > 
> > I've just learnt that it's possible to disable the MSI in snd_hda_intel and I
> > can suspend and resume the box now (with the non-preemptible 2.6.18-rc5-mm1
> > :-) ).
> 
> So result is
> 
> 1) we have preempt problem

Probably.  I have to investigate it a bit more, though.

> 2) we have MSI problem

I've got a patch from Takashi Iwai that fixes this one.

> ? Do we have powernow-k8 problem?

No. :-)

Please also have a look at Bug #5534, comments #153-#164.

Rafael


-- 
You never change things by fighting the existing reality.
		R. Buckminster Fuller

^ permalink raw reply	[flat|nested] 21+ messages in thread

* Re: Problem with resuming ATI SATA on HPC nx6325
  2006-09-07 22:22                 ` Rafael J. Wysocki
@ 2006-09-08 14:14                   ` Rafael J. Wysocki
  2006-09-08 15:49                   ` Pavel Machek
                                     ` (7 subsequent siblings)
  8 siblings, 0 replies; 21+ messages in thread
From: Rafael J. Wysocki @ 2006-09-08 14:14 UTC (permalink / raw)
  To: Pavel Machek; +Cc: Linux ACPI, Alan Cox, Takashi Iwai

On Friday, 8 September 2006 00:22, Rafael J. Wysocki wrote:
> Hi,
> 
> On Friday, 8 September 2006 00:08, Pavel Machek wrote:
> > Hi!
> > 
> > > > > (Just for the record, suspend with snd_hda_intel seems to work
> > > > > here...)
> > > > 
> > > > The problem seems to be related to the MSI.  Andrew and Greg KH say the
> > > > MSI code have been rewritten recently, so there's some hope.
> > > 
> > > I've just learnt that it's possible to disable the MSI in snd_hda_intel and I
> > > can suspend and resume the box now (with the non-preemptible 2.6.18-rc5-mm1
> > > :-) ).
> > 
> > So result is
> > 
> > 1) we have preempt problem
> 
> Probably.  I have to investigate it a bit more, though.

2.6.18-rc6-mm1 preemptible works too, up to the thermal management problem
after the resume described at http://bugzilla.kernel.org/show_bug.cgi?id=7122

I think the Linus' suspending of consoles makes it work ...

Rafael


-- 
You never change things by fighting the existing reality.
		R. Buckminster Fuller

^ permalink raw reply	[flat|nested] 21+ messages in thread

* Re: Problem with resuming ATI SATA on HPC nx6325
  2006-09-07 22:22                 ` Rafael J. Wysocki
  2006-09-08 14:14                   ` Rafael J. Wysocki
@ 2006-09-08 15:49                   ` Pavel Machek
  2006-09-08 23:27                     ` Rafael J. Wysocki
  2006-09-10 16:01                   ` Martin Zuther
                                     ` (6 subsequent siblings)
  8 siblings, 1 reply; 21+ messages in thread
From: Pavel Machek @ 2006-09-08 15:49 UTC (permalink / raw)
  To: Rafael J. Wysocki; +Cc: Linux ACPI, Alan Cox, Takashi Iwai

Hi!

> > ? Do we have powernow-k8 problem?
> 
> No. :-)
> 
> Please also have a look at Bug #5534, comments #153-#164.

Okay, ACPI people should fix fan driver ;-).

Hmm.. fan driver actually seems to be okay.... perhaps
acpi_thermal_resume needs some more care?
									Pavel

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

^ permalink raw reply	[flat|nested] 21+ messages in thread

* Re: Problem with resuming ATI SATA on HPC nx6325
  2006-09-08 15:49                   ` Pavel Machek
@ 2006-09-08 23:27                     ` Rafael J. Wysocki
  0 siblings, 0 replies; 21+ messages in thread
From: Rafael J. Wysocki @ 2006-09-08 23:27 UTC (permalink / raw)
  To: Pavel Machek; +Cc: Linux ACPI, Alan Cox, Takashi Iwai

On Friday, 8 September 2006 17:49, Pavel Machek wrote:
> Hi!
> 
> > > ? Do we have powernow-k8 problem?
> > 
> > No. :-)
> > 
> > Please also have a look at Bug #5534, comments #153-#164.
> 
> Okay, ACPI people should fix fan driver ;-).
> 
> Hmm.. fan driver actually seems to be okay.... perhaps
> acpi_thermal_resume needs some more care?

I bet on this one.

I have put some more details at http://bugzilla.kernel.org/show_bug.cgi?id=7122
and http://bugzilla.kernel.org/show_bug.cgi?id=5534.

Rafael


-- 
You never change things by fighting the existing reality.
		R. Buckminster Fuller

^ permalink raw reply	[flat|nested] 21+ messages in thread

* Re: Problem with resuming ATI SATA on HPC nx6325
  2006-09-07 22:22                 ` Rafael J. Wysocki
  2006-09-08 14:14                   ` Rafael J. Wysocki
  2006-09-08 15:49                   ` Pavel Machek
@ 2006-09-10 16:01                   ` Martin Zuther
  2006-09-10 18:31                   ` Yet another DSDL problem Martin Zuther
                                     ` (5 subsequent siblings)
  8 siblings, 0 replies; 21+ messages in thread
From: Martin Zuther @ 2006-09-10 16:01 UTC (permalink / raw)
  To: linux-acpi

Hi everybody!

My system

  Kubuntu Dapper 6.06 LTS (packages updated regularly)
  Current kernel image of 2.6.15-26-686

  Mainboard: MSI 865PE Neo2-P
  Processor: Intel Pentium 4 2.8E GHz 800 MHz (Box)
  RAM: 3 x 512 MB DDR
  Video card: NVidia GeForce 5200 FX

  Keyboard: Logitech iTouch Internet
  Graphics tablet: Wacom Intuos A5

doesn't shut down properly. I remember having the same problem under
Debian 3.0, but as that encounter was somewhat short and is about a year
ago, the only thing I can remember is that it was a 2.6 kernel as well.

Kubuntu also claims that I have a partial ACPI installation ("not fully
installed" or something the like in "System Settings -> Laptop and Power
-> Laptop Battery -> Power Control").

This is probably related to "acpi -V" producing the error message "No
support for device type: thermal" and having almost no useful entries in
"/proc/acpi/...".

When I remove the boot option "quiet splash" I get the following
messages during shutdown:

  * Will now halt.
  [...] md: stopping all md devices
  [...] usb 4-2: new full speed USB device using uhci_hcd and address 3
  [...] usb 4-2: not running at top speed; connect to a high speed hub
  [...] Shutdown: hda
  [...]     ACPI-0517: *** Error: Method parse/execution failed
  [\SB_.PCI0.IDE0.GTM_] (Node dffe5d60), AE_AML_PACKAGE_LIMIT
  [...]     ACPI-0517: *** Error: Method parse/execution failed
  [\_SB_.PCI0.IDE0.CHN0._GTM] (Node dffe5fa0), AE_AML_PACKAGE_LIMIT
  [...]     Power down.
  [...]     acpi_power_off called

Then there's a click as my hard drives shut down, and that's about as
near as I ever get to shutting down my computer. The only thing working
at this stage are pressing the power button (for unusual 4 seconds) or
the reset button.

Also, when I reboot the computer from KDE, it does as told, but when in
the BIOS routines, there's a noticeable pause and a click when my two
S-ATA drives are checked. I don't have a problem like that when
rebooting Win XP (I have a dual boot system).

I had a look at several forums and had a go at fixing my DSDT.dsl (you
can find the original file at
http://www.ubuntuusers.de/paste/2441/?format=txt). As running the
recommended

  cp /boot/initrd.img-`uname -r` /boot/initrd.img-`uname -r`-acpifix
  echo -n "INITRDDSDT123DSDT123" >> /boot/initrd.img-`uname -r`-acpifix
  cat /boot/DSDT.aml >> /boot/initrd.img-`uname -r`-acpifix

failed to produce a bootable image, a found a workaround (and I'm a
little proud, being still new to Linux... <g>):

  sudo cp ~/DSDT.aml /etc/mkinitramfs/DSDT.aml
  sudo mkinitramfs -o /boot/initrd.img-`uname -r`-acpifix

After rebooting with such an image I find this in the syslog:

  [...] ACPI-0284: *** Info: Table [DSDT] replaced by host OS
  [...] ACPI: Looking for DSDT in initramfs... found /DSDT.aml ...
  successfully read 13614 bytes from /DSDT.aml
  [...] ACPI: Using customized DSDT

As this message vanishes when I run an original image, I think it has
worked.

Es scheint also geklapt zu haben. Zeit, sich dem Problem zuzuwenden -
ein Lauf von iasl -sa DSDT.sdl ergibt die folgende Meldung:

So here are the warnings I found when recompiling the DSDT:

  Intel ACPI Component Architecture
  ASL Optimizing Compiler version 20060707 [Jul 25 2006]
  Copyright (C) 2000 - 2006 Intel Corporation
  Supports ACPI Specification Revision 3.0a

  DSDT.dsl  4034:                 Method (STM, 0, Serialized)
  Warning  1086 -                           ^ Not all control
    paths return a value (STM_)

  DSDT.dsl  4359:     Method (_WAK, 1, NotSerialized)
  Warning  1079 -                ^ Reserved method must return a
    value (_WAK)

  ASL Input:  DSDT.dsl - 4458 lines, 150438 bytes, 1514 keywords
  AML Output: DSDT.aml - 13606 bytes 500 named objects 1014
    executable opcodes

  Compilation complete. 0 Errors, 2 Warnings, 0 Remarks,
    462 Optimizations

For the second warning I use the googled "standard solution"

  Return(Package(0x02){0x00, 0x00})

So the problem seems to lie within the first warning. As my machine code
knowledge is based on the Z80 and was lost somewhere years ago, I'd like
to ask for your help. I also checked the WWW and the ACPI spec for
ideas, but couldn't come up with anything useful.

Thanks for any help, as I don't seem to get any further on my own...

Martin
Germany
-- 
mz_mail@mzuther.de
www.mzuther.de
www.radix-musik.de

^ permalink raw reply	[flat|nested] 21+ messages in thread

* Yet another DSDL problem
  2006-09-07 22:22                 ` Rafael J. Wysocki
                                     ` (2 preceding siblings ...)
  2006-09-10 16:01                   ` Martin Zuther
@ 2006-09-10 18:31                   ` Martin Zuther
  2006-09-11  8:05                     ` Sorry Martin Zuther
  2006-09-10 18:55                   ` Yet another DSDL problem Martin Zuther
                                     ` (4 subsequent siblings)
  8 siblings, 1 reply; 21+ messages in thread
From: Martin Zuther @ 2006-09-10 18:31 UTC (permalink / raw)
  To: linux-acpi

Hello everybody!

My system

  Kubuntu Dapper 6.06 LTS (packages updated regularly)
  Current kernel image of 2.6.15-26-686

  Mainboard: MSI 865PE Neo2-P
  Processor: Intel Pentium 4 2.8E GHz 800 MHz (Box)
  RAM: 3 x 512 MB DDR
  Video card: NVidia GeForce 5200 FX

  Keyboard: Logitech iTouch Internet
  Graphics tablet: Wacom Intuos A5

doesn't shut down properly. I remember having the same problem under
Debian 3.0, but as that encounter was somewhat short and is about a year
ago, the only thing I can remember is that it was a 2.6 kernel as well.

Kubuntu also claims that I have a partial ACPI installation ("not fully
installed" or something the like in "System Settings -> Laptop and Power
-> Laptop Battery -> Power Control").

This is probably related to "acpi -V" producing the error message "No
support for device type: thermal" and having almost no useful entries in
"/proc/acpi/...".

When I remove the boot option "quiet splash" I get the following
messages during shutdown:

  * Will now halt.
  [...] md: stopping all md devices
  [...] usb 4-2: new full speed USB device using uhci_hcd and address 3
  [...] usb 4-2: not running at top speed; connect to a high speed hub
  [...] Shutdown: hda
  [...]     ACPI-0517: *** Error: Method parse/execution failed
  [\SB_.PCI0.IDE0.GTM_] (Node dffe5d60), AE_AML_PACKAGE_LIMIT
  [...]     ACPI-0517: *** Error: Method parse/execution failed
  [\_SB_.PCI0.IDE0.CHN0._GTM] (Node dffe5fa0), AE_AML_PACKAGE_LIMIT
  [...]     Power down.
  [...]     acpi_power_off called

Then there's a click as my hard drives shut down, and that's about as
near as I ever get to shutting down my computer. The only thing working
at this stage are pressing the power button (for unusual 4 seconds) or
the reset button.

Also, when I reboot the computer from KDE, it does as told, but when in
the BIOS routines, there's a noticeable pause and a click when my two
S-ATA drives are checked. I don't have a problem like that when
rebooting Win XP (I have a dual boot system).

I had a look at several forums and had a go at fixing my DSDT.dsl (you
can find the original file at
http://www.ubuntuusers.de/paste/2441/?format=txt). As running the
recommended

  cp /boot/initrd.img-`uname -r` /boot/initrd.img-`uname -r`-acpifix
  echo -n "INITRDDSDT123DSDT123" >> /boot/initrd.img-`uname -r`-acpifix
  cat /boot/DSDT.aml >> /boot/initrd.img-`uname -r`-acpifix

failed to produce a bootable image, a found a workaround (and I'm a
little proud, being still new to Linux... <g>):

  sudo cp ~/DSDT.aml /etc/mkinitramfs/DSDT.aml
  sudo mkinitramfs -o /boot/initrd.img-`uname -r`-acpifix

After rebooting with such an image I find this in the syslog:

  [...] ACPI-0284: *** Info: Table [DSDT] replaced by host OS
  [...] ACPI: Looking for DSDT in initramfs... found /DSDT.aml ...
  successfully read 13614 bytes from /DSDT.aml
  [...] ACPI: Using customized DSDT

As this message vanishes when I run an original image, I think it has
worked.

Es scheint also geklapt zu haben. Zeit, sich dem Problem zuzuwenden -
ein Lauf von iasl -sa DSDT.sdl ergibt die folgende Meldung:

So here are the warnings I found when recompiling the DSDT:

  Intel ACPI Component Architecture
  ASL Optimizing Compiler version 20060707 [Jul 25 2006]
  Copyright (C) 2000 - 2006 Intel Corporation
  Supports ACPI Specification Revision 3.0a

  DSDT.dsl  4034:                 Method (STM, 0, Serialized)
  Warning  1086 -                           ^ Not all control
    paths return a value (STM_)

  DSDT.dsl  4359:     Method (_WAK, 1, NotSerialized)
  Warning  1079 -                ^ Reserved method must return a
    value (_WAK)

  ASL Input:  DSDT.dsl - 4458 lines, 150438 bytes, 1514 keywords
  AML Output: DSDT.aml - 13606 bytes 500 named objects 1014
    executable opcodes

  Compilation complete. 0 Errors, 2 Warnings, 0 Remarks,
    462 Optimizations

For the second warning I use the googled "standard solution"

  Return(Package(0x02){0x00, 0x00})

So the problem seems to lie within the first warning. As my machine code
knowledge is based on the Z80 and was lost somewhere years ago, I'd like
to ask for your help. I also checked the WWW and the ACPI spec for
ideas, but couldn't come up with anything useful.

Thanks for any help, as I don't seem to get any further on my own...

Martin
Germany
-- 
mz_mail@mzuther.de
www.mzuther.de
www.radix-musik.de


^ permalink raw reply	[flat|nested] 21+ messages in thread

* Sorry
  2006-09-10 18:31                   ` Yet another DSDL problem Martin Zuther
@ 2006-09-11  8:05                     ` Martin Zuther
  0 siblings, 0 replies; 21+ messages in thread
From: Martin Zuther @ 2006-09-11  8:05 UTC (permalink / raw)
  Cc: linux-acpi

Hi!

I'm sorry you got all these emails from me - I sent it over and over
again, as my email provider supplied me with lots of mailer daemon
errors. Naturally, I thought they were being deleted...

Anyway, thanks for any help I get!

Martin

^ permalink raw reply	[flat|nested] 21+ messages in thread

* Yet another DSDL problem
  2006-09-07 22:22                 ` Rafael J. Wysocki
                                     ` (3 preceding siblings ...)
  2006-09-10 18:31                   ` Yet another DSDL problem Martin Zuther
@ 2006-09-10 18:55                   ` Martin Zuther
  2006-09-10 19:37                   ` Yet another DSDT problem Martin Zuther
                                     ` (3 subsequent siblings)
  8 siblings, 0 replies; 21+ messages in thread
From: Martin Zuther @ 2006-09-10 18:55 UTC (permalink / raw)
  To: linux-acpi

Hi!

My system doesn't shut down properly.

  Kubuntu Dapper 6.06 LTS (packages updated regularly)
  Current kernel image of 2.6.15-26-686

  Mainboard: MSI 865PE Neo2-P
  Processor: Intel Pentium 4 2.8E GHz 800 MHz (Box)
  RAM: 3 x 512 MB DDR
  Video card: NVidia GeForce 5200 FX

  Keyboard: Logitech iTouch Internet
  Graphics tablet: Wacom Intuos A5

I remember having the same problem under
Debian 3.0, but as that encounter was somewhat short and is about a year
ago, the only thing I can remember is that it was a 2.6 kernel as well.

Kubuntu also claims that I have a partial ACPI installation ("not fully
installed" or something the like in "System Settings -> Laptop and Power
-> Laptop Battery -> Power Control").

This is probably related to "acpi -V" producing the error message "No
support for device type: thermal" and having almost no useful entries in
"/proc/acpi/...".

When I remove the boot option "quiet splash" I get the following
messages during shutdown:

  * Will now halt.
  [...] md: stopping all md devices
  [...] usb 4-2: new full speed USB device using uhci_hcd and address 3
  [...] usb 4-2: not running at top speed; connect to a high speed hub
  [...] Shutdown: hda
  [...]     ACPI-0517: *** Error: Method parse/execution failed
  [\SB_.PCI0.IDE0.GTM_] (Node dffe5d60), AE_AML_PACKAGE_LIMIT
  [...]     ACPI-0517: *** Error: Method parse/execution failed
  [\_SB_.PCI0.IDE0.CHN0._GTM] (Node dffe5fa0), AE_AML_PACKAGE_LIMIT
  [...]     Power down.
  [...]     acpi_power_off called

Then there's a click as my hard drives shut down, and that's about as
near as I ever get to shutting down my computer. The only thing working
at this stage are pressing the power button (for unusual 4 seconds) or
the reset button.

Also, when I reboot the computer from KDE, it does as told, but when in
the BIOS routines, there's a noticeable pause and a click when my two
S-ATA drives are checked. I don't have a problem like that when
rebooting Win XP (I have a dual boot system).

I had a look at several forums and had a go at fixing my DSDT.dsl (you
can find the original file at
http://www.ubuntuusers.de/paste/2441/?format=txt). As running the
recommended

  cp /boot/initrd.img-`uname -r` /boot/initrd.img-`uname -r`-acpifix
  echo -n "INITRDDSDT123DSDT123" >> /boot/initrd.img-`uname -r`-acpifix
  cat /boot/DSDT.aml >> /boot/initrd.img-`uname -r`-acpifix

failed to produce a bootable image, a found a workaround (and I'm a
little proud, being still new to Linux... <g>):

  sudo cp ~/DSDT.aml /etc/mkinitramfs/DSDT.aml
  sudo mkinitramfs -o /boot/initrd.img-`uname -r`-acpifix

After rebooting with such an image I find this in the syslog:

  [...] ACPI-0284: *** Info: Table [DSDT] replaced by host OS
  [...] ACPI: Looking for DSDT in initramfs... found /DSDT.aml ...
  successfully read 13614 bytes from /DSDT.aml
  [...] ACPI: Using customized DSDT

As this message vanishes when I run an original image, I think it has
worked.

Es scheint also geklapt zu haben. Zeit, sich dem Problem zuzuwenden -
ein Lauf von iasl -sa DSDT.sdl ergibt die folgende Meldung:

So here are the warnings I found when recompiling the DSDT:

  Intel ACPI Component Architecture
  ASL Optimizing Compiler version 20060707 [Jul 25 2006]
  Copyright (C) 2000 - 2006 Intel Corporation
  Supports ACPI Specification Revision 3.0a

  DSDT.dsl  4034:                 Method (STM, 0, Serialized)
  Warning  1086 -                           ^ Not all control
    paths return a value (STM_)

  DSDT.dsl  4359:     Method (_WAK, 1, NotSerialized)
  Warning  1079 -                ^ Reserved method must return a
    value (_WAK)

  ASL Input:  DSDT.dsl - 4458 lines, 150438 bytes, 1514 keywords
  AML Output: DSDT.aml - 13606 bytes 500 named objects 1014
    executable opcodes

  Compilation complete. 0 Errors, 2 Warnings, 0 Remarks,
    462 Optimizations

For the second warning I use the googled "standard solution"

  Return(Package(0x02){0x00, 0x00})

So the problem seems to lie within the first warning. As my machine code
knowledge is based on the Z80 and was lost somewhere years ago, I'd like
to ask for your help. I also checked the WWW and the ACPI spec for
ideas, but couldn't come up with anything useful.

Any help is deeply appreciated!

Martin
Germany
-- 
mz_mail@mzuther.de
www.mzuther.de
www.radix-musik.de

^ permalink raw reply	[flat|nested] 21+ messages in thread

* Yet another DSDT problem
  2006-09-07 22:22                 ` Rafael J. Wysocki
                                     ` (4 preceding siblings ...)
  2006-09-10 18:55                   ` Yet another DSDL problem Martin Zuther
@ 2006-09-10 19:37                   ` Martin Zuther
  2006-09-10 20:16                   ` Martin Zuther
                                     ` (2 subsequent siblings)
  8 siblings, 0 replies; 21+ messages in thread
From: Martin Zuther @ 2006-09-10 19:37 UTC (permalink / raw)
  To: linux-acpi

Dear list members,

my system doesn't shut down properly.

  Kubuntu Dapper 6.06 LTS (packages updated regularly)
  Current kernel image of 2.6.15-26-686

  Mainboard: MSI 865PE Neo2-P
  Processor: Intel Pentium 4 2.8E GHz 800 MHz (Box)
  RAM: 3 x 512 MB DDR
  Video card: NVidia GeForce 5200 FX

  Keyboard: Logitech iTouch Internet
  Graphics tablet: Wacom Intuos A5

I remember having the same problem under
Debian 3.0, but as that encounter was somewhat short and is about a year
ago, the only thing I can remember is that it was a 2.6 kernel as well.

Kubuntu also hints that I have a partial ACPI installation in "System
Settings - Laptop and Power
- Laptop Battery - Power Control".

This is probably related to "acpi -V" producing the error message "No
support for device type: thermal" and having almost no useful entries in
"/proc/acpi/...".

When I remove the boot option "quiet splash" I get the following
messages during shutdown:

  * Will now halt.
  [...] md: stopping all md devices
  [...] usb 4-2: new full speed USB device using uhci_hcd and address 3
  [...] usb 4-2: not running at top speed; connect to a high speed hub
  [...] Shutdown: hda
  [...]     ACPI-0517: *** Error: Method parse/execution failed
  [\SB_.PCI0.IDE0.GTM_] (Node dffe5d60), AE_AML_PACKAGE_LIMIT
  [...]     ACPI-0517: *** Error: Method parse/execution failed
  [\_SB_.PCI0.IDE0.CHN0._GTM] (Node dffe5fa0), AE_AML_PACKAGE_LIMIT
  [...]     Power down.
  [...]     acpi_power_off called

Then there's a click as my hard drives shut down, and that's about as
near as I ever get to shutting down my computer. The only thing working
at this stage are pressing the power button (for unusual 4 seconds) or
the reset button.

Also, when I reboot the computer from KDE, it does as told, but when in
the BIOS routines, there's a noticeable pause and a click when my two
S-ATA drives are checked. I don't have a problem like that when
rebooting Win XP (I have a dual boot system).

I had a look at several forums and had a go at fixing my DSDT.dsl (you
can find the original file at
http://www.ubuntuusers.de/paste/2441/?format=txt). As running the
recommended

  cp /boot/initrd.img-`uname -r` /boot/initrd.img-`uname -r`-acpifix
  echo -n "INITRDDSDT123DSDT123" >> /boot/initrd.img-`uname -r`-acpifix
  cat /boot/DSDT.aml >> /boot/initrd.img-`uname -r`-acpifix

failed to produce a bootable image, a found a workaround (and I'm a
little proud, being still new to Linux... <g>):

  sudo cp ~/DSDT.aml /etc/mkinitramfs/DSDT.aml
  sudo mkinitramfs -o /boot/initrd.img-`uname -r`-acpifix

After rebooting with such an image I find this in the syslog:

  [...] ACPI-0284: *** Info: Table [DSDT] replaced by host OS
  [...] ACPI: Looking for DSDT in initramfs... found /DSDT.aml ...
  successfully read 13614 bytes from /DSDT.aml
  [...] ACPI: Using customized DSDT

As this message vanishes when I run an original image, I think it has
worked.

Es scheint also geklapt zu haben. Zeit, sich dem Problem zuzuwenden -
ein Lauf von iasl -sa DSDT.sdl ergibt die folgende Meldung:

So here are the warnings I found when recompiling the DSDT:

  Intel ACPI Component Architecture
  ASL Optimizing Compiler version 20060707 [Jul 25 2006]
  Copyright (C) 2000 - 2006 Intel Corporation
  Supports ACPI Specification Revision 3.0a

  DSDT.dsl  4034:                 Method (STM, 0, Serialized)
  Warning  1086 -                           ^ Not all control
    paths return a value (STM_)

  DSDT.dsl  4359:     Method (_WAK, 1, NotSerialized)
  Warning  1079 -                ^ Reserved method must return a
    value (_WAK)

  ASL Input:  DSDT.dsl - 4458 lines, 150438 bytes, 1514 keywords
  AML Output: DSDT.aml - 13606 bytes 500 named objects 1014
    executable opcodes

  Compilation complete. 0 Errors, 2 Warnings, 0 Remarks,
    462 Optimizations

For the second warning I use the googled "standard solution"

  Return(Package(0x02){0x00, 0x00})

So the problem seems to lie within the first warning. As my machine code
knowledge is based on the Z80 and was lost somewhere years ago, I'd like
to ask for your help. I also checked the WWW and the ACPI spec for
ideas, but couldn't come up with anything useful.

Any help is deeply appreciated!

Martin

-- 
mz_mail@mzuther.de
www.mzuther.de
www.radix-musik.de

^ permalink raw reply	[flat|nested] 21+ messages in thread

* Yet another DSDT problem
  2006-09-07 22:22                 ` Rafael J. Wysocki
                                     ` (5 preceding siblings ...)
  2006-09-10 19:37                   ` Yet another DSDT problem Martin Zuther
@ 2006-09-10 20:16                   ` Martin Zuther
  2006-09-10 20:19                   ` Martin Zuther
  2006-09-10 20:43                   ` Martin Zuther
  8 siblings, 0 replies; 21+ messages in thread
From: Martin Zuther @ 2006-09-10 20:16 UTC (permalink / raw)
  To: linux-acpi

Hi,

this is a test, as I'm having real problems sending my problem and it's
probably a single word that keeps my message from being sent to this list.

In case it works I'll try to send my message again.

Martin


^ permalink raw reply	[flat|nested] 21+ messages in thread

* Yet another DSDT problem
  2006-09-07 22:22                 ` Rafael J. Wysocki
                                     ` (6 preceding siblings ...)
  2006-09-10 20:16                   ` Martin Zuther
@ 2006-09-10 20:19                   ` Martin Zuther
  2006-09-10 20:43                   ` Martin Zuther
  8 siblings, 0 replies; 21+ messages in thread
From: Martin Zuther @ 2006-09-10 20:19 UTC (permalink / raw)
  To: linux-acpi

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Dear list members,

my system doesn't shut down properly.

  Kubuntu Dapper 6.06 LTS (packages updated regularly)
  Current kernel image of 2.6.15-26-686

  Mainboard: MSI 865PE Neo2-P
  Processor: Intel Pentium 4 2.8E GHz 800 MHz (Box)
  RAM: 3 x 512 MB DDR
  Video card: NVidia GeForce 5200 FX

  Keyboard: Logitech iTouch Internet
  Graphics tablet: Wacom Intuos A5

I remember having the same problem under
Debian 3.0, but as that encounter was somewhat short and is about a year
ago, the only thing I can remember is that it was a 2.6 kernel as well.

Kubuntu also hints that I have a partial ACPI installation in "System
Settings - Laptop and Power
- - Laptop Battery - Power Control".

This is probably related to "acpi -V" producing the error message "No
support for device type: thermal" and having almost no useful entries in
"/proc/acpi/...".

When I remove the boot option "quiet splash" I get the following
messages during shutdown:

  * Will now halt.
  md: stopping all md devices
  usb 4-2: new full speed USB device using uhci_hcd and address 3
  usb 4-2: not running at top speed; connect to a high speed hub
  Shutdown: hda
  ACPI-0517: *** Error: Method parse/execution failed
  [SB_.PCI0.IDE0.GTM_] (Node dffe5d60), AE_AML_PACKAGE_LIMIT
  ACPI-0517: *** Error: Method parse/execution failed
  [_SB_.PCI0.IDE0.CHN0._GTM (Node dffe5fa0), AE_AML_PACKAGE_LIMIT
  Power down.
  acpi_power_off called

Then there's a click as my hard drives shut down, and that's about as
near as I ever get to shutting down my computer. The only thing working
at this stage are pressing the power button (for unusual 4 seconds) or
the reset button.

Also, when I reboot the computer from KDE, it does as told, but when in
the BIOS routines, there's a noticeable pause and a click when my two
S-ATA drives are checked. I don't have a problem like that when
rebooting Win XP (I have a dual boot system).

I had a look at several forums and had a go at fixing my DSDT.dsl (you
can find the original file at
http://www.ubuntuusers.de/paste/2441/?format=txt). As running the
recommended method for including a new DSDT failed to produce a bootable
image, a found a workaround (and I'm a little proud, being still new to
Linux... <g>):

  sudo cp ~/DSDT.aml /etc/mkinitramfs/DSDT.aml
  sudo mkinitramfs -o /boot/initrd.img-`uname -r`-acpifix

After rebooting with such an image I find this in the syslog:

  ACPI-0284: *** Info: Table [DSDT] replaced by host OS
  ACPI: Looking for DSDT in initramfs... found /DSDT.aml ...
  successfully read 13614 bytes from /DSDT.aml
  ACPI: Using customized DSDT

As this message vanishes when I run an original image, I think it has
worked.

Es scheint also geklapt zu haben. Zeit, sich dem Problem zuzuwenden -
ein Lauf von iasl -sa DSDT.sdl ergibt die folgende Meldung:

So here are the warnings I found when recompiling the DSDT:

  DSDT.dsl  4034:                 Method (STM, 0, Serialized)
  Warning  1086 -                           ^ Not all control
    paths return a value (STM_)

  DSDT.dsl  4359:     Method (_WAK, 1, NotSerialized)
  Warning  1079 -                ^ Reserved method must return a
    value (_WAK)

  ASL Input:  DSDT.dsl - 4458 lines, 150438 bytes, 1514 keywords
  AML Output: DSDT.aml - 13606 bytes 500 named objects 1014
    executable opcodes

  Compilation complete. 0 Errors, 2 Warnings, 0 Remarks,
    462 Optimizations

For the second warning I use the googled "standard solution"

  Return(Package(0x02){0x00, 0x00})

So the problem seems to lie within the first warning. As my machine code
knowledge is based on the Z80 and was lost somewhere years ago, I'd like
to ask for your help. I also checked the WWW and the ACPI spec for
ideas, but couldn't come up with anything useful.

Any help is deeply appreciated!

Martin
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFBHNOx8z6qIGmGv0RAsFfAJ90hHJN7Wbvntht5JUtY03smP+4TQCeObZB
zoCa37FxWn2A/+VmdwrdeiE=
=n1LD
-----END PGP SIGNATURE-----

^ permalink raw reply	[flat|nested] 21+ messages in thread

* Yet another DSDT problem
  2006-09-07 22:22                 ` Rafael J. Wysocki
                                     ` (7 preceding siblings ...)
  2006-09-10 20:19                   ` Martin Zuther
@ 2006-09-10 20:43                   ` Martin Zuther
  8 siblings, 0 replies; 21+ messages in thread
From: Martin Zuther @ 2006-09-10 20:43 UTC (permalink / raw)
  To: linux-acpi

Dear list members,

It doesn't seem to work. So I'll only give a synopsis of my problem here
- the full problem report can be found at:

  http://www.mzuther.de/data/linux-acpi_01.txt

while the original DSDT is here:

  http://www.ubuntuusers.de/paste/2441/?format=txt

My system doesn't shut down properly. Kubuntu also hints that I have a
partial ACPI installation, which is probably related to "acpi -V"
producing the error message "No support for device type: thermal"...

On shutdown my hard drives click, and that's about as near as I ever get
to shutting down my computer. The only thing working at this stage are
pressing the power or reset button.

Also, when I reboot the computer from KDE, it does as told, but when in
the BIOS routines, there's a noticeable pause and a click when my two
S-ATA drives are checked. I don't have a problem like that when
rebooting other OS's.

Here are the warnings I found when recompiling the DSDT:

  Warning  1086 - Not all control paths return a value (STM_)

  Warning  1079 - Reserved method must return a value (_WAK)

For the second warning I use the googled "standard solution", so the
problem seems to lie within the first warning. As my machine code
knowledge is based on the Z80 and was lost somewhere years ago, I'd like
to ask for your help. I also checked the WWW and the ACPI spec for
ideas, but couldn't come up with anything useful.

Any help is deeply appreciated!

Martin

^ permalink raw reply	[flat|nested] 21+ messages in thread

end of thread, other threads:[~2006-09-11  8:02 UTC | newest]

Thread overview: 21+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-09-04 11:32 Problem with resuming ATI SATA on HPC nx6325 Rafael J. Wysocki
2006-09-05  6:24 ` Pavel Machek
2006-09-05 11:38   ` Rafael J. Wysocki
2006-09-06 10:42     ` Pavel Machek
2006-09-06 20:47       ` Rafael J. Wysocki
2006-09-06 21:12         ` Pavel Machek
2006-09-07  7:03           ` Rafael J. Wysocki
2006-09-07 10:34             ` Rafael J. Wysocki
2006-09-07 22:08               ` Pavel Machek
2006-09-07 22:22                 ` Rafael J. Wysocki
2006-09-08 14:14                   ` Rafael J. Wysocki
2006-09-08 15:49                   ` Pavel Machek
2006-09-08 23:27                     ` Rafael J. Wysocki
2006-09-10 16:01                   ` Martin Zuther
2006-09-10 18:31                   ` Yet another DSDL problem Martin Zuther
2006-09-11  8:05                     ` Sorry Martin Zuther
2006-09-10 18:55                   ` Yet another DSDL problem Martin Zuther
2006-09-10 19:37                   ` Yet another DSDT problem Martin Zuther
2006-09-10 20:16                   ` Martin Zuther
2006-09-10 20:19                   ` Martin Zuther
2006-09-10 20:43                   ` Martin Zuther

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox