So, I did : ifconfig urtwn0 debug # urtwn0: device timeout urtwn0: RUN -> INIT
2017-08-24 17:44 GMT-03:00 R0me0 *** <[email protected]>: > snapshot is from OpenBSD 6.2-beta (GENERIC) #0: Tue Aug 22 17:53:50 AEST > 2017 > > 2017-08-24 17:32 GMT-03:00 R0me0 *** <[email protected]>: > >> + bugs at openbsd dot org >> >> Hello, Todd! >> I am using the snapshot from yesterday. >> If I do not start tor, so my connections keeps working, for example: I >> can download large files using ssh, I just noticed it when I start tor >> service. >> >> Thanks in advance for attention, >> >> >> >> 2017-08-24 17:25 GMT-03:00 R0me0 *** <[email protected]>: >> >>> Hello, Todd! >>> I am using the snapshot from yesterday. >>> If I do not start tor, so my connections keeps working, for example: I >>> can download large files using ssh, I just noticed it when I start tor >>> service. >>> >>> Thanks in advance for attention, >>> >>> >>> >>> >>> >>> 2017-08-24 17:16 GMT-03:00 Todd C. Miller <[email protected]>: >>> >>>> On Thu, 24 Aug 2017 16:15:48 -0300, "R0me0 ***" wrote: >>>> >>>> > I have noticed the following behavior: >>>> > >>>> > >>>> > urtwn0: device timeout >>>> > >>>> > The system just hangs and hard reboot is needed. >>>> >>>> That sounds similar to this bug: >>>> https://marc.info/?l=openbsd-bugs&m=150157788716680&w=2 >>>> >>>> Which was fixed in revision 1.30 of sys/dev/ic/rtwn.c: >>>> date: 2017/08/20 14:53:06; author: stsp; state: Exp; lines: +37 -34 >>>> Fix use of uninitialized variables during rtwn(4) I/Q calibration, which >>>> restored device registers from uninitialized memory after calibration. >>>> Bug was hinted at by clang which produced a non-working driver at -O2. >>>> The problem was eventually spotted by jsg@ with gcc 6.3.1. >>>> >>> >>> >> >
