Date: Fri, 21 Nov 2003 14:24:24 -0500 From: Peter Radcliffe <pir@pir.net> To: freebsd-stable@freebsd.org Subject: Re: Hang on boot with 4.9-STABLE Message-ID: <20031121192423.GA20052@pir.net> In-Reply-To: <20031121092104.U57910@carver.gumbysoft.com> References: <20031118001514.GC15325@pir.net> <20031120094552.M48733@carver.gumbysoft.com> <20031120150136.P50912@carver.gumbysoft.com> <20031120232332.GI3321@pir.net> <20031121092104.U57910@carver.gumbysoft.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Doug White <dwhite@gumbysoft.com> probably said:
> Well, until you can spend some time on them to provoke crashdumps or find
> the date things go bad or whatever, there isn't much we can do.
I installed the spare remote controlled power strip today and managed
to persuade the owner of the systems to give me some time to move the
power to it and using one to debug for a bit.
Switching to acpi (or simply removing apm from the config) does seem
to work around the problem, but experimental acpi in 4.x doesn't give
me warm fuzzy feelings.
Don't seem to be able to provoke a crashdump, even with loader.conf
setting where to dump to, but with RELENG_4 source from
date=2003.10.15.05.00.00 I do get a kernel trap;
apm0: <APM BIOS> on motherboard
kernel trap 12 with interrupts disabled
Fatal trap 12: page fault while in kernel mode
mp_lock = 00000006; cpuid = 0; lapic.id = 00000000
fault virtual address = 0x36
fault code = supervisor write, page not present
instruction pointer = 0x8:0xc020d05a
stack pointer = 0x10:0xc03fad66
frame pointer = 0x10:0xc03fae06
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 = 0 (swapper)
interrupt mask = net tty bio cam <- SMP: XXX
kernel: type 12 trap, code=0
Stopped at vm_fault+0x132: lock addw %ax,0x36(%edx)
db> trace
vm_fault(c0354e2c,c0000000,2,0,c) at vm_fault+0x132
trap_pfault(c03fae82,0,c00004d8,ffffffff,0) at trap_pfault+0xda
trap(18,70000010,60,1c,0) at trap+0x377
calltrap() at calltrap+0x17
--- trap 0xc, eip = 0x6096, esp = 0xc03faec2, ebp = 0xc03faec8 ---
gd_idlestack(aedc0058,0,530e0102,80202,5061aa) at 0x6096
I've limited the time of the problem being introduced to between
date=2003.10.10.05.00.00 and date=2003.10.15.05.00.00 and am working
on finding a more exact range.
P.
--
pir
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031121192423.GA20052>