Kernels &#62; 2.6.1-mm3 do not boot.

Alle Sunday 25 January 2004 02:02, Adrian Bunk ha scritto:

Quoted 5 lines

Please check exactly between which two kernel versions the problem first appeared.
Please send the .config of the last kernel that worked for you.

Confirmed here also...
the latest working kernel is 2.6.1-mm3; the first non working is 2.6.1-mm4 The symptom is that the booting sequence stops right after "Uncompressing..". I've cofnigured -mm4 using .config and "make oldconfig", answering when needed.
The only relevant changed config options are related to CPU, but I haven't looked in configure files.
I've attached both .config (working-mm3/not working 2.6.2-rc1-mm3). I'm now trying to compile 2.6.2-rc1-mm3, but the problem is here from 2.6.1-mm4 (not rc).
I've also tried several choices for CPU (386->P4), without any change. The system is a P4/HT, chipset i875p, 1Gb ram
If more information/test are needed, just let me know.

Signature · 4 lines

Fabio Coatti       http://www.ferrara.linux.it/members/cova     
Ferrara Linux Users Group           http://ferrara.linux.it
GnuPG fp:9765 A5B6 6843 17BC A646  BE8C FA56 373A 5374 C703
Old SysOps never die... they simply forget their password.

Adrian Bunk

2004-01-25 14:34 UTC #7 lore raw

Quoted 8 lines · Fabio Coatti

Alle Sunday 25 January 2004 02:02, Adrian Bunk ha scritto:
Quoted 5 lines
Please check exactly between which two kernel versions the problem first appeared.
Please send the .config of the last kernel that worked for you.

Quoted 13 lines

Confirmed here also...
the latest working kernel is 2.6.1-mm3; the first non working is 2.6.1-mm4 The symptom is that the booting sequence stops right after "Uncompressing..". I've cofnigured -mm4 using .config and "make oldconfig", answering when needed.
The only relevant changed config options are related to CPU, but I haven't looked in configure files.
I've attached both .config (working-mm3/not working 2.6.2-rc1-mm3). I'm now trying to compile 2.6.2-rc1-mm3, but the problem is here from 2.6.1-mm4 (not rc).
I've also tried several choices for CPU (386->P4), without any change. The system is a P4/HT, chipset i875p, 1Gb ram
If more information/test are needed, just let me know.

I sent the following to Eric:

<-- snip -->

After diffing two of your .config's, I don't see how the CPU selection options might have caused this.

I'm sorry that I don't have a real idea where to search for the problems, only a few thoughts how to get nearer to finding it:

Please try 2.6.2-rc1 (without any -mm patch).

<-- snip -->

The same is true for your .config's, so i you have some spare time these tests would be interesting.

TIA
Adrian

Signature · 4 lines

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

Fabio Coatti

2004-01-25 15:41 UTC #8 lore raw

Alle Sunday 25 January 2004 15:34, Adrian Bunk ha scritto:

Quoted 1 line

I sent the following to Eric:

[...]

sorry, I've seen your mail just few seconds after sending my message; anyway I've tried following your suggestions:

Quoted 2 lines

Please try 2.6.2-rc1 (without any -mm patch).

Works just fine.

Quoted 3 lines

If this kernel works, please try -mm4 with disabled SMP support and support for the Athlon (and no other CPUs).

Doesn't work

Quoted 2 lines

If you compile with
make V=1

gcc -Wp,-MD,fs/.dcache.o.d -nostdinc -iwithprefix include -D__KERNEL__
-Iinclude -D__KERNEL__ -Iinclude -Wall -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -pipe -msoft-float -mpreferred-stack-boundary=2 -march=pentium4 -Iinclude/asm-i386/mach-default
-O2 -fomit-frame-pointer -funit-at-a-time -DKBUILD_BASENAME=dcache
-DKBUILD_MODNAME=dcache -c -o fs/.tmp_dcache.o fs/dcache.c

Signature · 4 lines

Fabio Coatti       http://www.ferrara.linux.it/members/cova     
Ferrara Linux Users Group           http://ferrara.linux.it
GnuPG fp:9765 A5B6 6843 17BC A646  BE8C FA56 373A 5374 C703
Old SysOps never die... they simply forget their password.

Adrian Bunk

2004-01-25 16:21 UTC #9 lore raw

Quoted 10 lines · Fabio Coatti

...
Quoted 2 lines
If this kernel works, please try -mm4 with disabled SMP support and support for the Athlon (and no other CPUs).
Doesn't work
Quoted 2 lines
If you compile with
make V=1
gcc -Wp,-MD,fs/.dcache.o.d -nostdinc -iwithprefix include -D__KERNEL__

Review

Quoted 5 lines

(quoted diff) +0 -5

-Iinclude  -D__KERNEL__ -Iinclude  -Wall -Wstrict-prototypes -Wno-trigraphs 
-fno-strict-aliasing -fno-common -pipe -msoft-float 
-mpreferred-stack-boundary=2 -march=pentium4 -Iinclude/asm-i386/mach-default 
-O2 -fomit-frame-pointer -funit-at-a-time     -DKBUILD_BASENAME=dcache 
-DKBUILD_MODNAME=dcache -c -o fs/.tmp_dcache.o fs/dcache.c

What's your gcc version ("gcc --version")?

Could you back out ("patch -p1 -R < ..." or manually remove the lines) the patch below and retry?

TIA
Adrian

Makefile renamed from Makefile~use-funit-at-a-time +4 -0

diff -puN Makefile~use-funit-at-a-time Makefile
@@ -445,6 +445,10 @@ ifdef CONFIG_DEBUG_INFO
 CFLAGS		+= -g
 endif
 
+# Enable unit-at-a-time mode when possible. It shrinks the
+# kernel considerably.
+CFLAGS += $(call check_gcc,-funit-at-a-time,)
+
 # warn about C99 declaration after statement
 CFLAGS += $(call check_gcc,-Wdeclaration-after-statement,)

[email protected]

2004-01-25 16:31 UTC #66 lore raw

Review

Quoted 6 lines · Fabio Coatti

gcc -Wp,-MD,fs/.dcache.o.d -nostdinc -iwithprefix include -D__KERNEL__

(quoted diff) +0 -5

-Iinclude  -D__KERNEL__ -Iinclude  -Wall -Wstrict-prototypes -Wno-trigraphs 
-fno-strict-aliasing -fno-common -pipe -msoft-float 
-mpreferred-stack-boundary=2 -march=pentium4 -Iinclude/asm-i386/mach-default 
-O2 -fomit-frame-pointer -funit-at-a-time     -DKBUILD_BASENAME=dcache 
-DKBUILD_MODNAME=dcache -c -o fs/.tmp_dcache.o fs/dcache.c

Does it work if you disable -funit-at-a-time? I had a problem with that totally wedging a kernel right after the decompressing/loading messages.

Fabio Coatti

2004-01-25 17:13 UTC #10 lore raw

Re: Kernels > 2.6.1-mm3 do not boot. - SOLVED

In reply to [email protected]

Alle Sunday 25 January 2004 17:21, Adrian Bunk ha scritto:

Quoted 2 lines

What's your gcc version ("gcc --version")?

gcc (GCC) 3.3.1 (Mandrake Linux 9.2 3.3.1-2mdk)

Quoted 3 lines

Could you back out ("patch -p1 -R < ..." or manually remove the lines) the patch below and retry?

Yep, and now it works :)
Now I'm running 2.6.1-mm4, tested both UP and SMP (SMT) and it boots just fine. Later I'll try with more recents releases, but I'm pretty sure that these will work.

Many thanks, the patch has solved this issue :)

Signature · 4 lines

Fabio Coatti       http://www.ferrara.linux.it/members/cova     
Ferrara Linux Users Group           http://ferrara.linux.it
GnuPG fp:9765 A5B6 6843 17BC A646  BE8C FA56 373A 5374 C703
Old SysOps never die... they simply forget their password.

Fabio Coatti

2004-01-25 17:14 UTC #67 lore raw

Alle Sunday 25 January 2004 17:28, [email protected] ha scritto:

Quoted 2 lines

Does it work if you disable -funit-at-a-time? I had a problem with that totally wedging a kernel right after the decompressing/loading messages.

Yep, the patch posted by Adrian removed -funit-at-a-time and now it works, thanks.

Signature · 4 lines

Fabio Coatti       http://www.ferrara.linux.it/members/cova     
Ferrara Linux Users Group           http://ferrara.linux.it
GnuPG fp:9765 A5B6 6843 17BC A646  BE8C FA56 373A 5374 C703
Old SysOps never die... they simply forget their password.

Adrian Bunk

2004-01-25 17:31 UTC #11 lore raw

[patch] Re: Kernels > 2.6.1-mm3 do not boot. - SOLVED

Quoted 12 lines · Fabio Coatti

Alle Sunday 25 January 2004 17:21, Adrian Bunk ha scritto:
Quoted 2 lines
What's your gcc version ("gcc --version")?
gcc (GCC) 3.3.1 (Mandrake Linux 9.2 3.3.1-2mdk)
Quoted 3 lines
Could you back out ("patch -p1 -R < ..." or manually remove the lines) the patch below and retry?

Quoted 6 lines

Yep, and now it works :)
Now I'm running 2.6.1-mm4, tested both UP and SMP (SMT) and it boots just fine. Later I'll try with more recents releases, but I'm pretty sure that these will work.
Many thanks, the patch has solved this issue :)

Many thanks to Eric and you for your help in tracking the problem down!

@Andi,Andrew:

It seems use-funit-at-a-time breaks with distributions shipping a gcc 3.3 that supports -funit-at-a-time.

Th patch below replaces use-funit-at-a-time.patch and uses scripts/gcc-version.sh from add-config-for-mregparm-3-ng* to use -funit-at-a-time only with gcc >= 3.4 .

cu
Adrian

Makefile renamed from Makefile.old +9 -0

@@ -441,6 +441,15 @@
 CFLAGS		+= -g
 endif
 
+# Enable unit-at-a-time mode when possible. It shrinks the
+# kernel considerably.
+#
+# Check the gcc version since -funit-at-a-time is available since gcc 3.4,
+# but some distributions ship a gcc 3.3 patched with a broken
+# -funit-at-a-time implementation
+GCC_VERSION = $(shell $(CONFIG_SHELL) scripts/gcc-version.sh $(CC))
+CFLAGS += $(shell if [ $(GCC_VERSION) -ge 0304 ] ; then echo "-funit-at-a-time"; fi ;)
+
 # warn about C99 declaration after statement
 CFLAGS += $(call check_gcc,-Wdeclaration-after-statement,)

Andi Kleen

2004-01-25 17:50 UTC #12 lore raw

Re: [patch] Re: Kernels > 2.6.1-mm3 do not boot. - SOLVED

Quoted 2 lines

It seems use-funit-at-a-time breaks with distributions shipping a gcc 3.3 that supports -funit-at-a-time.

It works for me with the hammer branch gcc 3.3 with -funit-at-a-time.

Are you sure the exception table sorting patch was properly applied?

Quoted 3 lines

Th patch below replaces use-funit-at-a-time.patch and uses scripts/gcc-version.sh from add-config-for-mregparm-3-ng* to use -funit-at-a-time only with gcc >= 3.4 .

I disagree with that change.

-Andi

[email protected]

2004-01-25 17:53 UTC #65 lore raw

Re: [patch] Re: Kernels > 2.6.1-mm3 do not boot. - SOLVED

Quoted 3 lines · Adrian Bunk

Th patch below replaces use-funit-at-a-time.patch and uses scripts/gcc-version.sh from add-config-for-mregparm-3-ng* to use -funit-at-a-time only with gcc >= 3.4 .

The Fedora gcc-ssa compiler has this problem, but claims to be 3.5. So at a minimum, we'd need to document the Fedora breakage and stick a big "Don't do that" on it.

[email protected]

2004-01-25 18:03 UTC #13 lore raw

Re: [patch] Re: Kernels > 2.6.1-mm3 do not boot. - SOLVED

Quoted 3 lines · Andi Kleen

It works for me with the hammer branch gcc 3.3 with -funit-at-a-time.
Are you sure the exception table sorting patch was properly applied?

Was that patch an x86 issue as well, or only on the 64-bit boxes? And if it is a x86 issue, can you repost what *you* think it is (as opposed to what the -mm patch thinks it is?)

Andi Kleen

2004-01-25 19:14 UTC #14 lore raw

Re: [patch] Re: Kernels > 2.6.1-mm3 do not boot. - SOLVED

Quoted 9 lines · On Sun, Jan 25, 2004 at 01:00:27PM -0500, [email protected] wrote:

Quoted 3 lines · Andi Kleen
It works for me with the hammer branch gcc 3.3 with -funit-at-a-time.
Are you sure the exception table sorting patch was properly applied?
Was that patch an x86 issue as well, or only on the 64-bit boxes? And if it is a x86 issue, can you repost what *you* think it is (as opposed to what the -mm patch thinks it is?)

