From owner-freebsd-amd64@FreeBSD.ORG Fri May 28 13:10:01 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 4CF231065677 for ; Fri, 28 May 2010 13:10:01 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (unknown [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id ED98E8FC13 for ; Fri, 28 May 2010 13:10:00 +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 o4SDA0Rh012163 for ; Fri, 28 May 2010 13:10:00 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o4SDA0PA012162; Fri, 28 May 2010 13:10:00 GMT (envelope-from gnats) Resent-Date: Fri, 28 May 2010 13:10:00 GMT Resent-Message-Id: <201005281310.o4SDA0PA012162@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-amd64@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Tom Dewaele Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 05581106567B for ; Fri, 28 May 2010 13:06:13 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (www.freebsd.org [IPv6:2001:4f8:fff6::21]) by mx1.freebsd.org (Postfix) with ESMTP id E8FD78FC14 for ; Fri, 28 May 2010 13:06:12 +0000 (UTC) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.14.3/8.14.3) with ESMTP id o4SD6B1t073249 for ; Fri, 28 May 2010 13:06:11 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.14.3/8.14.3/Submit) id o4SD6BvN073233; Fri, 28 May 2010 13:06:11 GMT (envelope-from nobody) Message-Id: <201005281306.o4SD6BvN073233@www.freebsd.org> Date: Fri, 28 May 2010 13:06:11 GMT From: Tom Dewaele To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.1 X-Mailman-Approved-At: Fri, 28 May 2010 13:41:13 +0000 Cc: Subject: amd64/147162: Page Fault / Kernel panic when jail starts on boot X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 May 2010 13:10:01 -0000 >Number: 147162 >Category: amd64 >Synopsis: Page Fault / Kernel panic when jail starts on boot >Confidential: no >Severity: serious >Priority: low >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri May 28 13:10:00 UTC 2010 >Closed-Date: >Last-Modified: >Originator: Tom Dewaele >Release: FreeBSD 8.0p3 AMD64 >Organization: ABVV >Environment: FreeBSD T00FVS01.fed.diva.net 8.0-RELEASE-p3 FreeBSD 8.0-RELEASE-p3 #0: Tue May 25 20:54:11 UTC 2010 root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 >Description: A short system explanation: Hardware: HP DL 360G6 2x E5504 / 8GB I'am running 3 jails on this server with ezjail (latest port) I've updated from 8.0p2 to 8.0p3 yesterday. After reboot the server did not come back. It showed a page fault crash on the console after ezjail started the first jail. The page fault happen with the 'ping' proces. The jail that started and crashed the system is a network monitoring server with several ping scripts. I have "security.jail.allow_raw_sockets=1" active on the system to allow this. I had to reboot in single user mode and disable the autostart of my jails. I've updated all jails to 8.0p3 (with ezjail - update binary via FTP) and rebuilt all ports to make sure that this was not the issue. That did not solve my problem. However, once the system is booted, I can start the jails via ezjail with crashing. The crash only happens when the jails start on boot. I think this is caused by the security fixes in p3 for the jail system. I've never had this problem before this. >How-To-Repeat: It happens everytime I boot with ezjail_enable="YES". After the first jail start, the system goes down with kernel panic / page fault. >Fix: I does not happen when I start the jails manually using ezjail-admin onestart [jail] >Release-Note: >Audit-Trail: >Unformatted: