From: Francesco VIRLINZI <francesco.virlinzi@st.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: linux-pm@lists.linux-foundation.org
Subject: Re: Problem on Suspend to RAM vs ext3
Date: Mon, 16 Jun 2008 15:32:44 +0200 [thread overview]
Message-ID: <48566B7C.4090903@st.com> (raw)
In-Reply-To: <200806161530.49979.rjw@sisk.pl>
Hi Rafael
I will try to update my kernel
> This is a problem with the SATA driver IMO. There's a good chance it's been
> fixed in one of the more recent kernels.
>
> Please try 2.6.25.x.
>
Thanks for your support
Regards
Francesco
> Thanks,
> Rafael
>
>
>
>> sd 0:0:1:0: [sda] Starting disk
>> ata1.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
>> ata1.01: cmd 40/00:01:00:00:00/00:00:00:00:00/f0 tag 0 cdb 0x0 data 0
>> res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
>> ata1: port is slow to respond, please be patient (Status 0xd0)
>> ata1: device not ready (errno=-16), forcing hardreset
>> ata1: soft resetting port
>> ata1.01: failed to IDENTIFY (I/O error, err_mask=0x3)
>> ata1.01: revalidation failed (errno=-5)
>> ata1: failed to recover some devices, retrying in 5 secs
>> ata1: soft resetting port
>> ata1.01: failed to IDENTIFY (I/O error, err_mask=0x3)
>> ata1.01: revalidation failed (errno=-5)
>> ata1.01: limiting speed to UDMA7:PIO5
>> ata1: failed to recover some devices, retrying in 5 secs
>> ata1: soft resetting port
>> ata1.01: failed to IDENTIFY (I/O error, err_mask=0x3)
>> ata1.01: revalidation failed (errno=-5)
>> ata1.01: disabled
>> ata1: EH pending after completion, repeating EH (cnt=4)
>> ata1: soft resetting port
>> ata1: EH complete
>> sd 0:0:1:0: [sda] START_STOP FAILED
>> sd 0:0:1:0: [sda] Result: hostbyte=0x04 driverbyte=0x00
>> Restarting tasks ... done.
>> sd 0:0:1:0: [sda] Result: hostbyte=0x04 driverbyte=0x00
>> end_request: I/O error, dev sda, sector 6042767
>> Buffer I/O error on device sda1, logical block 755338
>> lost page write due to I/O error on sda1
>> sd 0:0:1:0: [sda] Result: hostbyte=0x04 driverbyte=0x00
>> end_request: I/O error, dev sda, sector 6042927
>> Buffer I/O error on device sda1, logical block 755358
>> lost page write due to I/O error on sda1
>> sd 0:0:1:0: [sda] Result: hostbyte=0x04 driverbyte=0x00
>> end_request: I/O error, dev sda, sector 6042839
>> Buffer I/O error on device sda1, logical block 755347
>> lost page write due to I/O error on sda1
>> Aborting journal on device sda1.
>> ext3_abort called.
>> EXT3-fs error (device sda1): ext3_journal_start_sb: Detected aborted
>> journal
>> Remounting filesystem read-only
>> sd 0:0:1:0: [sda] Result: hostbyte=0x04 driverbyte=0x00
>> end_request: I/O error, dev sda, sector 5767247
>> Buffer I/O error on device sda1, logical block 720898
>> lost page write due to I/O error on sda1
>> sd 0:0:1:0: [sda] Result: hostbyte=0x04 driverbyte=0x00
>> end_request: I/O error, dev sda, sector 7140655
>>
>
>
prev parent reply other threads:[~2008-06-16 13:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-16 6:50 Problem on Suspend to RAM vs ext3 Francesco VIRLINZI
2008-06-16 12:58 ` Rafael J. Wysocki
2008-06-16 13:22 ` Francesco VIRLINZI
2008-06-16 13:30 ` Rafael J. Wysocki
2008-06-16 13:32 ` Francesco VIRLINZI [this message]
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=48566B7C.4090903@st.com \
--to=francesco.virlinzi@st.com \
--cc=linux-pm@lists.linux-foundation.org \
--cc=rjw@sisk.pl \
/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