The latest bk tree (post 2.6.2rc1) has a full solution that should cover all architectures.

AFAIK there is a known problem on MIPS (not related to the exception tables)

If someone is seeing crashes with a BK snapshot from today and -funit-at-a-time please send me the decoded oops.

-Andi

John Stoffel

2004-01-25 20:21 UTC #15 lore raw

Re: [patch] Re: Kernels > 2.6.1-mm3 do not boot. - SOLVED

Andi> The latest bk tree (post 2.6.2rc1) has a full solution that Andi> should cover all architectures.

Can you post your patch please? I've been running into this too. I'm compiling 2.6.2-rc1-mm3 right now after having commented out the -funit-at-a-time in Makefile. I'm running gcc 3.3.3 on Debian with the stable/unstable/testing branches.

Of course I posted my email before I read the entire rest of the chain of messages on this.

Thanks,
John

Andi Kleen

2004-01-25 20:27 UTC #16 lore raw

Re: [patch] Re: Kernels > 2.6.1-mm3 do not boot. - SOLVED

Quoted 6 lines · John Stoffel

Andi> The latest bk tree (post 2.6.2rc1) has a full solution that Andi> should cover all architectures.
Can you post your patch please? I've been running into this too. I'm compiling 2.6.2-rc1-mm3 right now after having commented out the

It should be in there already.

Quoted 2 lines

-funit-at-a-time in Makefile. I'm running gcc 3.3.3 on Debian with the stable/unstable/testing branches.

Did you actually have problems?

-Andi

John Stoffel

2004-01-25 20:38 UTC #17 lore raw

Re: [patch] Re: Kernels > 2.6.1-mm3 do not boot. - SOLVED

Quoted 1 line · John Stoffel

Quoted 1 line

Andi> The latest bk tree (post 2.6.2rc1) has a full solution that Andi> should cover all architectures.

Quoted 3 lines

Quoted 3 lines
Can you post your patch please? I've been running into this too. I'm compiling 2.6.2-rc1-mm3 right now after having commented out the

Andi> It should be in there already.

It's not in there, since my Makefile had the -funit-at-a-time stuff, which I've now commented out. Still compiling, and waiting to do areboot to test it out.

Quoted 2 lines

Quoted 2 lines
-funit-at-a-time in Makefile. I'm running gcc 3.3.3 on Debian with the stable/unstable/testing branches.

Andi> Did you actually have problems?

Sure, the darn thing wouldn't boot, it kept Oopsing with the test_wp_bit oops (that I just posted more details about).

More confirmation as I get it.

John

Andrew Morton

2004-01-25 21:13 UTC #51 lore raw

Re: [patch] Re: Kernels > 2.6.1-mm3 do not boot. - SOLVED

Quoted 7 lines · Andi Kleen

Quoted 3 lines
It seems use-funit-at-a-time breaks with distributions shipping a gcc 3.3 that supports -funit-at-a-time.
It works for me with the hammer branch gcc 3.3 with -funit-at-a-time.
Are you sure the exception table sorting patch was properly applied?

I'd say so. There are no extable patches in current -mm.

Quoted 5 lines

Quoted 3 lines
Th patch below replaces use-funit-at-a-time.patch and uses scripts/gcc-version.sh from add-config-for-mregparm-3-ng* to use -funit-at-a-time only with gcc >= 3.4 .
I disagree with that change.

Well there doesn't seem much doubt that -funit-at-a-time causes Fabio's kernel to fail. Do we know exactly which compiler he is using?

Fabio Coatti

2004-01-25 21:23 UTC #52 lore raw

Re: [patch] Re: Kernels > 2.6.1-mm3 do not boot. - SOLVED

Alle Sunday 25 January 2004 22:11, Andrew Morton ha scritto:

Quoted 5 lines

Quoted 2 lines
I disagree with that change.
Well there doesn't seem much doubt that -funit-at-a-time causes Fabio's kernel to fail. Do we know exactly which compiler he is using?

Well, I'm using gcc (GCC) 3.3.1 (Mandrake Linux 9.2 3.3.1-2mdk), provided with Mandrake 9.2. If more details about configuration are needed please let me know.

Signature · 4 lines

Fabio Coatti       http://www.ferrara.linux.it/members/cova     
Ferrara Linux Users Group           http://ferrara.linux.it
GnuPG fp:9765 A5B6 6843 17BC A646  BE8C FA56 373A 5374 C703
Old SysOps never die... they simply forget their password.

Andi Kleen

2004-01-25 21:47 UTC #18 lore raw

Re: [patch] Re: Kernels > 2.6.1-mm3 do not boot. - SOLVED

Quoted 7 lines · John Stoffel

Quoted 1 line · John Stoffel
Quoted 1 line
Andi> The latest bk tree (post 2.6.2rc1) has a full solution that Andi> should cover all architectures.
Quoted 1 line
Quoted 1 line

Quoted 8 lines

Quoted 2 lines
Quoted 2 lines
Can you post your patch please? I've been running into this too. I'm compiling 2.6.2-rc1-mm3 right now after having commented out the
Andi> It should be in there already.
It's not in there, since my Makefile had the -funit-at-a-time stuff, which I've now commented out. Still compiling, and waiting to do areboot to test it out.

I meant the patch to sort the exception tables, which fixes the only problem I know that unit-at-a-time triggered on i386

Quoted 8 lines

Quoted 3 lines
Quoted 3 lines
-funit-at-a-time in Makefile. I'm running gcc 3.3.3 on Debian with the stable/unstable/testing branches.
Andi> Did you actually have problems?
Sure, the darn thing wouldn't boot, it kept Oopsing with the test_wp_bit oops (that I just posted more details about).

Looks like the sort extable patch was missing. Are you 100% sure you booted the right kernel?

2.6.2-rc1 has Paul Mackerras' generalized sort extable patch already.

I just booted an 2.6.2-rc1-mm3 kernel compiled with an -funit-at-a-time capable gcc 3 and it worked just fine.

-Andi

Adrian Bunk

2004-01-25 21:48 UTC #64 lore raw

Re: [patch] Re: Kernels > 2.6.1-mm3 do not boot. - SOLVED

Quoted 10 lines · Andrew Morton

Andi Kleen <[email protected]> wrote:
...
Quoted 5 lines
Quoted 3 lines
Th patch below replaces use-funit-at-a-time.patch and uses scripts/gcc-version.sh from add-config-for-mregparm-3-ng* to use -funit-at-a-time only with gcc >= 3.4 .
I disagree with that change.
Well there doesn't seem much doubt that -funit-at-a-time causes Fabio's kernel to fail. Do we know exactly which compiler he is using?

gcc (GCC) 3.3.1 (Mandrake Linux 9.2 3.3.1-2mdk)

cu
Adrian

Signature · 4 lines

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

Adrian Bunk

2004-01-25 21:49 UTC #19 lore raw

Re: [patch] Re: Kernels > 2.6.1-mm3 do not boot. - SOLVED

Quoted 10 lines · John Stoffel

...
Quoted 2 lines
Quoted 2 lines
-funit-at-a-time in Makefile. I'm running gcc 3.3.3 on Debian with the stable/unstable/testing branches.
Andi> Did you actually have problems?
Sure, the darn thing wouldn't boot, it kept Oopsing with the test_wp_bit oops (that I just posted more details about).
More confirmation as I get it.

I'd say that's a different issue:
The gcc 3.3 in debian unstable doesn't know about -funit-at-a-time, and it should therefore not be affected by this problem.

Quoted 1 line

John

cu
Adrian

Signature · 4 lines

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

Andi Kleen

2004-01-25 21:52 UTC #53 lore raw

Re: [patch] Re: Kernels > 2.6.1-mm3 do not boot. - SOLVED

Quoted 11 lines · Fabio Coatti

Alle Sunday 25 January 2004 22:11, Andrew Morton ha scritto:
Quoted 5 lines
Quoted 2 lines
I disagree with that change.
Well there doesn't seem much doubt that -funit-at-a-time causes Fabio's kernel to fail. Do we know exactly which compiler he is using?
Well, I'm using gcc (GCC) 3.3.1 (Mandrake Linux 9.2 3.3.1-2mdk), provided with Mandrake 9.2. If more details about configuration are needed please let me know.

Let's take this from the start:

what kernel version are you running exactly?
what oops are you seeing?
does official 2.6.2rc1 (not mm) with -funit-at-a-time enabled in the Makefile work?

-Andi

Andi Kleen

2004-01-25 21:58 UTC #63 lore raw

Re: [patch] Re: Kernels > 2.6.1-mm3 do not boot. - II

Quoted 11 lines · Fabio Coatti

Alle Sunday 25 January 2004 22:11, Andrew Morton ha scritto:
Quoted 5 lines
Quoted 2 lines
I disagree with that change.
Well there doesn't seem much doubt that -funit-at-a-time causes Fabio's kernel to fail. Do we know exactly which compiler he is using?
Well, I'm using gcc (GCC) 3.3.1 (Mandrake Linux 9.2 3.3.1-2mdk), provided with Mandrake 9.2. If more details about configuration are needed please let me know.

Oh yes i forgot...

Also please save your .config, do a make distclean and compile again and try if it still happens. Sometimes compile dirs get messed up and produce miscompilations.

-Andi

Bartlomiej Zolnierkiewicz

2004-01-25 22:04 UTC #54 lore raw

Re: [patch] Re: Kernels > 2.6.1-mm3 do not boot. - SOLVED

Quoted 13 lines · Andi Kleen

Quoted 11 lines · Fabio Coatti
Alle Sunday 25 January 2004 22:11, Andrew Morton ha scritto:
Quoted 5 lines
Quoted 2 lines
I disagree with that change.
Well there doesn't seem much doubt that -funit-at-a-time causes Fabio's kernel to fail. Do we know exactly which compiler he is using?
Well, I'm using gcc (GCC) 3.3.1 (Mandrake Linux 9.2 3.3.1-2mdk), provided with Mandrake 9.2. If more details about configuration are needed please let me know.

Quoted 6 lines

Let's take this from the start:
what kernel version are you running exactly?
what oops are you seeing?
does official 2.6.2rc1 (not mm) with -funit-at-a-time enabled in the Makefile work?

I remember trying 2.6.1-mm4 + your sort extable patch (i386 specific version) on Mandrake 9.2 -> no boot. Removing -funit-at-a-time cured problem. I didn't have time to investigate it more (like trying patched vanilla). Just FYI.

--bart

Fabio Coatti

2004-01-25 22:10 UTC #55 lore raw

Re: [patch] Re: Kernels > 2.6.1-mm3 do not boot. - SOLVED

Alle Sunday 25 January 2004 22:46, Andi Kleen ha scritto:

Quoted 2 lines

what kernel version are you running exactly?

I've tried all -mm versions for 2.6.1 and 2.6.2-rc1 The latest working one without any patch was 2.6.1-mm3 2.6.2-rc1-mm3 didn't work.

Quoted 1 line

what oops are you seeing?

no oops at all. The boot stops right after "Uncompressing.." line

Quoted 2 lines

does official 2.6.2rc1 (not mm) with -funit-at-a-time enabled in the Makefile work?

Yes.

Signature · 4 lines

Fabio Coatti       http://www.ferrara.linux.it/members/cova     
Ferrara Linux Users Group           http://ferrara.linux.it
GnuPG fp:9765 A5B6 6843 17BC A646  BE8C FA56 373A 5374 C703
Old SysOps never die... they simply forget their password.

Andi Kleen

2004-01-25 22:14 UTC #56 lore raw

Re: [patch] Re: Kernels > 2.6.1-mm3 do not boot. - SOLVED

Quoted 4 lines · Fabio Coatti

Quoted 2 lines
does official 2.6.2rc1 (not mm) with -funit-at-a-time enabled in the Makefile work?
Yes.

Ok, then it is something in -mm*. I would suspect the new weird CPU configuration stuff. Can you double check you configured your CPU correctly? Or do you use 4/4? If yes turn that off.

-Andi

Andrew Morton

2004-01-25 22:25 UTC #57 lore raw

Re: [patch] Re: Kernels > 2.6.1-mm3 do not boot. - SOLVED

Quoted 3 lines · Andi Kleen

I would suspect the new weird CPU
configuration stuff.

What do you believe is wrong with it?

Andi Kleen

2004-01-25 22:32 UTC #58 lore raw

Re: [patch] Re: Kernels > 2.6.1-mm3 do not boot. - SOLVED

Quoted 6 lines · Andrew Morton

Quoted 3 lines · Andi Kleen
I would suspect the new weird CPU
configuration stuff.
What do you believe is wrong with it?

It's different and it is weird and probably easy to screw up.

It's just that CPU configuration errors often cause problems before the console is running. And we unfortunately still don't have early printk on i386, which makes it hard to diagnose.

-Andi

