From owner-freebsd-amd64@FreeBSD.ORG Mon Dec 6 16:40:10 2010 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 053BB1065672 for ; Mon, 6 Dec 2010 16:40:10 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id E485D8FC28 for ; Mon, 6 Dec 2010 16:40:09 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id oB6Ge9p1015209 for ; Mon, 6 Dec 2010 16:40:09 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id oB6Ge9S2015207; Mon, 6 Dec 2010 16:40:09 GMT (envelope-from gnats) Date: Mon, 6 Dec 2010 16:40:09 GMT Message-Id: <201012061640.oB6Ge9S2015207@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: "Kenneth D. Merry" X-Mailman-Approved-At: Mon, 06 Dec 2010 16:45:37 +0000 Cc: Subject: Re: amd64/131314: [modules] [panic] large modules fail to load on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: "Kenneth D. Merry" List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Dec 2010 16:40:10 -0000 The following reply was made to PR amd64/131314; it has been noted by GNATS. From: "Kenneth D. Merry" To: Andriy Gapon Cc: bug-followup@freebsd.org Subject: Re: amd64/131314: [modules] [panic] large modules fail to load on amd64 Date: Mon, 6 Dec 2010 09:11:39 -0700 On Sun, Dec 05, 2010 at 14:19:07 +0200, Andriy Gapon wrote: > > Ken, > > this is an interesting problem. Are you able to reproduce it still? > I think that something like that should be easily debuggable. Unfortunately, no. I no longer have access to the codebase that was generating the problem. (It was at my previous job.) But, you may be able to reproduce the problem by putting a very large global variable/table in the kernel and see what happens. As I mentioned in the bug report, I made the problem go away by taking out that table. Ken -- Kenneth Merry ken@FreeBSD.ORG