2014-09-01 10:47 GMT+02:00 Martin Pieuchot <mpieuc...@nolizard.org>:
> On 30/08/14(Sat) 12:28, ludovic coues wrote:
>> 2014-08-30 11:58 GMT+02:00 Martin Pieuchot <mpieuc...@nolizard.org>:
>> > On 30/08/14(Sat) 11:46, ludovic coues wrote:
>> >> 2014-08-30 10:53 GMT+02:00 Martin Pieuchot <mpieuc...@nolizard.org>:
>> >> > Hello Ludovic,
>> >> >
>> >> > On 28/08/14(Thu) 20:52, ludovic coues wrote:
>> >> >> Hello,
>> >> >>
>> >> >> Recently, I get a kernel page fault every time I try to use the
>> >> >> micronucleus [1] command line tool. It 's for uploading an hex file to
>> >> >> ATtiny processor, much like arduino's avrude. The crash is pretty
>> >> >> consistent, occuring every time I run `micronucleus --run`.
>> >> >> I've managed to use it with success in the past on this machine with
>> >> >> 55-release so it might be hardware related. I added a realtek wireless
>> >> >> device since last time I've get a successful run with micronucleus.
>> >> >>
>> >> >> I get the following message when I run it:
>> >> >> uvm_fault(0xffffffff81daaf001, 0x2, 2, 0, 1) -> e
>> >> >> kernel: page fault trap, code=0
>> >> >> Stopped at usbd_get_cdesc+035: movzwl 0x2 (%rax),%eax
>> >> >>
>> >> >> It's followed by the debugger prompt. I don't know how what to do from
>> >> >> that point. I'm willing to spend time tracking the source of the
>> >> >> problem but I have no idea of what I'm looking for.
>> >> >
>> >> > Thanks for reporting the problem.  I believe this is the same issue that
>> >> > has been reported by Thomas Pfaff in February [0] and fixed post 5.5 
>> >> > [1].
>> >> >
>> >> > Could you try a snapshot and tell me if you can still reproduce it?
>> >> >
>> >> > Cheers,
>> >> > Martin
>> >> >
>> >> > [0] http://marc.info/?l=openbsd-bugs&m=139135208628637&w=2
>> >> > [1] http://marc.info/?l=openbsd-cvs&m=139194643911061&w=2
>> >>
>> >> I might have failed to upgrade to snapshot but I still have the error.
>> >> Right now, I got the snapshot install56.fs file, used it to run an
>> >> upgrade and run sysmerge. I must have done something right as
>> >> start_daemon isn't available anymore in /etc/rc.local but the error is
>> >> still present.
>> >
>> > In this case could you send me your dmesg, the output of "usbdevs -dv"
>> > and the trace when the trap occurs?
>>
>
> Thanks Ludovic,
>
>> usbdevs -dv:
>> [...]
>>   port 4 addr 3: high speed, power 100 mA, unconfigured,
>> RTL8187B(0x8189), Realtek(0x0bda), rev 2.00, iSerialNumber
>> 00e04c000001
>>     urtw0
>
> The problem comes from this driver that does not set any configuration
> when it attaches itself to the device.
>
> Could you test the diff below, it is a sync with urtwn(4), and tell me
> if you can reproduce this problem with it?
>

Nope, I cannot reproduce :)

Thank a lot for your time.

Reply via email to