Andrew Morton

2004-01-25 23:00 UTC #59 lore raw

Re: [patch] Re: Kernels > 2.6.1-mm3 do not boot. - SOLVED

Quoted 11 lines · Andi Kleen

Quoted 6 lines · Andrew Morton
Quoted 3 lines · Andi Kleen
I would suspect the new weird CPU
configuration stuff.
What do you believe is wrong with it?
It's different and it is weird and probably easy to screw up.

I must say that it does seem to be causing quite a few problems and doesn't have a very good benefit:breakage ratio. Maybe we should say that 2.6 has sucky CPU selection and leave it for 2.7.

John Stoffel

2004-01-25 23:20 UTC #20 lore raw

Re: [patch] Re: Kernels > 2.6.1-mm3 do not boot. - SOLVED

Quoted 1 line · John Stoffel

Quoted 1 line
More confirmation as I get it.

Adrian> I'd say that's a different issue: The gcc 3.3 in debian Adrian> unstable doesn't know about -funit-at-a-time, and it should Adrian> therefore not be affected by this problem.

It certainly didn't seem to make a difference, after doing a make mrproper and then putting my .config back in place, it still doesn't boot. I'm not doing anything funky in grub, here's my boot options:

    title           2.6.2-rc1-mm3
    root            (hd0,0)
    kernel          /vmlinuz-2.6.2-rc1-mm3 root=/dev/sda2 ro

savedefault
boot

I point this out since the last Oops I got on boot said something about kernel_options, but since I didn't write it down, that's not a good report.

I'll see about falling back to 2.6.1-mm5 and then to 2.6.2-rc1 and seeing what happens. I could even try going back to 2.6.1 plain as well.

Any suggestions? Or any other info I can provide here?

John

John Stoffel

2004-01-25 23:26 UTC #61 lore raw

Re: [patch] Re: Kernels > 2.6.1-mm3 do not boot. - SOLVED

Andi> Ok, then it is something in -mm*. I would suspect the new weird Andi> CPU configuration stuff. Can you double check you configured Andi> your CPU correctly?

As I recall (and I'll test tonight) it didn't make a difference if I chose just the PIII config, or if I compiled for I386 on up to PIII using the new selection stuff. Check the .config I posted before.

I've got a laptop here, so maybe I can configure the serial console and get a copy of the boot messages so I can post them. We'll see if I get a chance to do this tongiht.

Right now, 2.6.1-mm5 is compiling, I should be testing it, then 2.6.2-rc1 in an hour.

John

Andi Kleen

2004-01-25 23:49 UTC #21 lore raw

Re: [patch] Re: Kernels > 2.6.1-mm3 do not boot. - SOLVED

Quoted 5 lines · John Stoffel

Quoted 1 line · John Stoffel
Quoted 1 line
More confirmation as I get it.

Quoted 7 lines

Adrian> I'd say that's a different issue: The gcc 3.3 in debian Adrian> unstable doesn't know about -funit-at-a-time, and it should Adrian> therefore not be affected by this problem.
It certainly didn't seem to make a difference, after doing a make mrproper and then putting my .config back in place, it still doesn't boot. I'm not doing anything funky in grub, here's my boot options:

Can you apply the appended patch and boot with earlyprintk=serial (+ serial console with 38400 baud on ttyS0 and a terminal program that does logging on the other side). If you don't have a serial console you can also use earlyprintk=vga , but that would require writing down what's on the screen.

What does it say?

-Andi

arch/i386/Kconfig renamed from arch/i386/Kconfig-o +4 -0

diff -u linux-2.6.2rc1mm3/arch/i386/Kconfig-o linux-2.6.2rc1mm3/arch/i386/Kconfig
@@ -1247,6 +1247,10 @@
 	  Say Y here if you are developing drivers or trying to debug and
 	  identify kernel problems.
 
+config EARLY_PRINTK
+       bool
+       default y 
+
 config DEBUG_STACKOVERFLOW
 	bool "Check for stack overflows"
 	depends on DEBUG_KERNEL

arch/i386/kernel/setup.c renamed from arch/i386/kernel/setup.c-o +12 -0

diff -u linux-2.6.2rc1mm3/arch/i386/kernel/setup.c-o linux-2.6.2rc1mm3/arch/i386/kernel/setup.c
@@ -1118,6 +1118,18 @@
 #endif
 	paging_init();
 
+#ifdef CONFIG_EARLY_PRINTK
+	{
+	char *s = strstr(*cmdline_p, "earlyprintk="); 
+	if (s) { 
+	     extern void setup_early_printk(char *);
+	     setup_early_printk(s+12); 
+             printk("early console should work ....\n");
+	}
+	}
+#endif
+
+
 	dmi_scan_machine();
 
 #ifdef CONFIG_X86_GENERICARCH

arch/i386/kernel/Makefile renamed from arch/i386/kernel/Makefile-o +3 -0

diff -u linux-2.6.2rc1mm3/arch/i386/kernel/Makefile-o linux-2.6.2rc1mm3/arch/i386/kernel/Makefile
@@ -32,6 +32,9 @@
 obj-$(CONFIG_ACPI_SRAT) 	+= srat.o
 obj-$(CONFIG_HPET_TIMER) 	+= time_hpet.o
 obj-$(CONFIG_EFI) 		+= efi.o efi_stub.o
+obj-$(CONFIG_EARLY_PRINTK)	+= early_printk.o
+
+early_printk-y := ../../x86_64/kernel/early_printk.o
 
 EXTRA_AFLAGS   := -traditional

arch/x86_64/kernel/early_printk.c renamed from arch/x86_64/kernel/early_printk.c-o +4 -0

diff -u linux-2.6.2rc1mm3/arch/x86_64/kernel/early_printk.c-o linux-2.6.2rc1mm3/arch/x86_64/kernel/early_printk.c
@@ -7,7 +7,11 @@
 
 /* Simple VGA output */
 
+#ifdef __i386__
+#define VGABASE		(__PAGE_OFFSET + 0xb8000UL)
+#else
 #define VGABASE		0xffffffff800b8000UL
+#endif
 
 #define MAX_YPOS	25
 #define MAX_XPOS	80

John Stoffel

2004-01-26 02:40 UTC #22 lore raw

Re: [patch] Re: Kernels > 2.6.1-mm3 do not boot. - SOLVED

Andi,

I've got the serial cable setu, now I'm compiling 2.6.2-rc1 based on the config from 2.6.1-mm5, which is what I'm running right now. So it looks like my issue is possibly with the new CPU selection stuff in 2.6.2-rc1 and later -mm kernels. Hopefully I'll get this up and running soon.

Thanks for your help and the early printk patch.

John

John Stoffel

2004-01-26 03:23 UTC #23 lore raw

Re: [patch] Re: Kernels > 2.6.1-mm3 do not boot. - SOLVED

Andi,

I applied the early-printk patch to 2.6.2-rc1 and here's the serial output I got, before the system just stopped booting:

    Linux version 2.6.2-rc1 (john@jfsnew) (gcc version 3.3.3 20040110
    (prerelease) (Debian)) #4 SMP Sun Jan 25 22:13:38 EST 2004
    BIOS-provided physical RAM map:
     BIOS-e820: 0000000000000000 - 00000000000a0000 (usable)
     BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
     BIOS-e820: 0000000000100000 - 000000002fffe000 (usable)
     BIOS-e820: 000000002fffe000 - 0000000030000000 (reserved)
     BIOS-e820: 00000000fec00000 - 00000000fec10000 (reserved)
     BIOS-e820: 00000000fee00000 - 00000000fee10000 (reserved)
     BIOS-e820: 00000000ffe00000 - 0000000100000000 (reserved)
    767MB LOWMEM available.
    found SMP MP-table at 000fe710
    hm, page 000fe000 reserved twice.
    hm, page 000ff000 reserved twice.
    hm, page 000f0000 reserved twice.
    On node 0 totalpages: 196606
      DMA zone: 4096 pages, LIFO batch:1
      Normal zone: 192510 pages, LIFO batch:16
      HighMem zone: 0 pages, LIFO batch:1

Here's the copied odwn output from tty0, my regular console:

       Booting '2.6.2-rc1'

     root (hd0,0)
      Filesystem type is ext2fs, partition type 0x83
     kernel /vmlinux-2.6.2-rc1 root=sda2 ro console=ttyS0,38400n8
      console=tty0 earlyprintk=serial
	[linux-bzImage, setup=0xa00, size=0x1d3b38]
     savedefault
     boot
     Uncompressing Linux... Ok, booting the kernel.

And that's it. I'll see about applying the patch to the various 2.6.2-rc1-mm kernels as well, and possibly to 2.6.2-rc2, which I just got downloaded. Hmmm... I'll try that one first actually and try to get more info out tonight.

John

Adrian Bunk

2004-01-26 03:27 UTC #62 lore raw

Re: [patch] Re: Kernels > 2.6.1-mm3 do not boot. - SOLVED

Quoted 9 lines · Andi Kleen

Quoted 4 lines · Fabio Coatti
Quoted 2 lines
does official 2.6.2rc1 (not mm) with -funit-at-a-time enabled in the Makefile work?
Yes.
Ok, then it is something in -mm*. I would suspect the new weird CPU configuration stuff. Can you double check you configured your CPU correctly?
...

The .config's were already sent, and they seemed to be correct.

Quoted 1 line

-Andi

cu
Adrian

Signature · 4 lines

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

Adrian Bunk

2004-01-26 03:48 UTC #60 lore raw

Re: [patch] Re: Kernels > 2.6.1-mm3 do not boot. - SOLVED

Quoted 8 lines · Andrew Morton

Quoted 7 lines · Andi Kleen
Quoted 5 lines · Andrew Morton
Quoted 3 lines · Andi Kleen
I would suspect the new weird CPU
configuration stuff.

Quoted 8 lines

Quoted 4 lines
Quoted 1 line
What do you believe is wrong with it?
It's different and it is weird and probably easy to screw up.
I must say that it does seem to be causing quite a few problems and doesn't have a very good benefit:breakage ratio. Maybe we should say that 2.6 has sucky CPU selection and leave it for 2.7.

The cpu selection patch is perhaps a bit prominent and therefore the first suspect in case of problems. After looking at yesterday's problems (including looking through the .config's) I'd claim that my cpu selection changes are definitely not guilty. Besides that it broke "allnoconfig" I haven't yet seen it having big problems caused.

Your impression might be different, and you are the one who makes the decisions.

cu
Adrian

Signature · 4 lines

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

John Stoffel

2004-01-26 04:28 UTC #24 lore raw

Re: [patch] Re: Kernels > 2.6.1-mm3 do not boot. - SOLVED

Just a quick followup, but 2.6.2-rc2 also hung in the exact same spot, after printing out the HighMem zone: line.

Falling back to 2.6.1-mm5 for now. More testing tomorrow evening when I get a chance.

John

Andi Kleen

2004-01-26 05:07 UTC #25 lore raw

Re: [patch] Re: Kernels > 2.6.1-mm3 do not boot. - SOLVED

Quoted 4 lines

On node 0 totalpages: 196606
DMA zone: 4096 pages, LIFO batch:1
Normal zone: 192510 pages, LIFO batch:16
HighMem zone: 0 pages, LIFO batch:1

Ok, it didn't oops. Just hung early. Probably needs some printks to track it down.

And the problem really goes away when you disable -funit-at-a-time ?

-Andi

Andrew Morton

2004-01-26 06:02 UTC #28 lore raw

Re: [patch] Re: Kernels > 2.6.1-mm3 do not boot. - SOLVED

Quoted 3 lines · John Stoffel

Sure, the darn thing wouldn't boot, it kept Oopsing with the
test_wp_bit oops (that I just posted more details about).

Does this fix the test_wp_bit oops?

init/main.c renamed from init/main.c~test_wp_bit-oops-fix +1 -1

@@ -434,9 +434,9 @@ asmlinkage void __init start_kernel(void
 	}
 #endif
 	page_address_init();
+	sort_main_extable();
 	mem_init();
 	kmem_cache_init();
-	sort_main_extable();
 	if (late_time_init)
 		late_time_init();
 	calibrate_delay();

Andi Kleen

2004-01-26 06:11 UTC #29 lore raw

Re: [patch] Re: Kernels > 2.6.1-mm3 do not boot. - SOLVED

Quoted 6 lines · Andrew Morton

Quoted 3 lines · John Stoffel
Sure, the darn thing wouldn't boot, it kept Oopsing with the
test_wp_bit oops (that I just posted more details about).
Does this fix the test_wp_bit oops?

He apparently doesn't have an test_wp_bit oops, but just an hang very early (after mem_init according to early printk)

-Andi

John Stoffel

2004-01-26 14:14 UTC #30 lore raw

Re: [patch] Re: Kernels > 2.6.1-mm3 do not boot. - SOLVED

Quoted 6 lines · Andrew Morton

