Re: repeatable panic on pageout with 945GM

2016-06-04 Thread Matthew Macy
> > I believe that this is a bug in amd64 pmap. Fictitious pages are not > promoted, in particular, the pv_table array does not span over the > dynamically registered fictitious ranges. As result, pa_to_pvh() returns > garbage and pvh must not be accessed in the case of 'small_mappings'

Re: repeatable panic on pageout with 945GM

2016-06-02 Thread Matthew Macy
> > Slight variation -won't build as above; trying with "pmap_page_is_mapped(m)" > Oops copy pasta + serious fatigue. But you got the right idea. -M ___ freebsd-current@freebsd.org mailing list

Re: repeatable panic on pageout with 945GM

2016-06-02 Thread Matthew Macy
Tell me if that makes any difference. -M On Thu, 02 Jun 2016 16:55:53 -0700 K. Macy wrote > It looks like it might be trying to remove mappings for a page that doesn't > have any. It's a bit odd. Likely a bug in cdev_pager_free_page or gem > release mmap.

Re: VirtualBox network connectivity broken on recent -CURRENT

2016-06-04 Thread Matthew Macy
On Sat, 04 Jun 2016 19:04:42 -0700 Randy Westlund wrote > On Fri, Jun 03, 2016 at 05:11:24PM -0700, Don Lewis wrote: > > It looks like something changed in -CURRENT to break network > > connectivity to VirtualBox guests. This was last known to work with

Re: PostgreSQL performance on FreeBSD

2016-06-03 Thread Matthew Macy
> >>> A couple small steps have been taken toward eliminating the need for > >>> this > >>> hack: the addition of the "page size index" field to struct vm_page and > >>> the > >>> addition of a similarly named parameter to pmap_enter(). However, at > >>> the > >>> moment, the only

latest memstick image fails to mountroot by default on Thinkpad e565

2016-06-03 Thread Matthew Macy
In order to boot USB reliably on recent laptop hardware (both my thinkpad and XPS13 need this) you need to add the following to the installer images loader.conf: kern.cam.boot_delay="1" kern.cam.scsi_delay="3000" ___ freebsd-current@freebsd.org

Re: HWPMC on SkyLake

2016-06-14 Thread Matthew Macy
I think rrs@ may have done it.Randall? On Tue, 14 Jun 2016 08:06:55 -0700 Doug Rabson wrote Did you get any feedback on this? I would like to be able to use hwpmc but my desktop is a recent skylake and I also get the 'hwpc_core: unknown

Re: Kqueue races causing crashes

2016-06-15 Thread Matthew Macy
You can use dwarf4 if you use GDB from ports  On Wed, 15 Jun 2016 04:50:00 -0700 Peter Holm wrote On Wed, Jun 15, 2016 at 11:11:43AM +0300, Konstantin Belousov wrote: > On Tue, Jun 14, 2016 at 10:26:14PM -0500, Eric Badger wrote: > > I

Re: repeatable panic on pageout with 945GM

2016-06-04 Thread Matthew Macy
> > This "band-aid" seems to have worked. I haven't had a single panic since > - Thanks! :-) > > I tried to compile with -O0 but, for some reason, it panics in the sound > driver with a double-fault. When I get time, I'll recompile only the > files involved and see if I can't

Re: latest memstick image fails to mountroot by default on Thinkpad e565

