Re: cannot get touchpad mouse, no psm device, on Dell Precision 3520

On 06/07/2018 14:01, Anton Shterenlikht wrote: On Thu, Jun 07, 2018 at 01:34:31PM -0700, Pete Wright wrote: On 06/07/2018 13:21, Anton Shterenlikht wrote: Please help get touchpad mouse on Dell Precision 3520. The usb mouse works fine. pciconf isn't really applicable here i think.  does

Re: rust broken?

On Thu, Jun 7, 2018 at 10:33 Michael Butler wrote: > Ah - I'll re-enable that to see if it makes a difference .. > It's not a question of enabling. It doesn't explicitly use the 11 symbols. Rust developers assume that every OS has a frozen ABI like Linux. The rust from rustup will only work on

Re: panic: Assertion td->td_lock == TDQ_LOCKPTR(tdq) failed at /usr/src/sys/kern/sched_ule.c:2137

On Thu, Jun 07, 2018 at 05:13:45PM -0700, bob prohaska wrote: > > I'll try again, this time with USB swap turned off. The circle closed, back to the original panic in the subject line. Console, top and buildworld.log files are at http://www.zefox.net/~fbsd/rpi3/crashes/20180607

Re: rust broken?

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: r334533 renders head unbootable on XenServer 7.4

On Wed, Jun 6, 2018 at 6:50 PM, Trond Endrestøl < trond.endres...@fagskolen.gjovik.no> wrote: > After trial and error, I found r334533 to be responsible for rendering > head unbootable on XenServer 7.4. Neither of the two available > XenServer patches has been applied on the host server. > >

Re: panic: Assertion td->td_lock == TDQ_LOCKPTR(tdq) failed at /usr/src/sys/kern/sched_ule.c:2137

On Wed, Jun 06, 2018 at 10:28:58PM -0700, Mark Millard wrote: > > Looks like there has been another stab at avoiding some > unnecessary Out Of Memory killing of processes: > > Author: alc > Date: Thu Jun 7 02:54:11 2018 > New Revision: 334752 > URL:

Re: cannot get touchpad mouse, no psm device, on Dell Precision 3520

On Thu, Jun 07, 2018 at 01:34:31PM -0700, Pete Wright wrote: > > > On 06/07/2018 13:21, Anton Shterenlikht wrote: > > Please help get touchpad mouse on > > Dell Precision 3520. > > The usb mouse works fine. > > > pciconf isn't really applicable here i think.  does your dmesg buffer >

Re: cannot get touchpad mouse, no psm device, on Dell Precision 3520

On 06/07/2018 13:21, Anton Shterenlikht wrote: Please help get touchpad mouse on Dell Precision 3520. The usb mouse works fine. pciconf isn't really applicable here i think.  does your dmesg buffer reference any PS/2 devices being detected?  here is CURRENT detecting my synaptics

cannot get touchpad mouse, no psm device, on Dell Precision 3520

Please help get touchpad mouse on Dell Precision 3520. The usb mouse works fine. z> pciconf -lv hostb0@pci0:0:0:0: class=0x06 card=0x07a91028 chip=0x19108086 rev=0x07 hdr=0x00 vendor = 'Intel Corporation' device = 'Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host

Re: rust broken?

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 > > wrote: > > > > Ah - I'll re-enable that to see if it makes a difference .. > > > > > > > > It's not a question

Re: rust broken?

On 06/07/18 13:36, Matthew Macy wrote: > On Thu, Jun 7, 2018 at 10:33 Michael Butler > wrote: > > Ah - I'll re-enable that to see if it makes a difference .. > > > > It's not a question of enabling. It doesn't explicitly use the 11 > symbols. Rust

Re: rust broken?

Ah - I'll re-enable that to see if it makes a difference .. 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 7, 2018 at 10:11 Alan Somers >

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

On 03/05/2018 12:41, Andriy Gapon wrote: > I think that we need preemption policies that might not be expressible as one > or > two numbers. A policy could be something like this: > - interrupt threads can preempt only threads from "lower" classes: real-time, > kernel, timeshare, idle; > -

Re: rust broken?

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 of 1.26.0. -Alan On Thu, Jun 7, 2018 at 9:44 AM, Michael Butler wrote: > In

rust broken?

In response to a Firefox update, I tried to build the new version. However, rust now fails with a core-dump in the build process. checking for libffi > 3.0.9... yes checking MOZ_FFI_CFLAGS... -I/usr/local/lib/libffi-3.2.1/include checking MOZ_FFI_LIBS... -L/usr/local/lib -lffi checking for

Re: how do I use the make universe machines?

Just replying to one of the messages at random... Benjamin Kaduk wrote: [stuff snipped] >I think https://www.freebsd.org/internal/machines.html sounds like >the page you're looking for. (universe is just a top-level make >target like buildworld, but will take a while on non-beefy >hardware.) Yea,

Re: panic: Assertion td->td_lock == TDQ_LOCKPTR(tdq) failed at /usr/src/sys/kern/sched_ule.c:2137

bob prohaska fbsd at www.zefox.net wrote on Wed Jun 6 23:57:57 UTC 2018 : > On Wed, Jun 06, 2018 at 08:55:39PM +0200, Ronald Klop wrote: > > On Sat, 02 Jun 2018 13:40:27 +0200, Ronald Klop > > > wrote: > > > > > > How do you ever run a -j4 buildworld? My RPI3 starts building clang/llvm >