public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: RE: 2.5.75 out
Date: Fri, 11 Jul 2003 18:30:31 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105795124111262@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105788013113852@msgid-missing>

Luming,

Do you know what the status is in getting the ia64 ACPI changes folded
into 2.5.xx?

Thanks,

	--david

>>>>> On Fri, 11 Jul 2003 10:58:15 -0700, "Chen, Kenneth W" <kenneth.w.chen@intel.com> said:

  Ken> Ditto for tiger-4 machine.  Doesn't boot because interrupts are
  Ken> all messed up.

  Ken> - Ken

  Ken> -----Original Message----- From: Peter Chubb
  Ken> [mailto:peter@chubb.wattle.id.au] Sent: Thursday, July 10, 2003
  Ken> 7:54 PM To: davidm@hpl.hp.com Cc: linux-ia64@vger.kernel.org
  Ken> Subject: RE: 2.5.75 out

  DavidM> There is good and bad news: the bad news is that 2.5.75
  DavidM> doesn't work out-of-the-box on ia64.  The good news it
  DavidM> _does_ compile.
  Ken> The
  DavidM> thing that keeps it from working are a few (late) per-CPU
  Ken> related
  DavidM> changes.

  Ken> There still appears to be an ACPI issue.

  Ken> On bootup for a single processor I2000 (so the per-cpu problem
  Ken> doesn't arise), the interrupt routing isn't set up properly, so
  Ken> nothing that needs an interrupt work properly.

  >> From the log:
  Ken> ...  ACPI Namespace successfully loaded at root
  Ken> a00000010067b8b0 evxfevnt-0093 [04] acpi_enable : Transition to
  Ken> ACPI mode successful evgpeblk-0748 [06] ev_create_gpe_block :
  Ken> GPE 00 to 15 [_GPE] 2 regs at 0000000000000A0C on int 9
  Ken> evgpeblk-0748 [06] ev_create_gpe_block : GPE 16 to 31 [_GPE] 2
  Ken> regs at 0000000000000A16 on int 9 ACPI: SCI (IRQ-1) allocation
  Ken> failed evevent-0133: *** Error: Unable to install System
  Ken> Control Interrupt Handler, AE_NOT_ACQUIRED ACPI: Unable to
  Ken> start the ACPI Interpreter evxfevnt-0135 [06] acpi_disable :
  Ken> Could not exit ACPI mode to legacy mode evmisc-0563 [05]
  Ken> ev_terminate : acpi_disable failed utalloc-0986 [05]
  Ken> ut_dump_allocations : No outstanding allocations.  Trying to
  Ken> free free IRQ0 SCSI subsystem initialized
  Ken> drivers/usb/core/usb.c: registered new driver usbfs
  Ken> drivers/usb/core/usb.c: registered new driver hub ACPI: ACPI
  Ken> tables contain no PCI IRQ routing entries PCI: Invalid ACPI-PCI
  Ken> IRQ routing table ...  - To unsubscribe from this list: send
  Ken> the line "unsubscribe linux-ia64" in the body of a message to
  Ken> majordomo@vger.kernel.org More majordomo info at
  Ken> http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2003-07-11 18:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-10 23:34 2.5.75 out David Mosberger
2003-07-10 23:45 ` Luck, Tony
2003-07-10 23:54 ` David Mosberger
2003-07-11  0:05 ` Luck, Tony
2003-07-11  2:53 ` Peter Chubb
2003-07-11  7:30 ` Andrew Morton
2003-07-11 17:58 ` Chen, Kenneth W
2003-07-11 18:30 ` David Mosberger [this message]
2003-07-16  3:16 ` Yu, Luming
2003-07-16  4:29 ` David Mosberger
2003-07-16 11:13 ` Matthew Wilcox

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-105795124111262@msgid-missing \
    --to=davidm@napali.hpl.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