From owner-freebsd-current@FreeBSD.ORG Sun Dec 28 06:13:31 2003 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 8B46016A4CE for ; Sun, 28 Dec 2003 06:13:31 -0800 (PST) Received: from email07.aon.at (WARSL402PIP8.highway.telekom.at [195.3.96.97]) by mx1.FreeBSD.org (Postfix) with SMTP id 1620B43D3F for ; Sun, 28 Dec 2003 06:13:30 -0800 (PST) (envelope-from shoesoft@gmx.net) Received: (qmail 184214 invoked from network); 28 Dec 2003 13:41:37 -0000 Received: from m094p012.dipool.highway.telekom.at (HELO ?62.46.1.172?) ([62.46.1.172]) (envelope-sender ) by 172.18.5.236 (qmail-ldap-1.03) with SMTP for ; 28 Dec 2003 13:41:37 -0000 From: Stefan Ehmann To: current@freebsd.org Content-Type: text/plain Message-Id: <1072618904.757.12.camel@shoeserv.freebsd> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 Date: Sun, 28 Dec 2003 14:41:45 +0100 Content-Transfer-Encoding: 7bit Subject: page fault panic tracked down (selwakeuppri()) 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: Sun, 28 Dec 2003 14:13:31 -0000 Some weeks ago I posted about a panic in 5.2-BETA. After accessing a read-only ext2fs for some hours I got a "page fault" panic (or rarely a "getblk: size(7537385) > MAXBSIZE(65536)"). The backtrace was always somewhat different. You can read about it a bit more detailed here: http://lists.freebsd.org/pipermail/freebsd-current/2003-November/015405.html After lots of buildworld and buildkernel I finally was able to detect the commit that caused this panic. Current from 2003.11.09.09.00.00 runs fine for > 10 hours. Current from 2003.11.09.09.20.00 crashed twice within less than 2 hours. The only src/sys commit in that time is http://lists.freebsd.org/pipermail/cvs-src/2003-November/013515.html where selwakeup()s is replaced with selwakeuppri(). So the problem must be somewhere in selwakeuppri(). I hope this can be resolved now.