Date: Mon, 24 Oct 2005 12:11:29 +0100 From: Owen Smith <og.smith@gmail.com> To: freebsd-questions@freebsd.org Subject: page fault while in kernel mode Message-ID: <472ab61e0510240411t77f839fcm51f4455c62f99144@mail.gmail.com>
next in thread | raw e-mail | index | archive | help
Hi Whilst running 5.3-RELEASE-p22 on a GENERIC+ SMP options kernel we have had this: Fatal trap 12: page fault while in kernel mode cpuid =3D 1; apic id =3D 00 fault virtual address =3D 0x42d38cf0 fault code =3D supervisor write, page not present instruction pointer =3D 0x8:0xc062f242 stack pointer =3D 0x10:0xeb4649bc frame pointer =3D 0x10:0xeb4649c4 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 1015 (screen) trap number =3D 12 panic: page fault cpuid =3D 1 boot() called on cpu#1 Uptime: 12d18h29m43s Cannot dump. No dump device defined. iir0: Flushing all Host Drives. Please wait ... kernel trap 12 with interrupts disabled Fatal trap 12: page fault while in kernel mode cpuid =3D 0; apic id =3D 01 fault virtual address =3D 0x24 fault code =3D supervisor read, page not present instruction pointer =3D 0x8:0xc062c613 stack pointer =3D 0x10:0xe4dffc30 frame pointer =3D 0x10:0xe4dffc44 code segment =3D base 0x0, limit 0xfffff, type 0x1b =3D DPL 0, pres 1, def32 1, gran 1 processor eflags =3D resume, IOPL =3D 0 current process =3D 37 (swi5: clock sio) trap number =3D 12 spin lock sched lock held by 0xc22b94b0 for > 5 seconds panic: spin lock held too long cpuid =3D 1 spin lock sched lock held by 0xc22b94b0 for > 5 seconds panic: spin lock held too long cpuid =3D 1 # nm -n /boot/kernel/kernel | grep c062f c062f098 T openbsd_poll c062f0a8 T clear_selinfo_list c062f0d4 T selrecord c062f178 T selwakeup c062f188 T selwakeuppri c062f198 t doselwakeup c062f320 t selectinit c062f348 t pipeinit c062f37c t pipe_zone_ctor c062f454 t pipe_zone_dtor c062f468 t pipe_zone_init c062f48c t pipe_zone_fini c062f4a0 T pipe c062f794 t pipespace_new c062f8d0 t pipespace c062f8e0 t pipe_create c062f94c t pipe_read c062ff34 t pipe_build_write_buffer It is the 2nd time in a month the server has crashed the first time it rebooted on its own so I didn't get the error, but this time I had to power cycle it. The server is a Dual 800MHz intel box with 1.5GB RAM and 4*36GB RAID SCSI d= isks, It generally is not under much load. Whats the best thing todo? debugging kernel etc or just upgrade to 5.4? Thanks Ogg
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?472ab61e0510240411t77f839fcm51f4455c62f99144>