All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Luis Miguel García" <ktech@wanadoo.es>
To: linux-kernel@vger.kernel.org
Subject: DATA CORRUPTION in 2.6.1 and 2.6.2-rc1 (not in 2.6.0-mm2)
Date: Fri, 23 Jan 2004 20:29:36 +0100	[thread overview]
Message-ID: <40117620.6040103@wanadoo.es> (raw)

Hello:

(sorry with my _very_ poor english)

I've been using 2.6.0-mm2 since it appears with almost no problems 
(besides bttv not giving me audio out).

When I switched to 2.6.1 for the first time, I have just booted and a 
lookup blocked my computer. When I have hand-reseted it, I realized that 
some files was filled with garbage. In fact, modules.autoload was in 
this way.

Because of this, I reverted to 2.6.0-mm2 and newly no problems in a while.

Today, I have builded 2.6.2-rc1 and the same has happened. A hard lookup 
and lots of files were screwed from my /home directory. Xfce has no 
configuration files and Firebird says "Welcome, new Firebird user", so 
lots of files are deleted or filled with garbage.

I have an n-force2 ide chipset running an AMD 2500+ cpu. Do you need 
more info about my hardware?

I have realized that when the lookup ocurrs, the HD led is on all the time.

Thanks a lot.

                 reply	other threads:[~2004-01-23 18:15 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=40117620.6040103@wanadoo.es \
    --to=ktech@wanadoo.es \
    --cc=linux-kernel@vger.kernel.org \
    /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.