Lockup

Lockup

Post by Daniel Rud » Mon, 26 Feb 2001 11:23:07



Hello,

Here is something weird.  When I try and do a make build world, the
system locks up after awhile during the build.  I then have to hit the
reset button to recover the system.  There are no error messages or
anything.  Anyone have any ideas as to what possiable cause to this
problem is?
--
Daniel Rudy

Remove "0123456789." and ".invalid" to reply.
Please reply to dcrudy at aol dot com.

 
 
 

Lockup

Post by Steven G. Kar » Mon, 26 Feb 2001 13:13:31




Quote:> Hello,

> Here is something weird.  When I try and do a make build world, the
> system locks up after awhile during the build.  I then have to hit the
> reset button to recover the system.  There are no error messages or
> anything.  Anyone have any ideas as to what possiable cause to this
> problem is?

What version of FreeBSD is running?
What version of FreeBSD are you trying to build?
Are you doing a "make buildworld" on a heavily loaded system
or a rather idle system?

If it dies during a buildworld, try updating our sources.

Do "cd /usrc/src; make cleandir && make cleandir"

--
steve

 
 
 

Lockup

Post by Daniel Rud » Mon, 26 Feb 2001 15:17:57





> > Hello,

> > Here is something weird.  When I try and do a make build world, the
> > system locks up after awhile during the build.  I then have to hit the
> > reset button to recover the system.  There are no error messages or
> > anything.  Anyone have any ideas as to what possiable cause to this
> > problem is?

> What version of FreeBSD is running?
> What version of FreeBSD are you trying to build?
> Are you doing a "make buildworld" on a heavily loaded system
> or a rather idle system?

> If it dies during a buildworld, try updating our sources.

> Do "cd /usrc/src; make cleandir && make cleandir"

> --
> steve

I'm updating a 4.2-STABLE to 4.2-STABLE.  Thing is it just dies during
the buildworld.  This time it finished without any problems.  A number
of warnings, but that's it.
--
Daniel Rudy

Remove "0123456789." and ".invalid" to reply.
Please reply to dcrudy at aol dot com.

 
 
 

Lockup

Post by Steven G. Kar » Tue, 27 Feb 2001 01:58:40




Quote:> I'm updating a 4.2-STABLE to 4.2-STABLE.  Thing is it just dies during
> the buildworld.  This time it finished without any problems.  A number
> of warnings, but that's it.

If you get a Signal 11, then this normally means you have a
hardware problem: marginal memory, memory or cpu
is too hot, or you're overclocking.

The other problem that can occur is that you updated your
source while a change was being made to the source tree.
You sometime get only half of the changed files.  This is
why I recommend to update the sources again.  Also, the
"make cleandir && make cleandir" really cleans out possibly
rogue .depend and *.o files.

--
steve

 
 
 

Lockup

Post by Daniel Rud » Tue, 27 Feb 2001 12:24:26





> > I'm updating a 4.2-STABLE to 4.2-STABLE.  Thing is it just dies during
> > the buildworld.  This time it finished without any problems.  A number
> > of warnings, but that's it.

> If you get a Signal 11, then this normally means you have a
> hardware problem: marginal memory, memory or cpu
> is too hot, or you're overclocking.

> The other problem that can occur is that you updated your
> source while a change was being made to the source tree.
> You sometime get only half of the changed files.  This is
> why I recommend to update the sources again.  Also, the
> "make cleandir && make cleandir" really cleans out possibly
> rogue .depend and *.o files.

> --
> steve

I will keep your advise in mind when I do the next update.  I was
begining to think it was some kind of hardware problem.  The build
machine is an old K6-2/333 with 128MB Ram which is more than 2 years
old.
--
Daniel Rudy

Remove "0123456789." and ".invalid" to reply.
Please reply to dcrudy at aol dot com.

 
 
 

Lockup

Post by RaRa Rasput » Tue, 27 Feb 2001 19:46:02


In the last exciting episode of comp.unix.bsd.freebsd.misc,
Daniel Rudy said:




>> > Hello,

