From: Peter Chubb <peter@chubb.wattle.id.au>
To: linux-ia64@vger.kernel.org
Subject: NaT consumption faults in current 2.5 BK kernel
Date: Thu, 17 Jul 2003 00:21:13 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105840128613012@msgid-missing> (raw)
OK, thanks to the latest mod from David, I have the system running on
the simulator. Hurrah.
I can see a NaT consumption fault every time I cat /proc/net/dev
Is there any easy way to track down what's causing this?
The offending code section is:
dev_seq_pr*+02a0 ld8 r3=[r15],8
MII
mov r34=gp
mov r38=r33;;
ld8 r1=[r15]
mov b7=r3
br.call.sptk.many b0·
;;
in the middle of dev_seq_printf_stats().
I suspect a compiler or assembler bug. I can't see anything obviously
wrong with the generated code.
The branch to dev_seq_printf+0x2a0 is here:
alloc r37 = ar.pfs,3,3,8,0
adds r12 = -96, r12
mov r11 = r0
adds r2 = 88, r33
mov r36 = b0
.body
;;
nop.i 0
ld8 r15 = [r2]
nop.f 0
nop.b 0
;;
cmp.eq p8, p9 = 0, r15
nop.i 0
(p9) br.cond.dpnt.few dev_seq_pr*+02a0
.mii
adds r15€,r11
adds r16ˆ,r11
adds r17–,r11
...
cat[174]: NaT consumption 17179869216 [4]
Pid: 174, CPU 0, comm: cat
psr : 0000101008026018 ifs : 800000000000030e ip :
[<a000000100266f60>] Not tainted
ip is at dev_seq_printf_stats+0x2a0/0x2e0
unat: 0000000000000000 pfs : 0000000000000309 rsc : 0000000000000003
rnat: 0000000000000000 bsps: a00000010065b830 pr : 000000000006aa19
ldrs: 0000000000000000 ccv : 0000000000000000 fpsr: 0009804c0270033f
csd : 0000000000000000 ssd : 0000000000000000
b0 : a000000100266fe0 b6 : a000000100002d70 b7 : a000000100266fa0
f6 : 1003e0000000000004000 f7 : 1003e0000000000000040
f8 : 1003e0000000000000000 f9 : 1003e0000000000000000
f10 : 000000000000000000000 f11 : 000000000000000000000
r1 : a00000010065b830 r2 : e000000007f42858 r3 : 0000000000000002
r8 : e000000007f42800 r9 : 0000000000004000 r10 : 0000000000000143
r11 : 0000000000000000 r12 : e0000000075bfdb0 r13 : e0000000075b8000
Call Trace:
[<a000000100013a20>] show_stack+0x80/0xa0
spà000000075bf910
bspà000000075b9028
[<a000000100020190>] die+0x130/0x1c0
spà000000075bfae0
bspà000000075b9000
[<a000000100020f70>] ia64_fault+0x150/0xec0
spà000000075bfae0
bspà000000075b8fb8
[<a00000010000d840>] ia64_leave_kernel+0x0/0x260
spà000000075bfbe0
bspà000000075b8fb8
[<a000000100266f60>] dev_seq_printf_stats+0x2a0/0x2e0
spà000000075bfdb0
bspà000000075b8f48
[<a000000100266fe0>] dev_seq_show+0x40/0x100
spà000000075bfe10
bspà000000075b8f18
[<a0000001001041e0>] seq_read+0x4c0/0x760
spà000000075bfe10
bspà000000075b8e88
[<a0000001000c6100>] vfs_read+0x200/0x2a0
spà000000075bfe20
bspà000000075b8e40
[<a0000001000c65e0>] sys_read+0x60/0xc0
spà000000075bfe20
bspà000000075b8dc8
[<a00000010000d6c0>] ia64_ret_from_syscall+0x0/0x20
spà000000075bfe30
bspà000000075b8dc8
Segmentation fault
next reply other threads:[~2003-07-17 0:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-17 0:21 Peter Chubb [this message]
2003-07-18 0:08 ` NaT consumption faults in current 2.5 BK kernel (FIXED) Peter Chubb
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-105840128613012@msgid-missing \
--to=peter@chubb.wattle.id.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.