[03:19] Are all the shiftfs patches touching fs/shiftfs.c ? === Eighth_Doctor is now known as Conan_Kudo === Conan_Kudo is now known as Eighth_Doctor [13:31] sforshee, ^ [15:07] Is there any Ubuntu Kernel Meeting today during GUADEC? Or you already had it [15:20] #ubuntu-desktop [15:20] whoops [15:59] luna_, we don't really have irc meetings; if you have something to bring up you can do it at anytime here [16:04] Good afternoon. I've been running into some various freezing issues with my Ubuntu installation, and the most recent freeze seems like it might be in your folks wheelhouse. [16:05] The behavior is that I'll be doing something and suddenly I'll get a hard freeze. I thought it might be graphics drivers, but I have observed this hard freeze behavior with both a Radeon 5700XT and an nVidia 1060 3GB - open source drivers on both. [16:06] I started out on stock Ubuntu Kernel and drivers, but now I'm using 5.7.9 from Ubuntu and graphics drivers from oibaf. [16:07] And the most recent crash resulted in a rather interesting thing in my journalctl: https://hastebin.com/xagixisile.txt [16:08] A write attempt to an NX page. At the time I was simply opening a new page in Firefox. My intuition is that it points to faulty RAM, but I've already run memtest86 (not +) overnight [16:17] apw: ah alright nah i don't just saw it in the fridge calendar and wondered [16:17] will join todays Firefox and Fenix meeting instead then [16:53] My apologies if this isn't the right channel, I was suggested to go here to ask [17:17] AlexMax: hey - I'm not going to be able to help you out here but please double check that there's not a stack trace in your logs following what you've already pasted [17:18] No stack trace, unfortunately. [17:18] AlexMax: bummer - there's not really enough info for anyone to debug your issue [17:18] Thanks for what little time you had to spare [17:19] AlexMax: the kernel attempts to print a normal stack trace after those messages but your system must be dying before those log messages can reach the disk [17:36] might be possible to send them elsewhere (in the future), depending on why it doesn't reach the disk? [20:14] Is there enough information to know what it couldn't be? Or could it be any of kernel bug/driver bug/bad RAM/Motherboard?