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

Re: Problems with 2.2.19

In message <E14uhms-0000Jc-00@kings-cross.london.uk.eu.org> you wrote:

> >4 gives the following 'system dump' (is this the correct linux name?)
> >Unable to handle kernel paging request at virtual address ef9f0030
> >pgd=c1e70000
> >*pgd=00000000, *pmd=00000000
> >Internal error: Oops 2
> Well, this is quite bad.  Can you capture the full message (including the 
> register and stack information) and send it to me?
I have attached the dump file. Mind you although I have checked the file
carefully I had to type it all in, thus there could be one (or two) typo's.
> >My system is a RISC PC with 48MB RAM, 2 MB VRAM and has an StrongArm with the
> >STM bug (this seemed to be important for netbsd-arm32, is this also important
> >for linux?).
> Remind me which is the `STM' bug again? 
Up to a certain revision of the StrongArm (I think k) there was a bug 
regarding the STM opcode. In short: if you stored multiple registers with 
STM and you happened to go over a page boundery wich was not in memory, this
would give  page error. netbsd would then load the page from the swap into
memory and the write could continue. However the STM opcode would not
continue with the not saved registers but would start all over again, but did
this to the wrong address.

This might not be discribed exactly but I hope you get the picture.

Thanks for your help


Leo Smiers
System specialist FB/SP             bv Nederland Haarlem
!PDF 0.73a | !Flash        http://members.ams.chello.nl/l.smiers
Unable to handle kernel paging request at virtual address ef9f0030
pgd = c1fd0000
*pgd=00000000, *pmd=00000000
Internal error: Oops: 2
CPU: 0
pc : [<c00536dc>]    lr : [<c004d16c>]
sp : c1fdf53c  ip : c1f8d000  fp : 00000000
r10: c01b02c8  r9 : 64a2962c  r8 : c1fd5f6c
r7 : 00000008  r6 : c283f800  r5 : ef9f0000  r4 : ef9effe8
r3 : 00000000  r2 : 00001fff  r1 : c01084ec  r0 : c01b0000
Flags: nzCv  IRQs on  FIQs on  Mode SVC_32  Segment user
Control: 18FD117F  Table: 18FD117F  DAC: 00000015
Process find (pid: 206, stackpage=c1fd5000)
c1fd5f20:                            c004d16c  c00536dc 20000013 ffffffff c1f8d000
c1fd5f40: c1fd5f6c 00000000 c283f800 00000000  c1f8d008 00000400 00000000 c004d16c
c1fd5f60: c1fd5f6c 00000000 c004d5d4 c1f8d000  00000008 64a2962c c1f8d000 c1f8d000
c1fd5f80: 00000000 c1fd4000 c1fd5ff4 02016ab0  c004d6e8 00000000 c001c3c8 bffffa20
c1fd5fa0: c004add8 00000000 c001c3c8 0000006b  c001c220 00000000 02016ebe bffffa20
c1fd5fc0: bffffa9c 02016ebe 00000000 02016eb8  00000003 bffffa9c 02016ebe 00000400
c1fd5fe0: 02016ab0 bffffa80 bffffa84 bffffa20  0200d584 400aba2c 20000010 02016ebe
Backtrace: no frame pointer
Code: e58d3000 0a00002b (e5943048) e5955000 e1530009
Segmentation fault

Reply to: