Re: Panic in sys_fstatat()

2019-02-15 Thread Steve Kargl
On Fri, Feb 15, 2019 at 09:50:55AM +0200, Andriy Gapon wrote: > > So, I suspect something exotic like some sort of a stack alignment issue, or a > CPU bug, or a mismatch between object files, or some local experiment, etc. > You might be right about something exotic. It is an old laptop, so it

Re: Panic in sys_fstatat()

2019-02-14 Thread Steve Kargl
On Thu, Feb 14, 2019 at 12:47:26PM -0800, John Baldwin wrote: > On 2/14/19 12:38 PM, Steve Kargl wrote: > > On Thu, Feb 14, 2019 at 12:26:01PM -0800, John Baldwin wrote: > >> On 2/13/19 6:47 PM, Steve Kargl wrote: > >>> #16 0x00ff58bb in trap (frame=0x2e7b6880) at

Re: Panic in sys_fstatat()

2019-02-14 Thread Steve Kargl
On Thu, Feb 14, 2019 at 12:26:01PM -0800, John Baldwin wrote: > On 2/13/19 6:47 PM, Steve Kargl wrote: > > #16 0x00ff58bb in trap (frame=0x2e7b6880) at > > /usr/src/sys/i386/i386/trap.c:519 > > #17 0xffc0315d in ?? () > > #18 0x2e7b6880 in ?? () > > #19 0x0

Panic in sys_fstatat()

2019-02-13 Thread Steve Kargl
I have the core file and kernel.debug, if someone wnat additional information. mobile dumped core - see /var/crash/vmcore.0 Wed Feb 13 18:37:44 PST 2019 FreeBSD mobile 13.0-CURRENT FreeBSD 13.0-CURRENT #0 r344034M: Tue Feb 12 08:14:16 PST 2019

Re: drm2 removed?

2019-02-12 Thread Steve Kargl
On Mon, Feb 11, 2019 at 08:20:20AM -0800, Steve Kargl wrote: > On Mon, Feb 11, 2019 at 08:12:05AM -0800, Steve Kargl wrote: > > Anyone have any idea which recent change broke the > > drm-legacy-kmod port. This is why I raised an issue > > with removal of drm2 from src

Re: drm2 removed?

2019-02-11 Thread Steve Kargl
On Mon, Feb 11, 2019 at 06:42:29PM +0100, Niclas Zeising wrote: > > > > The patch allows the port to be built. > > > > kldloading the i915kms module causes a 'black screen > > of death' > > > Hi! > I assume you load the kernel module either manually with kldload or > using kld_list in rc.conf,

Re: drm2 removed?

2019-02-11 Thread Steve Kargl
On Mon, Feb 11, 2019 at 09:01:55PM +, Graham Perrin wrote: > On 11/02/2019 20:42, Steve Kargl wrote: > > > Are you building on i386 or x86_64? > > $ uname -a > FreeBSD momh167-gjp4-8570p 13.0-CURRENT FreeBSD 13.0-CURRENT r343931 > GENERIC-NODEBUG  amd64 amd64

Re: drm2 removed?

2019-02-11 Thread Steve Kargl
On Mon, Feb 11, 2019 at 08:40:01PM +, Graham Perrin wrote: > On 11/02/2019 16:20, Steve Kargl wrote: > > > On Mon, Feb 11, 2019 at 08:12:05AM -0800, Steve Kargl wrote: > > > >> Anyone have any idea which recent change broke the > >> drm-legacy-kmod

Re: drm2 removed?

2019-02-11 Thread Steve Kargl
On Mon, Feb 11, 2019 at 06:42:29PM +0100, Niclas Zeising wrote: > On 2/11/19 6:36 PM, Steve Kargl wrote: > > > > The patch allows the port to be built. > > > > kldloading the i915kms module causes a 'black screen > > of death' > > > > I'll

Re: drm2 removed?

2019-02-11 Thread Steve Kargl
On Mon, Feb 11, 2019 at 06:05:03PM +0100, Niclas Zeising wrote: > On 2/11/19 5:20 PM, Steve Kargl wrote: > > On Mon, Feb 11, 2019 at 08:12:05AM -0800, Steve Kargl wrote: > >> Anyone have any idea which recent change broke the > >> drm-legacy-kmod port. Th

Re: drm2 removed?

2019-02-11 Thread Steve Kargl
On Mon, Feb 11, 2019 at 04:33:24PM +, Johannes Lundberg wrote: > > On 2/11/19 4:23 PM, Niclas Zeising wrote: > > On 2/11/19 5:20 PM, Steve Kargl wrote: > >> On Mon, Feb 11, 2019 at 08:12:05AM -0800, Steve Kargl wrote: > >>> Anyone have any idea which recent

Re: drm2 removed?

2019-02-11 Thread Steve Kargl
On Mon, Feb 11, 2019 at 08:12:05AM -0800, Steve Kargl wrote: > Anyone have any idea which recent change broke the > drm-legacy-kmod port. This is why I raised an issue > with removal of drm2 from src/sys. How is suppose > to be fixed? > It was r343567. The merging of PAE an

drm2 removed?

