Bugzilla Bug 165815

I have Gigabyte 965P-DS4 with ICH8R and additional JMicron 363 for IDE support.
In 2.6.19-gentoo-r4 suspending worked fine. In 2.6.20 I'm getting next messages
in dmesg:
ata9: suspend failed, device 0 still active
pci_device_suspend(): ata_pci_device_suspend+0x0/0x50() returns -16
suspend_device(): pci_device_suspend+0x0/0x80() returns -16
Could not suspend device 0000:04:00.1: error -16

and echo disk >/sys/power/state fails with write error

lspci output:
04:00.0 SATA controller: JMicron Technologies, Inc. JMicron 20360/20363 AHCI
Controller (rev 02)
04:00.1 IDE interface: JMicron Technologies, Inc. JMicron 20360/20363 AHCI
Controller (rev 02)

boot time dmesg:
ata9: PATA max UDMA/100 cmd 0xA000 ctl 0xA402 bmdma 0xB000 irq 18
ata10: PATA max UDMA/100 cmd 0xA800 ctl 0xAC02 bmdma 0xB008 irq 18
scsi8 : pata_jmicron
ata9.00: ATAPI, max UDMA/33
ata9.00: configured for UDMA/33
scsi9 : pata_jmicron
ATA: abnormal status 0x7F on port 0xA807
scsi 8:0:0:0: CD-ROM            HL-DT-ST DVDRAM GSA-4163B A106 PQ: 0 ANSI: 5
sr0: scsi3-mmc drive: 40x/40x writer dvd-ram cd/rw xa/form2 cdda tray
sr 8:0:0:0: Attached scsi CD-ROM sr0
sr 8:0:0:0: Attached scsi generic sg1 type 5

but if I've removed pata_jmicron module, than suspending works fine.
I'd tried to remove recent pata_jmicron and quirks patch that was introduced in
2.6.20 compared to 2.6.19, but this didn't helped

Did you use pata_jmicron under 2.6.19?

(In reply to comment #1)
> Did you use pata_jmicron under 2.6.19?
> 
yes, I did

same error message
#echo standby >/sys/power/state
bash: echo: write error: Resource temporarily unavailable
# cat /sys/power/state
standby

(In reply to comment #3)
> same error message
> #echo standby >/sys/power/state
> bash: echo: write error: Resource temporarily unavailable
> # cat /sys/power/state
> standby
> 

should i open another but for my problem?

(In reply to comment #4)
> (In reply to comment #3)
> > same error message
> > #echo standby >/sys/power/state
> > bash: echo: write error: Resource temporarily unavailable
> > # cat /sys/power/state
> > standby
> > 
> 
> should i open another but for my problem?
> 

i use do not use pata jmicron but VIA PATA that isn't experimental or whatever

GNUtoo, open a new bug
Max, please reproduce with 2.6.21-rc1

(In reply to comment #6)
> Max, please reproduce with 2.6.21-rc1
With pata_jmicron loaded situation is the same, but with unloaded module it is
even worse - it is just can't be suspended and after switching off the screen,
and the lan, it is waiting for watchdog reboot or AltSysRQ.

btw, 2.6.20 when going to suspend don't turned off the lan so i can see link
light on my router, and when I push power on button on the case than the system
starts than turning off itself and never going POST OK. To boot it in resume
mode or any i needed to turn off power switch until disappearing of the link
signal from that sysem on the router, but after resume the network is very
unstable, some packets is silently dropping e.t.c; normal rebooting fixes that.
So there may be second problem with net hardware because in 2.6.21-rc1 I see
that the lan has switched off, but after that system doesn't go to poweroff
state.

Any chance you can reproduce on 2.6.21-rc5? Suspend issues should be mostly
fixed now so hopefully you can at least suspend without pata_jmicron...

(In reply to comment #8)
> Any chance you can reproduce on 2.6.21-rc5? Suspend issues should be mostly
> fixed now so hopefully you can at least suspend without pata_jmicron...
> 

yes,in rc5 pata_jmicron doesn't prevent suspending anymore, but i still have a
bunch of problems with suspend, but this is another story^Wbug, and i'll start
to test it when 2.6.21 would be released.

OK, i'm marking this as fixed because the libata pata drivers are still
experimental.

You should open new bugs for your 2.6.21-rc5 issues at
http://bugzilla.kernel.org. The idea of -rc releases is that bugs get fixed
before it goes final.