Messages in this thread | | | Date | Sat, 17 Jan 2004 21:16:39 +0100 | From | Sander <> | Subject | several oopses during boot (was: Re: [PATCH] Add CONFIG for -mregparm=3) |
| |
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 - 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/
| |