2019-02-11 Thread Steve Kargl
Anyone have any idea which recent change broke the drm-legacy-kmod port. This is why I raised an issue with removal of drm2 from src/sys. How is suppose to be fixed? --- ttm_bo_manager.o --- cc -O2 -pipe -march=core2 -fno-strict-aliasing -march=core2 -Werror -D_KERNEL -DKLD_MODULE -nostdinc

Re: Updating bugzilla password?

2019-02-04 Thread Steve Kargl
On Mon, Feb 04, 2019 at 10:13:40AM -0800, Enji Cooper wrote: > > > PS: if anyone cares there are 3 patches sitting in freebsd-numerics@. > > Steve, > As some others noted in the private channel, you’ll need > to reset your Kerberos password via these instructions in the > committer’s

Re: Updating bugzilla password?

2019-02-04 Thread Steve Kargl
On Mon, Feb 04, 2019 at 09:39:49AM -0800, Enji Cooper wrote: > > > Let me loop in some other folks. Something might be up with mail forwarding > for your account. > Just sent an email to ka...@freebsd.org. It was forwarded to my local account as expected. Checking /var/log/maillog, I see no

Re: Updating bugzilla password?

2019-02-04 Thread Steve Kargl
On Mon, Feb 04, 2019 at 09:35:45AM -0800, Enji Cooper wrote: > > > Was this for your old FreeBSD.org address, by chance? > Yes. ka...@freebsd.org .forward is set up to send the email on to my local hacking account. -- Steve

Re: Updating bugzilla password?

2019-02-04 Thread Steve Kargl
On Mon, Feb 04, 2019 at 09:15:28AM -0800, Enji Cooper wrote: > > > On Feb 4, 2019, at 08:34, Steve Kargl > > wrote: > > > > I have forgotten my bugzilla account password. I've > > entered the Login: account name, and clicked the > > "Forg

Updating bugzilla password?

2019-02-04 Thread Steve Kargl
I have forgotten my bugzilla account password. I've entered the Login: account name, and clicked the "Forgot Password" button. Expecting to receiving an email that would provide instructions for updating the password. That email never comes. So, is bugzilla broken? Is it impossible to reset

Re: HEADSUP: Something has gone south with -current

2018-12-07 Thread Steve Kargl
On Fri, Dec 07, 2018 at 05:02:03PM -0800, Steve Kargl wrote: > On Sat, Dec 08, 2018 at 02:43:17AM +0200, Konstantin Belousov wrote: > > On Fri, Dec 07, 2018 at 04:25:39PM -0800, Steve Kargl wrote: > > > On Sat, Dec 08, 2018 at 02:08:20AM +0200, Konstantin Belousov wrote: >

Re: HEADSUP: Something has gone south with -current

2018-12-07 Thread Steve Kargl
On Sat, Dec 08, 2018 at 02:43:17AM +0200, Konstantin Belousov wrote: > On Fri, Dec 07, 2018 at 04:25:39PM -0800, Steve Kargl wrote: > > On Sat, Dec 08, 2018 at 02:08:20AM +0200, Konstantin Belousov wrote: > > > > > > Most likely this is an issue fixed by r339350. >

Re: HEADSUP: Something has gone south with -current

2018-12-07 Thread Steve Kargl
On Sat, Dec 08, 2018 at 02:08:20AM +0200, Konstantin Belousov wrote: > On Fri, Dec 07, 2018 at 03:52:33PM -0800, Steve Kargl wrote: > > On Fri, Dec 07, 2018 at 03:30:19PM -0800, Steve Kargl wrote: > > > On Fri, Dec 07, 2018 at 03:06:22PM -0800, Steve Kargl wrote: > > >

Re: HEADSUP: Something has gone south with -current

2018-12-07 Thread Steve Kargl
On Fri, Dec 07, 2018 at 03:52:33PM -0800, Steve Kargl wrote: > On Fri, Dec 07, 2018 at 03:30:19PM -0800, Steve Kargl wrote: > > On Fri, Dec 07, 2018 at 03:06:22PM -0800, Steve Kargl wrote: > > > > > > make core dumps. > > > devd core dumps. > > > init

Re: HEADSUP: Something has gone south with -current

2018-12-07 Thread Steve Kargl
On Fri, Dec 07, 2018 at 03:30:19PM -0800, Steve Kargl wrote: > On Fri, Dec 07, 2018 at 03:06:22PM -0800, Steve Kargl wrote: > > > > make core dumps. > > devd core dumps. > > init core dumps. > > cc core dumps. > > c++ core dumps. > > > &

Re: HEADSUP: Something has gone south with -current

2018-12-07 Thread Steve Kargl
On Fri, Dec 07, 2018 at 06:23:57PM -0500, Shawn Webb wrote: > On Fri, Dec 07, 2018 at 03:06:22PM -0800, Steve Kargl wrote: > > Dell 7510 laptop was happily running FreeBSD12-alpha9 > > from Oct. 10th. I decided to update to top-of-tree > > today, which would be FreeBSD13 at

Re: HEADSUP: Something has gone south with -current

2018-12-07 Thread Steve Kargl
On Fri, Dec 07, 2018 at 03:06:22PM -0800, Steve Kargl wrote: > > make core dumps. > devd core dumps. > init core dumps. > cc core dumps. > c++ core dumps. > > Something seems to be broken. > Further investigation, as core dumps. cpp core dumps.

