From owner-freebsd-current@FreeBSD.ORG Mon Jan 30 17:30:34 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5FBB3106566C for ; Mon, 30 Jan 2012 17:30:34 +0000 (UTC) (envelope-from freebsd@damnhippie.dyndns.org) Received: from qmta14.emeryville.ca.mail.comcast.net (qmta14.emeryville.ca.mail.comcast.net [76.96.27.212]) by mx1.freebsd.org (Postfix) with ESMTP id 4567B8FC0A for ; Mon, 30 Jan 2012 17:30:34 +0000 (UTC) Received: from omta05.emeryville.ca.mail.comcast.net ([76.96.30.43]) by qmta14.emeryville.ca.mail.comcast.net with comcast id TtU11i0050vp7WLAEtWZqC; Mon, 30 Jan 2012 17:30:33 +0000 Received: from damnhippie.dyndns.org ([24.8.232.202]) by omta05.emeryville.ca.mail.comcast.net with comcast id TtWY1i00m4NgCEG8RtWZue; Mon, 30 Jan 2012 17:30:33 +0000 Received: from [172.22.42.240] (revolution.hippie.lan [172.22.42.240]) by damnhippie.dyndns.org (8.14.3/8.14.3) with ESMTP id q0UHUVT4019270; Mon, 30 Jan 2012 10:30:31 -0700 (MST) (envelope-from freebsd@damnhippie.dyndns.org) From: Ian Lepore To: Andriy Gapon In-Reply-To: <4F26CC5A.2070501@FreeBSD.org> References: <4F26CC5A.2070501@FreeBSD.org> Content-Type: text/plain Date: Mon, 30 Jan 2012 10:30:31 -0700 Message-Id: <1327944631.1686.24.camel@revolution.hippie.lan> Mime-Version: 1.0 X-Mailer: Evolution 2.26.0 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: revisiting tunables under Safe Mode menu option X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Mon, 30 Jan 2012 17:30:34 -0000 On Mon, 2012-01-30 at 18:59 +0200, Andriy Gapon wrote: > > o hw.ata.ata_dma, hw.ata.atapi_dma - I am not sure if there have been any > significant problems with ATA DMA recently. Maybe these could be removed? I still have to work with hardware that requires ata_dma disabled. It seems to be required for most systems I've worked with that have a compact flash socket on the mainboard (sometimes you can just limit the mode to udma33 or less, sometimes you have to turn it off completely.) Adding kern.eventtimer.periodic=1 seems like a good idea. As a general philosophical thing, I don't have a problem with the idea "safe mode turns off everything that has ever historically been problematic," because I don't think anyone expects a system to run well in safe mode. I see it more as a tool to start narrowing down the area of trouble, like step 1 of a binary search for the problem. As such, the most important aspect is a comprehensive list of what changes for safe mode, so that you can procede by selectively en/disabling the various things it does. -- Ian