All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christof Warlich <christof@warlich.name>
To: Robert Hancock <hancockrwd@gmail.com>
Cc: linux-kernel@vger.kernel.org, ide <linux-ide@vger.kernel.org>
Subject: Re: "EXT3-fs error" after resume from s2ram
Date: Tue, 07 Jul 2009 19:42:02 +0200	[thread overview]
Message-ID: <4A5388EA.7030503@warlich.name> (raw)
In-Reply-To: <4A535973.9090206@gmail.com>

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

Robert Hancock schrieb:
> On 07/07/2009 03:13 AM, Christof Warlich wrote:
>> Christof Warlich schrieb:
>>> Do you think I can fix the issue and circumvent the BIOS by passing
>>> the real geomerty of the drive as kernel boot parameters? This may
>>> also have the nice side effect that I could utilize the full capacity
>>> of the drive. I'll definitly do some experiments in this direction and
>>> let you know immediately if I succeed. Please let me know if this may
>>> be a waste of time or if you know an appropriate fix.
>> I retried with the boot parameter hda=16383,16,63 according to the
>> values that I got from fdisk, but without success. Anyway, I would have
>> expected that the kernel may have had a way to set the LBA48 geometry
>> instead of CHS, but it looks like I'm on the wrong track here...
>
> That's an old IDE parameter, not a libata one, and 160GB is way too 
> large to be settable using CHS. What you likely want to do is pass the 
> ignore_hpa=1 option to libata when it's loaded - either 
> libata.ignore_hpa=1 on kernel command line, or in /etc/modprobe.conf 
> if it's a module (how exactly to do this depends on your 
> distribution). That way the protected area on the disk will get 
> disabled and you can use the full capacity.
Hmm - that doen't seem to fix it :-(:

After the reboot, fdisk still reports 137.4GB, and dmesg now contains 
the line:

ata1.00: device aborted resize (268435456 -> 312581808), skipping HPA 
handling

instead of

ata1.00: HPA detected: current 268435456, native 312581808

that we have seen without the libata.ignore_hpa=1 kernel command line 
option.

After s2ram -f -p, I still see the EXT3-fs error on resume. Is it worth 
to take another log from this suspend /resume cycle?

[-- Attachment #2: christof.vcf --]
[-- Type: text/x-vcard, Size: 278 bytes --]

begin:vcard
fn:Christof Warlich
n:Warlich;Christof
org:Warlich Consulting
adr:;;Am Haselhang 7;Hilpoltstein;Bayern;91161;Deutschland
email;internet:christof@warlich.name
tel;work:09174/492914
tel;home:09174/492914
x-mozilla-html:TRUE
url:www.warlich.name
version:2.1
end:vcard


  reply	other threads:[~2009-07-07 17:42 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-28 13:37 "EXT3-fs error" after resume from s2ram Christof Warlich
2009-06-29  0:18 ` Robert Hancock
2009-06-29 13:54   ` Christof Warlich
2009-06-30  0:28     ` Robert Hancock
2009-06-30  5:37       ` Christof Warlich
2009-07-02  5:17         ` Robert Hancock
2009-07-06  9:51           ` Christof Warlich
2009-07-07  0:13             ` Robert Hancock
2009-07-07  7:04               ` Christof Warlich
2009-07-07  9:13                 ` Christof Warlich
2009-07-07 14:19                   ` Robert Hancock
2009-07-07 17:42                     ` Christof Warlich [this message]
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
2009-07-09 23:19         ` Pavel Machek

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=4A5388EA.7030503@warlich.name \
    --to=christof@warlich.name \
    --cc=hancockrwd@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.