From: Zhang Rui <rui.zhang@intel.com>
To: jgarzik@pobox.com, forrest.zhao@gmail.com, kristen.c.accardi@intel.com
Cc: linux-ide@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: sata driver fails to work after resume from S3
Date: Fri, 26 Jan 2007 15:46:42 +0800 [thread overview]
Message-ID: <1169797602.25758.85.camel@localhost.localdomain> (raw)
Hi,
I met a problem that sata driver fails to work after resume from S3.
The kernel version is 2.6.16.33.
After resume from S3,
I got the following messages:
First, "ATA: abnormal status 0x80 on port 0x1F7" for 3 times.
Then, "sd 0:0:0(sometimes is 1):0: SCSI error: return code=0x40000
end_request: I/O error, dev sdb, sector ....
Buffer I/O error on device dm-0, logical block...
lost page write due to I/O error on device dm-0"
keeps on popping up.
Finally I got a message saying that "Remounting filesystem read-only"
and can't access the disk any more.
The problem is exactly like bug6262 in bugzilla, except for
this happens when I set SATA mode to "compatibility"(not "AHCI").
I can confirm that it is fixed in the 2.6.18.
But how to make SATA drive S3 work properly in 2.6.16.33?
I found several similar bugs, but the final conclusion I got is
"This is fixed in linux-2.6.18..." and I can not find the original patches
against this problem.
I think the patch set "ACPI support for SATA/PATA" from Forrest and
updated by Kristen may be helpful. But I can't apply them to 2.6.16.33
due to too much changes in sata driver.
Do I need to open a bug report in bugzilla?
Does the patch set really make sense to my problem?
If so, any patch I should apply first?
If not, which patches I should test?
Is there anyone who could show me what I should do please?
Any comment is appreciated. Thanks in advance.
Thanks,
Rui
next reply other threads:[~2007-01-26 7:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-26 7:46 Zhang Rui [this message]
2007-01-30 3:09 ` sata driver fails to work after resume from S3 Tejun Heo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1169797602.25758.85.camel@localhost.localdomain \
--to=rui.zhang@intel.com \
--cc=forrest.zhao@gmail.com \
--cc=jgarzik@pobox.com \
--cc=kristen.c.accardi@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-ide@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).