Re: sshd triggers Protection id trap

On 1/15/07, Thibaut VARENE <[email protected]> wrote:
> I got one of those traps again today trying to boot git head on my rp3440:
>
> Configuring network interfaces...done.
>       _______________________________
>      < Your System ate a SPARC! Gah! >
>       -------------------------------
>              \   ^__^
>               \  (xx)\_______
>                  (__)\       )\/\
>                   U  ||----w |
>                      ||     ||
> sh (pid 625): Protection id trap (code 27)
>
>      YZrvWESTHLNXBCVMcbcbcbcbOGFRQPDI
> PSW: 00001000000001001111001100001111 Not tainted
> r00-03  000000ff0804f30f 000000004060a340 0000000000000068 00000000fb199c10
> r04-07  00000000405fd340 000000007eb24190 00000000000ded34 00000000000ded34
> r08-11  0000000000000000 00000000000f2508 0000000000000000 0000000000000008
> r12-15  0000000000000000 0000000000000000 00000000000f1f28 0000000000000001
> r16-19  00000000000dd534 00000000000ad800 00000000000efa18 0000000000000000
> r20-23  0000000000000000 0000000000000803 0000000000000000 000000007eb242b0
> r24-27  0000000000000068 00000000fb199c10 000000000000001f 00000000405fd340
> r28-31  0000000044c4f7c5 000000007eb242a0 000000007eb24480 00000000fb199c10
> sr00-03  00000000002b2800 0000000000000000 00000000002b2800 00000000002b2800
> sr04-07  0000000000000000 0000000000000000 0000000000000000 0000000000000000
>
> IASQ: 0000000000000000 0000000000000000 IAOQ: 00000000402e62b0 00000000402e62b4
>  IIR: 0f3692a8    ISR: 00000000002b2800  IOR: 00000000fb199c10
>  CPU:        0   CR30: 000000007eb24000 CR31: 00000000405b4000
>  ORIG_R28: 00000000405fd340
>  IAOQ[0]: pa_memcpy+0x78/0x2b0
>  IAOQ[1]: pa_memcpy+0x7c/0x2b0
>  RP(r2): 0x68
> Backtrace:
>
> /etc/init.d/rc: line 77:   625 Segmentation fault      $@
> Initializing random number generator...done.
> tg3: eth0: Link is up at 1000 Mbps, full duplex.
> tg3: eth0: Flow control is off for TX and off for RX.
>
> That seems to have killed the boot process, I didn't get a login prompt

I don't know if that's related but it seems that 1 out of 2 boot
attempts the kernel doesn't get past the startup of INIT and freezes
there. I don't think this is my 'ldap' bug because this box is
properly configured to avoid it. Something else is happening I
suppose....

HTH

-- 
Thibaut VARENE
http://www.parisc-linux.org/~varenet/