Re: kernel panic and fun debugging

2020-10-17 Thread Steve Kargl
On Sat, Oct 17, 2020 at 12:58:48PM -0600, Warner Losh wrote: > On Sat, Oct 17, 2020, 12:00 PM Andrey V. Elsukov wrote: > > > On 15.10.2020 09:56, Steve Kargl wrote: > > > Just had a kernel panic. Best info I give you is > > > > > > % uname -a > &g

Re: kernel panic and fun debugging

2020-10-17 Thread Steve Kargl
On Sat, Oct 17, 2020 at 08:57:31PM +0300, Andrey V. Elsukov wrote: > On 15.10.2020 09:56, Steve Kargl wrote: > > Just had a kernel panic. Best info I give you is > > > > % uname -a > > FreeBSD mobile 13.0-CURRENT FreeBSD 13.0-CURRENT #1 r366176M: Sat Sep 26 >

kernel panic and fun debugging

2020-10-15 Thread Steve Kargl
Just had a kernel panic. Best info I give you is % uname -a FreeBSD mobile 13.0-CURRENT FreeBSD 13.0-CURRENT #1 r366176M: Sat Sep 26 10:35:23 PDT 2020 kargl@mobile:/usr/obj/usr/src/i386.i386/sys/MOBILE i386 % kgdb gdb /usr/lib/debug/boot/kernel/kernel.debug vmcore.1 ... Reading symbols

Re: Plans for git

2020-09-20 Thread Steve Kargl
On Sun, Sep 20, 2020 at 08:41:13AM -0700, Pete Wright wrote: > > > > making quarterly reports about this for almost a years as well. We put out > > > calls for people to help with the efforts about the same time. We have > > > tried at every step of the way to be open and honest that this was

[PATCH] libm -- optimize __ldexp_cexp[f]

2020-09-19 Thread Steve Kargl
The following patch is an opimization for he kernels used by cexp(x) and cexpf(x). . Use sincos[f] instead of a call to cos[f] and a call to sin[f]. . While here, alphabetize declaration. --- /usr/src/lib/msun/src/k_exp.c 2019-02-23 07:45:03.879997000 -0800 +++ src/k_exp.c 2019-12-26

Re: [PATCH] libm -- fix expl kernels

2020-09-19 Thread Steve Kargl
On Sat, Sep 19, 2020 at 04:58:49PM -0700, Steve Kargl wrote: > The following patch fixes the ld80 and ld128 kernels for expl(x). Subj: is slightly wrong. This fixes the cexpl(z) kernels. > I can't test ld128, so that patch is untested. > > . Micro-optimization: use sincosl(x) inste

[PATCH] libm -- fix expl kernels

2020-09-19 Thread Steve Kargl
The following patch fixes the ld80 and ld128 kernels for expl(x). I can't test ld128, so that patch is untested. . Micro-optimization: use sincosl(x) instead of a call to cosl(x) and a call to sinl(x). Argument reduction is done once not twice. . Use a long double constant instead of an

Re: Deprecating ftpd in the FreeBSD base system?

2020-09-17 Thread Steve Kargl
On Thu, Sep 17, 2020 at 09:01:57AM -0600, Ian Lepore wrote: > On Thu, 2020-09-17 at 18:43 +0400, Gleb Popov wrote: > > On Thu, Sep 17, 2020 at 6:05 PM Cy Schubert < > > cy.schub...@cschubert.com> > > wrote: > > > > > I've been advocating removing FTP (and HTTP) from libfetch as well. > > > People

Re: clang miscompiles OpenLibm on i686-*-freebsd

2020-09-08 Thread Steve Kargl
On Tue, Sep 08, 2020 at 09:11:50PM +0200, Dimitry Andric wrote: > On 8 Sep 2020, at 19:47, Steve Kargl > wrote: > > > > I think I've found the problem, and it appears to be > > due to a change byt Openlibm developers to the file > > math_private.h copied fr

Re: clang miscompiles OpenLibm on i686-*-freebsd

2020-09-08 Thread Steve Kargl
On Mon, Sep 07, 2020 at 07:55:13PM -0700, Steve Kargl wrote: > On Mon, Sep 07, 2020 at 07:10:02PM -0700, Steve Kargl wrote: > > > > Interval tested for exp2f: [1,8] > >ulp <= 0.5: 0.056% 14072 | 0.056% 14072 > > 0.5 < ulp < 0.6: 0.000%

Re: clang miscompiles OpenLibm on i686-*-freebsd

2020-09-07 Thread Steve Kargl
On Mon, Sep 07, 2020 at 07:10:02PM -0700, Steve Kargl wrote: > > Interval tested for exp2f: [1,8] >ulp <= 0.5: 0.056% 14072 | 0.056% 14072 > 0.5 < ulp < 0.6: 0.000% 8 | 0.056% 14080 > 3.0 < ulp < 0.0: 99.944% 25151744

clang miscompiles OpenLibm on i686-*-freebsd

2020-09-07 Thread Steve Kargl
TL;DR summary: clang is broken for numerical on i686 FreeBSD. % uname -a FreeBSD mobile 13.0-CURRENT FreeBSD 13.0-CURRENT #0 r361834M: Fri Jun 5 08:49:26 PDT 2020 obj/usr/src/i386.i386/sys/MOBILE i386 % which clang /usr/bin/clang % clang --version FreeBSD clang version 10.0.1

Re: Plans for git (was: Please check the current beta git conversions)

2020-09-02 Thread Steve Kargl
On Wed, Sep 02, 2020 at 11:11:50AM -0600, Warner Losh wrote: > On Wed, Sep 2, 2020 at 10:47 AM Steve Kargl < > s...@troutmask.apl.washington.edu> wrote: > > This is an insultingly stupid comment to make. We don't need people to say > the obvious. > > This sort of co

Re: Plans for git (was: Please check the current beta git conversions)

2020-09-02 Thread Steve Kargl
On Wed, Sep 02, 2020 at 12:14:08PM -0400, Ed Maste wrote: > On Wed, 2 Sep 2020 at 02:31, Steve Kargl > wrote: > > > > > A short intro on git for svn users: > > > https://hackmd.io/ML5TSl8mQ5-27B5eqDf7YA?view > > > > > > > ROTFL. From the

Re: Plans for git (was: Please check the current beta git conversions)

2020-09-02 Thread Steve Kargl
On Wed, Sep 02, 2020 at 08:01:17AM +0200, Kurt Jaeger wrote: > Hi! > > > On Tuesday, 1 September 2020 at 13:14:10 -0400, Ed Maste wrote: > > > We've been updating the svn-git converter and pushing out a new > > > converted repo every two weeks, and are now approaching the time where > > > we'd

Re: Outdated jemalloc in CURRENT

2020-04-18 Thread Steve Kargl
On Sat, Apr 18, 2020 at 05:01:08PM +0200, Gordon Bergling wrote: > > On Sat, Apr 18, 2020 at 07:20:03AM -0700, Steve Kargl wrote: >> On Sat, Apr 18, 2020 at 03:05:25PM +0300, nonamel...@ukr.net wrote: >>> Hi everyone! >>> >>> As I see, CURRENT still

Re: Outdated jemalloc in CURRENT

2020-04-18 Thread Steve Kargl
On Sat, Apr 18, 2020 at 03:05:25PM +0300, nonamel...@ukr.net wrote: > Hi everyone! > > As I see, CURRENT still uses outdated jemalloc 5.1.0 with some performance > regressions that was fixed in 5.2.1. > > Are there some issues that blocking update jemalloc to recent version? >

panic: sleeping thread. Possibly related to drm and swapping.

2020-04-15 Thread Steve Kargl
Just recieved this panic. I am using drm-legacy-kmod-g20200306 on a Dell Latitude D530 laptop. The panic occurred as I was starting libreoffice. Suggestions? mobile dumped core - see /var/crash/vmcore.2 Wed Apr 15 09:22:07 PDT 2020 FreeBSD mobile 13.0-CURRENT FreeBSD 13.0-CURRENT #2 r359179M:

Re: Is sc(4) no longer supported in GENERIC?

2020-04-03 Thread Steve Kargl
On Fri, Apr 03, 2020 at 11:50:44AM -0700, Chris wrote: > > No. *I'm* sorry. You were perfectly clear. It was late for me, and I > wasn't very alert. Thank you *very* much for all your help! :) > For future reference, FreeBSD comes with some fairly decent documentation (see, e.g., vt(4)). --

Buildworld dying wint lldb?

2020-02-12 Thread Steve Kargl
Anyone else see ===> usr.bin/clang/lldb (all) c++ -target x86_64-unknown-freebsd13.0 --sysroot=/usr/obj/usr/src/amd64.amd64/tmp -B/usr/obj/usr/src/amd64.amd64/tmp/usr/bin -O2 -pipe -I/usr/src/contrib/llvm-project/lldb/include -I/usr/obj/usr/src/amd64.amd64/usr.bin/clang/lldb -march=bdver2

Re: After update to r357104 build of poudriere jail fails with 'out of swap space'

2020-01-25 Thread Steve Kargl
On Sat, Jan 25, 2020 at 03:31:16PM -0800, Steve Kargl wrote: > On Sat, Jan 25, 2020 at 02:09:29PM -0800, Cy Schubert wrote: > > On January 25, 2020 1:52:03 PM PST, Steve Kargl > > wrote: > > >On Sat, Jan 25, 2020 at 01:41:16PM -0800, Cy Schubert wrote: > > >

Re: After update to r357104 build of poudriere jail fails with 'out of swap space'

2020-01-25 Thread Steve Kargl
On Sat, Jan 25, 2020 at 02:09:29PM -0800, Cy Schubert wrote: > On January 25, 2020 1:52:03 PM PST, Steve Kargl > wrote: > >On Sat, Jan 25, 2020 at 01:41:16PM -0800, Cy Schubert wrote: > >> > >> It's not just poudeiere. Standard port builds of chromium, rust > &

Re: After update to r357104 build of poudriere jail fails with 'out of swap space'

2020-01-25 Thread Steve Kargl
On Sat, Jan 25, 2020 at 01:41:16PM -0800, Cy Schubert wrote: > > It's not just poudeiere. Standard port builds of chromium, rust > and thunderbird also fail on my machines with less than 8 GB. > Interesting. I routinely build chromium, rust, firefox, llvm and few other resource-hunger ports on

Re: Turn off PROFILE option and remove WITH_PROFILE after FreeBSD 13?

2020-01-17 Thread Steve Kargl
On Fri, Jan 17, 2020 at 01:12:32PM -0500, Ed Maste wrote: > On Fri, 17 Jan 2020 at 12:19, Steve Kargl > wrote: > > > > Why? Because adding -pg to the gfortran command line is sufficient > > to getting profiling information for long running numerically > > i

