From owner-freebsd-fs@freebsd.org  Mon May 16 07:47:44 2016
Return-Path: <owner-freebsd-fs@freebsd.org>
Delivered-To: freebsd-fs@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 27999B3D1DD
 for <freebsd-fs@mailman.ysv.freebsd.org>; Mon, 16 May 2016 07:47:44 +0000 (UTC)
 (envelope-from hps@selasky.org)
Received: from mail.turbocat.net (mail.turbocat.net
 [IPv6:2a01:4f8:d16:4514::2])
 (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 DED251F43;
 Mon, 16 May 2016 07:47:43 +0000 (UTC) (envelope-from hps@selasky.org)
Received: from laptop015.home.selasky.org (unknown [62.141.129.119])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (No client certificate requested)
 by mail.turbocat.net (Postfix) with ESMTPSA id 306171FE023;
 Mon, 16 May 2016 09:47:42 +0200 (CEST)
Subject: Re: bug in umass?
To: "K. Macy" <kmacy@freebsd.org>,
 "freebsd-fs@FreeBSD.org" <freebsd-fs@freebsd.org>,
 Alexander Motin <mav@FreeBSD.org>
References: <CAHM0Q_OYGmRmG39v=688f7f8ARs7avSZHBk8y-BSJkfzzYUzdA@mail.gmail.com>
From: Hans Petter Selasky <hps@selasky.org>
Message-ID: <d5d2e8c9-2b3b-f96b-34c1-f5b4a865eab9@selasky.org>
Date: Mon, 16 May 2016 09:51:01 +0200
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101
 Thunderbird/45.0
MIME-Version: 1.0
In-Reply-To: <CAHM0Q_OYGmRmG39v=688f7f8ARs7avSZHBk8y-BSJkfzzYUzdA@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 16 May 2016 07:47:44 -0000

Hi Alexander,

Does dumping core on a USB stick from KDB require any threads?

 From the USB point of view we are doing polling in "umass_cam_poll()".

--HPS

On 05/16/16 07:02, K. Macy wrote:
> I'm not able to complete a coredump in i915 to a USB key. The
> backtrace in the log looks like a bug in umass.
>
>
> May 15 21:57:10 beastie kernel: cmap[0]=0 cmap[1]=7f0000 cmap[2]=7f00
> cmap[3]=c4a000
> May 15 21:57:10 beastie kernel: end FB_INFO
> May 15 21:57:10 beastie kernel: drmn0: fb0: inteldrmfb frame buffer device
> May 15 21:57:10 beastie kernel: ..3%
> May 15 21:58:16 beastie syslogd: kernel boot file is /boot/kernel/kernel
> May 15 21:58:16 beastie kernel: trap_fatal() at trap_fatal+0x2d/frame
> 0xfffffe01e2fd6350
> May 15 21:58:16 beastie kernel: trap() at trap+0xc48/frame 0xfffffe01e2fd6690
> May 15 21:58:16 beastie kernel: trap_check() at trap_check+0x4a/frame
> 0xfffffe01e2fd66b0
> May 15 21:58:16 beastie kernel: calltrap() at calltrap+0x8/frame
> 0xfffffe01e2fd66b0
> May 15 21:58:16 beastie kernel: --- trap 0x9, rip =
> 0xffffffff80f5a950, rsp = 0xfffffe01e2fd6780, rbp = 0xfffffe01e2fd6810
> ---
> May 15 21:58:16 beastie kernel: __mtx_lock_flags() at
> __mtx_lock_flags+0xd0/frame 0xfffffe01e2fd6810
> May 15 21:58:16 beastie kernel: xpt_done_process() at
> xpt_done_process+0x495/frame 0xfffffe01e2fd68c0
> May 15 21:58:16 beastie kernel: xpt_done_td() at
> xpt_done_td+0x1c0/frame 0xfffffe01e2fd6930
> May 15 21:58:16 beastie kernel: fork_exit() at fork_exit+0x13b/frame
> 0xfffffe01e2fd69b0
> May 15 21:58:16 beastie kernel: fork_trampoline() at
> fork_trampoline+0xe/frame 0xfffffe01e2fd69b0
> May 15 21:58:16 beastie kernel: --- trap 0, rip = 0, rsp = 0, rbp = 0 ---
>