From owner-freebsd-stable@freebsd.org Tue Jan 19 14:40:06 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2A76CA87105; Tue, 19 Jan 2016 14:40:06 +0000 (UTC) (envelope-from ml@netfence.it) Received: from smtp207.alice.it (smtp207.alice.it [82.57.200.103]) by mx1.freebsd.org (Postfix) with ESMTP id B84A31C70; Tue, 19 Jan 2016 14:40:05 +0000 (UTC) (envelope-from ml@netfence.it) Received: from soth.ventu (79.42.55.85) by smtp207.alice.it (8.6.060.28) (authenticated as acanedi@alice.it) id 562CAA6911DAB765; Tue, 19 Jan 2016 15:39:58 +0100 Received: from alamar.ventu (alamar.ventu [10.1.2.18]) by soth.ventu (8.15.2/8.14.9) with ESMTP id u0JEdtNA074539; Tue, 19 Jan 2016 15:39:56 +0100 (CET) (envelope-from ml@netfence.it) Subject: Re: Panic with sym on 10.2 To: freebsd-questions@freebsd.org References: <569E368F.4060802@netfence.it> <569E45D9.1050604@freebsd.org> Cc: freebsd-stable@freebsd.org Reply-To: freebsd-stable@freebsd.org From: Andrea Venturoli Message-ID: <569E4ABB.9070903@netfence.it> Date: Tue, 19 Jan 2016 15:39:55 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:38.0) Gecko/20100101 Thunderbird/38.5.0 MIME-Version: 1.0 In-Reply-To: <569E45D9.1050604@freebsd.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Jan 2016 14:40:06 -0000 On 01/19/16 15:19, Matthew Seaman wrote: > On 01/19/16 13:13, Andrea Venturoli wrote: >> Two days ago I upgraded a (perfectly working) 9.3/i386 box to 10.2p10 >> Since then I've had two panics with the following message: >> >> panic: assertion "lp->busy_itl==0&&lp->busy_itlq==0" failed: file >> /usr/src/sys/dev/sym/sym_hipd.c >> >> Since the disk controller is involved, I do not get any core and I have >> to press the reset button. >> >> Google showed up no results (I'm not using ZFS, btw) and Bugzilla didn't >> help either. >> >> Any hint on where to go from here? > > I recommend asking about this on freebsd-stable@... I'm cc:ing and reply-to:ing :) it now. > and/or raising a PR in bugzilla. I'd gladly do this, but I though I'd ask for some direction before, since, right now, I have very few details. > If there's any more information you can pull out of your > system, that would probably be helpful Something in particular? The only thing that comes to my mind is the following: > # pciconf -lv > ... > sym0@pci0:3:5:0: class=0x010000 card=0x39071de1 chip=0x000c1000 rev=0x01 hdr=0x00 > vendor = 'LSI Logic / Symbios Logic' > device = '53c895' > class = mass storage > subclass = SCSI The card really is a Tekram DC-390U2W. Oh, and I'm using gmirror with a couple of disks. There's also a zip drive attached (which has always worked), but I've not been using it in the last three days, so it was not "active" when the system paniced. >-- even if it's a case of taking > a photo of your screen and sticking it on a pasteboard site somewhere. Not much to see, really: the above message (which should be *almost* exact, since I copied it by hand) and a backtrace which doesn't mean much. Nothing else. > Hmmm... sym(4) looks like it's fairly elderly, implying the same is > probably true of your hardware. Sure. > Is it possible your disk controller is succumbing to the vagaries of age? I have never seen any little trouble with such a card (I've had more than one here and at customers'); thought it might actually be dying, I really find it strange that it started as soon as I upgraded from 9.3 to 10.2... bye & Thanks a lot av.