linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Robert Hancock <hancockrwd@gmail.com>
To: Christof Warlich <christof@warlich.name>
Cc: linux-kernel@vger.kernel.org, ide <linux-ide@vger.kernel.org>
Subject: Re: "EXT3-fs error" after resume from s2ram
Date: Mon, 06 Jul 2009 18:13:17 -0600	[thread overview]
Message-ID: <4A52931D.5070109@gmail.com> (raw)
In-Reply-To: <4A51C929.5010909@warlich.name>

(ccing linux-ide)

On 07/06/2009 03:51 AM, Christof Warlich wrote:
> Robert Hancock schrieb:
>> There should definitely be some libata messages from the
>> suspend/resume process, they might not end up in that file though. You
>> might want to try changing the console loglevel before suspend so that
>> all kernel messages get displayed..
>
> Ok, I got the suspend / resume process logged quite complete now, it
> took me some time though to save the data due to the inaccessibility of
> the root filesystem after resume. But (a modified version of) netcat
> finally was my friend :-).
>
> So below you'll find all messages from "kern.*" between the point when
> calling "s2ram -f -p" up to the point when the system is back. The
> requested libata messages are included. Please let me know if any
> additional data would help.
> Jul 6 09:15:40 fossie kernel: [ 314.072707] WARNING: at
> /home/kernel-ppa/mainline/build/kernel/smp.c:289
> smp_call_function_single+0xa9/0x100()
> Jul 6 09:15:40 fossie kernel: [ 314.072707] WARNING: at
> /home/kernel-ppa/mainline/build/kernel/smp.c:289
> smp_call_function_single+0xa9/0x100()

This WARN should likely be looked at by someone, but it doesn't seem to 
be the main culprit.

> Jul 6 09:15:41 fossie kernel: [ 316.648468] ata1.00: ACPI cmd
> ef/03:0c:00:00:00:a0 filtered out
> Jul 6 09:15:41 fossie kernel: [ 316.648468] ata1.00: ACPI cmd
> ef/03:0c:00:00:00:a0 filtered out
> Jul 6 09:15:41 fossie kernel: [ 316.648480] ata1.00: ACPI cmd
> ef/03:45:00:00:00:a0 filtered out
> Jul 6 09:15:41 fossie kernel: [ 316.648480] ata1.00: ACPI cmd
> ef/03:45:00:00:00:a0 filtered out
> Jul 6 09:15:41 fossie kernel: [ 316.659047] ata1.00: n_sectors mismatch
> 268435456 != 312581808
> Jul 6 09:15:41 fossie kernel: [ 316.659047] ata1.00: n_sectors mismatch
> 268435456 != 312581808
> Jul 6 09:15:41 fossie kernel: [ 316.659054] ata1.00: revalidation failed
> (errno=-19)

This is why the hard disk failed to resume, somehow the drive shows a 
capacity of 149GB after resume but only 128GB before. What's the actual 
capacity of the drive? I suspect the drive has a host protected area on 
it, and somehow the HPA isn't showing up after we resume.

Can you post the dmesg log from normal bootup?

       reply	other threads:[~2009-07-07  0:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4A4771FD.1020207@warlich.name>
     [not found] ` <4A480859.5010206@gmail.com>
     [not found]   ` <4A48C799.2010102@warlich.name>
     [not found]     ` <4A495C2D.1040706@gmail.com>
     [not found]       ` <4A49A49C.10104@warlich.name>
     [not found]         ` <4A4C42E2.6030305@gmail.com>
     [not found]           ` <4A51C929.5010909@warlich.name>
2009-07-07  0:13             ` Robert Hancock [this message]
2009-07-07  7:04               ` "EXT3-fs error" after resume from s2ram Christof Warlich
2009-07-07  9:13                 ` Christof Warlich
2009-07-07 14:19                   ` Robert Hancock
2009-07-07 17:42                     ` Christof Warlich
2009-07-07 23:30                       ` Robert Hancock
2009-07-08  6:41                         ` Christof Warlich
2009-07-08 14:28                           ` Tejun Heo
2009-07-08 15:21                             ` Tejun Heo
2009-07-09 18:17                               ` Christof Warlich
2009-07-09 23:31                                 ` Robert Hancock
2009-07-10 13:21                                   ` Tejun Heo
2009-07-08 15:50                             ` Christof Warlich

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=4A52931D.5070109@gmail.com \
    --to=hancockrwd@gmail.com \
    --cc=christof@warlich.name \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@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).