From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: IA64 test report: .6.4-rc1-mm2/Lion 2004-3-3: 10/10 pass
Date: Wed, 03 Mar 2004 16:34:59 +0000 [thread overview]
Message-ID: <200403030934.59343.bjorn.helgaas@hp.com> (raw)
In-Reply-To: <3ACA40606221794F80A5670F0AF15F8401720DBF@PDSMSX403.ccr.corp.intel.com>
Is this the same box as the 2.6.4-rc1 test? I guess not -- the
"Lion 2.6.4-rc1" test claims this:
> ACPI: XSDT (v001 INTEL SR870BN4 0x01072002 MSFT 0x00010013) @ 0x000000003ff83090
Which looks like an 870-based box (Tiger, maybe)?
This one ("Lion 2.6.4-mm2") looks 460-based:
> ACPI: XSDT (v001 INTEL SR460AC 0x00000003 MSFT 0x0100000a) @ 0x000000005fe96658
> 4 CPUs available, 8 CPUs total
So 4 of the 8 CPUs are disabled. Is that what you expect?
> ACPI: LSAPIC (acpi_id[0x01] lsapic_id[0x01] lsapic_eid[0x00] enabled)
> CPU 1 (0x0100) enabled
> CPU 1: base freq\x133.333MHz, ITC ratio\x12/2, ITC freq€0.003MHz+/--1ppm
> Calibrating delay loop... 797.80 BogoMIPS
> CPU 1: synchronized ITC with CPU 0 (last diff 0 cycles, maxerr 551 cycles)
Hmm... We still print 5 lines per CPU (tons better than it used to
be), but we have no indication of what processor model it is. That
seems more useful than some of this stuff.
> pci_irq-0302 [03] acpi_pci_irq_derive : Unable to derive IRQ for device 0000:00:03.3
> ACPI: No IRQ known for interrupt pin B of device 0000:00:03.3
Ah, here's our friend the SMBus device.
No USB funnies in this boot. I guess that's probably due to
the fact that this really isn't the same box as the 2.6.4-rc1
boot.
next prev parent reply other threads:[~2004-03-03 16:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-03 11:31 IA64 test report: .6.4-rc1-mm2/Lion 2004-3-3: 10/10 pass Yu, Luming
2004-03-03 16:34 ` Bjorn Helgaas [this message]
2004-03-08 2:08 ` Yu, Luming
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=200403030934.59343.bjorn.helgaas@hp.com \
--to=bjorn.helgaas@hp.com \
--cc=linux-ia64@vger.kernel.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