From owner-freebsd-stable@FreeBSD.ORG Wed Apr 5 20:57:25 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 D84E716A428 for ; Wed, 5 Apr 2006 20:57:25 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 60C6343D4C for ; Wed, 5 Apr 2006 20:57:25 +0000 (GMT) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by smarthost1.sentex.ca (8.13.6/8.13.6) with ESMTP id k35KvOgp028936; Wed, 5 Apr 2006 16:57:24 -0400 (EDT) (envelope-from mike@sentex.net) Received: from simian.sentex.net (simeon.sentex.ca [192.168.43.27]) by lava.sentex.ca (8.13.3P/8.13.3) with ESMTP id k35KvNqA082837 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 5 Apr 2006 16:57:23 -0400 (EDT) (envelope-from mike@sentex.net) Message-Id: <6.2.3.4.0.20060405164905.09e6d1c8@64.7.153.2> X-Mailer: QUALCOMM Windows Eudora Version 6.2.3.4 Date: Wed, 05 Apr 2006 16:56:28 -0400 To: shih@math.jussieu.fr From: Mike Tancsa In-Reply-To: <20060405203741.GF14126@math.jussieu.fr> References: <20060405200341.GD14126@math.jussieu.fr> <20060405200727.GA28371@xor.obsecurity.org> <20060405201500.GE14126@math.jussieu.fr> <20060405202100.GA28626@xor.obsecurity.org> <20060405203741.GF14126@math.jussieu.fr> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Virus-Scanned: by amavisd-new Cc: freebsd-stable@freebsd.org Subject: Re: Disappointed 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: Wed, 05 Apr 2006 20:57:25 -0000 At 04:37 PM 05/04/2006, Albert Shih wrote: >NB: Why this kind of problem can happen ? I ask this because until 6. I >never have this kind of problem. Think about it this way, if one of your users came to you and said, "its not working. I need you to fix it"... You would start by getting your user to provide details of what "it" is. So when you ask "why this kind of problem can happen", you have not provided any details as to what the problem is. The crash can be bad hardware, it could be a change in any number of drivers. No one knows what hardware you are using even. It could be something as simple as a NIC driver regression or not. But without details, its not possible to do anything. Start by creating a debug kernel (see the website documentation on how to do it and how to enable and save a crash dump) as well as by providing a dmesg that shows the hardware you are using. The more detail and description you provide in the PR, the better the chance someone can fix it or help you work around it. ---Mike