From: Peter Lieverdink <cafuego@cafuego.net>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Valdis.Kletnieks@vt.edu, linux-kernel@vger.kernel.org
Subject: Re: loopback device + crypto = crash on 2.6.0-test7 ?
Date: Tue, 11 Nov 2003 20:43:49 +1100 [thread overview]
Message-ID: <6.0.0.22.2.20031111202757.01af5f50@caffeine.cc.com.au> (raw)
In-Reply-To: <200311110250.hAB2orA8004592@turing-police.cc.vt.edu>
>On Tue, 11 Nov 2003 10:27:16 +1100, Peter Lieverdink
><linux@cafuego.net> said:
>
> > I agree that something is very broken, though. Mind you, I can only
> > replicate this problem on one of my machines - the other one I've tried it
> > on seems to work fine. Odder still, when I compile a kernel on the machine
> > which is fine and ruin said kernel on the machine which is not fine, I
> > don't experience the crash.
>
>At 11:15 11/11/2003, you wrote:
>That _really_ sounds like your "broken machine" is nothing more than a
>broken compiler (or possibly binutils, but compilers tend to be more
>fragile by far, so it's more likely the compiler).
>
>What compiler versions do you have installed on the broken vs good
>machines?
>
>At 13:50 11/11/2003, you wrote:
>Could we see a 'gcc -V' from *both* machines, please? (and an 'as -v'
>and 'ld -v' as well, just to be thorough?)
They're the same. Both boxes use Debian Sid with gcc-3.3.2. I made sure
they were both running the same versions of gcc/binutils when I tested it.
When I use gcc-2.95.4 (gcc version 2.95.4 20011002 Debian prerelease) on
the "broken" machine I get a crash at the same point, but with different
output. (not captured, due to got annoyed and gave up) I can probably spend
an hour or so recompiling and capturing said crash if you want me to.
As for software versions (kahlua is "bad", shiraz is "good")
root@kahlua:~$ gcc -v
Reading specs from /usr/lib/gcc-lib/i486-linux/3.3.2/specs
Configured with: ../src/configure -v
--enable-languages=c,c++,java,f77,pascal,objc,ada,treelang --prefix=/usr
--mandir=/usr/share/man --infodir=/usr/share/info
--with-gxx-include-dir=/usr/include/c++/3.3 --enable-shared
--with-system-zlib --enable-nls --without-included-gettext
--enable-__cxa_atexit --enable-clocale=gnu --enable-debug
--enable-java-gc=boehm --enable-java-awt=xlib --enable-objc-gc i486-linux
Thread model: posix
gcc version 3.3.2 (Debian)
root@kahlua:~$ as -v
GNU assembler version 2.14.90.0.7 (i386-linux) using BFD version
2.14.90.0.7 20031029 Debian GNU/Linux
root@kahlua:~$ ld -v
GNU ld version 2.14.90.0.7 20031029 Debian GNU/Linux
root@shiraz:~$ gcc -v
Reading specs from /usr/lib/gcc-lib/i486-linux/3.3.2/specs
Configured with: ../src/configure -v
--enable-languages=c,c++,java,f77,pascal,objc,ada,treelang --prefix=/usr
--mandir=/usr/share/man --infodir=/usr/share/info
--with-gxx-include-dir=/usr/include/c++/3.3 --enable-shared
--with-system-zlib --enable-nls --without-included-gettext
--enable-__cxa_atexit --enable-clocale=gnu --enable-debug
--enable-java-gc=boehm --enable-java-awt=xlib --enable-objc-gc i486-linux
Thread model: posix
gcc version 3.3.2 (Debian)
root@shiraz:~$ as -v
GNU assembler version 2.14.90.0.7 (i386-linux) using BFD version
2.14.90.0.7 20031029 Debian GNU/Linux
root@shiraz:~$ ld -v
GNU ld version 2.14.90.0.7 20031029 Debian GNU/Linux
As you see, versions are identical on both machines - this is what had me
baffled. Every single other thing works fine on the "bad" machine, so I
tend to not suspect a hardware problem.
- Peter.
next prev parent reply other threads:[~2003-11-11 9:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-29 7:09 Soeren Sonnenburg
2003-11-07 14:01 ` Bill Davidsen
2003-11-09 13:10 ` Florian Weimer
2003-11-09 12:23 ` Soeren Sonnenburg
2003-11-10 22:41 ` bill davidsen
2003-11-10 23:27 ` Peter Lieverdink
2003-11-10 23:46 ` bill davidsen
2003-11-11 0:15 ` Linus Torvalds
2003-11-11 8:54 ` Florian Weimer
2003-11-11 2:50 ` Valdis.Kletnieks
2003-11-11 9:43 ` Peter Lieverdink [this message]
2003-11-11 16:49 ` Linus Torvalds
2003-11-16 8:46 ` Peter Lieverdink
2004-01-06 10:36 ` Peter Lieverdink
2004-01-06 10:53 ` Matthias Hentges
2003-11-15 13:13 Jindrich Makovicka
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=6.0.0.22.2.20031111202757.01af5f50@caffeine.cc.com.au \
--to=cafuego@cafuego.net \
--cc=Valdis.Kletnieks@vt.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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
all inboxes | Powered by JetHome®