RE: Semi-frequent lock-ups (unrealated)

2000-04-28 Thread Christian Pernegger
 -Original Message-
 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of chris horn.
 Sent: Wednesday, April 26, 2000 2:42 PM
 To: debian-user@lists.debian.org
 Subject: Semi-frequent lock-ups


 Hi. I'm running wiht packages from the newest update of Slink off the
ftp.cs.unm.edu/mirrors/debian
 Debian2.1r5 site, with kernel 2.2.14 #4 SMP ...

I've always wondered: What does the #4 (#1 on my box) mean?

Christian


RE: Semi-frequent lock-ups (unrealated)

2000-04-28 Thread Curtis Hogg
The # after 2.2.14 indicates what build of the kernel you're running...
namely, if you recompile your kernel, this number will increase.

Mine's at #17 =)

-- Curtis Hogg

Email 1 - [EMAIL PROTECTED]
Email 2 - [EMAIL PROTECTED]
WWW - http://www.cyberhighway.net/~buckmins
--

UNIX Trix

For those of you in the reseller business, here is a helpful tip that will
save your support staff a few hours of precious time.  Before you send your
next machine out to an untrained client, change the permissions on /etc/passwd
to 666 and make sure there is a copy somewhere on the disk.  Now when they
forget the root password, you can easily login as an ordinary user and correct
the damage.  Having a bootable tape (for larger machines) is not a bad idea
either.  If you need some help, give us a call.
-- CommUNIXque 1:1, ASCAR Business Systems
--

On Fri, 28 Apr 2000, Christian Pernegger wrote:

  -Original Message-
  From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of chris horn.
  Sent: Wednesday, April 26, 2000 2:42 PM
  To: debian-user@lists.debian.org
  Subject: Semi-frequent lock-ups
 
 
  Hi. I'm running wiht packages from the newest update of Slink off the
 ftp.cs.unm.edu/mirrors/debian
  Debian2.1r5 site, with kernel 2.2.14 #4 SMP ...
 
 I've always wondered: What does the #4 (#1 on my box) mean?
 
 Christian
 
 
 -- 
 Unsubscribe?  mail -s unsubscribe [EMAIL PROTECTED]  /dev/null
 


Re: Semi-frequent lock-ups

2000-04-26 Thread Paul Check
I have also had lock-ups from time to time.  The non-hard lock-up
I get is with Netscape...sometimes it runs out of control
and hogs CPU and freezes up.  I can kill it, so not too
big a deal.  At times I'll get a hard lock-up and forced re-boot.
I think these events may be related (ie. I'm having the Netscape
problem at the same time as I'm doing something else on the
desktop and the hard lock-up occurs -- this is conjecture).

It seems that the Netscape freezes are Java related.  Any takers
on this one?

Cheers, Paul


Re: Semi-frequent lock-ups

2000-04-26 Thread Oswald Buddenhagen
 I get is with Netscape...
 It seems that the Netscape freezes are Java related.
 
