From: Steven Walter <srwalter@yahoo.com>
To: andyw@edafio.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Crash on boot (2.4.5)
Date: Sun, 24 Jun 2001 15:41:34 -0500 [thread overview]
Message-ID: <20010624154134.A9203@hapablap.dyn.dhs.org> (raw)
In-Reply-To: <001001c0fcde$a9422ec0$ecbd3fd8@wamprat>
In-Reply-To: <001001c0fcde$a9422ec0$ecbd3fd8@wamprat>; from the_toastman@aristotle.net on Sun, Jun 24, 2001 at 01:51:09PM -0500
On Sun, Jun 24, 2001 at 01:51:09PM -0500, Daniel Fraley wrote:
> Hi, everyone.. I'm borrowing my roommate's email, so please send replies to
> andyw@edafio.com. Thanks!
>
> Here's my problem... when I boot anything 2.4, I get several oopsen in a
> row, all of which are either (most commonly) kernel paging request could not
> be handled, or (much less common) unable to handle kernel Null pointer
> dereference. I will send any info on request, but here's my hardware and
> kernel config:
>
> iWill KKR-266R (Via 8363 Northbridge, 686B south)
> AMD tbird 1GHz
> 256MB cas2 pc133 sdram
> ATI Radeon DDR 64MB VIVO
> Kingston KNE120TX (Realtek 8139 chip)
> SBLive! 5.1
> IBM GXP75 30GB (on the via ide controller)
> Pioneer 16x dvd
> ls120
>
> This happens regardless if I turn on swap or not. When swap is on, it is a
> 128MB partition (and yes, I'm aware of the recommendation of 2x RAM, but I
> believe I read somewhere that someone was working on that, and I didn't want
> to waste the extra 384MB on swap).
>
> Is there anything I can do to fix this?
>
> -- andyw
>
> p.s., booting with devfs=nomount is better, but still causes oopsen (I get
> to a login prompt, but if I do much more than mount a disk a copy to it, the
> system freaks)
>From the look of things, you're being bitten by the VIA southbridge
problem. As I've gathered, its some sort of interaction with that chip
and the 3DNow! fast copy routines the kernel uses.
If you compile the kernel for a 686, does the problem go away? What
about 586 or lower? If so, I believe there are some people working on
finding common aspects of the hardware that experience this problem,
though I don't remember who. You should get in contact with them, or
they might get into contact with you.
Good luck on working this out.
--
-Steven
In a time of universal deceit, telling the truth is a revolutionary act.
-- George Orwell
next prev parent reply other threads:[~2001-06-24 20:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-24 18:51 Crash on boot (2.4.5) Daniel Fraley
2001-06-24 19:13 ` David Brown
2001-06-24 20:41 ` Steven Walter [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-06-25 4:44 Andy Ward
2001-06-25 4:45 Andy Ward
2001-06-25 6:17 Andy Ward
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=20010624154134.A9203@hapablap.dyn.dhs.org \
--to=srwalter@yahoo.com \
--cc=andyw@edafio.com \
--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