From owner-freebsd-questions@FreeBSD.ORG Sun Oct 1 03:55:35 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B5F9D16A49E for ; Sun, 1 Oct 2006 03:55:35 +0000 (UTC) (envelope-from snagit@cbpratt.prohosting.com) Received: from n054.sc0.cp.net (smtpout1098.sc0.he.tucows.com [64.97.144.98]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7A0D043D45 for ; Sun, 1 Oct 2006 03:55:35 +0000 (GMT) (envelope-from snagit@cbpratt.prohosting.com) Received: from [192.168.1.100] (67.47.213.85) by n054.sc0.cp.net (7.2.069.1) (authenticated as eagletree@hughes.net) id 451E1D8E00017350 for freebsd-questions@freebsd.org; Sun, 1 Oct 2006 03:55:34 +0000 Mime-Version: 1.0 (Apple Message framework v752.2) Content-Transfer-Encoding: 7bit Message-Id: Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: FreeBSD Questions From: Chris Date: Sat, 30 Sep 2006 20:55:27 -0700 X-Mailer: Apple Mail (2.752.2) Subject: Question on when to submit PRs (a reboot hang) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Oct 2006 03:55:35 -0000 I have what seems to be a mostly stable 6.2 PRERELEASE that I couldn't take backward to RELENG_6_1 for reasons I couldn't figure out. Unimportant because it's being loaded with data and going to test production right now. The "mostly" part is that in cvsupping I picked up a nasty reboot problem where "reboot" would stop at Uptime and hang about 75% of the time. If the system runs like I've come to expect FreeBSD to run over the years, I don't really care plus I'm installing a remote Power Tower to overcome such issues next week. On 6.2 PR, it ran through about 50 reboots without a problem until I stupidly updated once more. Yesterday I updated yet another time and the frequency of the problem dropped to the point where it didn't do it but 1 in 10 intentional reboots. But since I am still seeing it. I'm wondering if it's worthwhile putting in a problem report? I dislike troubling people if I am the only one who's going to experience a problem, especially one which I will soon be able to manage it by cycling grouped power inputs (if it even happens again now, since I won't be rebooting a production system). It's AMD64 on an s4882 Tyan. The question is probably best stated as what is whining and what is helping? For all I know it's a timing problem with bios version I'm running.