From: Keith Owens <kaos@ocs.com.au>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] Intermittent errors on mov rr
Date: Fri, 16 Feb 2001 07:45:00 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590693005157@msgid-missing> (raw)
BigSur dual B3. Kernel 2.4.1 + ia64-010131 + kdb (no switch_stack
changes). Cross compiled with gcc version 2.96-ia64-000717 snap
001117.
I get intermittent errors in copy_mm+0x6b0, where it is setting the new
region registers. This only happens under high load, like compiling
gcc. I cannot see why IA64 is complaining here, any ideas?
sh[8767]: General Exception: IA-64 Reserved Register/Field fault (data access) 2199023255600
psr : 0000121008026018 ifs : 8000000000000996 ip : [<e000000000565491>]
unat: 0000000000000000 pfs : 0000000000000996 rsc : 0000000000000003
rnat: 0000000000000000 bsps: e000000000aa2d40 pr : 0000000015950253
ldrs: 0000000000000000 ccv : 0000000000000000 fpsr: 0009804c0270033f
b0 : e000000000565250 b6 : e000000000502f60 b7 : e0000000005210a0
f6 : 1003e000000000004b2f8 f7 : 1003eaaaaaaaaaaaaaaab
f8 : 1003e000000000000002f f9 : 10004d400000000000000
r1 : e000000000aa2d40 r2 : 0000000000000000 r3 : 8000100000000000
r8 : 0000000000000000 r9 : 0000000000000996 r10 : 0000000000000000
r11 : 0000000000000287 r12 : e00000002750fbf0 r13 : e000000027508000
r14 : 0000000004000039 r15 : 0000000000200000 r16 : 0000000000000000
r17 : 0000000004000139 r18 : 0000000004000239 r19 : 0000000004000339
r20 : 0000000004000439 r21 : e000000000a6e540 r22 : e00000003f176c2c
r23 : e00000003f0c1800 r24 : e00000003f176c18 r25 : e00000003f176c2c
r26 : e00000003f176c20 r27 : e000000026ab0180 r28 : e000000026ab0198
r29 : 0000000000000001 r30 : 0000000000000008 r31 : 0000000000000027
r32 : 0000000000000000 r33 : 0000000000000000 r34 : 0000000000000000
r35 : 0000000000000000 r36 : 0000000000000000 r37 : 0000000000000000
r38 : 0000000000000000 r39 : 0000000000000000 r40 : 0000000000000000
r41 : 0000000000000000 r42 : 0000000000000000 r43 : 0000000000000000
r44 : 0000000000000000 r45 : 0000000000000000 r46 : 0000000000000000
r47 : 0000000000000000 r48 : 0000000000000000 r49 : 0000000000000000
r50 : 0000000000000000 r51 : 0000000000000000 r52 : 0000000000000000
r53 : 0000000000000000
Call Trace: [<e000000000527020>] sp=0xe00000002750f770 bsp=0xe000000027509198
[<e0000000005277b0>] sp=0xe00000002750f930 bsp=0xe000000027509148
[<e000000000532510>] sp=0xe00000002750f950 bsp=0xe000000027509120
[<e000000000533ca0>] sp=0xe00000002750f950 bsp=0xe0000000275090e8
[<e000000000521740>] sp=0xe00000002750fa50 bsp=0xe0000000275090e8
[<e000000000565490>] sp=0xe00000002750fbf0 bsp=0xe000000027509038
[<e000000000566cc0>] sp=0xe00000002750fbf0 bsp=0xe000000027508fa0
[<e0000000005210d0>] sp=0xe00000002750fc30 bsp=0xe000000027508f80
[<e000000000521720>] sp=0xe00000002750fe60 bsp=0xe000000027508f80
Entering kdb (current=0xe000000027508000, pid 8767) on processor 0 Panic: <NULL>
due to panic @ 0xe000000000565491
psr: 0x0000121008026018 ifs: 0x8000000000000996 ip: 0xe000000000565490
unat: 0x0000000000000000 pfs: 0x0000000000000996 rsc: 0x0000000000000003
rnat: 0x0000000000000000 bsps: 0xe000000000aa2d40 pr: 0x0000000015950253
ldrs: 0x0000000000000000 ccv: 0x0000000000000000 fpsr: 0x0009804c0270033f
b0: 0xe000000000565250 b6: 0xe000000000502f60 b7: 0xe0000000005210a0
r1: 0xe000000000aa2d40 r2: 0x0000000000000000 r3: 0x8000100000000000
r8: 0x0000000000000000 r9: 0x0000000000000996 r10: 0x0000000000000000
r11: 0x0000000000000287 r12: 0xe00000002750fbf0 r13: 0xe000000027508000
r14: 0x0000000004000039 r15: 0x0000000000200000 r16: 0x0000000000000000
r17: 0x0000000004000139 r18: 0x0000000004000239 r19: 0x0000000004000339
r20: 0x0000000004000439 r21: 0xe000000000a6e540 r22: 0xe00000003f176c2c
r23: 0xe00000003f0c1800 r24: 0xe00000003f176c18 r25: 0xe00000003f176c2c
r26: 0xe00000003f176c20 r27: 0xe000000026ab0180 r28: 0xe000000026ab0198
r29: 0x0000000000000001 r30: 0x0000000000000008 r31: 0x0000000000000027
®s = e00000002750fa60
[0]kdb> bt
0xe000000000565490 copy_mm+0x6b0
args (0xe000000000a6c094, 0xe000000026ab0098, 0xe000000000a6c090, 0xe00000003a8e5c30, 0xe000000000a1d640)
kernel .text 0xe000000000500000 0xe000000000564de0 0xe000000000565680
0xe000000000566cc0 do_fork+0xbc0
args (0x11, 0x0, 0xe00000002750fe70, 0x0, 0xe000000026ab0000)
kernel .text 0xe000000000500000 0xe000000000566100 0xe000000000567380
0xe0000000005210d0 sys_clone+0x50
args (0x11, 0x0, 0xe000000000521720, 0x2)
kernel .text 0xe000000000500000 0xe000000000521080 0xe000000000521100
0xe000000000521720 ia64_ret_from_syscall
args (0x11, 0x0)
kernel .text 0xe000000000500000 0xe000000000521720 0xe000000000521740
[0]kdb> id 0xe000000000565480
0xe000000000565480 copy_mm+0x6a0 [MII] adds r17%6,r14
0xe000000000565486 copy_mm+0x6a6 adds r18Q2,r14
0xe00000000056548c copy_mm+0x6ac adds r19v8,r14
0xe000000000565490 copy_mm+0x6b0 [MMI] adds r20\x1024,r14
0xe000000000565496 copy_mm+0x6b6 mov rr[r16]=r14
0xe00000000056549c copy_mm+0x6bc nop.i 0x0
0xe0000000005654a0 copy_mm+0x6c0 [MLX] nop.m 0x0
0xe0000000005654a6 copy_mm+0x6c6 movl r15=0x2000000000000000;;
0xe0000000005654b0 copy_mm+0x6d0 [MLX] mov rr[r15]=r17
0xe0000000005654b6 copy_mm+0x6d6 movl r14=0x4000000000000000;;
0xe0000000005654c0 copy_mm+0x6e0 [MLX] mov rr[r14]=r18
0xe0000000005654c6 copy_mm+0x6e6 movl r15=0x6000000000000000;;
0xe0000000005654d0 copy_mm+0x6f0 [MLX] mov rr[r15]=r19
0xe0000000005654d6 copy_mm+0x6f6 movl r14=0x8000000000000000;;
0xe0000000005654e0 copy_mm+0x700 [MMI] mov rr[r14]=r20;;
0xe0000000005654e6 copy_mm+0x706 srlz.i
0xe0000000005654ec copy_mm+0x70c nop.i 0x0;;
0xe0000000005654f0 copy_mm+0x710 [MMI] mov r34=r37
0xe0000000005654f6 copy_mm+0x716 mf
0xe0000000005654fc copy_mm+0x71c nop.i 0x0
next reply other threads:[~2001-02-16 7:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-16 7:45 Keith Owens [this message]
2001-02-16 19:12 ` [Linux-ia64] Intermittent errors on mov rr Jim Hull
2001-02-16 19:48 ` David Mosberger
2001-02-16 23:57 ` Keith Owens
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-105590693005157@msgid-missing \
--to=kaos@ocs.com.au \
--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