HEADSUP: Something has gone south with -current

2018-12-07 Thread Steve Kargl
Dell 7510 laptop was happily running FreeBSD12-alpha9 from Oct. 10th. I decided to update to top-of-tree today, which would be FreeBSD13 at r341703. % cd /usr/obj % rm -rf usr % cd ../src % svn update % make -j6 buildwould (OK) % make -j6 buildkernel (OK) % make installkernel(OK) %

Re: ath(4) issues?

2018-11-23 Thread Steve Kargl
receives it fine; then > > * + ath_rate_sample complains that it got a completion for a rate it's not > > supposed to use. > > > > They're harmless. You can comment it out for now; I really need to fix > > ath_rate_sample to use a dynamic table rather than the ar

Re: ath(4) issues?

2018-11-22 Thread Steve Kargl
On Thu, Nov 22, 2018 at 09:05:20AM -0800, Steve Kargl wrote: > I have an old D-Link AirPlus G (DWL-630) pccard card > that I have used for years with FreeBSD. Recently, > I see > > % dmesg | grep ath > mobile:kargl[201] dmesg | grep ath > [ath_hal] loaded > [ath_dfs] lo

ath(4) issues?

2018-11-22 Thread Steve Kargl
I have an old D-Link AirPlus G (DWL-630) pccard card that I have used for years with FreeBSD. Recently, I see % dmesg | grep ath mobile:kargl[201] dmesg | grep ath [ath_hal] loaded [ath_dfs] loaded [ath_rate] loaded [ath] loaded ath0: irq 19 at device 0.0 on cardbus0 ath0: AR2413 mac 7.8 RF2413

Re: Waterfox: shared object "libicui18n.so.62" not found, required by "libxul.so"

2018-10-28 Thread Steve Kargl
On Sun, Oct 28, 2018 at 10:33:31PM +, Graham Perrin wrote: > $ waterfox > XPCOMGlueLoad error for file /usr/local/lib/waterfox/libxul.so: > Shared object "libicui18n.so.62" not found, required by "libxul.so" > Couldn't load XPCOM. > $ date ; uname -v > Sun 28 Oct 2018 22:31:00 GMT > FreeBSD

Re: drm2 in base

2018-09-28 Thread Steve Kargl
On Fri, Sep 28, 2018 at 01:30:59PM -0700, Matthew Macy wrote: > > Bug reports are addressed as they come in. If issues haven't come up > it likely reflects a scarcity of users. > It is likely that -current users are still using drm2 from base (or have sufficiently new hardware that

Re: drm2 in base

2018-09-28 Thread Steve Kargl
On Fri, Sep 28, 2018 at 02:21:24PM -0600, Warner Losh wrote: > On Fri, Sep 28, 2018 at 2:02 PM Steve Kargl < > s...@troutmask.apl.washington.edu> wrote: > > > On Fri, Sep 28, 2018 at 02:47:39PM -0500, Matthew D. Fuller wrote: > > > On Fri, Sep 28, 2018 at 11:0

Re: drm2 in base

2018-09-28 Thread Steve Kargl
On Fri, Sep 28, 2018 at 01:58:26PM -0600, Warner Losh wrote: > On Fri, Sep 28, 2018 at 12:01 PM Steve Kargl < > s...@troutmask.apl.washington.edu> wrote: > > > > > At the risk of raising the ire of others, but with the pending > > branching for FreeBSD 12,

Re: drm2 in base

2018-09-28 Thread Steve Kargl
On Fri, Sep 28, 2018 at 02:47:39PM -0500, Matthew D. Fuller wrote: > On Fri, Sep 28, 2018 at 11:00:02AM -0700 I heard the voice of > Steve Kargl, and lo! it spake thus: > > > > I have a radeon HD 6450 video card (CAICOS firmware), and have been > > informed that

drm2 in base

2018-09-28 Thread Steve Kargl
At the risk of raising the ire of others, but with the pending branching for FreeBSD 12, I respectfully request that drm2 remain in head after the branch. I have a radeon HD 6450 video card (CAICOS firmware), and have been informed that the hardware is too old for graphics/drm-stable-kmod and

Re: LLVM breaks buildworld

2018-09-27 Thread Steve Kargl
On Thu, Sep 27, 2018 at 10:32:35PM +0200, Dimitry Andric wrote: > On 27 Sep 2018, at 22:06, Steve Kargl > wrote: > > > > Hmmm, deleting the file MipsDSPInstrInfo.td seems to flip > > SHRD to SHRL. Oddly, 'svn diff' did not show a diff with > > the corrupt file. :

Re: LLVM breaks buildworld

2018-09-27 Thread Steve Kargl
On Thu, Sep 27, 2018 at 12:39:07PM -0700, Steve Kargl wrote: > On Thu, Sep 27, 2018 at 12:34:39PM -0700, Steve Kargl wrote: > > cd /usr/obj > > rm -f usr > > cd /usr/src > > svn update > > make buildworld > > (wait a long time) > > > > ===> li

Re: LLVM breaks buildworld

