From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@quanstro.net
Subject: [9fans] kernel panic
Date: Sun, 29 Jul 2007 20:32:07 -0400 [thread overview]
Message-ID: <43deece94abb1cac0134faadb901aac0@quanstro.net> (raw)
unfortuantely, it's not obvious to me which memmove is triggering
this panic.
- erik
ladd# fcpu1: registers for validateaddress 25320
aFLAGS=10202 TRAP=E ECODE=2 PC=F0195E51u SS=5F66 USP=F027F830
l AX 0082801C BX F082D098 CX 00000000 DX F082D098
t SI 00005000 DI 0001E000 BP 00000002
CS 0010 DS 0008 ES 0008 FS 001B GS 001B
n CR0 80010039 CR2 00828058 CR3 0763f000l CR4 000000d0o
MCA 86a0985d12 MCT 00000000c
ur f29f42c4 up f0305b38
kpanic: fault: 0x828058
s 1
lock 0xf027f830 loop key 0xdeaddead pc 0xf01961dd held by pc 0xf0195f66 proc 25320
25318:validateaddress pc f01a683c dbgpc 373b Fault (Running) ut 0 st 27 bss 3f000 qpc f0195949 nl 0 n0
25320:validateaddress pc f015375f dbgpc 3615 Fault (Running) ut 0 st 10 bss 3f000 qpc f0195949 nl 2 n0
pdumpstack disabled
acpu1: exiting
nic: fault: 0x828058
acid: src(0xf0195f66)
/sys/src/9/port/page.c:129
124 KMap *k;
125 uchar ct;
126 int i, hw, dontalloc, color;
127
128 lock(&palloc);
>129 color = getpgcolor(va);
130 hw = swapalloc.highwater;
131 for(;;) {
132 if(palloc.freecount > hw)
133 break;
134 if(up->kp && palloc.freecount > 0)
acid: src(0xf01a683c)
/sys/src/libc/386/memmove.s:32
27 _forward:
28 MOVL BX, CX
29 CLD
30 SHRL $2, CX
31 ANDL $3, BX
>32 REP; MOVSL
33
34 /*
35 * copy the rest, by bytes
36 */
37 JEQ _return /* flags set by above ANDL */
next reply other threads:[~2007-07-30 0:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-30 0:32 erik quanstrom [this message]
2007-09-26 13:58 [9fans] Kernel Panic Brad Frank
2007-09-26 14:24 ` erik quanstrom
2007-09-26 15:25 [9fans] kernel panic Brad Frank
2007-09-26 15:56 ` erik quanstrom
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=43deece94abb1cac0134faadb901aac0@quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@quanstro.net \
/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;
as well as URLs for NNTP newsgroup(s).