Bug 6993 - cvsup (X): Heaps of fatal process exception: page fault,... but seems to work still.
Summary: cvsup (X): Heaps of fatal process exception: page fault,... but seems to work...
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-ports (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 1998-06-19 11:40 UTC by pc
Modified: 1998-07-11 16:30 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description pc 1998-06-19 11:40:02 UTC
Look at this. 

petra:~# cvsup cvsup.petra.src-all.cvs-crypto
(... some lines are missing here ...)
fatal process exception: page fault, fault VA = 0x11a610
fatal process exception: page fault, fault VA = 0x128b38
fatal process exception: page fault, fault VA = 0x11b894
fatal process exception: page fault, fault VA = 0x12d124
fatal process exception: page fault, fault VA = 0x12f008
fatal process exception: page fault, fault VA = 0x145864
fatal process exception: page fault, fault VA = 0x145844
fatal process exception: page fault, fault VA = 0x11b8ac
fatal process exception: page fault, fault VA = 0x1472fc
fatal process exception: page fault, fault VA = 0x1472fc
fatal process exception: page fault, fault VA = 0x127988
fatal process exception: page fault, fault VA = 0x13e884
fatal process exception: page fault, fault VA = 0x17edac
fatal process exception: page fault, fault VA = 0x118110
fatal process exception: page fault, fault VA = 0x1192d0
fatal process exception: page fault, fault VA = 0x10c1a0
fatal process exception: page fault, fault VA = 0x11aa20
fatal process exception: page fault, fault VA = 0x1240bc
fatal process exception: page fault, fault VA = 0x12a3a0
fatal process exception: page fault, fault VA = 0x12a3a0
fatal process exception: page fault, fault VA = 0x1496d0
fatal process exception: page fault, fault VA = 0x1484e8
fatal process exception: page fault, fault VA = 0x125478
fatal process exception: page fault, fault VA = 0x1802a8
fatal process exception: page fault, fault VA = 0x181090
fatal process exception: page fault, fault VA = 0x1822ec
fatal process exception: page fault, fault VA = 0x183150
fatal process exception: page fault, fault VA = 0x184098
fatal process exception: page fault, fault VA = 0x13e5dc
fatal process exception: page fault, fault VA = 0x12784c
fatal process exception: page fault, fault VA = 0x149c84
fatal process exception: page fault, fault VA = 0x12d584
fatal process exception: page fault, fault VA = 0x17eee4
fatal process exception: page fault, fault VA = 0x130694
fatal process exception: page fault, fault VA = 0x148dac
fatal process exception: page fault, fault VA = 0x192d7c
fatal process exception: page fault, fault VA = 0x192dc8
fatal process exception: page fault, fault VA = 0x18ae10
fatal process exception: page fault, fault VA = 0x13d870
fatal process exception: page fault, fault VA = 0x13d9b0
fatal process exception: page fault, fault VA = 0x12a3a0
fatal process exception: page fault, fault VA = 0x12a3a0
fatal process exception: page fault, fault VA = 0x18f558
fatal process exception: page fault, fault VA = 0x18f564
fatal process exception: page fault, fault VA = 0x13b380
fatal process exception: page fault, fault VA = 0x13b380
fatal process exception: page fault, fault VA = 0x11b008
fatal process exception: page fault, fault VA = 0x13c868
fatal process exception: page fault, fault VA = 0x13c86c
fatal process exception: page fault, fault VA = 0x197acc
fatal process exception: page fault, fault VA = 0x1496d4
fatal process exception: page fault, fault VA = 0x18a2b8
fatal process exception: page fault, fault VA = 0x19a144
fatal process exception: page fault, fault VA = 0x18b008
fatal process exception: page fault, fault VA = 0x18b00c
fatal process exception: page fault, fault VA = 0x17ede0
fatal process exception: page fault, fault VA = 0x17ede4
fatal process exception: page fault, fault VA = 0x197a2c
fatal process exception: page fault, fault VA = 0x199bd0
fatal process exception: page fault, fault VA = 0x11b62c
fatal process exception: page fault, fault VA = 0x1472a4
fatal process exception: page fault, fault VA = 0x1472a8
fatal process exception: page fault, fault VA = 0x18c0c0
fatal process exception: page fault, fault VA = 0x18c0c4
fatal process exception: page fault, fault VA = 0x18db38
fatal process exception: page fault, fault VA = 0x18db3c
fatal process exception: page fault, fault VA = 0x19af40
fatal process exception: page fault, fault VA = 0x135db8
fatal process exception: page fault, fault VA = 0x19538c
fatal process exception: page fault, fault VA = 0x19537c
fatal process exception: page fault, fault VA = 0x19e520
fatal process exception: page fault, fault VA = 0x19fdfc
fatal process exception: page fault, fault VA = 0x19fdec
fatal process exception: page fault, fault VA = 0x1a15e0
fatal process exception: page fault, fault VA = 0x1a15d0
fatal process exception: page fault, fault VA = 0x1a0564
fatal process exception: page fault, fault VA = 0x1a20f0
fatal process exception: page fault, fault VA = 0x1a20e0
fatal process exception: page fault, fault VA = 0x1a356c
fatal process exception: page fault, fault VA = 0x1a355c
fatal process exception: page fault, fault VA = 0x11a9c4
fatal process exception: page fault, fault VA = 0x19b018
fatal process exception: page fault, fault VA = 0x19b008
fatal process exception: page fault, fault VA = 0x1a0008
fatal process exception: page fault, fault VA = 0x1a42e4
fatal process exception: page fault, fault VA = 0x1a42d4
fatal process exception: page fault, fault VA = 0x19e5c4
fatal process exception: page fault, fault VA = 0x135cf8
fatal process exception: page fault, fault VA = 0x19ce60
fatal process exception: page fault, fault VA = 0x11d0a4
fatal process exception: page fault, fault VA = 0x11d030
fatal process exception: page fault, fault VA = 0x14cf4c
fatal process exception: page fault, fault VA = 0x2ab5d4
fatal process exception: page fault, fault VA = 0x2abdf8
fatal process exception: page fault, fault VA = 0x2a91cc
fatal process exception: page fault, fault VA = 0x2a91bc
fatal process exception: page fault, fault VA = 0x14cde0
fatal process exception: page fault, fault VA = 0x1a6210
fatal process exception: page fault, fault VA = 0x1a5018
fatal process exception: page fault, fault VA = 0x1a5008
fatal process exception: page fault, fault VA = 0x2a88f4
fatal process exception: page fault, fault VA = 0x2a88e4
fatal process exception: page fault, fault VA = 0x2a7cfc
fatal process exception: page fault, fault VA = 0x2a7cec
fatal process exception: page fault, fault VA = 0x19c08c
fatal process exception: page fault, fault VA = 0x13113c
fatal process exception: page fault, fault VA = 0x131044
fatal process exception: page fault, fault VA = 0x10c140
fatal process exception: page fault, fault VA = 0x10c144
fatal process exception: page fault, fault VA = 0x12d124
fatal process exception: page fault, fault VA = 0x12f008
fatal process exception: page fault, fault VA = 0x12d034
fatal process exception: page fault, fault VA = 0x2a69f0
fatal process exception: page fault, fault VA = 0x2a6988
fatal process exception: page fault, fault VA = 0x2a5874
fatal process exception: page fault, fault VA = 0x2a5864
fatal process exception: page fault, fault VA = 0x2a496c
fatal process exception: page fault, fault VA = 0x2a495c
#

These are the last few lines that I got from the window I started cvsup
from (with X, but without I recall the same thing). No syslog, no way
to cvsup ...blah... > file 2>&1, just cut 'n paste.

When I start the update, the window gets literally flooded with these
messages.

This effect I noticed from when I started cvsup-dating from 2.2.5-RELEASE,
so I felt quite safe to ignore it, also since cvsup-dating seems to work
fine.

There's another machine that I have access to runnting 2.2.5-RELEASE, and
no reports of such faults whatsoever. But I don't dare updating it because
of some other problems I had on my 'petra'.

Fix: 

I have no idea.
How-To-Repeat: 
Well, calling cvsup <cvsup-file> starts the flood here...
Comment 1 pc 1998-06-19 11:49:32 UTC
Please also have a look at my prs kern/6991, misc/6992, ports/6993. They
might be related.

Thanks for your attention,                                                      

Peter.                    

---
Peter Cornelius <pc@akk.uni-karlsruhe.de>
Comment 2 jkh freebsd_committer freebsd_triage 1998-06-19 15:53:32 UTC
State Changed
From-To: open->closed

I think this is related to your hardware problems; cannot reproduce. 

Comment 3 brett 1998-06-19 17:24:42 UTC
> petra:~# cvsup -v
> CVSup client
> Software version: REL_15_2
^^^^^^^^^^^^^^^^^^^^^^^^^^^^

You MUST use 15.4 now.  Upgrade CVSUP and see the mail list archives for
John Polstra's explanation.

Brett
*********************************************************
Brett Taylor 		brett@peloton.physics.montana.edu
http://peloton.physics.montana.edu/brett/
Comment 4 John Polstra 1998-07-02 16:14:48 UTC
This PR was closed for the wrong reason.  The reported problem was
caused by the kernel being built with the undocumented option
"options DEBUG" in the config file.  Don't do that.
--
   John Polstra                                       jdp@polstra.com
   John D. Polstra & Co., Inc.                Seattle, Washington USA
   "Self-knowledge is always bad news."                 -- John Barth
Comment 5 pc 1998-07-11 16:17:11 UTC
Thank you for the response and please excuse the late reply. I had to
recover from a little bit of a breakdown 8-S

On Fri, Jun 19, 1998 at 10:24:42AM -0600, Brett Taylor wrote:

> You MUST use 15.4 now.  Upgrade CVSUP and see the mail list archives for
> John Polstra's explanation.

Thanks for the hint, I upgraded, but the messages did not go away. But I
received a note from John Polstra about which kernel option to switch off
to quiet a bit the kernel :)

Thanks again,

best regards,

Peter.

---
Peter Cornelius <pc@akk.uni-karlsruhe.de>
Comment 6 pc 1998-07-11 16:25:30 UTC
Re...

Thanks for the reply!

On Thu, Jul 02, 1998 at 08:20:56AM -0700, John Polstra wrote:

> Oops, I should have said "options DEBUG".  I've added this to the
> CVSup FAQ at <http://www.polstra.com/projects/freeware/CVSup/faq.html>.

Ooops... why did this creep in... Ah, yes. I am trying to get going a
scanner. Weird bugger, no success yet (relisys avec color 2400). That's
why I wanted the kernel to be _really_ verbose... I promise never ever to
forget that again... )8-S But with my ram problems I suspected something
quite different...

Thanks again,

Best regards,

Peter.

---
Peter Cornelius <pc@akk.uni-karlsruhe.de>