Date: Fri, 15 Apr 2005 19:29:26 +0200 From: Eirik =?ISO-8859-1?B?2A==?=verby <ltning@anduin.net> To: Doug White <dwhite@gumbysoft.com> Cc: "current@freebsd.org" <current@freebsd.org> Subject: Re: Panic after "in_cksum_skip: out of data by 260" Message-ID: <BE85C696.13B57%ltning@anduin.net> In-Reply-To: <20050415102457.F34838@carver.gumbysoft.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 15-04-05 19:26, "Doug White" <dwhite@gumbysoft.com> wrote: > On Wed, 13 Apr 2005, Eirik [ISO-8859-1] =D8verby wrote: >=20 >> Hi, >>=20 >> Today I received this message on my serial console: >>=20 >> in_cksum_skip: out of data by 260 >=20 > From a brief reading of the source it looks like this is a corrupted mbuf > that got tripped over later. If you can reproduce this I'd turn the > printf at the end of src/sys/i386/i386/in_cksum.c into a panic and get a > crashdump so the bad data can be analysed. If I could reproduce it I would have ;) But this is the first time I've see= n it, and I somehow doubt I'll be seeing it any time soon. I have enabled crash dumping and all that on the system though, so we'll see, but as it's = a production system I can't play around too much. I have instructed the monitoring and support folks what to do if it SHOULD happen again though, so we can get some proper data out of it. But don't hold your breath..... Thanks, /Eirik >=20 >> Fatal trap 12: page fault while in kernel mode >> cpuid =3D 1; apic id =3D 00 >> fault virtual address =3D 0xc >> fault code =3D supervisor read, page not present >> instruction pointer =3D 0x8:0xc066ec33 >> stack pointer =3D 0x10:0xd5437974 >> frame pointer =3D 0x10:0xd5437998 >> code segment =3D base 0x0, limit 0xfffff, type 0x1b >> =3D DPL 0, pres 1, def32 1, gran 1 >> processor eflags =3D interrupt enabled, resume, IOPL =3D 0 >> current process =3D 36 (swi1: net) >> trap number =3D 12 >> panic: page fault >> cpuid =3D 1 >> boot() called on cpu#0 >> Uptime: 1d15h8m10s >>=20 >> This server has been very stable for a very long time. This crash surpri= ses >> me somewhat. >> Uname output: >> FreeBSD carnen.net 5.3-STABLE FreeBSD 5.3-STABLE #0: Wed Feb 2 21:02:44= CET >> 2005 root@carnen.net:/usr/obj/usr/src/sys/CARNEN i386 >>=20 >> Any idea what could have caused this? >>=20 >> Thanks, >> /Eirik >>=20 >>=20 >> _______________________________________________ >> freebsd-current@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.or= g" >>=20
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BE85C696.13B57%ltning>