From owner-freebsd-current@FreeBSD.ORG Fri Sep 28 05:34:21 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 A075916A418; Fri, 28 Sep 2007 05:34:21 +0000 (UTC) (envelope-from jpedras+freebsd-current@webvolution.net) Received: from mail.portrait.com (mail.portrait.com [64.171.32.41]) by mx1.freebsd.org (Postfix) with ESMTP id 6C76F13C455; Fri, 28 Sep 2007 05:34:21 +0000 (UTC) (envelope-from jpedras+freebsd-current@webvolution.net) Received: from teko.tafkap.priv (beastie.webvolution.net [64.174.136.225]) (authenticated bits=0) by mail.portrait.com (8.13.1/8.13.1) with ESMTP id l8S5JiIx021881 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 27 Sep 2007 22:19:48 -0700 (PDT) (envelope-from jpedras+freebsd-current@webvolution.net) Message-ID: <46FC8EEE.5080908@webvolution.net> Date: Thu, 27 Sep 2007 22:19:42 -0700 From: Joao Pedras User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: Kris Kennaway References: <46FA0C14.10201@webvolution.net> <46FADB35.2090708@FreeBSD.org> <46FC2AA7.2040308@webvolution.net> <46FC2C85.4080600@FreeBSD.org> In-Reply-To: <46FC2C85.4080600@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=0.1 required=3.0 tests=FORGED_RCVD_HELO X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on mail.portrait.com 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: Fri, 28 Sep 2007 05:34:21 -0000 Kris Kennaway wrote: > Joao Pedras wrote: >> Hi again, >> >> hope this info sheds some light on this. A similar system is getting >> setup to reproduce the problem there as well. >> >> Thanks! >> >> Joao >> >> Kris Kennaway wrote: >>> 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 >>> > > Well that's a start, but you need to trace other processes too, e.g. the > running ones. Do an 'alltrace' to trace everything. > > Kris > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" Thank you for your help Kris. I am not very familiar with these tasks. I got the 'alltrace' and I also saved a crash dump. The session output is here http://pedras.webvolution.net/s2932-9.txt. I was able to reproduce the issue on a similar system (a vanilla Tyan S2932, one SATA disc only) and it exhibits the exact same problem. Thanks again. Joao