I'm replying late, but last night I almost had a complete meltdown of the
system.
I did a partial pkg upgrade for the packages that managed to get built by
poudriere, then all hell broke loose. Screen lock-ups, random reboots, and
several hard reboots later I decided to do a fresh
uname: FreeBSD 11.0-CURRENT #0 r266393M: Sun May 18 13:04:00 2014 amd64
I'm also loading the Radeon_kms modules
Upon system startup, memory profile is clean. I get locked memory (mem_wire)
usage as:
9% before Radeon*.ko modules loaded
12% when slim is started (loads Radeon*.ko modules)
On Thursday, May 29, 2014 5:41:03 am Beeblebrox wrote:
uname: FreeBSD 11.0-CURRENT #0 r266393M: Sun May 18 13:04:00 2014 amd64
I'm also loading the Radeon_kms modules
Upon system startup, memory profile is clean. I get locked memory (mem_wire)
usage as:
9%before Radeon*.ko modules
On Thu, 29 May 2014 09:08:10 -0400
John Baldwin j...@freebsd.org wrote:
On Thursday, May 29, 2014 5:41:03 am Beeblebrox wrote:
uname: FreeBSD 11.0-CURRENT #0 r266393M: Sun May 18 13:04:00 2014
amd64 I'm also loading the Radeon_kms modules
SKIP
I don't know if the lsof dump in single
On 2014-05-29 09:57, Alexander Kabaev wrote:
On Thu, 29 May 2014 09:08:10 -0400
John Baldwin j...@freebsd.org wrote:
On Thursday, May 29, 2014 5:41:03 am Beeblebrox wrote:
uname: FreeBSD 11.0-CURRENT #0 r266393M: Sun May 18 13:04:00 2014
amd64 I'm also loading the Radeon_kms modules
SKIP
Why do you think libc.so.7 has anything to do with this?
Well, because there are two instances of it running in the lsof dump, with
several possible child process candidates. Why would they be hanging
around when practically everything has been killed?
Radeon*.ko modules are a very strong
On Thursday, May 29, 2014 9:57:22 am Alexander Kabaev wrote:
On Thu, 29 May 2014 09:08:10 -0400
John Baldwin j...@freebsd.org wrote:
On Thursday, May 29, 2014 5:41:03 am Beeblebrox wrote:
uname: FreeBSD 11.0-CURRENT #0 r266393M: Sun May 18 13:04:00 2014
amd64 I'm also loading the
On 2014-05-29 12:04, John Baldwin wrote:
On Thursday, May 29, 2014 9:57:22 am Alexander Kabaev wrote:
On Thu, 29 May 2014 09:08:10 -0400
John Baldwin j...@freebsd.org wrote:
On Thursday, May 29, 2014 5:41:03 am Beeblebrox wrote:
uname: FreeBSD 11.0-CURRENT #0 r266393M: Sun May 18 13:04:00
On Thursday, May 29, 2014 10:42:18 am Beeblebrox wrote:
Why do you think libc.so.7 has anything to do with this?
Well, because there are two instances of it running in the lsof dump, with
several possible child process candidates. Why would they be hanging
around when practically everything