2018-09-27 Thread Steve Kargl
On Thu, Sep 27, 2018 at 12:34:39PM -0700, Steve Kargl wrote: > cd /usr/obj > rm -f usr > cd /usr/src > svn update > make buildworld > (wait a long time) > > ===> lib/clang/libllvm (all) > llvm-tblgen -gen-asm-matcher -I /usr/src/contrib/llvm/include -I > /usr

LLVM breaks buildworld

2018-09-27 Thread Steve Kargl
cd /usr/obj rm -f usr cd /usr/src svn update make buildworld (wait a long time) ===> lib/clang/libllvm (all) llvm-tblgen -gen-asm-matcher -I /usr/src/contrib/llvm/include -I /usr/src/contrib/llvm/lib/Target/Mips -d MipsGenAsmMatcher.inc.d -o MipsGenAsmMatcher.inc

Re: ALPHA4 panic in VM

2018-09-19 Thread Steve Kargl
On Wed, Sep 19, 2018 at 05:02:11PM -0400, Mark Johnston wrote: > On Wed, Sep 19, 2018 at 01:01:52PM -0700, Steve Kargl wrote: > > I have the kernel and core file if more information is needed. > > > > % cat info.2 > > Dump header from device: /dev/ada0

ALPHA4 panic in VM

2018-09-19 Thread Steve Kargl
I have the kernel and core file if more information is needed. % cat info.2 Dump header from device: /dev/ada0p3 Architecture: amd64 Architecture Version: 2 Dump Length: 2348281856 Blocksize: 512 Compression: none Dumptime: Wed Sep 19 12:29:59 2018 Hostname:

Re: kldref: unhandled relocation type 2

2018-08-17 Thread Steve Kargl
On Fri, Aug 17, 2018 at 05:50:06PM -0400, Ed Maste wrote: > On 8 August 2018 at 13:27, Warner Losh wrote: > > > >> % /usr/obj/usr/src/i386.i386/usr.sbin/kldxref/kldxref /boot/kernel > >> kldxref: unhandled relocation type 2 > >> (40+ messages...) > > > > > > Oh, wait: relocation type, not module

Re: kldref: unhandled relocation type 2

2018-08-08 Thread Steve Kargl
On Wed, Aug 08, 2018 at 06:27:21PM +0100, Warner Losh wrote: > On Wed, Aug 8, 2018 at 6:19 PM, Steve Kargl < > s...@troutmask.apl.washington.edu> wrote: > > > > Thanks for info. > > > > I'll note that freshly built kldxref gives the same messages. > >

Re: kldref: unhandled relocation type 2

2018-08-08 Thread Steve Kargl
On Wed, Aug 08, 2018 at 06:14:19PM +0100, Warner Losh wrote: > On Wed, Aug 8, 2018 at 5:58 PM, Steve Kargl < > s...@troutmask.apl.washington.edu> wrote: > > > Just build a new world and kernel. Upon doing "make installkernel", > > I see at the end of the

kldref: unhandled relocation type 2

2018-08-08 Thread Steve Kargl
Just build a new world and kernel. Upon doing "make installkernel", I see at the end of the process kldxref /boot/kernel kldxref: unhandled relocation type 2 kldxref: unhandled relocation type 2 kldxref: unhandled relocation type 2 (40 more messages) kldxref: unhandled relocation type 2 The

Re: svn commit: r337340 - in head: [This broke all ci.freebsd.org 's FreeBSD-head-*-build 's, clang based and gcc 4.2.1 based]

2018-08-05 Thread Steve Kargl
On Sat, Aug 04, 2018 at 10:23:56PM -0600, Brad Davis wrote: > On Sat, Aug 4, 2018, at 9:48 PM, Brad Davis wrote: > > On Sat, Aug 4, 2018, at 7:43 PM, Mark Millard wrote: > > > > Author: brd > > > > Date: Sat Aug 4 22:41:17 2018 > > > > New Revision: 337340 > > > > URL: > > > >

Re: [PATCH] Recent libm additions

2018-07-18 Thread Steve Kargl
This is now PR 229876. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229876 -- steve On Mon, Jul 16, 2018 at 08:20:11PM -0700, Steve Kargl wrote: > Version 2. After applying the patch, one can > > % svn delete libm/msun/src/polevll.c > % svn commit libm/msun/src/polevll.

Re: [PATCH] Recent libm additions

2018-07-16 Thread Steve Kargl
Version 2. After applying the patch, one can % svn delete libm/msun/src/polevll.c % svn commit libm/msun/src/polevll.c * lib/msun/Makefile: . Remove polevll.c * lib/msun/ld80/e_powl.c: . Copy contents of polevll.c to here. This is the only consumer of these functions. Make functions

Re: [PATCH] Recent libm additions

2018-07-15 Thread Steve Kargl
On Sun, Jul 15, 2018 at 02:00:37PM -0700, Matthew Macy wrote: > On Sun, Jul 15, 2018 at 12:43 PM, Montgomery-Smith, Stephen > wrote: > > On 07/15/2018 02:09 PM, Warner Losh wrote: > >> I'm not saying that he has a lock. I'm saying he's are domain expert and > >> many mistakes can be avoided by

Re: [PATCH] Recent libm additions

