Date: Thu, 9 Oct 2003 13:04:47 -0700 From: Joao Pedras <jpedras@webvolution.net> To: "Kevin Oberman" <oberman@es.net> Cc: freebsd-stable@freebsd.org Subject: Re: panic after update Message-ID: <20031009130447.7a0fdc06.jpedras@webvolution.net> In-Reply-To: <20031009162058.AA0445D07@ptavv.es.net> References: <20031008211436.2b1f5ff7.jpedras@webvolution.net> <20031009162058.AA0445D07@ptavv.es.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Kevin, first of all thank you for your quick reply. It was a good sugestion. The kernel boots up perfectly without apm. I already submitted a pr. Thanks! On Thu, 09 Oct 2003 09:20:58 -0700 "Kevin Oberman" <oberman@es.net> wrote: > > Date: Wed, 8 Oct 2003 21:14:36 -0700 > > From: Joao Pedras <jpedras@webvolution.net> > > Sender: owner-freebsd-stable@freebsd.org > > > > > > Hi all, > > > > After going over the usual steps to update my laptop (thinkpad A31) to today's -stable I get > > a kernel panic when booting the new kernel. I didn't change anything in the kernel > > config or anywhere else for that matter. This laptop has been running sucessfully several > > versions of -stable over the last year. > > > > buildworld, buildkernel and friends were 100% sucessfull. > > > > Any insight into this matter is appreciatted. > > > > Here is the output: > > > > apm0: <APM BIOS> on motherboard > > Kernel trap 12 with interrupts disabled > > Fatal trap 12: page fault while in kernel mode > > fault virtual address = 0x36 > > fault code = supervisor write, page not present > > instruction pointer = 0x8:0xc025b240 > > stack pointer = 0x10:0xc0436d6e > > frame pointer = 0x10:0xc0436e0e > > code segment = base 0x0, limit 0xfffff, type 0x1b > > = DPL 0, pres 1, def 32 1, gran 1 > > processor eflags = interrupt enabled, resume, IOPL = 0 > > current process = 0 (swapper) > > interrupt mask = net tty bio com > > trap number = 12 > > panic: page fault > > uptime : 0s > > Automatic reboot in 15 seconds > > This looks like it MIGHT be an APM problem which Peter Wemm found and > fixed in CURRENT about a week ago. As far as I know, this is the first > report of the problem on a STABLE system (if it's the same problem). > > Try building a new kernel without APM (and don't load it in > /boot/loader.conf, either). If this allows the system to boot, please > submit a PR so that the few people who understand the locore.s stuff > well enough to have a chance to find it can get it fixed. (I am not > one of those people.) > -- > R. Kevin Oberman, Network Engineer > Energy Sciences Network (ESnet) > Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) > E-mail: oberman@es.net Phone: +1 510 486-8634 --
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031009130447.7a0fdc06.jpedras>