From: "Yu, Luming" <luming.yu@intel.com>
To: linux-ia64@vger.kernel.org
Subject: Latest 2.6 IA64 Baseline (Mosberger) testing report (Tiger)
Date: Wed, 03 Dec 2003 14:35:25 +0000 [thread overview]
Message-ID: <marc-linux-ia64-107046218607600@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106863716316469@msgid-missing>
[-- Attachment #1: Type: text/plain, Size: 2663 bytes --]
ACPI Test Report for 2.6 ia64 kernel
=========================
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.5 on 12/3 (Shanghai time)
2.bk pull from http://linux-acpi.bkbits.net/linux-acpi-test-2.6.0 on 12/3 (Shanghai time)
3. patch from http://bugzilla.kernel.org/show_bug.cgi?id=1634 to fix compile-time bug.
Resolved 1 conflict by hand.(Take change from linux-ia64-2.5)
ACPI Features Tested: (prioritized).
--------------------
1. Boot tested ok
2. serial console tested ok
3. ATI (run X window system) tested ok
4. PS/2 mouse 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
29: 0 0 0 0 LSAPIC cmc_poll
30: 0 0 0 0 IO-SAPIC-level cpe_hndlr
31: 0 0 0 0 LSAPIC cmc_hndlr
34: 1 0 63 0 IO-SAPIC-edge ide0
39: 0 0 4 0 IO-SAPIC-level acpi
45: 0 1 94 0 IO-SAPIC-edge serial
48: 0 0 0 0 IO-SAPIC-level ehci_hcd
49: 1 24 1812 0 IO-SAPIC-level uhci_hcd
50: 0 0 40 0 IO-SAPIC-level uhci_hcd
51: 0 2 399 0 IO-SAPIC-level eth0
56: 7 128 3828 0 IO-SAPIC-level ioc0
57: 0 0 42 0 IO-SAPIC-level ioc1
232: 0 0 0 0 LSAPIC mca_rdzv
238: 0 0 0 0 LSAPIC perfmon
239: 203826 198715 198222 197807 LSAPIC timer
240: 0 0 0 0 LSAPIC mca_wkup
254: 34 94 87 91 LSAPIC IPI
NMI: 0 0 0 0
ERR: 0
Problems:
Please refer dmesg attached .
[Dmesg, /proc/interrupts, lspci -v , .config are attached below]
<<2.6.ZIP>>
Thanks,
Luming
[-- Attachment #2: 2.6.ZIP --]
[-- Type: application/x-zip-compressed, Size: 12898 bytes --]
next prev parent reply other threads:[~2003-12-03 14:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-12 11:37 Latest 2.6 IA64 Baseline (Mosberger) testing report (Boot hang) Yu, Luming
2003-11-13 3:14 ` Matt Chapman
2003-11-13 12:32 ` Yu, Luming
2003-11-19 12:42 ` Yu, Luming
2003-11-19 12:46 ` Latest 2.6 IA64 Baseline (Mosberger) testing report Yu, Luming
2003-11-26 14:08 ` Yu, Luming
2003-12-03 13:17 ` Latest 2.6 IA64 Baseline (Mosberger) testing report (Lion) Yu, Luming
2003-12-03 14:35 ` Yu, Luming [this message]
2003-12-10 9:55 ` Yu, Luming
2003-12-10 10:06 ` Latest 2.6 IA64 Baseline (Mosberger) testing report (Tiger) 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=marc-linux-ia64-107046218607600@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