All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Jackson <pj@sgi.com>
To: Jens Axboe <jens.axboe@oracle.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Matthew Wilcox <willy@debian.org>,
	FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>,
	Anil S Keshavamurthy <anil.s.keshavamurthy@intel.com>,
	Vladimir Saveliev <vs@namesys.com>,
	Edward Shishkin <edward@namesys.com>,
	linux-kernel <linux-kernel@vger.kernel.org>
Date: Sat, 13 Oct 2007 00:10:27 -0700	[thread overview]
Message-ID: <20071013001027.535cc294.pj@sgi.com> (raw)

The git-block patches in 2.6.23-mm1 freeze my ia64 SN Altix hard on boot.
Not good (tm).

Something broke between the git-block patch of Sept 26 in 2.6.23-rc8-mm2
and the git-block patches of Oct 10-11 in 2.6.23-mm1 on my ia64 SN Altix
system using sn2_defconfig.

Bisecting 2.6.23-mm1 narrows the problem down to the git-block patches:

    git-block.patch
    git-block-fixup-1.patch
    git-block-fixup.patch
    git-block-fixup-fix.patch
    git-block-borkages.patch
    git-block-s390-fix.patch

I can boot 2.6.23-rc8-mm2 fine, but I freeze early in boot
on 2.6.23-mm1, after the following prints on the console:

    McKinley Errata 9 workaround not needed; disabling it
    SLUB: Genslabs=26, HWalign=128, Order=0-2, MinObjects=8, CPUs=8, Nodes=1024
    Dentry cache hash table entries: 1048576 (order: 9, 8388608 bytes)
    Inode-cache hash table entries: 524288 (order: 8, 4194304 bytes)
    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).

The next output that I -would- have expected, based on successful boots
without these patches, but never get, is:

    net_namespace: 120 bytes
    DMI not present or invalid.
    xor: measuring software checksum speed
       ia64      :  2692.000 MB/sec
    xor: using function: ia64 (2692.000 MB/sec)
    NET: Registered protocol family 16
    ACPI  DSDT OEM Rev 0x20101

-- 
                  I won't rest till it's the best ...
                  Programmer, Linux Scalability
                  Paul Jackson <pj@sgi.com> 1.925.600.0401

                 reply	other threads:[~2007-10-13  7:10 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20071013001027.535cc294.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.