From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: linux-acpi@vger.kernel.org, linux-ia64@vger.kernel.org, "Moore,
Robert" <robert.moore@intel.com>,
Thomas Renninger <trenn@suse.de>
Subject: Re: some new unaligned access while booting ia64 (HP rx2620)
Date: Tue, 14 Mar 2006 16:59:49 -0700 [thread overview]
Message-ID: <200603141659.49535.bjorn.helgaas@hp.com> (raw)
In-Reply-To: <200602021946.k12Jk446028921@agluck-lia64.sc.intel.com>
On Thursday 02 February 2006 12:46, Luck, Tony wrote:
> Booting a snapshot of Linus' tree this morning I saw a few (new?)
> kernel unaligned access warnings:
>
> ACPI: Subsystem revision 20060127
> ACPI: Interpreter enabled
> ACPI: Using IOSAPIC for interrupt routing
> ACPI: PCI Root Bridge [PCI0] (0000:00)
> kernel unaligned access to 0xe00000407ec5a204, ip=0xa0000001003af8c0
> kernel unaligned access to 0xe00000407ec5a23c, ip=0xa0000001003af8c0
> kernel unaligned access to 0xe00000407ec5a28c, ip=0xa0000001003af8c0
> kernel unaligned access to 0xe00000407ec5a1fc, ip=0xa0000001003ae6c1
> kernel unaligned access to 0xe00000407ec5a204, ip=0xa0000001003ae6d1
> ACPI: PCI Interrupt Routing Table [\_SB_.SBA0.PCI0._PRT]
> ACPI: PCI Root Bridge [PCI1] (0000:20)
Did we ever resolve this? Are we just waiting for new ACPI bits
to trickle into -mm and mainline?
I'd like to see the patch for just this issue, because it affects
SLES10, and Novell might balk at a complete ACPI CA update, but
might take just the individual patch.
Bjorn
next prev parent reply other threads:[~2006-03-14 23:59 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-02 19:46 some new unaligned access while booting ia64 (HP rx2620) Luck, Tony
2006-03-14 23:59 ` Bjorn Helgaas [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-02-02 22:28 Moore, Robert
2006-02-09 16:56 Moore, Robert
2006-02-09 20:44 Luck, Tony
2006-02-09 20:55 Moore, Robert
2006-02-09 21:04 Luck, Tony
2006-02-09 21:15 Luck, Tony
2006-02-09 23:43 Moore, Robert
2006-02-10 2:07 ` Thomas Renninger
2006-02-10 20:11 Moore, Robert
2006-02-10 21:15 Luck, Tony
2006-02-10 21:19 Moore, Robert
2006-02-10 21:54 Luck, Tony
2006-02-10 21:56 Moore, Robert
2006-02-10 22:58 Luck, Tony
2006-02-11 21:25 ` Bjorn Helgaas
2006-02-10 23:07 Moore, Robert
2006-02-10 23:15 Moore, Robert
2006-02-10 23:25 Luck, Tony
2006-02-10 23:31 Moore, Robert
2006-02-13 18:51 ` Thomas Renninger
2006-02-13 22:33 ` Bjorn Helgaas
2006-02-13 22:57 ` Andreas Schwab
2006-02-14 0:22 ` Bjorn Helgaas
2006-02-10 23:58 Luck, Tony
2006-02-11 0:39 Luck, Tony
2006-02-11 12:21 ` Robin Holt
2006-03-15 15:47 Moore, Robert
2006-03-15 16:49 ` Bjorn Helgaas
2006-03-15 17:14 Moore, Robert
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=200603141659.49535.bjorn.helgaas@hp.com \
--to=bjorn.helgaas@hp.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-ia64@vger.kernel.org \
--cc=robert.moore@intel.com \
--cc=tony.luck@intel.com \
--cc=trenn@suse.de \
/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