Crashes with the current -HEAD

[Juli Mallett]

JC,

It's probably my fault if that's when your last good kernel was.  Do
you mind trying updating to r206713 then r206714 then r206717 then
r206819 and r206834?  Or start with r206717 and go earlier or later
based on whether it works.  If you can figure out what commit was at
fault, I'll be glad to work with you to isolate whatever's
responsible.  In the meantime, I'll try to reproduce and fix this
locally.

Thanks,
Juli.

On Fri, Apr 23, 2010 at 06:38, C. Jayachandran <c.jayachandran at gmail.com> wrote:
> I'm seeing crashes like the one below when I do a 'make -j16
> buildworld' in the current HEAD.  This is without SMP enabled and
> without any of the XLR smp changes.
>
> buildworld used to work on XLR with earlier kernels - the last good
> kernel I have is around r206712.  Any idea what can be causing this?
>
> Thanks,
> JC.
>
> xlrboard#    Mar 18 14:04:43 xlrboard kernel: BAD_PAGE_FAULT: pid
> 12596 (cc), uid 1001: pc 0 got a read fault at 0
> Mar 18 14:04:43 xlrboard kernel: Trapframe Register Dump:
> Mar 18 14:04:43 xlrboard kernel: zero: 0        at: 0x1000a1f4  v0:
> 0x7fffcf28  v1: 0
> Mar 18 14:04:43 xlrboard kernel: a0: 0x7fffd638 a1: 0x470bf8    a2:
> 0x7fffcf28  a3: 0x470c24
> Mar 18 14:04:43 xlrboard kernel: t0: 0  t1: 0x4000000   t2: 0   t3: 0
> Mar 18 14:04:43 xlrboard kernel: t4: 0  t5: 0   t6: 0   t7: 0
> Mar 18 14:04:43 xlrboard kernel: t8: 0  t9: 0   s0: 0x7fffd638  s1: 0
> Mar 18 14:04:43 xlrboard kernel: s2: 0x1b       s3: 0   s4: 0   s5:
> 0x7fffcf31
> Mar 18 14:04:43 xlrboard kernel: s6: 0x471398   s7: 0x3 k0: 0   k1: 0
> Mar 18 14:04:43 xlrboard kernel: gp: 0x1000f630 sp: 0x7fffcec8  s8:
> 0x7fffcf31  ra: 0x43a200
> Mar 18 14:04:43 xlrboard kernel: sr: 0xc013     mullo: 0        mulhi:
> 0        badvaddr: 0
> Mar 18 14:04:43 xlrboard kernel: cause: 0x8     pc: 0
> Mar 18 14:04:43 xlrboard kernel: pc address 0 is inaccessible, pde =
> 0x0, pte = 0x0
> Mar 18 14:04:43 xlrboard kernel: BAD_PAGE_FAULT: pid 12601 (as), uid
> 1001: pc 0x524818 got a read fault at 0x4b90
>
> --
> C. Jayachandran    c.jayachandran at gmail.com
>