nothing new ... :-(

-- 
Hi! I'm a .signature virus! Copy me into your ~/.signature, please!
--
Linux - the last service pack you'll ever need.


Re: Semi-frequent lock-ups

2000-04-26 Thread Chris Gray
On Wed, Apr 26, 2000 at 08:42:09AM -0400, chris horn. wrote:
 Hi. I'm running wiht packages from the newest update of Slink off the
 ftp.cs.unm.edu/mirrors/debian Debian2.1r5 site, with kernel 2.2.14 #4
 SMP Sun Feb 6 12:02:09 EST 2000 i686
 
 I've been getting hard lockups lately, and want to know how to track
 them down.

I had hard lockups like you describe that were heat related.  This was
on an overclocked machine (my parents') which would lock when I was home
on summer vacation but not for Christmas break.  

So make sure that your CPU is getting the proper cooling, and if you are
overclocking, I guess it's just kind of something you have to live with.

Cheers,
Chris Gray

-- 
pick, pack, pock, puck: like drops of water in a fountain falling
softly in the brimming bowl.


Re: Semi-frequent lock-ups

2000-04-26 Thread chris horn.
 I had hard lockups like you describe that were heat related.  This was
 on an overclocked machine (my parents') which would lock when I was home
 on summer vacation but not for Christmas break.  
 
 So make sure that your CPU is getting the proper cooling, and if you are
 overclocking, I guess it's just kind of something you have to live with.

Yeah, good thought. I actually have that under control - plenty of filtered
circulation, and a temperature readout (courtesy of LMsensors w/ Procmeter3) of
/rarely/ higher than 42.0C.


cheers.
chris.

-

26-Apr-00 - 10:46:26


Re: Semi-frequent lock-ups

2000-04-26 Thread Paul Check
Is there a Debian package that displays the temp?  Maybe I should keep
my eye on that too.  

I thought I had heard of the Netscape/Java freeze problem
before.  Any ideas on fix and/or where the problem
is coming from?  I think I'm now having the same
problem while running Star Office too.

Cheers, Paul


Re: Semi-frequent lock-ups

2000-04-26 Thread chris horn.
 Is there a Debian package that displays the temp?  Maybe I should keep
 my eye on that too.  

I don't know about a deb, but I compiled lm_sensors-2.3.4 from source and then
installed procmeter3-3.2 from source, as well - and now have a procmeter which
displays my system (board thermistor) temp as well as both my CPU temps. This is
board dependent (I'm using an Abit BP6) - but most new ones have some sort of
environmental monitoring on them...

Head over to http://www.netroedge.com/~lm78/ to check out what kind of
potential you have.

There might be a frozen package, but I'm risk averse and am waiting for the
real thing (stable Potato).

 I thought I had heard of the Netscape/Java freeze problem
 before.  Any ideas on fix and/or where the problem
 is coming from?  I think I'm now having the same
 problem while running Star Office too.

I hadn't heard anything about this, but then again I wasn't listening for it...
Actually, I just upgraded Navigator to 4.7 last night (found a deb), and had
the same sort of lockup as I had had with 4.6. So, that /almost/ rules that
out, but not quite.

cheers.
chris.

-

26-Apr-00 - 11:11:07


Re: Semi-frequent lock-ups

2000-04-26 Thread John S Jacobs Anderson
on 4/26/00 2:13 PM, chris horn. at [EMAIL PROTECTED] wrote:

 The hardware is brand new (August 1999), and top quality. I haven't had any
 trouble with it until lately, really...
 
 Abit BP6
 Dual Celeron 400 (not o/c)
[snip]

Were you aware that there is a mailing list (linux-abit) dedicated to
hardware lock-ups with this mobo? It's been a fairly difficult bug to track
down, but some people are reporting success with the most recent BIOS update
released by Abit (version is QQ, I believe).

I don't have any of the URLs handy, but Google should.

Good luck,
john.

-- 
   [ John S Jacobs Anderson ]--URL:mailto:[EMAIL PROTECTED]
[ Genehack: Not your daddy's weblog ]--URL:http://genehack.org



Re: Semi-frequent lock-ups

2000-04-26 Thread chris horn.
Thank you.

I will slap that BIOS on a boot disk and flash away into the sunset!
I'll also go find that site.


chris.

-

26-Apr-00 - 14:53:40


Re: Semi-frequent lock-ups

2000-04-26 Thread Bruce Sass
On Wed, 26 Apr 2000, chris horn. wrote:

  Assuming that a software problem would leave clues in the logs or be
  predictable, and a peripheral problem (i.e., the HDD) would give
  symptoms first  Try testing the memory (hwtools pkg), checking for
  overheating (take the cover off and point a fan at the motherboard), or
  checking the power supply (remove it and take it into an electronics
  shop). 
 
 The hardware is brand new (August 1999), and top quality. I haven't had any
 trouble with it until lately, really...

I believe you.  :)
Electronics (chips that is) either goes bad within the first few months,
or lives for 15-20 years before the failure rate start to climb again.
The initial failures are caused by defects, the later ones by `wearing
out'.  So, if the box is a few years old it is less likely to be a
problem with the electronics than if the box is new.

Also, overheating is not just a CPU (or wherever else they put
temperature sensors) problem.  If you have a bad bus transceiver (for
example) it could cause the box to crash hard and you would never
realize that is the problem, unless you checked its temperature with a
thermometer (bad chips tend to run hot).  The burnin (they still do that
I assume) process should weed out defective chips, but ocassionally it
will weken a marginal chip to the point where it fails prematurely. 


- Bruce


Re: Semi-frequent lock-ups

2000-04-26 Thread chris horn.
 I believe you.  :)

*grin*

 Electronics (chips that is) either goes bad within the first few months,
 or lives for 15-20 years before the failure rate start to climb again.
 The initial failures are caused by defects, the later ones by `wearing
 out'.  So, if the box is a few years old it is less likely to be a
 problem with the electronics than if the box is new.

Okay. I also found the BP6 site someone else mentioned. I'm not the only one w/
stability problems, although they seem to be getting worse lately... Possibly
what you're talking about - but that's just wild speculation. Damn, I might
have to stick a fan on my chipset! What's the world coming to!?!
 
 Also, overheating is not just a CPU (or wherever else they put
 temperature sensors) problem.  If you have a bad bus transceiver (for
 example) it could cause the box to crash hard and you would never
 realize that is the problem, unless you checked its temperature with a
 thermometer (bad chips tend to run hot).  The burnin (they still do that
 I assume) process should weed out defective chips, but ocassionally it
 will weken a marginal chip to the point where it fails prematurely. 

So I'm going to put a new BIOS on, and cross my fingers.
If that fails, how do I go about testing the individual components? (eg 'bus
transceiver' or chipset) To do the chipset, do I just use it heavily? heh
heh. I do run RC5 24/7 and commonly run intensive stuff over that. Come to
think about it, it's been crashing after the morning cron job. That does a
massive find for something (forgot what, exactly) - but that would stress the
chipset and bus, and then right after that RC5 keeps plugging away, and then
a couple MP3z are cronned to wake me up. Huh. Maybe it doesn't like playing
MP3z after it's had a rough day searching for things on the disk... Ahhh.
speculation.

And I thought I was getting a steal...
Well, crashing once a month is kinda worth the 2X price difference, I suppose.
Hell, I'm just a poor college student (well, I certainly am after putting
together this box, that is)

Just as long as my data stays warm and safe. Time to do some more backups.


chris.

-

26-Apr-00 - 15:05:00


Re: Semi-frequent lock-ups

2000-04-26 Thread chris horn.
Well, I flashed the BIOS. So now it's just sit tight, and hope.  ;)

I think I have to update lm_sensors now, though.
It's reading temps of 30C for everything! I knew it was cold in here, but wow!

Oh, wait. RC5 hadn't been on for a bit. [sitting. staring.] The system was
slacking. There they go... *smug smile* Already at 38C. Heh.  - L O A D -


Thanks for the help, everyone. If anyone wants a BP6 to trade...

chris.

-

26-Apr-00 - 16:04:03


Re: Semi-frequent lock-ups

2000-04-26 Thread kmself
On Wed, Apr 26, 2000 at 08:42:09AM -0400, chris horn. wrote:
 Hi. I'm running with packages from the newest update of Slink off the
 ftp.cs.unm.edu/mirrors/debian Debian2.1r5 site, with kernel 2.2.14 #4
 SMP Sun Feb 6 12:02:09 EST 2000 i686
 
 I've been getting hard lockups lately, and want to know how to track them
 down.  I've looked in all my logs (immediately after reboot), but can't
 seem to find anything important, or telling. Is someone taking me down,
 or is something going wrong internally? How can I find out? From what I
 can tell, the last two have been about a half an hour after the morning
 cron job (6:25am) tidies the system up. The last thing in the syslog
 last time was a mail related line. This time, there wasn't anything.

I'd check /var/log/kern.log.  

Looks like you've identified your mobo as a likely cause of the
problems.  I've been having a similar set of problems with a work system
(home box on similar Debian config but different hardware is fine), with
crashes every few days.

I've posted to the linux-kernel mailing list with a full bug report,
most recently here:
http://www.uwsg.indiana.edu/hypermail/linux/kernel/0004.3/0110.html

So far, no responses :-(

-- Unsubscribe?  mail -s unsubscribe [EMAIL PROTECTED]
 /dev/null


-- 
Karsten M. Self kmself@ix.netcom.com   http:/www.netcom.com/~kmself
What part of Gestalt don't you understand?
http://gestalt-system.sourceforge.net/
GPG fingerprint: F932 8B25 5FDD 2528 D595  DC61 3847 889F 55F2 B9B0


pgpax1BAK5iCs.pgp
Description: PGP signature