lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20071013003624.c11358a4.pj@sgi.com>
Date:	Sat, 13 Oct 2007 00:36:24 -0700
From:	Paul Jackson <pj@....com>
To:	Jens Axboe <jens.axboe@...cle.com>
Cc:	akpm@...ux-foundation.org, willy@...ian.org,
	fujita.tomonori@....ntt.co.jp, anil.s.keshavamurthy@...el.com,
	vs@...esys.com, edward@...esys.com, linux-kernel@...r.kernel.org
Subject: Re: git-block patches broken on 2.6.23-mm1 ia64 SN

Booting with initcall_debug doesn't change the output at all.  If I
boot a working kernel with initcall_debug, the added output starts
showing up right after the point that my broken kernel is freezing.

    Mount-cache hash table entries: 1024
    ACPI: Core revision 20070126
    Boot processor id 0x0/0x0
    Brought up 8 CPUs
    Total of 8 processors activated (15564.80 BogoMIPS).
<< Broken kernel freezes here >>
<< Good kernel continues with ...>>
    Calling initcall 0xa0000001009d6310: net_ns_init+0x0/0x3e0()
    net_namespace: 120 bytes
    initcall 0xa0000001009d6310: net_ns_init+0x0/0x3e0() returned 0.
    initcall 0xa0000001009d6310 ran for 0 msecs: net_ns_init+0x0/0x3e0()
    Calling initcall 0xa0000001009d6630: run_dmi_scan+0x0/0x40()

-- 
                  I won't rest till it's the best ...
                  Programmer, Linux Scalability
                  Paul Jackson <pj@....com> 1.925.600.0401
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists