From owner-freebsd-current@FreeBSD.ORG Thu Apr 23 17:09:54 2009 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 08BEC1065673 for ; Thu, 23 Apr 2009 17:09:54 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id CF9B68FC1C for ; Thu, 23 Apr 2009 17:09:53 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [65.122.17.41]) by cyrus.watson.org (Postfix) with ESMTPS id 71F1746B1A; Thu, 23 Apr 2009 13:09:53 -0400 (EDT) Date: Thu, 23 Apr 2009 18:09:53 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Arnar Mar Sig In-Reply-To: <91A2A3D2-C4F6-46EF-83A9-AA8CF58F54BF@valka.is> Message-ID: References: <49F072FB.1090404@yartv.ru> <91A2A3D2-C4F6-46EF-83A9-AA8CF58F54BF@valka.is> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="621616949-899222135-1240506593=:54334" Cc: =?KOI8-R?B?4c7E0sXKIOfSz9vF1w==?= , freebsd-current@freebsd.org Subject: Re: panic malloc_init: bad malloc type magic 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: Thu, 23 Apr 2009 17:09:54 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --621616949-899222135-1240506593=:54334 Content-Type: TEXT/PLAIN; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8BIT On Thu, 23 Apr 2009, Arnar Mar Sig wrote: > On Apr 23, 2009, at 4:47 PM, Marius Nünnerich wrote: >> On Thu, Apr 23, 2009 at 15:54, Андрей Грошев wrote: >>> Hello, people! Today the world has updated and now I get subj. Because of >>> what's going on? And how to locate the problems? >> >> Could you send a backtrace of the panic? > > Got the same panic yesterday after updating. > > I was able to boot with older kernel and build new from scratch (rm -rf > /usr/obj/*) that worked. I changed the size of "struct malloc_type", which is embedded in modules declaring new malloc types, on 19 April, r191267. However, I also changed __FreeBSD_version, which should cause updated kernels to reject older modules. If people are experiencing the panic, they should make sure all modules are in sync with their kernel. If it still occurs, it's probably a bug in the module's use of malloc(9), although it may be a bug in the malloc(9) sanity-checking I added. :-) Robert N M Watson Computer Laboratory University of Cambridge --621616949-899222135-1240506593=:54334--