From owner-freebsd-stable@FreeBSD.ORG Wed Dec 17 14:58:54 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B1CBC78D; Wed, 17 Dec 2014 14:58:54 +0000 (UTC) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8A6BB97D; Wed, 17 Dec 2014 14:58:54 +0000 (UTC) Received: from ralph.baldwin.cx (pool-173-70-85-31.nwrknj.fios.verizon.net [173.70.85.31]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 77074B984; Wed, 17 Dec 2014 09:58:53 -0500 (EST) From: John Baldwin To: Shane Ambler Subject: Re: Help debugging stable/10 Date: Wed, 17 Dec 2014 09:30:26 -0500 Message-ID: <2129928.1Q3VzLjDQL@ralph.baldwin.cx> User-Agent: KMail/4.14.2 (FreeBSD/10.1-STABLE; KDE/4.14.2; amd64; ; ) In-Reply-To: <5490BF55.3020108@ShaneWare.Biz> References: <5488F58D.7060708@ShaneWare.Biz> <201412161129.57704.jhb@freebsd.org> <5490BF55.3020108@ShaneWare.Biz> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Wed, 17 Dec 2014 09:58:53 -0500 (EST) Cc: Alexander Motin , freebsd-stable@freebsd.org, hselasky@freebsd.org, mjg@freebsd.org, Shane Ambler X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Dec 2014 14:58:54 -0000 On Wednesday, December 17, 2014 09:55:09 AM Shane Ambler wrote: > I think it was in RC3 I got errors of - > xptioctl: pass driver is not in the kernel > xptioctl: put "device pass" in your kernel config file > a couple of times with the USB memstick - again not recently. Interesting. Perhaps take 'pass' back out then as the cure seems worse than the disease. :) Can you figure out what processes are running when those errors are logged? Whatever is calling xptioctl() is triggering this I believe. -- John Baldwin