Re: [PATCH] [RFC] fix kernel crash (protection id trap) when compiling

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Dec 17, 2008 at 07:05:26PM -0500, John David Anglin wrote:
> > r20-23  8210c000 00000000 0020fd0e 8210c39e
> > r24-27  00000000 00000001 8e7c5660 105e7a90
> > r28-31  0000000f 00190834 8210c500 101a12b8
> > sr00-03  00000000 00000000 00000000 00000847
> > sr04-07  00000000 00000000 00000000 00000000
> > 
> > IASQ: 00000000 00000000 IAOQ: 101a147c 101a1480
> >  IIR: 0ed5d240    ISR: 00000847  IOR: 0020fd0e
> >  CPU:        0   CR30: 8210c000 CR31: d22344f0
> >  ORIG_R28: 00001000
> >  IAOQ[0]: do_sys_poll+0x1ac/0x1b8
> >  IAOQ[1]: do_sys_poll+0x1b0/0x1b8
> >  RP(r2): do_sys_poll+0x14c/0x1b8
> 
> The faulting instruction is:
> 
> dave@hiauly6:~/opt/gnu/bin$ disasm 0x0ed5d240
>    0:	0e d5 d2 40 	sth r21,0(sr3,r22)
> 
> r22 is 0.  r22 being 0 is a bit wierd as revents has on offset of 6.
> 

Eh? r22 is 0020fd0e... although it's easier to spot by looking at IOR
> >  IIR: 0ed5d240    ISR: 00000847  IOR: 0020fd0e

Weird.

Although, I don't think we're supposed to ever be taking a P. Id trap on
a userspace process as the kernel...
--
To unsubscribe from this list: send the line "unsubscribe linux-parisc" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux SoC]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux