Date: Wed, 18 Nov 2009 23:22:44 -0800 From: Julian Elischer <julian@elischer.org> To: Justin Wong <jmnwong@gmail.com> Cc: freebsd-virtualization@freebsd.org Subject: Re: Random Page Fault on Soekris Message-ID: <4B04F244.903@elischer.org> In-Reply-To: <66313f8d0911181205t4fccb9a1o1d1c346602813ba2@mail.gmail.com> References: <66313f8d0911181205t4fccb9a1o1d1c346602813ba2@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Justin Wong wrote: > Hi all, > > I am currently running a snapshot of the vimage source > (vimage_7_20090505.tgz) against FreeBSD 7.1 on a Soekris Net5501-70. I am > running a small load on the Soekris board and periodically I will receive > the following error: > > > ---------- > Fatal trap 12: page fault while in kernel mode > fault virtual address = 0x8 > fault code = supervisor read, page not present > instruction pointer = 0x20:0xc068745b > stack pointer = 0x28:0xc4362c18 > frame pointer = 0x28:0xc4362c44 > 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 = 13 (swi4: clock sio) > [thread pid 13 tid 100004 ] > Stopped at send_pkt+0x1b: movl 0x8(%eax),%eax > > db> bt > Tracing pid 13 tid 100004 td 0xc4439690 > send_pkt(3437336e,2,c4439af0,c4439690,c4362c64,...) at send_pkt+0x1b > ipfw_tick(c453b400,c4439690,0,c4362cbc,c05c1f93,...) at ipfw_tick+0x10e > softclock(0,0,c0838d87,4a1,aa55aa55,...) at softclock+0x247 > ithread_loop(c4436020,c4362d38,aa55aa55,aa55aa55,aa55aa55,...) at > ithread_loop+0x1ab > fork_exit(c05986f0,c4436020,c4362d38) at fork_exit+0x96 > fork_trampoline() at fork_trampoline+0x8 > --- trap 0, eip = 0, esp = 0xc4362d70, ebp = 0 --- > > db> show registers > cs 0x20 > ds 0xc4430028 > es 0xc4360028 > fs 0x8 > ss 0x28 > eax 0 > ecx 0x3065b7ee > edx 0xc4b45598 > ebx 0xc4b4557c > esp 0xc4362c18 > ebp 0xc4362c44 > esi 0xc453b400 > edi 0x70 > eip 0xc068745b send_pkt+0x1b > efl 0x10286 > send_pkt+0x1b: movl 0x8(%eax),%eax I'm running a -current (as of a month or so ago) on a 5501 with teh standard new vimage code. I do not use the vimage part of it much (just for testing) but I have not seen this error. 7.1 based vimage will be probably not developed much more soit may be worth switching to -current which has it built in. ipfw was re-ported to vimage in -current to support new features. Julian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4B04F244.903>