From: "Rogério Brito" <rbrito@ime.usp.br>
To: Grzegorz Kulewski <kangur@polcom.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Strange disk corruption with Linux >= 2.6.13
Date: Tue, 27 Sep 2005 09:20:33 -0300 [thread overview]
Message-ID: <204F8530-3DAD-4B20-AC24-2CBA776CC2C2@ime.usp.br> (raw)
In-Reply-To: <Pine.LNX.4.63.0509271331590.21130@alpha.polcom.net>
Hi, Grzegorz. Thank you for your response.
On Sep 27, 2005, at 8:43 AM, Grzegorz Kulewski wrote:
> What is your southbridge?
The southbridge is a VIA VT82C686.
> Maybe there are some problems there with DMA or cables.
Humm, cables. I forgot to check that. I will check that as soon as I
wake up. I spent the entire night trying to fix this, but of course,
I gave up after some days of effort and decided to ask for help.
> Anything in logs?
Nothing in the logs. No oops, no stack trace, no nothing. :-( Oh, now
that you mention it, I remember that I also made my Matrox G400 use
speed 4x. I will try slowing it down to see if there is any influence
on what I see.
> Maybe sourthbridge or northbridge is simply overheating? Maybe you
> have bad power suply? What are readings of temperatures and
> voltages in BIOS after some heavy disk-memmory activities?
I don't know, because lmsensors doesn't give accurate measurements,
unfortunately. :-(
> You can use http://pyropus.ca/software/memtester/ to check your
> memory in linux. You can run cpuburn at the same time. And you can
> do some disk activity at the same time (for example dd if=/dev/hda
> bs=200M | md5sum several times to check if it will give the same
> results).
I had already tried using memtester, but I guess that I was too
ambitious with the amount of memory that I tried it to allocate. I
will try this, but with my filesystem in read-only mode, as I cannot
afford to loose what I have (and Debian's mondo/mind isn't working
right now---I already filed a bug report that is shared by others).
> I will bet that you have some hardware problem there. You can try
> to remove the 256MB DDR module and turn HIGHMEM off. You can also
> try to check each module separately.
I already checked each module separately, but I didn't see any
corruption. I guess that I maybe wasn't paying too much attention. I
will try it again. Thanks for the suggestion.
> And the best choice will be probably to buy new mb (for example
> Abit KW7 or KV7) because your is very old and it can start to
> silently break after so many years... Today mbs are very short
> living parts - 3-4 years and they are broken...
Yes, I was just trying to avoid getting a new system now, with all
the transitions going on (i386 -> x86_64 CPUs, PATA -> SATA etc). But
my time is also costing me some nights of sleep... :-( It sucks not
to be in the US, where things are cheaper. :-(
Thank you very much, Rogério.
--
Rogério Brito : rbrito@ime.usp.br : http://www.ime.usp.br/~rbrito
Homepage of the algorithms package : http://algorithms.berlios.de
Homepage on freshmeat: http://freshmeat.net/projects/algorithms/
next prev parent reply other threads:[~2005-09-27 12:20 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-27 11:10 Rogério Brito
2005-09-27 11:34 ` Diego Calleja
2005-09-27 11:58 ` Rogério Brito
2005-09-27 12:10 ` Rogério Brito
2005-09-27 11:57 ` Grant Coady
2005-09-27 12:43 ` Ondrej Zary
2005-10-01 21:22 ` Rogério Brito
2005-09-27 14:04 ` Lennart Sorensen
2005-10-01 21:28 ` Rogério Brito
2005-10-03 16:20 ` Lennart Sorensen
[not found] ` <Pine.LNX.4.63.0509271331590.21130@alpha.polcom.net>
2005-09-27 12:20 ` Rogério Brito [this message]
2005-09-27 12:38 ` Grzegorz Kulewski
2005-09-27 19:42 ` Guennadi Liakhovetski
2005-09-27 21:01 ` Erik Mouw
2005-09-27 21:44 ` Guennadi Liakhovetski
2005-10-01 21:15 ` Rogério Brito
2005-10-08 22:35 ` Guennadi Liakhovetski
2005-10-09 9:30 ` Rogério Brito
2005-10-01 21:02 ` Rogério Brito
2005-09-27 23:31 ` Nigel Cunningham
2005-10-01 21:36 ` Rogério Brito
2005-10-02 0:06 ` Grant Coady
2005-10-03 4:17 ` Rogério Brito
2005-10-03 4:20 ` Willy Tarreau
2005-10-03 4:55 ` Nigel Cunningham
2005-10-04 10:28 ` Sander
2005-10-04 12:42 ` Nigel Cunningham
2005-09-28 8:43 ` Ville Herva
2005-09-28 23:23 ` Alan Cox
2005-09-29 6:29 ` Ville Herva
2005-09-29 16:14 ` Alan Cox
2005-10-03 5:05 ` Rogério Brito
2005-10-03 5:15 ` Rogério Brito
[not found] <4RlFC-2ev-17@gated-at.bofh.it>
[not found] ` <4Rxdq-2Tc-19@gated-at.bofh.it>
[not found] ` <4SXfs-7hM-27@gated-at.bofh.it>
2005-10-02 3:37 ` Bodo Eggert
2005-10-03 4:30 ` Rogério Brito
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=204F8530-3DAD-4B20-AC24-2CBA776CC2C2@ime.usp.br \
--to=rbrito@ime.usp.br \
--cc=kangur@polcom.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®