From owner-freebsd-amd64@FreeBSD.ORG Wed Dec 19 01:50:01 2012 Return-Path: Delivered-To: freebsd-amd64@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8257C3B6 for ; Wed, 19 Dec 2012 01:50:01 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 641848FC12 for ; Wed, 19 Dec 2012 01:50:01 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id qBJ1o13v050209 for ; Wed, 19 Dec 2012 01:50:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id qBJ1o1CC050204; Wed, 19 Dec 2012 01:50:01 GMT (envelope-from gnats) Date: Wed, 19 Dec 2012 01:50:01 GMT Message-Id: <201212190150.qBJ1o1CC050204@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org Cc: From: KAHO Toshikazu Subject: Re: amd64/174409: stopping during resume caused by io_apic.c change(r243764) X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: KAHO Toshikazu List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Dec 2012 01:50:01 -0000 The following reply was made to PR amd64/174409; it has been noted by GNATS. From: KAHO Toshikazu To: Andriy Gapon Cc: bug-followup@freebsd.org Subject: Re: amd64/174409: stopping during resume caused by io_apic.c change(r243764) Date: Wed, 19 Dec 2012 10:47:26 +0900 Hello, > Are you set up for crash dumps (minidumps are ok) ? > Could you please add a call to panic("ioapic_resume"); at the beginning of > ioapic_resume function in sys/x86/x86/io_apic.c and save a crash dump for debugging? The machine now panics, but any keyboard operation makes nothing in debugger. If sysctl debug.debugger_on_panic=0 , kernel was trying to save a dump but failed by ahci error. All devices seem to be sleeping yet. -- kaho@elam.kais.kyoto-u.ac.jp