From owner-freebsd-current@FreeBSD.ORG Tue Jul 22 23:53:12 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 2038C37B401 for ; Tue, 22 Jul 2003 23:53:12 -0700 (PDT) Received: from bluejay.mail.pas.earthlink.net (bluejay.mail.pas.earthlink.net [207.217.120.218]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8DEEE43F3F for ; Tue, 22 Jul 2003 23:53:11 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from user-2ivfkao.dialup.mindspring.com ([165.247.209.88] helo=mindspring.com) by bluejay.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 19fDUs-0004L2-00; Tue, 22 Jul 2003 23:53:10 -0700 Message-ID: <3F1E308D.6491D6C0@mindspring.com> Date: Tue, 22 Jul 2003 23:51:57 -0700 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Anish Mistry References: <200307222346.04865.mistry.7@osu.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a406770e35a55cd6627afa766aba600826666fa475841a1c7a350badd9bab72f9c350badd9bab72f9c cc: freebsd-current@freebsd.org Subject: Re: su and suspend problems with -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: Wed, 23 Jul 2003 06:53:12 -0000 Anish Mistry wrote: > I've been using -CURRENT for while now and have finally gotten some time to > come up with a list of problems I'm getting: > When I su to change to the root user I get a "Bus Error" from su. This have > been around for about a month, still happens after multiple build and install > worlds, I just haven't gotten around to reporting it. This is generally a result of an out-of-date PAM module, or a pam.conf that is out of date. > About a week ago I started to have the laptop reboot when is comes out of > suspend, which it never used to do. This is likely an ACPI or device driver issue. Since you know the approximate time, you can bsearch for the kernel change that caused it. You will be able to get it down to a 1 hour time window with only 8 kernel builds. Have you ever played "Higher and Lower"? Start with a kernel from 84 hours ago (3.5 days * 24 hours). If it has the problem, try a kernel from 126 hours ago; if it doesn't, try a kernel from 42 hours ago. Stop when you find the hour that introduce the problem. Doing this will always take you at most log2(# of hours)+1 tries to find any kernel change that caused your problem. 8-). -- Terry