Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 17 Dec 2014 22:34:57 -0600
From:      Adam Vande More <amvandemore@gmail.com>
To:        Shane Ambler <BSD@shaneware.biz>
Cc:        "freebsd-stable@freebsd.org" <freebsd-stable@freebsd.org>, Hans Petter Selasky <hselasky@freebsd.org>, mjg@freebsd.org, Alexander Motin <mav@freebsd.org>, Shane Ambler <FreeBSD@shaneware.biz>, John Baldwin <jhb@freebsd.org>
Subject:   Re: Help debugging stable/10
Message-ID:  <CA%2BtpaK1JhOZcDwavKxtp8yAiN7Hzehe%2Bomup6gzR-s5X7==1dw@mail.gmail.com>
In-Reply-To: <54923507.5030908@ShaneWare.Biz>
References:  <5488F58D.7060708@ShaneWare.Biz> <201412161129.57704.jhb@freebsd.org> <5490BF55.3020108@ShaneWare.Biz> <2129928.1Q3VzLjDQL@ralph.baldwin.cx> <54923507.5030908@ShaneWare.Biz>

next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Dec 17, 2014 at 7:59 PM, Shane Ambler <BSD@shaneware.biz> wrote:
>
> 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.


There are previous mentions of that error being tickled by hald. Disabling
it or preventing it from attacking your device might be a workaround.


-- 
Adam



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA%2BtpaK1JhOZcDwavKxtp8yAiN7Hzehe%2Bomup6gzR-s5X7==1dw>