From: Andi Kleen <ak@colin2.muc.de>
To: Sander <sander@humilis.net>
Cc: 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: 17 Jan 2004 21:53:02 +0100
Date: Sat, 17 Jan 2004 21:53:02 +0100 [thread overview]
Message-ID: <20040117205302.GA16658@colin2.muc.de> (raw)
In-Reply-To: <20040117201639.GA16420@favonius>
> 2.6.1-mm4
Note that this kernel is broken on gcc 3.4 and on 3.3-hammer. If you're
using that disable the -funit-at-a-time setting in the main Makefile.
> VIA C3 Ezra
>
> It mounts its root filesystem over nfs and has netconsole compiled in.
>
> Without the REGPARM option the system boots and runs fine.
>
> Should I post the oopses, the result of ksymoops, a dmesg and kernel
> config or is this an already known issue?
Not known. Please post the decoded oopses. Also give your compiler
version.
-Andi
next prev parent reply other threads:[~2004-01-17 20:52 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 [this message]
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
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=20040117205302.GA16658@colin2.muc.de \
--to=ak@colin2.muc.de \
--cc=ak@muc.de \
--cc=akpm@osdl.org \
--cc=jh@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=sander@humilis.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.