Messages in this thread | | | From | Eric <> | Subject | Re: [patch] Re: Kernels > 2.6.1-mm3 do not boot. - SOLVED | Date | Mon, 26 Jan 2004 23:57:07 -0600 |
| |
On Monday 26 January 2004 23:50, Andrew Morton wrote: > Eric <eric@cisu.net> wrote: > > 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 > > 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 ------------------------- - 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/
| |