From owner-freebsd-current@FreeBSD.ORG Thu Dec 18 21:48:39 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 70B4816A4CE for ; Thu, 18 Dec 2003 21:48:39 -0800 (PST) Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3E57943D3F for ; Thu, 18 Dec 2003 21:48:38 -0800 (PST) (envelope-from truckman@FreeBSD.org) Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.12.9p2/8.12.9) with ESMTP id hBJ5mSeF076722; Thu, 18 Dec 2003 21:48:32 -0800 (PST) (envelope-from truckman@FreeBSD.org) Message-Id: <200312190548.hBJ5mSeF076722@gw.catspoiler.org> Date: Thu, 18 Dec 2003 21:48:28 -0800 (PST) From: Don Lewis To: mezz7@cox.net In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii cc: freebsd-current@FreeBSD.org Subject: Re: The reboot doesn't work anymore in today -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, 19 Dec 2003 05:48:39 -0000 On 18 Dec, Jeremy Messenger wrote: > On Fri, 19 Dec 2003 00:20:48 -0500, Joe Marcus Clarke > wrote: > >> On Fri, 2003-12-19 at 00:16, Jeremy Messenger wrote: >>> Yesterday and today, I CVSup'ed and the reboot doesn't work anymore, >>> something isn't work correct. The last week -CURRENT works fine, I can >>> reboot. I tried to use GENERIC kernel and I still get the same result, >>> so >>> I am not sure what I should do next. Attaching the dmesg.txt here.. >>> >>> shutdown's -r and -p don't work, I had to press the power button to turn >>> off and on by manual. It does shutdown clean like 'shutdown -h', >>> thought. I just saw the same thing here when I rebooted a two day old kernel. >> Justin Gibbs just committed a fix for an infinite loop in the ahc code. >> I wonder if that will fix this problem. > > I just noticed that too after I sent an email, but mine is aic7899 and > Justin commited on aic79xx.c. I am going to give it another try sometime > at like midnight or late, thought. In my case it is an aic7892. aic7892: Ultra160 Wide Channel A, SCSI Id=7, 32/253 SCBs ahc0: port 0xe400-0xe4ff mem 0xef022000-0xef022fff irq 16 at device 12.0 on pci0