Quoted 6 lines
Quoted 3 lines · John Stoffel
Sure, the darn thing wouldn't boot, it kept Oopsing with the
test_wp_bit oops (that I just posted more details about).
Does this fix the test_wp_bit oops?

Andi> He apparently doesn't have an test_wp_bit oops, but just an hang Andi> very early (after mem_init according to early printk)

Just to follow up here. On kernels 2.6.2-rc1 and 2.6.2-rc2, it just hangs on bootup and doesn't give any Oops output.

When I tried out 2.6.2-rc1-mm[1,2,3], it would start booting, but oops immediately with the one I posted before, but I've re-created here.

I'm at work now, so I won't be able to do any tests besides remote kernel compiles during the day.

My plan is to apply the patch from Andrew where sort_main_extable() is moved up above mem_init() to both 2.6.2-rc2 and to 2.6.2-rc1-mm3 and see what happens.

Here's my .config for 2.6.2-rc1-mm3:

#
# Automatically generated make config: don't edit
#
CONFIG_X86=y
CONFIG_MMU=y
CONFIG_UID16=y
CONFIG_GENERIC_ISA_DMA=y

#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y
# CONFIG_CLEAN_COMPILE is not set
CONFIG_STANDALONE=y
CONFIG_BROKEN=y
CONFIG_BROKEN_ON_SMP=y

#
# General setup
#
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_BSD_PROCESS_ACCT=y
CONFIG_SYSCTL=y
CONFIG_LOG_BUF_SHIFT=14
# CONFIG_IKCONFIG is not set
# CONFIG_EMBEDDED is not set
CONFIG_KALLSYMS=y
CONFIG_FUTEX=y
CONFIG_EPOLL=y
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_AS=y
CONFIG_IOSCHED_DEADLINE=y
CONFIG_IOSCHED_CFQ=y
# CONFIG_CC_OPTIMIZE_FOR_SIZE is not set

#
# Loadable module support
#
CONFIG_MODULES=y
CONFIG_MODULE_UNLOAD=y
CONFIG_MODULE_FORCE_UNLOAD=y
CONFIG_OBSOLETE_MODPARM=y
# CONFIG_MODVERSIONS is not set
CONFIG_KMOD=y

#
# Processor support
#

#
# Select all processors your kernel should support #
# CONFIG_CPU_386 is not set CONFIG_CPU_486=y
CONFIG_CPU_586=y
CONFIG_CPU_586TSC=y
CONFIG_CPU_586MMX=y
CONFIG_CPU_686=y
CONFIG_CPU_PENTIUMII=y CONFIG_CPU_PENTIUMIII=y
# CONFIG_CPU_PENTIUMM is not set
# CONFIG_CPU_PENTIUM4 is not set
# CONFIG_CPU_K6 is not set
# CONFIG_CPU_K7 is not set
# CONFIG_CPU_K8 is not set
# CONFIG_CPU_CRUSOE is not set
# CONFIG_CPU_WINCHIPC6 is not set
# CONFIG_CPU_WINCHIP2 is not set
# CONFIG_CPU_WINCHIP3D is not set
# CONFIG_CPU_CYRIXIII is not set
# CONFIG_CPU_VIAC3_2 is not set CONFIG_CPU_INTEL=y
CONFIG_X86_CMPXCHG=y
CONFIG_X86_XADD=y CONFIG_X86_L1_CACHE_SHIFT=5 CONFIG_RWSEM_XCHGADD_ALGORITHM=y CONFIG_X86_PPRO_FENCE=y CONFIG_X86_F00F_BUG=y CONFIG_X86_WP_WORKS_OK=y CONFIG_X86_INVLPG=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y CONFIG_X86_ALIGNMENT_16=y CONFIG_X86_BAD_APIC=y CONFIG_X86_INTEL_USERCOPY=y
# CONFIG_X86_4G is not set
# CONFIG_X86_SWITCH_PAGETABLES is not set # CONFIG_X86_4G_VM_LAYOUT is not set
# CONFIG_X86_UACCESS_INDIRECT is not set
# CONFIG_X86_HIGH_ENTRY is not set CONFIG_HPET_TIMER=y CONFIG_HPET_EMULATE_RTC=y
CONFIG_SMP=y
CONFIG_NR_CPUS=8
# CONFIG_SCHED_SMT is not set
# CONFIG_PREEMPT is not set CONFIG_X86_LOCAL_APIC=y CONFIG_X86_IO_APIC=y
# CONFIG_X86_MCE is not set
# CONFIG_TOSHIBA is not set
# CONFIG_I8K is not set
# CONFIG_MICROCODE is not set
# CONFIG_X86_MSR is not set
# CONFIG_X86_CPUID is not set
# CONFIG_EDD is not set
CONFIG_NOHIGHMEM=y
# CONFIG_HIGHMEM4G is not set
# CONFIG_HIGHMEM64G is not set CONFIG_MATH_EMULATION=y
CONFIG_MTRR=y
# CONFIG_EFI is not set CONFIG_HAVE_DEC_LOCK=y
# CONFIG_REGPARM is not set

#
# Power management options (ACPI, APM)
#
# CONFIG_PM is not set

#
# ACPI (Advanced Configuration and Power Interface) Support #
CONFIG_ACPI=y
CONFIG_ACPI_BOOT=y
CONFIG_ACPI_INTERPRETER=y
CONFIG_ACPI_AC=m
CONFIG_ACPI_BATTERY=m
CONFIG_ACPI_BUTTON=m
CONFIG_ACPI_FAN=m
CONFIG_ACPI_PROCESSOR=m
CONFIG_ACPI_THERMAL=m
CONFIG_ACPI_ASUS=m
CONFIG_ACPI_TOSHIBA=m
CONFIG_ACPI_DEBUG=y
CONFIG_ACPI_BUS=y
CONFIG_ACPI_EC=y
CONFIG_ACPI_POWER=y
CONFIG_ACPI_PCI=y
CONFIG_ACPI_SYSTEM=y
# CONFIG_ACPI_RELAXED_AML is not set
# CONFIG_X86_PM_TIMER is not set

#
# CPU Frequency scaling
#
# CONFIG_CPU_FREQ is not set

#
# Bus options (PCI, PCMCIA, EISA, MCA, ISA)
#
CONFIG_PCI=y
# CONFIG_PCI_GOBIOS is not set
# CONFIG_PCI_GODIRECT is not set
CONFIG_PCI_GOANY=y
CONFIG_PCI_BIOS=y
CONFIG_PCI_DIRECT=y
# CONFIG_PCI_USE_VECTOR is not set
CONFIG_PCI_LEGACY_PROC=y
CONFIG_PCI_NAMES=y
CONFIG_ISA=y
# CONFIG_EISA is not set
# CONFIG_MCA is not set
# CONFIG_SCx200 is not set
CONFIG_HOTPLUG=y

#
# PCMCIA/CardBus support
#
# CONFIG_PCMCIA is not set
CONFIG_PCMCIA_PROBE=y

#
# PCI Hotplug Support
#
# CONFIG_HOTPLUG_PCI is not set

#
# Executable file formats
#
CONFIG_BINFMT_ELF=y
CONFIG_BINFMT_AOUT=y
CONFIG_BINFMT_MISC=y

#
# Device Drivers
#

#
# Generic Driver Options
#
# CONFIG_FW_LOADER is not set

#
# Memory Technology Devices (MTD)
#
# CONFIG_MTD is not set

#
# Plug and Play support
#
CONFIG_PNP=y
CONFIG_PNP_DEBUG=y

#
# Protocols
#
CONFIG_ISAPNP=y
CONFIG_PNPBIOS=y
# CONFIG_PNPBIOS_PROC_FS is not set

#
# Block devices
#
CONFIG_BLK_DEV_FD=y
# CONFIG_BLK_DEV_XD is not set
# CONFIG_PARIDE is not set
# CONFIG_BLK_CPQ_DA is not set
# CONFIG_BLK_CPQ_CISS_DA is not set
# CONFIG_BLK_DEV_DAC960 is not set
# CONFIG_BLK_DEV_UMEM is not set
CONFIG_BLK_DEV_LOOP=y
# CONFIG_BLK_DEV_CRYPTOLOOP is not set
CONFIG_BLK_DEV_NBD=y
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_SIZE=4096
# CONFIG_BLK_DEV_INITRD is not set
CONFIG_LBD=y

#
# ATA/ATAPI/MFM/RLL support
#
CONFIG_IDE=y
CONFIG_BLK_DEV_IDE=y

#
# IDE chipset support/bugfixes
#
CONFIG_IDE_GENERIC=y
# CONFIG_BLK_DEV_CMD640 is not set
# CONFIG_BLK_DEV_IDEPNP is not set
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_IDEPCI_SHARE_IRQ=y
# CONFIG_BLK_DEV_OFFBOARD is not set
CONFIG_BLK_DEV_GENERIC=y
# CONFIG_BLK_DEV_OPTI621 is not set
# CONFIG_BLK_DEV_RZ1000 is not set
CONFIG_BLK_DEV_IDEDMA_PCI=y
# CONFIG_BLK_DEV_IDEDMA_FORCED is not set
CONFIG_IDEDMA_PCI_AUTO=y
# CONFIG_IDEDMA_ONLYDISK is not set
# CONFIG_IDEDMA_PCI_WIP is not set
CONFIG_BLK_DEV_ADMA=y
# CONFIG_BLK_DEV_AEC62XX is not set
# CONFIG_BLK_DEV_ALI15X3 is not set
# CONFIG_BLK_DEV_AMD74XX is not set
# CONFIG_BLK_DEV_CMD64X is not set
# CONFIG_BLK_DEV_TRIFLEX is not set
# CONFIG_BLK_DEV_CY82C693 is not set
# CONFIG_BLK_DEV_CS5520 is not set
# CONFIG_BLK_DEV_CS5530 is not set
# CONFIG_BLK_DEV_HPT34X is not set
# CONFIG_BLK_DEV_HPT366 is not set
# CONFIG_BLK_DEV_SC1200 is not set
CONFIG_BLK_DEV_PIIX=y
# CONFIG_BLK_DEV_NS87415 is not set
# CONFIG_BLK_DEV_PDC202XX_OLD is not set
# CONFIG_BLK_DEV_PDC202XX_NEW is not set
# CONFIG_BLK_DEV_SVWKS is not set
# CONFIG_BLK_DEV_SIIMAGE is not set
# CONFIG_BLK_DEV_SIS5513 is not set
# CONFIG_BLK_DEV_SLC90E66 is not set
# CONFIG_BLK_DEV_TRM290 is not set
# CONFIG_BLK_DEV_VIA82CXXX is not set
# CONFIG_IDE_CHIPSETS is not set
CONFIG_BLK_DEV_IDEDMA=y
# CONFIG_IDEDMA_IVB is not set
CONFIG_IDEDMA_AUTO=y
# CONFIG_DMA_NONPCI is not set
# CONFIG_BLK_DEV_HD is not set

#
# SCSI device support
#
CONFIG_SCSI=y
CONFIG_SCSI_PROC_FS=y

#
# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=y
CONFIG_MAX_SD_DISKS=16
CONFIG_CHR_DEV_ST=y
# CONFIG_CHR_DEV_OSST is not set
CONFIG_BLK_DEV_SR=y
# CONFIG_BLK_DEV_SR_VENDOR is not set
CONFIG_CHR_DEV_SG=y

#
# Some SCSI devices (e.g. CD jukebox) support multiple LUNs #
CONFIG_SCSI_MULTI_LUN=y
CONFIG_SCSI_REPORT_LUNS=y
CONFIG_SCSI_CONSTANTS=y
CONFIG_SCSI_LOGGING=y

