From: Paul Jackson <pj@sgi.com>
To: Jens Axboe <jens.axboe@oracle.com>
Cc: akpm@linux-foundation.org, willy@debian.org,
fujita.tomonori@lab.ntt.co.jp, anil.s.keshavamurthy@intel.com,
vs@namesys.com, edward@namesys.com, linux-kernel@vger.kernel.org
Subject: Re: git-block patches broken on 2.6.23-mm1 ia64 SN
Date: Sat, 13 Oct 2007 00:36:24 -0700 [thread overview]
Message-ID: <20071013003624.c11358a4.pj@sgi.com> (raw)
In-Reply-To: <20071013072504.GD969@kernel.dk>
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@sgi.com> 1.925.600.0401
next prev parent reply other threads:[~2007-10-13 7:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-13 7:13 git-block patches broken on 2.6.23-mm1 ia64 SN Paul Jackson
2007-10-13 7:18 ` Jens Axboe
2007-10-13 7:20 ` Paul Jackson
2007-10-13 7:22 ` Andrew Morton
2007-10-13 7:25 ` Jens Axboe
2007-10-13 7:36 ` Paul Jackson [this message]
2007-10-13 7:57 ` Paul Jackson
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=20071013003624.c11358a4.pj@sgi.com \
--to=pj@sgi.com \
--cc=akpm@linux-foundation.org \
--cc=anil.s.keshavamurthy@intel.com \
--cc=edward@namesys.com \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vs@namesys.com \
--cc=willy@debian.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