linux-kernel - Re: "EXT3-fs error" after resume from s2ram

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 9 Jul 2009 17:31:36 -0600
From:	Robert Hancock <hancockrwd@...il.com>
To:	Christof Warlich <christof@...lich.name>
Cc:	Tejun Heo <htejun@...il.com>, linux-kernel@...r.kernel.org,
	ide <linux-ide@...r.kernel.org>
Subject: Re: "EXT3-fs error" after resume from s2ram

On Thu, Jul 9, 2009 at 12:17 PM, Christof Warlich<christof@...lich.name> wrote:
> Hi Tejun, Robert,
>
> hey, great: Suspend to ram seems to work like a charm now! Many thanks to
> Robert for taking the time to identify the root cause and to Tejun for
> providing the patch.
>
> I've attached both boot and suspend / resume messages from
> /var/log/kern.log, just let me know if I can do anything else to
> help getting the patch into an official kernel release. Furthermore, I would
> be happy to be kept posted on the progress being made regarding this.
>
> Just one clarification: From what I understood so far, it will be impossible
> to ever utilize the full disk capacity as long as the BIOS applies the HPA
> on boot, right?

I believe that's the case, yes.. if the BIOS is applying the HPA on
each boot, then we can't change the max address again without a
hardware reset..
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/