Re: Turn off PROFILE option and remove WITH_PROFILE after FreeBSD 13?

2020-01-17 Thread Steve Kargl
On Fri, Jan 17, 2020 at 10:40:09AM -0500, Ed Maste wrote: > > Any comments on this plan? Does anyone use the -pg compiler flag and > the _p.a profiling library archives? > Yes, I do. I have WITHOUT_PROFILE='yes' set in /etc/make.conf for a normal buildworld. I then comment it out and

Re: OpenSSL breaks factor(6)

2020-01-06 Thread Steve Kargl
On Sun, Dec 29, 2019 at 08:02:47AM -0800, Steve Kargl wrote: > Here's a final attempt at fixing and documenting FreeBSD's factor(6). > Do what you want with the patch. With and without OpenSSL, one now > gets > > % factor +123 123 123 123zabc 123abc +123abc 0x123abc +0x123

Re: OpenSSL breaks factor(6)

2019-12-29 Thread Steve Kargl
On Sun, Dec 29, 2019 at 05:14:28PM -0500, Garance A Drosehn wrote: > On 29 Dec 2019, at 2:17, Steve Kargl wrote: > > > On Sun, Dec 29, 2019 at 01:34:28AM -0500, Garance A Drosehn wrote: > >>> > >>> An interested user will need to add that support. AFAIK,

Re: OpenSSL breaks factor(6)

2019-12-29 Thread Steve Kargl
On Sun, Dec 29, 2019 at 01:31:26PM -0900, Robert Wing wrote: > Have y'all ever seen reviews.freebsd.org? > I have a FreeBSD login account and a FreeBSD bugzilla account. I don't need yet another FreeBSD account. If bugzilla were set up to parse email replies, this would be attached a bug

Re: OpenSSL breaks factor(6)

2019-12-29 Thread Steve Kargl
On Sun, Dec 29, 2019 at 08:02:47AM -0800, Steve Kargl wrote: > Here's a final attempt at fixing and documenting FreeBSD's factor(6). > Do what you want with the patch. With and without OpenSSL, one now > gets > > % factor +123 123 123 123zabc 123abc +123abc 0x123abc +0x123

Re: OpenSSL breaks factor(6)

2019-12-29 Thread Steve Kargl
Here's a final attempt at fixing and documenting FreeBSD's factor(6). Do what you want with the patch. With and without OpenSSL, one now gets % factor +123 123 123 123zabc 123abc +123abc 0x123abc +0x123abc 123: 3 41 123: 3 41 123: 3 41 123: 3 41 1194684: 2 2 3 29 3433 1194684: 2 2 3 29 3433

Re: OpenSSL breaks factor(6)

2019-12-28 Thread Steve Kargl
On Sat, Dec 28, 2019 at 11:17:31PM -0800, Steve Kargl wrote: > On Sun, Dec 29, 2019 at 01:34:28AM -0500, Garance A Drosehn wrote: > > On 29 Dec 2019, at 0:10, Steve Kargl wrote: > > > > > On Sat, Dec 28, 2019 at 10:46:52PM -0500, Garance A Drosehn wrote: > > &g

Re: OpenSSL breaks factor(6)

2019-12-28 Thread Steve Kargl
On Sun, Dec 29, 2019 at 01:34:28AM -0500, Garance A Drosehn wrote: > On 29 Dec 2019, at 0:10, Steve Kargl wrote: > > > On Sat, Dec 28, 2019 at 10:46:52PM -0500, Garance A Drosehn wrote: > >> > >> What if the user wants to factor a hexadecimal value which does not

Re: OpenSSL breaks factor(6)

2019-12-28 Thread Steve Kargl
On Sat, Dec 28, 2019 at 09:34:52PM -0800, Rodney W. Grimes wrote: > > On Sat, Dec 28, 2019 at 10:46:52PM -0500, Garance A Drosehn wrote: > > > On 27 Dec 2019, at 17:42, Steve Kargl wrote: > > > > > > > > This patch now includes a fix for hexadecimal conversi

Re: OpenSSL breaks factor(6)

2019-12-28 Thread Steve Kargl
On Sat, Dec 28, 2019 at 10:46:52PM -0500, Garance A Drosehn wrote: > On 27 Dec 2019, at 17:42, Steve Kargl wrote: > > > > This patch now includes a fix for hexadecimal conversion. It > > simple scans the string for a hex digit in [a,...,f] and assumes > > that a

Re: OpenSSL breaks factor(6)

2019-12-28 Thread Steve Kargl
On Fri, Dec 27, 2019 at 09:15:33PM -0800, Steve Kargl wrote: > On Fri, Dec 27, 2019 at 08:42:53PM -0800, Rodney W. Grimes wrote: > > > On Fri, Dec 27, 2019 at 07:00:04PM -0800, Rodney W. Grimes wrote: > > > > > On Fri, Dec 27, 2019 at 01:47:17

Re: OpenSSL breaks factor(6)

2019-12-27 Thread Steve Kargl
On Fri, Dec 27, 2019 at 08:42:53PM -0800, Rodney W. Grimes wrote: > > On Fri, Dec 27, 2019 at 07:00:04PM -0800, Rodney W. Grimes wrote: > > > > On Fri, Dec 27, 2019 at 01:47:17PM -0800, Steve Kargl wrote: > > > > > > > > This patch now

