From owner-freebsd-hackers@FreeBSD.ORG Sat Nov 11 19:17:45 2006 Return-Path: X-Original-To: hackers@FreeBSD.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 372FE16A4A7 for ; Sat, 11 Nov 2006 19:17:45 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id DFA0E43D4C for ; Sat, 11 Nov 2006 19:17:43 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id D4F871A3C19; Sat, 11 Nov 2006 11:17:43 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id F1EE751390; Sat, 11 Nov 2006 14:17:33 -0500 (EST) Date: Sat, 11 Nov 2006 14:17:33 -0500 From: Kris Kennaway To: Gergely CZUCZY Message-ID: <20061111191733.GB7930@xor.obsecurity.org> References: <20061111172731.GB39999@harmless.hu> <20061111183110.GA6975@xor.obsecurity.org> <20061111183432.GA41296@harmless.hu> <20061111184025.GA7128@xor.obsecurity.org> <20061111184625.GA41463@harmless.hu> <20061111185228.GA7338@xor.obsecurity.org> <20061111185747.GA56613@harmless.hu> <20061111190245.GA7577@xor.obsecurity.org> <20061111191322.GA56870@harmless.hu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="3uo+9/B/ebqu+fSQ" Content-Disposition: inline In-Reply-To: <20061111191322.GA56870@harmless.hu> User-Agent: Mutt/1.4.2.2i Cc: hackers@FreeBSD.org, Kris Kennaway Subject: Re: system randomly freezes X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Nov 2006 19:17:45 -0000 --3uo+9/B/ebqu+fSQ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Nov 11, 2006 at 08:13:22PM +0100, Gergely CZUCZY wrote: > On Sat, Nov 11, 2006 at 02:02:46PM -0500, Kris Kennaway wrote: > > On Sat, Nov 11, 2006 at 07:57:47PM +0100, Gergely CZUCZY wrote: > >=20 > > > > OK, seems weird to go through all the disruption of changing to a n= ew > > > > OS instead of a few minutes work at a console to give us what we ne= ed > > > > to resolve the matter -- but whatever works for you. > > > already done some stuff like these movings... i'm familiars with them. > > > it's not about a few minutes work. it's about the few hours' downtime= :) > >=20 > > It's a few minutes to perform the additional work at the serial > > console when your system hangs, which is *required* for a developer to > > help with your problem. If you're not willing to do this, there's not > > much more we can do for you. > i will see what can i do. a serial console may be accessable, but i'm not= sure. > i will have to visit the server hotel and talk with the techies there. we > have two boxes there, and it may be somehow possible to connect their > serial ports. the problem is, they are far away in the room from each oth= er. > the hotel only gives system console(VGA+ps2 keyboard) access if i ask. but > this bloody box sometimes ain't even responses to that anyways, the LCD > remains blank. You can't even break to the debugger? > i'd like to solve this, but the technical opportunities are limited here. > we cannot have downtime, and if we have it have to be minimized. as you s= ee > clients won't accept a reasons like "sorry, we were debugging this OS we > run at the server". >=20 > the question will be that, when i have a serial link, and shit happens(tm= ), > should i inspect it myself, or should i scream somewhere for a more decent > person (maybe a developer) to check it? Did you read the developers handbook chapter I pointed you to, yet? > > After 6.2 is release will of course be too late for you, again. If > > the problem is not fixed by magic then you'll be in the same position > > you are now. > why too late? it usually go for a month with a reboot. and it should be > released in a month. as i see, it fits into the time :) Because (if it is a FreeBSD bug) then you'll have more work to do to apply a patch to your system, and also it won't help anyone else who might also be seeing the problem, until 6.3-RELEASE in ~6 months. Kris --3uo+9/B/ebqu+fSQ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFViHNWry0BWjoQKURAiZvAKDmTrgDj3hT2hTZptu23qVdkdoY9ACgwD1g aXYiYEEZvvIhchVTpKiatsk= =qoDo -----END PGP SIGNATURE----- --3uo+9/B/ebqu+fSQ--