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
> (kgdb) p (void *)va
> $4 = (void *) 0x291b
[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
===
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