Re: OpenSSL breaks factor(6)

2019-12-27 Thread Steve Kargl
On Fri, Dec 27, 2019 at 07:00:04PM -0800, Rodney W. Grimes wrote: > > On Fri, Dec 27, 2019 at 01:47:17PM -0800, Steve Kargl wrote: > > > On Fri, Dec 27, 2019 at 01:25:30PM -0800, Steve Kargl wrote: > > > > The use of OpenSSL in factor(6) breaks factor(6) with respect t

Re: OpenSSL breaks factor(6)

2019-12-27 Thread Steve Kargl
On Fri, Dec 27, 2019 at 02:42:12PM -0800, Steve Kargl wrote: > On Fri, Dec 27, 2019 at 01:47:17PM -0800, Steve Kargl wrote: > > On Fri, Dec 27, 2019 at 01:25:30PM -0800, Steve Kargl wrote: > > > The use of OpenSSL in factor(6) breaks factor(6) with respect to >

Re: OpenSSL breaks factor(6)

2019-12-27 Thread Steve Kargl
On Fri, Dec 27, 2019 at 01:47:17PM -0800, Steve Kargl wrote: > On Fri, Dec 27, 2019 at 01:25:30PM -0800, Steve Kargl wrote: > > The use of OpenSSL in factor(6) breaks factor(6) with respect to > > its documentation. > > > > % man factor > > ... > >

Re: OpenSSL breaks factor(6)

2019-12-27 Thread Steve Kargl
On Fri, Dec 27, 2019 at 01:25:30PM -0800, Steve Kargl wrote: > The use of OpenSSL in factor(6) breaks factor(6) with respect to > its documentation. > > % man factor > ... > Numbers may be preceded by a single '+'. > ... > > % factor +125 > factor

OpenSSL breaks factor(6)

2019-12-27 Thread Steve Kargl
The use of OpenSSL in factor(6) breaks factor(6) with respect to its documentation. % man factor ... Numbers may be preceded by a single '+'. ... % factor +125 factor: +125: illegal numeric format. without OpenSSL one gets % factor +125 125: 5 5 5 Although undocumented, factor(6) seems

Re: [PATCH] primes(6) -- remove unnecessary code

2019-12-27 Thread Steve Kargl
On Fri, Dec 27, 2019 at 08:36:34PM +, Jamie Landeg-Jones wrote: > Steve Kargl wrote: > > > Hmm, I withdraw the patch. One can get a negative start > > value, but one would need to force that condition via > > a subversion via getopt. > > Or: > > pri

Re: [PATCH] primes(6) -- remove unnecessary code

2019-12-27 Thread Steve Kargl
On Fri, Dec 27, 2019 at 09:55:10AM -0800, Steve Kargl wrote: > This patch removes an unnecessary check as > the condition can never occur. > > Index: primes.c > === > --- primes.c (revision 355983) > +++ pr

[PATCH] primes(6) -- remove unnecessary code

