From owner-freebsd-current@FreeBSD.ORG Tue Nov 22 13:10:31 2005 Return-Path: X-Original-To: freebsd-current@FreeBSD.org 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 C095916A420; Tue, 22 Nov 2005 13:10:31 +0000 (GMT) (envelope-from gavin.atkinson@ury.york.ac.uk) Received: from mail-gw1.york.ac.uk (mail-gw1.york.ac.uk [144.32.128.246]) by mx1.FreeBSD.org (Postfix) with ESMTP id E0E4F43D88; Tue, 22 Nov 2005 13:09:59 +0000 (GMT) (envelope-from gavin.atkinson@ury.york.ac.uk) Received: from buffy.york.ac.uk (buffy-128.york.ac.uk [144.32.128.160]) by mail-gw1.york.ac.uk (8.12.10/8.12.10) with ESMTP id jAMD9uSR005041; Tue, 22 Nov 2005 13:09:56 GMT Received: from buffy.york.ac.uk (localhost [127.0.0.1]) by buffy.york.ac.uk (8.13.4/8.13.4) with ESMTP id jAMD9uLG017455; Tue, 22 Nov 2005 13:09:56 GMT (envelope-from gavin.atkinson@ury.york.ac.uk) Received: (from ga9@localhost) by buffy.york.ac.uk (8.13.4/8.13.4/Submit) id jAMD9tiA017454; Tue, 22 Nov 2005 13:09:55 GMT (envelope-from gavin.atkinson@ury.york.ac.uk) X-Authentication-Warning: buffy.york.ac.uk: ga9 set sender to gavin.atkinson@ury.york.ac.uk using -f From: Gavin Atkinson To: John Baldwin In-Reply-To: <200510061355.56903.jhb@FreeBSD.org> References: <1123588622.893.15.camel@buffy.york.ac.uk> <200509291210.38799.jhb@FreeBSD.org> <1128598440.25106.13.camel@buffy.york.ac.uk> <200510061355.56903.jhb@FreeBSD.org> Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Tue, 22 Nov 2005 13:09:55 +0000 Message-Id: <1132664995.12635.8.camel@buffy.york.ac.uk> Mime-Version: 1.0 X-Mailer: Evolution 2.2.3 FreeBSD GNOME Team Port X-York-MailScanner: Found to be clean X-York-MailScanner-From: gavin.atkinson@ury.york.ac.uk Cc: freebsd-current@FreeBSD.org Subject: Re: 6.0-BETA2 DRM/witness panic: Assertion j < 1000 failed at /usr/src/sys/kern/subr_witness.c:1513 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: Tue, 22 Nov 2005 13:10:32 -0000 [posted to -current rather than stable as the rest of the thread started before 6.0 was released] On Thu, 2005-10-06 at 13:55 -0400, John Baldwin wrote: > On Thursday 06 October 2005 07:34 am, Gavin Atkinson wrote: > > On Thu, 2005-09-29 at 12:10 -0400, John Baldwin wrote: > > > On Tuesday 09 August 2005 12:02 pm, Gavin Atkinson wrote: > > > > On Tue, 2005-08-09 at 10:50 -0400, John Baldwin wrote: > > > > > On Tuesday 09 August 2005 07:57 am, Gavin Atkinson wrote: > > > > > > Hi, > > > > > > > > > > > > I have a regular panic (3 times a day) on a system running > > > > > > 6.0-BETA2 which was very stable under 5.4. dmesg available at > > > > > > http://www.devrandom.co.uk/freebsd/dmesg-buffy-20050809 . The panic > > > > > > seems to relate to DRM, I have a ATI Radeon QY RV100 7000/VE card. > > > > > > > > > > Do a 'show witness', it looks like witness has a cycle somehow. > > > > > Normally these can only occur if there is a cycle in the static lock > > > > > order. > > > > > > > > http://www.devrandom.co.uk/freebsd/sh-witness-buffy-20050809 > > > > > > > > Gavin > > > > > > Do you still get this panic on more recent 6.0? > > > > I've been running a 6.0 from Friday for a week now without seeing this > > panic, so I suspect it's fixed. However, I don't remember seeing any > > commits which look like they were responsible for fixing it, is it > > possible that it's just been masked by some other commit? I'm happy to > > step back and find the responsible commit, unless you're happy that it > > was fixed for certain. > > > > Gavin > > Well, I'm not sure how you could even have triggered the panic in the first > place. If you can't reproduce it that is fine with me for now. Sadly, it looks like I spoke too soon. Since this last email, I was happily running with the kernel mentioned above without any problems, and an uptime of 40 days with the screensavers that used to trigger it running all night. I rebooted my machine a couple of days ago, and since then (and with the exact same kernel/world) the panic is back. I've updated the machine to 6-STABLE but the panic remains. I guess I was just lucky in my month without panics - they definitely still exist. I wonder if the fact that it survived so long means anything - e.g. is it a failure to initialise something that just by chance was initialised correctly that time? I'm happy to do any more investigating that you want. Gavin