Today is not a good day for -current on alpha

[Wilko Bulte]

On Wed, Aug 20, 2003 at 07:10:24PM +0200, Bernd Walter wrote:
> On Mon, Aug 18, 2003 at 10:15:45PM +0200, Wilko Bulte wrote:
> > Second time today on my quad AS4100:
> > 
> > db> trace
> > sysctl_vm_zone() at sysctl_vm_zone+0x370
> > sysctl_root() at sysctl_root+0x16c
> > userland_sysctl() at userland_sysctl+0x170
> > __sysctl() at __sysctl+0xe8
> > syscall() at syscall+0x3b8
> > XentSys() at XentSys+0x64
> > --- syscall (202, FreeBSD ELF64, __sysctl) ---
> > --- user mode ---
> > db> 
> 
> Was this a missalignment panic?
> I get one reproduceable when going multi with a kernel from 17th.
> Trace looks the same.

No, it was:

 > ^M
 >     trap entry     = 0x2 (memory management fault)^M
 >     cpuid          = 1^M
 >     faulting va    = 0x30010^M
 >     type           = access violation^M
 >     cause          = load instructon^M
 >     pc             = 0xfffffc000058f9a0^M
 >     ra             = 0xfffffc000058fad4^M
 >     sp             = 0xfffffe003b51ba80^M
 >     usp            = 0x11fff328^M
 >     curthread      = 0xfffffc0063d2f7c0^M
 >         pid = 174, comm = sysctl^M
 > ^M
 > Stopped at      sysctl_vm_zone+0x370:   ldq_u   t0,0xfffffffffffffffe(t1)
 > <0x30010>     <t0=0x30000,t1=0x30012>^M
 >

Bosko sent me a patch which fixes the panic, I'm now running a buildworld
with the patched kernel to see if it runs to completion.

-- 
|   / o / /_  _   		wilko at FreeBSD.org
|/|/ / / /(  (_)  Bulte