From owner-freebsd-amd64@freebsd.org  Thu Feb 16 03:16:25 2017
Return-Path: <owner-freebsd-amd64@freebsd.org>
Delivered-To: freebsd-amd64@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id D1FDBCE0250
 for <freebsd-amd64@mailman.ysv.freebsd.org>;
 Thu, 16 Feb 2017 03:16:25 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id C1D1A360
 for <freebsd-amd64@FreeBSD.org>; Thu, 16 Feb 2017 03:16:25 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v1G3GPEt086573
 for <freebsd-amd64@FreeBSD.org>; Thu, 16 Feb 2017 03:16:25 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-amd64@FreeBSD.org
Subject: [Bug 217126] reading data from fat32 USB card spontaneously reboots
 system
Date: Thu, 16 Feb 2017 03:16:25 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 11.0-RELEASE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: cem@freebsd.org
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-217126-6-QeKyldLpyE@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-217126-6@https.bugs.freebsd.org/bugzilla/>
References: <bug-217126-6@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-amd64@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Porting FreeBSD to the AMD64 platform <freebsd-amd64.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-amd64>,
 <mailto:freebsd-amd64-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-amd64/>
List-Post: <mailto:freebsd-amd64@freebsd.org>
List-Help: <mailto:freebsd-amd64-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-amd64>,
 <mailto:freebsd-amd64-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 03:16:25 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D217126

--- Comment #4 from Conrad Meyer <cem@freebsd.org> ---
> In my attempt to dd the image, I got 4.1GB out of 32GB and a "device not =
configured".

That's probably ENXIO (the hardware has some issue and disappeared during d=
d).=20
I wouldn't be surprised if this lead to a panic in msdosfs because it doesn=
't
handle ENXIO errors (failing or removed disks) well.

Or maybe the bad device is causing some other issue.

> I'm referencing https://www.freebsd.org/doc/en/books/developers-handbook/=
kerneldebug-gdb.html in the hopes that it'll lead me correctly.

If you can get a core, even better.

> FWIW, I've got encrypted swap and zfs underneath the system.

That will make it hard to get a core :-).

--=20
You are receiving this mail because:
You are on the CC list for the bug.=