* Memory corruption on Indy
@ 1999-02-14 23:27 ralf
1999-02-15 0:32 ` Thomas Bogendoerfer
0 siblings, 1 reply; 6+ messages in thread
From: ralf @ 1999-02-14 23:27 UTC (permalink / raw)
To: linux, linux-mips, linux-mips
Hi all,
since quite some time I've tried to find a memory corruption bug on my Indy.
I now suspect that the actual cause is a hardware problem and a recent
IRIX kernel core dump supports that theory. Just to be on the safe side,
could people running Linux on Indys please run something like
find / -fstype ext2 -type f | xargs md5sym
several times and compare the obtained output. Do they differ in any
unexplainable way?
Thanks,
Ralf
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Memory corruption on Indy
1999-02-14 23:27 Memory corruption on Indy ralf
@ 1999-02-15 0:32 ` Thomas Bogendoerfer
1999-02-15 1:05 ` ralf
[not found] ` <Pine.SOL.3.95.990216085734.25445A-100000@ecom5>
0 siblings, 2 replies; 6+ messages in thread
From: Thomas Bogendoerfer @ 1999-02-15 0:32 UTC (permalink / raw)
To: ralf, linux, linux-mips, linux-mips
On Mon, Feb 15, 1999 at 12:27:46AM +0100, ralf@uni-koblenz.de wrote:
> find / -fstype ext2 -type f | xargs md5sym
>
> several times and compare the obtained output. Do they differ in any
> unexplainable way?
do you want, that everybody crash their Indys ?
Everybody, who wants to run the find, should umount /proc before doing it.
Otherwise the kernel will crash, when the md5sum /proc/kcore happens.
Thomas.
--
This device has completely bogus header. Compaq scores again :-|
It's a host bridge, but it should be called ghost bridge instead ;^)
[Martin `MJ' Mares on linux-kernel]
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: Memory corruption on Indy
1999-02-15 0:32 ` Thomas Bogendoerfer
@ 1999-02-15 1:05 ` ralf
[not found] ` <Pine.SOL.3.95.990216085734.25445A-100000@ecom5>
1 sibling, 0 replies; 6+ messages in thread
From: ralf @ 1999-02-15 1:05 UTC (permalink / raw)
To: Thomas Bogendoerfer, linux, linux-mips, linux-mips
On Mon, Feb 15, 1999 at 01:32:10AM +0100, Thomas Bogendoerfer wrote:
> On Mon, Feb 15, 1999 at 12:27:46AM +0100, ralf@uni-koblenz.de wrote:
> > find / -fstype ext2 -type f | xargs md5sym
> >
> > several times and compare the obtained output. Do they differ in any
> > unexplainable way?
>
> do you want, that everybody crash their Indys ?
>
> Everybody, who wants to run the find, should umount /proc before doing it.
> Otherwise the kernel will crash, when the md5sum /proc/kcore happens.
That's what the -fstype ext2 is supposed to take care of :-)
Ralf
^ permalink raw reply [flat|nested] 6+ messages in thread[parent not found: <Pine.SOL.3.95.990216085734.25445A-100000@ecom5>]
end of thread, other threads:[~1999-02-27 17:45 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
1999-02-14 23:27 Memory corruption on Indy ralf
1999-02-15 0:32 ` Thomas Bogendoerfer
1999-02-15 1:05 ` ralf
[not found] ` <Pine.SOL.3.95.990216085734.25445A-100000@ecom5>
1999-02-22 22:27 ` R4600 MIPS/Linux ralf
[not found] ` <Pine.SOL.3.95.990225231407.26058D-100000@ecom5>
1999-02-27 16:53 ` Kernel support for R4600 MIPS ralf
1999-02-27 17:45 ` Warner Losh
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.