From owner-freebsd-current@FreeBSD.ORG Tue Dec 27 20:27:21 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org 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 9080416A41F for ; Tue, 27 Dec 2005 20:27:21 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6EA6D43D7E for ; Tue, 27 Dec 2005 20:27:20 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.13.4/8.13.4) with ESMTP id jBRKRKYm000778 for ; Tue, 27 Dec 2005 12:27:20 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.13.4/8.13.1/Submit) id jBRKRKR2000777 for freebsd-current@freebsd.org; Tue, 27 Dec 2005 12:27:20 -0800 (PST) (envelope-from sgk) Date: Tue, 27 Dec 2005 12:27:20 -0800 From: Steve Kargl To: freebsd-current@freebsd.org Message-ID: <20051227202719.GA628@troutmask.apl.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Subject: uma_zalloc_arg panic! 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: Tue, 27 Dec 2005 20:27:21 -0000 Seems my recent post about the extremely slow probing of fxp0 during boot (6+ minutes) went unnoticed. The slow probing has now manfest itself as a panic. uma_zalloc_arg+0x12a lock pop db> trace Tracing pid 0 tid 0 td 0xffffffff8062ff20 uma_zalloc_arg at ... +0.12a vm_map_entry_create at ... +0x23 vm_map_insert at ... +0x258 contigmalloc2 at ... +0xc1 contigmalloc at ... +0xe2 alloc_bounce_pages at ... 0x81 bus_dmamap_create at ... 0x145 fxp_attach at ... 0xc64 I'll also note the recent rototilling of mount has rendered my back up kernels useless because it is no longer possible to mount my filesystems. Booting to single user mode is fine. At the # prompt: # fsck -y # mount -a mount: unknown option # mount -f -a mount: unknown option -- Steve