On Fri, Jun 06, 2025 at 07:29:27PM -0700, Steve Kargl wrote:
>
> I've narrowed the range to
>
> Good: 2025-04-24 9b2a503a1179 - main - e6000sw: add support for 88E6190X
> Bad: 2025-04-29 6c3a4b5f9b7b - main - alloca.3: move to share/man/man3
>
> Good means boots
On 6/5/25 17:18, Bjoern A. Zeeb wrote:
On Thu, 5 Jun 2025, Steve Kargl wrote:
On Thu, Jun 05, 2025 at 08:22:45AM +, Bjoern A. Zeeb wrote:
Sorting away wireless changes from sys/compat/.. here's what's left:
% git log --oneline adc33d3288..8d136fb027 sys/compat/ | grep -v
802
fff82a67fb6 at evergreen_init+0x276
#3 0x82abdc35 at radeon_device_init+0x835
#4 0x82aceb4e at radeon_driver_load_kms+0x19e
and no other mentions of evergreen.c. IOW, initialization
appears to occur once.
--
Steve
On 6/5/25 01:22, Bjoern A. Zeeb wrote:
On Wed, 4 Jun 2025, Steve Kargl wrote:
On 6/4/25 13:11, Steve Kargl wrote:
On Tue, Jun 03, 2025 at 06:45:31PM -0700, Steve Kargl wrote:
I was able to rebuild world/kernel for a 2025-04-15
src/ (aka adc33d3288) and rebuilt drm-515-kmod and
gpu-firmware
On 6/4/25 13:11, Steve Kargl wrote:
On Tue, Jun 03, 2025 at 06:45:31PM -0700, Steve Kargl wrote:
I was able to rebuild world/kernel for a 2025-04-15
src/ (aka adc33d3288) and rebuilt drm-515-kmod and
gpu-firmware. The system boots and I can kldload
radeonkmd.ko. startx brings up the expected
On Tue, Jun 03, 2025 at 06:45:31PM -0700, Steve Kargl wrote:
>
> Well, out of the frying pan and into the fire...
>
> Apparently, building world with old src/ on a system
> running a newer world and installing that old world
> over the new world is bad. To start install(1) is
On 6/4/25 00:44, Mark Millard wrote:
Steve Kargl wrote on
Date: Wed, 04 Jun 2025 01:45:31 UTC :
Well, out of the frying pan and into the fire...
Apparently, building world with old src/ on a system
running a newer world and installing that old world
over the new world is bad. To start
On 6/3/25 16:36, Steve Kargl wrote:
On Tue, Jun 03, 2025 at 08:00:00AM -0700, Steve Kargl wrote:
On 6/3/25 02:56, Matthew Seaman wrote:
On 02/06/2025 23:35, Steve Kargl wrote:
How does one use dates to checkout a particular head?
If I'm at the top of HEAD and need to got back to
mid-feb
On Tue, Jun 03, 2025 at 08:00:00AM -0700, Steve Kargl wrote:
> On 6/3/25 02:56, Matthew Seaman wrote:
> > On 02/06/2025 23:35, Steve Kargl wrote:
> > > How does one use dates to checkout a particular head?
> > > If I'm at the top of HEAD and need to got back t
On 6/3/25 02:56, Matthew Seaman wrote:
On 02/06/2025 23:35, Steve Kargl wrote:
How does one use dates to checkout a particular head?
If I'm at the top of HEAD and need to got back to
mid-february, what's the easiest option for performing
a bisection by hand?
Something like:
gi
On Mon, Jun 02, 2025 at 03:44:37PM -0700, David Wolfskill wrote:
> On Mon, Jun 02, 2025 at 03:35:50PM -0700, Steve Kargl wrote:
> > ...
> > How does one use dates to checkout a particular head?
> > If I'm at the top of HEAD and need to got back to
> > mid-februar
On Thu, May 29, 2025 at 02:37:08PM -0700, Steve Kargl wrote:
> On Thu, May 29, 2025 at 01:06:22PM -0700, Steve Kargl wrote:
> > __curthread () at /usr/src/sys/amd64/include/pcpu_aux.h:57
> > 57 __asm("movq %%gs:%c1,%0" : "=r" (td)
> > (kgdb)
On Thu, May 29, 2025 at 01:06:22PM -0700, Steve Kargl wrote:
> __curthread () at /usr/src/sys/amd64/include/pcpu_aux.h:57
> 57__asm("movq %%gs:%c1,%0" : "=r" (td)
> (kgdb) #0 __curthread () at /usr/src/sys/amd64/include/pcpu_aux.h:57
> td =
On Thu, May 29, 2025 at 01:06:22PM -0700, Steve Kargl wrote:
>
> After rebuilding world and installing, I rebuilt the drm-515
> port and the accompanying gpu-firmware. This port has worked
> upto this update. Upon running xinit to load Xorg, I am
> greeted with the panic followin
On 4/4/25 19:44, Steve Kargl wrote:
On 4/4/25 19:28, Alexander Motin wrote:
On 04.04.2025 21:45, Steve Kargl wrote:
Anyone using a Samsung T7 external SSD with FreeBSD current?
If I plug the drive into a USB 2.0 port, I see
usb_msc_auto_quirk: UQ_MSC_NO_GETMAXLUN set for USB mass storage
On 4/4/25 19:28, Alexander Motin wrote:
On 04.04.2025 21:45, Steve Kargl wrote:
Anyone using a Samsung T7 external SSD with FreeBSD current?
If I plug the drive into a USB 2.0 port, I see
usb_msc_auto_quirk: UQ_MSC_NO_GETMAXLUN set for USB mass storage
device Samsung PSSD T7 Shield (0x04e8
I need a quirk for this SSD to get recognized? Also,
shouldn't it connect with faster transfer rate than 'da0: 40.0MB/s'?
--
steve
On Wed, Feb 19, 2025 at 02:40:15PM -0800, Rick Macklem wrote:
>
> The subject line basically describes the problem glebius@
> ran into. When doing an NFS mount in /etc/fstab, it failed
> since the DNS service was not yet working and, as such,
> the DNS lookup of the server fqdn failed, causing th
On Sat, Jan 18, 2025 at 09:29:03AM -0800, bob prohaska wrote:
> A fresh install of
> FreeBSD-15.0-CURRENT-amd64-20250102-3d0a0dda3a7d-274510-memstick.img
> set up without much difficulty and Xorg seems to work out of the box
> on my Lenovo t400s. Both src and ports directories were installed by
>
On Fri, Feb 02, 2024 at 10:48:54PM +0200, Konstantin Belousov wrote:
> On Fri, Feb 02, 2024 at 12:07:35PM -0800, Steve Kargl wrote:
> >
> > Thanks for the explanation, but I think I now have a conundrum.
> > Suppose I have two shared libraries libfoo.so and libbar.so, and
>
On Sun, Jan 28, 2024 at 12:04:48PM +0200, Konstantin Belousov wrote:
> On Sat, Jan 27, 2024 at 09:22:59PM -0800, Steve Kargl wrote:
> > On Sat, Jan 27, 2024 at 10:29:34PM +0100, Dimitry Andric wrote:
> > > On 27 Jan 2024, at 18:08, Steve Kargl
> > > wrote:
> &
On Sat, Jan 27, 2024 at 10:29:34PM +0100, Dimitry Andric wrote:
> On 27 Jan 2024, at 18:08, Steve Kargl
> wrote:
> >
> > In an attempt to cleanup a bit of src/lib/msun, I ran into
> > a small issue that I cannot explain at the moment. If I have
> > /usr/bin/ld
so fabs is not built with libm.
% nm --dynamic /lib/libc.so.7 | grep fabs
000ba600 T fabs
% nm --dynamic /lib/libm.so.5 | grep fabs
0001fa90 T fabsf
000252e0 T fabsl
Is this a known issue? Should fabs be removed from Symbol.map?
--
Steve
0 kristerw Exp $") */
Should this be cleaned up or ws intentional left in the
source code?
--
Steve
ed by simply
> adjusting the defaults in newsyslog.conf.
Why ask for others opinions if you're simply going to commit
the change? It seems the commit (23 Dec 2023 06:53:06 UTC)
occurred before the initial post in the discussion here
(23 Dec 2023 07:18:23 UTC).
--
Steve
On Thu, Oct 05, 2023 at 03:11:02PM -0700, Steve Kargl wrote:
>
> I'll ping you off list when it's available.
>
Well, this is interesting. I cannot upload the files to
a location from which I can then put them up on freefall. :(
% scp -P1234 kernel.debug 10.95.
On Thu, Oct 05, 2023 at 11:33:46PM +0200, Kristof Provost wrote:
> On 5 Oct 2023, at 19:34, Steve Kargl wrote:
> > On Thu, Oct 05, 2023 at 06:05:37PM +0200, Kristof Provost wrote:
> >>
> >> On 5 Oct 2023, at 17:36, Steve Kargl wrote:
> >>> In case anyone else
On Thu, Oct 05, 2023 at 06:05:37PM +0200, Kristof Provost wrote:
> Hi Steve,
>
> On 5 Oct 2023, at 17:36, Steve Kargl wrote:
> > In case anyone else is using openvpn.
> >
> > % pkg info openvpn
> > openvpn-2.6.6
> > Name : openvpn
> > Versio
r_process (dev=,
crp=0xf80023386c08, hint=)
at /usr/src/sys/opencrypto/cryptosoft.c:1680
--
Steve
; version. At least once Acer "Peppy" chromebook has this
> issue,
s/once/one ?
--
Steve
On Thu, Aug 17, 2023 at 07:17:20PM +0100, Graham Perrin wrote:
> If I recall correctly, a few hours ago etcupdate -B resulted in removal of
> two files:
>
> /.cshrc
> /.profile
>
> Is this degree of checking/removal a novelty?
>
> (I can't recall the files' contents, or when I created them. I gu
On Sun, Feb 19, 2023 at 07:21:54PM +0100, Dimitry Andric wrote:
> On 19 Feb 2023, at 06:15, Steve Kargl
> wrote:
> >
> > On Sat, Feb 18, 2023 at 04:57:45PM -0800, Steve Kargl wrote:
> >>>
> >>> At that point it is still using the system compiler and
On Sat, Feb 18, 2023 at 04:57:45PM -0800, Steve Kargl wrote:
> >
> > At that point it is still using the system compiler and linker, and it
> > seems that the latter is lld. Do you know which version it is?
> >
>
> Good question. Unfortunate ident(1) is useless
On Sun, Feb 19, 2023 at 01:50:07AM +0100, Dimitry Andric wrote:
> On 19 Feb 2023, at 01:33, Steve Kargl
> wrote:
> >
> > During biuldworld,
> >
> > ==> usr.bin/nm (obj,all,install)
> > cc -O2 -pipe -g -fno-common -I/usr/src/contrib/elftoolchain/libelf
094-906c312bbf74:
Fri Feb 3 21:28:39 PST 2023
kargl@hotrats:/usr/obj/usr/src/amd64.amd64/sys/HOTRATS amd64
Is the wrong ld being called? The failing command shows /usr/bin/ld.
Should this be /usr/obj/usr/src/amd64.amd64/tmp/usr/bin/ld?
--
Steve
/usr/bin/ld+0xcc6e83)
#14 0x00cbe4bc (/usr/bin/ld+0xcbe4bc)
#15 0x00cbccda (/usr/bin/ld+0xcbccda)
cc: error: unable to execute command: Segmentation fault (core dumped)
cc: error: linker command failed due to signal (use -v to see invocation)
*** Error code 254
% uname -a
FreeBSD hotrats 14.0-CURRENT FreeBSD 14.0-CURRENT #0 main-n260094-906c312bbf74:
Fri Feb 3 21:28:39 PST 2023
kargl@hotrats:/usr/obj/usr/src/amd64.amd64/sys/HOTRATS amd64
The above is likely
--
Steve
On Mon, Dec 05, 2022 at 05:30:50PM +0100, Baptiste Daroussin wrote:
> On Mon, Dec 05, 2022 at 07:42:29AM -0800, Steve Kargl wrote:
> > If one has not seen Mike Karel's email, here's the URL.
> >
> > https://lists.freebsd.org/archives/dev-commits-src-main/2022-De
ow one must also add
sendmail_submit_enable="YES"
sendmail_msp_queue_enable="YES"
sendmail_outbound_enable="YES"
to rc.conf to recover a functioning sendmail.
When I upgrade the system next month, will dma remove the
ability to use sendmail without unfixing whatever damage
it does?
POLA?
--
Steve
On Sat, Dec 03, 2022 at 08:26:16PM -0500, grarpamp wrote:
> there or for some other reason. That's all bad news :( But can be fixed :)
>
It looks like the FreeBSD mailing list software
stripped your attachment with your patch. Can
you try sending it again with the patch in-line?
--
steve
On Sun, Nov 13, 2022 at 04:47:40PM +0100, louis.free...@xs4all.nl wrote:
> I noticed that after disabling gdm in /etc/rc.conf ^"gdm_enable="N"^ the
> system stays active.
> However . that is also the end the GUI in this case GNOME.
>
> Since I could not work which a machine hibernating e
On Thu, Nov 10, 2022 at 10:21:24PM -0500, Alexander Motin wrote:
> On 10.11.2022 15:29, louis.free...@xs4all.nl wrote:
> > I am still desperately trying to stop FreeBSD from sleeping, but I
> > simply do not manage.
> >
> > It is really very annoying that I have to restart the machine every 10
> >
_priority, cpu);
> } else {
> if (!single_cpu) {
> tidlemsk = idle_cpus_mask;
Mark,
My system has been running a fairly heavy load with this
patch for the last 20 or so hours without any incidences.
In fact, the system feels snappier. Thanks for the quick
response with a patch.
--
Steve
On Thu, Sep 22, 2022 at 09:07:08PM +0200, Mateusz Guzik wrote:
> On 9/22/22, Steve Kargl wrote:
> > On Thu, Sep 22, 2022 at 03:00:53PM -0400, Mark Johnston wrote:
> >> On Thu, Sep 22, 2022 at 11:31:40AM -0700, Steve Kargl wrote:
> >> > All,
> >> >
>
On Thu, Sep 22, 2022 at 03:00:53PM -0400, Mark Johnston wrote:
> On Thu, Sep 22, 2022 at 11:31:40AM -0700, Steve Kargl wrote:
> > All,
> >
> > I updated my kernel/world/all ports on Sept 19 2022.
> > Since then, I have had daily panics and hard lock-up
> > (n
oline() at fork_trampoline+0xe/frame 0xfe00daf65f30
--- trap 0, rip = 0, rop = 0, rbp = 0 ---
panic: mtx_lock_spin: recursed on non-recursive mutex sleepq chain @
/usr/src/sys/kern/subr_sleepqueue.c:267
cpuid = 7
time = 1663634259
KDB: stack backtrace:
db_trace_self_wrapper() at
--
Steve
On Thu, Jul 07, 2022 at 07:59:29PM +0200, Kristof Provost wrote:
> On 7 Jul 2022, at 19:00, Steve Kargl wrote:
>
> > The fix in
> > 37f604b49d4a seems rather questionable especially given
> > that there is no comment about why the macro is expanded
> > to a zero-trip
On Thu, Jul 07, 2022 at 10:37:40AM -0600, Warner Losh wrote:
> On Thu, Jul 7, 2022 at 10:37 AM Steve Kargl <
> s...@troutmask.apl.washington.edu> wrote:
>
> > Thanks, but
> >
> > root[216] git cherry-pick -n 37f604b49d4a
> > fatal: bad revision '
Thanks, but
root[216] git cherry-pick -n 37f604b49d4a
fatal: bad revision '37f604b49d4a'
root[217] pwd
/usr/src
--
steve
On Thu, Jul 07, 2022 at 11:24:47AM -0400, Ryan Stone wrote:
> You could "git cherry-pick -n 37f604b49d4a; git restore --unstaged
> sys/net/vnet.h"
ple please test their simple changes prior to
committing?
--
Steve
Yes, I do.
Deleting the line allows to code to compile.
--
steve
On Thu, Jul 07, 2022 at 08:24:47AM -0400, Ryan Stone wrote:
> Do you have VNET disabled in your kernel config? I believe that this
> was fixed by 37f604b49d4a.
>
> On Thu, Jul 7, 2022 at 1:07 AM Steve Ka
Please fix.
--
Steve
On Wed, May 04, 2022 at 01:22:57PM -0700, John Baldwin wrote:
> On 5/4/22 12:53 PM, Steve Kargl wrote:
> > On Wed, May 04, 2022 at 11:12:55AM -0700, John Baldwin wrote:
> >
> > I don't know the entire FreeBSD ecosystem. Do people
> > use FreeBSD on embedd
On Wed, May 04, 2022 at 11:12:55AM -0700, John Baldwin wrote:
> On 5/2/22 10:37 AM, Steve Kargl wrote:
> > On Mon, May 02, 2022 at 12:32:25PM -0400, Ed Maste wrote:
> > > On Sun, 1 May 2022 at 11:54, Steve Kargl
> > > wrote:
> > > >
> > > >
On Mon, May 02, 2022 at 10:37:00AM -0700, Steve Kargl wrote:
> On Mon, May 02, 2022 at 12:32:25PM -0400, Ed Maste wrote:
> > On Sun, 1 May 2022 at 11:54, Steve Kargl
> > wrote:
> > >
> > > diff --git a/gcc/config/freebsd-spec.h b/gcc/config/freebsd-spec.h
>
On Mon, May 02, 2022 at 12:32:25PM -0400, Ed Maste wrote:
> On Sun, 1 May 2022 at 11:54, Steve Kargl
> wrote:
> >
> > diff --git a/gcc/config/freebsd-spec.h b/gcc/config/freebsd-spec.h
> > index 594487829b5..1e8ab2e1827 100644
> > --- a/gcc/config/freebsd-spec.
On Sat, Apr 30, 2022 at 04:07:48PM -0400, Ed Maste wrote:
> On Sat, 30 Apr 2022 at 11:34, Steve Kargl
> wrote:
> >
> > On Sat, Apr 30, 2022 at 09:39:32AM -0400, Ed Maste wrote:
> > > On Fri, 29 Apr 2022 at 01:58, Steve Kargl
> > > wrote:
> > > >
On Sat, Apr 30, 2022 at 09:39:32AM -0400, Ed Maste wrote:
> On Fri, 29 Apr 2022 at 01:58, Steve Kargl
> wrote:
> >
> > If one looks at src.conf(5), one finds
> >
> >WITH_PROFILE
> > Build profiled libraries for use with gprof(8). This option i
On Fri, Apr 29, 2022 at 02:54:17PM -0700, Mark Millard wrote:
> On 2022-Apr-29, at 13:12, Steve Kargl
> wrote:
>
> > The evenual absence of libc_p.a and libm_p.a will break GCC's
> > -pg option in GCC. One will then need to know how to change the
> > GCC source
> >
> > MFC after: 1 week
> > Sponsored by: The FreeBSD Foundation
> > END QUOTE
> >
>
> I probably should have been explicit: the actual removal of WITH_PROFILE
> has not happened yet. So testing attempts to use it are not yet expected
> to have the new behavior yet.
>
The evenual absence of libc_p.a and libm_p.a will break GCC's
-pg option in GCC. One will then need to know how to change the
GCC source or install symlinks for to point *_p.a a the *.a libs.
--
Steve
On Thu, Apr 28, 2022 at 10:56:48PM -0700, Steve Kargl wrote:
> If one looks at src.conf(5), one finds
>
>WITH_PROFILE
> Build profiled libraries for use with gprof(8). This option is
> deprecated and is not present in FreeBSD 14.
>
> I assume that the
?
--
Steve
On Thu, Apr 21, 2022 at 09:44:04AM +0200, Emmanuel Vadot wrote:
>
> Hello Steve,
>
> On Tue, 19 Apr 2022 11:32:32 -0700
> Steve Kargl wrote:
>
> > FYI,
> >
> > I'm experiencing an almost daily black screen of death panic.
> > Kernel, worl
hread not running
cpuid = 4
time = 1650389478
KDB: stack backtrace:
One common trigger appears to be the use of firefox-99.0,2 from
the ports collection.
--
Steve
On Tue, Dec 21, 2021 at 03:46:40PM +0100, Marc Fonvieille wrote:
> Le 20.12.2021 16:48, Steve Kargl a écrit :
> > On Mon, Dec 20, 2021 at 11:15:53AM +0100, Marc Fonvieille wrote:
> > >
> > > I assume what Steve is talking about is the corresponding value in
> &g
On Mon, Dec 20, 2021 at 11:15:53AM +0100, Marc Fonvieille wrote:
>
> I assume what Steve is talking about is the corresponding value in
> decimal of the number of ULP.
>
Bad assumption. Please read Goldberg's paper. I am talking
about ULP in the underlying floating point format.
--
Steve
+01 tgamma
x = 1.59255925592559255925592559255925594e+01L
libm = 1.06660136733166211967839038834033897e+12
mpfr = 1.06660136733166211967839038834033459e+12L,
ULP = 41.40877
I don't print out the hex representation in ld128, but you see
the number of correct decimal digits is 33 digits compared to
36.
--
Steve
On Tue, Dec 14, 2021 at 10:21:55PM +, Mark Murray wrote:
> On 14 Dec 2021, at 21:51, Steve Kargl
> wrote:
> > Interval max ULP x at Max ULP
> > [6,1755.1]0.873414 at 1.480588145237629047468e+03
> > [1.0662,6]0.861508 at 1.999467927053
On Tue, Dec 14, 2021 at 03:47:17PM -0700, Warner Losh wrote:
> On Tue, Dec 14, 2021 at 3:23 PM Mark Murray wrote:
>
> > On 14 Dec 2021, at 21:51, Steve Kargl
> > wrote:
> > > Interval max ULP x at Max ULP
> > > [6,1755.1]0.8
emthing like 1.01e-19 or
1.01e-20.
--
Steve
imprecise.c to
ld128/b_tgammal.c. This is need to still get the
mapping of tgammal -> tgamma.
--
Steve
shot at ld128 tgammal(x) this
weekend as I still have my account on your aarch64 system
for testing.
--
Steve
On Sat, Dec 04, 2021 at 11:48:13PM +, Mark Murray wrote:
>
>
> > On 4 Dec 2021, at 18:53, Steve Kargl
> > wrote:
> >
> >
> > So, is anyone interested in seeing a massive patch?
>
> Me, please!
>
So, I have the ld80 case working. I
On Sat, Dec 04, 2021 at 11:48:13PM +, Mark Murray wrote:
>
>
> > On 4 Dec 2021, at 18:53, Steve Kargl
> > wrote:
> >
> >
> > So, is anyone interested in seeing a massive patch?
>
> Me, please!
>
It is ld80 only. ld128 is still broken. I&
On Sat, Dec 04, 2021 at 08:40:56PM +0100, Hans Petter Selasky wrote:
> On 12/4/21 19:53, Steve Kargl wrote:
> > What to do about tgammal?
(trim some history)
> >
> >Interval | Max ULP
> > ---+
> > [6,171]
rs need to be unraveled.
Extending what I have done to an ld128 implementation requires much
more effort than I have time and energy to pursue. Someone with
interest in floating point math on ld128 system can provide an
implementation.
So, is anyone interested in seeing a massive patch?
--
Steve
On Fri, Nov 05, 2021 at 03:14:46PM -0700, Steve Kargl wrote:
> On Fri, Nov 05, 2021 at 10:32:26PM +0100, Dimitry Andric wrote:
> > On 5 Nov 2021, at 21:13, Steve Kargl
> > wrote:
> > >
> > > Why was this committed?
> > >
> > > commit ac
On Fri, Nov 05, 2021 at 10:32:26PM +0100, Dimitry Andric wrote:
> On 5 Nov 2021, at 21:13, Steve Kargl
> wrote:
> >
> > Why was this committed?
> >
> > commit ac76bc1145dd7f4476e5d982ce8f355f71015713
> > Author: Dimitry Andric
> > Date: Tue Feb
the file,
which means that there are needless reloading of x, y, and h
from memory.
--
Steve
On Fri, Nov 05, 2021 at 01:25:42PM -0400, Ed Maste wrote:
> On Thu, 4 Nov 2021 at 21:09, Steve Kargl
> wrote:
> >
> > A patch has been attached to
> >
> > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216862
> >
> > which implements cexpl().
>
A patch has been attached to
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216862
which implements cexpl().
Note, the patch includes some bug fixes for libm on
ld128 hardware.
--
Steve
On Thu, Oct 28, 2021 at 03:28:51PM -0700, Steve Kargl wrote:
> kib@ recently committed my implementations of cospi[fl],
> sinpi[fl], and tanpi[fl]. These functions have been
> extensively tested for float, double, and long double
> where long double is the Intel 80-bit long double (
?
--
Steve
freebsd.org/src/commit/?id=3550a49f6814af38c21b0033ef8746953451dade
>
> Since the license is a verbatim copy of the standard SPDX license, I tagged
> it using our draft license policy's
> suggested SPDX-License-Identifier: tag.
>
> Warner
>
> On Fri, O
THER DEALINGS IN THE SOFTWARE.
Please add a Copyright to these files or remove them from the
repository to prevent someone from accidently violating said
Copyright.
--
Steve
On Fri, Oct 22, 2021 at 03:51:15PM -0600, Warner Losh wrote:
> On Fri, Oct 22, 2021 at 3:30 PM Steve Kargl <
> s...@troutmask.apl.washington.edu> wrote:
>
> > All,
> >
> > With the new world order, what is the future of ident(1)?
> > Should it be removed fro
I touch? For new files, is
it expected that useless $FreeBSD$ tags should be added?
--
Steve
On Wed, Sep 08, 2021 at 02:10:47AM +0100, Jamie Landeg-Jones wrote:
> Steve Kargl wrote:
>
> > Yes, that's likely. So, it could be a change in behavior
> > for ImageMagick. Your suggested ps command doesn't provide
>
> I don't know when the chan
On Tue, Sep 07, 2021 at 04:20:30PM -0700, Cy Schubert wrote:
> On September 7, 2021 3:42:53 PM PDT, Steve Kargl
> wrote:
> >I have stumbled about a quandry, which I hope someone
> >can shed some light upon. In my day job, I often
> >generate a sequence of images and disp
ce an independent program and not a
symlink to magick. Thus, killall just worked. Or,
(2) killall no longer works because command associated
with process 19463 is not really 'display' and the
symlink isn't resolved to actually kill 'magick'.
So, just chekcing (2), here. Is this a change in behvior
for FreeBSD?
--
Steve
if you are addressing Mark or me.
> > For me, I know nothing about ATF.
>
> man 7 atf
>
> has more details.
>
% man 7 atf
No manual entry for atf
% grep -i tests /etc/src.conf
WITHOUT_GOOGLETEST="YES"
WITHOUT_TESTS="YES"
--
Steve
s won't regress as I'm one of the
few people who actually looks at threshold issues
in libm.
--
Steve
No, thank you for the quick response.
Of course, a one character diff might be easier to review. :-)
--
steve
On Mon, Sep 06, 2021 at 06:55:07PM +0100, Mark Murray wrote:
> Thanks!
>
> And it's committed!
>
> M
>
> > On 6 Sep 2021, at 18:53, Steve Kargl
>
Fine with me. I don't have a phabricator account and
bugzilla reports seems to get lost in the ether.
--
steve
On Mon, Sep 06, 2021 at 06:45:11PM +0100, Mark Murray wrote:
> Hi
>
> I've opened a Phab ticket for this. I hope that's OK?
>
> https://reviews.freebsd
if(ix<0x3f77) return (hy<0)? sn*huge*huge:sn*tiny*tiny;
+ if(ix<0x3f76) return (hy<0)? sn*huge*huge:sn*tiny*tiny;
if(ix>0x3f87) return (hy>0)? sn*huge*huge:sn*tiny*tiny;
/* now |1-x| is tiny <= 2**-20, suffice to compute
log(x) by x-x^2/2+x^3/3-x^4/4 */
--
Steve
hives that
violate the statement on the FreeBSD.org.
--
steve
On Thu, Jul 29, 2021 at 05:39:04PM +0200, Matthias Apitz wrote:
>
> Is this a phishing attack or did I missed some change in the FBSD
> mailing lists?
>
> matthias
>
> - Forwarded message from fr
purposes, do you only need kernel.debug
and vmcore.2, or do you also need the loaded modules?
--
Steve
On Tue, Jul 20, 2021 at 12:15:58PM -0400, Mark Johnston wrote:
> On Tue, Jul 20, 2021 at 09:07:04AM -0700, Steve Kargl wrote:
> > On Mon, Jul 19, 2021 at 07:05:03PM -0700, Steve Kargl wrote:
> > > On Mon, Jul 19, 2021 at 07:55:07PM -0400, Mark Johnston wrote:
> > > >
On Mon, Jul 19, 2021 at 07:05:03PM -0700, Steve Kargl wrote:
> On Mon, Jul 19, 2021 at 07:55:07PM -0400, Mark Johnston wrote:
> > On Mon, Jul 19, 2021 at 03:02:19PM -0700, Steve Kargl wrote:
> > >
> > > (kgdb) #0 __curthread () at /usr/src/sys/amd64/include/pcpu
On Mon, Jul 19, 2021 at 07:55:07PM -0400, Mark Johnston wrote:
> On Mon, Jul 19, 2021 at 03:02:19PM -0700, Steve Kargl wrote:
> >
> > (kgdb) #0 __curthread () at /usr/src/sys/amd64/include/pcpu_aux.h:55
> > #1 doadump (textdump=textdump@entry=1)
> > at /usr/src/s
/amd64/amd64/trap.c:1156
#25
#26 0x0002011a12fa in ?? ()
Backtrace stopped: Cannot access memory at address 0x7fffe0c8
(kgdb)
--
Steve
1 - 100 of 1550 matches
Mail list logo
