From: David Mosberger <davidm@hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Panic in linuxrc (2.4.7)
Date: Thu, 02 Aug 2001 01:13:14 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590693005988@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590693005983@msgid-missing>
>>>>> On Wed, 1 Aug 2001 16:15:43 -0700, David Mosberger <davidm@hpl.hp.com> said:
David> Do you have CONFIG_PERFMON enabled? If not, try turning it
David> on. We are investigating the problem. It looks to be a
David> Heisenbug: the problem gets triggered depending on what the
David> exact code layout is. Adding or removing a single bundle in
David> the right place seems to make the difference...
OK, this turns out to be due to an assembler bug: the assembler fails
to put a stop bit in front of an "alloc" instruction if the "alloc" is
preceded by a .align directive and the directive inserts one or more
"nop" bundles. ;-(
This bug was difficult to track down because it got triggered while
psr.ic was cleared, which means that the IP reported in the tombstone
is all wrong and there is no easy way to find out at which address the
real fault occurred. Well, at least the workaround is easy:
--- arch/ia64/kernel/entry.S-orig Wed Aug 1 12:48:26 2001
+++ arch/ia64/kernel/entry.S Wed Aug 1 18:05:31 2001
@@ -687,7 +687,7 @@
shladd in0=loc1,3,r17
mov in1=0
;;
- .align 32
+// .align 32
rse_clear_invalid:
// cycle 0
{ .mii
Please try again with this patch applied.
--david
next prev parent reply other threads:[~2001-08-02 1:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-01 23:05 [Linux-ia64] Panic in linuxrc (2.4.7) richard offer
2001-08-01 23:15 ` David Mosberger
2001-08-01 23:16 ` Broadfoot, Ken P
2001-08-01 23:22 ` richard offer
2001-08-01 23:27 ` Van Maren, Kevin
2001-08-02 1:13 ` David Mosberger [this message]
2001-08-02 7:12 ` Van Maren, Kevin
2001-08-02 19:58 ` richard offer
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-105590693005988@msgid-missing \
--to=davidm@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