2018-07-15 Thread Steve Kargl
On Sun, Jul 15, 2018 at 02:00:37PM -0700, Matthew Macy wrote: > On Sun, Jul 15, 2018 at 12:43 PM, Montgomery-Smith, Stephen > wrote: > > On 07/15/2018 02:09 PM, Warner Losh wrote: > >> I'm not saying that he has a lock. I'm saying he's are domain expert and > >> many mistakes can be avoided by

Re: [PATCH] Recent libm additions

2018-07-15 Thread Steve Kargl
On Sun, Jul 15, 2018 at 12:23:06PM -0700, Cy Schubert wrote: > I wasn't saying Steve has a lock however in case non-committers > might feel they do, addressing all points in my reply. Not saying > anyone feels this way today but we should consider this in whatever > we decide here (considering all

Re: [PATCH] Recent libm additions

2018-07-15 Thread Steve Kargl
On Sun, Jul 15, 2018 at 10:44:28AM -0700, Matthew Macy wrote: > > In the bug report you cite, Chris Lattner states: "This is actually an > unspecified feature of C99 (whether it supports the _Imaginary type). > It is desirable to support this, but not a regression. > Chris Lattner is wrong when

Re: [PATCH] Recent libm additions

2018-07-15 Thread Steve Kargl
On Sun, Jul 15, 2018 at 12:06:47PM -0600, Ian Lepore wrote: > > On the other hand, what information is there for someone to know that > Steve should be involved in a review? There is nothing in MAINTAINERS. > The review was on phab for almost a month, and phab is supposedly the > preferred way to

Re: [PATCH] Recent libm additions

2018-07-15 Thread Steve Kargl
On Sun, Jul 15, 2018 at 10:21:25AM -0700, K. Macy wrote: > > > > Well, actually, the functions in polevll.c should have been copied > > into ld80/e_powl.c, and polevall.c should never have been committed. > > Unfortunately, the code was not reviewed for correctness. > > That is not correct.

Re: [PATCH] Recent libm additions

2018-07-15 Thread Steve Kargl
On Sun, Jul 15, 2018 at 11:00:41AM -0600, Ian Lepore wrote: > On Sun, 2018-07-15 at 08:06 -0700, Steve Kargl wrote: > > Index: ld80/e_powl.c > > === > > --- ld80/e_powl.c (revision 336304) > > +++ ld

[PATCH] Recent libm additions

2018-07-15 Thread Steve Kargl
Apparently, the recents additions to libm were not subject to any code review. The following patch does two things. First, it works around https://bugs.llvm.org/show_bug.cgi?id=8532 Second, it removes the pollution of libm with the polevll.c functions. Those functions are used only in

Re: numa involved in instability and swap usage despite RAM free?

2018-06-26 Thread Steve Kargl
On Tue, Jun 26, 2018 at 02:39:27PM -0700, Adrian Chadd wrote: > On Mon, 25 Jun 2018 at 11:23, Steve Kargl > wrote: > > > > On Sun, Jun 24, 2018 at 12:03:29PM +0200, Alexander Leidinger wrote: > > > > > > I don't have hard evidence, but there is enough &

Re: numa involved in instability and swap usage despite RAM free?

2018-06-25 Thread Steve Kargl
On Sun, Jun 24, 2018 at 12:03:29PM +0200, Alexander Leidinger wrote: > > I don't have hard evidence, but there is enough "smell" to open up a > discussion... > > Short: > Can it be that enabling numa in the kernel is the reason why some > people see instability with zfs and usage of swap

Re: Is kern.sched.preempt_thresh=0 a sensible default?

2018-06-09 Thread Steve Kargl
On Sat, Jun 09, 2018 at 06:07:15PM -0700, Don Lewis wrote: > On 9 Jun, Stefan Esser wrote: > > > 3) Programs that evenly split the load on all available cores have been > >suffering from sub-optimal assignment of threads to cores. E.g. on a > >CPU with 8 (virtual) cores, this resulted in

Re: how to deal with variable set but not used warnings?

2018-06-03 Thread Steve Kargl
On Sun, Jun 03, 2018 at 09:28:47PM +, Rick Macklem wrote: > mmacy has sent me a bunch of warnings of the "variable set but not used" kind > generated by gcc8. > > When I've looked at the code, these are for RPC arguments I parse but do not > use at this time. > I'd like to leave the code in

Re: hwpmc - wither ppro and p4

2018-05-31 Thread Steve Kargl
On Thu, May 31, 2018 at 03:23:56PM -0500, Mark Linimon wrote: > On Thu, May 31, 2018 at 12:58:23PM -0700, Steve Kargl wrote: > > On Thu, May 31, 2018 at 11:08:18AM -0700, Matthew Macy wrote: > > > > > > Based on the i386 discussion I recognize that there's a grea

Re: hwpmc - wither ppro and p4

2018-05-31 Thread Steve Kargl
On Thu, May 31, 2018 at 11:08:18AM -0700, Matthew Macy wrote: > > Based on the i386 discussion I recognize that there's a great deal of > sentimental attachment to older hardware. However, there's very few s/sentimental/practical -- Steve ___

Re: [RFC] Deprecation and removal of the drm2 driver

