From: Peter Santoro <psantoro@att.net>
To: linux-kernel@vger.kernel.org
Subject: kernel 2.4.26 oops (maybe solved)
Date: Wed, 21 Jul 2004 23:26:22 -0400 [thread overview]
Message-ID: <40FF33DE.6010307@att.net> (raw)
After trying many h/w and s/w configurations, I've apparently isolated
my instability issues to using the following the linux kernel highmem
options: CONFIG_HIGHMEM4G=y, CONFIG_HIGHMEM=y, CONFIG_HIGHMEMIO=y. I
have 1GB ram, so maybe one of my dimms is bad or maybe there's a highmem
bug in the 2.4.X kernel.
The crashes in my previous emails today were due to using the latest
alsa modules (loaded, but not used by any application) with a HIGHMEM
enabled kernel. I appear to have no problem using alsa when HIGHMEM is
disabled. Apparently, I'm not the only one having problems with alsa
and highmem
(http://www.mail-archive.com/alsa-user@lists.sourceforge.net/msg13918.html).
I would be willing to work with a kernel developer to better isolate
this problem and test a patch.
Thank you,
Peter Santoro
next reply other threads:[~2004-07-22 3:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-22 3:26 Peter Santoro [this message]
2004-07-22 4:50 ` kernel 2.4.26 oops (maybe solved) Alex Lyashkov
2004-07-24 17:17 ` Marcelo Tosatti
2004-07-26 23:22 ` Peter Santoro
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=40FF33DE.6010307@att.net \
--to=psantoro@att.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