public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: "Yu, Luming" <luming.yu@intel.com>
To: linux-ia64@vger.kernel.org
Subject: Latest 2.4 IA64 Baseline (Bjorn) testing report (Tiger)
Date: Wed, 10 Dec 2003 10:00:07 +0000	[thread overview]
Message-ID: <marc-linux-ia64-107105045020876@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106985955514249@msgid-missing>

[-- Attachment #1: Type: text/plain, Size: 2147 bytes --]

ACPI Test Report  for 2.4 ia64 kernel + latest ACPI
=========================
Hardware Configuration:
-----------------------
System Name: ACPI-Tiger
System Type: 4 way 900 Itanium2, tiger
M/B revision: N/A
Processor version: N/A
Firmware Versions: N/A
I/O configuration summary:
	MPT scsi host driver
	Seagate ST318406LC boot drive
	IDE floppy and CDROM
	Serial console
	USB mouse
	Ethernet Pro 1000

Software Configuration:
-----------------------
	1.Bk pull form http://lia64.bkbits.net/linux-ia64-2.4 on 12/10 (Shanghai time)
	2.Bk pull from http://linux-acpi.bkbits.net/linux-acpi-test-2.4.22 on 12/10 (Shanghai time)
		Nothing to pull

ACPI Features Tested: (prioritized).
--------------------
1. Boot off SCSI disk			tested ok
2. serial console				tested ok
3. USB 	keyboard			tested ok
4. ATI (run X window system)		tested ok
5. USB mouse				tested ok
6. NIC (eg. Ping or ftp)			tested ok
7. IDE (eg. r/w floppy or CDROM)	tested ok
8. SCI (eg. Press power button)		tested ok
9. Soft Power off				tested ok

           CPU0       CPU1       CPU2       CPU3
 32:          0          0          5          0   IO-SAPIC-edge  keyboard
 34:          0          0         71          1   IO-SAPIC-edge  ide0
 39:          0          0          4          0  IO-SAPIC-level  acpi
 45:          0          0       1899          0   IO-SAPIC-edge  serial
 48:          0          1         46          0  IO-SAPIC-level  usb-uhci
 49:          7         28       1450          2  IO-SAPIC-level  usb-uhci
 50:          0          0          0          0  IO-SAPIC-level  ehci_hcd
 51:          0          4        847          0  IO-SAPIC-level  eth0
 53:          5         27       4444          0  IO-SAPIC-level  ioc0
 54:          0          0         42          0  IO-SAPIC-level  ioc1
239:     308674     307900     307548     307036          LSAPIC  timer
254:      14455      14127      14779      13957          LSAPIC  IPI
NMI:          0          0          0          0
ERR:          0


[Dmesg, /proc/interrupts, lspci -v , .config are attached in 2.4.log below]
 <<2.4.ZIP>> 


[-- Attachment #2: 2.4.ZIP --]
[-- Type: application/x-zip-compressed, Size: 12547 bytes --]

      parent reply	other threads:[~2003-12-10 10:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-26 15:12 Latest 2.4 IA64 Baseline (Bjorn) testing report Yu, Luming
2003-11-26 15:14 ` Matthew Wilcox
2003-12-01 17:42 ` Bjorn Helgaas
2003-12-03 12:44 ` Latest 2.4 IA64 Baseline (Bjorn) testing report (Lion) Yu, Luming
2003-12-03 14:25 ` Latest 2.4 IA64 Baseline (Bjorn) testing report (Tiger) Yu, Luming
2003-12-04  3:59 ` Latest 2.4 IA64 Baseline (Bjorn) testing report Yu, Luming
2003-12-10  9:41 ` Latest 2.4 IA64 Baseline (Bjorn) testing report (Lion) Yu, Luming
2003-12-10  9:46 ` Yu, Luming
2003-12-10 10:00 ` Yu, Luming [this message]

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=marc-linux-ia64-107105045020876@msgid-missing \
    --to=luming.yu@intel.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