From owner-freebsd-stable@FreeBSD.ORG Tue Jan 31 15:58:26 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E9E4C16A420 for ; Tue, 31 Jan 2006 15:58:26 +0000 (GMT) (envelope-from jfarmer@goldsword.com) Received: from audi.websitewelcome.com (audi.websitewelcome.com [67.19.210.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id 871D443D45 for ; Tue, 31 Jan 2006 15:58:26 +0000 (GMT) (envelope-from jfarmer@goldsword.com) Received: from cpanel by audi.websitewelcome.com with local (Exim 4.52) id 1F3xte-0001kq-4R for freebsd-stable@freebsd.org; Tue, 31 Jan 2006 09:58:22 -0600 Received: from 65.13.105.239 ([65.13.105.239]) by www.goldsword.com (Horde MIME library) with HTTP; Tue, 31 Jan 2006 09:58:22 -0600 Message-ID: <20060131095822.7uwziuizct34cwsw@www.goldsword.com> Date: Tue, 31 Jan 2006 09:58:22 -0600 From: jfarmer@goldsword.com To: freebsd-stable@freebsd.org References: <20060130225306.77B3516A422@hub.freebsd.org> In-Reply-To: <20060130225306.77B3516A422@hub.freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: Internet Messaging Program (IMP) H3 (4.0.3) X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - audi.websitewelcome.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [32001 32001] / [47 12] X-AntiAbuse: Sender Address Domain - goldsword.com X-Source: X-Source-Args: X-Source-Dir: Subject: Debug Snapshot Tool/Script? [WAS:Re: Linksys WPC54g v4, NDIS, & Kernel Panics] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Jan 2006 15:58:27 -0000 Quoting Bill Paul : > There is a LOT more you should have said. > > - You didn't say what chipset this chip has. No, "Linksys WPC54g v4" > isn't enough to figure it out. You should do pciconf -lv with the > card plugged in and show us the result. > > - You didn't show the dmesg output from when the card is plugged in. > > - You didn't show what commands you typed to "set an SSID under iconfig," > or for your attempts to "set wither WEP or WPA-PSK keys." > > - If your panic info is accurate, you're using smbfs. Have you tried > _NOT_ using smbfs to see what happens? > > Remember, we're not there to look over your shoulder: you have to > _show_ us what you're doing, not summarize. > > People, I'm getting tired of always having to ask for this basic > information. The more I have to ask, the more annoyed I get, and the > less inclined I am to help anyone. The shit you don't think is important? > It's important. So spill it already. Bill makes important points, And I want to use them as a springboard to a possible way to avoid these sequences of "Pleases tell us,....now tell us...." messages on the lists. What about creating a simple "snapshot grabber" or similar tool that would grab the output of such commands and stuff them into a file? Then the user could attach it to the message to the list, or have it attached to the send-pr channel. Yeah, it would likely either grab too much or too little information. The first isn't a problem, simply group information blocks in the file to various sub-systems. The second possibility will get fixed as the tool is used & it's seen what additional information is asked for... Comments? John ------------------------------------------------------------------- John T. Farmer Owner & CTO GoldSword Systems jfarmer@goldsword.com 865-691-6498 Knoxville TN Consulting, Design, & Development of Networks & Software