#
# SCSI low-level drivers
#
# CONFIG_BLK_DEV_3W_XXXX_RAID is not set
# CONFIG_SCSI_7000FASST is not set
# CONFIG_SCSI_ACARD is not set
# CONFIG_SCSI_AHA152X is not set
# CONFIG_SCSI_AHA1542 is not set
# CONFIG_SCSI_AACRAID is not set
CONFIG_SCSI_AIC7XXX=y
CONFIG_AIC7XXX_CMDS_PER_DEVICE=32
CONFIG_AIC7XXX_RESET_DELAY_MS=15000
# CONFIG_AIC7XXX_BUILD_FIRMWARE is not set
CONFIG_AIC7XXX_DEBUG_ENABLE=y
CONFIG_AIC7XXX_DEBUG_MASK=0
CONFIG_AIC7XXX_REG_PRETTY_PRINT=y
# CONFIG_SCSI_AIC7XXX_OLD is not set
# CONFIG_SCSI_AIC79XX is not set
# CONFIG_SCSI_DPT_I2O is not set
# CONFIG_SCSI_ADVANSYS is not set
# CONFIG_SCSI_IN2000 is not set
# CONFIG_SCSI_AM53C974 is not set
# CONFIG_SCSI_MEGARAID is not set
# CONFIG_SCSI_SATA is not set
# CONFIG_SCSI_BUSLOGIC is not set
# CONFIG_SCSI_CPQFCTS is not set
# CONFIG_SCSI_DMX3191D is not set
# CONFIG_SCSI_DTC3280 is not set
# CONFIG_SCSI_EATA is not set
# CONFIG_SCSI_EATA_PIO is not set
# CONFIG_SCSI_FUTURE_DOMAIN is not set
# CONFIG_SCSI_GDTH is not set
# CONFIG_SCSI_GENERIC_NCR5380 is not set
# CONFIG_SCSI_GENERIC_NCR5380_MMIO is not set
# CONFIG_SCSI_IPS is not set
# CONFIG_SCSI_INITIO is not set
# CONFIG_SCSI_INIA100 is not set
# CONFIG_SCSI_PPA is not set
# CONFIG_SCSI_IMM is not set
# CONFIG_SCSI_NCR53C406A is not set
# CONFIG_SCSI_SYM53C8XX_2 is not set
# CONFIG_SCSI_PAS16 is not set
# CONFIG_SCSI_PCI2000 is not set
# CONFIG_SCSI_PCI2220I is not set
# CONFIG_SCSI_PSI240I is not set
# CONFIG_SCSI_QLOGIC_FAS is not set
# CONFIG_SCSI_QLOGIC_ISP is not set
# CONFIG_SCSI_QLOGIC_FC is not set
# CONFIG_SCSI_QLOGIC_1280 is not set
CONFIG_SCSI_QLA2XXX_CONFIG=y
# CONFIG_SCSI_QLA21XX is not set
# CONFIG_SCSI_QLA22XX is not set
# CONFIG_SCSI_QLA23XX is not set
# CONFIG_SCSI_SEAGATE is not set
# CONFIG_SCSI_SYM53C416 is not set
# CONFIG_SCSI_DC395x is not set
# CONFIG_SCSI_DC390T is not set
# CONFIG_SCSI_T128 is not set
# CONFIG_SCSI_U14_34F is not set
# CONFIG_SCSI_ULTRASTOR is not set
# CONFIG_SCSI_NSP32 is not set
# CONFIG_SCSI_DEBUG is not set

#
# Old CD-ROM drivers (not SCSI, not IDE)
#
# CONFIG_CD_NO_IDESCSI is not set

#
# Multi-device support (RAID and LVM)
#
CONFIG_MD=y
CONFIG_BLK_DEV_MD=y
CONFIG_MD_LINEAR=y
CONFIG_MD_RAID0=y
CONFIG_MD_RAID1=y
CONFIG_MD_RAID5=y
# CONFIG_MD_RAID6 is not set
# CONFIG_MD_MULTIPATH is not set
CONFIG_BLK_DEV_DM=y
# CONFIG_DM_IOCTL_V4 is not set

#
# Fusion MPT device support
#
# CONFIG_FUSION is not set

#
# IEEE 1394 (FireWire) support (EXPERIMENTAL)
#
CONFIG_IEEE1394=m

#
# Subsystem Options
#
# CONFIG_IEEE1394_VERBOSEDEBUG is not set
CONFIG_IEEE1394_OUI_DB=y

#
# Device Drivers
#

#
# Texas Instruments PCILynx requires I2C
#
CONFIG_IEEE1394_OHCI1394=m

#
# Protocol Drivers
#
CONFIG_IEEE1394_VIDEO1394=m
CONFIG_IEEE1394_SBP2=m
# CONFIG_IEEE1394_SBP2_PHYS_DMA is not set
# CONFIG_IEEE1394_ETH1394 is not set
CONFIG_IEEE1394_DV1394=m
CONFIG_IEEE1394_RAWIO=m
CONFIG_IEEE1394_CMP=m
# CONFIG_IEEE1394_AMDTP is not set

#
# I2O device support
#
# CONFIG_I2O is not set

#
# Macintosh device drivers
#

#
# Networking support
#
CONFIG_NET=y

#
# QoS and/or fair queueing
#
# CONFIG_NET_SCHED is not set

#
# Network testing
#
# CONFIG_NET_PKTGEN is not set
CONFIG_NETDEVICES=y

#
# ARCnet devices
#
# CONFIG_ARCNET is not set
CONFIG_DUMMY=m
# CONFIG_BONDING is not set
# CONFIG_EQUALIZER is not set
# CONFIG_TUN is not set
# CONFIG_NET_SB1000 is not set

#
# Tulip family network device support
#
# CONFIG_NET_TULIP is not set
# CONFIG_AT1700 is not set
# CONFIG_DEPCA is not set
# CONFIG_HP100 is not set
# CONFIG_NET_ISA is not set
CONFIG_NET_PCI=y
# CONFIG_PCNET32 is not set
# CONFIG_AMD8111_ETH is not set
# CONFIG_ADAPTEC_STARFIRE is not set
# CONFIG_AC3200 is not set
# CONFIG_APRICOT is not set
# CONFIG_B44 is not set
# CONFIG_FORCEDETH is not set
# CONFIG_CS89x0 is not set
# CONFIG_DGRS is not set
# CONFIG_EEPRO100 is not set
# CONFIG_E100 is not set
# CONFIG_FEALNX is not set
# CONFIG_NATSEMI is not set
# CONFIG_NE2K_PCI is not set
# CONFIG_8139CP is not set
# CONFIG_8139TOO is not set
# CONFIG_SIS900 is not set
# CONFIG_EPIC100 is not set
# CONFIG_SUNDANCE is not set
# CONFIG_TLAN is not set
# CONFIG_VIA_RHINE is not set
# CONFIG_NET_POCKET is not set

#
# Ethernet (10000 Mbit)
#
# CONFIG_IXGB is not set
# CONFIG_FDDI is not set
# CONFIG_HIPPI is not set
# CONFIG_PLIP is not set
# CONFIG_PPP is not set
# CONFIG_SLIP is not set

#
# Wireless LAN (non-hamradio)
#
# CONFIG_NET_RADIO is not set

#
# Token Ring devices
#
# CONFIG_TR is not set
# CONFIG_NET_FC is not set
# CONFIG_RCPCI is not set
# CONFIG_SHAPER is not set
# CONFIG_NETCONSOLE is not set

#
# Wan interfaces
#
# CONFIG_WAN is not set

#
# Amateur Radio support
#
# CONFIG_HAMRADIO is not set

#
# IrDA (infrared) support
#
# CONFIG_IRDA is not set

#
# ISDN subsystem
#
# CONFIG_ISDN_BOOL is not set

#
# Telephony Support
#
# CONFIG_PHONE is not set

#
# Input device support
#
CONFIG_INPUT=y

#
# Userland interfaces
#
CONFIG_INPUT_MOUSEDEV=y
CONFIG_INPUT_MOUSEDEV_PSAUX=y
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
# CONFIG_INPUT_JOYDEV is not set
# CONFIG_INPUT_TSDEV is not set
# CONFIG_INPUT_EVDEV is not set
# CONFIG_INPUT_EVBUG is not set

#
# Character devices
#
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
CONFIG_SERIAL_NONSTANDARD=y
# CONFIG_COMPUTONE is not set
# CONFIG_ROCKETPORT is not set
CONFIG_CYCLADES=y
# CONFIG_CYZ_INTR is not set
# CONFIG_DIGIEPCA is not set
# CONFIG_DIGI is not set
# CONFIG_ESPSERIAL is not set
# CONFIG_MOXA_INTELLIO is not set
# CONFIG_MOXA_SMARTIO is not set
# CONFIG_ISI is not set
# CONFIG_SYNCLINK is not set
# CONFIG_SYNCLINKMP is not set
# CONFIG_N_HDLC is not set
# CONFIG_RISCOM8 is not set
# CONFIG_SPECIALIX is not set
# CONFIG_SX is not set
# CONFIG_RIO is not set
# CONFIG_STALDRV is not set

#
# Serial drivers
#
CONFIG_SERIAL_8250=y
# CONFIG_SERIAL_8250_CONSOLE is not set
CONFIG_SERIAL_8250_ACPI=y
CONFIG_SERIAL_8250_NR_UARTS=4
# CONFIG_SERIAL_8250_EXTENDED is not set

#
# Mice
#
CONFIG_BUSMOUSE=y
# CONFIG_QIC02_TAPE is not set

#
# IPMI
#
# CONFIG_IPMI_HANDLER is not set

#
# Watchdog Cards
#
# CONFIG_WATCHDOG is not set
# CONFIG_HW_RANDOM is not set
# CONFIG_NVRAM is not set
CONFIG_RTC=y
# CONFIG_DTLK is not set
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set
# CONFIG_SONYPI is not set

#
# Ftape, the floppy tape device driver
#
# CONFIG_FTAPE is not set
CONFIG_AGP=y
# CONFIG_AGP_ALI is not set
# CONFIG_AGP_ATI is not set
# CONFIG_AGP_AMD is not set
# CONFIG_AGP_AMD64 is not set
CONFIG_AGP_INTEL=y
# CONFIG_AGP_NVIDIA is not set
# CONFIG_AGP_SIS is not set
# CONFIG_AGP_SWORKS is not set
# CONFIG_AGP_VIA is not set
# CONFIG_DRM is not set
# CONFIG_MWAVE is not set
# CONFIG_RAW_DRIVER is not set
# CONFIG_HANGCHECK_TIMER is not set

#
# I2C support
#
# CONFIG_I2C is not set

#
# Multimedia devices
#
# CONFIG_VIDEO_DEV is not set

#
# Digital Video Broadcasting Devices
#
# CONFIG_DVB is not set

#
# Graphics support
#
# CONFIG_FB is not set
# CONFIG_VIDEO_SELECT is not set

#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
# CONFIG_MDA_CONSOLE is not set
CONFIG_DUMMY_CONSOLE=y

#
# Sound
#
CONFIG_SOUND=m

#
# Advanced Linux Sound Architecture
#
CONFIG_SND=m
CONFIG_SND_SEQUENCER=m
CONFIG_SND_SEQ_DUMMY=m
CONFIG_SND_OSSEMUL=y
CONFIG_SND_MIXER_OSS=m
CONFIG_SND_PCM_OSS=m
CONFIG_SND_SEQUENCER_OSS=y
CONFIG_SND_RTCTIMER=m
CONFIG_SND_VERBOSE_PRINTK=y
CONFIG_SND_DEBUG=y
CONFIG_SND_DEBUG_MEMORY=y
CONFIG_SND_DEBUG_DETECT=y

#
# Generic devices
#
# CONFIG_SND_DUMMY is not set
# CONFIG_SND_VIRMIDI is not set
# CONFIG_SND_MTPAV is not set
# CONFIG_SND_SERIAL_U16550 is not set
# CONFIG_SND_MPU401 is not set

#
# ISA devices
#
# CONFIG_SND_AD1816A is not set
# CONFIG_SND_AD1848 is not set
# CONFIG_SND_CS4231 is not set
# CONFIG_SND_CS4232 is not set
# CONFIG_SND_CS4236 is not set
# CONFIG_SND_ES968 is not set
# CONFIG_SND_ES1688 is not set
# CONFIG_SND_ES18XX is not set
# CONFIG_SND_GUSCLASSIC is not set
# CONFIG_SND_GUSEXTREME is not set
# CONFIG_SND_GUSMAX is not set
# CONFIG_SND_INTERWAVE is not set
# CONFIG_SND_INTERWAVE_STB is not set
# CONFIG_SND_OPTI92X_AD1848 is not set
# CONFIG_SND_OPTI92X_CS4231 is not set
# CONFIG_SND_OPTI93X is not set
# CONFIG_SND_SB8 is not set
# CONFIG_SND_SB16 is not set
# CONFIG_SND_SBAWE is not set
# CONFIG_SND_WAVEFRONT is not set
# CONFIG_SND_ALS100 is not set
# CONFIG_SND_AZT2320 is not set
# CONFIG_SND_CMI8330 is not set
# CONFIG_SND_DT019X is not set
# CONFIG_SND_OPL3SA2 is not set
# CONFIG_SND_SGALAXY is not set
# CONFIG_SND_SSCAPE is not set

#
# PCI devices
#
# CONFIG_SND_ALI5451 is not set
# CONFIG_SND_AZT3328 is not set
# CONFIG_SND_CS46XX is not set
# CONFIG_SND_CS4281 is not set
# CONFIG_SND_EMU10K1 is not set
# CONFIG_SND_KORG1212 is not set
# CONFIG_SND_NM256 is not set
# CONFIG_SND_RME32 is not set
# CONFIG_SND_RME96 is not set
# CONFIG_SND_RME9652 is not set
# CONFIG_SND_HDSP is not set
# CONFIG_SND_TRIDENT is not set
# CONFIG_SND_YMFPCI is not set
# CONFIG_SND_ALS4000 is not set
# CONFIG_SND_CMIPCI is not set
# CONFIG_SND_ENS1370 is not set
CONFIG_SND_ENS1371=m
# CONFIG_SND_ES1938 is not set
# CONFIG_SND_ES1968 is not set
# CONFIG_SND_MAESTRO3 is not set
# CONFIG_SND_FM801 is not set
# CONFIG_SND_ICE1712 is not set
# CONFIG_SND_ICE1724 is not set
# CONFIG_SND_INTEL8X0 is not set
# CONFIG_SND_SONICVIBES is not set
# CONFIG_SND_VIA82XX is not set
# CONFIG_SND_VX222 is not set

