From: "Mallick, Asit K" <asit.k.mallick@intel.com>
To: linux-ia64@vger.kernel.org
Subject: RE: [Linux-ia64] Kernel panic in dtlb_fault
Date: Thu, 11 Jan 2001 22:10:11 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590693005034@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590678205904@msgid-missing>
[-- Attachment #1: Type: text/plain, Size: 2323 bytes --]
Attached is a patch to fix the problem. Uros and Jenna were able to boot
with this patch. Sorry for sending the early version.
Thanks,
Asit
> -----Original Message-----
> From: Uros Prestor [mailto:uros@turbolinux.com]
> Sent: Thursday, January 11, 2001 12:13 PM
> To: davidm@hpl.hp.com
> Cc: linux-ia64@linuxia64.org
> Subject: Re: [Linux-ia64] Kernel panic in dtlb_fault
>
>
> David Mosberger wrote:
>
> > Are you sure you picked up the new kernel? Try "objdump -d" on
> > vmlinux and verify that itlb_fault ends with "b0" being restored.
>
> This is the disassembly output of itlb_fault:
> e000000000500400 <itlb_fault>:
> e000000000500400: 00 80 00 28 24 04 [MII]
> mov r16=cr20
> e000000000500406: d0 01 00 62 00 e0 mov r29=b0
> e00000000050040c: 03 00 cc 00 mov r31=pr
> e000000000500410: 05 88 00 32 24 44 [MLX]
> mov r17=cr25
> e000000000500416: 00 00 00 00 60 c0
> movl r30=0xe00000000
> 0500420;;
> e00000000050041c: 03 02 22 68
> e000000000500420: 0a 90 00 22 18 10 [MMI]
> ld8 r18=[r17];;
> e000000000500426: 00 00 00 02 00 c0 nop.m 0x0
> e00000000050042c: 00 90 00 50
> tbit.z p6,p0=r18,0
> e000000000500430: 11 00 00 00 01 00 [MIB] nop.m 0x0
> e000000000500436: 00 00 00 02 00 03 nop.i 0x0
> e00000000050043c: 98 0c 00 41 (p06)
> br.cond.spnt.many e0
> 000000005010c0 <page_fault>;;
> e000000000500440: 0a 00 48 00 2f 04 [MMI]
> itc.i r18;;
> e000000000500446: 00 00 00 02 00 00 nop.m 0x0
> e00000000050044c: d0 09 00 07 mov b0=r29
> e000000000500450: 11 00 00 00 01 00 [MIB] nop.m 0x0
> e000000000500456: f0 ff c0 bf 05 00
> mov pr=r31,0xfffffff
> ffffffffe
> e00000000050045c: 00 00 20 00 rfi;;
>
> Seems like the b0 register is getting restored correctly.
>
> Uros
>
> --
> Uros Prestor
> uros@turbolinux.com
>
>
>
>
> _______________________________________________
> Linux-IA64 mailing list
> Linux-IA64@linuxia64.org
> http://lists.linuxia64.org/lists/listinfo/linux-ia64
>
[-- Attachment #2: ivt.diff --]
[-- Type: application/octet-stream, Size: 1073 bytes --]
--- linux-2.4.0/arch/ia64/kernel/ivt.S Tue Jan 9 03:48:36 2001
+++ linux/arch/ia64/kernel/ivt.S Thu Jan 11 02:30:30 2001
@@ -193,6 +193,7 @@
;;
1: ld8 r18=[r17] // read L3 PTE
;;
+ mov b0=r29
tbit.z p6,p0=r18,_PAGE_P_BIT // page present bit cleared?
(p6) br.cond.spnt.many page_fault
;;
@@ -228,6 +229,7 @@
;;
1: ld8 r18=[r17] // read L3 PTE
;;
+ mov b0=r29
tbit.z p6,p0=r18,_PAGE_P_BIT // page present bit cleared?
(p6) br.cond.spnt.many page_fault
;;
@@ -399,7 +401,6 @@
shr.u r18=r16,PMD_SHIFT // shift L2 index into position
;;
ld8 r17=[r17] // fetch the L1 entry (may be 0)
- mov b0=r30
;;
(p7) cmp.eq p6,p7=r17,r0 // was L1 entry NULL?
dep r17=r18,r17,3,(PAGE_SHIFT-3) // compute address of L2 page table entry
@@ -409,8 +410,8 @@
;;
(p7) cmp.eq.or.andcm p6,p7=r17,r0 // was L2 entry NULL?
dep r17=r19,r17,3,(PAGE_SHIFT-3) // compute address of L3 page table entry
- ;;
(p6) br.cond.spnt.many page_fault
+ mov b0=r30
br.sptk.many b0 // return to continuation point
;;
next prev parent reply other threads:[~2001-01-11 22:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-09 23:03 [Linux-ia64] Kernel panic in dtlb_fault Uros Prestor
2001-01-10 0:40 ` Uros Prestor
2001-01-10 3:15 ` Mallick, Asit K
2001-01-11 1:14 ` Mallick, Asit K
2001-01-11 19:09 ` Uros Prestor
2001-01-11 19:35 ` David Mosberger
2001-01-11 20:12 ` Uros Prestor
2001-01-11 20:23 ` Mallick, Asit K
2001-01-11 22:10 ` Mallick, Asit K [this message]
2001-01-12 19:36 ` Uros Prestor
2001-01-15 23:08 ` Mallick, Asit K
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-105590693005034@msgid-missing \
--to=asit.k.mallick@intel.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