From owner-freebsd-stable@FreeBSD.ORG Thu Dec 18 01:59:46 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0A33B2FC; Thu, 18 Dec 2014 01:59:46 +0000 (UTC) Received: from ipmail05.adl6.internode.on.net (ipmail05.adl6.internode.on.net [150.101.137.143]) by mx1.freebsd.org (Postfix) with ESMTP id DDD4F223; Thu, 18 Dec 2014 01:59:44 +0000 (UTC) Received: from ppp14-2-30-215.lns21.adl2.internode.on.net (HELO leader.local) ([14.2.30.215]) by ipmail05.adl6.internode.on.net with ESMTP; 18 Dec 2014 12:29:36 +1030 Message-ID: <54923507.5030908@ShaneWare.Biz> Date: Thu, 18 Dec 2014 12:29:35 +1030 From: Shane Ambler User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: John Baldwin Subject: Re: Help debugging stable/10 References: <5488F58D.7060708@ShaneWare.Biz> <201412161129.57704.jhb@freebsd.org> <5490BF55.3020108@ShaneWare.Biz> <2129928.1Q3VzLjDQL@ralph.baldwin.cx> In-Reply-To: <2129928.1Q3VzLjDQL@ralph.baldwin.cx> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit 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: Thu, 18 Dec 2014 01:59:46 -0000 On 18/12/2014 01:00, John Baldwin wrote: > 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. > I haven't altered the kernel config. That was an old error I got a few times when I had issues with the USB device insertion not registering. I think I saw it 3 times and it was a continuous repeat on the console. It only showed when things went bad so I wasn't convinced I needed to add it. Just mentioned as it appeared to be USB related and might hint to what triggers the USB system to falter. Could be a red herring too. -- FreeBSD - the place to B...Software Developing Shane Ambler