From: Thomas Renninger <trenn@suse.de>
To: "Moore, Robert" <robert.moore@intel.com>
Cc: "Luck, Tony" <tony.luck@intel.com>,
linux-acpi@vger.kernel.org, linux-ia64@vger.kernel.org
Subject: Re: some new unaligned access while booting ia64 (HP rx2620)
Date: Fri, 10 Feb 2006 03:07:43 +0100 [thread overview]
Message-ID: <43EBF56F.7090507@suse.de> (raw)
In-Reply-To: <971FCB6690CD0E4898387DBF7552B90E044F0914@orsmsx403.amr.corp.intel.com>
Moore, Robert wrote:
> The next thing that would be useful is to know what method(s) are
> executing when the message pops out.
>
>
>> -----Original Message-----
>> From: Luck, Tony
>> Sent: Thursday, February 09, 2006 1:16 PM
>> To: Moore, Robert; 'linux-acpi@vger.kernel.org'
>> Cc: 'linux-ia64@vger.kernel.org'
>> Subject: RE: some new unaligned access while booting ia64 (HP rx2620)
>>
>> But I goofed and muddled up my two problems. I tried
>> booting on my zx1 ... which was broken altogether by
>> recent acpi changes.
>>
>> Getting back to the rx2620 ... deleting those lines makes
>> no difference. I still boot ok, I still see the unaligned
>> access messages.
>>
>> /proc/acpi/dsdt for that system attached.
>>
>> -Tony
I also got kernel missalignment errors..., unfortunately also
a lot of slab debugger errors until the machine rebooted, so
I didn't care too much about the missalignments, but these
could have the same cause?
I now could nail the mem
corruptions down to ACPICA-20051021 by binary search.
It's late, maybe I got something wrong, but I am quite sure the
culprit lies there.
The patch is huge, but maybe it's just one of the other pragmas or
whatever related?:
grep pragma ../ACPICA_20051021.patch
+#pragma pack(1)
+#pragma pack()
+#pragma pack(1)
+#pragma pack()
Thomas
next prev parent reply other threads:[~2006-02-10 2:07 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-09 23:43 some new unaligned access while booting ia64 (HP rx2620) Moore, Robert
2006-02-10 2:07 ` Thomas Renninger [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-03-15 17:14 Moore, Robert
2006-03-15 15:47 Moore, Robert
2006-03-15 16:49 ` Bjorn Helgaas
2006-02-11 0:39 Luck, Tony
2006-02-11 12:21 ` Robin Holt
2006-02-10 23:58 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:25 Luck, Tony
2006-02-10 23:15 Moore, Robert
2006-02-10 23:07 Moore, Robert
2006-02-10 22:58 Luck, Tony
2006-02-11 21:25 ` Bjorn Helgaas
2006-02-10 21:56 Moore, Robert
2006-02-10 21:54 Luck, Tony
2006-02-10 21:19 Moore, Robert
2006-02-10 21:15 Luck, Tony
2006-02-10 20:11 Moore, Robert
2006-02-09 21:15 Luck, Tony
2006-02-09 21:04 Luck, Tony
2006-02-09 20:55 Moore, Robert
2006-02-09 20:44 Luck, Tony
2006-02-09 16:56 Moore, Robert
2006-02-02 22:28 Moore, Robert
2006-02-02 19:46 Luck, Tony
2006-03-14 23:59 ` 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=43EBF56F.7090507@suse.de \
--to=trenn@suse.de \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-ia64@vger.kernel.org \
--cc=robert.moore@intel.com \
--cc=tony.luck@intel.com \
/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