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:	Tue, 30 Jun 2009 07:37:32 +0200
From:	Christof Warlich <christof@...lich.name>
To:	Robert Hancock <hancockrwd@...il.com>
CC:	linux-kernel@...r.kernel.org
Subject: Re: "EXT3-fs error" after resume from s2ram

No, really nothing else but these EXT3-fs error messages are printed to vt1,
and as the disk is not accessible,  nothing can be found in 
/var/log/kern.log either.

With respect to libata and SCSI and on a normal system boot, 
/var/log/kern.log just
contains:

SCSI subsystem initialized
libata version 3.00 loaded.

so nothing helpful either.  Do you want me to send an entire boot - 
suspend cycle
from /var/log/kern.log?

Robert Hancock schrieb:
> Hmm.. How about any normal output from the libata, scsi, etc? Seems 
> odd you wouldn't get anything unusual there if the file system was 
> complaining..

View attachment "christof.vcf" of type "text/x-vcard" (279 bytes)