From owner-freebsd-fs@freebsd.org  Wed Jul 29 07:44:54 2015
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 69D9B9AB72A
 for <freebsd-fs@mailman.ysv.freebsd.org>; Wed, 29 Jul 2015 07:44:54 +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 56BD32F2
 for <freebsd-fs@FreeBSD.org>; Wed, 29 Jul 2015 07:44:54 +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 t6T7iscv017530
 for <freebsd-fs@FreeBSD.org>; Wed, 29 Jul 2015 07:44:54 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-fs@FreeBSD.org
Subject: [Bug 201912] panic in smbfs during mount
Date: Wed, 29 Jul 2015 07:44:54 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 10.1-RELEASE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: martin@sugioarto.com
X-Bugzilla-Status: New
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-201912-3630-GWCF4h0Z1n@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-201912-3630@https.bugs.freebsd.org/bugzilla/>
References: <bug-201912-3630@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://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: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jul 2015 07:44:54 -0000

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

--- Comment #3 from martin@sugioarto.com ---
(In reply to Andrey V. Elsukov from comment #2)

Yes, I am using the GENERIC kernel. ident says there are "no id keywords". Are
you sure that IDs are in GENERIC kernels? Maybe it's because I check out from
the Git repository on Github (https://github.com/freebsd/freebsd).

uname -a:
FreeBSD sugioarto.phiscience.local 10.1-RELEASE-p14 FreeBSD 10.1-RELEASE-p14 #0
r284985+86de4e2(releng/10.1): Fri Jul 10 11:54:22 CEST 2015    
root@sugioarto.phiscience.local:/usr/obj/usr/src/sys/GENERIC  amd64

Usually I remove all /usr/obj and build entire world. The timestamps in
/boot/kernel are also consistent.

I've seen this bug the first time and reported instantly. I'll rebuild the
world+kernel once again now with the latest patches, if you say so.

Ok, let's close this PR for now. I'll reopen it, when I see this crash again. I
use smbfs a lot and won't change my configuration of it for a long time, I
think.

-- 
You are receiving this mail because:
You are the assignee for the bug.