#
# ALSA USB devices
#
# CONFIG_SND_USB_AUDIO is not set

#
# Open Sound System
#
# CONFIG_SOUND_PRIME is not set

#
# USB support
#
CONFIG_USB=y
# CONFIG_USB_DEBUG is not set

#
# Miscellaneous USB options
#
CONFIG_USB_DEVICEFS=y
# CONFIG_USB_BANDWIDTH is not set
# CONFIG_USB_DYNAMIC_MINORS is not set

#
# USB Host Controller Drivers
#
CONFIG_USB_EHCI_HCD=m
CONFIG_USB_OHCI_HCD=m
# CONFIG_USB_UHCI_HCD is not set

#
# USB Device Class drivers
#
# CONFIG_USB_AUDIO is not set
# CONFIG_USB_BLUETOOTH_TTY is not set
# CONFIG_USB_MIDI is not set
# CONFIG_USB_ACM is not set
CONFIG_USB_PRINTER=m
CONFIG_USB_STORAGE=m
# CONFIG_USB_STORAGE_DEBUG is not set
CONFIG_USB_STORAGE_DATAFAB=y
CONFIG_USB_STORAGE_FREECOM=y
CONFIG_USB_STORAGE_ISD200=y
CONFIG_USB_STORAGE_DPCM=y
# CONFIG_USB_STORAGE_HP8200e is not set
CONFIG_USB_STORAGE_SDDR09=y
CONFIG_USB_STORAGE_SDDR55=y
CONFIG_USB_STORAGE_JUMPSHOT=y

#
# USB Human Interface Devices (HID)
#
CONFIG_USB_HID=m
CONFIG_USB_HIDINPUT=y
# CONFIG_HID_FF is not set
CONFIG_USB_HIDDEV=y

#
# USB HID Boot Protocol drivers
#
CONFIG_USB_KBD=m
CONFIG_USB_MOUSE=m
# CONFIG_USB_AIPTEK is not set
# CONFIG_USB_WACOM is not set
# CONFIG_USB_KBTAB is not set
# CONFIG_USB_POWERMATE is not set
# CONFIG_USB_XPAD is not set

#
# USB Imaging devices
#
# CONFIG_USB_MDC800 is not set
CONFIG_USB_SCANNER=m
# CONFIG_USB_MICROTEK is not set
# CONFIG_USB_HPUSBSCSI is not set

#
# USB Multimedia devices
#
# CONFIG_USB_DABUSB is not set

#
# Video4Linux support is needed for USB Multimedia device support #

#
# USB Network adaptors
#
# CONFIG_USB_CATC is not set
# CONFIG_USB_KAWETH is not set
# CONFIG_USB_PEGASUS is not set
# CONFIG_USB_RTL8150 is not set
# CONFIG_USB_USBNET is not set

#
# USB port drivers
#
# CONFIG_USB_USS720 is not set

#
# USB Serial Converter support
#
# CONFIG_USB_SERIAL is not set

#
# USB Miscellaneous drivers
#
# CONFIG_USB_EMI62 is not set
# CONFIG_USB_EMI26 is not set
# CONFIG_USB_TIGL is not set
# CONFIG_USB_AUERSWALD is not set
# CONFIG_USB_RIO500 is not set
# CONFIG_USB_LEGOTOWER is not set
# CONFIG_USB_BRLVGER is not set
# CONFIG_USB_LCD is not set
# CONFIG_USB_LED is not set
# CONFIG_USB_TEST is not set
# CONFIG_USB_GADGET is not set

#
# File systems
#
CONFIG_EXT2_FS=y
CONFIG_EXT2_FS_XATTR=y
# CONFIG_EXT2_FS_POSIX_ACL is not set
# CONFIG_EXT2_FS_SECURITY is not set
CONFIG_EXT3_FS=y
CONFIG_EXT3_FS_XATTR=y
# CONFIG_EXT3_FS_POSIX_ACL is not set
# CONFIG_EXT3_FS_SECURITY is not set
CONFIG_JBD=y
# CONFIG_JBD_DEBUG is not set
CONFIG_FS_MBCACHE=y
# CONFIG_REISERFS_FS is not set
# CONFIG_JFS_FS is not set
# CONFIG_XFS_FS is not set
# CONFIG_MINIX_FS is not set
# CONFIG_ROMFS_FS is not set
# CONFIG_QUOTA is not set
# CONFIG_AUTOFS_FS is not set
CONFIG_AUTOFS4_FS=y

#
# CD-ROM/DVD Filesystems
#
CONFIG_ISO9660_FS=y
CONFIG_JOLIET=y
# CONFIG_ZISOFS is not set
CONFIG_UDF_FS=y

#
# DOS/FAT/NT Filesystems
#
CONFIG_FAT_FS=y
CONFIG_MSDOS_FS=y
CONFIG_VFAT_FS=y
# CONFIG_NTFS_FS is not set

#
# Miscellaneous filesystems
#
# CONFIG_ADFS_FS is not set
# CONFIG_AFFS_FS is not set
# CONFIG_HFS_FS is not set
# CONFIG_BEFS_FS is not set
# CONFIG_BFS_FS is not set
# CONFIG_EFS_FS is not set
# CONFIG_CRAMFS is not set
# CONFIG_VXFS_FS is not set
# CONFIG_HPFS_FS is not set
# CONFIG_QNX4FS_FS is not set
# CONFIG_SYSV_FS is not set
# CONFIG_UFS_FS is not set

#
# Network File Systems
#
CONFIG_NFS_FS=y
CONFIG_NFS_V3=y
# CONFIG_NFS_V4 is not set
CONFIG_NFS_DIRECTIO=y
CONFIG_NFSD=y
CONFIG_NFSD_V3=y
# CONFIG_NFSD_V4 is not set
# CONFIG_NFSD_TCP is not set
CONFIG_LOCKD=y
CONFIG_LOCKD_V4=y
CONFIG_EXPORTFS=y
CONFIG_SUNRPC=y
# CONFIG_SUNRPC_GSS is not set
CONFIG_SMB_FS=y
# CONFIG_SMB_NLS_DEFAULT is not set
CONFIG_CIFS=y
# CONFIG_NCP_FS is not set
# CONFIG_CODA_FS is not set
# CONFIG_INTERMEZZO_FS is not set
# CONFIG_AFS_FS is not set

#
# Partition Types
#
CONFIG_PARTITION_ADVANCED=y
# CONFIG_ACORN_PARTITION is not set
# CONFIG_OSF_PARTITION is not set
# CONFIG_AMIGA_PARTITION is not set
# CONFIG_ATARI_PARTITION is not set
# CONFIG_MAC_PARTITION is not set
CONFIG_MSDOS_PARTITION=y
# CONFIG_BSD_DISKLABEL is not set
# CONFIG_MINIX_SUBPARTITION is not set
# CONFIG_SOLARIS_X86_PARTITION is not set
# CONFIG_UNIXWARE_DISKLABEL is not set
# CONFIG_LDM_PARTITION is not set
# CONFIG_NEC98_PARTITION is not set
# CONFIG_SGI_PARTITION is not set
# CONFIG_ULTRIX_PARTITION is not set
# CONFIG_SUN_PARTITION is not set
# CONFIG_EFI_PARTITION is not set

#
# Profiling support
#
# CONFIG_PROFILING is not set

#
# Kernel hacking
#
CONFIG_DEBUG_KERNEL=y
CONFIG_DEBUG_STACKOVERFLOW=y
CONFIG_DEBUG_SLAB=y
CONFIG_DEBUG_IOVIRT=y
CONFIG_MAGIC_SYSRQ=y
CONFIG_DEBUG_SPINLOCK=y
CONFIG_DEBUG_PAGEALLOC=y
# CONFIG_SPINLINE is not set
CONFIG_DEBUG_INFO=y
# CONFIG_LOCKMETER is not set
CONFIG_DEBUG_SPINLOCK_SLEEP=y
# CONFIG_KGDB is not set
CONFIG_FRAME_POINTER=y
CONFIG_X86_FIND_SMP_CONFIG=y
CONFIG_X86_MPPARSE=y

#
# Security options
#
# CONFIG_SECURITY is not set

#
# Cryptographic options
#
# CONFIG_CRYPTO is not set

#
# Library routines
#
CONFIG_CRC32=y
CONFIG_X86_SMP=y
CONFIG_X86_HT=y
CONFIG_X86_BIOS_REBOOT=y
CONFIG_X86_TRAMPOLINE=y
CONFIG_PC=y

John Stoffel

2004-01-26 14:15 UTC #26 lore raw

Re: [patch] Re: Kernels > 2.6.1-mm3 do not boot. - SOLVED

Quoted 5 lines

Quoted 5 lines
On node 0 totalpages: 196606
DMA zone: 4096 pages, LIFO batch:1 Normal zone: 192510 pages, LIFO batch:16 HighMem zone: 0 pages, LIFO batch:1

Andi> Ok, it didn't oops. Just hung early. Probably needs some printks Andi> to track it down.

Andi> And the problem really goes away when you disable -funit-at-a-time ?

This was from both 2.6.2-rc1 and 2.6.2-rc2, and since the later doesn't have the -funit-at-time declaration in the Makefile, I don't think that's the problem.

My gcc version is:

Quoted 1 line

gcc --version

    gcc.real (GCC) 3.3.3 20040110 (prerelease) (Debian)

John

Andi Kleen

2004-01-26 14:38 UTC #27 lore raw

Re: [patch] Re: Kernels > 2.6.1-mm3 do not boot. - SOLVED

Quoted 11 lines · John Stoffel

Quoted 5 lines
Quoted 5 lines
On node 0 totalpages: 196606
DMA zone: 4096 pages, LIFO batch:1 Normal zone: 192510 pages, LIFO batch:16 HighMem zone: 0 pages, LIFO batch:1
Andi> Ok, it didn't oops. Just hung early. Probably needs some printks Andi> to track it down.
Andi> And the problem really goes away when you disable -funit-at-a-time ?

Quoted 8 lines

This was from both 2.6.2-rc1 and 2.6.2-rc2, and since the later doesn't have the -funit-at-time declaration in the Makefile, I don't think that's the problem.
My gcc version is:
Quoted 1 line
gcc --version
    gcc.real (GCC) 3.3.3 20040110 (prerelease) (Debian)

Well, you have some different problem then. I was assuming you used -funit-at-a-time because you posted on the unit-at-a-time thread. I don't know what's wrong with your kernel, sorry.

