Re: panic when loading mlxen

2018-02-03 Thread Daniel Braniss
> On 2 Feb 2018, at 20:47, K. Macy wrote: > > That's odd since it doesn't use any of taskqgroup stuff. I take it you > can't get a core? no core but some more info: db> bt Tracing pid 0 tid 10 td 0x81e0e500 taskqgroup_attach_cpu() at taskqgroup_attach_cpu+0x4f/frame 0x822e4

Re: panic when loading mlxen

2018-02-03 Thread Hans Petter Selasky
On 02/03/18 08:34, Daniel Braniss wrote: On 2 Feb 2018, at 20:47, K. Macy wrote: That's odd since it doesn't use any of taskqgroup stuff. I take it you can't get a core? no core but some more info: db> bt Tracing pid 0 tid 10 td 0x81e0e500 taskqgroup_attach_cpu() at taskqgroup_

Re: panic when loading mlxen

2018-02-03 Thread Daniel Braniss
> On 3 Feb 2018, at 11:34, Hans Petter Selasky wrote: > > On 02/03/18 08:34, Daniel Braniss wrote: >>> On 2 Feb 2018, at 20:47, K. Macy wrote: >>> >>> That's odd since it doesn't use any of taskqgroup stuff. I take it you >>> can't get a core? >> no core but some more info: >> db> bt >> Traci

Re: panic when loading mlxen

2018-02-03 Thread Hans Petter Selasky
Hi, I think Alexander came ahead of me: https://svnweb.freebsd.org/base?view=revision&revision=328805 Can you try r328805 ? --HPS ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, se

Re: panic when loading mlxen

2018-02-03 Thread Daniel Braniss
> On 3 Feb 2018, at 12:16, Hans Petter Selasky wrote: > > Hi, > > I think Alexander came ahead of me: > > https://svnweb.freebsd.org/base?view=revision&revision=328805 > > Can you try r328805 ? > > --HPS yup, it works, well it doesn’t panic. thanks danny _

50 percent swap used, but "ps auxww" output shows no processes swapped out

2018-02-03 Thread Michael Voorhis
Hi all, I've got an amd64 system running 11.1-STABLE r325027, with something like 20G of swap. "swapinfo" shows that half the swap is used. So of course I'm curious to know which processes have been swapped out. I'm not using any "tmpfs" filesystems; no ZFS, no huge amounts of wired-down memory.

Re: 50 percent swap used, but "ps auxww" output shows no processes swapped out

2018-02-03 Thread Brandon Allbery
Swapping whole processes out is not really a thing any more. Individual pages are paged to/from memory; if a memory page has no backing file, it will be allocated a block in swap space as its backing storage. (I'm not sure "W" status even means swap; I thought whole-process swapping wasn't even su

Re: 50 percent swap used, but "ps auxww" output shows no processes swapped out

2018-02-03 Thread Michael Voorhis
On 02/03/2018 04:18 PM, Brandon Allbery wrote: > Swapping whole processes out is not really a thing any more. > Individual pages are paged to/from memory; if a memory page has no > backing file, it will be allocated a block in swap space as its > backing storage. Is there a method to determine

Re: 50 percent swap used, but "ps auxww" output shows no processes swapped out

2018-02-03 Thread Eugene Grosbein
04.02.2018 4:18, Brandon Allbery wrote: > (I'm not sure "W" status even means swap; I thought whole-process swapping > wasn't even supported any more.) Kernel may decide to swap out entire processes if vm.swap_enabled=1 (default) and its free page pool heavily stressed or system was configured by

Re: 50 percent swap used, but "ps auxww" output shows no processes swapped out

2018-02-03 Thread Mark Millard via freebsd-stable
Brandon Allbery allbery.b at gmail.com wrote on Sat Feb 3 21:18:53 UTC 2018 : > Swapping whole processes out is not really a thing any more. Individual > pages are paged to/from memory; if a memory page has no backing file, it > will be allocated a block in swap space as its backing storage. > >

Re: 50 percent swap used, but "ps auxww" output shows no processes swapped out

2018-02-03 Thread Brandon Allbery
Also worth noting is that likely candidates for such pageouts include long-lived daemons that are only needed, or which only need certain pages, during startup/shutdown. So evicting only those pages to swap allows optimal use of memory that would otherwise be wasted unnecessarily. Studying demand

Re: 50 percent swap used, but "ps auxww" output shows no processes swapped out

2018-02-03 Thread Eugene Grosbein
04.02.2018 5:09, Mark Millard via freebsd-stable wrote: > I do not know if a W after the first letter in state (STAT) for > "ps auxww" track the kernel-stacks' resident-vs-not status for the > process or not. (Matching your not sure status.) A process has specific flag P_INMEM that is normally 1

Re: 50 percent swap used, but "ps auxww" output shows no processes swapped out

2018-02-03 Thread Eugene Grosbein
04.02.2018 5:32, Brandon Allbery wrote: > Also worth noting is that likely candidates for such pageouts include > long-lived daemons that are only needed, or which only need certain pages, > during startup/shutdown. So evicting only those pages to swap allows > optimal use of memory that would oth

Re: 50 percent swap used, but "ps auxww" output shows no processes swapped out

2018-02-03 Thread Eugene Grosbein
04.02.2018 4:14, Michael Voorhis wrote: > I've got an amd64 system running 11.1-STABLE r325027, with something > like 20G of swap. "swapinfo" shows that half the swap is used. > > So of course I'm curious to know which processes have been swapped > out. I'm not using any "tmpfs" filesystems; no Z

Re: 50 percent swap used, but "ps auxww" output shows no processes swapped out

2018-02-03 Thread Michael Voorhis
On 02/03/2018 05:48 PM, Eugene Grosbein wrote: > These 10G may be just several pages of several processes. > Please show output of "top -ores -d1". This just shows a bunch of hungry postgres processes (see below). In response to your slightly-earlier email, swap_enabled is set (its default) and s

Re: 50 percent swap used, but "ps auxww" output shows no processes swapped out

2018-02-03 Thread Eugene Grosbein
04.02.2018 6:42, Michael Voorhis wrote: > 1 frame of your requested "top" output, sorted as specified: > >> last pid: 47195; load averages: 0.17, 0.37, 0.44 up 99+20:40:41 18:37:07 >> 369 processes: 1 running, 368 sleeping >> CPU: 0.2% user, 0.0% nice, 0.2% system, 0.0% interrupt, 99.7%