From: "Pods" <pods@dodo.com.au>
To: linux-kernel@vger.kernel.org
Subject: Re: lotsa oops - 2.6.5 (preempt + unable handle virutal address + more?)
Date: Mon, 7 Jun 2004 13:27:44 +1000 [thread overview]
Message-ID: <E1BXAnX-0005BG-00@mail.kbs.net.au> (raw)
Ok i fixed it. Was a RAM installation problem. I've had trouble with RAM in
this board before. When i initialy set it up, the RAM modules being in 2&3 3
was the only i could get it to boot.
However i had a few more tries and i got a single DIMM bootting the machine
and then i tried two. It didnt boot, so i wirggled it and it work? very
strange. I think the DDR slots may not be up to scratch, but its working...
o rat least, seems to be.
Thanx for your help, even though it wouldnt have been neccessary if i had
taken more care in installing the RAM. *color me red faced*
Thanx again.
--------- Original Message --------
From: Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua>
To: Pods <pods@dodo.com.au>, linux-kernel@vger.kernel.org
<linux-kernel@vger.kernel.org>
Subject: Re: lotsa oops - 2.6.5 (preempt + unable handle virutal address +
more?)
Date: 06/06/04 05:28
>
> On Saturday 05 June 2004 18:27, Pods wrote:
> > >> Run memtest86
> > Tried once before, didnt boot... died :( memtest page says this
happens on
> > some hardware and they're not sure why.
>
> Ho hum. Looks like good starting point to debug.
> Remove RAM until you have <= 2 GB, then run memtest86
> (or modified versions of it with debug prints)
> until you know where it dies.
>
> > >> Underclock your system
> > its not over clocked :/
>
> I mean, underclock below normal conditions.
>
> > >> lower IDE DMA mode and see whether it stops oopsing.
> >
> > tried setting dma = off in hdparm, didnt work, still got crashes
compiling
> > firebird.. infact, it didnt even get passed the ./configure stage :(
>
> Use hdparm to set, say, udma0.
>
> > Each time (just about, didnt do it once out of 6ish times) i set the
dma to
> > off (either at boot or runtime) i got a "spurious 8259A
interript: IRQ 7"..
> > apparantly, iirc that debug message has been taken out of 2.6.6
>
> I have 'em too. Not a real issue on lots of systems.
>
> > Please guys, CC me your responces, otherwise i have to look at some
> > archives, and reply via webmail... it took 2 firefox crashes (one of
which
> > brought down X) to just right this message... now im going to take a
chance
> > and hit the submit
> > button
> --
> vda
>
>
>
>
>
>
>
>
>
>
>
>
________________________________________________
Message sent using
Dodo Internet Webmail Server
next reply other threads:[~2004-06-07 3:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-07 3:27 Pods [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-06-06 6:00 Pods
2004-06-05 15:27 Pods
2004-06-05 19:00 ` Denis Vlasenko
2004-06-04 5:56 Pods
2004-06-04 6:26 ` Anupam Kapoor
2004-06-04 11:50 ` Denis Vlasenko
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=E1BXAnX-0005BG-00@mail.kbs.net.au \
--to=pods@dodo.com.au \
--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
all inboxes | Powered by JetHome®