Re: loopback device + crypto = crash on 2.6.0-test7 ?

From: Peter Lieverdink (cafuego_at_cafuego.net)
Date: 11/16/03

  • Next message: Russell King: "Bootmem broke ARM" 
    Date:	Sun, 16 Nov 2003 19:46:08 +1100
To: Linus Torvalds <torvalds@osdl.org>

    At 03:49 12/11/2003, you wrote:

    >On Tue, 11 Nov 2003, Peter Lieverdink wrote:
    > > >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.
    >
    >[ Taa-daa-taa-daa.. Theme from "The Twilight Zone" ]
    >
    >And yet the kenrel works when built on one machine?
    >
    >I'd love to see what the differences are. If the .config etc are all 100%
    >the same, I'd like to see what "diff" reports on the generated vmlinux
    >files (well, to be honest, I'd need either both files on some web-site, or
    >you to actually run diff and find _where_ the differences are).
    >
    > Linus

    Well, due to [insert long explanation] the -test8 kernel wasn't available.
    The "good" machine built a -test9, which crashed as well. *sigh* Mind you,
    there are differences between the kernel _it_ builds and the one built by
    the "bad" machine. I've uploaded a alien -t'd debian kernel packages to the
    fastest web space I have for you to have a peek, if you have some time.
    (what with lawsuits and whatnot ;-)

    2.6.0-test9 built on the "good" box:
    http://monolith.dnsalias.org/~cafuego/kernel-image-2.6.0-test9-kahlua.1.tgz

    2.6.0-test9 built on the "bad" box:
    http://monolith.dnsalias.org/~cafuego/kernel-image-2.6.0-test9-kahlua.2.tgz

    More importantly though, the post from Jindrich:

    At 00:13 16/11/2003, you wrote:
    >I can confirm, having similar problem. I am using Debian Sid &
    >2.6.0-test9, with 4Gig highmem support (1.5G physical RAM). When reading
    >from cryptoloop (dd if=/dev/loop0 of=testoutput), it seems to produce only
    >noise. Each run of dd produces completely different heap of garbage. When
    >I disable highmem, getting rid of about 512 Megs, cryptoloop seems to work
    >as expected - I can do losetup & mke2fs & mount & read/write files &
    >unmount & losetup -d & again.. ad nauseam.
    >
    >Jindrich Makovicka

    When I compiled on the "bad" machine with disabled HIGHMEM, the resultant
    kernel has NO problems with cryptoloop. I can make a cryptoloop fs, mount,
    copy, unmount, remount etc. That kernel is at:
    http://monolith.dnsalias.org/~cafuego/kernel-image-2.6.0-test9-kahlua.3.tgz

    So I guess HIGHMEM breaks cryptoloop somehow.

    - Peter.

    -
    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/

  • Next message: Russell King: "Bootmem broke ARM"

    Relevant Pages