From owner-freebsd-current Sun Sep 20 14:35:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA12142 for freebsd-current-outgoing; Sun, 20 Sep 1998 14:35:55 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA12136 for ; Sun, 20 Sep 1998 14:35:53 -0700 (PDT) (envelope-from tlambert@usr04.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id OAA26765; Sun, 20 Sep 1998 14:35:23 -0700 (MST) Received: from usr04.primenet.com(206.165.6.204) via SMTP by smtp01.primenet.com, id smtpd026748; Sun Sep 20 14:35:18 1998 Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id OAA02071; Sun, 20 Sep 1998 14:35:16 -0700 (MST) From: Terry Lambert Message-Id: <199809202135.OAA02071@usr04.primenet.com> Subject: Re: shouting in a void? To: ben@rosengart.com Date: Sun, 20 Sep 1998 21:35:16 +0000 (GMT) Cc: current@FreeBSD.ORG In-Reply-To: from "Snob Art Genre" at Sep 20, 98 02:18:29 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I've been reporting panics at least once a day for several days now. > It's entirely possible that someone is reading my posts and working on > these issues and is simply too busy to respond verbosely, of course, but > I don't seem to be getting much feedback at all. If these posts are > resulting in anything at all, I'd appreciate just a simple "yep, thanks, > keep up the beta-testing". Well, I haven't responded because there wasn't enough information for me to even be able to speculate reasonably. Most recent code: yes/no CAM: yes/no Soft updates: yes/no SCSI: yes/no AIC SCSI: yes/no backed off clock.c change: yes/no ELF: yes/no other mutating subsystem: yes/no (this one is hard to track) Trap address: _______________ nm /kernel | sort -n: _______________ _______________ _______________ (include only lines immediately proceeding and following the the trap address; this should be scripted by someone who cares). currently running program: _______________ stack traceback up to panic: _______________ _______________ _______________ (include only sufficient information to get to the point where the panic occurred, since se all know about the 12 or so things panic calls). Also, if you can identify a particular kernel subsystem from this, you should contact the maintainer of that subsystem directly for best response. There is a lot of activity in -current, and I'm having a hard time identifying where your problem begins and stale/bad code ends, which is why I haven't responded. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message