From owner-freebsd-current@FreeBSD.ORG Sat Jun 12 10:09:51 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 14A1616A4CE for ; Sat, 12 Jun 2004 10:09:51 +0000 (GMT) Received: from anduin.net (anduin.net [212.12.46.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id BF93843D2D for ; Sat, 12 Jun 2004 10:09:50 +0000 (GMT) (envelope-from ltning@anduin.net) Received: from mailnull by anduin.net with spam-scanned (Exim 4.34; FreeBSD) id 1BZ5Rk-000Fjw-90 for current@freebsd.org; Sat, 12 Jun 2004 12:09:18 +0200 Received: from [217.8.136.185] (helo=[192.168.1.10]) by anduin.net with esmtp (Exim 4.34; FreeBSD) id 1BZ5Rj-000Fjt-UD for current@freebsd.org; Sat, 12 Jun 2004 12:09:08 +0200 Message-ID: <40CAD634.8060808@anduin.net> Date: Sat, 12 Jun 2004 12:08:52 +0200 From: Eirik Oeverby User-Agent: Mozilla Thunderbird 0.6 (X11/20040504) X-Accept-Language: en-us, en MIME-Version: 1.0 To: current@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on anduin.net X-Spam-Status: No, hits=0.0 required=7.5 tests=none autolearn=no version=2.63 X-Spam-Level: Subject: 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 10:09:51 -0000 Hi all, 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. 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). I'm using minicom, but could use any other serial comms package on FreeBSD. Not sure if C-A-D would help, but as I don't know how to push that keycombo through minicom anyway, I'm kinda stuck. The box is replying to pings but no other services are available. The console is also 'dead', i.e. i can't get any command prompts or login prompt. Only these messages who keep showing up, about 1 per second. 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? Anyone? Thanks, /Eirik