NetBSD Problem Report #52764

From www@NetBSD.org  Sun Nov 26 16:57:05 2017
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 629E97A1B7
	for <gnats-bugs@gnats.NetBSD.org>; Sun, 26 Nov 2017 16:57:05 +0000 (UTC)
Message-Id: <20171126165704.647E77A1EC@mollari.NetBSD.org>
Date: Sun, 26 Nov 2017 16:57:04 +0000 (UTC)
From: alnsn@NetBSD.org
Reply-To: alnsn@NetBSD.org
To: gnats-bugs@NetBSD.org
Subject: NetBSD 8.0_BETA crashed - ipmi0: workqueue busy: updates stopped
X-Send-Pr-Version: www-1.0

>Number:         52764
>Category:       kern
>Synopsis:       NetBSD 8.0_BETA crashed - ipmi0: workqueue busy: updates stopped
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sun Nov 26 17:00:00 +0000 2017
>Originator:     Alexander Nasonov
>Release:        NetBSD 8.0_BETA (GENERIC.201711180940Z)
>Organization:
XMM SWAP LTD
>Environment:
NetBSD hostname 8.0_BETA NetBSD 8.0_BETA (GENERIC.201711180940Z) amd64
>Description:
I tried to boot NetBSD from Linux ext2 partition on a rented server. It didn't boot because it couldn't find a root device and the kernel prompted me for a root device. The system crashed when I was typing it (IPMI virtual keyboard is really bad - I have to press one button many times before it get echoed on the screen).

The hosting company (OVH) has an automatic fault detection. It a host is down, they start intervention. They probably started doing something over ipmi and it crashed the kernel.

boot device: <unknown>
root device: raid0
use one of: dk0 dk1 dk2 dk3 dk4 dk5 dk6 dk7 wm0 wm1 wd0[a-p] wedge:primary ... other wedges ... ddb halt reboot
root device: ipmi0: workqueue busy: updates stopped
panic: usbd_transfer: not done
fatal breakpoint trap in supervisor mode
trap type 1 code 0 rip 0xffffffff80224a05 cs 0x8 rflags 0x246 cr2 0 ilevel 0 rsp 0xffffe8139e8dcf0
Stopped in pid 0.62 (system) at netbsd:breakpoint+0x5:    leave
db{1}>

I later booted it in a multiuser mode and copied dmesg to https://www.netbsd.org/~alnsn/ovh-dmesg-netbsd8.out

>How-To-Repeat:
It may be reproducible but I don't want to annoy OVH stuff. A real human looks at my console every time I mess up my setup.
>Fix:

Home	PR Database Search