NetBSD Problem Report #53621

From gson@gson.org  Thu Sep 20 08:48:57 2018
Return-Path: <gson@gson.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 380167A152
	for <gnats-bugs@gnats.NetBSD.org>; Thu, 20 Sep 2018 08:48:57 +0000 (UTC)
Message-Id: <20180920084853.7DFB8989F53@guava.gson.org>
Date: Thu, 20 Sep 2018 11:48:53 +0300 (EEST)
From: gson@gson.org (Andreas Gustafsson)
Reply-To: gson@gson.org (Andreas Gustafsson)
To: gnats-bugs@NetBSD.org
Subject: i386 panics on boot
X-Send-Pr-Version: 3.95

>Number:         53621
>Category:       port-i386
>Synopsis:       i386 panics on boot
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    port-i386-maintainer
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Sep 20 08:50:00 +0000 2018
>Last-Modified:  Fri Sep 21 10:15:01 +0000 2018
>Originator:     Andreas Gustafsson
>Release:        NetBSD-current, source date 2018.09.20.06.54.36
>Organization:
>Environment:
System: NetBSD
Architecture: i386
Machine: i386
>Description:

I tried to boot a -current/i386 kernel on the old Pentium-class
machine of PR 52569 to check whether said PR has been fixed, but
the machine paniced on boot.

Here's a brief summary of the backtrace manually transcribed from
the VGA console:

vpanic()
__x86_indirect_thunk_edx()
cv_signal()
fdcintr1()
fdcintr()
intr_biglock_wrapper()
-- switch to interrupt stack ---
Xintr_legacy6()
--- interrupt ---
outb()
intr_establish_xname()
(etc)

Full backtrace:

http://www.gson.org/netbsd/bugs/i386-panic/5.jpg
http://www.gson.org/netbsd/bugs/i386-panic/6.jpg
http://www.gson.org/netbsd/bugs/i386-panic/7.jpg

For a dmesg from a successful boot with an older -current, see PR 52553.

>How-To-Repeat:

>Fix:

>Audit-Trail:
From: Andreas Gustafsson <gson@gson.org>
To: gnats-bugs@NetBSD.org
Cc: nat@NetBSD.org, cherry@zyx.in
Subject: Re: port-i386/53621: i386 panics on boot
Date: Fri, 21 Sep 2018 13:10:18 +0300

 I bisected this, and according to the bisection, the problem started
 with nat's commit of src/sys/dev/isa/sbdsp.c 1.137 on CVS source date
 2017.11.04.01.46.56.

 This is weird because the backtrace of the panic looks like it happens
 in the interrupt setup of the fd driver, and the sb driver does not
 appear in the backtrace.  However, another piece of evidence pointing
 towards sb is that using "boot -c" and "disable sb0" successfully
 boots kernels that otherwise panic.
 -- 
 Andreas Gustafsson, gson@gson.org

Home	PR Database Search