From: Andrew Morton <akpm@osdl.org>
To: Khalid Aziz <khalid.aziz@hp.com>
Cc: khalid_aziz@hp.com, linux-kernel@vger.kernel.org,
linux-ia64@vger.kernel.org, linux-acpi@intel.com
Subject: Re: 2.6.13-rc3-mm3
Date: Sat, 30 Jul 2005 18:02:49 +0000 [thread overview]
Message-ID: <20050730110249.481ebb2d.akpm@osdl.org> (raw)
In-Reply-To: <1122737595.3133.7.camel@minuet.fc.hp.com>
Khalid Aziz <khalid.aziz@hp.com> wrote:
>
> On Fri, 2005-07-29 at 16:17 -0700, Andrew Morton wrote:
> > Khalid Aziz <khalid_aziz@hp.com> wrote:
> > >
> > > Serial console is broken on ia64 on an HP rx2600 machine on
> > > 2.6.13-rc3-mm3. When kernel is booted up with "console=ttyS,...", no
> > > output ever appears on the console and system is hung. So I booted the
> > > kernel with "console=uart,mmio,0xff5e0000" to enable early console and
> > > here is how far the kernel got before hanging:
> >
> > (cc the ia64 and acpi lists)
> >
> > OK, thanks. There have been a few serial driver changes recently, but
> > there's also a tremendous ACPI patch in -mm. I'm wondering about those
> > ACPI error messages:
> >
> > > -------
> > > Linux version 2.6.13-rc3-mm3 (root@mars) (gcc version 3.3.5 (Debian 1:3.3.5-12)) #4 SMP Fri Jul 29 16:30:41 MDT 2005
> > > EFI v1.10 by HP: SALsystab=0x3fb38000 ACPI 2.0=0x3fb2e000 SMBIOS=0x3fb3a000 HCDP=0x3fb2c000
> > > booting generic kernel on platform hpzx1
> > > PCDP: v0 at 0x3fb2c000
> > > Explicit "console="; ignoring PCDP
> > ..............
> > > NET: Registered protocol family 16
> > > ACPI: bus type pci registered
> > > ACPI: Subsystem revision 20050708
> > > ACPI-0509: *** Error: Method execution failed [\PARS.GFIT] (Node e0000002ffff8a00), AE_BAD_PARAMETER
> > > ACPI-0509: *** Error: Method execution failed [\_SB_.SBA0._INI] (Node e0000002ffffa780), AE_BAD_PARAMETER
> > > ACPI: Interpreter enabled
> > > ACPI: Using IOSAPIC for interrupt routing
> >
> > Does the above happen on 2.6.13-rc3 or 2.6.13-rc4?
>
> No, I do not see this on 2.6.13-rc3. It does seem ACPI is busted on
> 2.6.13-rc3-mm3 which is leading to kernel not being able to scan PCI bus
> and set up IRQ routing.
>
OK, thanks. Could I suggest that you raise a bug against ACPI 20050708 at
bugzilla.kernel.org containing the info we've generated thus far?
And thanks for testing -mm: we really don't want to permit this to leak
into mainline...
next prev parent reply other threads:[~2005-07-30 18:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050728025840.0596b9cb.akpm@osdl.org>
[not found] ` <1122678354.20867.48.camel@lyra.fc.hp.com>
2005-07-29 23:17 ` 2.6.13-rc3-mm3 Andrew Morton
2005-07-30 15:33 ` 2.6.13-rc3-mm3 Khalid Aziz
2005-07-30 18:02 ` Andrew Morton [this message]
2005-08-01 15:36 ` 2.6.13-rc3-mm3 Bjorn Helgaas
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=20050730110249.481ebb2d.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=khalid.aziz@hp.com \
--cc=khalid_aziz@hp.com \
--cc=linux-acpi@intel.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@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