One more thought that may be nothing, but when kmemleak crashed,
SUnreclaim was at 932552 kB, and after reclaimed/cleared 299840 kB.
There weren't any performance issues like when I had a leak of 5.5 gB
in the 4.18 kernel.
On Mon, Jan 7, 2019 at 3:52 AM Catalin Marinas wrote:
>
> Under memory
I'm not all that sure it was memory related based on my Sun, 6 Jan
2019 13:17:04 -0600 post.
You'll see the log entries at 3AM, and based on earlier entries I
likely went to sleep around 1AM which would mean any memory intense
applications (eg. virtual machine) would've been closed out.
I have 8GB
Hi Nathan,
On Tue, Jan 01, 2019 at 01:17:06PM -0600, Nathan Royce wrote:
> I had a leak somewhere and I was directed to look into SUnreclaim
> which was 5.5 GB after an uptime of a little over 1 month on an 8 GB
> system. kmalloc-2048 was a problem.
> I just had enough and needed to find out the
Now it just looks like it crashes on it's own with no issues from
anything else (note the surrounding event entries which is just the
temperature sensor.):
*
Jan 06 03:27:03 computername plasmashell[1065]: qml: temp unit: 0
Jan 06 03:27:09 computername plasmashell[1065]: qml: temp unit: 0
Jan
It was unrelated to my USB issue. It happened again after I rebooted
within 4 hours of uptime.
This time there were 2 traces, one right after the other and included
another line number.
*
Jan 01 17:47:54 computername plasmashell[1048]: qt.qpa.xcb:
QXcbConnection: XCB error: 2 (BadValue),
Kernel 4.19.13
*
Jan 01 02:04:20 computername kernel: xhci_hcd :00:14.0: ERROR
unknown event type 37
Jan 01 02:04:20 computername kernel: WARNING: CPU: 2 PID: 2236 at
mm/page_alloc.c:4254 __alloc_pages_nodemask+0xf52/0xfb0
Jan 01 02:04:20 computername kernel: Modules linked in: rfcomm ccm
6 matches
Mail list logo