>> > Here is something weird.  When I try and do a make build world, the
>> > system locks up after awhile during the build.  I then have to hit the
>> > reset button to recover the system.  There are no error messages or
>> > anything.  Anyone have any ideas as to what possiable cause to this
>> > problem is?

>> What version of FreeBSD are you trying to build?
>> Are you doing a "make buildworld" on a heavily loaded system
>> or a rather idle system?

>> If it dies during a buildworld, try updating our sources.

>> Do "cd /usrc/src; make cleandir && make cleandir"

Or re-cvsup.

Quote:>I'm updating a 4.2-STABLE to 4.2-STABLE.  Thing is it just dies during
>the buildworld.  This time it finished without any problems.  A number
>of warnings, but that's it.

If it fails in the same place every time, it's possibly dodgy CVS source.
If it fails randomly (as my old P133 started doing last week)
something is on the way out (CPU/RAM/mobo).

I found turning off -j4 in the buildworld let me get away with it, but
I know this system's days are numbered now...

--
Rasputin
Jack of All Trades :: Master of Nuns

 
 
 

1. Kernel 2.2.21 aic7xxx lockup or kernel lockup

Hello,

**** Please BCC me in on any reply, not CC me.
Two reasons, I am not on the Mailing List,
and second I am suffering BIG time with SPAM
from posting to mailing lists/Newsgroups.
Instructions on real address at bottom.
Thanks in advance. *****

Could somone advise me what I need to do to obtain the details of a
aic7xxx module lockup that happens when using insmod?  I am not sure
what would be helpful data to report here and assist in determining
what is the problem, beyond the obvious system details?

I am now using kernel 2.2.21, and it is a tad better in terms of not
locking up the kernel hard in the different device connected
conditions.  The lockup does not always occur, much depends on if
something is connected to the 2930 or not.  In all cases with a device
connected a hard kernel lockup or module load lockup occur.  In the
latter I can ctrl-c or close the xterm to kill the load.  I tried an
strace but this appears not to provide any detail, at least in my
limited knowledge of the kernel and my techncial read of the strace
data.

The 2930 has no problem with seeing the devices.  The devices work
just fine as I changed to a BusLogic 930 and both scanner and CDWriter
work just fine.  The primary SCSI is a Buslogic 958 that the hard
drives boot off.  I was using the 2930 for external and slow devices.
The 958 remained in, I just swapped the 2930 for the 930.  The
buslogic.o is loaded at boot time from the Initial RAM disk, and there
is no compiled in SCSI driver support, all are modules.

I really appreciate if you bcc me in on your reply so I can avoid the
big SPAM problems that have been snowballing me lately.

Regards,

John L. Males
Willowdale, Ontario
Canada
29 June 2002 16:04

==================================================================

"Boooomer ... Boom Boom, how are you Boom Boom" Boomer 1985 -
February/2000

***** Please BCC me in on any reply, not CC me.
Two reasons, I am not on the Mailing List,
and second I am suffering BIG time with SPAM
from posting to mailing lists/Newsgroups.
Instructions on real address at bottom.
Thanks in advance. *****


TLD =         The last three letters of the word "internet"
Domain name = The first four letters of the word "software",
              followed by the first four letters of the word
              "homeless".
My appologies in advance for the jumbled eMail address
and request to BCC me, but SPAM has become a very serious
problem.  The eMail address in my header information is
not a valid eMail address for me.  I needed to use a valid
domain due to ISP SMTP screen rules.

  application_pgp-signature_part
< 1K Download

2. eth0 fatal error

3. Kernel lockups on dual-Athlon board -- help wanted

4. How to connect Linux and Windows 95 ?

5. Lockups

6. Solaris 2.4 x86 as Email Server?

7. Gnome mouse & keyboard lockup

8. Where is $PATH set in RH 6.0?

9. IDE lockups with 2.5.28...

10. TAR Lockups Machine

11. keyboard lockup installing redhat 6.0

12. block/IDE/interrupt lockup

13. Screen lockup when Gnome system sounds activated under Mandrake Linux 6