[prev in list] [next in list] [prev in thread] [next in thread] 

List:       axp-redhat
Subject:    Anything known about broken coredumps?
From:       bert hubert <ahu () vvtp ! tn ! tudelft ! nl>
Date:       1997-04-30 0:47:15
[Download RAW message or body]


My AlphaStation 200 4/233 (96MB Ram. 2.1.24 & 2.0.27) dumps core when 
compiling joe, as found on ftp.std.com. This in itself isn't as it should 
be, but I can live with it.

However, after gcc 2.7.2 dumps core, the kernel does one of several things:

Apr 30 00:40:02 feynman kernel: Unable to handle kernel paging request at 
virtua
l address 00000000000000fc
Apr 30 00:40:02 feynman kernel: cc1(1569): Oops 0
Apr 30 00:40:02 feynman kernel: pc = [<fffffc00003481c0>] ps = 0000
Apr 30 00:40:02 feynman kernel: rp = [<fffffc0000348150>] ra = 
[<fffffc000034fc9
8>]
Apr 30 00:40:02 feynman kernel: r0 = 0000000000000000  r1 = fffffc000297b662
Apr 30 00:40:02 feynman kernel: r2 = 0000000000000000  r3 = 0000000000010000
Apr 30 00:40:02 feynman kernel: r4 = fffffc000297b668  r5 = 0000000000000800
Apr 30 00:40:02 feynman kernel: r6 = fffffc0000441130  r7 = 0000000000000007
Apr 30 00:40:02 feynman kernel: r8 = 0000000000001c2e  r9 = 0000000000000000
Apr 30 00:40:02 feynman kernel: r10= 0000000000000602  r11= 0000000000008180
Apr 30 00:40:02 feynman kernel: r12= fffffc000557ba88  r13= 000000000000000d
Apr 30 00:40:02 feynman kernel: r14= 0000000000000004  r15= fffffc00004a3e98
Apr 30 00:40:02 feynman kernel: r16= fffffc000297b570  r17= 0000000000000002
Apr 30 00:40:02 feynman kernel: r18= 0000000000000602  r19= 0000000000008180
Apr 30 00:40:02 feynman kernel: r20= fffffc000557b628  r21= 0000000000800000
Apr 30 00:40:02 feynman kernel: r22= 0000000001f12000  r23= 0000000000000001
Apr 30 00:40:02 feynman kernel: r24= 000000000307a000  r25= 000006f800000004
Apr 30 00:40:02 feynman kernel: r27= 00000000000000ff  r28= fffffc0000000000
Apr 30 00:40:02 feynman kernel: gp = fffffc0000460598  sp = fffffc000557b5e0
Apr 30 00:40:02 feynman kernel: Code: e7600007  a77b0028  e7600005 
<a77b0000> 22
3fffff  
6b5b4000  
27ba0012  
23bd83cc  
a61e0048                                                                                   

If I disable coredumping, nothing goes wrong. However, sometimes it used 
to say VFS unkown device 0:0, or VFS trying to free free inode, of unable 
to get VMA of (something or another).

However, I've noticed that the system sometimes uses 128K of swap during 
this process, which is odd on an 96MB computer idling. The problem 
doesn't go away if I disable swap, and also occurs when running on a 
DOS-format partition.

It occurs both on 2.0.27 and 2.1.24! So I'm pretty much out of clues as 
to what happened. 

Any ideas?

--
To unsubscribe: send e-mail to axp-list-request@redhat.com with
'unsubscribe' as the subject.  Do not send it to axp-list@redhat.com

[prev in list] [next in list] [prev in thread] [next in thread]