From: Eric <eric@cisu.net>
To: Sid Boyce <sboyce@blueyonder.co.uk>
Cc: linux-kernel@vger.kernel.org, Adrian Bunk <bunk@fs.tum.de>,
Andrew Morton <akpm@osdl.org>
Subject: Re: 2.6.2-rc1-mm2 kernel oops
Date: Sun, 25 Jan 2004 17:14:57 -0600 [thread overview]
Message-ID: <200401251714.57799.eric@cisu.net> (raw)
In-Reply-To: <4014283D.9040207@blueyonder.co.uk>
On Sunday 25 January 2004 14:34, Sid Boyce wrote:
> John Stoffel wrote:
> > Sid> Andrew Morton wrote:
> >
> > Sid> Sid Boyce <sboyce@xxxxxxxxxxxxxxxx> wrote:
> >>>>I get this on bootup, Athlon XP2200+
> >>>>=====================================
> >>>>Linux version 2.6.2-rc1-mm2 (root@barrabas) (gcc version 3.3.1 (SuSE
> >>>>...
> >>>>EIP is at test_wp_bit+0x36/0x90
> >>>
> >>>oh crap, why does this thing keep breaking? Please send your .config
> >>>over,
> >>>thanks.
> >
> > Sid> Linus aslso asked if 2.6.2-rc1 work -- I shall build it
> > Sid> shortly. I also get the same error with 2.6.2-rc1-mm3.
> >
> > It doesn't work for me here, I started with 2.6.2-rc1 and moved up
> > through mm1 and mm3, all either hind on boot (after the uncompressing
> > message) or crashed with the test_wp_bit Oops that seems to be going
> > around.
> >
> > 2.6.1-mm4 is the last stable version that works for me.
> >
> > John
> > John Stoffel - Senior Unix Systems Administrator - Lucent Technologies
> > stoffel@lucent.com - http://www.lucent.com - 978-952-7548
>
> See my previous post, I just commented out the line that Adrian Bunk
> asked me to remove and it's now up and running.
> Regards
> Sid.
I am now having this problem. See the thread "Kernels > 2.6.1-mm3 do not
boot." I had a kernel that would hang after uncompressing. Seems that gcc 3.3
generates bad code w/ -funit-at-a-time. Now I get the test_wp_bit oops w/
kernel version 2.6.2-rc2-mm2.
Since I have already commented out the line.. and it led to this oops, what
the heck is the real problem here?
Seems alot of other SMP systems are breaking with this too.
2x AMD 2000MP SMP system
1GB Highmem system
eric:/home/bot403 # 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
-------------------------
next prev parent reply other threads:[~2004-01-25 23:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-25 14:20 2.6.2-rc1-mm2 kernel oops Sid Boyce
2004-01-25 20:11 ` John Stoffel
2004-01-25 20:34 ` Sid Boyce
2004-01-25 23:14 ` Eric [this message]
2004-01-25 23:25 ` Andrew Morton
2004-01-26 0:04 ` Andrew Morton
2004-01-26 6:33 ` Eric
-- strict thread matches above, loose matches on Subject: below --
2004-01-25 20:21 Sid Boyce
2004-01-25 15:14 Sid Boyce
2004-01-25 18:08 ` Adrian Bunk
2004-01-23 23:15 Sid Boyce
2004-01-24 5:12 ` Andrew Morton
2004-01-24 6:26 ` Linus Torvalds
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=200401251714.57799.eric@cisu.net \
--to=eric@cisu.net \
--cc=akpm@osdl.org \
--cc=bunk@fs.tum.de \
--cc=linux-kernel@vger.kernel.org \
--cc=sboyce@blueyonder.co.uk \
/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