On Fri, Oct 17, 2003 at 09:51:57AM -0700, Peter Wemm wrote:
>
> AHA! origpte being 0xd0d0d0d0 means that something really came unstuck
> because that is the fill pattern that userland malloc(3) uses. The
> 4MB page thing is a red herring, it just happens that PG_PS (0x80) is
> a set bit in the f
Jilles Tjoelker wrote:
> Hello,
>
> Yesterday our 5-CURRENT box panicked with panic: pmap_enter: attempted
> pmap_enter on 4MB page.
[..]
> (kgdb) p va
> $1 = 689672192
> (kgdb) p pte
> $2 = (pt_entry_t *) 0xbfca46e4
> (kgdb) p origpte
> $3 = 3503345872
>
Hello,
Yesterday our 5-CURRENT box panicked with panic: pmap_enter: attempted
pmap_enter on 4MB page.
uname -a:
FreeBSD turtle.stack.nl 5.1-CURRENT FreeBSD 5.1-CURRENT #15: Thu Oct 9 11:43:55 CEST
2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/TURTLE i386
This kernel includes a patch from
I've been getting subject panics lately. A sure way to provoke them is
to portupgrade -ap. Sooner or later, panic. With the latest build:
FreeBSD lab.databus.com 5.1-CURRENT FreeBSD 5.1-CURRENT #1: Tue Oct 14 01:41:23 EDT
2003
it seemed to last longer (almost 30 min!) before failing.
HW is As
I've been getting this panic a lot in the past week. Unfortunately it's on my
file server so I can't use gdb to get more details than what ddb provides
(the kernel is on the machine that's panic'd). This is a UP x86 box. The
stack trace is:
pmap_enter
kmem_malloc
page_alloc
slab_zalloc
uma_z
O: Testing 8254 interrupt delivery
APIC_IO: routing 8254 via IOAPIC #0 intpin 2
Timecounters tick every 10.000 msec
acpi_cpu: throttling enabled, 2 steps (100% to 50.0%), currently 100.0%
GEOM: create disk ad0 dp=0xc6537b70
ad0: 78533MB [159560/16/63] at ata0-master UDMA100
SMP: AP CPU #1 Launched!
Mounting
[EMAIL PROTECTED] wrote:
>
> > pci50: physical bus=-1061225984
> >
> > A little dubious, I think. Below is the dmesg(8) output from
> > kernel.old, my last good kernel built yesterday, booted with ``boot
> > -v''.
> >
>
> The enclosed patch might be relevant. I got similar problems without
>
> pci50: physical bus=-1061225984
>
> A little dubious, I think. Below is the dmesg(8) output from
> kernel.old, my last good kernel built yesterday, booted with ``boot
> -v''.
>
The enclosed patch might be relevant. I got similar problems without
it.
Index: pcisupport.c
===
nic: pmap_enter: attempted pmap_enter on 4MB page
The backtrace is _huge_, too much to copy down by hand, and this seems
too early to capture in a dump.
However, I notice that the ``boot -v'' probe messages at the time looked
odd:
pci50: physical bus=-1061225984
A little dubious, I thi
Peter Wemm wrote:
> Martin Cracauer wrote:
> > I'm getting the appended panic when starting Xfree86 under a -current
> > from today. I rebuild/reinstalled binutils (and kernel afterwards)
> > and sys/boot.
>
> I think I know what is causing this. We're passing a non-page-aligned
> address to pm
Martin Cracauer wrote:
> I'm getting the appended panic when starting Xfree86 under a -current
> from today. I rebuild/reinstalled binutils (and kernel afterwards)
> and sys/boot.
I think I know what is causing this. We're passing a non-page-aligned
address to pmap_kenter() in mem.c... I think
03
#1 0xc01e9e71 in panic (
fmt=0xc03a1d20 "pmap_enter: attempted pmap_enter on 4MB page")
at ../../kern/kern_shutdown.c:553
#2 0xc032b4d2 in pmap_enter (pmap=0xc0419240, va=3229622272, m=0xc09238d4,
prot=7 '\a', wired=0) at ../../i386/i386/pmap.c:2023
#3 0xc02e926c in
12 matches
Mail list logo
