From: nomura@hpc.bs1.fc.nec.co.jp
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] where to set rr for uncached region
Date: Thu, 22 Nov 2001 11:36:47 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590698805542@msgid-missing> (raw)
Hello,
Current code sets rr for region 6 (kernel uncached region) in ia64_mmu_init().
However, thinking about application processors, there are some printk()s
before ia64_mmu_init() to be called.
Since printk() ends up in vt_console_print() and store to uncached region
will happen, I think this cause a problem.
In reality, MCAs always happen on our machine after AP prints
"CPU 1: mapping PAL code ..." to serial console. The processor log
shows that MCA happend in vt_console_print() on CPU1.
I can work around the problem by applying this patch.
I've noticed the problem when EARLY_PRINTK was deleted from config option.
So I'm curious about whether anyone has not experienced same kind of problem.
diff -u -r1.1.1.8.6.1 head.S
--- arch/ia64/kernel/head.S 2001/10/04 10:31:46 1.1.1.8.6.1
+++ arch/ia64/kernel/head.S 2001/10/05 02:18:17
@@ -111,7 +111,6 @@
mov ar.fpsr=r2
;;
-#ifdef CONFIG_IA64_EARLY_PRINTK
mov r3=(6<<8) | (KERNEL_PG_SHIFT<<2)
movl r2=6<<61
;;
@@ -119,7 +118,6 @@
;;
srlz.i
;;
-#endif
#define isAP p2 // are we an Application Processor?
#define isBP p3 // are we the Bootstrap Processor?
Best regards.
--
NOMURA, Jun'ichi <j-nomura@ce.jp.nec.com, nomura@hpc.bs1.fc.nec.co.jp>
HPC Operating System Group, 1st Computers Software Division,
Computers Software Operations Unit, NEC Solutions.
next reply other threads:[~2001-11-22 11:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-22 11:36 nomura [this message]
2001-11-26 23:41 ` [Linux-ia64] where to set rr for uncached region David Mosberger
2001-11-29 7:34 ` nomura
2001-11-30 5:46 ` David Mosberger
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-105590698805542@msgid-missing \
--to=nomura@hpc.bs1.fc.nec.co.jp \
--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