public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sander <sander@humilis.net>
To: Andi Kleen <ak@muc.de>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org, jh@suse.cz
Subject: several oopses during boot (was: Re: [PATCH] Add CONFIG for -mregparm=3)
Date: Sat, 17 Jan 2004 21:16:39 +0100	[thread overview]
Message-ID: <20040117201639.GA16420@favonius> (raw)
In-Reply-To: <20040114090603.GA1935@averell>

Hi Andi and Andrew,

Andi Kleen wrote (ao):
> Using -mregparm=3 shrinks the kernel further:

...

> This patch adds an option to use -mregparm=3 while compiling the kernel.
> I did an LTP run and it showed no additional failures over an non 
> regparm kernel.
> 
> According to some gcc developers it should be safe to use in all
> gccs that are still supports (2.95 and up) 
> 
> I didn't make it the default because it will break all binary only
> modules (although they can be fixed by adding a wrapper that 
> calls them with "asmlinkage"). Actually it may be a good idea to 
> make this default with 2.7.1 or somesuch.

...
  
> +config REGPARM
> +	bool "Use register arguments (EXPERIMENTAL)"
> +	default n
> +	help
> +	Compile the kernel with -mregparm=3. This uses an different ABI
> +	and passes the first three arguments of a function call in registers.
> +	This will probably break binary only modules.	

This gives several oopses on my system during boot, after which is seems
dead.

2.6.1-mm4
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?

Kind regards, Sander

-- 
Humilis IT Services and Solutions
http://www.humilis.net

  parent reply	other threads:[~2004-01-17 20:16 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 ` Sander [this message]
2004-01-17 20:53   ` several oopses during boot (was: Re: [PATCH] Add CONFIG for -mregparm=3) 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

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=20040117201639.GA16420@favonius \
    --to=sander@humilis.net \
    --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