NetBSD Problem Report #54034

From www@NetBSD.org  Sat Mar  2 23:27:36 2019
Return-Path: <www@NetBSD.org>
Received: from mail.netbsd.org (mail.netbsd.org [199.233.217.200])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(Client CN "mail.NetBSD.org", Issuer "mail.NetBSD.org CA" (not verified))
	by mollari.NetBSD.org (Postfix) with ESMTPS id 6A2F17A1B6
	for <gnats-bugs@gnats.NetBSD.org>; Sat,  2 Mar 2019 23:27:36 +0000 (UTC)
Message-Id: <20190302232735.97F237A1F7@mollari.NetBSD.org>
Date: Sat,  2 Mar 2019 23:27:35 +0000 (UTC)
From: thorpej@me.com
Reply-To: thorpej@me.com
To: gnats-bugs@NetBSD.org
Subject: Using "hme" driver with qemu-system-sparc64 results in hard-hang of guest
X-Send-Pr-Version: www-1.0

>Number:         54034
>Category:       port-sparc64
>Synopsis:       Using "hme" driver with qemu-system-sparc64 results in hard-hang of guest
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    port-sparc64-maintainer
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat Mar 02 23:30:00 +0000 2019
>Last-Modified:  Sun Mar 03 07:30:01 +0000 2019
>Originator:     Jason Thorpe
>Release:        NetBSD 8.99.34 / NetBSD 8.0
>Organization:
>Environment:
NetBSD sparc64-vm 8.99.34 NetBSD 8.99.34 (GENERIC) #0: Thu Feb 28 17:41:27 UTC 2019  mkrepro@mkrepro.NetBSD.org:/usr/src/sys/arch/sparc64/compile/GENERIC sparc64
>Description:
Under both NetBSD 8.0 and NetBSD 8.99.34, using the "hme" driver (which is the default Qemu network interface model) results in a hard hang of the guest.  Using the "ne2k_pci" interface type in Qemu works fine.

I don't know if this is a NetBSD bug or a Qemu bug.

>How-To-Repeat:
Use dhcpcd with the "hme" driver in a Qemu guest.
>Fix:
unknown.

>Audit-Trail:
From: Martin Husemann <martin@duskware.de>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: port-sparc64/54034: Using "hme" driver with qemu-system-sparc64
 results in hard-hang of guest
Date: Sun, 3 Mar 2019 08:29:48 +0100

 On Sat, Mar 02, 2019 at 11:30:00PM +0000, thorpej@me.com wrote:
 > I don't know if this is a NetBSD bug or a Qemu bug.

 qemu ;-)

Home	PR Database Search