On Tuesday 30 September 2003 00:37, Mark Ferlatte wrote:
> It would mean taking your hardware offline, but I would try memtest.
> Think of it this way: maybe the next bit flip is in the middle of
> your data.
Uhm, but I thought memtest from the sysutils package (as opposed to
memtest86), was sui
On Tue, 30 Sep 2003 04:40:09 +0200, csj wrote:
> Try compiling the linux kernel X times. In my experience at some
> point bad memory will cause a kernel compile to fail (of course a
> bad CPU would casue it to fail much faster, but CPU's are
> probably the hardiest part of your system)
That, or i
At Mon, 29 Sep 2003 23:03:27 +0200,
Kjetil Kjernsmo wrote:
>
> On Monday 29 September 2003 22:06, Juri Haberland wrote:
> > Though I don't know much about kernel opps messages I still
> > recommend to check you RAM, e.g. with memtest86, as it might
> > be just a bit flipped due to failed memory.
>
Mark Ferlatte schrieb:
> Kjetil Kjernsmo said on Mon, Sep 29, 2003 at 11:03:27PM +0200:
>> How about memtest...? This box is under some load, but usually not too
>> bad, would it be a good idea to run it overnight? How would I go about
>> to test a much as possible of my memory with it?
>
> It w
Kjetil Kjernsmo said on Mon, Sep 29, 2003 at 11:03:27PM +0200:
> How about memtest...? This box is under some load, but usually not too
> bad, would it be a good idea to run it overnight? How would I go about
> to test a much as possible of my memory with it?
It would mean taking your hardware o
On Monday 29 September 2003 22:06, Juri Haberland wrote:
> Though I don't know much about kernel opps messages I still recommend
> to check you RAM, e.g. with memtest86, as it might be just a bit
> flipped due to failed memory.
Oh, yes, that's right, I forgot. Thanks. However, it requires taking i
Kjetil Kjernsmo schrieb:
> These segfaults started to appear, and I found there were little I could
> do to repair it. Eventually, it seems like more and more programs got
> this problem, and finally I couldn't log on anymore on Sunday evening.
>
> In the server room, I booted the machine with
Hello!
I realized I had to go down to the server room to fix this. Been there
all day. Think I'm catching a cold... ;-)
Just a reminder of what happened:
On Saturday 27 September 2003 15:22, Kjetil Kjernsmo wrote:
> Last night, the cronjob on my main server reported this:
> /etc/cron.daily/mail
Kjetil Kjernsmo wrote:
Thanks for the quick response!
On Saturday 27 September 2003 16:21, Russell Shaw wrote:
fsck the disk.
OK! However, physical access to this computer is a complex issue, and to
run fsck on the / and /usr partitions (which are the most obvious
places to look), I can't thin
Thanks for the quick response!
On Saturday 27 September 2003 16:21, Russell Shaw wrote:
> fsck the disk.
OK! However, physical access to this computer is a complex issue, and to
run fsck on the / and /usr partitions (which are the most obvious
places to look), I can't think of a way to unmount
Russell Shaw wrote:
> Kjetil Kjernsmo wrote:
>> Hi all!
>>
>> Last night, the cronjob on my main server reported this:
> ...
>> So, there is a segfault there too, but I guess this really doesn't imply
>> there is a trojan, but that this is a consequence of the same problem
>> as above.
>>
>> An
Kjetil Kjernsmo wrote:
Hi all!
Last night, the cronjob on my main server reported this:
...
So, there is a segfault there too, but I guess this really doesn't imply
there is a trojan, but that this is a consequence of the same problem
as above.
Any ideas?
fsck the disk. Find a specific program
12 matches
Mail list logo
