Date: Tue, 17 Sep 2002 19:03:22 -0600 From: "Kenneth D. Merry" <ken@kdm.org> To: marius@alchemy.franken.de Cc: freebsd-current@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: page fault while in kernel mode, cam related ? Message-ID: <20020917190321.A99415@panzer.kdm.org> In-Reply-To: <20020918025349.C96711@newtrinity.default-network.net>; from marius@alchemy.franken.de on Wed, Sep 18, 2002 at 02:53:49AM %2B0200 References: <20020918025349.C96711@newtrinity.default-network.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Sep 18, 2002 at 02:53:49 +0200, marius@alchemy.franken.de wrote: > > hi > > while trying to upgrade a -current box with an older scsi hd a scsi error > seemed to have triggered a panic (actually the first ever on that box): > > (da0:ahc0:0:0:0): READ(10). CDB: 28 0 0 4b 94 df 0 0 20 0 > (da0:ahc0:0:0:0): CAM Status: SCSI Status Error > (da0:ahc0:0:0:0): SCSI Status: Check Condition > (da0:ahc0:0:0:0): RECOVERED ERROR info:4b94f5 csi:b,b9,2,a2 asc:18,2 > (da0:ahc0:0:0:0): Recovered data - data auto-reallocated field replaceable unit1 > (da0:ahc0:0:0:0): No Recovery Action Needed That's just an informative message, you had a bad block that was reallocated. > Fatal trap 12: page fault while in kernel mode > fault virtual address = 0x3e > fault code = supervisor write, page not present > instruction pointer = 0x8:0xc02d3241 > stack pointer = 0x10:0xcfd2d954 > frame pointer = 0x10:0xcfd2d96c > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = 15268 (cpp0) > kernel: type 12 trap, code=0 > Stopped at vm_object_pip_add+0x21: addw %si,0x3e(%ebx) > db> Context switches not allowed in the debugger. > db> tr > vm_object_pip_add(0,1,0,0,c1f1e000) at vm_object_pip_add+0x21 > vm_fault(c0832000,c88c2000,2,0,c21b2b40) at vm_fault+0x212 > trap_pfault(cfd2dab8,0,c88c2001) at trap_pfault+0x131 > trap(18,10,10,c88c2001,c5c0add8) at trap+0x3ab > calltrap() at calltrap+0x5 > --- trap 0xc, eip = 0xc03025cf, esp = 0xcfd2daf8, ebp = 0xcfd2db44 --- > generic_bzero(cfd2dba0,cfd2dbcc,c02be266,cfd2dba0,4) at generic_bzero+0xf > spec_vnoperate(cfd2dba0) at spec_vnoperate+0x13 > ffs_getpages(cfd2dbd8) at ffs_getpages+0x406 > vnode_pager_getpages(c1fac708,cfd2dc8c,10,0) at vnode_pager_getpages+0x62 > vm_fault(c27883fc,28304000,1,0,c21b2b40) at vm_fault+0x6d6 > trap_pfault(cfd2dd48,1,28304000,28304000,0) at trap_pfault+0xed > trap(2f,2f,2f,839e000,83a5008) at trap+0x22b > calltrap() at calltrap+0x5 > --- trap 0xc, eip = 0x806e373, esp = 0xbfbfeff0, ebp = 0xbfbff008 --- > > > i don't know if fbsd is supposed to panic in case of such an error but i > think to remember similar cam/scsi errors under 4-stable that didn't > trigger a panic. > btw, this box is connected via a serial console at 9600 bps and while typing > at the ddb-prompt it swallowed most characters, i.e. i had to type single > characters up to four times. It doesn't look like the message above and the panic are related. The panic is in the VM code, I don't see any CAM functions in there. So my guess is that it's just a coincidence. You might try sending mail to the -current list and see if anyone has seen this sort of panic lately. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020917190321.A99415>