From owner-freebsd-current@freebsd.org Thu Dec 3 22:09:02 2015 Return-Path: Delivered-To: freebsd-current@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 9C6C7A403A8 for ; Thu, 3 Dec 2015 22:09:02 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-annu.net.uoguelph.ca (esa-annu.mail.uoguelph.ca [131.104.91.36]) by mx1.freebsd.org (Postfix) with ESMTP id 531A118E8 for ; Thu, 3 Dec 2015 22:09:01 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) IronPort-PHdr: 9a23:d7BVcx0qnRNEzPqOsmDT+DRfVm0co7zxezQtwd8ZsegeKvad9pjvdHbS+e9qxAeQG96LtbQc06L/iOPJZy8p2d65qncMcZhBBVcuqP49uEgeOvODElDxN/XwbiY3T4xoXV5h+GynYwAOQJ6tL2PbrnD61zMOABK3bVMzfbSrXNaKx+2MlMmMuLTrKz1SgzS8Zb4gZD6Xli728vcsvI15N6wqwQHIqHYbM85fxGdvOE7B102kvpT41NdZ/i9Ro/Ms8dJbGeW/JvxgDO8QMDNzHXo46efQmVHoUBGV630AGjEYiBdFCRPJqRrnRI38tDfSuPBw1SOBMYvxV79iChq46KI+ch7ji28iPjU69GzSwphqiatQoxasojRixIHJbYWNNLx1d/WOLpshWWNdU5MJBGR6CYSmYt5KVrJZMA== X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A2ClBACivGBW/61jaINehQG9SYFuhg6CChIBAQEBAQEBAYEJgi2CDiMEZAEiAg0ZAlsEiEKhKo9wkQ8BIIEBhVOMdIFEBY4fiEKPF4RDiRSNOQIoCDOEIiCFHIEHAQEB X-IronPort-AV: E=Sophos;i="5.20,378,1444708800"; d="scan'208";a="255652194" Received: from nipigon.cs.uoguelph.ca (HELO zcs1.mail.uoguelph.ca) ([131.104.99.173]) by esa-annu.net.uoguelph.ca with ESMTP; 03 Dec 2015 17:08:28 -0500 Received: from localhost (localhost [127.0.0.1]) by zcs1.mail.uoguelph.ca (Postfix) with ESMTP id 4BB7515F55D for ; Thu, 3 Dec 2015 17:08:28 -0500 (EST) Received: from zcs1.mail.uoguelph.ca ([127.0.0.1]) by localhost (zcs1.mail.uoguelph.ca [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id bWfGHbKSc3c5 for ; Thu, 3 Dec 2015 17:08:27 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by zcs1.mail.uoguelph.ca (Postfix) with ESMTP id C2F0715F565 for ; Thu, 3 Dec 2015 17:08:27 -0500 (EST) X-Virus-Scanned: amavisd-new at zcs1.mail.uoguelph.ca Received: from zcs1.mail.uoguelph.ca ([127.0.0.1]) by localhost (zcs1.mail.uoguelph.ca [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id hGosNfDuJhCY for ; Thu, 3 Dec 2015 17:08:27 -0500 (EST) Received: from zcs1.mail.uoguelph.ca (zcs1.mail.uoguelph.ca [172.17.95.18]) by zcs1.mail.uoguelph.ca (Postfix) with ESMTP id AABD915F55D for ; Thu, 3 Dec 2015 17:08:27 -0500 (EST) Date: Thu, 3 Dec 2015 17:08:27 -0500 (EST) From: Rick Macklem To: FreeBSD Current Message-ID: <802637848.117955972.1449180507630.JavaMail.zimbra@uoguelph.ca> Subject: panic "ffs_checkblk: bad block" on recent -head kernels MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [172.17.95.11] X-Mailer: Zimbra 8.0.9_GA_6191 (ZimbraWebClient - FF34 (Win)/8.0.9_GA_6191) Thread-Topic: panic "ffs_checkblk: bad block" on recent -head kernels Thread-Index: HFOmtZQEpjPZQDYHXdVQFZjdgDNGpg== X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 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: Thu, 03 Dec 2015 22:09:02 -0000 Hi, I get a fairly reproducible panic when doing a full kernel build on a 256Mbyte single core i386 when running recent kernels from -head. The panic is "ffs_checkblk: bad block ..". I don't actually have the block # (although I think it's just 0xfffffffffffffff, given the backtrace), because it runs off the screen. (I looked up the message via the debugger from the first arg. to panic.) Here's the backtrace without all the numbers: panic(c14f4b55, ffffffff, ffffffff, 0, 64,...) ffs_checkblk(ffffffff, 8000, fffffff9c, ffffffff, c4a02454,...) ffs_reallocblks VOP_REALLOCBLKS_APV cluster_write ffs_write VOP_WRITE_APV vn_write vn_io_fault_doio vn_io_fault1 vn_io_fault dofilewrite kern_writev sys_write syscall It doesn't happen on a kernel dated Sep. 30, but does happen on a Nov. 30 one. (I was away from home, so I didn't upgrade kernels for 2 months.) I am slowly doing a binary search for the first kernel rev. where it occurs, but since each build takes hours, it's going to take a while;-). At this point, it doesn't appear to happen on r289278 (just before jeff@'s buffer cache patch). With kernels between r289279-->r290480, I get into the "R" state that was fixed by r290481 before I get a crash. I tried reverting r289405 and r290047 from a recent kernel and the crashes still occurred, so it doesn't appear to be these commits. I am currently testing r290481 to see if the crash occurs for this rev. If anyone has some insight into which commit might cause this, please let me know. Also, if you want more info about if from "db", just let me know what you want, because I can reproduce it in a few hours. rick