From: Daniel Phillips <phillips@innominate.de>
To: Vedran Rodic <vedran@renata.irb.hr>, linux-kernel@vger.kernel.org
Subject: Re: 2.4.0-prerelease problems (it corrupted my ext2 filesystem)
Date: Tue, 02 Jan 2001 16:20:16 +0100 [thread overview]
Message-ID: <3A51F1B0.3AD38F9F@innominate.de> (raw)
In-Reply-To: <20010102131507.A7573@renata.irb.hr> <3A51D9BF.23C42DFE@innominate.de> <20010102152409.A10863@renata.irb.hr>
Vedran Rodic wrote:
> On Tue, Jan 02, 2001 at 02:38:07PM +0100, Daniel Phillips wrote:
> > Could you provide details of your configuration?
>
> I put the complete kernel log of that session at http://quark.fsb.hr/~vrodic/kern.log
>
> I scanned my swap device several times today with badblocks -w, and
> it didn't show any errors. I also did some RAM tests with memtest86,
> again with no errors.
>
> If you need more details, just ask.
Are you still running 2.4.0-pre? Can you reproduce the problem? Does
the problem occur only with v4l? Did you back up your files?
BTW, while spelunking the swap code I noticed this oddity:
pte_t pte_mkdirty(pte_t pte) { (pte).pte_low |= _PAGE_DIRTY; return
pte; }
and similarly for 10 or so other functions - these functions just return
the passed pte, and reassign it to the pte orginally passed. :-/ This
dates from version 1.2.13.
--
Daniel
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-02 15:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-02 12:15 2.4.0-prerelease problems (it corrupted my ext2 filesystem) Vedran Rodic
2001-01-02 13:38 ` Daniel Phillips
2001-01-02 14:24 ` Vedran Rodic
2001-01-02 15:20 ` Daniel Phillips [this message]
2001-01-02 17:07 ` Vedran Rodic
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=3A51F1B0.3AD38F9F@innominate.de \
--to=phillips@innominate.de \
--cc=linux-kernel@vger.kernel.org \
--cc=vedran@renata.irb.hr \
/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.