From owner-freebsd-stable@FreeBSD.ORG Tue Jan 14 09:25:44 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B6C64288 for ; Tue, 14 Jan 2014 09:25:44 +0000 (UTC) Received: from bay0-omc2-s16.bay0.hotmail.com (bay0-omc2-s16.bay0.hotmail.com [65.54.190.91]) by mx1.freebsd.org (Postfix) with ESMTP id A060110D5 for ; Tue, 14 Jan 2014 09:25:44 +0000 (UTC) Received: from BAY176-W40 ([65.54.190.123]) by bay0-omc2-s16.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Tue, 14 Jan 2014 01:24:39 -0800 X-TMN: [CPCp0LA/ZOQ1azDJ4Y76I7iTfmq29mHlucj33NgBKEU=] X-Originating-Email: [jl.dupont@outlook.com] Message-ID: From: Jean-Luc Dupont To: "freebsd-stable@freebsd.org" Subject: 10.0 RC5 panic after a clean buildworld on Hyper-V Date: Tue, 14 Jan 2014 09:24:38 +0000 Importance: Normal MIME-Version: 1.0 X-OriginalArrivalTime: 14 Jan 2014 09:24:39.0131 (UTC) FILETIME=[72DAA2B0:01CF110A] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.17 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Jan 2014 09:25:44 -0000 Hello=2C We are upgrading our ESX to Hyper-V=2C and all our virtual FreeBSD will b= e running on Hyper-V. For our POCs=2C we are testing all the releases of the 10.0 RCxx. I installed 10.0 RC5 on a new virtual machine running on Hyper-V. I svn checkout /base/stable/10 Without modifying neither the kernel nor the src.conf=2C I buildworld=2C bu= ildkernel=2C installkernel=2C installworld. After booting I had a kernel panic on attaching the storvsc. I don't remember having this panic on older RCs of the 10.0 Here is the bt (OCRed): cpuid =3D 0 KDB: stack backtrace: #0 0xffffffff808d1670 at kdb_backtrace+0x60 #1 0xffffffff80899045 at panic+0x155 #2 0xffffffff80c73672 at trap_fatal+0x3a2 #3 0xffffffff80c73949 at trap_pfault+0x2c9 #4 0xffffffff80c730d6 at trap+0x5e6 #5 0xffffffff80c5a462 at calltrap+0x8 #6 0xffffffff80885ff0 at __mtx_unlock_sleep+0x60 #7 0xffffffff80885b4a at unlock_mtx+0x2a #8 0xffffffff808a1c4e at _sleep+0x18e #9 0xffffffff802dc2be at cam_periph_runccb+0x9e #10 0xffffffff80cfe6f4 at storvsc_attach+0x6d4 #11 0xffffffff808c89e2 at device_attach+0x3a2 #12 0xffffffff80d0311b at hv_vmbus_child_deuice_register+0xdb #13 0xffffffff80d01a33 at vmbus_channel_process_offer+0x133 #14 0xffffffff80d01576 at work_item_callback+0x26 #15 0xffffffff808df406 at taskqueue_run_locked+0xe6 #16 0xffffffff808dfc88 at taskqueue_thread_loop+0xa8 #17 0xffffffff8086b11a at fork_exit+0x9a Uptime: 1s Automatic reboot in 15 seconds - press a key on the console to abort I tried to add hw.ata.disk_enable=3D1 in /boot/loader.conf without help. Thank you for any advice. Best regards =