From: Peter Santoro <psantoro@att.net>
To: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kernel 2.4.26 oops (maybe solved)
Date: Mon, 26 Jul 2004 19:22:38 -0400 [thread overview]
Message-ID: <4105923E.5090206@att.net> (raw)
In-Reply-To: <20040724171706.GA2530@dmt.cyclades>
Marcelo Tosatti wrote:
> Hi Peter,
>
> Care to disable ALSA to see if the problem really only happens
> when running ALSA+HIGHMEM ?
>
> Your previous oopses in core VM code seem to be hardware problems
> to me, I haven't done any deep analysis though.
>
Marcelo,
Thank you for responding to my post. I know how busy you and your
kernel colleagues are and I truly appreciate all your efforts. The last
thing I want to do is waste anyone's time. (Earlier this year, I
reported a Lexar usb thumb drive crash using an ibm pc to the usb kernel
developers and worked with Pete Zaitcev to test his 2.4.27 patch.)
Although my asus system has been very stable for about 4 years, I do
realize that my current problems could be due to failing hardware.
Given that I've also experienced a few random reboots over the last 4
months, I did replace the psu with a new Antec 430W Truepower psu. I
also tried replacing my cpu with an Intel P3 600e and have run all
memtest86 tests a few times without errors. The power to the room for
this computer is on a separate circuit, but I suppose I could try using
a ups. Or maybe it's time for a new motherboard?
My original crashes started occurring around the time I upgraded to
2.4.26 and started using HIGHMEM (no alsa) - of course, this could just
be a coincidence. Adding alsa simply made the system more unstable. I
have been running without a crash for about 5 days now (alsa without
HIGHMEM) - until today (2 random reboots: alsa without HIGHMEM).
I am now running without HIGHMEM and without alsa, to see if it makes
any difference. I will probably also try running memtest86 for a day or
two more. If you have any other suggestions, I'd be happy to listen.
Sincerely,
Peter Santoro
prev parent reply other threads:[~2004-07-26 23:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-22 3:26 kernel 2.4.26 oops (maybe solved) Peter Santoro
2004-07-22 4:50 ` Alex Lyashkov
2004-07-24 17:17 ` Marcelo Tosatti
2004-07-26 23:22 ` Peter Santoro [this message]
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=4105923E.5090206@att.net \
--to=psantoro@att.net \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com \
/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