2018-05-22 Thread Steve Kargl
On Tue, May 22, 2018 at 04:32:39PM -0700, K. Macy wrote: > Why are you running i386 on that? > I'm not. Just pointing out that drm2 runs on amd64 as well as i386. Also need to correct the dis-information that drm2 only applies to mid-Haswell and older. In the end, src committers will do what

Re: [RFC] Deprecation and removal of the drm2 driver

2018-05-22 Thread Steve Kargl
On Tue, May 22, 2018 at 07:50:39AM +0100, Johannes Lundberg wrote: > On Mon, May 21, 2018 at 23:50 Steve Kargl <s...@troutmask.apl.washington.edu> > wrote: > > > On Mon, May 21, 2018 at 03:20:49PM -0700, K. Macy wrote: > > > > > > > > I just ask. &g

Re: [RFC] Deprecation and removal of the drm2 driver

2018-05-22 Thread Steve Kargl
On Tue, May 22, 2018 at 02:56:55PM -0700, K. Macy wrote: > > > > > > it makes me giggle that people still think non-amd64 is "legacy". > > > > i386 is alive and well - new chips are being fabbed based on the 586 > > design with pci-e slots; not to mention things like the Talos and > > AmigaOne for

Re: [RFC] Deprecation and removal of the drm2 driver

2018-05-21 Thread Steve Kargl
On Mon, May 21, 2018 at 03:20:49PM -0700, K. Macy wrote: > > > > I just ask. > > Or why not include drm-next to base svn repo and add some > > option to make.conf to swith drm2/dem-next ? > > Even if it's not being built on amd64 we're still responsible for > keeping it building on !amd64 so long

Re: [RFC] Deprecation and removal of the drm2 driver

2018-05-21 Thread Steve Kargl
On Mon, May 21, 2018 at 01:16:12PM -0700, K. Macy wrote: > On Mon, May 21, 2018 at 10:07 AM, Steve Kargl > <s...@troutmask.apl.washington.edu> wrote: > > On Mon, May 21, 2018 at 02:40:50AM +0300, Rozhuk Ivan wrote: > >> On Sun, 20 May 2018 21:10:28 +0200 >

Re: [RFC] Deprecation and removal of the drm2 driver

2018-05-21 Thread Steve Kargl
On Mon, May 21, 2018 at 10:29:54AM -0700, Pete Wright wrote: > > On 05/21/2018 10:07, Steve Kargl wrote: > > On Mon, May 21, 2018 at 02:40:50AM +0300, Rozhuk Ivan wrote: > >> On Sun, 20 May 2018 21:10:28 +0200 > >> Oliver Pinter <oliver.pin...@harden

Re: [RFC] Deprecation and removal of the drm2 driver

2018-05-21 Thread Steve Kargl
On Mon, May 21, 2018 at 02:40:50AM +0300, Rozhuk Ivan wrote: > On Sun, 20 May 2018 21:10:28 +0200 > Oliver Pinter wrote: > > > > One of the reasons for the deprecation and removal of the drm2 bits > > > is that they prevent us from automatically loading the > > >

Re: [RFC] Deprecation and removal of the drm2 driver

2018-05-20 Thread Steve Kargl
On Sun, May 20, 2018 at 06:47:07PM +0200, Niclas Zeising wrote: > On 05/20/18 18:40, Steve Kargl wrote: > > On Fri, May 18, 2018 at 02:03:32PM -0600, Warner Losh wrote: > >> On Fri, May 18, 2018 at 1:30 PM, Steve Kargl < > >>> > >>> % mo

Re: [RFC] Deprecation and removal of the drm2 driver

2018-05-20 Thread Steve Kargl
On Fri, May 18, 2018 at 02:03:32PM -0600, Warner Losh wrote: > On Fri, May 18, 2018 at 1:30 PM, Steve Kargl < > s...@troutmask.apl.washington.edu> wrote: > > > On Fri, May 18, 2018 at 09:14:24PM +0200, Andreas Nilsson wrote: > > > On Fri, May 18, 2018, 20:00 Nicla

Re: [RFC] Deprecation and removal of the drm2 driver

2018-05-18 Thread Steve Kargl
On Fri, May 18, 2018 at 02:03:32PM -0600, Warner Losh wrote: > On Fri, May 18, 2018 at 1:30 PM, Steve Kargl < > s...@troutmask.apl.washington.edu> wrote: > > > Check the Makefiles > > > > % more /usr/ports/graphics/drm-next-kmod/Makefile > > > > ON

Re: [RFC] Deprecation and removal of the drm2 driver

2018-05-18 Thread Steve Kargl
On Fri, May 18, 2018 at 09:14:24PM +0200, Andreas Nilsson wrote: > On Fri, May 18, 2018, 20:00 Niclas Zeising wrote: > > > I propose that we remove the old drm2 driver (sys/dev/drm2) from > > FreeBSD. I suggest the driver is marked as deprecated in 11.x and > > removed from

Re: Runtime loader issue

2018-05-10 Thread Steve Kargl
On Wed, May 09, 2018 at 04:45:51PM -0700, Steve Kargl wrote: > In review PR 228007, it came to my attention some individuals are > mis-characterizing a FreeBSD loader issue as "gfortran's FreeBSD > issue". See It seems we've had the same discussion 2 years ago. M