2016-06-04 Thread Matthew Macy
On Sat, 04 Jun 2016 06:03:49 -0700 Edward Tomasz Napierała <tr...@freebsd.org> wrote > Dnia 04.06.2016 o godz. 07:52 Matthew Macy <mm...@nextbsd.org> napisał(a): > > > > > In order to boot USB reliably on recent laptop hardware (both my

Re: CFT update day 2

2016-05-28 Thread Matthew Macy
> > On May 26, 2016, at 19:08, Eric McCorkle <e...@metricspace.net> wrote: > > > > Letting you know, I had an error in detection. I'm trying to get a change > > done before code slush, but I will circle back and provide a detailed > > report

Re: r300951 make buildworld duration 18h

2016-05-30 Thread Matthew Macy
On Mon, 30 May 2016 07:37:26 -0700 Matthias Apitz wrote > > Hello, > > Yesterday I pulled via svn co ... a fresh r300951 and started the buildworld > as > > # make -j2 buildworld > > it ended today at lunchtime after 18 hours. The laptop has 2x

Re: CFT update day 2

2016-05-26 Thread Matthew Macy
g to make slush for the changes to sys to support this. If dates are interpreted as being UTC then it's already started. -M > > On May 23, 2016 4:12:52 AM EDT, Matthew Macy <mm...@nextbsd.org> wrote: > > > >The highlights for today are the following: > > &

Re: Kqueue races causing crashes

2016-06-15 Thread Matthew Macy
On Wed, 15 Jun 2016 10:45:24 -0700 Konstantin Belousov <kostik...@gmail.com> wrote > On Wed, Jun 15, 2016 at 10:39:42AM -0700, Matthew Macy wrote: > > > > > > > > > > You can use dwarf4 if you u

Skylake PMC support?

2016-06-27 Thread Matthew Macy
Does anyone have PMC patches for Skylake? Thanks in advance. -M ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Mapping drm's OBJT_DEFAULT causes crash on munmap

2016-06-26 Thread Matthew Macy
Clicking 2 times on the following WebGL demo will cause a panic using drm 3.8/4.6 (this particular usage of OBJT_DEFAULT is one of the few remaining pieces of shared code). http://myshards.com/ This is the backtrace from HEAD as of f1bd70502f890a8668985030c0aecc3aeacb10ac running the

Re:CFT update day 2

2016-05-23 Thread Matthew Macy
x_insert: key 33 is already present: > > http://sw.gddsn.org.cn/freebsd/drm-4.6-next-panic.jpg That should be easy to fix. However, I wont have time to get to it for a day or two. Could you please file a PR and assign it to me? I think that I can have that fixed by the next update. -

Re: Note on filing bugs found in the CFT

2016-05-24 Thread Matthew Macy
On Tue, 24 May 2016 13:30:12 -0700 Matthew Macy <mm...@nextbsd.org> wrote > > I had previously told testers to file bugs in bugzilla. But the sheer > numbers that are already there make it a bit heavyweight. In the future > please file issues in the gi

Re: CFT update day 2

2016-05-23 Thread Matthew Macy
before trying to start Xorg - there are some rendering issues (pink lines, weird transparency where there should be no transparency), but I don't know if these are related to i915, the experimental xf86-video-intel driver or the software renderer On 2016-05-23 10:12, Matthew Macy

Re: CFT update day 2

2016-05-23 Thread Matthew Macy
omething similar missing, I may try patching them in tomorrow if I can find out what exactly is missing. On 2016-05-23 23:21, Matthew Macy wrote: > Have you tried with the xf86-intel in ports. That actually works > better for most. Also try SNA. What does pciconf -lvbc show for > graphi

Re: CFT update day 2

2016-05-23 Thread Matthew Macy
morrow if I can find out what exactly is > missing. Try working with the ports people. The module load and missing pciids are a ports problem. The outputs not working and visual artifacts are mine. -M > On 2016-05-23 23:21, Matthew Macy wrote: > > Have you tried w

Re: pkg chroot issues?

2016-05-22 Thread Matthew Macy
On Sun, 22 May 2016 13:43:13 -0700 Tim Kientzle wrote > > > On May 22, 2016, at 1:28 PM, K. Macy wrote: > > > > > > > > On Sunday, May 22, 2016, Tim Kientzle wrote: > > Crochet has some experimental hooks

Note on CFT image

2016-05-22 Thread Matthew Macy
On Sun, 22 May 2016 11:27:28 -0700 Matthew Macy <mm...@nextbsd.org> wrote > To improve the user experience I disabled debug logging by default. Before > reporting a non-fatal error with i915 load the drm2 module first, then: > sysctl dev.drm.drm_debug=-1

Update on CFT error reporting

2016-05-22 Thread Matthew Macy
To improve the user experience I disabled debug logging by default. Before reporting a non-fatal error with i915 load the drm2 module first, then: sysctl dev.drm.drm_debug=-1 to enable full logging. Once you have done that you can then load i915. The "unimplemented" and "dodgy" warnings are

4.6 DRM/i915 update CFT (Sandy Bridge?)/IvyBridge/Haswell/Broadwell/SkyLake/KabyLake supported

2016-05-22 Thread Matthew Macy
I'm happy to announce a call for testers for the 4.6 update of drm and i915. The driver has been successfully tested on IvyBridge, Haswell, Broadwell and Skylake. At least basic HW 3D acceleration should work, VGA and DP out are known to work. Video decode has only been tried once and that did

Re: CFT update day 2

2016-05-23 Thread Matthew Macy
> > And as a reminder, if you're having problems with X on the USB > key, try disabling it by moving /etc/X11/xorg.conf.d/20-intel.conf > somewhere else on your file system. This change switches from SNA to UXA which may fix problems for some. > > If using the github repo, make

CFT update day 2

2016-05-23 Thread Matthew Macy
The highlights for today are the following: Bug fixes: - Will Andrews fixed attach for some laptops (such as the Carbon X1). The Carbon X1 has a quirky BIOS that doesn't allow the OS to enumerate the GPU's interrupt. - Will Andrews identified a conditionally uninitialized return in

4.6 DRM/i915 update CFT (Sandy Bridge?)/IvyBridge/Haswell/Broadwell/SkyLake/KabyLake supported

2016-05-22 Thread Matthew Macy
I'm happy to announce a call for testers for the 4.6 update of drm and i915. The driver has been successfully tested on IvyBridge, Haswell, Broadwell and Skylake. At least basic HW 3D acceleration should work, VGA and DP out are known to work. Video decode has only been tried once and that did

Note on filing bugs found in the CFT

2016-05-24 Thread Matthew Macy
I had previously told testers to file bugs in bugzilla. But the sheer numbers that are already there make it a bit heavyweight. In the future please file issues in the github issue tracker for our repo. Thanks. -M ___ freebsd-current@freebsd.org

drm-4.7-rc1 tagged

2016-08-12 Thread Matthew Macy
A few days ago I branched drm-next-4.6 in to drm-next and synced it with Torvalds' tree as of the v4.6 tag. I then integrated the ~800 commits to drm / i915 / radeon / amdgpu , testing periodically along the way and updating the linuxkpi as needed. I've just tagged the drm-next branch with

drm-4.7-final tagged - CFT for drm-next was Re: drm-4.7-rc1 tagged

2016-08-13 Thread Matthew Macy
corruption, but requires the use of a compositor to avoid tearing to keep frame updates in sync with screen refresh. The scope of my personal testing is limited so please report any regressions with respect to drm-next-4.6. On Fri, 12 Aug 2016 00:21:02 -0700 Matthew Macy <mm...@nextbsd.

Re: Wayland work status

2016-08-13 Thread Matthew Macy
> > ​Wayland relies on kqueue which is not implemented in drm's 3.8 or 4.6 > branches. I'm working on this now for drm-next-4.6 and it is almost > complete. > I will probably implement it also in the 3.8 ​branch to be able to run > Wayland on both to compare and find bugs in linuxkpi more

Re: difference in SIGCHLD behavior between Linux and FreeBSD breaks apt

2016-07-18 Thread Matthew Macy
On Mon, 18 Jul 2016 16:11:53 -0700 Alfred Perlstein <alf...@freebsd.org> wrote > I believe the > > > On 7/6/16 9:34 PM, Matthew Macy wrote: > > As a first step towards managing linux user space in a chrooted > > /compat/linux, initially f

Re: callout_drain either broken or man page needs updating

2016-07-15 Thread Matthew Macy
On Fri, 15 Jul 2016 01:43:03 -0700 Gleb Smirnoff <gleb...@freebsd.org> wrote > On Thu, Jul 14, 2016 at 10:14:46PM -0700, Matthew Macy wrote: > M> > On 07/15/16 05:45, Matthew Macy wrote: > M> > > glebius last commit needs some further re-work.

Re: 4.6 DRM/i915 update CFT (Sandy Bridge?)/IvyBridge/Haswell/Broadwell/SkyLake/KabyLake supported

2016-07-15 Thread Matthew Macy
> > > > ___ > > freebsd-current@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" > > When is a Broadwell support

Re: RoCE v2 on FreeBSD

2016-07-15 Thread Matthew Macy
On Thu, 14 Jul 2016 10:31:40 -0700 David Somayajulu wrote > Hi All, > Does FreeBSD support RoCE v2 ? > Thanks > David S. FreeBSD has OFED support. Does OFED support RoCE v2? -M ___

Re: refcnt 0 on LLE at boot....

2016-07-14 Thread Matthew Macy
On Thu, 07 Jul 2016 06:36:19 -0700 Larry Rosenman wrote > Thanks for that. I've added myself to the cc list, and a comment about > having 2 vmcore's. > This was introduced by 302350. It broke the return value of callout_{stop,drain}. returning 1 even if

Re: callout_drain either broken or man page needs updating

2016-07-14 Thread Matthew Macy
On Thu, 14 Jul 2016 21:21:57 -0700 Hans Petter Selasky <h...@selasky.org> wrote > On 07/15/16 05:45, Matthew Macy wrote: > > glebius last commit needs some further re-work. > > Hi, > > Glebius commit needs to be backed out, at least the A

callout_drain either broken or man page needs updating

2016-07-14 Thread Matthew Macy
Upon updating my drm-next branch to the latest -CURRENT callout_drain returning no longer means that the function was in fact pending when it was called. This little bit of code will panic because dwork->wq is NULL, because the callout was _not_ in fact enqueued. So either it's no longer

Re: panic with tcp timers

2016-06-28 Thread Matthew Macy
You guys should really look at Samy Bahra's epoch based reclamation. I solved a similar problem in drm/linuxkpi using it. -M On Tue, 28 Jun 2016 02:58:56 -0700 Julien Charbon wrote > > Hi Randall, > > On 6/25/16 4:41 PM, Randall Stewart via freebsd-net

EBR fix for life cycle races was Re: panic with tcp timers

2016-06-29 Thread Matthew Macy
On Tue, 28 Jun 2016 15:51:57 -0700 K. Macy <km...@freebsd.org> wrote > On Tue, Jun 28, 2016 at 10:51 AM, Matthew Macy <mm...@nextbsd.org> wrote: > > You guys should really look at Samy Bahra's epoch based reclamation. I > > solved a similar pr

difference in SIGCHLD behavior between Linux and FreeBSD breaks apt

2016-07-06 Thread Matthew Macy
As a first step towards managing linux user space in a chrooted /compat/linux, initially for i915 testing with intel gpu tools, later on to get widevine and steam to work I'm trying to get apt to work. I've fixed a number of issues to date in pseudofs/linprocfs but now I'm running in to a bug

Re: difference in SIGCHLD behavior between Linux and FreeBSD breaks apt

2016-07-07 Thread Matthew Macy
On Wed, 06 Jul 2016 23:28:40 -0700 Andrey Chernov <a...@freebsd.org> wrote > On 07.07.2016 7:52, K. Macy wrote: > > On Wednesday, July 6, 2016, Don Lewis <truck...@freebsd.org> wrote: > > > >> On 6 Jul, Matthew Macy wrote: > >

Re: difference in SIGCHLD behavior between Linux and FreeBSD breaks apt

2016-07-07 Thread Matthew Macy
On Wed, 06 Jul 2016 23:48:53 -0700 Andrey Chernov <a...@freebsd.org> wrote > On 07.07.2016 9:40, Matthew Macy wrote: > > > > > > > > On Wed, 06 Jul 2016 23:28:40 -0700 Andrey Chernov <a...@freebsd.org> > > wrote ---

Re: Recent -current stable panic at later boot stage

2016-07-09 Thread Matthew Macy
On Sat, 09 Jul 2016 18:19:57 -0700 Andrey Chernov wrote > BTW, it never happens with 11-ALPHA3 even with world build for 12. > > On 09.07.2016 22:06, Andrey Chernov wrote: > > SCHED_ULE used. I have textdump only. Interesting parts: > > <118>Starting

Re: difference in SIGCHLD behavior between Linux and FreeBSD breaks apt

2016-07-07 Thread Matthew Macy
On Thu, 07 Jul 2016 07:04:24 -0700 Konstantin Belousov <kostik...@gmail.com> wrote > On Thu, Jul 07, 2016 at 12:14:52AM -0700, Don Lewis wrote: > > On 6 Jul, Matthew Macy wrote: > > > > > > > > > > > > ---

Re: difference in SIGCHLD behavior between Linux and FreeBSD breaks apt

2016-07-08 Thread Matthew Macy
> Unsurprisingly I may have misinterpreted the trace. > > John observes: > Alternatively, if apt is creating a pipe() that it passes to dpkg() via > fork() and apt > only creates the read end opened and dpkg only keeps the write end up > opened, then when > dpkg exits, the

Re: EBR fix for life cycle races was Re: panic with tcp timers

2016-06-30 Thread Matthew Macy
On Tue, 28 Jun 2016 23:19:45 -0700 Matthew Macy <mm...@nextbsd.org> wrote > > > > On Tue, 28 Jun 2016 15:51:57 -0700 K. Macy <km...@freebsd.org> wrote > > > On Tue, Jun 28, 2016 at 10:51 AM, Matthew Macy <mm...@nextbs

gfx-next update: drm-4.8-rc2 tagged in drm-next

2016-08-16 Thread Matthew Macy
As of this moment sys/dev/drm in the drm-next tree is sync with https://github.com/torvalds/linux drivers/gpu/drm (albeit only for the subset of drivers that FreeBSD supports - i915, radeon, and amdgpu). I feel this is a bit of a milestone as it means that it is possible that in the future

Re: External toolchain support broken for devel/llvm38 but not devel/llvm37

2016-08-30 Thread Matthew Macy
On Tue, 30 Aug 2016 14:08:41 -0700 Brooks Davis <bro...@freebsd.org> wrote > On Mon, Aug 29, 2016 at 08:12:08PM -0700, Matthew Macy wrote: > > It looks like there is something broken with the devel/llvm38 port or > > external toolchain

External toolchain support broken for devel/llvm38 but not devel/llvm37

2016-08-29 Thread Matthew Macy
It looks like there is something broken with the devel/llvm38 port or external toolchain support has regressed: This works: make XCC=/usr/local/bin/clang37 XCXX=/usr/local/bin/clang++37 XCPP=/usr/local/bin/clang-cpp37 buildworld -j12 -s This fails: make XCC=/usr/local/bin/clang38

warning errors with buildworld with llvm39

2016-08-30 Thread Matthew Macy
I did a buildworld with llvm39. Unsurprisingly I had to pass NO_WERROR= as the llvm has added additional warnings since 3.8. https://gist.github.com/mattmacy/5f0c994b7587a10e3f58e7fd9fc1dd01 The most prevalent seems to be: jemalloc_nstime.c:120:7: warning: macro expansion producing

Re: gfx-next update: drm-4.8-rc2 tagged in drm-next

2016-08-17 Thread Matthew Macy
ics. > > Thanks in advance. > > Tomoya > > On Tue, Aug 16, 2016 at 12:12:44AM -0700, Matthew Macy wrote: > > As of this moment sys/dev/drm in the drm-next tree is sync with > > https://github.com/torvalds/linux drivers/gpu/drm (albeit only for the

Re: HEADS-UP: IFLIB implementations of sys/dev/e1000 em, lem, igb pending

2017-01-11 Thread Matthew Macy
> > > My tunning are (same for both test): > > > hw.igb.rxd="2048" (it should be useless now) > > > hw.igb.txd="2048" (it should be useless now) > > Matt: I think he meant "useless now" because there is no igb, and the > below hw.em version covers it. No. igb still exists and the old

Re: HEADS-UP: IFLIB implementations of sys/dev/e1000 em, lem, igb pending

2017-01-11 Thread Matthew Macy
On Wed, 11 Jan 2017 01:23:46 -0800 Olivier Cochard-Labbé wrote > On Tue, Jan 10, 2017 at 4:31 AM, Sean Bruno wrote: > > > > > I've updated sys/dev/e1000 at svn R311849 to match Matt Macy's work on > > IFLIB in the kernel. > > > > At

Re: CURRENT: em0 NIC freezes under heavy I/O on net

2017-01-11 Thread Matthew Macy
It looks like I have the wrong msix bar value for your NIC. Will fix in the next day or so.-M On Wed, 11 Jan 2017 00:27:30 -0800 O. Hartmann wrote Running recent CURRENT (FreeBSD 12.0-CURRENT #5 r311919: Wed Jan 11 08:24:28 CET

Re: CURRENT: em0 NIC freezes under heavy I/O on net

2017-01-11 Thread Matthew Macy
Sorry, I meant to send that to the other thread. Was this after the iflib driver commit? If so it's odd that we haven't seen anything like this and I'll try to get a fix in ASAP. On Wed, 11 Jan 2017 03:06:19 -0800 Me wrote It looks

Re: HEADS-UP: IFLIB implementations of sys/dev/e1000 em, lem, igb pending

2017-01-11 Thread Matthew Macy
> > I can generate profiling data for you: what kind of data do you want ? > > > A flame graph for the core cycle count and a flame graph with cache miss stats from pmc would be a great start. ___ freebsd-current@freebsd.org mailing list

Re: HEADS-UP: IFLIB implementations of sys/dev/e1000 em, lem, igb pending

2017-01-11 Thread Matthew Macy
On Wed, 11 Jan 2017 12:02:06 -0800 Sean Bruno wrote > > > On 01/11/17 12:47, Olivier Cochard-Labbé wrote: > > On Wed, Jan 11, 2017 at 4:17 PM, Sean Bruno > > wrote: > > > > > > > >

Re: HEADS-UP: IFLIB implementations of sys/dev/e1000 em, lem, igb pending

2017-01-11 Thread Matthew Macy
> A flame graph for the core cycle count and a flame graph with cache miss > stats from pmc would be a great start. > > > ​I didn't know the exact event name to use for cache miss stats, but here > are the flame graphs for CPU_CLK_UNHALTED_CORE: >

Re: HEADS-UP: IFLIB implementations of sys/dev/e1000 em, lem, igb pending

2017-01-11 Thread Matthew Macy
> > x head r311848: packets per second > + head r311849 and BAR patch: packets per second > +--+ > |++++ + xxx x x| > |

Re: HEADS-UP: IFLIB implementations of sys/dev/e1000 em, lem, igb pending

2017-01-11 Thread Matthew Macy
You can still explicitly set the number of descriptors. It is now reported under the dev sysctl tree. dev... -M On Wed, 11 Jan 2017 12:34:23 -0800 Olivier Cochard-Labbé <oliv...@freebsd.org> wrote > > On Wed, Jan 11, 2017 at 9:13 PM, Matthew Macy <mm...@nex

drm-next update and longer term plans

2016-12-01 Thread Matthew Macy
I imagine that for most users the state of graphics support for post-Haswell hardware is a bit of a black box so I'm sending out this note to let users know what they can and cannot expect. Wayland has actually become a reality for some. Talk to Johannes Lundberg if you're interested in

Re: PQ_LAUNDRY: unexpected behaviour

2017-01-06 Thread Matthew Macy
> > Please try the drm-next branch now. Up until very recently, the > > shrinkers responsible for culling ttm/gem allocations were never run. > > I've now implemented the shrinker, but it's driven from vm_lowmem, so > > you'll probably still see what looks like a leak until you hit low

Re: PQ_LAUNDRY: unexpected behaviour

2017-01-06 Thread Matthew Macy
Thanks. Pete already filed that as part of #108. With luck markj@ will have that fixed this weekend. -M On Fri, 06 Jan 2017 11:24:00 -0800 Jonathan Anderson <jonathan.robert.ander...@gmail.com> wrote > On 6 Jan 2017, at 14:06, Matthew Macy wrote: > > >

Re: PQ_LAUNDRY: unexpected behaviour

2017-01-06 Thread Matthew Macy
10:53:03 -0800 Pete Wright <p...@nomadlogic.org> wrote > > > On 1/6/17 10:44 AM, Jonathan Anderson wrote: > > On 6 Jan 2017, at 12:48, Pete Wright wrote: > > > >> On 1/6/17 9:14 AM, Matthew Macy wrote: > >>> > >>>

Re: PQ_LAUNDRY: unexpected behaviour

2017-01-04 Thread Matthew Macy
On Mon, 02 Jan 2017 06:01:50 -0800 Jonathan Anderson wrote > Hi all, > > I'm seeing some unexpected PQ_LAUNDRY behaviour on something fairly close > to -CURRENT (drm-next-4.7 with an IFC on 26 Dec). Aside from the use of > not-quite-CURRENT, it's

Re: rust broken?

2018-06-07 Thread Matthew Macy
On Thu, Jun 7, 2018 at 10:50 Michael Butler wrote: > On 06/07/18 13:36, Matthew Macy wrote: > > On Thu, Jun 7, 2018 at 10:33 Michael Butler > <mailto:i...@protected-networks.net>> wrote: > > > > Ah - I'll re-enable that to see if it makes a difference .. &g

Re: rust broken?

2018-06-07 Thread Matthew Macy
Rustup uses the 11 ABI. On Thu, Jun 7, 2018 at 10:11 Alan Somers wrote: > Can you reproduce the problem using rust installed from rustup instead of > from Ports? If so, you should file a bug report with the Rust developers. > Hint: when using Rustup, you'll have to use vresion 1.26.1 instead

Re: rust broken?

2018-06-07 Thread Matthew Macy
y work on 11. This is why you need to use the port / pkg. -M > I missed that in the comparison between my two build environments :-( > > Michael > > On 06/07/18 13:21, Matthew Macy wrote: > > > > Rustup uses the 11 ABI. > > > > On Thu, Jun

hwpmc - wither ppro and p4

2018-05-31 Thread Matthew Macy
Intel now provides comprehensive tables for all performance counters and the various valid configuration permutations as text .json files. I've converted libpmc to use these and simplified the hwpmc_core to pass the values through. I'd like to remove all the existing Intel tables from the kernel.

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

2018-06-03 Thread Matthew Macy
On Sun, Jun 3, 2018 at 2:40 PM, Theron wrote: >> 4. Disable the stupid warning in the Makefile / build system. If you don't >> care, and there's a good reason for what you are doing (sounds like there >> is), better to just disable the warning as so much useless noise. >> >> Warner >>

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

2018-06-04 Thread Matthew Macy
On Mon, Jun 4, 2018 at 12:03 PM, Adrian Chadd wrote: > Hi, > > As a driver/framework developer - no, don't do that. > > It's worked mostly great for the video side of things because your > touch points are "the VM system" and "linuxkpi". And they're all in > one big driver pull from Linux. > >

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

2018-06-05 Thread Matthew Macy
Implementing a callback in 140 different files for the sake of a handful of out of tree drivers and people not reading updating is pretty prohibitive. 11 may be more your cup of tea. On Mon, Jun 4, 2018 at 22:27 Adrian Chadd wrote: > Hi, > > If there's an API that isn't being used then great,

Re: atomic_testandclear_, atomic_testandset_

2018-06-24 Thread Matthew Macy
On Sun, Jun 24, 2018 at 01:42 Konstantin Belousov wrote: > On Sat, Jun 23, 2018 at 01:38:07PM -0700, Matthew Macy wrote: > > It turns out ck already has equivalent primitives. Pardon the noise. > Why not to add trivial cmpset-based implementations to the lacking > arches ? If mai

atomic_testandclear_, atomic_testandset_

2018-06-23 Thread Matthew Macy
The functions in the subject are both documented in atomic(9) and are implemented by every arch except sparc64 and MIPS. I have some code in review that uses them that I intend to commit once the various design issues are addressed. Please implement them so that those targets can remain part of

Re: atomic_testandclear_, atomic_testandset_

2018-06-23 Thread Matthew Macy
It turns out ck already has equivalent primitives. Pardon the noise. -M On Sat, Jun 23, 2018 at 12:18 Matthew Macy wrote: > The functions in the subject are both documented in atomic(9) and are > implemented by every arch except sparc64 and MIPS. I have some code in > review that

Re: atomic changes break drm-next-kmod?

2018-07-03 Thread Matthew Macy
This seems like a clang inline asm bug. Could you try building the port with a recent gcc against an unpatched HEAD? On Tue, Jul 3, 2018 at 15:38 Pete Wright wrote: > > > On 07/03/2018 15:29, John Baldwin wrote: > > That seems like kgdb is looking at the wrong CPU. Can you use > > 'info

Re: Page fault in udp_usrreq.c:823

2018-06-21 Thread Matthew Macy
Try updating. It should be fixed. On Thu, Jun 21, 2018 at 6:14 PM, Cy Schubert wrote: > In message <20180620090957.ga...@x2.osted.lan>, Peter Holm writes: >> 20180620 10:32:47 all (1/1): udp.sh >> Kernel page fault with the following non-sleepable locks held: >> shared rw udpinp (udpinp) r = 0

Re: Page fault in udp_usrreq.c:823

2018-06-21 Thread Matthew Macy
SD.org > > The need of the many outweighs the greed of the few. > > > In message il.com> > , Matthew Macy writes: >> Try updating. It should be fixed. >> >> On Thu, Jun 21, 2018 at 6:14 PM, Cy Schubert wrot >> e: >> > In message <201

Re: panic after ifioctl/if_clone_destroy

2018-08-05 Thread Matthew Macy
If you could give me a self-contained reproducer that would expedite a fix. Thanks. -M On Sun, Aug 5, 2018 at 08:36 Roman Bogorodskiy wrote: > Running -CURRENT r336863 on amd64. Get the following panic right after > (or during) boot: > > Fatal trap 12: page fault while in kernel mode > cpuid =

Re: ci.freebsd.org 's FreeBSD-head-{amd64, i386}-test started failing after -r337332 (last good), inp_gcmoptions involved

2018-08-05 Thread Matthew Macy
That looks like it is tied to changes I made 3 months ago. I won't be at my desk until the end of the week, but if it's consistent I can take a look. -M On Sun, Aug 5, 2018 at 17:57 Li-Wen Hsu wrote: > On Sun, Aug 5, 2018 at 6:23 PM Mark Millard wrote: > > > > amd64: #8493 was for -r337342

Re: panic after ifioctl/if_clone_destroy

2018-08-06 Thread Matthew Macy
The struct thread is typesafe. The problem is that the link is no longer typesafe now that it’s not part of the thread. Thanks for pointing this out. I’ll commit a fix later today. -M On Mon, Aug 6, 2018 at 02:39 Hans Petter Selasky wrote: > Hi Matthew, > > On 08/06/18 10:02, Hans Petter

Re: kernel build failure

2018-08-13 Thread Matthew Macy
On Mon, Aug 13, 2018 at 5:33 PM Rick Macklem wrote: > Rodney W. Grimes wrote: > >> On Sun, 12 Aug 2018 14:39-0700, Matthew Macy wrote: > >> > >> > Sorry guys, last time I touched ZFS I tried to push to make it an > option to > >> > statically lin

Re: kernel build failure

2018-08-12 Thread Matthew Macy
Sorry guys, last time I touched ZFS I tried to push to make it an option to statically link and was actually told that it wasn't something anyone else wanted. The issue comes from ZFS not being in NOTES and thus not in LINT. -M On Sun, Aug 12, 2018 at 12:46 PM Trond Endrestøl <

Re: kernel build failure

2018-08-12 Thread Matthew Macy
On Sun, Aug 12, 2018 at 3:25 PM Warner Losh wrote: > > > On Sun, Aug 12, 2018, 3:40 PM Matthew Macy wrote: > >> Sorry guys, last time I touched ZFS I tried to push to make it an option >> to >> statically link and was actually told that it wasn't something anyone e

Re: ci.freebsd.org 's FreeBSD-head-{amd64, i386}-test started failing after -r337332 (last good), inp_gcmoptions involved

2018-08-11 Thread Matthew Macy
0, rsp = 0, rbp = 0 --- > db> > > > Li-Wen > > On Mon, Aug 6, 2018 at 9:53 AM Alan Somers wrote: > > > > I can't reproduce the failure. On my VM, with a kernel from Aug-2, the > test passes. But it sure seems to be consistent in Jenkins. > > > >

drm / drm2 removal in 12

2018-08-21 Thread Matthew Macy
Just in case anyone misses the change to UPDATING: 20180821: drm and drm2 have been removed. Users on powerpc, 32-bit hardware, or with GPUs predating Radeon and i915 will need to install the graphics/drm-legacy-kmod. All other users should be able to use one of

Native Encryption for ZFS on FreeBSD CFT

2018-08-21 Thread Matthew Macy
To anyone with an interest in native encryption in ZFS please test the projects/zfs-crypto-merge-0820 branch in my freebsd repo: https://github.com/mattmacy/networking.git ( git clone https://github.com/mattmacy/networking.git -b projects/zfs-crypto-merge-0820 ) The UI is quite close to the

Re: Native Encryption for ZFS on FreeBSD CFT

2018-08-21 Thread Matthew Macy
On Tue, Aug 21, 2018 at 20:22 Alan Somers wrote: > On Tue, Aug 21, 2018 at 9:13 PM Sean Fagan wrote: > >> On Aug 21, 2018, at 8:11 PM, Alan Somers wrote: >> > The last time I looked (which was a long time ago), Oracle's ZFS >> encryption looked extremely vulnerable to watermarking attacks.

Re: Native Encryption for ZFS on FreeBSD CFT

2018-08-21 Thread Matthew Macy
On Tue, Aug 21, 2018 at 6:55 PM Matthew Macy wrote: > To anyone with an interest in native encryption in ZFS please test the > projects/zfs-crypto-merge-0820 branch in my freebsd repo: > https://github.com/mattmacy/networking.git > > Oh and I neglected to state that this work is

Re: Native Encryption for ZFS on FreeBSD CFT

2018-08-22 Thread Matthew Macy
pe 'struct mtx' that is never > completed > static struct mtx freebsd_crypto_mutex; > ^ > > /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/freebsd_crypto.c:62:15: > note: forward declaration of 'struct mtx' > static struct mtx freebsd_crypto_mutex;

Re: Native Encryption for ZFS on FreeBSD CFT

2018-08-22 Thread Matthew Macy
Fixed. Pull. bc2b257d1082112cc27e56db793f5c569f603bec On Wed, Aug 22, 2018 at 12:10 AM Matthew Macy wrote: > Yes. I _just_ rebased and broke world in the process. Fix coming up > momentarily. > -M > > On Wed, Aug 22, 2018 at 12:06 AM Outback Dingo > wrote: > >>

Re: priority of paths to kernel modules?

2018-08-24 Thread Matthew Macy
No we're not. x86 and PPC will be disconnected from the build in a subsequent commit during the freeze. Warner was simply too tired to communicate this adequately and still meet the timeline that RE wanted. And take heart. Even if Warner weren't trying to balance the needs of RE and the graphics

Re: ifnet use after free

2018-08-24 Thread Matthew Macy
On Fri, Aug 24, 2018 at 15:25 Shawn Webb wrote: > Hey All, > > Somewhere in the last month or so, a use after free was introduced. I > don't have the time right now to bisect the commits and figure out > which commit introduced the breakage. Attached is the core.txt (which > seems nonsensical

Re: drm / drm2 removal in 12

2018-08-24 Thread Matthew Macy
On Fri, Aug 24, 2018 at 14:53 Ali wrote: > On Tue, Aug 21, 2018 at 06:54:54PM -0700, Matthew Macy wrote: > > Just in case anyone misses the change to UPDATING: > > > > 20180821: > > drm and drm2 have been removed. Users on powerpc, 32-bit > hardware, >

Re: drm / drm2 removal in 12

2018-08-25 Thread Matthew Macy
Aug 24, 2018 at 4:20 PM Matthew Macy wrote: >> >> > On Fri, Aug 24, 2018 at 14:53 Ali wrote: >> > >> > > On Tue, Aug 21, 2018 at 06:54:54PM -0700, Matthew Macy wrote: >> > > > Just in case anyone misses the change to UPDATING: >> >

Re: ifnet use after free

2018-08-25 Thread Matthew Macy
Aug 2018, at 0:26, Matthew Macy wrote: > > On Fri, Aug 24, 2018 at 15:25 Shawn Webb > wrote: > > Hey All, > > Somewhere in the last month or so, a use after free was introduced. I > don't have the time right now to bisect the commits and figure out > which comm

Re: ifnet use after free

2018-08-25 Thread Matthew Macy
k you for updating me. -M > Kristof > > On 25 Aug 2018, at 19:44, Matthew Macy wrote: > > I'll take a look. But it's likely to not be the OP's issue. For future > reference memguard on the memory type in question is extremely useful in > catching use after free. > > -M &g

Re: drm / drm2 removal in 12

2018-08-26 Thread Matthew Macy
Please just stop responding to this person or we're going to have to migrate to moderated lists. You're legitimizing the voice of one person who project members have spend hours of their time (some even in person) trying to explain the time tradeoffs of supporting graphics. For some reason he

  1   2   >