from:"R0me0 \*\*\*"

OBSD 7.2 snapshot and 7.3 stable Banana pi m2+

2023-01-25 Thread R0me0 ***

u-boot-arm-2021.10p4.tgz
dtb-5.14p1.tgz

7.2/packages/amd64



>> OpenBSD/armv7 BOOTARM 1.20
boot>
booting sd0a:/bsd: 4953084+936340+138024+594516
[276144+107+340656+302308]=0x0

OpenBSD/armv7 booting ...
arg0 0xc0a32640 arg1 0x0 arg2 0x78e1c000
Allocating page tables
IRQ stack: p0x40a61000 v0xc0a61000
ABT stack: p0x40a62000 v0xc0a62000
UND stack: p0x40a63000 v0xc0a63000
SVC stack: p0x40a64000 v0xc0a64000
Creating L1 page table at 0x40a34000
Mapping kernel
Constructing L2 page tables
undefined page type 0x2 pa 0x4000 va 0x4000 pages 0x2000 attr 0x8
type 0x7 pa 0x4200 va 0x4200 pages 0x5ef7 attr 0x8
type 0x9 pa 0x47ef7000 va 0x47ef7000 pages 0x12 attr 0x8
type 0x7 pa 0x47f09000 va 0x47f09000 pages 0x30f13 attr 0x8
type 0x2 pa 0x78e1c000 va 0x78e1c000 pages 0x7 attr 0x8
type 0x4 pa 0x78e23000 va 0x78e23000 pages 0x1 attr 0x8
type 0x7 pa 0x78e24000 va 0x78e24000 pages 0x1 attr 0x8
type 0x2 pa 0x78e25000 va 0x78e25000 pages 0x100 attr 0x8
type 0x1 pa 0x78f25000 va 0x78f25000 pages 0x1e attr 0x8
type 0x4 pa 0x78f43000 va 0x78f43000 pages 0x8 attr 0x8
type 0x6 pa 0x78f4b000 va 0x78f4b000 pages 0x1 attr 0x8008
type 0x4 pa 0x78f4c000 va 0x78f4c000 pages 0x3 attr 0x8
type 0x6 pa 0x78f4f000 va 0x78f4f000 pages 0x3 attr 0x8008
type 0x4 pa 0x78f52000 va 0x78f52000 pages 0x1 attr 0x8
type 0x6 pa 0x78f53000 va 0x78f53000 pages 0x4 attr 0x8008
type 0x4 pa 0x78f57000 va 0x78f57000 pages 0xe attr 0x8
type 0x2 pa 0x78f65000 va 0x78f65000 pages 0x5028 attr 0x8
type 0x5 pa 0x7df8d000 va 0x7df8d000 pages 0x1 attr 0x8008
type 0x2 pa 0x7df8e000 va 0x7df8e000 pages 0x47 attr 0x8
type 0x0 pa 0x7dfd5000 va 0x7dfd5000 pages 0x3 attr 0x8
type 0x2 pa 0x7dfd8000 va 0x7dfd8000 pages 0x28 attr 0x8
type 0x0 pa 0x7e00 va 0x7e00 pages 0x300 attr 0x8
type 0x2 pa 0x7e30 va 0x7e30 pages 0x1d00 attr 0x8
pmap [ using 919748 bytes of bsd ELF symbol table ]
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California.  All rights reserved.
Copyright (c) 1995-2023 OpenBSD. All rights reserved.
https://www.OpenBSD.org

OpenBSD 7.2-current (GENERIC) #98: Wed Jan 25 10:31:17 MST 2023
dera...@armv7.openbsd.org:/usr/src/sys/arch/armv7/compile/GENERIC
real mem  = 954245120 (910MB)
avail mem = 926617600 (883MB)
random: good seed from bootblocks
mainbus0 at root: Banana Pi BPI-M2-Plus H3
cpu0 at mainbus0 mpidr 0: ARM Cortex-A7 r0p5
cpu0: 32KB 32b/line 2-way L1 VIPT I-cache, 32KB 64b/line 4-way L1 D-cache
cpu0: 512KB 64b/line 8-way L2 cache
cortex0 at mainbus0
psci0 at mainbus0: PSCI 0.0
sxiccmu0 at mainbus0
simplebus0 at mainbus0: "soc"
sxisid0 at simplebus0
sxiccmu1 at simplebus0
sxipio0 at simplebus0: 94 pins
ampintc0 at simplebus0 nirq 160, ncpu 4: "interrupt-controller"
sxirtc0 at simplebus0
sxiccmu2 at simplebus0
sxipio1 at simplebus0: 12 pins
sxisyscon0 at simplebus0
"clock" at simplebus0 not configured
"mixer" at simplebus0 not configured
"dma-controller" at simplebus0 not configured
"lcd-controller" at simplebus0 not configured
sximmc0 at simplebus0
sdmmc0 at sximmc0: 4-bit, sd high-speed, mmc high-speed, dma
sximmc1 at simplebus0
sdmmc1 at sximmc1: 4-bit, sd high-speed, mmc high-speed, dma
sximmc2 at simplebus0
sdmmc2 at sximmc2: 8-bit, sd high-speed, mmc high-speed, dma
"mailbox" at simplebus0 not configured
"usb" at simplebus0 not configured
"phy" at simplebus0 not configured
ehci0 at simplebus0
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 configuration 1 interface 0 "Generic EHCI root hub" rev
2.00/1.00 addr 1
ohci0 at simplebus0: version 1.0
ehci1 at simplebus0
usb1 at ehci1: USB revision 2.0
uhub1 at usb1 configuration 1 interface 0 "Generic EHCI root hub" rev
2.00/1.00 addr 1
ohci1 at simplebus0: version 1.0
ehci2 at simplebus0
usb2 at ehci2: USB revision 2.0
uhub2 at usb2 configuration 1 interface 0 "Generic EHCI root hub" rev
2.00/1.00 addr 1
ohci2 at simplebus0: version 1.0
"timer" at simplebus0 not configured
dwxe0 at simplebus0: address 02:81:6f:e8:73:fe
rgephy0 at dwxe0 phy 1: RTL8169S/8110S/8211 PHY, rev. 5
"dram-controller" at simplebus0 not configured
sxidog0 at simplebus0
com0 at simplebus0: dw16550
com0: console
com1 at simplebus0: dw16550
"hdmi" at simplebus0 not configured
"hdmi-phy" at simplebus0 not configured
"interrupt-controller" at simplebus0 not configured
"codec-analog" at simplebus0 not configured
"ir" at simplebus0 not configured
"deinterlace" at simplebus0 not configured
"video-codec" at simplebus0 not configured
"crypto" at simplebus0 not configured
"gpu" at simplebus0 not configured
sxitemp0 at simplebus0
gpio0 at sxipio0: 32 pins
gpio1 at sxipio0: 32 pins
gpio2 at sxipio0: 32 pins
gpio3 at sxipio0: 32 pins
gpio4 at sxipio0: 32 pins
gpio5 at sxipio0: 32 pins
gpio6 at sxipio0: 32 pins
gpio7 at sxipio1: 32 pins
usb3 at ohci0: USB revision 1.0
uhub3 at usb3 configuration 1 interface 0 "Generic OHCI root hub" rev
1.00/1.00 addr 1
usb4 at ohci1: USB revision 1.0
uhub4 at usb4 configuration 1 interface 0

kernel Panic VPS

2020-09-21 Thread R0me0 ***

Hello Guys,

My OpenBSD machine just hangs, Attached as image  ddb trace

