From owner-freebsd-current@FreeBSD.ORG Sat Jun 12 21:28:33 2004 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 D27DC16A4CE for ; Sat, 12 Jun 2004 21:28:33 +0000 (GMT) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id C718643D31 for ; Sat, 12 Jun 2004 21:28:33 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id DCEB672DF2; Sat, 12 Jun 2004 14:28:10 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id DA6F572DB5; Sat, 12 Jun 2004 14:28:10 -0700 (PDT) Date: Sat, 12 Jun 2004 14:28:10 -0700 (PDT) From: Doug White To: Eirik Oeverby In-Reply-To: <40CAD634.8060808@anduin.net> Message-ID: <20040612142543.H74026@carver.gumbysoft.com> References: <40CAD634.8060808@anduin.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org Subject: Re: Serial console - how to reboot? 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: Sat, 12 Jun 2004 21:28:34 -0000 On Sat, 12 Jun 2004, Eirik Oeverby wrote: > I have recently been getting the following messages on my console: > swap_pager: indefinite wait buffer: device: #amrd/0x20001, blkno: 1072, > size: 4096 > swap_pager: indefinite wait buffer: device: #amrd/0x20001, blkno: 832, > size: 4096 > swap_pager: indefinite wait buffer: device: #amrd/0x20001, blkno: 512, > size: 4096 > swap_pager: indefinite wait buffer: device: #amrd/0x20001, blkno: 576, > size: 4096 > swap_pager: indefinite wait buffer: device: #amrd/0x20001, blkno: 584, > size: 4096 > > I am aware that this usually indicates a bad drive or something, but > given that it's a RAID volume hanging on an AMI MegaRAID controller > (SCSI), and none of the drives in the array are degraded, that can't > really be the case. I'm suspecting a bug in the driver (though freebsd > 4.10 should be stable, right?) or a faulty cable or such. Yes, usually it means the device is not responding to requests. What kind of container is your swap in? Mirror? Stripe? > What would mitigate the problem for now though would be to have a way to > reboot the system. I'm about 1000 miles away from the box, so I can't go > there, but I do have access via serial console (which is where I'm > getting these messages). [...] > Entering the kernel debugger might help, though I'm actually not sure if > it's compiled into the running kernel. But if it is, how can I get to it > via serial? If you built the kernel with 'options BREAK_TO_DEBUGGER', then a serial break will drop to ddb. From there you could do 'call boot(0)' to attempt and orderly shutdown, or 'reset' to, well, reset :) There's also an 'ALT_BREAK_TO_DEBUGGER' option that emulates the sun alt-break -- [cr] ~ ^B. Without either of those, though, maybe you should call someone nearby and entice them to press some buttons for you :) -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org