From owner-freebsd-current@FreeBSD.ORG Wed Sep 26 22:20:35 2007 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 C8D1316A421 for ; Wed, 26 Sep 2007 22:20:35 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx1.freebsd.org (Postfix) with ESMTP id DF8BC13C467; Wed, 26 Sep 2007 22:20:34 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <46FADB35.2090708@FreeBSD.org> Date: Thu, 27 Sep 2007 00:20:37 +0200 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: Joao Pedras References: <46FA0C14.10201@webvolution.net> In-Reply-To: <46FA0C14.10201@webvolution.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: lock up 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: Wed, 26 Sep 2007 22:20:35 -0000 Joao Pedras wrote: > Greetings all! > > A system (Tyan S2932) I am testing CURRENT amd64 with is experiencing a > strange lock up. No panic, not much on the console, just a lock up, freeze. > > I first noticed the issue while tailing a build in a ssh session over a > vpn connection. On the local network the issue doesn't seem to occur. > I can reproduce the lock up all the time. > > Last I tried, the system was running CURRENT from a couple hours ago. > > I have tried: > > - 4BSD and ULE > - switching network cards > - taking the IPMI card out (seems to work locally with freeipmi and > ipmitoll remotely) > - enabled/disabled "redirection after post" (BIOS setting) > - without debug > - without IPv6 and friends (see rtfree below) > > dmesg and pciconf attached. The dmesg is after a lock up. > rtfree pops a few times before the lock up. I noticed from a recent post > some action was taken and the related patch is there (ie. today's CURRENT). > > The system had a fresh install this past weekend and the LSI MegaRAID > array doesn't contain any data, it is just mounted. The system boots off > the onboard LSI SAS (couple disks in RAID 1). > > Thank you for your input. Break to DDB and obtain process traces, etc. See the developers handbook. Kris