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
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
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,
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
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
> >
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.
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:
>
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
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
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)
>
>
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
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
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
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
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
Hi all,
I can tell now for sure, that all SIG11 and SIG4 problems are
gone with make buildworld, if I compile here
make(8)
rm(8)
mkdir(8)
with -g -ggdb
If I don't do that, make world stops after 4 - 30 seconds. So it
could be definitly some optimizing bug in our gcc. And this bug
seems to be
Martin Blapp wrote:
> Now rm(1) and make(1) coredump with sig 10. So I thought it
> would be a good idea to recompile them with -g -ggdb and
> retry.
>
> Now the strange part. The coredumps are gone. Ok, I did not
> use -pipe then. I'll will now try to use -pipe and -g and -ggdb
> all together.
>
Hi,
I see here now very strange effects. I've upgraded to the
newest CURRENT yesterday, installed on the PIV machine
over NFS.
Now rm(1) and make(1) coredump with sig 10. So I thought it
would be a good idea to recompile them with -g -ggdb and
retry.
Now the strange part. The coredumps are gon
> On Sat, May 04, 2002 at 09:26:33PM +0100, Brian Somers wrote:
> > Try disabling -pipe when building the compiler. This seems to make
> > things more stable here (CFLAGS=-O in /etc/make.conf) - as if
> > building the kernel with -pipe sometimes produces a kernel that
> > subsequently murders
Hi,
I have to take back that a kernel from april 3. runs fine.
It happens there too, but few times than on recent current.
The build lives for 5 minutes, instead of 30 seconds. Then
I get a SIG4 as usual and cc crashes.
Anybody has a idea to which date I can switch back to
have my problem solv
Hi all,
The problem must have been introduced after April, 3.
I've a kernel.old from this date which runs perfectly.
Maybe this can help to track the bug down.
Martin
Martin Blapp, <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
--
ImproW
On Sat, May 04, 2002 at 21:54:08 +0200, Martin Blapp wrote:
> Hi all,
>
> I experiment very strange problems here at the moment with
> a new server.
>
> Buildworld survives about 30 secondy, the errors are SIG4 (90%)
> and SIG11 (10%). And I cannot compile any important programs :-/
>
> I've ex
On Sun, 5 May 2002, Bruce Evans wrote:
> On Sat, 4 May 2002, Jake Burkholder wrote:
>
> > Apparently, On Sun, May 05, 2002 at 10:44:44AM +1000,
> > Bruce Evans said words to the effect of;
> > >
> > > I have seen signs of a generic pipe bug in vi: vi's i/o buffer for
> > > pipes is sometimes
On Sat, 4 May 2002, Jake Burkholder wrote:
> Apparently, On Sun, May 05, 2002 at 10:44:44AM +1000,
> Bruce Evans said words to the effect of;
> >
> > I have seen signs of a generic pipe bug in vi: vi's i/o buffer for
> > pipes is sometimes invalid (kern/sys_pipe.c:pipe_build_write_buffer()
Apparently, On Sun, May 05, 2002 at 10:44:44AM +1000,
Bruce Evans said words to the effect of;
> On Sat, 4 May 2002, David O'Brien wrote:
>
> > On Sat, May 04, 2002 at 09:26:33PM +0100, Brian Somers wrote:
> > > Try disabling -pipe when building the compiler. This seems to make
> > > th
On Sat, 4 May 2002, David O'Brien wrote:
> On Sat, May 04, 2002 at 09:26:33PM +0100, Brian Somers wrote:
> > Try disabling -pipe when building the compiler. This seems to make
> > things more stable here (CFLAGS=-O in /etc/make.conf) - as if
> > building the kernel with -pipe sometimes produces
On Sat, May 04, 2002 at 09:26:33PM +0100, Brian Somers wrote:
> Try disabling -pipe when building the compiler. This seems to make
> things more stable here (CFLAGS=-O in /etc/make.conf) - as if
> building the kernel with -pipe sometimes produces a kernel that
> subsequently murders the compil
On Sat, 2002-05-04 at 13:54, Martin Blapp wrote:
>
> Hi all,
>
> I experiment very strange problems here at the moment with
> a new server.
>
> Buildworld survives about 30 secondy, the errors are SIG4 (90%)
> and SIG11 (10%). And I cannot compile any important programs :-/
>
> I've exchanged
Hi,
Try disabling -pipe when building the compiler. This seems to make
things more stable here (CFLAGS=-O in /etc/make.conf) - as if
building the kernel with -pipe sometimes produces a kernel that
subsequently murders the compiler with sig11/sig4 all the time.
This is just marginally more th
I can tell now for sure that it happens on CURRENT only.
I replaced the disk with a STABLE one, same model, and have
completed a make buildworld -j 20 sucessfully.
The CURRENT disk (in this case SCSI, but it happens also on ATA
dumps core a buildworld after 10 - 30 seconds.
Martin
Martin Blap
Hi all,
I experiment very strange problems here at the moment with
a new server.
Buildworld survives about 30 secondy, the errors are SIG4 (90%)
and SIG11 (10%). And I cannot compile any important programs :-/
I've exchanged all relevant parts:
- Power Supply: 300W, for PIV with additional CP
31 matches
Mail list logo
