Date: Thu, 18 Dec 2014 12:29:35 +1030 From: Shane Ambler <BSD@ShaneWare.Biz> To: John Baldwin <jhb@freebsd.org> Cc: Alexander Motin <mav@freebsd.org>, freebsd-stable@freebsd.org, hselasky@freebsd.org, mjg@freebsd.org, Shane Ambler <FreeBSD@shaneware.biz> Subject: Re: Help debugging stable/10 Message-ID: <54923507.5030908@ShaneWare.Biz> In-Reply-To: <2129928.1Q3VzLjDQL@ralph.baldwin.cx> References: <5488F58D.7060708@ShaneWare.Biz> <201412161129.57704.jhb@freebsd.org> <5490BF55.3020108@ShaneWare.Biz> <2129928.1Q3VzLjDQL@ralph.baldwin.cx>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?54923507.5030908>