Re: Runtime loader issue

2018-05-10 Thread Steve Kargl
On Thu, May 10, 2018 at 06:21:51PM +0200, Tijl Coosemans wrote: > On Wed, 9 May 2018 16:45:51 -0700 Steve Kargl > <s...@troutmask.apl.washington.edu> wrote: > > > > So, the runtime loader finds 6 instead of 716, tries to link, > > fails, and issues an error mes

Re: Runtime loader issue

2018-05-10 Thread Steve Kargl
On Thu, May 10, 2018 at 10:24:52AM -0400, Diane Bruce wrote: > On Thu, May 10, 2018 at 10:46:31AM +0300, Gleb Popov wrote: > > On Thu, May 10, 2018 at 2:45 AM, Steve Kargl < > > s...@troutmask.apl.washington.edu> wrote: > > > > > In review PR 228007, it c

Runtime loader issue

2018-05-09 Thread Steve Kargl
In review PR 228007, it came to my attention some individuals are mis-characterizing a FreeBSD loader issue as "gfortran's FreeBSD issue". See https://lists.freebsd.org/pipermail/freebsd-fortran/2018-May/000124.html The problem can be summarized by the following % gfortran7 -o z h.f90 % ./z

Re: clang manual page?

2018-04-06 Thread Steve Kargl
On Fri, Apr 06, 2018 at 01:25:54PM +0200, Dimitry Andric wrote: > Yes, but that manual is also pretty much incomplete, so with the last > import I decided to stay with the older perl doc based one. Upstream > is pretty bad at writing detailed documentation, certainly in the form > of man pages. >

Re: clang manual page?

2018-04-06 Thread Steve Kargl
On Fri, Apr 06, 2018 at 06:20:41AM +0100, David Chisnall wrote: > On 6 Apr 2018, at 01:30, Pete Wright <p...@nomadlogic.org> wrote: > > > > > > On 04/05/2018 17:15, Steve Kargl wrote: > >> This assumes that a gcc(1) is available on the system. > >>

Re: clang manual page?

2018-04-05 Thread Steve Kargl
On Thu, Apr 05, 2018 at 08:11:50PM -0500, Benjamin Kaduk wrote: > On Thu, Apr 05, 2018 at 05:56:24PM -0700, Steve Kargl wrote: > > I never said that you said it was in base. I'm noting that > > referring a user to a non-existent manual page is of little > > help. In fact,

Re: clang manual page?

2018-04-05 Thread Steve Kargl
, Conrad Meyer wrote: > I never said it was in base. > > On Thu, Apr 5, 2018 at 5:15 PM, Steve Kargl > <s...@troutmask.apl.washington.edu> wrote: > > This assumes that a gcc(1) is available on the system. > > > > % man gcc > > No manual entry for gcc >

Re: clang manual page?

2018-04-05 Thread Steve Kargl
On Thu, Apr 05, 2018 at 05:30:04PM -0700, Pete Wright wrote: > > > On 04/05/2018 17:15, Steve Kargl wrote: > > This assumes that a gcc(1) is available on the system. > > > > % man gcc > > No manual entry for gcc > > > > If the system compiler is clan

Re: clang manual page?

2018-04-05 Thread Steve Kargl
c(1). > > Conrad > > On Thu, Apr 5, 2018 at 3:38 PM, Steve Kargl > <s...@troutmask.apl.washington.edu> wrote: > > Is anyone working on fixing the clang manual to actually > > document the available options? > > > > % man clang > > (search for -std=) &

clang manual page?

2018-04-05 Thread Steve Kargl
Is anyone working on fixing the clang manual to actually document the available options? % man clang (search for -std=) -std= Specify the language standard to compile for. OK, what does mean? -- Steve ___

Re: Can't load linux64.ko module

2018-04-04 Thread Steve Kargl
On Wed, Apr 04, 2018 at 02:13:15PM -0700, Steve Kargl wrote: > > OK, so where is elf64_linux_vdso_fixup suppose to come from? > The answer is compat/linux/linux_vdso.c where we find #if defined(__i386__) || (defined(__amd64__) && defined(COMPAT_LINUX32)) #define __ELF_W

Re: Can't load linux64.ko module

2018-04-04 Thread Steve Kargl
On Wed, Apr 04, 2018 at 01:19:55PM -0700, Steve Kargl wrote: > On Wed, Apr 04, 2018 at 12:09:02PM -0700, Steve Kargl wrote: > > > > kernel config file contains > > > > options COMPAT_LINUX32 > > options COMPAT_LINUXKPI > > options

Re: Can't load linux64.ko module

2018-04-04 Thread Steve Kargl
On Wed, Apr 04, 2018 at 12:09:02PM -0700, Steve Kargl wrote: > > kernel config file contains > > options COMPAT_LINUX32 > options COMPAT_LINUXKPI > options LINPROCFS > > When booting, the kernel tries to load the module. A manual > lo

Re: Can't load linux64.ko module

2018-04-04 Thread Steve Kargl
On Wed, Apr 04, 2018 at 02:41:35PM -0400, Ed Maste wrote: > On 3 April 2018 at 12:26, Steve Kargl <s...@troutmask.apl.washington.edu> > wrote: > > Booting a kernel from > > % uname -a > > FreeBSD sleepdirt 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r331370: \ >