OpenBSD 6.7 (GENERIC.MP) #5: Tue Jul 21 13:50:07 MDT 2020
r...@syspatch-67-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/
GENERIC.MP
real mem = 2130558976 (2031MB)
avail mem = 2053427200 (1958MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xf5940 (9 entries)
bios0: vendor SeaBIOS version "rel-1.12.1-0-ga5cab58e9a3f-prebuilt.qemu.org"
date 04/01/2014
bios0: QEMU Standard PC (i440FX + PIIX, 1996)
acpi0 at bios0: ACPI 1.0
acpi0: sleep states S3 S4 S5
acpi0: tables DSDT FACP APIC HPET
acpi0: wakeup devices
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel Xeon Processor (Cascadelake), 2893.77 MHz, 06-55-06
cpu0:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,SSE3,PCLMUL,SSSE3,FMA3,CX16,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,RDRAND,HV,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,AVX512F,AVX512DQ,CLFLUSHOPT,CLWB,AVX512CD,AVX512BW,AVX512VL,PKU,IBRS,IBPB,SSBD,ARAT,XSAVEOPT,MELTDOWN
cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB
64b/line 16-way L2 cache
cpu0: ITLB 255 4KB entries direct-mapped, 255 4MB entries direct-mapped
cpu0: DTLB 255 4KB entries direct-mapped, 255 4MB entries direct-mapped
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: apic clock running at 999MHz
ioapic0 at mainbus0: apid 0 pa 0xfec0, version 20, 24 pins
acpihpet0 at acpi0: 1 Hz
acpiprt0 at acpi0: bus 0 (PCI0)
acpicpu0 at acpi0: C1(@1 halt!)
"ACPI0006" at acpi0 not configured
acpipci0 at acpi0 PCI0: _OSC failed
acpicmos0 at acpi0
"PNP0A06" at acpi0 not configured
"PNP0A06" at acpi0 not configured
"PNP0A06" at acpi0 not configured
"QEMU0002" at acpi0 not configured
"ACPI0010" at acpi0 not configured
pvbus0 at mainbus0: KVM
pvclock0 at pvbus0
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 "Intel 82441FX" rev 0x02
pcib0 at pci0 dev 1 function 0 "Intel 82371SB ISA" rev 0x00
pciide0 at pci0 dev 1 function 1 "Intel 82371SB IDE" rev 0x00: DMA, channel
0 wired to compatibility, channel 1 wired to compatibility
pciide0: channel 0 disabled (no drives)
atapiscsi0 at pciide0 channel 1 drive 0
scsibus1 at atapiscsi0: 2 targets
cd0 at scsibus1 targ 0 lun 0:  removable
cd0(pciide0:1:0): using PIO mode 4, DMA mode 2
uhci0 at pci0 dev 1 function 2 "Intel 82371SB USB" rev 0x01: apic 0 int 11
piixpm0 at pci0 dev 1 function 3 "Intel 82371AB Power" rev 0x03: apic 0 int
9
iic0 at piixpm0
vga1 at pci0 dev 2 function 0 "Cirrus Logic CL-GD5446" rev 0x00
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
virtio0 at pci0 dev 3 function 0 "Qumranet Virtio Network" rev 0x00
vio0 at virtio0: address 56:00:02:f8:fb:3f
virtio0: msix per-VQ
virtio1 at pci0 dev 4 function 0 "Qumranet Virtio Storage" rev 0x00
vioblk0 at virtio1
scsibus2 at vioblk0: 2 targets
sd0 at scsibus2 targ 0 lun 0: 
sd0: 56320MB, 512 bytes/sector, 115343360 sectors
virtio1: msix shared
virtio2 at pci0 dev 5 function 0 "Qumranet Virtio Memory Balloon" rev 0x00
viomb0 at virtio2
virtio2: apic 0 int 10
virtio3 at pci0 dev 6 function 0 "Qumranet Virtio RNG" rev 0x00
viornd0 at virtio3
virtio3: apic 0 int 10
isa0 at pcib0
isadma0 at isa0
fdc0 at isa0 port 0x3f0/6 irq 6 drq 2
pckbc0 at isa0 port 0x60/5 irq 1 irq 12
pckbd0 at pckbc0 (kbd slot)
wskbd0 at pckbd0: console keyboard, using wsdisplay0
pms0 at pckbc0 (aux slot)
wsmouse0 at pms0 mux 0
pcppi0 at isa0 port 0x61
spkr0 at pcppi0
usb0 at uhci0: USB revision 1.0
uhub0 at usb0 configuration 1 interface 0 "Intel UHCI root hub" rev
1.00/1.00 addr 1
uhidev0 at uhub0 port 1 configuration 1 interface 0 "QEMU QEMU USB Tablet"
rev 2.00/0.00 addr 2
uhidev0: iclass 3/0
ums0 at uhidev0: 3 buttons, Z dir
wsmouse1 at ums0 mux 0
vscsi0 at root
scsibus3 at vscsi0: 256 targets
softraid0 at root
scsibus4 at softraid0: 256 targets
root on sd0a (b902da1aec59e4c4.a) swap on sd0b dump on sd0b
WARNING: / was not properly unmounted
fd0 at fdc0 drive 1: density unknown

OpenBSD 6.2 IKED IPv6 Connections and address dropped

2018-02-15 Thread R0me0 ***

Hello guys!

I have a very weird issue, not sure if a bug, but seems.

Here my iked.conf

ikev2 "pufferfish"  passive esp from 0.0.0.0/0 to 192.10.10.0/24 \
 local 10.10.10.10 peer any  \
 ikesa enc aes-256 auth hmac-sha2-256 group modp2048 \
 childsa enc aes-256 auth hmac-sha2-256 group modp2048 \
 dstid pufferfish psk "mypsk" config address 192.10.10.15

My default gateway is fe80::1%vmx0


If I run:


/etc/rc.d/iked start

All IPV6 connections are dropped immediately .

Even if I remove all IPV6 address from all interfaces I cant back

OpenBSD reboot is needed !

all patches applied using syspatch.



ping6 ::1
PING ::1 (::1): 56 data bytes
ping6: sendmsg: No route to host
ping: wrote ::1 64 chars, ret=-1
^C
--- ::1 ping statistics ---
1 packets transmitted, 0 packets received, 100.0% packet loss


ping6 fe80::1%vmx0
PING fe80::1%vmx0 (fe80::1%vmx0): 56 data bytes
ping6: sendmsg: No route to host
ping: wrote fe80::1%vmx0 64 chars, ret=-1
^C
--- fe80::1%vmx0 ping statistics ---
1 packets transmitted, 0 packets received, 100.0% packet loss







































































































































































*rebooting...OpenBSD 6.2 (GENERIC.MP ) #5: Fri Feb  2
23:02:19 CET 2018
r...@syspatch-62-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 1056899072 (1007MB)avail mem = 1017901056
(970MB)mpath0 at rootscsibus0 at mpath0: 256 targetsmainbus0 at rootbios0
at mainbus0: SMBIOS rev. 2.7 @ 0xe0010 (242 entries)bios0: vendor Phoenix
Technologies LTD version "6.00" date 04/05/2016bios0: VMware, Inc. VMware
Virtual Platformacpi0 at bios0: rev 2acpi0: sleep states S0 S1 S4 S5acpi0:
tables DSDT FACP BOOT APIC MCFG SRAT HPET WAETacpi0: wakeup devices
PCI0(S3) USB_(S1) P2P0(S3) S1F0(S3) S2F0(S3) S8F0(S3) S16F(S3) S17F(S3)
S18F(S3) S22F(S3) S23F(S3) S24F(S3) S25F(S3) PE40(S3) S1F0(S3) PE50(S3)
[...]acpitimer0 at acpi0: 3579545 Hz, 24 bitsacpimadt0 at acpi0 addr
0xfee0: PC-AT compatcpu0 at mainbus0: apid 0 (boot processor)cpu0:
Intel(R) Xeon(R) CPU E5-1650 v2 @ 3.50GHz, 3500.11 MHzcpu0:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,MMX,FXSR,SSE,SSE2,SS,SSE3,PCLMUL,SSSE3,CX16,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,HV,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,ARATcpu0:
256KB 64b/line 8-way L2 cachecpu0: TSC frequency 3500112670 Hzcpu0: smt 0,
core 0, package 0mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed
rangescpu0: apic clock running at 65MHzcpu1 at mainbus0: apid 2
(application processor)cpu1: Intel(R) Xeon(R) CPU E5-1650 v2 @ 3.50GHz,
3499.85 MHzcpu1:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,MMX,FXSR,SSE,SSE2,SS,SSE3,PCLMUL,SSSE3,CX16,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,HV,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,ARATcpu1:
256KB 64b/line 8-way L2 cachecpu1: smt 0, core 0, package 2ioapic0 at
mainbus0: apid 1 pa 0xfec0, version 11, 24 pinsacpimcfg0 at acpi0 addr
0xf000, bus 0-127acpihpet0 at acpi0: 14318179 Hzacpiprt0 at acpi0: bus
0 (PCI0)acpicpu0 at acpi0: C1(@1 halt!)acpicpu1 at acpi0: C1(@1
halt!)"PNP0001" at acpi0 not configured"VMW0003" at acpi0 not
configured"PNP0A05" at acpi0 not configuredacpiac0 at acpi0: AC unit
onlinepvbus0 at mainbus0: VMwarevmt0 at pvbus0pci0 at mainbus0 bus 0pchb0
at pci0 dev 0 function 0 "Intel 82443BX AGP" rev 0x01ppb0 at pci0 dev 1
function 0 "Intel 82443BX AGP" rev 0x01pci1 at ppb0 bus 1pcib0 at pci0 dev
7 function 0 "Intel 82371AB PIIX4 ISA" rev 0x08pciide0 at pci0 dev 7
function 1 "Intel 82371AB IDE" rev 0x01: DMA, channel 0 configured to
compatibility, channel 1 configured to compatibilitypciide0: channel 0
disabled (no drives)pciide0: channel 1 disabled (no drives)piixpm0 at pci0
dev 7 function 3 "Intel 82371AB Power" rev 0x08: SMBus disabled"VMware
VMCI" rev 0x10 at pci0 dev 7 function 7 not configuredvga1 at pci0 dev 15
function 0 "VMware SVGA II" rev 0x00wsdisplay0 at vga1 mux 1: console
(80x25, vt100 emulation)wsdisplay0: screen 1-5 added (80x25, vt100
emulation)mpi0 at pci0 dev 16 function 0 "Symbios Logic 53c1030" rev 0x01:
apic 1 int 17mpi0: 0, firmware 1.3.41.32scsibus1 at mpi0: 16 targets,
initiator 7sd0 at scsibus1 targ 0 lun 0:  SCSI4
0/direct fixedsd0: 8192MB, 512 bytes/sector, 16777216 sectorsmpi0: target 0
Sync at 160MHz width 16bit offset 127 QAS 1 DT 1 IU 1ppb1 at pci0 dev 17
function 0 "VMware PCI" rev 0x02pci2 at ppb1 bus 2uhci0 at pci2 dev 0
function 0 "VMware UHCI" rev 0x00: apic 1 int 18ehci0 at pci2 dev 1
function 0 "VMware EHCI" rev 0x00: apic 1 int 19usb0 at ehci0: USB revision
2.0uhub0 at usb0 configuration 1 interface 0 "VMware EHCI root hub" rev
2.00/1.00 addr 1ahci0 at pci2 dev 3 function 0 "VMware AHCI" rev 0x00: apic
1 int 17, AHCI 1.3ahci0: port 0: 6.0Gb/sscsibus2 at ahci0: 32 targetscd0 at
scsibus2 targ 0 lun 0:  ATAP

Re: syspatch not installing 6.1 binary patches

2018-02-07 Thread R0me0 ***

Hello guys,

Clarified! Thank you so much all.



2018-02-07 18:17 GMT-02:00 Raf Czlonka :

> R0me0,
>
> Syspatch has been around *since* 6.1 - yes.
>
> Like Bryan already mentioned, binary patches are *only* available
> for the most recent release, though - it being 6.2.
>
> Cheers,
>
> Raf
>
> On Wed, Feb 07, 2018 at 07:33:16PM GMT, R0me0 *** wrote:
> > Hello, I got confused, since I already applied a lot on 6.1?
> > AFAIK , syspatch is supported since 6.1
> >
> > Regards,
> >
> >
> >
> > 2018-02-04 14:30 GMT-02:00 Bryan Steele :
> >
> > > On Sun, Feb 04, 2018 at 09:57:39AM -0200, R0me0 *** wrote:
> > > > Hello guys,
> > > >
> > > > I am trying to apply binary patches on 6.1 and syspatch isn't able to
> > > find
> > > > them
> > > >
> > > > on 6.2 works as expected.
> > > >
> > > > syspatch
> > > > -l
> > > >
> > > >
> > > > 001_dhcpd
> > > > 002_vmmfpu
> > > > 003_libressl
> > > > 004_softraid_concat
> > > > 005_pf_src_tracking
> > > > 006_libssl
> > > > 007_freetype
> > > > 008_exec_subr
> > > > 009_icmp_opts
> > > > 010_perl
> > > > 012_wsmux
> > > > 013_icmp6_linklocal
> > > > 014_libcrypto
> > > > 015_sigio
> > > > 016_sendsyslog
> > > > 017_fuse
> > > > 018_recv
> > > > 019_tcp_usrreq
> > > > 020_sockaddr
> > > > 021_ptrace
> > > > 022_fcntl
> > > > 023_wsdisplay
> > > > 024_sosplice
> > > > 025_ieee80211
> > > > 026_smap
> > > > 027_net80211_replay
> > > > 028_perl
> > > > 029_tcb
> > > > 030_xrstor
> > > > 031_xrstor_resume
> > >
> > > syspatch is only supported on the latest OpenBSD release, 6.2.
> > >
> > > See ajacoutot@'s FOSDEM 2018 talk:
> > > https://fosdem.org/2018/schedule/event/openbsd_base_
> > > system_maintenance_made_easy/
> > >
> > > -Bryan.
> > >
> > >
>

Re: syspatch not installing 6.1 binary patches

2018-02-07 Thread R0me0 ***

Hello, I got confused, since I already applied a lot on 6.1?
AFAIK , syspatch is supported since 6.1

Regards,



2018-02-04 14:30 GMT-02:00 Bryan Steele :

> On Sun, Feb 04, 2018 at 09:57:39AM -0200, R0me0 *** wrote:
> > Hello guys,
> >
> > I am trying to apply binary patches on 6.1 and syspatch isn't able to
> find
> > them
> >
> > on 6.2 works as expected.
> >
> > syspatch
> > -l
> >
> >
> > 001_dhcpd
> > 002_vmmfpu
> > 003_libressl
> > 004_softraid_concat
> > 005_pf_src_tracking
> > 006_libssl
> > 007_freetype
> > 008_exec_subr
> > 009_icmp_opts
> > 010_perl
> > 012_wsmux
> > 013_icmp6_linklocal
> > 014_libcrypto
> > 015_sigio
> > 016_sendsyslog
> > 017_fuse
> > 018_recv
> > 019_tcp_usrreq
> > 020_sockaddr
> > 021_ptrace
> > 022_fcntl
> > 023_wsdisplay
> > 024_sosplice
> > 025_ieee80211
> > 026_smap
> > 027_net80211_replay
> > 028_perl
> > 029_tcb
> > 030_xrstor
> > 031_xrstor_resume
>
> syspatch is only supported on the latest OpenBSD release, 6.2.
>
> See ajacoutot@'s FOSDEM 2018 talk:
> https://fosdem.org/2018/schedule/event/openbsd_base_
> system_maintenance_made_easy/
>
> -Bryan.
>
>

syspatch not installing 6.1 binary patches

2018-02-04 Thread R0me0 ***

Hello guys,

I am trying to apply binary patches on 6.1 and syspatch isn't able to find
them

on 6.2 works as expected.

syspatch
-l


001_dhcpd
002_vmmfpu
003_libressl
004_softraid_concat
005_pf_src_tracking
006_libssl
007_freetype
008_exec_subr
009_icmp_opts
010_perl
012_wsmux
013_icmp6_linklocal
014_libcrypto
015_sigio
016_sendsyslog
017_fuse
018_recv
019_tcp_usrreq
020_sockaddr
021_ptrace
022_fcntl
023_wsdisplay
024_sosplice
025_ieee80211
026_smap
027_net80211_replay
028_perl
029_tcb
030_xrstor
031_xrstor_resume





OpenBSD 6.1 (GENERIC.MP) #24: Wed Oct  4 18:47:09 CEST 2017
rob...@syspatch-61-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/
GENERIC.MP
real mem = 520028160 (495MB)
avail mem = 499642368 (476MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xe0010 (242 entries)
bios0: vendor Phoenix Technologies LTD version "6.00" date 04/05/2016
bios0: VMware, Inc. VMware Virtual Platform
acpi0 at bios0: rev 2
acpi0: sleep states S0 S1 S4 S5
acpi0: tables DSDT FACP BOOT APIC MCFG SRAT HPET WAET
acpi0: wakeup devices PCI0(S3) USB_(S1) P2P0(S3) S1F0(S3) S2F0(S3) S8F0(S3)
S16F(S3) S17F(S3) S18F(S3) S22F(S3) S23F(S3) S24F(S3) S25F(S3) PE40(S3)
S1F0(S3) PE50(S3) [...]
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Xeon(R) CPU E3-1275 v6 @ 3.80GHz, 3792.67 MHz
cpu0:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,MMX,FXSR,SSE,SSE2,SS,SSE3,PCLMUL,SSSE3,FMA3,CX16,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,HV,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,ARAT
cpu0: 256KB 64b/line 8-way L2 cache
cpu0: TSC frequency 3792672880 Hz
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: apic clock running at 65MHz
cpu1 at mainbus0: apid 2 (application processor)
cpu1: Intel(R) Xeon(R) CPU E3-1275 v6 @ 3.80GHz, 3792.35 MHz
cpu1:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,MMX,FXSR,SSE,SSE2,SS,SSE3,PCLMUL,SSSE3,FMA3,CX16,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,HV,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,ARAT
cpu1: 256KB 64b/line 8-way L2 cache
cpu1: smt 0, core 0, package 2
ioapic0 at mainbus0: apid 1 pa 0xfec0, version 11, 24 pins
acpimcfg0 at acpi0 addr 0xf000, bus 0-127
acpihpet0 at acpi0: 14318179 Hz
acpiprt0 at acpi0: bus 0 (PCI0)
acpicpu0 at acpi0: C1(@1 halt!)
acpicpu1 at acpi0: C1(@1 halt!)
"PNP0001" at acpi0 not configured
"PNP0303" at acpi0 not configured
"VMW0003" at acpi0 not configured
"PNP0A05" at acpi0 not configured
acpiac0 at acpi0: AC unit online
pvbus0 at mainbus0: VMware
vmt0 at pvbus0
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 "Intel 82443BX AGP" rev 0x01
ppb0 at pci0 dev 1 function 0 "Intel 82443BX AGP" rev 0x01
pci1 at ppb0 bus 1
pcib0 at pci0 dev 7 function 0 "Intel 82371AB PIIX4 ISA" rev 0x08
pciide0 at pci0 dev 7 function 1 "Intel 82371AB IDE" rev 0x01: DMA, channel
0 configured to compatibility, channel 1 configured to compatibility
pciide0: channel 0 disabled (no drives)
pciide0: channel 1 disabled (no drives)
piixpm0 at pci0 dev 7 function 3 "Intel 82371AB Power" rev 0x08: SMBus
disabled
"VMware VMCI" rev 0x10 at pci0 dev 7 function 7 not configured
vga1 at pci0 dev 15 function 0 "VMware SVGA II" rev 0x00
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
mpi0 at pci0 dev 16 function 0 "Symbios Logic 53c1030" rev 0x01: apic 1 int
17
mpi0: 0, firmware 1.3.41.32
scsibus1 at mpi0: 16 targets, initiator 7
sd0 at scsibus1 targ 0 lun 0:  SCSI4 0/direct
fixed
sd0: 8192MB, 512 bytes/sector, 16777216 sectors, thin
mpi0: target 0 Sync at 160MHz width 16bit offset 127 QAS 1 DT 1 IU 1
ppb1 at pci0 dev 17 function 0 "VMware PCI" rev 0x02
pci2 at ppb1 bus 2
uhci0 at pci2 dev 0 function 0 "VMware UHCI" rev 0x00: apic 1 int 18
ehci0 at pci2 dev 1 function 0 "VMware EHCI" rev 0x00: apic 1 int 19
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 configuration 1 interface 0 "VMware EHCI root hub" rev
2.00/1.00 addr 1
usb1 at uhci0: USB revision 1.0
uhub1 at usb1 configuration 1 interface 0 "VMware UHCI root hub" rev
1.00/1.00 addr 1
ppb2 at pci0 dev 21 function 0 "VMware PCIE" rev 0x01
pci3 at ppb2 bus 3
ppb3 at pci0 dev 21 function 1 "VMware PCIE" rev 0x01
pci4 at ppb3 bus 4
vmx0 at pci4 dev 0 function 0 "VMware VMXNET3" rev 0x01: apic 1 int 18,
address 00:0c:29:2f:23:76
ppb4 at pci0 dev 21 function 2 "VMware PCIE" rev 0x01
pci5 at ppb4 bus 5
ppb5 at pci0 dev 21 function 3 "VMware PCIE" rev 0x01
pci6 at ppb5 bus 6
ppb6 at pci0 dev 21 function 4 "VMware PCIE" rev 0x01
pci7 at ppb6 bus 7
ppb7 at pci0 dev 21 function 5 "VMware

RPI3 TL-WN722N

2017-12-04 Thread R0me0 ***

Hi , just would like to share.


I was trying TL-WN722N v 1.10 ( Atheros AR9271L )
On RPI3 , my system just hangs without any message

on AMD64 ( KVM  )
I have athn0 iface but with the follow error:
athn0: firmware command 0x18 timed out

Regards,


#
dmesg

OpenBSD 6.2 (GENERIC) #34: Tue Oct  3 23:53:05 MDT 2017
dera...@arm64.openbsd.org:/usr/src/sys/arch/arm64/compile/GENERIC
real mem  = 964972544 (920MB)
avail mem = 909017088 (866MB)
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
syscon0 at simplebus0
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 "SanDisk Cruzer Fit" rev
2.10/1.00 addr 4
umass0: using SCSI over Bulk-Only
scsibus0 at umass0: 2 targets, initiator 0
sd0 at scsibus0 targ 1 lun 0:  SCSI4 0/direct
removable serial.07815571580517102513
sd0: 15264MB, 512 bytes/sector, 31260672 sectors
urtwn0 at uhub1 port 5 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 (ac7e902ee4f2d3d5.a) swap on sd0b dump on sd0b

[RPI3] 6.2 - release ( panic )

2017-11-06 Thread R0me0 ***

ddb> trace
db_enter() at panic+0x154
panic() at pool_get+0x68
pool_get() at uvm_mapent_alloc+0x1fc
uvm_mapent_alloc() at uvm_map_mkentry+0x54
uvm_map_mkentry() at uvm_mapent_clone+0x88
uvm_mapent_clone() at uvm_mapent_forkcopy+0x4c
uvm_mapent_forkcopy() at uvmspace_fork+0x14c
uvmspace_fork() at process_new+0x14c
process_new() at fork1+0x224
fork1() at svc_handler+0x1bc
svc_handler() at do_el0_sync+0xbc
do_el0_sync() at handle_el0_sync+0x68
handle_el0_sync() at 0x1266da418
--- trap ---
ddb> show panic
pool_do_get: vmmpepl free list modified: page 0xff80173b4000; item addr
0xf
f80173b40c8; offset 0x0=0x0 != 0xc7735af87fa0349f
ddb> show registers
x0   0x1
x10xff8014ae5000
x2  0x4c
x3   0x8
x40xff8014de0908
x5 0
x6 0
x70xc7735af87fa0349f
x8   0x1
x9 0xa46ee291d5b2fdb
x10  0x1
x11 0x64
x12 0x17
x13  0x53a684000
x14   0x1000
x15   0xff80008d1c98kernel_pmap_
x16   0xff8000671cc8ap_bits_user
x17   0xff8000671d08ap_bits_kern
x18   0xff8014de0970
x19   0xff800061a6e6$d.3+0x18e
x200x100
x21   0xff80008dc000uvm_vmspace_pool+0x158
x22   0xffc8
x23   0xff8014de0a80
x24   0xff8014de09b0
x250
x26  0x53a684000
x27   0xff80173b49f8
x280
x29   0xff8014de0a70
x300
sp0xff8014de0970
spsr  0x6345
elr   0xff80004dc498db_enter
lr0xff800031c6ecpanic+0x158
panic+0x158:


ddb> ps
  PID TID   PPIDUID  S   FLAGS  WAIT  COMMAND
* 5837   25875  88087  0  70x12ksh
88087  241331  86230  0  30x10008a  pause sh
86230  259221   7677  0  30x10008a  pause sh
 7677 169  38181  0  30x100090  piperdcron
12456  445896  1566  30x90  kqreadtor
44072  216602  1  0  30x100080  poll  ntpd
24888  242028  21660 83  30x100092  poll  ntpd
21660  150396  1 83  30x100092  poll  ntpd
  824  265553  1  0  30x100083  ttyin getty
38181  113849  1  0  30x100098  poll  cron
14013  470674  1688  30x90  kqreaddnscrypt-proxy
98479   53453  1688  30x90  kqreaddnscrypt-proxy
36391  472501  1  0  30x80  selectsshd
70148  283963  1 53  30x90  kqreadunbound
92581  409492616 74  30x100092  bpf   pflogd
  616  508759  1  0  30x80  netio pflogd
41315  134479   2739 73  30x100090  kqreadsyslogd
 2739  197161  1  0  30x100082  netio syslogd
96645  164218  0  0  2 0x14200zerothread
48300  198589  0  0  3 0x14200  aiodoned  aiodoned
98762   75133  0  0  3 0x14200  syncerupdate
80796  175535  0  0  3 0x14200  cleaner   cleaner
29998  419764  0  0  3 0x14200  reaperreaper
21744  283546  0  0  3 0x14200  pgdaemon  pagedaemon
31037  318637  0  0  3 0x14200  bored crynlk
57969  481903  0  0  3 0x14200  bored crypto
16509  354395  0  0  3 0x14200  usbtskusbtask
32724   77788  0  0  3 0x14200  usbatsk   usbatsk
 3691  374481  0  0  3 0x14200  bored dwc2
87002  340072  0  0  3 0x14200  bored softnet
 3135  237163  0  0  3 0x14200  bored systqmp
  241  215387  0  0  3 0x14200  bored systq
90355  370719  0  0  3  0x40014200  bored softclock
93815  200865  0  0  3  0x40014200idle0
99181  485436  0  0  3 0x14200  kmalloc   kmthread
1  402733  0  0  30x82  wait  init
0   0 -1  0  3 0x10200  scheduler swapper


dmesg



OpenBSD 6.2 (GENERIC) #34: Tue Oct  3 23:53:05 MDT 2017
   dera...@arm64.openbsd.org:/usr/src/sys/arch/arm64/compile/GENERIC
real mem  = 964972544 (920MB)
avail mem = 909017088 (866MB)
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"
bcm

OpenBSD 6.1 Vmware esxi 6.5 ( vmwpvs driver )

2017-09-18 Thread R0me0 ***

Hello guys,

Just noticed, I can't install OpenBSD using fully disk encryption
with vmwpvs driver.

If another driver is used like LSI Logic SAS, then installation is
performed as expected.

I tested with OpenBSD 6.1 and latest Vmware ESXI 6.5 with all updates
applied.

Thanks in advance,


dmesg:


OpenBSD 6.1 (GENERIC.MP) #20: Sat Apr  1 13:45:56 MDT 2017
   dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 4278124544 (4079MB)
avail mem = 4143792128 (3951MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root

bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xe0010 (242 entries)

bios0: vendor Phoenix Technologies LTD version "6.00" date 04/05/2016

bios0: VMware, Inc. VMware Virtual Platform

acpi0 at bios0: rev 2

acpi0: sleep states S0 S1 S4 S5

acpi0: tables DSDT FACP BOOT APIC MCFG SRAT HPET WAET

acpi0: wakeup devices PCI0(S3) USB_(S1) P2P0(S3) S1F0(S3) S2F0(S3) S8F0(S3)
S16F(S3) S18F(S3) S22F(S3) S23F(S3) S24F(S3) S25F(S3) PE40(S3) S1F0(S3)
PE50(S3) S1F0(S3) [...]
acpitimer0 at acpi0: 3579545 Hz, 24 bits

acpimadt0 at acpi0 addr 0xfee0: PC-AT compat

cpu0 at mainbus0: apid 0 (boot processor)

cpu0: Intel(R) Xeon(R) CPU E3-1275 v5 @ 3.60GHz, 3600.62 MHz

cpu0:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,MMX,FXSR,SSE,SSE2,SS,SSE3,PCLMUL,SSSE3,FMA3,CX16,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,
F16C,RDRAND,HV,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,SENSOR,ARAT

cpu0: 256KB 64b/line 8-way L2 cache
cpu0: TSC frequency 3600617700 Hz
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: apic clock running at 65MHz
cpu1 at mainbus0: apid 2 (application processor)
cpu1: Intel(R) Xeon(R) CPU E3-1275 v5 @ 3.60GHz, 3600.29 MHz
cpu1:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,MMX,FXSR,SSE,SSE2,SS,SSE3,PCLMUL,SSSE3,FMA3,CX16,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,
F16C,RDRAND,HV,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,SENSOR,ARAT

cpu1: 256KB 64b/line 8-way L2 cache
cpu1: smt 0, core 0, package 2
ioapic0 at mainbus0: apid 1 pa 0xfec0, version 11, 24 pins
acpimcfg0 at acpi0 addr 0xf000, bus 0-127
acpihpet0 at acpi0: 14318179 Hz
acpiprt0 at acpi0: bus 0 (PCI0)
acpicpu0 at acpi0: C1(@1 halt!)
acpicpu1 at acpi0: C1(@1 halt!)
"PNP0001" at acpi0 not configured
"PNP0303" at acpi0 not configured
"VMW0003" at acpi0 not configured
"PNP0A05" at acpi0 not configured
acpiac0 at acpi0: AC unit online
pvbus0 at mainbus0: VMware
vmt0 at pvbus0
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 "Intel 82443BX AGP" rev 0x01
ppb0 at pci0 dev 1 function 0 "Intel 82443BX AGP" rev 0x01
pci1 at ppb0 bus 1
pcib0 at pci0 dev 7 function 0 "Intel 82371AB PIIX4 ISA" rev 0x08
pciide0 at pci0 dev 7 function 1 "Intel 82371AB IDE" rev 0x01: DMA, channel
0 configured to compatibility, channel 1 configured to compatibility
pciide0: channel 0 disabled (no drives)
pciide0: channel 1 disabled (no drives)
piixpm0 at pci0 dev 7 function 3 "Intel 82371AB Power" rev 0x08: SMBus
disabled
"VMware VMCI" rev 0x10 at pci0 dev 7 function 7 not configured
vga1 at pci0 dev 15 function 0 "VMware SVGA II" rev 0x00
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
ppb1 at pci0 dev 17 function 0 "VMware PCI" rev 0x02
pci2 at ppb1 bus 2
uhci0 at pci2 dev 0 function 0 "VMware UHCI" rev 0x00: apic 1 int 18
ehci0 at pci2 dev 1 function 0 "VMware EHCI" rev 0x00: apic 1 int 19
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 configuration 1 interface 0 "VMware EHCI root hub" rev
2.00/1.00 addr 1
usb1 at uhci0: USB revision 1.0
uhub1 at usb1 configuration 1 interface 0 "VMware UHCI root hub" rev
1.00/1.00 addr 1
ppb2 at pci0 dev 21 function 0 "VMware PCIE" rev 0x01
pci3 at ppb2 bus 3
mpi0 at pci3 dev 0 function 0 "Symbios Logic SAS1068" rev 0x01: apic 1 int
18
mpi0: SAS3444, firmware 1.3.41.32
scsibus1 at mpi0: 256 targets, initiator 16
sd0 at scsibus1 targ 0 lun 0:  SCSI4 0/direct
fixed
sd0: 145408MB, 512 bytes/sector, 297795584 sectors, thin
ppb3 at pci0 dev 21 function 1 "VMware PCIE" rev 0x01
pci4 at ppb3 bus 4
ppb4 at pci0 dev 21 function 2 "VMware PCIE" rev 0x01
pci5 at ppb4 bus 5
ppb5 at pci0 dev 21 function 3 "VMware PCIE" rev 0x01
pci6 at ppb5 bus 6
ppb6 at pci0 dev 21 function 4 "VMware PCIE" rev 0x01
pci7 at ppb6 bus 7
ppb7 at pci0 dev 21 function 5 "VMware PCIE" rev 0x01
pci8 at ppb7 bus 8
ppb8 at pci0 dev 21 function 6 "VMware PCIE" rev 0x01
pci9 at ppb8 bus 9
ppb9 at pci0 dev 21 function 7 "VMware PCIE" rev 0x01
pci10 at ppb9 bus 10
ppb10 at pci0 dev 22 function 0 "VMware PCIE" rev 0x01
pci11 at ppb10 bus 11
vmx0 at pci11 dev 0 function 0 "VMware VMXNET3" rev 0x01: apic 1 int 19,
address 00:0c:29:d5:0c:b1
ppb11

Re: [RPI3] urtwn0: device timeout when tor is being bootstraped

2017-08-28 Thread R0me0 ***

I figured out!

Just running snapshot without the patch.

I went with rpi3 closest to AP.

Just connected over tor.

What really is happening is: if too far of AP and has loss of
connectivity or some kind of frame loss is causing the issue.

If you get far of AP, I think you will be able to reproduce.

That's it. I am sure!





2017-08-28 14:24 GMT-03:00 R0me0 *** :

> Hi Stefan,
>
> I have improved the signal of the AP router, changed the power supply as
> suggested by you, sent you an image of dongle and the ifconfig of urtwn0 to
> provided as much I can with details of the environment.
>
> With snapshot of today every single time I try to bring up tor I had :
>
> rpibsd /bsd: urtwn0 device timeout  urtwn0: RUN -> INIT ( and the device
> hangs )
>
> But with the patch below applied on sources from August 25,  I was able to
> build the tor circuit after I improved the signal and ensured not packet
> loss. I am checking every single element involved on this.
>
> I will apply this patch to snapshot of today and perform more tests. From
> now without the patch below the system hangs completely.
>
>
> Thank you so much for spent time on this.
>
>
> rtwn.c
> ===
> RCS file: /cvs/src/sys/dev/ic/rtwn.c,v
> retrieving revision 1.33
> diff -u -p -r1.33 rtwn.c
> --- rtwn.c  23 Aug 2017 09:25:17 -  1.33
> +++ rtwn.c  26 Aug 2017 10:33:43 -
> @@ -1375,7 +1375,8 @@ rtwn_watchdog(struct ifnet *ifp)
> if (sc->sc_tx_timer > 0) {
> if (--sc->sc_tx_timer == 0) {
> printf("%s: device timeout\n",
> sc->sc_pdev->dv_xname);
> -   task_add(systq, &sc->init_task);
> +   if (sc->chip & RTWN_CHIP_PCI)
> +   task_add(systq, &sc->init_task);
> ifp->if_oerrors++;
> return;
> }
>
> 2017-08-28 13:41 GMT-03:00 Stefan Sperling :
>
>> On Mon, Aug 28, 2017 at 01:09:17PM -0300, R0me0 *** wrote:
>> > This is snapshot from today:
>> >
>> > Aug 28 16:05:25 rpibsd Tor[54551]: Bootstrapped 50%: Loading relay
>> > descriptors
>> > urtwn0: device timeout
>> > Aug 28 16:05:30 rpibsd /bsd: urtwn0: device timeout
>>
>> This again works fine here without device timeout messages:
>>
>> $ tail /var/log/messages
>> Aug 28 15:47:19 carberry Tor[69953]: Bootstrapped 56%: Loading relay
>> descriptors
>> Aug 28 15:47:21 carberry Tor[69953]: Bootstrapped 63%: Loading relay
>> descriptors
>> Aug 28 15:47:22 carberry Tor[69953]: Bootstrapped 68%: Loading relay
>> descriptors
>> Aug 28 15:47:22 carberry Tor[69953]: Bootstrapped 75%: Loading relay
>> descriptors
>> Aug 28 15:47:22 carberry Tor[69953]: Bootstrapped 80%: Connecting to the
>> Tor network
>> Aug 28 15:47:23 carberry Tor[69953]: Bootstrapped 85%: Finishing
>> handshake with first hop
>> Aug 28 15:47:23 carberry Tor[69953]: Bootstrapped 90%: Establishing a Tor
>> circuit
>> Aug 28 15:47:24 carberry Tor[69953]: Tor has successfully opened a
>> circuit. Looks like client functionality is working.
>> Aug 28 15:47:24 carberry Tor[69953]: Bootstrapped 100%: Done
>> $ date
>> Mon Aug 28 18:31:52 CEST 2017
>>
>> Ping test has been running fine as well:
>> 9851 packets transmitted, 9828 packets received, 3 duplicates, 0.2%
>> packet loss
>> round-trip min/avg/max/std-dev = 2.759/114.881/3848.698/1285.292 ms
>>
>> I am not convinced that the urtwn driver is part of your problem.
>> Unless you can show convincing evidence that it's a driver problem I
>> am not going to spend more time on this.
>>
>> Have you already tried using this urtwn device in another machine?
>> I suspect it will work just fine.
>>
>> It seems your hardware is not behaving as expected.
>> Have you already tried using a different electrical power supply for your
>> rpi3?
>>
>
>

Re: [RPI3] urtwn0: device timeout when tor is being bootstraped

2017-08-28 Thread R0me0 ***

Hi Stefan,

I have improved the signal of the AP router, changed the power supply as
suggested by you, sent you an image of dongle and the ifconfig of urtwn0 to
provided as much I can with details of the environment.

With snapshot of today every single time I try to bring up tor I had :

rpibsd /bsd: urtwn0 device timeout  urtwn0: RUN -> INIT ( and the device
hangs )

But with the patch below applied on sources from August 25,  I was able to
build the tor circuit after I improved the signal and ensured not packet
loss. I am checking every single element involved on this.

I will apply this patch to snapshot of today and perform more tests. From
now without the patch below the system hangs completely.


Thank you so much for spent time on this.


rtwn.c
===
RCS file: /cvs/src/sys/dev/ic/rtwn.c,v
retrieving revision 1.33
diff -u -p -r1.33 rtwn.c
--- rtwn.c  23 Aug 2017 09:25:17 -  1.33
+++ rtwn.c  26 Aug 2017 10:33:43 -
@@ -1375,7 +1375,8 @@ rtwn_watchdog(struct ifnet *ifp)
if (sc->sc_tx_timer > 0) {
if (--sc->sc_tx_timer == 0) {
printf("%s: device timeout\n",
sc->sc_pdev->dv_xname);
-   task_add(systq, &sc->init_task);
+   if (sc->chip & RTWN_CHIP_PCI)
+   task_add(systq, &sc->init_task);
ifp->if_oerrors++;
return;
}

2017-08-28 13:41 GMT-03:00 Stefan Sperling :

> On Mon, Aug 28, 2017 at 01:09:17PM -0300, R0me0 *** wrote:
> > This is snapshot from today:
> >
> > Aug 28 16:05:25 rpibsd Tor[54551]: Bootstrapped 50%: Loading relay
> > descriptors
> > urtwn0: device timeout
> > Aug 28 16:05:30 rpibsd /bsd: urtwn0: device timeout
>
> This again works fine here without device timeout messages:
>
> $ tail /var/log/messages
> Aug 28 15:47:19 carberry Tor[69953]: Bootstrapped 56%: Loading relay
> descriptors
> Aug 28 15:47:21 carberry Tor[69953]: Bootstrapped 63%: Loading relay
> descriptors
> Aug 28 15:47:22 carberry Tor[69953]: Bootstrapped 68%: Loading relay
> descriptors
> Aug 28 15:47:22 carberry Tor[69953]: Bootstrapped 75%: Loading relay
> descriptors
> Aug 28 15:47:22 carberry Tor[69953]: Bootstrapped 80%: Connecting to the
> Tor network
> Aug 28 15:47:23 carberry Tor[69953]: Bootstrapped 85%: Finishing handshake
> with first hop
> Aug 28 15:47:23 carberry Tor[69953]: Bootstrapped 90%: Establishing a Tor
> circuit
> Aug 28 15:47:24 carberry Tor[69953]: Tor has successfully opened a
> circuit. Looks like client functionality is working.
> Aug 28 15:47:24 carberry Tor[69953]: Bootstrapped 100%: Done
> $ date
> Mon Aug 28 18:31:52 CEST 2017
>
> Ping test has been running fine as well:
> 9851 packets transmitted, 9828 packets received, 3 duplicates, 0.2% packet
> loss
> round-trip min/avg/max/std-dev = 2.759/114.881/3848.698/1285.292 ms
>
> I am not convinced that the urtwn driver is part of your problem.
> Unless you can show convincing evidence that it's a driver problem I
> am not going to spend more time on this.
>
> Have you already tried using this urtwn device in another machine?
> I suspect it will work just fine.
>
> It seems your hardware is not behaving as expected.
> Have you already tried using a different electrical power supply for your
> rpi3?
>

Re: [RPI3] urtwn0: device timeout when tor is being bootstraped

2017-08-28 Thread R0me0 ***

This is snapshot from today:

ifconfig urtwn0


urtwn0: flags=8843 mtu 1500
   lladdr 98:de:d0:11:ac:a1
   index 4 priority 4 llprio 3
   groups: wlan egress
   media: IEEE802.11 autoselect (OFDM54 mode 11g)
   status: active
   ieee80211: nwid localhost chan 11 bssid 54:23:da:32:30:80 -78dBm
wpakey 0x4532432342346123467451284312423564443124124 wpaprotos wpa2 wpaakms
psk wpaciphers ccmp wpagroupc
ipher ccmp
   inet 192.168.0.17 netmask 0xff00 broadcast 192.168.0.255

# pkg_add tor
# rcctl start tor
# tail -f /var/log/messages
Aug 28 16:04:48 rpibsd Tor[54551]: Tor 0.3.0.6 (git-47d2e4f06ec26a79)
running on OpenBSD with Libevent 2.0.22-stable, OpenSSL LibreSSL 2.6.1 and
Zlib 1.2.3.
Aug 28 16:04:48 rpibsd Tor[54551]: Tor can't help you if you use it wrong!
Learn how to be safe at https://www.torproject.org/download/download#warning
Aug 28 16:04:48 rpibsd Tor[54551]: Read configuration file
"/etc/tor/torrc".
Aug 28 16:04:48 rpibsd Tor[54551]: Opening Socks listener on 127.0.0.1:9050
Aug 28 16:04:50 rpibsd Tor[54551]: Parsing GEOIP IPv4 file
/usr/local/share/tor/geoip.
Aug 28 16:05:04 rpibsd Tor[54551]: Parsing GEOIP IPv6 file
/usr/local/share/tor/geoip6.
Aug 28 16:05:05 rpibsd Tor[54551]: We were built to run on a 64-bit CPU,
with OpenSSL 1.0.1 or later, but with a version of OpenSSL that apparently
lacks accelerated support for the NIST P-224 and P-
256 groups. Building openssl with such support (using the
enable-ec_nistp_64_gcc_128 option when configuring it) would make ECDH much
faster.
Aug 28 16:05:09 rpibsd Tor[54551]: Bootstrapped 0%: Starting
Aug 28 16:05:10 rpibsd Tor[54551]: couldn't find end of hashed material "
directory-signature"
Aug 28 16:05:10 rpibsd Tor[54551]: Unable to compute digest of
network-status
Aug 28 16:05:11 rpibsd Tor[54551]: Unable to parse networkstatus consensus
Aug 28 16:05:11 rpibsd Tor[54551]: Couldn't load consensus microdesc
networkstatus from "/var/tor/cached-microdesc-consensus"
Aug 28 16:05:11 rpibsd Tor[54551]: Starting with guard context "default"
Aug 28 16:05:11 rpibsd Tor[54551]: Bootstrapped 5%: Connecting to directory
server
Aug 28 16:05:11 rpibsd Tor[54551]: Bootstrapped 10%: Finishing handshake
with directory server
Aug 28 16:05:12 rpibsd Tor[54551]: Bootstrapped 15%: Establishing an
encrypted directory connection
Aug 28 16:05:12 rpibsd Tor[54551]: Bootstrapped 20%: Asking for
networkstatus consensus
Aug 28 16:05:12 rpibsd Tor[54551]: Bootstrapped 25%: Loading networkstatus
consensus
Aug 28 16:05:24 rpibsd Tor[54551]: I learned some more directory
information, but not enough to build a circuit: We're missing descriptors
for some of our primary entry guards
Aug 28 16:05:25 rpibsd Tor[54551]: Bootstrapped 50%: Loading relay
descriptors
urtwn0: device timeout
Aug 28 16:05:30 rpibsd /bsd: urtwn0: device timeout

dmesg:


OpenBSD 6.2-beta (GENERIC) #0: Mon Aug 28 18:01:26 AEST 2017
   j...@arm64.jsg.id.au:/usr/src/sys/arch/arm64/compile/GENERIC
real mem  = 964993024 (920MB)
avail mem = 909037568 (866MB)
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 2 configuration 1 interface 0 "HP v165w" rev
2.00/16.38 addr 4
umass0: using SCSI over Bulk-Only
scsibus0 at umass0: 2 targets, initiator 0
sd0 at scsibus0 targ 1 lun 0:  SCSI2 0/direct removable
serial.03f053071C210624
sd0: 15600MB, 512 bytes/sector, 31950720 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
.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 (ea8d362141524188.a) swap on sd0b dump on sd0b
WARNING: / was not properly unmounted
WARNING: CHECK AND RESET THE DATE!



2017-08-28 6:25 GMT-03:00 Ste

Re: [RPI3] urtwn0: device timeout when tor is being bootstraped

2017-08-27 Thread R0me0 ***

Hi Stefan,
How are you doing today? Hope very well.

Unfortunately, The system just hangs, I will perform more tests and dig
into this and with a little of luck, I can provide more information on this.

Thank you :)







2017-08-27 9:52 GMT-03:00 Stefan Sperling :

> On Sun, Aug 27, 2017 at 02:48:51PM +0200, Stefan Sperling wrote:
> > On Sat, Aug 26, 2017 at 07:11:58PM -0300, R0me0 *** wrote:
> > > Hiya!
> > >
> > > Stefan, initially patch worked, after the timeout, the system kept
> running,
> >
> > Great, thanks for testing.
> >
> > > but at moment I have had put the interface urtwn0 down ( ifconfig
> urtwn0
> > > down ) the system hangs.
> >
> > That sounds like an unrelated problem. I don't see this problem on amd64
> > where I can run 'ifconfig urtwn0 down' without hanging the machine.
> >
> > Is this problem perhaps specific to the rpi3 or arm64 machines in
> general?
>
> Correction: In fact the 'device timeout' and 'ifconfig urtwn0' run the
> same bit of code. So it's probable still the same problem but you have
> found another way to trigger it.
>
> However, I cannot debug this problem without more information.
> Does anything happen on the serial console when it hangs?
>

Re: [RPI3] urtwn0: device timeout when tor is being bootstraped

2017-08-26 Thread R0me0 ***

Hiya!

Stefan, initially patch worked, after the timeout, the system kept running,
but at moment I have had put the interface urtwn0 down ( ifconfig urtwn0
down ) the system hangs.

Another thing I have noticed not sure at this point if related. but when my
date/time was updated ( used the date command to correct it ) I have the
timeout message on interface

That's it.

Thank you so much for everything.

Regards,



2017-08-26 7:40 GMT-03:00 Stefan Sperling :

> On Fri, Aug 25, 2017 at 05:35:10PM -0300, R0me0 *** wrote:
> > Hello all,
> > Stefan thanks for heads up! :)
> >
> > following dmesg:
>
> Thanks.
>
> Could you try the diff below? Does it help?
>
> With this diff, if a device timeout happens, the interface may either
> continue working or it could stall and not recover automatically.
> However, you should be able to keep using the system and if necessary
> run ifconfig to reset urtwn0 into a working state.
>
> Index: rtwn.c
> ===
> RCS file: /cvs/src/sys/dev/ic/rtwn.c,v
> retrieving revision 1.33
> diff -u -p -r1.33 rtwn.c
> --- rtwn.c  23 Aug 2017 09:25:17 -  1.33
> +++ rtwn.c  26 Aug 2017 10:33:43 -
> @@ -1375,7 +1375,8 @@ rtwn_watchdog(struct ifnet *ifp)
> if (sc->sc_tx_timer > 0) {
> if (--sc->sc_tx_timer == 0) {
> printf("%s: device timeout\n",
> sc->sc_pdev->dv_xname);
> -   task_add(systq, &sc->init_task);
> +   if (sc->chip & RTWN_CHIP_PCI)
> +   task_add(systq, &sc->init_task);
> ifp->if_oerrors++;
> return;
> }
>
>

Re: [RPI3] urtwn0: device timeout when tor is being bootstraped

2017-08-25 Thread R0me0 ***

Hello all,
Stefan thanks for heads up! :)

following dmesg:

# dmesg

OpenBSD 6.2-beta (GENERIC) #0: Tue Aug 22 17:53:50 AEST 2017
   j...@arm64.jsg.id.au:/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:  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 :

> 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 *** :
> >
> > > 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 *** :
> > >
> > >> + 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 *** :
> > >>
> > >>> 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  >:
> > >>>
> > >>>> 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.
> > >>>>
> > >>>
> > >>>
> > >>
> > >
>

Re: [RPI3] urtwn0: device timeout when tor is being bootstraped

2017-08-24 Thread R0me0 ***

So, I did : ifconfig urtwn0 debug

# urtwn0: device timeout
urtwn0: RUN -> INIT




2017-08-24 17:44 GMT-03:00 R0me0 *** :

> 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 *** :
>
>> + 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 *** :
>>
>>> 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 :
>>>
>>>> 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.
>>>>
>>>
>>>
>>
>

Re: [RPI3] urtwn0: device timeout when tor is being bootstraped

2017-08-24 Thread R0me0 ***

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 *** :

> + 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 *** :
>
>> 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 :
>>
>>> 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.
>>>
>>
>>
>

Re: [RPI3] urtwn0: device timeout when tor is being bootstraped

2017-08-24 Thread R0me0 ***

+ 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 *** :

> 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 :
>
>> 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.
>>
>
>

[RPI3] urtwn0: device timeout when tor is being bootstraped

2017-08-24 Thread R0me0 ***

I have noticed the following behavior:


urtwn0: device timeout

The system just hangs and hard reboot is needed.

[RPI3] Kernel Relink

2017-08-23 Thread R0me0 ***

I have noticed this just with RPI3, every reboot, kernel relink fails. ( It
comes from 6.1-current )

/usr/share/compile/GENERIC/relink.log

(SHA256) /bsd: OK
LD="ld" sh makegap.sh 0xd4d4d4d4 gapdummy.o
ld: error: gap.link:11: unknown command ;
ld: error: gap.link:11: LONG(0xd4d4d4d4);
ld: error: gap.link:11:   ^
ld: error: cannot open gapdummy.o: No such file or directory
ld: error: target emulation unknown: -m or at least one .o file required
*** Error 1 in /usr/share/compile/GENERIC (Makefile:531 'newbsd')


is it expected?

Thanks in advance,


dmesg:


OpenBSD 6.2-beta (GENERIC) #0: Tue Aug 22 17:53:50 AEST 2017
   j...@arm64.jsg.id.au:/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:  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: CHECK AND RESET THE DATE!

Re: [rpi3] OpenBSD-6.2-beta does not boot after installer finish

2017-08-23 Thread R0me0 ***

Fixed :)
Thanks

2017-08-22 6:04 GMT-03:00 Jonathan Gray :

> On Tue, Aug 22, 2017 at 12:27:55PM +1000, Jonathan Gray wrote:
> > On Mon, Aug 21, 2017 at 06:28:16PM -0300, R0me0 *** wrote:
> > > Hello,
> > >
> > > Wrote miniroot62.fs to usb stick as usual, boots and installs
> > >
> > > ( tried with miniroot from ftp.openbsd.org and ftp.hostserver.de )
> > >
> > > miniroot62.fs 21-Aug-2017 03:10  22020096
> > >
> > >
> > > But after reboot, rpi3 does not initialize. Just boot if I rewrite
> miniroot
> > > to usb sitck
> > >
> > >
> > >
> > > Relinking to create unique kernel...done.
> > >
> > > CONGRATULATIONS! Your OpenBSD install has been successfully completed!
> > > To boot the new system, enter 'reboot' at the command prompt.
> > > When you login to your new system the first time, please read your mail
> > > using the 'mail' command.
> > >
> > > # reboot
> > > syncing disks... done
> > > rebooting...
> >
> > scan_dmesg does not seem to work correctly for this.
> >
> > # sed -n 's/^mainbus0 at root: \(.*\)$/\1/p' /var/run/dmesg.boot
> > Raspberry Pi 3 Model B Rev 1.2
> >
> > but scan_dmesg sorts the words of the string so that
> >
> > $(scan_dmesg 's/^mainbus0 at root: \(.*\)$/\1/p') gives
> >
> > "1.2 3 B Model Pi Raspberry Rev"
> >
> > The next snapshot will include a revised version of the diff
> > to use $(sysctl -n hw.product).
>
> 22nd August snapshot should work.  Thanks for the report.
>
> >
> > armv7 should be changed to use the same.
> >
> > Index: miniroot/Makefile
> > ===
> > RCS file: /cvs/src/distrib/arm64/miniroot/Makefile,v
> > retrieving revision 1.4
> > diff -u -p -r1.4 Makefile
> > --- miniroot/Makefile 7 May 2017 12:00:12 -   1.4
> > +++ miniroot/Makefile 22 Aug 2017 02:25:34 -
> > @@ -65,6 +65,8 @@ do_files:
> >   cp /usr/mdec/BOOTAA64.EFI ${MOUNT_POINT}/efi/boot/bootaa64.efi
> >   echo bootaa64.efi > ${MOUNT_POINT}/efi/boot/startup.nsh
> >   echo 
> > 'arm_control=0x200\nenable_uart=1\ndevice_tree_address=0x100\nkernel=u-boot.bin'
> > ${MOUNT_POINT}/config.txt
> > + dd if=${PUBOOT}/pine64_plus/u-boot-sunxi-with-spl.bin \
> > + of=${VND_CDEV} bs=1024 seek=8
> >
> >  rd_setup:
> >   dd if=/dev/zero of=${IMAGE} bs=512 count=${NBLKS}
> > Index: ramdisk/Makefile
> > ===
> > RCS file: /cvs/src/distrib/arm64/ramdisk/Makefile,v
> > retrieving revision 1.2
> > diff -u -p -r1.2 Makefile
> > --- ramdisk/Makefile  18 Feb 2017 02:01:53 -  1.2
> > +++ ramdisk/Makefile  22 Aug 2017 02:25:34 -
> > @@ -18,6 +18,7 @@ DISKTYPE=   rdroot
> >  MAKEFSARGS_RD=   -o disklabel=${DISKTYPE},minfree=0,density=4096
> >
> >  DIRS=\
> > + pine64 \
> >   rpi
> >
> >  .ifndef DESTDIR
> > Index: ramdisk/install.md
> > ===
> > RCS file: /cvs/src/distrib/arm64/ramdisk/install.md,v
> > retrieving revision 1.6
> > diff -u -p -r1.6 install.md
> > --- ramdisk/install.md28 Jul 2017 18:15:44 -  1.6
> > +++ ramdisk/install.md22 Aug 2017 02:25:34 -
> > @@ -38,23 +38,35 @@ MOUNT_ARGS_msdos="-o-l"
> >  md_installboot() {
> >   local _disk=/dev/$1 _mdec _plat
> >
> > + case $(sysctl -n hw.product) in
> > + *Pine64*)   _plat=pine64;;
> > + *'Raspberry Pi'*)   _plat=rpi;;
> > + esac
> > +
> >   # Mount MSDOS partition, extract U-Boot and copy UEFI boot program
> >   mount ${MOUNT_ARGS_msdos} ${_disk}i /mnt/mnt
> >   mkdir -p /mnt/mnt/efi/boot
> >   cp /mnt/usr/mdec/BOOTAA64.EFI /mnt/mnt/efi/boot/bootaa64.efi
> >   echo bootaa64.efi > /mnt/mnt/efi/boot/startup.nsh
> >
> > - _plat=rpi
> >   _mdec=/usr/mdec/$_plat
> >
> > - cp $_mdec/{bootcode.bin,start.elf,fixup.dat,*.dtb} /mnt/mnt/
> > - cp $_mdec/u-boot.bin /mnt/mnt/
> > - cat > /mnt/mnt/config.txt<<-__EOT
> > - arm_control=0x200
> > - enable_uart=1
> > - device_tree_address=0x100
> > - kernel=u-boot.bin
> > - __EOT
> > + case $_pla

[rpi3] OpenBSD-6.2-beta does not boot after installer finish

2017-08-21 Thread R0me0 ***

Hello,

Wrote miniroot62.fs to usb stick as usual, boots and installs

( tried with miniroot from ftp.openbsd.org and ftp.hostserver.de )

miniroot62.fs 21-Aug-2017 03:10  22020096


But after reboot, rpi3 does not initialize. Just boot if I rewrite miniroot
to usb sitck



Relinking to create unique kernel...done.

CONGRATULATIONS! Your OpenBSD install has been successfully completed!
To boot the new system, enter 'reboot' at the command prompt.
When you login to your new system the first time, please read your mail
using the 'mail' command.

# reboot
syncing disks... done
rebooting...

Re: [RPI3] TP-Link TL-WN821N V4 kernel panic

2017-08-04 Thread R0me0 ***

To ensure, one more time I removed again all /usr/obj/*

Certified that diff is correct. What was little different now, was the
panic ( RUN-RUN ) so why I am posting again, may it helps in something.

I will perform AMD64-Current tests today and will back with results

Thank you so much for your attention and efforts.

Bests,



# *cd /sys/arch/$(machine)/compile/GENERIC*
# *make obj*
# *make config*
# *make && make install*
# *reboot*

# sh /etc/netstart urtwn0

panic: invalid transition RUN -> RUN
Stopped at  panic+0x158:TIDPIDUID PRFLAGS
PFLAGS  C
PU  COMMAND
*412518  74742  0 0x14000  0x2000  usbtask
db_enter() at panic+0x154
panic() at rtwn_newstate+0x6c4
rtwn_newstate() at urtwn_task+0x5c
urtwn_task() at usb_task_thread+0xe8
usb_task_thread() at proc_trampoline+0xc
https://www.openbsd.org/ddb.html describes the minimum info required in bug
reports.  Insufficient info makes it difficult to find and fix bugs.
ddb> show panic
invalid transition RUN -> RUN

Re: [RPI3] TP-Link TL-WN821N V4 kernel panic

2017-08-04 Thread R0me0 ***

 sh /etc/netstart urtwn0

panic: invalid transition AUTH -> RUN
Stopped at  panic+0x158:TIDPIDUID PRFLAGS
PFLAGS  C
PU  COMMAND
*352180  67191  0 0x14000  0x2000  usbtask
db_enter() at panic+0x154
panic() at rtwn_newstate+0x6c4
rtwn_newstate() at urtwn_task+0x5c
urtwn_task() at usb_task_thread+0xe8
usb_task_thread() at proc_trampoline+0xc
https://www.openbsd.org/ddb.html describes the minimum info required in bug
reports.  Insufficient info makes it difficult to find and fix bugs.
ddb> show panic
invalid transition AUTH -> RUN
ddb> trace
db_enter() at panic+0x154
panic() at rtwn_newstate+0x6c4
rtwn_newstate() at urtwn_task+0x5c
urtwn_task() at usb_task_thread+0xe8
usb_task_thread() at proc_trampoline+0xc

# diff -u /root/ieee80211_proto-orig.c ieee80211_proto.c
--- /root/ieee80211_proto-orig.cFri Aug  4 10:45:32 2017
+++ ieee80211_proto.c   Fri Aug  4 10:05:29 2017
@@ -1022,11 +1022,11 @@
   switch (ostate) {
   case IEEE80211_S_INIT:
   case IEEE80211_S_SCAN:
-   case IEEE80211_S_ASSOC:
   panic("invalid transition %s -> %s",
   ieee80211_state_name[ostate],
   ieee80211_state_name[nstate]);
   break;
+   case IEEE80211_S_ASSOC:
   case IEEE80211_S_AUTH:
   IEEE80211_SEND_MGMT(ic, ni,
   IEEE80211_FC0_SUBTYPE_ASSOC_REQ, 0);








2017-08-03 16:13 GMT-03:00 Stefan Sperling :

> On Thu, Aug 03, 2017 at 03:20:13PM -0300, R0me0 *** wrote:
> > Yes, all on raspberry
> >
> > Stefan, I can setup  VM and test amd64. Current or 6.1-stable?
> >
> > To ensure I didn't a mess follow the diff:
> >
> > diff -u ieee80211_proto-orig.c /usr/src/sys/net80211/ieee80211_proto.c
>
> This diff is incorrect, it deletes way too many lines.
>
> > --- ieee80211_proto-orig.c  Thu Aug  3 13:38:26 2017
> > +++ /usr/src/sys/net80211/ieee80211_proto.c Thu Aug  3 13:10:45 2017
> > @@ -1023,10 +1023,6 @@
> >case IEEE80211_S_INIT:
> >case IEEE80211_S_SCAN:
> >case IEEE80211_S_ASSOC:
> > -   panic("invalid transition %s -> %s",
> > -   ieee80211_state_name[ostate],
> > -   ieee80211_state_name[nstate]);
> > -   break;
> >case IEEE80211_S_AUTH:
> >IEEE80211_SEND_MGMT(ic, ni,
> >IEEE80211_FC0_SUBTYPE_ASSOC_REQ, 0);
>
> Here is my diff again (move just the "IEEE80211_S_ASSOC" line down).
>
> Index: ieee80211_proto.c
> ===
> RCS file: /cvs/src/sys/net80211/ieee80211_proto.c,v
> retrieving revision 1.78
> diff -u -p -r1.78 ieee80211_proto.c
> --- ieee80211_proto.c   22 Jul 2017 16:54:46 -  1.78
> +++ ieee80211_proto.c   28 Jul 2017 09:05:55 -
> @@ -1022,11 +1022,11 @@ justcleanup:
> switch (ostate) {
> case IEEE80211_S_INIT:
> case IEEE80211_S_SCAN:
> -   case IEEE80211_S_ASSOC:
> panic("invalid transition %s -> %s",
> ieee80211_state_name[ostate],
> ieee80211_state_name[nstate]);
> break;
> +   case IEEE80211_S_ASSOC:
> case IEEE80211_S_AUTH:
> IEEE80211_SEND_MGMT(ic, ni,
> IEEE80211_FC0_SUBTYPE_ASSOC_REQ, 0);
>
>

Re: [RPI3] TP-Link TL-WN821N V4 kernel panic

2017-08-03 Thread R0me0 ***

Yes, all on raspberry

Stefan, I can setup  VM and test amd64. Current or 6.1-stable?

To ensure I didn't a mess follow the diff:

diff -u ieee80211_proto-orig.c /usr/src/sys/net80211/ieee80211_proto.c

--- ieee80211_proto-orig.c  Thu Aug  3 13:38:26 2017
+++ /usr/src/sys/net80211/ieee80211_proto.c Thu Aug  3 13:10:45 2017
@@ -1023,10 +1023,6 @@
   case IEEE80211_S_INIT:
   case IEEE80211_S_SCAN:
   case IEEE80211_S_ASSOC:
-   panic("invalid transition %s -> %s",
-   ieee80211_state_name[ostate],
-   ieee80211_state_name[nstate]);
-   break;
   case IEEE80211_S_AUTH:
   IEEE80211_SEND_MGMT(ic, ni,
   IEEE80211_FC0_SUBTYPE_ASSOC_REQ, 0);



Thank you





2017-08-03 15:04 GMT-03:00 Stefan Sperling :

> On Thu, Aug 03, 2017 at 01:39:27PM -0300, R0me0 *** wrote:
> > Hi, applied the patch by hands as suggested:
> >
> >
> > urtwn0: no link . got link
>
> Since the link is up It is already in RUN state at this point.
>
> > DHCPDISCOVER on urtwn0 - interval 1
> > DHCPDISCOVER on urtwn0 - interval 1
> > panic: invalid transition AUTH -> RUN
>
> So this makes absolutely no sense at all without more context.
>
> Is this still on the raspberry pi?
> Can you reproduce this same bug on an amd64 machine?
>
> > Stopped at  panic+0x158:TIDPIDUID PRFLAGS
> > PFLAGS  C
> > PU  COMMAND
> > *489298   5181  0 0x14000  0x2000  usbtask
> > db_enter() at panic+0x154
> > panic() at rtwn_newstate+0x6c4
> > rtwn_newstate() at urtwn_task+0x5c
> > urtwn_task() at usb_task_thread+0xe8
> > usb_task_thread() at proc_trampoline+0xc
> > https://www.openbsd.org/ddb.html describes the minimum info required in
> bug
> > reports.  Insufficient info makes it difficult to find and fix bugs.
> > ddb> show panic
> > invalid transition AUTH -> RUN
> > ddb> trace
> > db_enter() at panic+0x154
> > panic() at rtwn_newstate+0x6c4
> > rtwn_newstate() at urtwn_task+0x5c
> > urtwn_task() at usb_task_thread+0xe8
> > usb_task_thread() at proc_trampoline+0xc
> >
> >
> >
> > @Stefan thanks!
> >
> > :-)
> >
> >
> > 2017-08-01 18:39 GMT-03:00 Stefan Sperling :
> >
> > > On Tue, Aug 01, 2017 at 06:54:00AM -0300, R0me0 *** wrote:
> > > > Hello, Stefan! How you doing!? Hope very well!;
> > > >
> > > > I have installed the latest snapshot and the issue persists. Also, I
> > > took a
> > > > look at diff you provided ( I am not a programmer sorry any mistake
> ) and
> > > > seems is already committed.
> > >
> > > AFAIK this diff is not committed yet.
> > >
>

Re: [RPI3] TP-Link TL-WN821N V4 kernel panic

2017-08-03 Thread R0me0 ***

Hi, applied the patch by hands as suggested:

urtwn0: no link . got link

DHCPDISCOVER on urtwn0 - interval 1
DHCPDISCOVER on urtwn0 - interval 1
panic: invalid transition AUTH -> RUN
Stopped at  panic+0x158:TIDPIDUID PRFLAGS
PFLAGS  C
PU  COMMAND
*489298   5181  0 0x14000  0x2000  usbtask
db_enter() at panic+0x154
panic() at rtwn_newstate+0x6c4
rtwn_newstate() at urtwn_task+0x5c
urtwn_task() at usb_task_thread+0xe8
usb_task_thread() at proc_trampoline+0xc
https://www.openbsd.org/ddb.html describes the minimum info required in bug
reports.  Insufficient info makes it difficult to find and fix bugs.
ddb> show panic
invalid transition AUTH -> RUN
ddb> trace
db_enter() at panic+0x154
panic() at rtwn_newstate+0x6c4
rtwn_newstate() at urtwn_task+0x5c
urtwn_task() at usb_task_thread+0xe8
usb_task_thread() at proc_trampoline+0xc

@Stefan thanks!

:-)

2017-08-01 18:39 GMT-03:00 Stefan Sperling :

> On Tue, Aug 01, 2017 at 06:54:00AM -0300, R0me0 *** wrote:
> > Hello, Stefan! How you doing!? Hope very well!;
> >
> > I have installed the latest snapshot and the issue persists. Also, I
> took a
> > look at diff you provided ( I am not a programmer sorry any mistake ) and
> > seems is already committed.
>
> AFAIK this diff is not committed yet.
>

Re: [RPI3] Latest minirootfs

2017-08-02 Thread R0me0 ***

Yeap, fixed



2017-08-02 9:03 GMT-03:00 Jonathan Gray :

> On Tue, Aug 01, 2017 at 06:40:26AM -0300, R0me0 *** wrote:
> > Hello, Jonathan!
> >
> > Copying the provided u-boot.bin worked :)
> >
> > Yes, the issue just affects USB DRIVE.
> >
> > Never touched config.txt.
> >
> > The procedures were: dd if=minirootfs61.fs of=(USB drive or sd-card )
> >  bs=1M
> >
> > If I use sd-card, then I make sure that USB drive is not bootable and is
> > empty and use both.
> >
> > If USB Drive, just itself.
> >
> > Thank you so much!
> >
>
> The arm64 snapshot that went up today uses U-Boot 2017.09-rc1 which also
> includes the recent U-Boot efi_loader changes.
>

Re: [RPI3] TP-Link TL-WN821N V4 kernel panic

2017-08-01 Thread R0me0 ***

Hello, Stefan! How you doing!? Hope very well!;

I have installed the latest snapshot and the issue persists. Also, I took a
look at diff you provided ( I am not a programmer sorry any mistake ) and
seems is already committed.
I will try and back asap with feedbacks.

Thank you so much!



2017-07-28 6:11 GMT-03:00 Stefan Sperling :

> On Thu, Jul 27, 2017 at 08:45:32PM -0300, R0me0 *** wrote:
> > invalid transition ASSOC -> ASSOC
>
> This diff should fix this panic and allow normal operation.
> Can you please test it?
>
> This kind of transition can be triggerred if management frames arrive at
> an inconvenient point in time, so this transition is not actually invalid
> and the net80211 stack should handle it.
>
> Index: ieee80211_proto.c
> ===
> RCS file: /cvs/src/sys/net80211/ieee80211_proto.c,v
> retrieving revision 1.78
> diff -u -p -r1.78 ieee80211_proto.c
> --- ieee80211_proto.c   22 Jul 2017 16:54:46 -  1.78
> +++ ieee80211_proto.c   28 Jul 2017 09:05:55 -
> @@ -1022,11 +1022,11 @@ justcleanup:
> switch (ostate) {
> case IEEE80211_S_INIT:
> case IEEE80211_S_SCAN:
> -   case IEEE80211_S_ASSOC:
> panic("invalid transition %s -> %s",
> ieee80211_state_name[ostate],
> ieee80211_state_name[nstate]);
> break;
> +   case IEEE80211_S_ASSOC:
> case IEEE80211_S_AUTH:
> IEEE80211_SEND_MGMT(ic, ni,
> IEEE80211_FC0_SUBTYPE_ASSOC_REQ, 0);
>

Re: [RPI3] Latest minirootfs

2017-08-01 Thread R0me0 ***

Hello, Jonathan!

Copying the provided u-boot.bin worked :)

Yes, the issue just affects USB DRIVE.

Never touched config.txt.

The procedures were: dd if=minirootfs61.fs of=(USB drive or sd-card )
 bs=1M

If I use sd-card, then I make sure that USB drive is not bootable and is
empty and use both.

If USB Drive, just itself.

Thank you so much!





2017-07-31 21:17 GMT-03:00 Jonathan Gray :

> On Mon, Jul 31, 2017 at 11:15:52PM +0000, R0me0 *** wrote:
> > I wrote minirootfs as usual directly to usb flash drive
> >
> > minirootfs61.fs31-Jul-2017 03:11  22020096
> >
> >
> >
> > U-Boot> boot
> > Card did not respond to voltage select!
> > mmc_init: -95, time 24
> >
> > USB device 0:
> >Device 0: Vendor: Kingston Rev: 1.00 Prod: DataTraveler 2.0
> >Type: Removable Hard Disk
> >Capacity: 14762.4 MB = 14.4 GB (30233588 x 512)
> > ... is now current device
> > Scanning usb 0:1...
> > Found EFI removable media binary efi/boot/bootaa64.efi
> > reading efi/boot/bootaa64.efi
> > 75732 bytes read in 75 ms (985.4 KiB/s)
> > ## Starting EFI application at 0100 ...
> > Card did not respond to voltage select!
> > mmc_init: -95, time 24
> > Found 0 disks
> > BS->LocateHandle() returns 0
> > "Synchronous Abort" handler, esr 0x0200
> > ELR: 39b3ecfc
> > LR:  39b421ec
> > x0 :  x1 : 3afec000
> > x2 : 0002 x3 : 003f
> > x4 : 0010 x5 : 
> > x6 : 3af96558 x7 : 39b3efa8
> > x8 : 39b4c8ac x9 : 39b3e39c
> > x10: 3ab4fa70 x11: 3ab4faf0
> > x12: 3ab4fbc0 x13: 39b4d850
> > x14: 3ab4fd6c x15: 
> > x16: 4110 x17: ad7bd9a555f85ec4
> > x18:  x19: 39b4db12
> > x20: 39b4c920 x21: 0001
> > x22: 39a3d030 x23: 39b4cb00
> > x24: 39b4c920 x25: 0200
> > x26: 3afa76b0 x27: 39b3e148
> > x28:  x29: 3ab4fcd0
> >
> > Resetting CPU ...
> >
> > resetting ...
>
> That is with only a USB drive?  You've previously blown the
> fuse by setting the config.txt value and no SD card is present?
>
> Try with a newer U-Boot
> http://jsg.id.au/openbsd/u-boot.bin
> SHA256 (u-boot.bin) = 342af5b0331c502a0b1c64a96b2b7f
> c915b516567cc3bd293a5078ea493a6e49
>
> Mount the msdos fs /dev/sdNi and copy u-boot.bin over the existing one.
>
> The U-Boot build is based on the latest development version and
> in particular includes:
>
> commit 70bfcdc6bb6f969babd69efc49e1dc7a1faeca54
> Author: xypron.g...@gmx.de 
> Date:   Tue Jun 20 19:10:27 2017 +
>
> efi_loader: disk: iterate only over valid block devices
>
> The efi_loader currently stops iterating over the available
> block devices stopping at the first device that fails.
> This may imply that no block device is found.
>
> With the patch efi_loader only iterates over valid devices.
> ...
>

Re: [RPI3] Latest minirootfs

2017-07-31 Thread R0me0 ***

writing minirootfs to SD card boot and installs as usual but not boot from
usb flash drive and returns the same errors as previously e-mail

( enter in  loop )



2017-07-31 20:15 GMT-03:00 R0me0 *** :

> I wrote minirootfs as usual directly to usb flash drive
>
> minirootfs61.fs31-Jul-2017 03:11  22020096
>
>
>
> U-Boot> boot
> Card did not respond to voltage select!
> mmc_init: -95, time 24
>
> USB device 0:
>Device 0: Vendor: Kingston Rev: 1.00 Prod: DataTraveler 2.0
>Type: Removable Hard Disk
>Capacity: 14762.4 MB = 14.4 GB (30233588 x 512)
> ... is now current device
> Scanning usb 0:1...
> Found EFI removable media binary efi/boot/bootaa64.efi
> reading efi/boot/bootaa64.efi
> 75732 bytes read in 75 ms (985.4 KiB/s)
> ## Starting EFI application at 0100 ...
> Card did not respond to voltage select!
> mmc_init: -95, time 24
> Found 0 disks
> BS->LocateHandle() returns 0
> "Synchronous Abort" handler, esr 0x0200
> ELR: 39b3ecfc
> LR:  39b421ec
> x0 :  x1 : 3afec000
> x2 : 0002 x3 : 003f
> x4 : 0010 x5 : 
> x6 : 3af96558 x7 : 39b3efa8
> x8 : 39b4c8ac x9 : 39b3e39c
> x10: 3ab4fa70 x11: 3ab4faf0
> x12: 3ab4fbc0 x13: 39b4d850
> x14: 3ab4fd6c x15: 
> x16: 4110 x17: ad7bd9a555f85ec4
> x18:  x19: 39b4db12
> x20: 39b4c920 x21: 0001
> x22: 39a3d030 x23: 39b4cb00
> x24: 39b4c920 x25: 0200
> x26: 3afa76b0 x27: 39b3e148
> x28:  x29: 3ab4fcd0
>
> Resetting CPU ...
>
> resetting ...
>
>
>
>
>

[RPI3] Latest minirootfs

2017-07-31 Thread R0me0 ***

I wrote minirootfs as usual directly to usb flash drive

minirootfs61.fs31-Jul-2017 03:11  22020096



U-Boot> boot
Card did not respond to voltage select!
mmc_init: -95, time 24

USB device 0:
   Device 0: Vendor: Kingston Rev: 1.00 Prod: DataTraveler 2.0
   Type: Removable Hard Disk
   Capacity: 14762.4 MB = 14.4 GB (30233588 x 512)
... is now current device
Scanning usb 0:1...
Found EFI removable media binary efi/boot/bootaa64.efi
reading efi/boot/bootaa64.efi
75732 bytes read in 75 ms (985.4 KiB/s)
## Starting EFI application at 0100 ...
Card did not respond to voltage select!
mmc_init: -95, time 24
Found 0 disks
BS->LocateHandle() returns 0
"Synchronous Abort" handler, esr 0x0200
ELR: 39b3ecfc
LR:  39b421ec
x0 :  x1 : 3afec000
x2 : 0002 x3 : 003f
x4 : 0010 x5 : 
x6 : 3af96558 x7 : 39b3efa8
x8 : 39b4c8ac x9 : 39b3e39c
x10: 3ab4fa70 x11: 3ab4faf0
x12: 3ab4fbc0 x13: 39b4d850
x14: 3ab4fd6c x15: 
x16: 4110 x17: ad7bd9a555f85ec4
x18:  x19: 39b4db12
x20: 39b4c920 x21: 0001
x22: 39a3d030 x23: 39b4cb00
x24: 39b4c920 x25: 0200
x26: 3afa76b0 x27: 39b3e148
x28:  x29: 3ab4fcd0

Resetting CPU ...

resetting ...

Re: [RPI3] TP-Link TL-WN821N V4 kernel panic

2017-07-27 Thread R0me0 ***

 j...@arm64.jsg.id.au:/usr/src/sys/arch/arm64/compile/GENERIC
real mem  = 961077248 (916MB)
avail mem = 905650176 (863MB)
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
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:  SCSI2
0/direct removable serial.09511665FDB1A9792441
sd0: 14762MB, 512 bytes/sector, 30233588 sectors
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 (5d4a11b53da05352.a) swap on sd0b dump on sd0b
WARNING: / was not properly unmounted
WARNING: CHECK AND RESET THE DATE!

2017-07-27 17:41 GMT-03:00 Stuart Henderson :

> On 2017/07/27 17:11, R0me0 *** wrote:
> > Latest snapshot 07-26-17
> >
> > The bug happens during wpa authentication:
> >
> >
> > Stopped at  panic+0x158:TIDPIDUID PRFLAGS
> > PFLAGS  C
> > PU  COMMAND
> > *137987  33873  0 0x14000  0x2000  usbtask
> > db_enter() at panic+0x154
> > panic() at rtwn_newstate+0x6c4
> > rtwn_newstate() at urtwn_task+0x5c
> > urtwn_task() at usb_task_thread+0xe8
> > usb_task_thread() at proc_trampoline+0xc
> > https://www.openbsd.org/ddb.html describes the minimum info required in
> bug
> > reports.  Insufficient info makes it difficult to find and fix bugs.
> > ddb> trace
> > db_enter() at panic+0x154
> > panic() at rtwn_newstate+0x6c4
> > rtwn_newstate() at urtwn_task+0x5c
> > urtwn_task() at usb_task_thread+0xe8
> > usb_task_thread() at proc_trampoline+0xc
>
> We need the panic message itself. If it's still in ddb,
>
> show panic
>
>

[RPI3] TP-Link TL-WN821N V4 kernel panic

2017-07-27 Thread R0me0 ***

Latest snapshot 07-26-17

The bug happens during wpa authentication:


Stopped at  panic+0x158:TIDPIDUID PRFLAGS
PFLAGS  C
PU  COMMAND
*137987  33873  0 0x14000  0x2000  usbtask
db_enter() at panic+0x154
panic() at rtwn_newstate+0x6c4
rtwn_newstate() at urtwn_task+0x5c
urtwn_task() at usb_task_thread+0xe8
usb_task_thread() at proc_trampoline+0xc
https://www.openbsd.org/ddb.html describes the minimum info required in bug
reports.  Insufficient info makes it difficult to find and fix bugs.
ddb> trace
db_enter() at panic+0x154
panic() at rtwn_newstate+0x6c4
rtwn_newstate() at urtwn_task+0x5c
urtwn_task() at usb_task_thread+0xe8
usb_task_thread() at proc_trampoline+0xc

Re: ARM64 Panic

2017-06-26 Thread R0me0 ***

Hello, Stuart! :) Thank you for the reply, I will try a fresh install
:)

[] 's guys

2017-06-26 20:04 GMT-03:00 Stuart Henderson :

> On 2017/06/26 09:30, R0me0 *** wrote:
> > Hello guys,
> > After Installed a snapshot from one week ago.
>
> A problem with the dwctwo(4) driver which could result in this
> was fixed on 2017/06/20. I'm unsure whether this made it into a
> snapshot yet, but if you're not already running "OpenBSD
> 6.1-current (GENERIC) #0: Wed Jun 21 17:47:53 AEST 2017" you
> should update to at least that version, if it still occurs then
> you could build a new kernel or wait for a newer snap to be
> built.
>
>

ARM64 Panic

2017-06-26 Thread R0me0 ***

Hello guys,
After Installed a snapshot from one week ago.
I just kept pi3 on "login" and day by day I went to console and tried
login/logout

Randomly it crashes and seems it is the same error I was facing before 6.1
release
I already tried to install on different usb's flash drives and is the same
error;


Any directions are really appreciated.
Thank you

Sorry the lack of dmesg

ddb> trace
db_enter() at panic+0x154
panic() at pool_get+0x54
pool_get() at dwc2_hcd_urb_enqueue+0x94
dwc2_hcd_urb_enqueue() at dwc2_device_start+0x3c4
dwc2_device_start() at usb_transfer_complete+0x2ec
usb_transfer_complete() at dwc2_softintr+0x74
dwc2_softintr() at softintr_dispatch+0xa0
softintr_dispatch() at arm_do_pending_intr+0x9c
arm_do_pending_intr() at bcm_intc_irq_handler+0xa8
bcm_intc_irq_handler() at handle_el1h_irq+0x6c
handle_el1h_irq() at sched_idle+0x198
sched_idle() at proc_trampoline+0xc

ddb> continue
syncing disks... panic: mtx 0xff800435cab8: locking against myself
Stopped at  panic+0x158:db_enter() at panic+0x154
panic() at dwc2_device_start+0x34c
dwc2_device_start() at usbd_transfer+0x140
usbd_transfer() at umass_setup_transfer+0x90
umass_setup_transfer() at umass_bbb_transfer+0x1ac
umass_bbb_transfer() at umass_scsi_cmd+0xd4
umass_scsi_cmd() at sdstart+0x2a0

Re: IPv6 not working before pinging the gateway

2017-06-26 Thread R0me0 ***

Did you open a trouble ticket on Hetzner?




2017-06-26 8:34 GMT-03:00 Martin Pieuchot :

> On 26/06/17(Mon) 12:39, Marc Peters wrote:
> > Am 06/26/17 um 10:58 schrieb Martin Pieuchot:
> > > [...]
> > > Could you set net.inet6.icmp6.nd6_debug to 1 and redo this?
> > >
> > > Do you see anything in the log?
> >
> > Rebooting the box with the sysctl active show following
> /var/log/messages:
> >
> > Jun 26 12:25:35 arafel /bsd: nd6_na_input: ND packet from non-neighbor
>
> Indeed.
>
> Your machine is asking with the following address:
>
> 2a01:4f8:212:216c::1:443 > ff02::1:ff00:1: icmp6: neighbor sol: who has
> fe80::1
>
> Your provider is answering with an address that doesn't match your
> subnet:
>
> 2a01:4f8::a:21:b > 2a01:4f8:212:216c::1:443: icmp6: neighbor adv: tgt is
> fe80::1 [class 0xc0]
>
> It'd be nice if somebody could tell us what the RFCs say about this
> case.  Florian do you have an idea?  Should we fix something or should
> Marc tell his provider to fix his setup?
>
>

Re: [ARM64] RPI3 Panic

2017-04-05 Thread R0me0 ***

Hello, guys, just testing and making use of ARM64.

* Using a pendrive and booting from it:

I have downloaded ports snapshot, and ran cvs up attached to tmux session
over ssh , after a while, I got: ( please, ignore if you guys already aware
)



ddb> trace
Debugger() at panic+0x154
panic() at VOP_LOOKUP+0x34
VOP_LOOKUP() at vfs_lookup+0x224
vfs_lookup() at namei+0x2b8
namei() at vn_open+0x78
vn_open() at doopenat+0x120
doopenat() at svc_handler+0x1bc
svc_handler() at handle_el0_sync+0x68
handle_el0_sync() at 0x4ab2de7c4
--- trap ---

dmesg:

OpenBSD 6.1 (GENERIC) #0: Sun Apr  2 17:05:03 AEST 2017
   j...@arm64.jsg.id.au:/usr/src/sys/arch/arm64/compile/GENERIC
real mem  = 989855744 (944MB)
avail mem = 931606528 (888MB)
mainbus0 at root: Raspberry Pi 3 Model B Rev 1.2
simplefb0 at mainbus0: 640x480
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
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 2 configuration 1 interface 0 "Kingston DataTraveler
2.0" rev 2.00/2.00 addr 4
umass0: using SCSI over Bulk-Only
scsibus0 at umass0: 2 targets, initiator 0
sd0 at scsibus0 targ 1 lun 0:  SCSI2
0/direct removable serial.09511665DDC01C1B
sd0: 14916MB, 512 bytes/sector, 30548032 sectors
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 (fc7dd3ed1a299b8b.a) swap on sd0b dump on sd0b
WARNING: CHECK AND RESET THE DATE!

[ARM64] RPI3 Panic

2017-03-24 Thread R0me0 ***

Hi guys,

I know ARM64 is under heavy development, and I have been using the last days

Just trying to contribute.

# panic: pool_do_get: dwc2qtd free list modified: page 0xff800c53e000;
item addr 0xff800c53e0e0; offset 0x0=0xdead4100
Stopped at  panic+0x158:TIDPIDUID PRFLAGS
PFLAGS  C
PU  COMMAND
Debugger() at panic+0x154
panic() at pool_get+0x54
pool_get() at dwc2_hcd_urb_enqueue+0x94
dwc2_hcd_urb_enqueue() at dwc2_device_start+0x3c8
dwc2_device_start() at usb_transfer_complete+0x2e4
usb_transfer_complete() at dwc2_softintr+0x74
dwc2_softintr() at softintr_dispatch+0xa0
https://www.openbsd.org/ddb.html describes the minimum info required in bug
reports.  Insufficient info makes it difficult to find and fix bugs.
ddb> trace

Debugger() at panic+0x154
panic() at pool_get+0x54
pool_get() at dwc2_hcd_urb_enqueue+0x94
dwc2_hcd_urb_enqueue() at dwc2_device_start+0x3c8
dwc2_device_start() at usb_transfer_complete+0x2e4
usb_transfer_complete() at dwc2_softintr+0x74
dwc2_softintr() at softintr_dispatch+0xa0
softintr_dispatch() at arm_do_pending_intr+0x9c
arm_do_pending_intr() at bcm_intc_irq_handler+0xa8
bcm_intc_irq_handler() at handle_el1h_irq+0x6c
handle_el1h_irq() at sched_idle+0x198
sched_idle() at proc_trampoline+0xc



dmesg:


OpenBSD 6.1-beta (GENERIC) #0: Thu Mar 23 23:39:33 AEDT 2017
   j...@arm64.jsg.id.au:/usr/src/sys/arch/arm64/compile/GENERIC
real mem  = 989855744 (944MB)
avail mem = 931614720 (888MB)
mainbus0 at root: Raspberry Pi 3 Model B Rev 1.2
simplefb0 at mainbus0: 640x480
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
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 2 configuration 1 interface 0 "Kingston DataTraveler
2.0" rev 2.00/2.00 addr 4
umass0: using SCSI over Bulk-Only
scsibus0 at umass0: 2 targets, initiator 0
sd0 at scsibus0 targ 1 lun 0:  SCSI2
0/direct removable serial.09511665DDC01C1B
sd0: 14916MB, 512 bytes/sector, 30548032 sectors
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 (fc7dd3ed1a299b8b.a) swap on sd0b dump on sd0b
WARNING: / was not properly unmounted
WARNING: CHECK AND RESET THE DATE!

Re: Possible Bug in PF with round-robin sticky-address

2012-11-01 Thread R0me0 ***

Hello OpenBSD Team,

I downloaded the lastest version of OpenBSD 5.2 and the possible bug
persist :)
Please if don't is a bug, let me know

Cheers,


2012/8/30 "Marcus Mülbüsch, AS-Infodienste GmbH (Systemadministration)" <
muelbue...@as-infodienste.de>

> Am 29.08.2012 20:10, schrieb R0me0 ***:
>
>  Hello Marcos,
>> I tried this in a phisical hardware (dell )  and the problem is the same.
>>
>> Regards,
>>
>
> Thank you - so I will use an older OpenBSD version in our VMWare.
>
>
> Marcus
>
> --
> fon: 0800 3366 111 - 63
> fax: 0800 3366 111 - 93
>
> __**_
>
> AS-Infodienste GmbH
> Hardenbergstr. 18 b
> 45472 Mülheim
>
> fax: 0800 3366 111 - 99
> web: http://www.as-infodienste.de
>
> Kontakt zum Telefonsupport für
> Servicerufnummern: 0800 3366 111 - 1
> Telefonsekretariat:0800 3366 111 - 2
> SMS-Dienstleistungen:  0800 3366 111 - 3
> Telefonkonferenzen:0800 3366 111 - 7
>
> International Telefon: +49 208 941398 - 49
> International Telefax: +49 208 941398 - 949
> __**_
>
> Unternehmensangaben:
>
> Die AS-Infodienste GmbH ist im
> Handelsregister des AG Duisburg
> unter HRB 16061 registriert.
>
> Geschäftsführer:
> Andreas Schlacht
> Alexander Stellmach
>
> USt.-ID: DE 813295188
> St.-Nr.: 120 / 5742 / 0589

Possible Bug in PF with round-robin sticky-address

2012-07-25 Thread R0me0 ***

Hello OpenBSD Team :)

I sended this possible bug previosly, but I do this incorrectly. My
apologies to Theo and Henning Brauer

So the bug occurs when I put the follow rule in pf.conf

pass in log on bnx1 inet from $int_net route-to {($ext_if $ext_gw),
($ext_if2 $ext_gw2)} round-robin sticky-address

 If CARP is also configured and in another node the rule exists, then the
node will crash too.

First, I do the tests in Dell Power Edge, and now in VMWARE,

I would want to congrat the work of all OpenBSD Team

Regards,
Guilherme Hakme
Minima Network Management - Brazil


Follow the dmesg.boot

---

tual PCIE-PCIE" rev 0x01
pci19 at ppb18 bus 19
ppb19 at pci0 dev 23 function 1 "VMware Virtual PCIE-PCIE" rev 0x01
pci20 at ppb19 bus 20
ppb20 at pci0 dev 23 function 2 "VMware Virtual PCIE-PCIE" rev 0x01
pci21 at ppb20 bus 21
ppb21 at pci0 dev 23 function 3 "VMware Virtual PCIE-PCIE" rev 0x01
pci22 at ppb21 bus 22
ppb22 at pci0 dev 23 function 4 "VMware Virtual PCIE-PCIE" rev 0x01
pci23 at ppb22 bus 23
ppb23 at pci0 dev 23 function 5 "VMware Virtual PCIE-PCIE" rev 0x01
pci24 at ppb23 bus 24
ppb24 at pci0 dev 23 function 6 "VMware Virtual PCIE-PCIE" rev 0x01
pci25 at ppb24 bus 25
ppb25 at pci0 dev 23 function 7 "VMware Virtual PCIE-PCIE" rev 0x01
pci26 at ppb25 bus 26
ppb26 at pci0 dev 24 function 0 "VMware Virtual PCIE-PCIE" rev 0x01
pci27 at ppb26 bus 27
ppb27 at pci0 dev 24 function 1 "VMware Virtual PCIE-PCIE" rev 0x01
pci28 at ppb27 bus 28
ppb28 at pci0 dev 24 function 2 "VMware Virtual PCIE-PCIE" rev 0x01
pci29 at ppb28 bus 29
ppb29 at pci0 dev 24 function 3 "VMware Virtual PCIE-PCIE" rev 0x01
pci30 at ppb29 bus 30
ppb30 at pci0 dev 24 function 4 "VMware Virtual PCIE-PCIE" rev 0x01
pci31 at ppb30 bus 31
ppb31 at pci0 dev 24 function 5 "VMware Virtual PCIE-PCIE" rev 0x01
pci32 at ppb31 bus 32
ppb32 at pci0 dev 24 function 6 "VMware Virtual PCIE-PCIE" rev 0x01
pci33 at ppb32 bus 33
ppb33 at pci0 dev 24 function 7 "VMware Virtual PCIE-PCIE" rev 0x01
pci34 at ppb33 bus 34
isa0 at piixpcib0
isadma0 at isa0
com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
com1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo
pckbc0 at isa0 port 0x60/5
pckbd0 at pckbc0 (kbd slot)
pckbc0: using irq 1 for kbd slot
wskbd0 at pckbd0: console keyboard, using wsdisplay0
pms0 at pckbc0 (aux slot)
pckbc0: using irq 12 for aux slot
wsmouse0 at pms0 mux 0
pcppi0 at isa0 port 0x61
spkr0 at pcppi0
lpt0 at isa0 port 0x378/4 irq 7
npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16
fdc0 at isa0 port 0x3f0/6 irq 6 drq 2
mtrr: Pentium Pro MTRR support
uhidev0 at uhub1 port 1 configuration 1 interface 0 "VMware VMware Virtual
USB Mouse" rev 1.10/1.02 addr 2
uhidev0: iclass 3/0
ums0 at uhidev0: 16 buttons, Z dir
wsmouse1 at ums0 mux 0
uhidev1 at uhub1 port 1 configuration 1 interface 1 "VMware VMware Virtual
USB Mouse" rev 1.10/1.02 addr 2
uhidev1: iclass 3/0
ums1 at uhidev1: 16 buttons, Z dir
wsmouse2 at ums1 mux 0
uhub2 at uhub1 port 2 "vendor 0x0e0f VMware Virtual USB Hub" rev 1.10/1.00
addr 3
vscsi0 at root
scsibus2 at vscsi0: 256 targets
softraid0 at root
scsibus3 at softraid0: 256 targets
root on wd0a (ec9a0c7525eefe60.a) swap on wd0b dump on wd0b
WARNING: / was not properly unmounted
carp0: state transition: BACKUP -> MASTER
carp1: state transition: BACKUP -> MASTER
uvm_fault(0xd0a08980, 0xd53ea000, 0, 1) -> e
kernel: page fault trap, code=0
Stopped at  pf_test_rule+0xdbc: movl0xff70(%ebp),%eax
ddb{0}>PID   PPID   PGRPUID  S   FLAGS  WAIT  COMMAND

 18022  1  18022  0  30x80  ttyin getty
 29508  1  29508  0  30x80  ttyin getty
 18412  1  18412  0  30x80  ttyin getty
 18481  1  18481  0  30x80  ttyin getty
 25259  1  25259  0  30x80  ttyin ksh
 32237  1  32237  0  30x80  selectcron
 13237  1  13237 99  30x80  poll  sndiod
 28582  1  28582  0  30x80  selectinetd
 11511  1  11511  0  30x80  selectsendmail
 28235  1  28235  0  30x80  selectsshd
  4718  13953  13953 74  30x80  bpf   pflogd
 13953  1  13953  0  30x80  netio pflogd
 23939  23805  23805 73  20x80syslogd
 23805  1  23805  0  30x80  netio syslogd
15  0  0  0  30x100200  aiodoned  aiodoned
14  0  0  0  30x100200  syncerupdate
13  0  0  0  30x100200  cleaner   cleaner
12  0  0  0  30x100200  reaperreaper
11  0  0  0  30x100200  pgdaemon  pagedaemon
10  0  0  0  30x100200  bored crypto
 9  0  0  0  30x100200  pftm  pfpurge
 8  0  0  0  30x100200  usbtskusbtask

40 matches

Mail list logo