Hello all,
Stefan thanks for heads up! :)

following dmesg:

# dmesg

OpenBSD 6.2-beta (GENERIC) #0: Tue Aug 22 17:53:50 AEST 2017
   [email protected]:/usr/src/sys/arch/arm64/compile/GENERIC
real mem  = 965042176 (920MB)
avail mem = 909217792 (867MB)
mainbus0 at root: Raspberry Pi 3 Model B Rev 1.2
cpu0 at mainbus0: ARM Cortex-A53 r0p4
simplefb0 at mainbus0: 656x416
wsdisplay0 at simplefb0 mux 1
wsdisplay0: screen 0 added (std, vt100 emulation)
simplebus0 at mainbus0: "soc"
bcmintc0 at simplebus0
bcmdog0 at simplebus0
pluart0 at simplebus0
bcmaux0 at simplebus0
com0 at simplebus0: ns16550, no working fifo
com0: console
dwctwo0 at simplebus0
agtimer0 at simplebus0: tick rate 19200 KHz
simplebus1 at mainbus0: "clocks"
usb0 at dwctwo0: USB revision 2.0
uhub0 at usb0 configuration 1 interface 0 "Broadcom DWC2 root hub" rev
2.00/1.00 addr 1
uhub1 at uhub0 port 1 configuration 1 interface 0 "Standard Microsystems
product 0x9514" rev 2.00/2.00 addr 2
smsc0 at uhub1 port 1 configuration 1 interface 0 "Standard Microsystems
SMSC9512/14" rev 2.00/2.00 addr 3
smsc0: address b8:27:eb:78:27:cd
ukphy0 at smsc0 phy 1: Generic IEEE 802.3u media interface, rev. 3: OUI
0x0001f0, model 0x000c
umass0 at uhub1 port 3 configuration 1 interface 0 "Kingston DataTraveler
2.0" rev 2.00/1.00 addr 4
umass0: using SCSI over Bulk-Only
scsibus0 at umass0: 2 targets, initiator 0
sd0 at scsibus0 targ 1 lun 0: <Kingston, DataTraveler 2.0, 1.00> SCSI2
0/direct removable serial.09511665FDB1A9792441
sd0: 14762MB, 512 bytes/sector, 30233588 sectors
urtwn0 at uhub1 port 4 configuration 1 interface 0 "802.11n USB WLAN" rev
2.00/2.00 addr 5
urtwn0: MAC/BB RTL8192CU, RF 6052 2T2R, address 98:de:d0:11:ac:a1
vscsi0 at root
scsibus1 at vscsi0: 256 targets
softraid0 at root
scsibus2 at softraid0: 256 targets
bootfile: sd0a:/bsd
boot device: sd0
root on sd0a (5023b2de782a611f.a) swap on sd0b dump on sd0b
WARNING: / was not properly unmounted
WARNING: CHECK AND RESET THE DATE!

2017-08-25 6:32 GMT-03:00 Stefan Sperling <[email protected]>:

> On Thu, Aug 24, 2017 at 05:47:06PM -0300, R0me0 *** wrote:
> > So, I did : ifconfig urtwn0 debug
> >
> > # urtwn0: device timeout
> > urtwn0: RUN -> INIT
> >
>
> Missing dmesg on bug report -> ignored
>
> >
> >
> > 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.
> > >>>>
> > >>>
> > >>>
> > >>
> > >
>

Reply via email to