Re: Solved: CURRENT and P-IV problems

2002-08-21 Thread Don Lewis
On 21 Aug, Don Lewis wrote: > On 21 Aug, Martin Blapp wrote: >> >> Hi, >> >> Try to compile the entire system on another box, install it then >> on the CURRENT target box, and try again ! >> >> Bye the way, after 6 rounds, I see now SIG4 and SIG11 too :-/ >> To bad - so it's definitly data corr

Re: Solved: CURRENT and P-IV problems

2002-08-21 Thread Don Lewis
On 21 Aug, Martin Blapp wrote: > > Hi, > > Try to compile the entire system on another box, install it then > on the CURRENT target box, and try again ! > > Bye the way, after 6 rounds, I see now SIG4 and SIG11 too :-/ > To bad - so it's definitly data corruption in CURRENT. > > Asus Board P4B

Re: Solved: CURRENT and P-IV problems

2002-08-21 Thread KT Sin
Hi Please try to continue from where it broke by repeating make. Otherwise, please get a precompiled port package. kt On Wed, Aug 21, 2002 at 10:26:37PM +0200, Mark Santcroos wrote: > On Wed, Aug 21, 2002 at 08:05:17PM +0200, Mark Santcroos wrote: > > On Wed, Aug 21, 2002 at 11:38:20PM +0800,

Re: Solved: CURRENT and P-IV problems

2002-08-21 Thread Martin Blapp
Hi, Try to compile the entire system on another box, install it then on the CURRENT target box, and try again ! Bye the way, after 6 rounds, I see now SIG4 and SIG11 too :-/ To bad - so it's definitly data corruption in CURRENT. Asus Board P4B533-V, P-IV 2,26Ghz, 1GB DDR 2100 Ram. Martin Mar

Re: Solved: CURRENT and P-IV problems

2002-08-21 Thread Mark Santcroos
On Wed, Aug 21, 2002 at 08:05:17PM +0200, Mark Santcroos wrote: > On Wed, Aug 21, 2002 at 11:38:20PM +0800, KT Sin wrote: > > Hi > > > > I believe this is caused by the pre-released version of gcc in the system. > > > > I started seeing this problem one week after I upgraded my hardware to > >

Re: Solved: CURRENT and P-IV problems

2002-08-21 Thread Mark Santcroos
On Wed, Aug 21, 2002 at 11:38:20PM +0800, KT Sin wrote: > Hi > > I believe this is caused by the pre-released version of gcc in the system. > > I started seeing this problem one week after I upgraded my hardware to > Pentium 4 in May. Two weeks ago, I built the final release version of > gcc 3.

Re: Solved: CURRENT and P-IV problems

2002-08-21 Thread Alexander Leidinger
On Wed, 21 Aug 2002 14:48:38 +0200 (CEST) Martin Blapp <[EMAIL PROTECTED]> wrote: > As reported, Brian and I did see SIG4 and SIG11 during make > buildworlds. > > I've replaced everything, two - three times, the problem persisted. > I also tried three motherboards, but all from the same type: >

Re: Solved: CURRENT and P-IV problems

2002-08-21 Thread KT Sin
Hi I believe this is caused by the pre-released version of gcc in the system. I started seeing this problem one week after I upgraded my hardware to Pentium 4 in May. Two weeks ago, I built the final release version of gcc 3.1.1 in the ports and used that to compile the kernel and userlands. A

Re: Solved: CURRENT and P-IV problems

2002-08-21 Thread Martin Blapp
Hi, > > The 2nd one fails at exactly the same point, that can't be coindedence. > > Also with a signal 10. (libutil) > > > > The 3rd ended somewhere else(games/rogue), but now with signal 4. > > > > Doing the 4rd now. > > Which ends with signal 11 in usr.sbin/devinfo/ ... > > Mark May this be t

Re: Solved: CURRENT and P-IV problems

2002-08-21 Thread Mark Santcroos
On Wed, Aug 21, 2002 at 04:45:54PM +0200, Mark Santcroos wrote: > > > Can you try that ? > > > > Eek! First one already bailed out! Talking about bad luck! > > Signal 10 this time. > > The 2nd one fails at exactly the same point, that can't be coindedence. > Also with a signal 10. (libutil) > >

Re: Solved: CURRENT and P-IV problems

2002-08-21 Thread Mark Santcroos
On Wed, Aug 21, 2002 at 04:07:14PM +0200, Mark Santcroos wrote: > On Wed, Aug 21, 2002 at 03:32:44PM +0200, Martin Blapp wrote: > > > I have a P4 mobile in my laptop and also had this behaviour for a certain > > > -current window last week (the time I got the laptop). (Dell C640) > > > Now it is

Re: Solved: CURRENT and P-IV problems

2002-08-21 Thread Mark Santcroos
On Wed, Aug 21, 2002 at 03:32:44PM +0200, Martin Blapp wrote: > > I have a P4 mobile in my laptop and also had this behaviour for a certain > > -current window last week (the time I got the laptop). (Dell C640) > > Now it is gone. I'm sorry, I don't have an exact date/commit. > > Try to do some

Re: Solved: CURRENT and P-IV problems

2002-08-21 Thread Martin Blapp
Hi, > I have a P4 mobile in my laptop and also had this behaviour for a certain > -current window last week (the time I got the laptop). (Dell C640) > Now it is gone. I'm sorry, I don't have an exact date/commit. Try to do some worlds in a row (5-10) and you will see if it survives. The probl

Re: Solved: CURRENT and P-IV problems

2002-08-21 Thread Mark Santcroos
On Wed, Aug 21, 2002 at 02:48:38PM +0200, Martin Blapp wrote: > > Hi, > > As reported, Brian and I did see SIG4 and SIG11 during make buildworlds. > > I've replaced everything, two - three times, the problem persisted. > I also tried three motherboards, but all from the same type: > > Intel BD

Solved: CURRENT and P-IV problems

2002-08-21 Thread Martin Blapp
Hi, As reported, Brian and I did see SIG4 and SIG11 during make buildworlds. I've replaced everything, two - three times, the problem persisted. I also tried three motherboards, but all from the same type: Intel BD843BG with DDR 266 Ram (2100). Just for interest, I've replaced this Mobo now w