From: Christian Ohm <chr.ohm@gmx.net>
To: vda <vda@port.imtp.ilyichevsk.odessa.ua>
Cc: linux-kernel@vger.kernel.org
Subject: Re: file corruption in 2.4.16/17
Date: Wed, 26 Dec 2001 01:59:50 +0100 [thread overview]
Message-ID: <20011226005950.GB3970@moongate.thevoid.net> (raw)
In-Reply-To: <20011224010450.GB1482@moongate.thevoid.net> <Pine.LNX.4.33.0112232355540.5312-100000@coffee.psychology.mcmaster.ca> <20011225003901.GA3752@moongate.thevoid.net> <01122510384005.01845@manta>
In-Reply-To: <01122510384005.01845@manta>
> Force Athlon bug stomper to be executed at startup (look into pci-pc.c).
> Your kernel thinks you don't need it. It may be wrong.
> Please report back.
like i said, i don't really think this is hardware related, unless someone
convinces me of the opposite. anyway, first i'll try to reproduce it to be
sure 2.4.17 still behaves this way. then comes the fun part: searching for
the cause...
bye
christian ohm
next prev parent reply other threads:[~2001-12-26 1:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-22 22:02 Christian Ohm
[not found] ` <01122300525700.01910@manta>
2001-12-22 23:06 ` Christian Ohm
[not found] ` <Pine.LNX.4.33.0112222109310.5312-100000@coffee.psychology.mcmaster.ca>
2001-12-23 2:57 ` Christian Ohm
[not found] ` <Pine.LNX.4.33.0112230110110.5312-100000@coffee.psychology.mcmaster.ca>
2001-12-24 1:04 ` Christian Ohm
[not found] ` <Pine.LNX.4.33.0112232355540.5312-100000@coffee.psychology.mcmaster.ca>
2001-12-25 0:39 ` Christian Ohm
[not found] ` <01122510384005.01845@manta>
2001-12-26 0:59 ` Christian Ohm [this message]
2001-12-23 6:48 ` Andre Hedrick
2001-12-23 13:39 ` Alan Cox
2001-12-24 1:12 ` Christian Ohm
2001-12-24 9:17 ` Hans Reiser
2001-12-25 0:44 ` Christian Ohm
2001-12-25 10:23 ` Hans Reiser
2001-12-26 0:53 ` Christian Ohm
2001-12-26 6:20 ` Oleg Drokin
2001-12-27 3:09 ` Christian Ohm
2001-12-27 11:06 ` Hans Reiser
2001-12-28 0:24 ` Christian Ohm
2001-12-28 1:32 ` Hans Reiser
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=20011226005950.GB3970@moongate.thevoid.net \
--to=chr.ohm@gmx.net \
--cc=linux-kernel@vger.kernel.org \
--cc=vda@port.imtp.ilyichevsk.odessa.ua \
/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
Powered by JetHome