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
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
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
Hello guys,
Clarified! Thank you so much all.
2018-02-07 18:17 GMT-02:00 Raf Czlonka <rczlo...@gmail.com>:
> R0me0,
>
> Syspatch has been around *since* 6.1 - yes.
>
> Like Bryan already mentioned, binary patches are *only* available
> for the most recent releas
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 <bry...@gmail.com>:
> On Sun, Feb 04, 2018 at 09:57:39AM -0200, R0me0 *** wrote:
> > Hello guys,
> >
> > I am try
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
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
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
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:
to reproduce.
That's it. I am sure!
2017-08-28 14:24 GMT-03:00 R0me0 *** <knight@gmail.com>:
> 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 mu
return;
}
2017-08-28 13:41 GMT-03:00 Stefan Sperling <s...@stsp.name>:
> 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 rela
id0 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 Stefan Sperling <s...@stsp.name>:
> On Sun, A
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, t
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 <s...@stsp.name>:
> On Fri, Aug 25, 2017 at 05:35:10PM -0300, R0me0 *** wrote:
> > Hello all,
> > Stefa
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 <s...@s
So, I did : ifconfig urtwn0 debug
# urtwn0: device timeout
urtwn0: RUN -> INIT
2017-08-24 17:44 GMT-03:00 R0me0 *** <knight@gmail.com>:
> 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 ***
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 *** <knight@gmail.com>:
> + bugs at openbsd dot org
>
> Hello, Todd!
> I am using the snapshot from yesterday.
> If I do not start tor, so my connections keeps
R0me0 *** <knight@gmail.com>:
> 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 attent
I have noticed the following behavior:
urtwn0: device timeout
The system just hangs and hard reboot is needed.
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:
Fixed :)
Thanks
2017-08-22 6:04 GMT-03:00 Jonathan Gray <j...@jsg.id.au>:
> 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
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
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
_FC0_SUBTYPE_ASSOC_REQ, 0);
2017-08-03 16:13 GMT-03:00 Stefan Sperling <s...@stsp.name>:
> 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?
> >
>
n Sperling <s...@stsp.name>:
> 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.
>
&
c
@Stefan thanks!
:-)
2017-08-01 18:39 GMT-03:00 Stefan Sperling <s...@stsp.name>:
> 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
Yeap, fixed
2017-08-02 9:03 GMT-03:00 Jonathan Gray <j...@jsg.id.au>:
> 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
-28 6:11 GMT-03:00 Stefan Sperling <s...@stsp.name>:
> 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 kin
.
If USB Drive, just itself.
Thank you so much!
2017-07-31 21:17 GMT-03:00 Jonathan Gray <j...@jsg.id.au>:
> On Mon, Jul 31, 2017 at 11:15:52PM +0000, R0me0 *** wrote:
> > I wrote minirootfs as usual directly to usb flash drive
> >
> > minirootfs61.fs
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 *** <knight@gmail.com>:
> I wrote minirootfs as usual directly to usb fl
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
d4a11b53da05352.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 <s...@spacehopper.org>:
> On 2017/07/27 17:11, R0me0 *** wrote:
> > Latest snapshot 07-26-17
> >
> > The bug h
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
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 <s...@spacehopper.org>:
> On 2017/06/26 09:30, R0me0 *** wrote:
> > Hello guys,
> > After Installed a snapshot from one week ago.
>
>
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
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
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
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 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
39 matches
Mail list logo