From: Sander <sander@humilis.net>
To: Andi Kleen <ak@colin2.muc.de>
Cc: Sander <sander@humilis.net>, Andi Kleen <ak@muc.de>,
akpm@osdl.org, linux-kernel@vger.kernel.org, jh@suse.cz
Subject: Re: several oopses during boot (was: Re: [PATCH] Add CONFIG for -mregparm=3)
Date: Mon, 19 Jan 2004 07:47:56 +0100 [thread overview]
Message-ID: <20040119064756.GA9708@favonius> (raw)
In-Reply-To: <20040118210017.GB68521@colin2.muc.de>
Andi Kleen wrote (ao):
> > I have no idea if it is hardware or software related, and if it has
> > got anything to do with the REGPARM option, but I entered this
> > thread because the kernel oopsed the first time I booted it and the
> > first time I enabled this option.
>
> Do the oopses go away when you disable the option? And do they come
> back when you reenable it again?
I have to try that, but have no reliable way to get the oopses yet which
makes that a bit hard.
> You could run memtest86 to make sure your RAM is ok.
I'll do that.
--
Humilis IT Services and Solutions
http://www.humilis.net
prev parent reply other threads:[~2004-01-19 6:47 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-14 9:06 [PATCH] Add CONFIG for -mregparm=3 Andi Kleen
2004-01-14 9:16 ` Russell King
2004-01-14 9:30 ` Andi Kleen
2004-01-14 9:29 ` Andrew Morton
2004-01-14 9:35 ` Andi Kleen
2004-01-14 19:25 ` Adrian Bunk
2004-01-15 15:02 ` Andrea Arcangeli
2004-01-14 9:54 ` Arjan van de Ven
2004-01-14 9:34 ` Arjan van de Ven
2004-01-14 9:39 ` Andi Kleen
2004-01-14 9:44 ` Arjan van de Ven
2004-01-14 9:47 ` Andrew Morton
2004-01-15 0:40 ` Rusty Russell
2004-01-15 9:22 ` Andi Kleen
2004-01-17 20:16 ` several oopses during boot (was: Re: [PATCH] Add CONFIG for -mregparm=3) Sander
2004-01-17 20:53 ` Andi Kleen
2004-01-17 21:07 ` Sander
2004-01-17 21:28 ` Andi Kleen
2004-01-17 22:01 ` Mike Fedyk
2004-01-18 5:44 ` Sander
2004-01-18 20:34 ` Sander
2004-01-18 21:00 ` Andi Kleen
2004-01-19 6:47 ` Sander [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=20040119064756.GA9708@favonius \
--to=sander@humilis.net \
--cc=ak@colin2.muc.de \
--cc=ak@muc.de \
--cc=akpm@osdl.org \
--cc=jh@suse.cz \
--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