lkml.org 
[lkml]   [2001]   [Jun]   [25]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRE: Crash on boot (2.4.5)
Date
From
Well, I have tried your suggestion, and it works beautifully...  The
only change I made was to the cpu type (to 686), and everything *just*
works now... Thanks, all!!!

-- andyw

-----Original Message-----
From: Steven Walter [mailto:srwalter@yahoo.com]
Sent: Sunday, June 24, 2001 3:42 PM
To: Andy Ward
Cc: linux-kernel@vger.kernel.org
Subject: Re: Crash on boot (2.4.5)


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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 12:55    [W:0.059 / U:2.152 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site