Den mån 3 maj 2021 kl 08:36 skrev jeanfrancois :
> AMD released their 64 bit extensions with the FX series back in 2005(?),
> which Intel later adopted.
> Intel had their own 64 bit architecture with itanium, which could run 32
> bit i386 Software, but that was, iirc, emulation.
https://ark.intel
>Synopsis: Encountered bus error on tcpdumping a cycled interface
>Category: system
>Environment:
System : OpenBSD 6.9
Details : OpenBSD 6.9 (GENERIC.MP) #551: Sun Apr 18 03:06:59 MDT
2021
dera...@octeon.openbsd.org:/usr/src/sys/arch/oct
Can you reproduce this, and capture core files?
Since our tcpdump is a privsep program, getting a core is a bit harder.
mkdir /var/crash/tcpdump
echo kern.nosuidcoredump=3 >> /etc/sysctl.conf
reboot
You could recompile tcpdump with -g or -ggdb, to gain better symbols.
If you manage to create a
Yup I'll try. Give me bit of time to find results.
Best Regards,
-peter
On Mon, May 03, 2021 at 08:27:57AM -0600, Theo de Raadt wrote:
> Can you reproduce this, and capture core files?
>
> Since our tcpdump is a privsep program, getting a core is a bit harder.
>
> mkdir /var/crash/tcpdump
> ec
On Mon, May 03, 2021 at 08:27:57AM -0600, Theo de Raadt wrote:
> Can you reproduce this, and capture core files?
Yes after a reboot I could reproduce it, I didn't even have to cycle the
interfaces. I got a coredump like you descriped for me. See below:
> Since our tcpdump is a privsep program,
You didn't use a -g binary as I suggested, then gdb will show more.
Peter J. Philipp wrote:
> On Mon, May 03, 2021 at 08:27:57AM -0600, Theo de Raadt wrote:
> > Can you reproduce this, and capture core files?
>
> Yes after a reboot I could reproduce it, I didn't even have to cycle the
> interfa
On Mon, May 03, 2021 at 09:42:10AM -0600, Theo de Raadt wrote:
> You didn't use a -g binary as I suggested, then gdb will show more.
Apologies, I did compile with -g but since I cherry picked the source over
to the router (which is extremely low on space) it installed the binary in
the wrong spot
Hi Peter,
Here is a small diff. Two questions:
1. Does the machine powerdown if you do halt -p with this diff?
2. Does the diff fix the crashes?
Thanks,
Mark
Index: dev/acpi/acpi.c
===
RCS file: /cvs/src/sys/dev/acpi/acpi.c,v
r
Further info (screen shots) - today during a lengthy rsync it seemed the
screen saver kicked in but X crashed right after and then this sequence
happened:
https://www.bsdly.net/~peter/20210503_164555.jpg
https://www.bsdly.net/~peter/20210503_164607.jpg
https://www.bsdly.net/~peter/20210503_164616
>Synopsis: pkg_add fails
>Category:
>Environment:
System : OpenBSD 6.9
Details : OpenBSD 6.9 (GENERIC.MP) #473: Mon Apr 19 10:40:28 MDT
2021
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
Architecture: Ope
Also my /etc/installurl is:
desktop(/etc)$: cat /etc/installurl
https://cdn.openbsd.org/pub/OpenBSD
desktop(/etc)$:
- Original message -
From: Jon Fineman
To: bugs@openbsd.org
Cc: j...@fineman.me
Subject: pkg_add -u Base64.c: loadable library and perl binaries are mismatched
Date: Mon
On Mon, May 03, 2021 at 08:11:04PM -0400, Jon Fineman wrote:
> >Synopsis:pkg_add fails
> >Category:
> >Environment:
> System : OpenBSD 6.9
> Details : OpenBSD 6.9 (GENERIC.MP) #473: Mon Apr 19 10:40:28 MDT
> 2021
>
> dera...@amd64.openbsd.org:/u
- Original message -
From: Andrew Hewus Fresh
To: Jon Fineman
Cc: bugs@openbsd.org
Subject: Re: pkg_add -u Base64.c: loadable library and perl binaries are
mismatched
Date: Monday, May 03, 2021 8:20 PM
On Mon, May 03, 2021 at 08:11:04PM -0400, Jon Fineman wrote:
> >Synopsis:pkg_a
On Mon, May 03, 2021 at 08:27:11PM -0400, Jon Fineman wrote:
>
>
> - Original message -
> From: Andrew Hewus Fresh
> To: Jon Fineman
> Cc: bugs@openbsd.org
> Subject: Re: pkg_add -u Base64.c: loadable library and perl binaries are
> mismatched
> Date: Monday, May 03, 2021 8:20 PM
>
Any detailed instructions on how to remove the newer module? Both cpan and
cpanm also get the binary mismatch error, so I can't uninstall base64 via cpan.
Is there a list of files/directories I can remove? I tried moving Base64.so in
local but still got the error. So there seems to be a few more
On Mon, May 03, 2021 at 08:47:15PM -0400, Jon Fineman wrote:
> Any detailed instructions on how to remove the newer module? Both cpan and
> cpanm also get the binary mismatch error, so I can't uninstall base64 via
> cpan.
>
> Is there a list of files/directories I can remove? I tried moving Base
For cpan/cpanm I had gotten the same base64 error.
After moving those two directories and rebooting I was able to run pkg_add and
now cpanm. However cpan now gets the below error:
desktop(~)$: cpan
Encode.c: loadable library and perl binaries are mismatched (got handshake key
0xb60, needed 0
On Mon, May 03, 2021 at 09:51:59PM -0400, Jon Fineman wrote:
> For cpan/cpanm I had gotten the same base64 error.
>
> After moving those two directories and rebooting I was able to run pkg_add
> and now cpanm. However cpan now gets the below error:
> desktop(~)$: cpan
> Encode.c: loadable library
> I produced a patch for you, but it's not complete but works around the SIGBUS:
>
> Index: print-wg.c
> ===
> RCS file: /cvs/src/usr.sbin/tcpdump/print-wg.c,v
> retrieving revision 1.6
> diff -u -p -u -r1.6 print-wg.c
> --- print-wg.
Andrew Hewus Fresh wrote:
> This would do it, you will need to update this file that you've someone
> installed manually, this covers over the one that ships with base and
> will definitely cause that issue. Removing the files installed by the
> old version of perl's cpan client should get thing
I'll be honest your best bet is
rm -rf /usr/local/*
And I wish I was joking.
It seems somehow perl has become accustomed to prefering whatever it finds
in /usr/local, rather than it's own components installed as part of base.
Another way of looking at this, is that the /usr/ports tree part
21 matches
Mail list logo