2019-12-27 Thread Steve Kargl
This patch removes an unnecessary check as the condition can never occur. Index: primes.c === --- primes.c(revision 355983) +++ primes.c(working copy) @@ -129,7 +129,7 @@ switch (argc) { case 2:

[PATCH] Typo in hastd.8 man page

2019-12-21 Thread Steve Kargl
Path should explain the issue. Index: hastd.8 === --- hastd.8 (revision 355983) +++ hastd.8 (working copy) @@ -44,7 +44,7 @@ daemon is responsible for managing highly available GEOM providers. .Pp .Nm -allows the

Re: CAM breaks USB [was Re: USB causing boot to hang]

2019-12-09 Thread Steve Kargl
On Fri, Dec 06, 2019 at 06:11:48PM -0800, Steve Kargl wrote: > On Sat, Dec 07, 2019 at 01:16:13AM +0100, Hans Petter Selasky wrote: > > > > There is an option you can compile into the kernel which will allow the > > keyboard to enter the debugger. > > > >

Re: CAM breaks USB [was Re: USB causing boot to hang]

2019-12-06 Thread Steve Kargl
On Sat, Dec 07, 2019 at 01:16:13AM +0100, Hans Petter Selasky wrote: > > There is an option you can compile into the kernel which will allow the > keyboard to enter the debugger. > > options ALT_BREAK_TO_DEBUGGER > > Sounds to me like either a leaked refcount or that one thread is >

Re: CAM breaks USB [was Re: USB causing boot to hang]

2019-12-06 Thread Steve Kargl
On Fri, Dec 06, 2019 at 07:09:55PM -0500, Alexander Motin wrote: > On 06.12.2019 18:41, Steve Kargl wrote: > > On Fri, Dec 06, 2019 at 06:15:32PM -0500, Alexander Motin wrote: > >> On 06.12.2019 17:52, Steve Kargl wrote: > >>> On Fri, Dec 06, 2019 at 03:33

Re: CAM breaks USB [was Re: USB causing boot to hang]

2019-12-06 Thread Steve Kargl
On Fri, Dec 06, 2019 at 06:15:32PM -0500, Alexander Motin wrote: > On 06.12.2019 17:52, Steve Kargl wrote: > > On Fri, Dec 06, 2019 at 03:33:09PM -0700, Warner Losh wrote: > >> On Fri, Dec 6, 2019 at 3:31 PM Steve Kargl > >> > >> wrote: > >> > >

Re: CAM breaks USB [was Re: USB causing boot to hang]

2019-12-06 Thread Steve Kargl
On Fri, Dec 06, 2019 at 02:52:31PM -0800, Steve Kargl wrote: > > The commit message for 355010 states: > >Devices appearing on USB bus later may still require setting >kern.cam.boot_delay, but hopefully those are minority. > > There is no statement about "

Re: CAM breaks USB [was Re: USB causing boot to hang]

2019-12-06 Thread Steve Kargl
On Fri, Dec 06, 2019 at 05:44:55PM -0500, Alexander Motin wrote: > > Yes, I made the change, and it was supposed to improve USB > inter-operation, but after reading this email I still have no clue what > could be wrong, so ideas welcome. Sorry about the initial vagueness. It took a couple of

Re: CAM breaks USB [was Re: USB causing boot to hang]

2019-12-06 Thread Steve Kargl
On Fri, Dec 06, 2019 at 03:33:09PM -0700, Warner Losh wrote: > On Fri, Dec 6, 2019 at 3:31 PM Steve Kargl > wrote: > > > On Fri, Dec 06, 2019 at 12:23:16PM -0800, Steve Kargl wrote: > > > I updates /usr/src to r355452, and updated by kernel and > > > world. Upon

CAM breaks USB [was Re: USB causing boot to hang]

2019-12-06 Thread Steve Kargl
On Fri, Dec 06, 2019 at 12:23:16PM -0800, Steve Kargl wrote: > I updates /usr/src to r355452, and updated by kernel and > world. Upon rebooting, verbose boot messages susgests > the system is hanging when USB starts to attach. With > the 3-week kernel verbose boot shows: > > .

Re: USB causing boot to hang

2019-12-06 Thread Steve Kargl
On Fri, Dec 06, 2019 at 09:32:01PM +, Bjoern A. Zeeb wrote: > On 6 Dec 2019, at 20:23, Steve Kargl wrote: > > > I updates /usr/src to r355452, and updated by kernel and > > world. Upon rebooting, verbose boot messages susgests > > the system is hanging w

USB causing boot to hang

2019-12-06 Thread Steve Kargl
I updates /usr/src to r355452, and updated by kernel and world. Upon rebooting, verbose boot messages susgests the system is hanging when USB starts to attach. With the 3-week kernel verbose boot shows: ... pcm4: at nid 30 on hdaa1 pcm4: Playback: pcm4: Stream cap: 0x0005 AC3 PCM

Re: unkillable process consuming 100% cpu

2019-11-13 Thread Steve Kargl
On Mon, Nov 11, 2019 at 01:22:09PM +0100, Hans Petter Selasky wrote: > diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_gpuvm.c > b/drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_gpuvm.c > index a6e0a16ae..0697d70f4 100644 > --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_gpuvm.c > +++

Re: unkillable process consuming 100% cpu

2019-11-13 Thread Steve Kargl
On Wed, Nov 13, 2019 at 04:22:19PM +0100, Hans Petter Selasky wrote: > On 2019-11-13 15:52, Steve Kargl wrote: > > at /usr/src/sys/amd64/amd64/trap.c:743 > > #7 0x808b0468 in trap (frame=0xfe00b460e0c0) > > at /usr/src/sys/amd64/amd64/trap.

Re: unkillable process consuming 100% cpu

2019-11-13 Thread Steve Kargl
On Wed, Nov 13, 2019 at 09:10:06AM +0100, Hans Petter Selasky wrote: > On 2019-11-13 01:30, Steve Kargl wrote: > > > > I installed the 2nd seqlock.diff, rebuilt drm-current-kmod-4.16.g20191023, > > rebooting, and have been pounding on the system with workloads that ar

Re: unkillable process consuming 100% cpu

2019-11-12 Thread Steve Kargl
On Tue, Nov 12, 2019 at 06:48:22PM +0100, Hans Petter Selasky wrote: > On 2019-11-12 18:31, Steve Kargl wrote: > >> Can you open the radeonkms.ko in gdb83 from ports and type: > >> > >> l *(radeon_gem_busy_ioctl+0x30) > >> > > % /boot/modules/radeonkms

Re: unkillable process consuming 100% cpu

2019-11-12 Thread Steve Kargl
On Mon, Nov 11, 2019 at 10:34:23AM +0100, Hans Petter Selasky wrote: > Hi, > > Can you open the radeonkms.ko in gdb83 from ports and type: > > l *(radeon_gem_busy_ioctl+0x30) > % /boot/modules/radeonkms.ko (gdb) l *(radeon_gem_busy_ioctl+0x30) 0xa12b0 is in radeon_gem_busy_ioctl

Re: unkillable process consuming 100% cpu

2019-11-11 Thread Steve Kargl
On Mon, Nov 11, 2019 at 02:22:55PM +0100, Hans Petter Selasky wrote: > On 2019-11-08 23:09, Steve Kargl wrote: > > Here's 'procstat -kk' for the stuck process with the long line wrapped. > > Can you run this command a couple of times and see if the backtrace changes? >

Re: unkillable process consuming 100% cpu

2019-11-08 Thread Steve Kargl
On Thu, Nov 07, 2019 at 03:32:23PM -0500, Mark Johnston wrote: > On Thu, Nov 07, 2019 at 12:29:19PM -0800, Steve Kargl wrote: > > I haven't seen anyone post about an unkillable process > > (even by root), which consumes 100% cpu. > > > > last pid: 4592; load average

Re: unkillable process consuming 100% cpu

2019-11-07 Thread Steve Kargl
On Thu, Nov 07, 2019 at 03:32:23PM -0500, Mark Johnston wrote: > On Thu, Nov 07, 2019 at 12:29:19PM -0800, Steve Kargl wrote: > > I haven't seen anyone post about an unkillable process > > (even by root), which consumes 100% cpu. > > > > last pid: 4592; load average

unkillable process consuming 100% cpu

2019-11-07 Thread Steve Kargl
I haven't seen anyone post about an unkillable process (even by root), which consumes 100% cpu. last pid: 4592; load averages: 1.24, 1.08, 0.74 up 13+20:21:20 12:26:29 68 processes: 2 running, 66 sleeping CPU: 0.1% user, 0.0% nice, 12.6% system, 0.0% interrupt, 87.2% idle Mem: 428M

[PATCH] Typo in libm code

2019-11-07 Thread Steve Kargl
This patch https://cvsweb.openbsd.org/src/lib/libm/src/ld80/k_sincosl.h?sortby=date is applicable to FreeBSD. Index: src/k_sincosl.h === --- src/k_sincosl.h (revision 353571) +++ src/k_sincosl.h (working copy) @@ -28,8

Re: Someone broke buildworld with ZFS commit!

2019-10-15 Thread Steve Kargl
On Tue, Oct 15, 2019 at 09:44:12AM -0700, Steve Kargl wrote: > In file included from > /usr/src/cddl/contrib/opensolaris/lib/libzfs_core/common/libzfs_core.c:89: > In file included from > /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/sys/zfs_ioctl.h:35: > In file includ

Someone broke buildworld with ZFS commit!

2019-10-15 Thread Steve Kargl
In file included from /usr/src/cddl/contrib/opensolaris/lib/libzfs_core/common/libzfs_core.c:89: In file included from /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/sys/zfs_ioctl.h:35: In file included from /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/sys/dsl_deleg.h:30: In

Re: radeon panics kernels

2019-10-04 Thread Steve Kargl
On Fri, Oct 04, 2019 at 12:17:30PM -0700, Johannes Lundberg wrote: > On Fri, Oct 4, 2019 at 11:39 Steve Kargl > wrote: > > > On Thu, Oct 03, 2019 at 11:52:38PM +0200, Hans Petter Selasky wrote: > > > On 2019-10-03 22:26, Steve Kargl wrote: > > > > > >

Re: radeon panics kernels

2019-10-04 Thread Steve Kargl
On Thu, Oct 03, 2019 at 11:52:38PM +0200, Hans Petter Selasky wrote: > On 2019-10-03 22:26, Steve Kargl wrote: > > On Thu, Oct 03, 2019 at 03:05:27PM +0200, Hans Petter Selasky wrote: > >> > >> If you leave the port debug knob for drm-current-kmod AS-IS, I

Re: radeon panics kernels

2019-10-03 Thread Steve Kargl
On Thu, Oct 03, 2019 at 11:52:38PM +0200, Hans Petter Selasky wrote: > On 2019-10-03 22:26, Steve Kargl wrote: > > On Thu, Oct 03, 2019 at 03:05:27PM +0200, Hans Petter Selasky wrote: > >> > >> If you leave the port debug knob for drm-current-kmod AS-IS, I

Re: radeon panics kernels

2019-10-03 Thread Steve Kargl
On Thu, Oct 03, 2019 at 03:05:27PM +0200, Hans Petter Selasky wrote: > > If you leave the port debug knob for drm-current-kmod AS-IS, I think you > can get away with: > > make DEBUG_FLAGS="-g" > > Then re-load the vmcore file in GDB/KGDB from ports (!) and add the > symbol files for the

Re: radeon panics kernels

2019-10-03 Thread Steve Kargl
On Thu, Oct 03, 2019 at 03:05:27PM +0200, Hans Petter Selasky wrote: > On 2019-10-03 14:59, Steve Kargl wrote: > > On Thu, Oct 03, 2019 at 09:17:32AM +0200, Hans Petter Selasky wrote: > >> On 2019-10-02 23:19, Steve Kargl wrote: > >>> troutmask.apl.washington.ed

Re: radeon panics kernels

2019-10-03 Thread Steve Kargl
On Thu, Oct 03, 2019 at 05:59:20AM -0700, Steve Kargl wrote: > On Thu, Oct 03, 2019 at 09:17:32AM +0200, Hans Petter Selasky wrote: > > On 2019-10-02 23:19, Steve Kargl wrote: > > > troutmask.apl.washington.edu dumped core - see /var/crash/vmcore.7 > > > > &g

Re: radeon panics kernels

2019-10-03 Thread Steve Kargl
On Thu, Oct 03, 2019 at 09:17:32AM +0200, Hans Petter Selasky wrote: > On 2019-10-02 23:19, Steve Kargl wrote: > > troutmask.apl.washington.edu dumped core - see /var/crash/vmcore.7 > > > > Wed Oct 2 14:12:38 PDT 2019 > > > > This looks like a simple NULL

radeon panics kernels

2019-10-02 Thread Steve Kargl
troutmask.apl.washington.edu dumped core - see /var/crash/vmcore.7 Wed Oct 2 14:12:38 PDT 2019 FreeBSD troutmask.apl.washington.edu 13.0-CURRENT FreeBSD 13.0-CURRENT r352812 HPC amd64 panic: page fault Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 10 fault virtual

Re: Working ath10k device?

2019-08-21 Thread Steve Kargl
On Wed, Aug 21, 2019 at 10:39:33PM -0400, Anthony Jenkins wrote: > On 8/2/19 6:19 PM, Steve Kargl wrote: > > I have a Dell XPS 13 that reports the wifi chip is > > a Qualcomm Atheros 6147. I've found Adrain's WIP > > driver, and built it. I'm seeing the panic reported

Re: HEADSUP: drm-current-kmod now installs sources

2019-08-14 Thread Steve Kargl
On Wed, Aug 14, 2019 at 06:40:28PM -0400, Daniel Eischen wrote: > I've lost the original thread, but would the sources in > /usr/local/sys/modules get built regardless of what > MAKEOBJDIRPREFIX is? And, now that sources may be installed > by a port, what is the method for _just_ updating the

Re: FUSE Call for Testing

2019-08-08 Thread Steve Kargl
On Thu, Aug 08, 2019 at 12:34:52PM -0600, Alan Somers wrote: > The new FUSE driver has just landed in current. It raises the protocol > level from 7.8 to 7.23, fixes many bugs, adds a test suite for the > driver, and adds many new features. New features include: Thanks for sharing your work! --

Working ath10k device?

2019-08-02 Thread Steve Kargl
I have a Dell XPS 13 that reports the wifi chip is a Qualcomm Atheros 6147. I've found Adrain's WIP driver, and built it. I'm seeing the panic reported at https://lists.freebsd.org/pipermail/freebsd-current/2019-February/072769.html Does anyone have a /dev/if_athp.ko and firmware? -- Steve

Re: drm-legacy is broken, again

2019-08-01 Thread Steve Kargl
On Thu, Aug 01, 2019 at 03:31:15PM -0400, Mark Johnston wrote: > On Thu, Aug 01, 2019 at 12:30:24PM -0700, Steve Kargl wrote: > > On Thu, Aug 01, 2019 at 03:22:27PM -0400, Mark Johnston wrote: > > > On Thu, Aug 01, 2019 at 12:10:09PM -0700, Steve Kargl wrote: > > > >

Re: drm-legacy is broken, again

2019-08-01 Thread Steve Kargl
On Thu, Aug 01, 2019 at 03:22:27PM -0400, Mark Johnston wrote: > On Thu, Aug 01, 2019 at 12:10:09PM -0700, Steve Kargl wrote: > > Just updated /usr/src to top of tree. > > > > Trying to update drm-legacy port. After > > a failed 'make' in /usr/ports/drm-legacy >

drm-legacy is broken, again

2019-08-01 Thread Steve Kargl
Just updated /usr/src to top of tree. Trying to update drm-legacy port. After a failed 'make' in /usr/ports/drm-legacy % make |& tee drm.txt % tail drm.txt ===> drm2/drm2 (all) Warning: Object directory not changed from original

Re: vm_page_hold() and drm-legacy-kmod

2019-07-09 Thread Steve Kargl
On Mon, Jul 08, 2019 at 10:57:41PM -0700, Steve Kargl wrote: > On Tue, Jul 09, 2019 at 01:43:42AM -0400, Mark Johnston wrote: > > On Mon, Jul 08, 2019 at 10:04:00PM -0700, Steve Kargl wrote: > > > > > > This was broken by r349846 committed by markj. > > > &

Re: Someone broke USB

2019-07-09 Thread Steve Kargl
On Tue, Jul 09, 2019 at 10:19:55AM +0200, Niclas Zeising wrote: > On 2019-07-09 06:33, Steve Kargl wrote: > > On Mon, Jul 08, 2019 at 10:54:24PM +0200, Hans Petter Selasky wrote: > >> On 2019-07-08 22:08, Steve Kargl wrote: > >>> On Mon, Jul 08, 2019 at 09:08:17PM +0

Re: vm_page_hold() and drm-legacy-kmod

2019-07-09 Thread Steve Kargl
On Tue, Jul 09, 2019 at 01:43:42AM -0400, Mark Johnston wrote: > On Mon, Jul 08, 2019 at 10:04:00PM -0700, Steve Kargl wrote: > > > > This was broken by r349846 committed by markj. > > Please try this patch. If it works for you I will submit a pull request > to the

Re: vm_page_hold() and drm-legacy-kmod

2019-07-08 Thread Steve Kargl
On Mon, Jul 08, 2019 at 09:43:36PM -0700, Steve Kargl wrote: > On Mon, Jul 08, 2019 at 09:35:05PM -0700, Steve Kargl wrote: > > On Mon, Jul 08, 2019 at 09:31:12PM -0700, Steve Kargl wrote: > > > It seems the recent flurry of vm commits has > > > broken the gr

Re: vm_page_hold() and drm-legacy-kmod

2019-07-08 Thread Steve Kargl
On Mon, Jul 08, 2019 at 09:35:05PM -0700, Steve Kargl wrote: > On Mon, Jul 08, 2019 at 09:31:12PM -0700, Steve Kargl wrote: > > It seems the recent flurry of vm commits has > > broken the graphics/drm-legacy-kmod port. > > vm_page_hold() no longer exists. How

Re: Someone broke USB

2019-07-08 Thread Steve Kargl
On Mon, Jul 08, 2019 at 10:54:24PM +0200, Hans Petter Selasky wrote: > On 2019-07-08 22:08, Steve Kargl wrote: > > On Mon, Jul 08, 2019 at 09:08:17PM +0200, Hans Petter Selasky wrote: > >> Hi Steve, > >> > >> Can you revert all prior patches and try this one

Re: vm_page_hold() and drm-legacy-kmod

2019-07-08 Thread Steve Kargl
On Mon, Jul 08, 2019 at 09:31:12PM -0700, Steve Kargl wrote: > It seems the recent flurry of vm commits has > broken the graphics/drm-legacy-kmod port. > vm_page_hold() no longer exists. How do I > fix the port? > Whoops. The missing function is vm_page_unhold(). Anywho

vm_page_hold() and drm-legacy-kmod

2019-07-08 Thread Steve Kargl
It seems the recent flurry of vm commits has broken the graphics/drm-legacy-kmod port. vm_page_hold() no longer exists. How do I fix the port? -- Steve ___ freebsd-current@freebsd.org mailing list

Re: Someone broke USB

2019-07-08 Thread Steve Kargl
On Mon, Jul 08, 2019 at 09:08:17PM +0200, Hans Petter Selasky wrote: > Hi Steve, > > Can you revert all prior patches and try this one instead. > With the new patch, none of the USB devices are found. I'll be away from the laptop for a few hours. -- Steve

Re: Someone broke USB

2019-07-08 Thread Steve Kargl
On Mon, Jul 08, 2019 at 10:24:14AM -0700, Steve Kargl wrote: > On Mon, Jul 08, 2019 at 07:09:39PM +0200, Hans Petter Selasky wrote: > > On 2019-07-08 19:03, Steve Kargl wrote: > > > On Mon, Jul 08, 2019 at 11:50:31AM +0200, Hans Petter Selasky wrote: > > >> Hi Ste

Re: Someone broke USB

2019-07-08 Thread Steve Kargl
On Mon, Jul 08, 2019 at 07:09:39PM +0200, Hans Petter Selasky wrote: > On 2019-07-08 19:03, Steve Kargl wrote: > > On Mon, Jul 08, 2019 at 11:50:31AM +0200, Hans Petter Selasky wrote: > >> Hi Steve, > >> > >> Can you test this patch? > >> > &g

Re: Someone broke USB

2019-07-08 Thread Steve Kargl
On Mon, Jul 08, 2019 at 11:50:31AM +0200, Hans Petter Selasky wrote: > Hi Steve, > > Can you test this patch? > > I made a slight variant which delay the explore threads instead of the > main thread running all the sysinits. > > --HPS With this patch, the kernel does not find any USB devices.

Re: Someone broke USB

2019-07-07 Thread Steve Kargl
On Sun, Jul 07, 2019 at 10:46:10PM +0200, Hans Petter Selasky wrote: > On 2019-07-07 22:36, Steve Kargl wrote: > > On Sun, Jul 07, 2019 at 09:10:00PM +0200, Hans Petter Selasky wrote: > >> On 2019-07-07 20:58, Steve Kargl wrote: > >>> I assume the pause goes aft

Re: Someone broke USB

2019-07-07 Thread Steve Kargl
On Sun, Jul 07, 2019 at 09:10:00PM +0200, Hans Petter Selasky wrote: > On 2019-07-07 20:58, Steve Kargl wrote: > > I assume the pause goes after "max--;" statement. I also > > assume you want the info with the sysctl removed from > > /boot/loader.conf. > &

Re: Someone broke USB

2019-07-07 Thread Steve Kargl
On Sun, Jul 07, 2019 at 08:27:18PM +0200, Hans Petter Selasky wrote: > On 2019-07-07 18:58, Hans Petter Selasky wrote: > > On 2019-07-07 18:54, Steve Kargl wrote: > >> This a 7720 line, 262KB file, do you want me to send it > >> to you in private email or put in my home

Re: Someone broke USB

2019-07-07 Thread Steve Kargl
On Sun, Jul 07, 2019 at 11:53:27AM +0200, Hans Petter Selasky wrote: > On 2019-07-07 10:05, Steve Kargl wrote: > > On Sat, Jul 06, 2019 at 04:14:53PM -0700, Steve Kargl wrote: > >> On Sat, Jul 06, 2019 at 03:08:13PM -0600, Ian Lepore wrote: > >>> > >>

Re: Someone broke USB

2019-07-07 Thread Steve Kargl
On Sat, Jul 06, 2019 at 04:14:53PM -0700, Steve Kargl wrote: > On Sat, Jul 06, 2019 at 03:08:13PM -0600, Ian Lepore wrote: > > > > It seems almost certain to be r349161 that causes the problem. > > > > I've backed out the change, and the buildkernel is currently

Re: Someone broke USB

2019-07-06 Thread Steve Kargl
On Sat, Jul 06, 2019 at 03:08:13PM -0600, Ian Lepore wrote: > On Sat, 2019-07-06 at 14:06 -0700, Steve Kargl wrote: > > On Sat, Jul 06, 2019 at 10:50:59PM +0200, Hans Petter Selasky wrote: > > > On 2019-07-06 21:41, Steve Kargl wrote: > > > > On Sat, Jul 06, 2019 at

  1   2   3   4   5   6   7   8   9   10   >