From owner-freebsd-current@FreeBSD.ORG Fri Jun 6 07:00:28 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D8EB237B405 for ; Fri, 6 Jun 2003 07:00:27 -0700 (PDT) Received: from out001.verizon.net (out001pub.verizon.net [206.46.170.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8A5DC43F75 for ; Fri, 6 Jun 2003 07:00:16 -0700 (PDT) (envelope-from mtm@identd.net) Received: from kokeb.ambesa.net ([138.88.93.237]) by out001.verizon.net (InterMail vM.5.01.05.33 201-253-122-126-133-20030313) with ESMTP id <20030606140015.HCMG12592.out001.verizon.net@kokeb.ambesa.net>; Fri, 6 Jun 2003 09:00:15 -0500 Date: Fri, 6 Jun 2003 10:00:14 -0400 From: Mike Makonnen To: "Robin P. Blanchard" In-Reply-To: References: X-Mailer: Sylpheed version 0.8.10 (GTK+ 1.2.10; i386-portbld-freebsd5.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Authentication-Info: Submitted using SMTP AUTH at out001.verizon.net from [138.88.93.237] at Fri, 6 Jun 2003 09:00:15 -0500 Message-Id: <20030606140015.HCMG12592.out001.verizon.net@kokeb.ambesa.net> cc: current@freebsd.org Subject: How to ask for help on this list (was Re: Reproducible hard freeze on 5.1-CURRENT) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Jun 2003 14:00:28 -0000 On Fri, 6 Jun 2003 08:48:17 -0400 "Robin P. Blanchard" wrote: > Upon launching samba-2.2.8a (via ports) on the below system, the machine > immediately hard freezes. I've included interesting portions of kernel > config. Any suggestions how I can acquire more useful information ? [snip] > #options WITNESS > #options WITNESS_DDB > #options WITNESS_SKIPSPIN > #options INVARIANTS > #options INVARIANT_SUPPORT > #options DIAGNOSTIC [snip] > > #options SCHED_4BSD > options SCHED_ULE This is not to pick on you in particular. There have been a lot of these lately and I just picked this one to reply to. None of this is new, these points have already been made elsewhere and people on this list should be familiar with them. But I'll go ahead and point them out anyway. If you experience a freeze, panic, or any other fatal problem please keep in mind the following things: 1. There is a reason SCHED_ULE is labeled 'experimental'. It means that this is a new feature that needs some more testing and deguggin. Don't be surprised if it panics your system, eats your homework, or causes your hair to fall out. If you insist on using it, then please properly label your email with such information, and at the very least try to determine if _not_ using it makes your problems go away. 2. Before you report a problem enable all the debugging options in your kernel configuration file. If you don't want to put up with the reduction in performance, then build two kernels from the same source: one without the debuging options and one with. When you hit a problem, boot into the kernel with the debugging options and try to reproduce the problem. Report any Lock Oreder Reversals (LORs) and other errors reported by the kernel. When you do report a problem like "my box freezes" it is essential that you at least have 'options DDB' in your kernel so you can attempt to enter the kernel debugger and get an idea of what's happening. If enabling the debugging options makes your problems go away, that is helpful information in and of itself, so report it. 3. There is an entry in The Handbook and the Articles that provide information on how to obtain debuging information from your kernel. Greg Lehey also has an article about that in the works (see archives). Please read these before you ask "How can I get more debugging information." 4. Some problems, are caused by faulty hardware. The ports tree has some applications you can use to check your hardware (memtest86, etc). If you see random panics and/or freezes it may be a good idea to use some of these programs to check your hardware. Believe it or not, hardware does fail, so don't discount this possibility. 5. You can greatly increase the chance that your problem gets resolved if you provide good quality debugging information, and actually do some of the diagnosing yourself. Even a partial attempt at solving the problem is better than nothing. 6. Finally, please try to understand that this is a volunteer project. Few developers actually get paid to work on FreeBSD, and when they do it's usually for something specific that their employer needs. Most developers give up free time during the week to work on FreeBSD. So, it may not be possible to devote the time and energy you believe your problem deserves. Cheers. -- Mike Makonnen | GPG-KEY: http://www.identd.net/~mtm/mtm.asc mtm@identd.net | D228 1A6F C64E 120A A1C9 A3AA DAE1 E2AF DBCC 68B9 mtm@FreeBSD.Org| FreeBSD - The Power To Serve