Can't load linux64.ko module

2018-04-03 Thread Steve Kargl
Booting a kernel from % uname -a FreeBSD sleepdirt 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r331370: \ Thu Mar 22 13:41:30 AKDT 2018 \ kargl@sleepdirt:/usr/obj/usr/src/amd64.amd64/sys/SLEEPDIRT amd64 gives the following from dmesg % dmesg | grep linux link_elf_obj: symbol

Re: kldxref: ...: Bad address.

2018-01-26 Thread Steve Kargl
On Fri, Jan 26, 2018 at 07:25:51AM -0800, Steve Kargl wrote: > On Fri, Jan 26, 2018 at 10:28:13PM +0900, Tomoaki AOKI wrote: > > Hi. > > Try `make install` in /usr/src/usr.sbin/kldxref BEFORE > > `make installkernel`. (Backup kldxref for safety.) > > > > Tha

Re: kldxref: ...: Bad address.

2018-01-26 Thread Steve Kargl
On Fri, Jan 26, 2018 at 10:28:13PM +0900, Tomoaki AOKI wrote: > Hi. > Try `make install` in /usr/src/usr.sbin/kldxref BEFORE > `make installkernel`. (Backup kldxref for safety.) > Thanks! This at least allowed 'make installkernel' to finish cleanly. Now, outward to rebooting ... -- Steve

kldxref: ...: Bad address.

2018-01-25 Thread Steve Kargl
This can't be good. make buildworld make buildkernel make installkernel ... ===> zlib (install) install -T release -o root -g wheel -m 555 zlib.ko /boot/kernel/ install -T debug -o root -g wheel -m 555 zlib.ko.debug /usr/lib/debug/boot/kernel/ kldxref /boot/kernel kldxref: error while

Wedge system == lost files

2018-01-25 Thread Steve Kargl
So, my system just wedge itself. No panic. No keyboard. No mouse. No remote login. Nothing. Just wedged. The system is FreeBSD 12.0-CURRENT r326432 Fri Dec 1 2017 amd64. Imagine my surprise when I rebooted system and the file I had been editing (and saving after every change) is gone.

Re: inconsistent for() and while() behavior when using floating point

2018-01-15 Thread Steve Kargl
On Mon, Jan 15, 2018 at 08:38:15PM +0300, Mehmet Erol Sanliturk wrote: > > When you perform floating point computations , it may be useful > to ... read David Goldberg's paper, "What Every Computer Scientist Should Know about Floating-Point Arithmetic." http://www.validlab.com/ -- Steve

Re: LLD: man pages missing?

2017-12-25 Thread Steve Kargl
On Mon, Dec 25, 2017 at 09:16:24PM +0100, O. Hartmann wrote: > > Can someone help? > There isn't a lld.1 manpage. grep MAN /usr/src/usr.bin/clang/lld/Makefile MAN= google 'man lld' eventually get one to https://lld.llvm.org/#using-lld which leads one to assume that there is no documentation

Re: Poll: should man(1)'s default pager change to "less -s"?

2017-12-12 Thread Steve Kargl
On Tue, Dec 12, 2017 at 10:41:49AM -0800, Conrad Meyer wrote: > On Tue, Dec 12, 2017 at 10:27 AM, Steve Kargl > <s...@troutmask.apl.washington.edu> wrote: > > There isn't a question. I'm pointing out your poll apparently > > is limited to a select few individuals that use

Re: Poll: should man(1)'s default pager change to "less -s"?

2017-12-12 Thread Steve Kargl
On Tue, Dec 12, 2017 at 11:19:21AM -0700, Alan Somers wrote: > On Tue, Dec 12, 2017 at 11:15 AM, Steve Kargl < > s...@troutmask.apl.washington.edu> wrote: > > > On Tue, Dec 12, 2017 at 11:03:54AM -0700, Alan Somers wrote: > > > Should man(1)'s default pager change

Re: Poll: should man(1)'s default pager change to "less -s"?

2017-12-12 Thread Steve Kargl
On Tue, Dec 12, 2017 at 11:03:54AM -0700, Alan Somers wrote: > Should man(1)'s default pager change to "less -s"? Vote and flame at the > Phabricator link below. > > https://reviews.freebsd.org/V7 > Does not work. Unhandled Exception ("AphrontMalformedRequestException") Your browser did not

Re: [PATCH] Document powl and tgammal kludges

2017-12-10 Thread Steve Kargl
On Sun, Dec 10, 2017 at 05:44:33PM +0100, Dimitry Andric wrote: > On 9 Dec 2017, at 02:02, Steve Kargl <s...@troutmask.apl.washington.edu> > wrote: > > > > The following patch documents the remaining kludges that > > theraven@ committed in r255294 on 2013-09-

[PATCH] Document powl and tgammal kludges

2017-12-08 Thread Steve Kargl
The following patch documents the remaining kludges that theraven@ committed in r255294 on 2013-09-06. I have cleaned up all of the others, but powl and tgammal remain. ngie@ seems to have documented the existence of powl with r290605, but did not document the rather poor numerical accuracy of

  1   2   3   4   5   6   7   8   9   10   >