From owner-freebsd-current@FreeBSD.ORG Sun Aug 29 05:59:37 2004 Return-Path: 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 90F6C16A4CE for ; Sun, 29 Aug 2004 05:59:37 +0000 (GMT) Received: from black.imgsrc.co.jp (black.imgsrc.co.jp [210.226.20.147]) by mx1.FreeBSD.org (Postfix) with ESMTP id F35C043D48 for ; Sun, 29 Aug 2004 05:59:36 +0000 (GMT) (envelope-from kuriyama@imgsrc.co.jp) Received: from localhost (localhost [127.0.0.1]) by black.imgsrc.co.jp (Postfix) with ESMTP id D865650BD6; Sun, 29 Aug 2004 14:59:35 +0900 (JST) Received: from black.imgsrc.co.jp (black.imgsrc.co.jp [IPv6:2001:218:422:2::9999]) by black.imgsrc.co.jp (Postfix) with ESMTP id 4605D50BC0; Sun, 29 Aug 2004 14:59:34 +0900 (JST) Date: Sun, 29 Aug 2004 14:59:34 +0900 Message-ID: <7meklq4h89.wl@black.imgsrc.co.jp> From: Jun Kuriyama To: "Poul-Henning Kamp" In-Reply-To: <3181.1093688358@critter.freebsd.dk> References: <7mk6vj4lis.wl@black.imgsrc.co.jp> <3181.1093688358@critter.freebsd.dk> User-Agent: Wanderlust/2.10.1 (Watching The Wheels) SEMI/1.14.6 (Maruoka) FLIM/1.14.6 (Marutamachi) APEL/10.6 Emacs/21.3 (i386--freebsd) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII X-Virus-Scanned: by amavisd 0.1 cc: Current Subject: Re: Hang at probing on VMware installation X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Sun, 29 Aug 2004 05:59:37 -0000 At Sat, 28 Aug 2004 10:20:09 +0000 (UTC), Poul-Henning Kamp wrote: > >VMware said "unrecoverable error" and "Exception 0xc0000005 {access > >violation} has occured" and virtual machine has stopped. > > Is there any way to get mode detailed diagnostics ? Like the > program counter or anything ? In fdc_initial_reset() shows here: ----- fdc0: at port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on isa2 ----- Actual hang up is in loop in device_probe_and_attach(). With BUS_DEBUG, final output is here: ----- device_probe_child:1556: Start find loop device_probe_child:1561: Trying bt devclass_find_internal:752: looking for bt devclass_add_device:1225: (null) in devclass bt devclass_alloc_unit:1158: unit -1 in devclass bt devclass_alloc_unit:1198: now: unit 1 in devclass bt devclass_delete_device:1264: bt in devclass bt device_probe_child:1561: Trying cbb devclass_find_internal:752: looking for cbb devclass_add_device:1225: (null) in devclass cbb devclass_alloc_unit:1158: unit -1 in devclass cbb devclass_alllass cbb device_probe_child:1561: Trying sn devclass_t:1158: unit -1 in devclass sn devclass_alloc_unit:1198: now: unit 1 in devclass sn devclass_delete_device:1264: sn in devclass sn device_probe_child:1561: Trying stg devclass_find_internal:752: looking for stg devclass_add_device:1225: (null) in devclass stg devclass_alloc_unit:1158: unit -1 in devclass stg devclass_alloc_unit:1198: now: unit 0 in devclass stg ----- This is called from isa_probe_children(), isa_assign_resources(i=40) returns true, device_probe_and_attach(). Where should I check next? Inside of device_probe_child() or resouce allocation area more ealier stage? -- Jun Kuriyama // IMG SRC, Inc. // FreeBSD Project