Frank McConnell wrote:
I have two ways to provoke the failure: starting named (a modified
BIND 8
As a general rule, it would be a good idea to start thinking about moving
toward BIND 9. The 9.4 series will have better performance, DNSSEC, and
other attractive features. If you start thinking
dpk wrote:
> On Thu, 4 Aug 2005, Frank McConnell wrote:
>> Further debugging led me to the conclusion that the problem is in
>> pmap_protect(), in src/sys/i386/i386/pmap.c; and has to do with a
[...]
>> Then I checked the cvs logs, and saw rev 1.524, which looks like what
>> I was thinking about as
On Thu, 4 Aug 2005, Frank McConnell wrote:
> Further debugging led me to the conclusion that the problem is in
> pmap_protect(), in src/sys/i386/i386/pmap.c; and has to do with a
> 32-bit-truncated pt_entry_t being passed to PHYS_TO_VM_PAGE().
> (pt_entry_t is 64 bits if the kernel is built with P
Further debugging led me to the conclusion that the problem is in
pmap_protect(), in src/sys/i386/i386/pmap.c; and has to do with a
32-bit-truncated pt_entry_t being passed to PHYS_TO_VM_PAGE().
(pt_entry_t is 64 bits if the kernel is built with PAE.) This caused
a page fault in vm_page_flag_set()
Earlier I wrote:
> It looks to me like the pagedaemon is running and trying to acquire
> the vm page queue mutex, which appears to be owned on behalf of named,
> which isn't running but also isn't blocked on a turnstile.
And looking at the same crash (haven't rebooted yet), it occurred to
me that
Poking at this some more
Yesterday I put together another PC, installed 5.4-RELEASE, cvsup'd to
RELENG_5 using stable-supfile, built world and kernel, installed
kernel and world, then built a new kernel for the target with kernel
config file as follows:
--- begin kernel config ---
include PAE
Robert Watson wrote:
> This appears to be a NULL pointer dereference in
> propagate_priotity(). Often a panic in propagate_priority is actually
> a symptom of a slightly earlier problem which is discovered by
> propagate_priority when it trips over, for example, a bad mutex. If
> you're set up wit
On Thu, 28 Jul 2005, Frank McConnell wrote:
--- begin paste ---
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x24
fault code = supervisor read, page not present
instruction pointer= 0x8:0xc03db1cf
stack pointer = 0x10:0xeb328c64
frame pointer
Intel SE7320VP2 motherboard with single Xeon 2.8GHz, 4GB RAM, and an
80GB disk and a CD-ROM drive connected to motherboard ATA. 1GB of the
RAM appears above 4GB which suggested building a PAE kernel. So,
imagine 5.4-RELEASE with a kernel config file that goes like this:
include PAE
options MAXDS
