linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Richard B. Johnson" <root@chaos.analogic.com>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: gene.heskett@verizon.net,
	Jean-Marc Valin <Jean-Marc.Valin@USherbrooke.ca>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Increasing HZ (patch for HZ > 1000)
Date: Thu, 11 Dec 2003 13:10:16 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.53.0312111304380.5754@chaos> (raw)
In-Reply-To: <1316960000.1071164020@[10.10.2.4]>

On Thu, 11 Dec 2003, Martin J. Bligh wrote:

> > Hardware indeed.  I'm a Certified Electronics Technician.  Have
> > someone check all those electrolyric caps in the on-board psu in
> > particular, using a device similar to a "Capacitor Wizard" which
> > measures not the capacity of the cap, but the caps Equivalent Series
> > Resistance (ESR) at 100 kilohertz or more.  Anything over half an ohm
> > should be replaced forthwith.  This assumes of course that your tech
> > in charge of hot solder has the tools to do it correctly.  If not,
> > find one who does have the tools.
> >
> > Many mobos in a period ranging from about 2.5 to 1.5 years ago were
> > built with caps that go defective prematurely due to a bad batch of
> > them from several far eastern cap makers who were fed a bad recipe
> > for the electrolyte in the caps, eg the Ethylene Glycol wasn't near
> > pure enough.
>
> When you say "fed a bad recipe", didn't they actually steal it? Or
> is that just an urban legend?
>
> M.

"Appropriated". Also, it isn't ethylene glycol (that's antifreeze),
It's potassium hydroxide with an inhibitor. The inhibitor was cleverly
removed from the recipe and left out to be stolen. As expected, it
was. Unfortunately, the bad caps didn't damage the competing company
bad enough to put them out-of-business so the whole ploy was a waste
of effort. ;^)


Cheers,
Dick Johnson
Penguin : Linux version 2.4.22 on an i686 machine (797.90 BogoMips).
            Note 96.31% of all statistics are fiction.



  reply	other threads:[~2003-12-11 18:08 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-11  6:05 Increasing HZ (patch for HZ > 1000) Jean-Marc Valin
2003-12-11  7:07 ` Martin J. Bligh
2003-12-11  7:15   ` Jean-Marc Valin
2003-12-11  7:18     ` Martin J. Bligh
2003-12-11 17:18       ` Gene Heskett
2003-12-11 17:33         ` Martin J. Bligh
2003-12-11 18:10           ` Richard B. Johnson [this message]
2003-12-11 19:14             ` Gene Heskett
2003-12-11 18:35           ` Gene Heskett
2003-12-12 22:08       ` Pavel Machek
2003-12-12 22:57         ` Jean-Marc Valin
2003-12-12 23:18           ` Måns Rullgård
2003-12-12 23:40           ` Pavel Machek
2003-12-13  2:25             ` Måns Rullgård
2003-12-16  3:04             ` john stultz
2003-12-16  5:20               ` Mitchell Blank Jr
2003-12-14  1:05           ` bill davidsen
2003-12-14  4:48             ` Pat Erley
2003-12-11  7:30     ` Nick Piggin
2003-12-11  8:25     ` Tim Schmielau
2003-12-12  8:00   ` Jean-Marc Valin
2003-12-12 22:10     ` Pavel Machek
2003-12-12 22:50       ` Jean-Marc Valin
2004-01-03 18:16         ` Bill Davidsen
     [not found]         ` <010f01c415a4_27033d00_d100000a@sbs2003.local>
2004-04-06 13:00           ` Pavel Machek
2003-12-11 19:22 Grover, Andrew
2003-12-12 22:31 ` Jamie Lokier
2003-12-12 22:58   ` Vojtech Pavlik
2003-12-12 23:45     ` Jamie Lokier
2003-12-13  8:36       ` Vojtech Pavlik
2003-12-12 15:52 Vincent Legoll

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.53.0312111304380.5754@chaos \
    --to=root@chaos.analogic.com \
    --cc=Jean-Marc.Valin@USherbrooke.ca \
    --cc=gene.heskett@verizon.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbligh@aracnet.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).