From: Mathieu LESNIAK <maverick@eskuel.net>
To: Pavel Machek <pavel@ucw.cz>
Cc: linux-kernel@vger.kernel.org, mochel@osdl.org
Subject: Re: Fs corruption with swsusp in test4-mm6 ?
Date: Sun, 07 Sep 2003 10:06:03 +0200 [thread overview]
Message-ID: <3F5AE6EB.4000308@eskuel.net> (raw)
In-Reply-To: <20030906212206.GA26916@atrey.karlin.mff.cuni.cz>
Hi,
Pavel Machek wrote:
> Hi!
>
>
>
>>I've tested the latest -mm6 kernel on a Compaq Presario 2157EA laptop
>>(Celeron Mobile 2GHz)
>>Everything worked fine until I tested suspend to disk. After resuming,
>>I've got random messages about reiserfs problem on the console :
>>
>>vs-4080: reiserfs_free_block: free_block (hda2:95121)[dev:blocknr]: bit
>>already cleared
>>Sep 6 10:30:51 herrbach kernel: vs-4080: reiserfs_free_block:
>>free_block (hda2:95122)[dev:blocknr]: bit already cleared
>>Sep 6 10:30:58 herrbach kernel: vs-13060: reiserfs_update_sd: stat data
>>of object [689 645 0x0 SD] (nlink == 1) not found (pos 25)
>>Sep 6 10:30:58 herrbach kernel: vs-13060: reiserfs_update_sd: stat data
>>of object [689 652 0x0 SD] (nlink == 1) not found (pos 25)
>>
>>Please find in attachement 1 syslog showing the suspend / resume cycle
>>and the fs errors.
>
>
> Be sure to reboot then run reiserfsck.
>
> OHCI lacks suspend/resume support. Turn it off. ... ... but it should
> not do this kind of corruption. Can you reproduce this without OHCI?
> Can you try -test3?
> Pavel
>
When I tested -test3 a few week ago, I hadn't got this problem.
Mathieu LESNIAK
next prev parent reply other threads:[~2003-09-07 8:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-06 9:29 Fs corruption with swsusp in test4-mm6 ? Mathieu LESNIAK
2003-09-06 21:22 ` Pavel Machek
2003-09-07 8:06 ` Mathieu LESNIAK [this message]
2003-09-07 13:32 ` Pavel Machek
2003-09-08 19:41 ` Patrick Mochel
2003-09-08 20:11 ` Mathieu LESNIAK
2003-09-08 20:11 ` Patrick Mochel
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=3F5AE6EB.4000308@eskuel.net \
--to=maverick@eskuel.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@osdl.org \
--cc=pavel@ucw.cz \
/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