All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yu, Luming" <luming.yu@intel.com>
To: linux-ia64@vger.kernel.org
Subject: IA64 test report: 2.6.0-test11/Lion 2003-12-18: 9/9 pass
Date: Thu, 18 Dec 2003 09:14:57 +0000	[thread overview]
Message-ID: <marc-linux-ia64-107173908709395@msgid-missing> (raw)

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

ACPI Test Report  for 2.6 ia64 kernel 
=========================
Hardware Configuration:
-----------------------
System Name: ACPI-LION
System Type: 4 way 800M Itanium, Lion
M/B revision: N/A
Processor version: N/A
Firmware Versions: N/A
I/O configuration summary:
	QLogic QLA12160, Seagate ST39205LC boot drive
	IDE floppy and CDROM
	Serial console
	PS/2 keyboard and mouse
	USB mouse
	Ethernet Pro 100

Software Configuration:
	1.Bk pull form http://lia64.bkbits.net/linux-ia64-2.5 on 12/18 (Shanghai time)
	2.bk pull from http://linux-acpi.bkbits.net/linux-acpi-test-2.6.0 on 12/18 (Shanghai time)
		resolved 2 conflicts manually

ACPI Features Tested: (prioritized).
--------------------
1. Boot 				tested ok
2. PS/2 keyboard			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
 32:        886          9          2         21   IO-SAPIC-edge  i8042
 33:        396          2          0          6   IO-SAPIC-edge  ide1
 34:         12         12          0         14   IO-SAPIC-edge  ide0
 36:       2358          0          0         88   IO-SAPIC-edge  i8042
 39:          7          0          0          0  IO-SAPIC-level  acpi
 45:         15          0          0          2   IO-SAPIC-edge  serial
 54:       2910         11          0         51  IO-SAPIC-level  uhci_hcd
 55:       1329          3          0         12  IO-SAPIC-level  eth0
 61:       5530         19          1        238  IO-SAPIC-level  qla1280
232:          0          0          0          0          LSAPIC  mca_rdzv
238:          0          0          0          0          LSAPIC  perfmon
239:     693079     688461     688026     687583          LSAPIC  timer
240:          0          0          0          0          LSAPIC  mca_wkup
254:        123        155        120        184          LSAPIC  IPI
NMI:          0          0          0          0 
ERR:          0

Problem:

1.alloc 0x0-0xcf7 from PCI IO for PCI Bus 0000:00 failed .
Known issue, bjorn has idea to fix it.

2. pci_irq-0302 [03] acpi_pci_irq_derive   : Unable to derive IRQ for device 0000:00:03.3
Please refere http://bugzilla.kernel.org/show_bug.cgi?id=1534 


 <<2.6.config.ZIP>>  <<2.6.ZIP>> 


[-- Attachment #2: 2.6.config.ZIP --]
[-- Type: application/x-zip-compressed, Size: 5437 bytes --]

[-- Attachment #3: 2.6.ZIP --]
[-- Type: application/x-zip-compressed, Size: 7085 bytes --]

                 reply	other threads:[~2003-12-18  9:14 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=marc-linux-ia64-107173908709395@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 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.