From owner-freebsd-hackers Wed Dec 5 12:45: 5 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from elvis.mu.org (elvis.mu.org [216.33.66.196]) by hub.freebsd.org (Postfix) with ESMTP id CB1AD37B405 for ; Wed, 5 Dec 2001 12:44:55 -0800 (PST) Received: by elvis.mu.org (Postfix, from userid 1192) id 7C8F781D01; Wed, 5 Dec 2001 14:44:50 -0600 (CST) Date: Wed, 5 Dec 2001 14:44:50 -0600 From: Alfred Perlstein To: "PSI, Mike Smith" Cc: hackers@freebsd.org Subject: Re: Tracking down system freeze Message-ID: <20011205144450.L92148@elvis.mu.org> References: <3C0E641B.F65BAC6@mitre.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3C0E641B.F65BAC6@mitre.org>; from mlsmith@mitre.org on Wed, Dec 05, 2001 at 01:14:51PM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * PSI, Mike Smith [011205 12:12] wrote: > Hi all. > > Does anyone have ANY suggestions on how to determine where the > kernel/program is when the system freezes??? Even hardware solutions, > such as the infamous paperclip across two pins will do. Ohh... the infamous paperclip trick... That's what I used to debug the wi wireless driver. * THIS DIAGRAM IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE * ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS * OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY * OUT OF THE USE OF THIS DIAGRAM, EVEN IF ADVISED OF THE POSSIBILITY OF * SUCH DAMAGE. Ok, now.. What you do is fold a paperclip then use it to make the last two pins of the ISA bus short: here vv ________________________________ | || || || || :: :: :: | [-] <- blow up diagram | || || || || :: :: :: | [ ] make paperclip short | || || || || :: :: :: | [ ] the last two terminals | || || || || :: :: :: | [ ] that face each other | || || || || :: :: :: | [ ] | || || || || :: :: :: | [ ] | || || || || | [ ] | || || || || \_____/ | [ ] | PCI slots | | \________/ | | ISA slots | | | | | |________________________________| Be warned, this doesn't work on all motherboards! The one that I had that it didn't work on didn't have any damage though. -- -Alfred Perlstein [alfred@freebsd.org] 'Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom.' http://www.morons.org/rants/gpl-harmful.php3 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message