« Return to Thread: "EXT3-fs error" after resume from s2ram

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

by Robert Hancock-4 :: Rate this Message:

Reply to Author | View in Thread

On 06/29/2009 11:37 PM, Christof Warlich wrote:

> 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?

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..

>
> 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..
>

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

 « Return to Thread: "EXT3-fs error" after resume from s2ram