If it happened to me here I would add printks to the early kernel initialisation until I figured out where it hangs.
(it's somewhere after mem_init and before console_init in init/main.c:start_kernel). You could try that, together with earlyprintk.

-Andi

Fabio Coatti

2004-01-26 14:51 UTC #31 lore raw

Re: [patch] Re: Kernels > 2.6.1-mm3 do not boot. - SOLVED

Alle Monday 26 January 2004 15:12, John Stoffel ha scritto:

Quoted 7 lines

Just to follow up here. On kernels 2.6.2-rc1 and 2.6.2-rc2, it just hangs on bootup and doesn't give any Oops output.
When I tried out 2.6.2-rc1-mm[1,2,3], it would start booting, but oops immediately with the one I posted before, but I've re-created here.

It seems a little bit different from my situation: 2.6.2-rcX (basically non -mm versions) boots and works just fine (besides some oopses on shutdown, but this is another story, I'll investigate further on this).
-mm series, both 2.6.2-rcX-mmY and 2.6.1-mmZ with Z > 3 hangs after decompressing image, if I leave -funit-at-time in Makefile. I can redo any of these tests, I can also use a serial interface to capture any "hidden" oops, if someone sends me any needed patch to show some data (i.e. early printk) and the desired tests.

Quoted 3 lines

I'm at work now, so I won't be able to do any tests besides remote kernel compiles during the day.

The same holds for me :)

Signature · 4 lines

Fabio Coatti       http://www.ferrara.linux.it/members/cova     
Ferrara Linux Users Group           http://ferrara.linux.it
GnuPG fp:9765 A5B6 6843 17BC A646  BE8C FA56 373A 5374 C703
Old SysOps never die... they simply forget their password.

Eric

author

2004-01-26 19:27 UTC #32 lore raw

Re: [patch] Re: Kernels > 2.6.1-mm3 do not boot. - SOLVED

Quoted 5 lines · Andrew Morton

Quoted 2 lines · John Stoffel
Sure, the darn thing wouldn't boot, it kept Oopsing with the
test_wp_bit oops (that I just posted more details about).
Does this fix the test_wp_bit oops?

Yes, it fixes my test_wp_bit oops. But NOW, when booting 2.6.2-rc1-mm3 (which i pathed removing -funit-at-a-time and the wp_but oops patch) I get an oops derefrencing null pointer in blkdev_reread_part.

I booted normal and with vga=ask acpi=off
Here is a close approxamation of what I wrote down by hand.

raid1: raid set md1 active..(blah blah)
Unable to handle null dereference at virtual address 0000008c025b893 *pde = 00000000
oops = 0000 [#1]
PREEMPT SMP
CPU: 0
EIP: 0060 Not Tainted VLI
EIP is at blkdev_reread_part+0x13/0x80

Trace
[<c025bdfe>] blkdev_ioctl+0x30e/0x3b5
[<co17f426>] wake_up_inode+0x6/0x30 (might be 0xb.. cant read my writing)
[<co1bb696>] io_ctl_by_bdev+0x26/0x40
[<c0307e53>] do_md_run+0x493/0x5c0
.....trace continues about 20-30 functions

Let me know if you need more (or more accurate) debugging info. I am very
sorry if I have copied something down incorrectly. If I have, I guess its a great time to learn how to set a up serial console :)

-------------------------
Eric Bambach
Eric at cisu dot net
-------------------------

Andrew Morton

2004-01-26 19:57 UTC #33 lore raw

Re: [patch] Re: Kernels > 2.6.1-mm3 do not boot. - SOLVED

Quoted 11 lines · Eric

Quoted 5 lines · Andrew Morton
Quoted 2 lines · John Stoffel
Sure, the darn thing wouldn't boot, it kept Oopsing with the
test_wp_bit oops (that I just posted more details about).
Does this fix the test_wp_bit oops?
Yes, it fixes my test_wp_bit oops. But NOW, when booting 2.6.2-rc1-mm3 (which i pathed removing -funit-at-a-time and the wp_but oops patch) I get an oops derefrencing null pointer in blkdev_reread_part.

It is likely that this can be fixed by reverting

	ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.2-rc1/2.6.2-rc1-mm3/broken-out/md-06-allow-partitioning.patch

John Stoffel

2004-01-27 00:19 UTC #48 lore raw

2.6.2-rc2 Hangs on boot (was: [patch] Re: Kernels > 2.6.1-mm3 do not boot. - SOLVED)

Quoted 1 line

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
"Andrew" == Andrew Morton <[email protected]> writes:

Quoted 3 lines · Andrew> "John Stoffel" <[email protected]> wrote:

Quoted 3 lines
Sure, the darn thing wouldn't boot, it kept Oopsing with the test_wp_bit oops (that I just posted more details about).

Andrew> Does this fix the test_wp_bit oops?

Andrew> --- 25/init/main.c~test_wp_bit-oops-fix 2004-01-25 15:29:53.000000000 -0800
Andrew> +++ 25-akpm/init/main.c 2004-01-25 15:30:03.000000000 -0800
Andrew> @@ -434,9 +434,9 @@ asmlinkage void __init start_kernel(void

Andrew>  	}
Andrew>  #endif
Andrew>  	page_address_init();

Andrew> + sort_main_extable();
Andrew> mem_init();
Andrew> kmem_cache_init();
Andrew> - sort_main_extable();

Andrew>  	if (late_time_init)
Andrew>  		late_time_init();
Andrew>  	calibrate_delay();

No, nor does this fix my booting problem(s) with 2.6.2-rc2. I'm now back and running 2.6.1-mm5 without any problems. Is there any further info I can give, or patches I can apply? I've applied the early printk patch, the above patch, and I'm at a loss where the problem is.

It hangs at the following spot:

Linux version 2.6.2-rc2 (john@jfsnew) (gcc version 3.3.3 20040110 (prerelease) (Debian)) #2 SMP Mon Jan 26 09:17:00 EST 2004 BIOS-provided physical RAM map:

    BIOS-e820: 0000000000000000 - 00000000000a0000 (usable)
    BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
    BIOS-e820: 0000000000100000 - 000000002fffe000 (usable)
    BIOS-e820: 000000002fffe000 - 0000000030000000 (reserved)
    BIOS-e820: 00000000fec00000 - 00000000fec10000 (reserved)
    BIOS-e820: 00000000fee00000 - 00000000fee10000 (reserved)
    BIOS-e820: 00000000ffe00000 - 0000000100000000 (reserved)

767MB LOWMEM available.
found SMP MP-table at 000fe710
hm, page 000fe000 reserved twice.
hm, page 000ff000 reserved twice.
hm, page 000f0000 reserved twice.
On node 0 totalpages: 196606
DMA zone: 4096 pages, LIFO batch:1
Normal zone: 192510 pages, LIFO batch:16
HighMem zone: 0 pages, LIFO batch:1

Should I start adding in printks, or would it make sense to go back through the various 2.6.2-bk# snapshots looking for where the problem hit?

Here's my PCI info, just in case this info helps:

Quoted 1 line

lspci

    00:00.0 Host bridge: Intel Corp. 440GX - 82443GX Host bridge
    00:01.0 PCI bridge: Intel Corp. 440GX - 82443GX AGP bridge
    00:07.0 ISA bridge: Intel Corp. 82371AB/EB/MB PIIX4 ISA (rev 02)
    00:07.1 IDE interface: Intel Corp. 82371AB/EB/MB PIIX4 IDE (rev 01)
    00:07.2 USB Controller: Intel Corp. 82371AB/EB/MB PIIX4 USB (rev 01)
    00:07.3 Bridge: Intel Corp. 82371AB/EB/MB PIIX4 ACPI (rev 02)
    00:0d.0 RAID bus controller: Triones Technologies, Inc. HPT302 (rev
    01)
    00:10.0 PCI bridge: Hint Corp HB6 Universal PCI-PCI bridge
    (non-transparent mode) (rev 13)
    00:11.0 Ethernet controller: 3Com Corporation 3c905B 100BaseTX
    [Cyclone] (rev 24)
    00:13.0 PCI bridge: Digital Equipment Corporation DECchip 21152 (rev
    03)
    01:00.0 VGA compatible controller: Matrox Graphics, Inc. MGA G400 AGP
    (rev 82)
    02:08.0 USB Controller: NEC Corporation USB (rev 41)
    02:08.1 USB Controller: NEC Corporation USB (rev 41)
    02:08.2 USB Controller: NEC Corporation USB 2.0 (rev 02)
    02:0b.0 FireWire (IEEE 1394): Texas Instruments TSB12LV26 IEEE-1394
    Controller (Link)
    03:06.0 Multimedia audio controller: Ensoniq ES1371 [AudioPCI-97] (rev
    06)
    03:0a.0 SCSI storage controller: Adaptec AHA-2940U2/U2W / 7890/7891
    03:0e.0 SCSI storage controller: Adaptec AIC-7880U (rev 01)

Andrew Morton

2004-01-27 00:38 UTC #49 lore raw

Re: 2.6.2-rc2 Hangs on boot (was: [patch] Re: Kernels > 2.6.1-mm3 do not boot. - SOLVED)

Quoted 25 lines · John Stoffel

...
It hangs at the following spot:

   Linux version 2.6.2-rc2 (john@jfsnew) (gcc version 3.3.3 20040110
   (prerelease) (Debian)) #2 SMP Mon Jan 26 09:17:00 EST 2004
   BIOS-provided physical RAM map:
    BIOS-e820: 0000000000000000 - 00000000000a0000 (usable)
    BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
    BIOS-e820: 0000000000100000 - 000000002fffe000 (usable)
    BIOS-e820: 000000002fffe000 - 0000000030000000 (reserved)
    BIOS-e820: 00000000fec00000 - 00000000fec10000 (reserved)
    BIOS-e820: 00000000fee00000 - 00000000fee10000 (reserved)
    BIOS-e820: 00000000ffe00000 - 0000000100000000 (reserved)
   767MB LOWMEM available.
   found SMP MP-table at 000fe710
   hm, page 000fe000 reserved twice.
   hm, page 000ff000 reserved twice.
   hm, page 000f0000 reserved twice.
   On node 0 totalpages: 196606
     DMA zone: 4096 pages, LIFO batch:1
     Normal zone: 192510 pages, LIFO batch:16
     HighMem zone: 0 pages, LIFO batch:1

Quoted 3 lines

Should I start adding in printks, or would it make sense to go back through the various 2.6.2-bk# snapshots looking for where the problem hit?

Adding printk's is a pretty quick-n-easy way of finding out where it is getting stuck. Just add

#define AAA() printk("%s:%d\n", __FILE__, __LINE__)

to kernel.h and sprinkle AAA()'s everywhere. It takes a few iterations to drill right down to the bug.

Eric

author

2004-01-27 05:44 UTC #34 lore raw

Re: [patch] Re: Kernels > 2.6.1-mm3 do not boot. - SOLVED

Quoted 12 lines · Andrew Morton

Quoted 10 lines · Eric
Quoted 5 lines · Andrew Morton
Quoted 2 lines · John Stoffel
Sure, the darn thing wouldn't boot, it kept Oopsing with the
test_wp_bit oops (that I just posted more details about).
Does this fix the test_wp_bit oops?
Yes, it fixes my test_wp_bit oops. But NOW, when booting 2.6.2-rc1-mm3
(which i pathed removing -funit-at-a-time and the wp_but oops patch) I get an oops derefrencing null pointer in blkdev_reread_part.

Quoted 8 lines

It is likely that this can be fixed by reverting
	ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.2-rc1/2.
6.2-rc1-mm3/broken-out/md-06-allow-partitioning.patch -
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

YES. I finally have a working 2.6.2-rc1-mm3 booted kernel.
Lets review folks---
reverted -funit-at-a-time
patched test_wp_bit so exception tables are sorted sooner reverted md-partition patch
Thank you very much for your help. I hope we all learned something today. I definatly did.
-------------------------
Eric Bambach
Eric at cisu dot net
-------------------------

Andrew Morton

2004-01-27 05:53 UTC #35 lore raw

Re: [patch] Re: Kernels > 2.6.1-mm3 do not boot. - SOLVED

Review

Quoted 6 lines · Eric

YES. I finally have a working 2.6.2-rc1-mm3 booted kernel.
Lets review folks---
(quoted diff) +0 -0
 	reverted -funit-at-a-time
 	patched test_wp_bit so exception tables are sorted sooner
 	reverted md-partition patch

The latter two are understood, but the `-funit-at-a-time' problem is not.

Can you plesae confirm that restoring only -funit-at-a-time again produces a crashy kernel? And that you are using a flavour of gcc-3.3? If so, I guess we'll need to only enable it for gcc-3.4 and later.

Eric

author

2004-01-27 05:57 UTC #36 lore raw

Re: [patch] Re: Kernels > 2.6.1-mm3 do not boot. - SOLVED

Quoted 7 lines · Andrew Morton

Review
Quoted 5 lines · Eric
YES. I finally have a working 2.6.2-rc1-mm3 booted kernel.
Lets review folks---
(quoted diff) +0 -0
 	reverted -funit-at-a-time
 	patched test_wp_bit so exception tables are sorted sooner
 	reverted md-partition patch

Quoted 5 lines

The latter two are understood, but the `-funit-at-a-time' problem is not.
Can you plesae confirm that restoring only -funit-at-a-time again produces a crashy kernel? And that you are using a flavour of gcc-3.3? If so, I guess we'll need to only enable it for gcc-3.4 and later.

Yea ill try it right now. Ill get back to you in about half hour, probably less. Would you like me to send you a complied kernel or some files that my compiler has generated if its still crashy?
I remember reading somewhere on lkml about another problem that hung RIGHT on
boot and it was related to GCC producing an invalid instruction for that particular processor. This smells of badly generated code. Heres a recap of my GCC:

SuSE Linux 8.2
eric:/usr/src/linux-2.6.2-rc1-mm3/linux-2.6.1 # gcc -v
Reading specs from /usr/lib/gcc-lib/i486-suse-linux/3.3/specs Configured with: ../configure --enable-threads=posix --prefix=/usr --with-local-prefix=/usr/local --infodir=/usr/share/info --mandir=/usr/share/man --libdir=/usr/lib --enable-languages=c,c++,f77,objc,java,ada --disable-checking --enable-libgcj --with-gxx-include-dir=/usr/include/g++ --with-slibdir=/lib --with-system-zlib --enable-shared --enable-__cxa_atexit i486-suse-linux Thread model: posix
gcc version 3.3 20030226 (prerelease) (SuSE Linux)

-------------------------
Eric Bambach
Eric at cisu dot net
-------------------------

Eric

author

2004-01-27 06:38 UTC #37 lore raw

Re: [patch] Re: Kernels > 2.6.1-mm3 do not boot. - SOLVED

Quoted 7 lines · Andrew Morton

Review
Quoted 5 lines · Eric
YES. I finally have a working 2.6.2-rc1-mm3 booted kernel.
Lets review folks---
(quoted diff) +0 -0
 	reverted -funit-at-a-time
 	patched test_wp_bit so exception tables are sorted sooner
 	reverted md-partition patch

Quoted 6 lines

The latter two are understood, but the `-funit-at-a-time' problem is not.
Can you plesae confirm that restoring only -funit-at-a-time again produces a crashy kernel? And that you are using a flavour of gcc-3.3? If so, I guess we'll need to only enable it for gcc-3.4 and later.

Yes, confirmed. My version of gcc, I just sent you adding the -funit-at-a-time hung after uncompressing the kernel. I booted a secondary kernel, recompiled without it and all was fine again. Confirmed non-boot for 2.6.2-rc1-mm3 but without a doubt for all kernels previous where -funit-at-a-time is active in the makefile.

-------------------------
Eric Bambach
Eric at cisu dot net
-------------------------

Erik Hensema

2004-01-27 09:40 UTC #50 lore raw

Re: [patch] Re: Kernels > 2.6.1-mm3 do not boot. - SOLVED

Quoted 10 lines · Andrew Morton

Quoted 3 lines · John Stoffel
Sure, the darn thing wouldn't boot, it kept Oopsing with the
test_wp_bit oops (that I just posted more details about).
Does this fix the test_wp_bit oops?

init/main.c asmlinkage void __init start_kernel(void · line 442

Quoted 10 lines

init/main.c renamed from init/main.c~test_wp_bit-oops-fix +1 -1

@@ -434,9 +434,9 @@ asmlinkage void __init start_kernel(void
 	}
 #endif
 	page_address_init();
+	sort_main_extable();
 	mem_init();
 	kmem_cache_init();
-	sort_main_extable();
 	if (late_time_init)
 		late_time_init();
 	calibrate_delay();

This makes 2.6.2-rc2 boot for me.

Signature · 1 line

Erik Hensema <[email protected]>

Andi Kleen

2004-01-27 16:21 UTC #42 lore raw

Re: [patch] Re: Kernels > 2.6.1-mm3 do not boot. - SOLVED

Quoted 2 lines

Can you plesae confirm that restoring only -funit-at-a-time again produces a crashy kernel? And that you are using a flavour of gcc-3.3? If so, I

It works just fine on the SuSE 9.0 3.3-hammer gcc.

So far the reports point to some Mandrake gcc 3.3 having problems (they used an older version of Hammer branch). It's hard to be sure because everybody having any problem with the kernel seems to like to report it to this thread :-) But before just disabling it I would like to track down the problem and see if it's really a compiler issue or something that can be fixed in the kernel.

If you really want to disable it I would prefer to only check for that compiler version and keep it for working 3.3-hammers.

-Andi

Andi Kleen

2004-01-27 16:27 UTC #38 lore raw

Re: [patch] Re: Kernels > 2.6.1-mm3 do not boot. - SOLVED

In reply to Eric

Quoted 14 lines · Eric

Quoted 7 lines · Andrew Morton
Review
Quoted 5 lines · Eric
YES. I finally have a working 2.6.2-rc1-mm3 booted kernel.
Lets review folks---
(quoted diff) +0 -0
 	reverted -funit-at-a-time
 	patched test_wp_bit so exception tables are sorted sooner
 	reverted md-partition patch
Quoted 6 lines
The latter two are understood, but the `-funit-at-a-time' problem is not.
Can you plesae confirm that restoring only -funit-at-a-time again produces a crashy kernel? And that you are using a flavour of gcc-3.3? If so, I guess we'll need to only enable it for gcc-3.4 and later.

Quoted 5 lines

Yes, confirmed. My version of gcc, I just sent you adding the -funit-at-a-time hung after uncompressing the kernel. I booted a secondary kernel, recompiled without it and all was fine again. Confirmed non-boot for 2.6.2-rc1-mm3 but without a doubt for all kernels previous where -funit-at-a-time is active in the makefile.

Ok thanks for the confimration. I will try to reproduce this with the SuSE 8.2 compiler and track it down.

-Andi

Andi Kleen

2004-01-27 18:16 UTC #39 lore raw

Re: [patch] Re: Kernels > 2.6.1-mm3 do not boot. - REALLY SOLVED

In reply to Eric

Quoted 14 lines · Eric

Quoted 7 lines · Andrew Morton
Review
Quoted 5 lines · Eric
YES. I finally have a working 2.6.2-rc1-mm3 booted kernel.
Lets review folks---
(quoted diff) +0 -0
 	reverted -funit-at-a-time
 	patched test_wp_bit so exception tables are sorted sooner
 	reverted md-partition patch
Quoted 6 lines
The latter two are understood, but the `-funit-at-a-time' problem is not.
Can you plesae confirm that restoring only -funit-at-a-time again produces a crashy kernel? And that you are using a flavour of gcc-3.3? If so, I guess we'll need to only enable it for gcc-3.4 and later.

Quoted 5 lines

Yes, confirmed. My version of gcc, I just sent you adding the -funit-at-a-time hung after uncompressing the kernel. I booted a secondary kernel, recompiled without it and all was fine again. Confirmed non-boot for 2.6.2-rc1-mm3 but without a doubt for all kernels previous where -funit-at-a-time is active in the makefile.

Ok, found it. This patch should fix it. The top level asm in process.c assumed that the section was .text, but that is not guaranteed in a funit-at-a-time compiler. It ended up in the setup section and messed up the argument parsing. This bug could have hit with any compiler, it was just plain luck that it worked with newer gcc 3.3 and 3.4.

Please test if it fixes your problem.

Andrew, please merge it if the bug is confirmed to be fixed.

-Andi

arch/i386/kernel/process.c renamed from arch/i386/kernel/process.c-o +4 -2

diff -u linux-2.6.2rc1mm3-test/arch/i386/kernel/process.c-o linux-2.6.2rc1mm3-test/arch/i386/kernel/process.c
@@ -253,13 +253,15 @@
  * the "args".
  */
 extern void kernel_thread_helper(void);
-__asm__(".align 4\n"
+__asm__(".section .text\n"
+	".align 4\n"
 	"kernel_thread_helper:\n\t"
 	"movl %edx,%eax\n\t"
 	"pushl %edx\n\t"
 	"call *%ebx\n\t"
 	"pushl %eax\n\t"
-	"call do_exit");
+	"call do_exit\n"
+	".previous");
 
 /*
  * Create a kernel thread

Eric

author

2004-01-27 19:33 UTC #40 lore raw

Re: [patch] Re: Kernels > 2.6.1-mm3 do not boot. - REALLY SOLVED

Quoted 22 lines · Andi Kleen

Quoted 15 lines · Eric
Quoted 7 lines · Andrew Morton
Review
Quoted 5 lines · Eric
YES. I finally have a working 2.6.2-rc1-mm3 booted kernel.
Lets review folks---
(quoted diff) +0 -0
 	reverted -funit-at-a-time
 	patched test_wp_bit so exception tables are sorted sooner
 	reverted md-partition patch
Quoted 6 lines
The latter two are understood, but the `-funit-at-a-time' problem is not.
Can you plesae confirm that restoring only -funit-at-a-time again produces a crashy kernel? And that you are using a flavour of gcc-3.3?
If so, I guess we'll need to only enable it for gcc-3.4 and later.
Quoted 5 lines
Yes, confirmed. My version of gcc, I just sent you adding the -funit-at-a-time hung after uncompressing the kernel. I booted a secondary kernel, recompiled without it and all was fine again. Confirmed non-boot for 2.6.2-rc1-mm3 but without a doubt for all kernels previous where -funit-at-a-time is active in the makefile.

Quoted 7 lines

Ok, found it. This patch should fix it. The top level asm in process.c assumed that the section was .text, but that is not guaranteed in a funit-at-a-time compiler. It ended up in the setup section and messed up the argument parsing. This bug could have hit with any compiler, it was just plain luck that it worked with newer gcc 3.3 and 3.4.
Please test if it fixes your problem.

Yes. Confirmed. Lets review again.
-removed -funit from makefile
patched to fix exception table sorting
reverted md-partition-patch
BOOTS
add -funit again
FAILS
leave -funit active in makefile
patch with patch below
BOOTS

This patch is confirmed to fix the boot with -funit-at-a-time with 2.6.2-rc1-mm2 with gcc(below)

Thanks so much for everyones attention in the matter.

bot403@eric:~> gcc -v
Reading specs from /usr/lib/gcc-lib/i486-suse-linux/3.3/specs Configured with: ../configure --enable-threads=posix --prefix=/usr --with-local-prefix=/usr/local --infodir=/usr/share/info --mandir=/usr/share/man --libdir=/usr/lib --enable-languages=c,c++,f77,objc,java,ada --disable-checking --enable-libgcj --with-gxx-include-dir=/usr/include/g++ --with-slibdir=/lib --with-system-zlib --enable-shared --enable-__cxa_atexit i486-suse-linux Thread model: posix
gcc version 3.3 20030226 (prerelease) (SuSE Linux)

Quoted 17 lines

Andrew, please merge it if the bug is confirmed to be fixed.
-Andi
diff -u linux-2.6.2rc1mm3-test/arch/i386/kernel/process.c-o linux-2.6.2rc1mm3-test/arch/i386/kernel/process.c ---
linux-2.6.2rc1mm3-test/arch/i386/kernel/process.c-o 2004-01-27
02:26:39.000000000 +0100 +++
linux-2.6.2rc1mm3-test/arch/i386/kernel/process.c 2004-01-27
19:09:41.131460832 +0100 @@ -253,13 +253,15 @@
* the "args".
*/
extern void kernel_thread_helper(void);
arch/i386/kernel/process.c renamed from arch/i386/kernel/process.c-o +2 -1
-__asm__(".align 4\n"
+__asm__(".section .text\n"
+	".align 4\n"
 	"kernel_thread_helper:\n\t"

arch/i386/kernel/process.c line 267

Quoted 10 lines

arch/i386/kernel/process.c renamed from arch/i386/kernel/process.c-o +2 -1

 	"movl %edx,%eax\n\t"
 	"pushl %edx\n\t"
 	"call *%ebx\n\t"
 	"pushl %eax\n\t"
-	"call do_exit");
+	"call do_exit\n"
+	".previous");
 
 /*
  * Create a kernel thread

-------------------------
Eric Bambach
Eric at cisu dot net
-------------------------

Andrew Morton

2004-01-27 20:56 UTC #43 lore raw

Re: [patch] Re: Kernels > 2.6.1-mm3 do not boot. - SOLVED

Quoted 13 lines · Andi Kleen

Quoted 3 lines
Can you plesae confirm that restoring only -funit-at-a-time again produces a crashy kernel? And that you are using a flavour of gcc-3.3? If so, I
It works just fine on the SuSE 9.0 3.3-hammer gcc.
So far the reports point to some Mandrake gcc 3.3 having problems (they used an older version of Hammer branch). It's hard to be sure because everybody having any problem with the kernel seems to like to report it to this thread :-) But before just disabling it I would like to track down the problem and see if it's really a compiler issue or something that can be fixed in the kernel.

Quoted 2 lines

If you really want to disable it I would prefer to only check for that compiler version and keep it for working 3.3-hammers.

I've moved the enabling of -funit-at-a-time out of Makefile and down into arch/i386/Makefile, and I changed to require gcc-3.4 or higher.

So if you want to use -funit-at-a-time on gcc-3.3/hammer you can do so.

Fabio Coatti

2004-01-27 21:11 UTC #41 lore raw

Re: [patch] Re: Kernels > 2.6.1-mm3 do not boot. - REALLY SOLVED

Alle Tuesday 27 January 2004 19:15, Andi Kleen ha scritto:

Quoted 5 lines

Ok, found it. This patch should fix it. The top level asm in process.c assumed that the section was .text, but that is not guaranteed in a funit-at-a-time compiler. It ended up in the setup section and messed up the argument parsing. This bug could have hit with any compiler, it was just plain luck that it worked with newer gcc 3.3 and 3.4.

Confirmed here. 2.6.2-rc1-mm3 boots just fine with this patch; without patch it hangs just as described before.
(-funit-at-a-time enabled, of course).

Many thanks to all.

Signature · 4 lines

Fabio Coatti       http://www.ferrara.linux.it/members/cova     
Ferrara Linux Users Group           http://ferrara.linux.it
GnuPG fp:9765 A5B6 6843 17BC A646  BE8C FA56 373A 5374 C703
Old SysOps never die... they simply forget their password.

Andi Kleen

2004-01-27 22:31 UTC #44 lore raw

Re: [patch] Re: Kernels > 2.6.1-mm3 do not boot. - SOLVED