Re: kern.sched.quantum: Creepy, sadistic scheduler

On Wed, Apr 04, 2018 at 09:32:58AM -0400, George Mitchell wrote: > On 04/04/18 06:39, Alban Hertroys wrote: > > [...] > > That said, SCHED_ULE (the default scheduler for quite a while now) was > > designed with multi-CPU configurations in mind and there are claims that > > SCHED_4BSD works

stable/11 r332356 started panicing in bpf_dtor/__mtx_lock_sleep

Hi! I have a server that was running stable/11 rock-stable for many months. A week ago I've updates it to 11.1-STABLE r332356 and today it paniced and I have crashdump. Any thoughts? Unread portion of the kernel message buffer: Sleeping thread (tid 100444, pid 28400) owns a non-sleepable lock

Re: stable/11 r332356 started panicing in bpf_dtor/__mtx_lock_sleep

On 17.04.2018 16:30, Eugene Grosbein wrote: CCing mjoras@ as author of suspicious change https://svnweb.freebsd.org/base?view=revision=323477 > I have a server that was running stable/11 rock-stable for many months. It was running stable/11 r314043 before last update. > A week ago I've

11.1 stable r321309 loader.efi boot faile

>> freebsd 11.1 stable r321309 boot failed >> loader.efi recognize efipart as new disk on MacBook pro mid 2015 >> >> >> >> > ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send

Re: amd64 kernel crash introduced between 20180329 & 20180408

On Tue, Apr 17, 2018 at 9:44 AM, Dan Allen wrote: > I run FreeBSD 11-STABLE on actual machines, and I build the system every few > days. Things have been fine. > > However, I also run FreeBSD 11 via the qemu emulator on my Mac. I run lots > of different BSD & Linux OSes

amd64 kernel crash introduced between 20180329 & 20180408

I run FreeBSD 11-STABLE on actual machines, and I build the system every few days. Things have been fine. However, I also run FreeBSD 11 via the qemu emulator on my Mac. I run lots of different BSD & Linux OSes here to test them out. I have been running the same binary of qemu-system-x86_64

CentOs Competitors Users Contact List.

style="color:rgb(31,78,121)">Hello, Would you be interested in CentOS (Linux) Users List? We are a Global Technology User’s List Provider’s with 90 Million Plus data and counting. You may also acquire the alternatives such as: Windows Server users List, Oracle Linux users List, 

Re: amd64 kernel crash introduced between 20180329 & 20180408

> On 17 Apr 2018, at 9:24 AM, Kyle Evans wrote: > > Can you set vm.pmap.pti=0 at the loader prompt and see if > this affects your situation at all, just to rule that out? I redid everything from the start, did set vm.pmap.pti=0, and it behaves exactly the same: kernel

Re: amd64 kernel crash introduced between 20180329 & 20180408

> On 17 Apr 2018, at 8:49 AM, Kyle Evans wrote: > > As "the guy most likely to have broken boot code in stable," may I ask > what leads you specifically to amd64 boot code? Mostly curious if > there's something beyond "i386 works well" that lead you to this > conclusion.

Re: amd64 kernel crash introduced between 20180329 & 20180408

On Tue, Apr 17, 2018 at 10:18 AM, Dan Allen wrote: > > >> On 17 Apr 2018, at 8:49 AM, Kyle Evans wrote: >> >> As "the guy most likely to have broken boot code in stable," may I ask >> what leads you specifically to amd64 boot code? Mostly curious if >>

Re: kern.sched.quantum: Creepy, sadistic scheduler

On Tue, Apr 17, 2018 at 8:49 AM, Kevin Oberman wrote: > On Mon, Apr 16, 2018 at 11:56 PM, Eivind Nicolay Evensen < > eivi...@terraplane.org> wrote: > > > On Wed, Apr 04, 2018 at 09:32:58AM -0400, George Mitchell wrote: > > > On 04/04/18 06:39, Alban Hertroys wrote: > > > >

Re: kern.sched.quantum: Creepy, sadistic scheduler

On Mon, Apr 16, 2018 at 11:56 PM, Eivind Nicolay Evensen < eivi...@terraplane.org> wrote: > On Wed, Apr 04, 2018 at 09:32:58AM -0400, George Mitchell wrote: > > On 04/04/18 06:39, Alban Hertroys wrote: > > > [...] > > > That said, SCHED_ULE (the default scheduler for quite a while now) was >

more data: SCHED_ULE+PREEMPTION is the problem

On 04/07/18 10:18, Peter wrote: > Hi all, > [...] Thanks for all the investigation! > 3. kern.sched.preempt_thresh > > I could make the problem disappear by changing kern.sched.preempt_thresh >  from the default 80 to either 11 (i5-3570T) or 7 (p3) or smaller. This > seems to correspond to the

Re: kern.sched.quantum: Creepy, sadistic scheduler

On 04/17/18 17:20, EBFE via freebsd-stable wrote: > On Tue, 17 Apr 2018 09:05:48 -0700 > Freddie Cash wrote: > >> # Tune for desktop usage >> kern.sched.preempt_thresh=224 >> >> ​Works quite nicely on a 4-core AMD Phenom-II X4 960T Processor >> (3010.09-MHz K8-class CPU)

Re: kern.sched.quantum: Creepy, sadistic scheduler

On Tue, 17 Apr 2018 09:05:48 -0700 Freddie Cash wrote: > # Tune for desktop usage > kern.sched.preempt_thresh=224 > > ​Works quite nicely on a 4-core AMD Phenom-II X4 960T Processor > (3010.09-MHz K8-class CPU) running KDE4 using an Nvidia 210 GPU. For interactive tasks,