Date: Fri, 14 May 1999 11:13:06 +0200 (CEST) From: "Karel J. Bosschaart" <karelj@wop21.wop.wtb.tue.nl> To: freebsd-stable@FreeBSD.ORG Subject: Re: KERNEL PANIC in 3.1-stable Message-ID: <Pine.BSF.4.05.9905141042520.72700-100000@wop21.wop.wtb.tue.nl> In-Reply-To: <008201be9d64$de7ee0a0$380051c2@greg.qmpgmc.ac.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 13 May 1999, Greg Quinlan wrote:
> They should be in /var/log/messages.... ?
>
> But I have searched and nothing!
>
> Is there some way I can delay the reboot process; so that some one can write
> down a proper message when it happens again?
I also have nothing in /var/log/messages, but I find the messages in the
dumped core when looking at it with kgdb... I produced 3 dumps last night,
finally I know more or less how to reproduce the panic on my system. It's
weird; the panics *only* happen when I "cold-started" the computer, that's
with the power-button. Then it lasts for minutes to some hours for the
panic to occur. After the subsequent reboot, the system appears rock
stable to me. I have 3.1-STABLE cvsupped on 30 April, from that day
I left my computer on and I didn't get any panic until I switched it
off (after 10 days) and turned it on couple of hours later: reboot in one
hour. It seems indicative to me for some hardware initialization problems,
but I wouldn't know exactly what part of the system.
What does the message "BIOS EXTMEM (...) != RTC EXTMEM (...)" mean
exactly? Is it harmful? I noticed it scrolling by when rebooting but
couldn't find it back with dmesg. BIOS EXTMEM was 64MB, the other 128MB,
which is the amount of memory I have and is also used by FreeBSD. Do I
need to revise my BIOS settings? There is an option "OS/2 Onboard Memory
> 64 MB" which is disabled by default.
> >> Fatal trap 12: page fault while in kernel mode
> >> fatal virtual address: 0x0
> >> fatal code = supervisor read page not present
> >> instruction pointer = .......
> >> stack pointer = .......
> >> frame pointer = ......
> >> code segment = base 0x0 limit 0xfffff
> >> current process = 14802
> >> interupt mask
> >> trap number = 12
> >> panic: page fault
> >> syncing disks................
Very similar to my messages (from kgdb, see below). This one was with the
GENERIC kernel (as of 30 April). It looks very similar for my own kernel,
though some numbers are different. Always a page fault, either read or
write.
Karel.
(kgdb) symbol-file kernel
Reading symbols from kernel...done.
(kgdb) exec-file /home/karelj/crash.GENERIC/kernel.0
(kgdb) core-file /home/karelj/crash.GENERIC/vmcore.0
IdlePTD 3469312
initial pcb at 2da760
panicstr: page fault
panic messages:
---
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0xc5eb9dd0
fault code = supervisor write, page not present
instruction pointer = 0x8:0xc0225165
stack pointer = 0x10:0xc5e3ee6c
frame pointer = 0x10:0xc5e3ee78
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 = 34940 (sh)
interrupt mask =
trap number = 12
panic: page fault
syncing disks... 2 done
dumping to dev 40001, offset 142128
dump 127 126 125 124 123 122 121 120 119 118 117 116 115 114 113 112 111 110 109 108 107 106 105 104 103 102 101 100 99 98 97 96 95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
---
#0 boot (howto=256) at ../../kern/kern_shutdown.c:285
285 dumppcb.pcb_cr3 = rcr3();
(kgdb)
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.05.9905141042520.72700-100000>