On 30/07/2020 10:19, Markus Kolb wrote:
Am 29.07.2020 15:13, schrieb Anton Aylward:
Please don't cc me. I subscribe to the list and read there; there is not need to send me a personal copy as well.
Marcus did not mention the specific application that triggered the lock-up. The way he phrased it seemed to indicate that it was an accumulation of activity that triggered the problem with that specific kernel. That makes me wonder about the swap. My own experience with trying to 'tune' swap and swappiness and other paging parameters that seem to run afoul of using FF, as well as other sceptical comments on this forum about the way swap works in 15.x kernels compared to 42.x and 43.x adds to that.
I'm talking about kernel crashing with hard lockup. So Num lock key or here the Shift lock key is blinking and also SysRq doesn't react.
Yes, yes, and yes. That's what I'm describing.
It has nothing to do with any application is using too many resources...
I also have a window on 'vmstat' running, which will show me if I'm approaching a heavy load factor, swap thrashing or anything like that. <sidebar> yes, I've observed those with some applications and it has nothing to do with lock-up. </sidebar> I also have on my bottom panel the simple graphs showing disk activity and CPU load. These are available as widget under KDE. I'm sure there are similar for other desktops. Yes, I can run application like Darktable that do heavy image rendering and eat memory and CPU ('cos I don't have a $4,000 GPU), but what over-heats then is my cooking pan as I make dinner waiting for the rendering to finish. No lock-up. DT is nice about that :-) For a kernel to lock up there has to be a flaw in the kernel that is triggered by some event; a peripheral asynchronous event or a as a result of a user space activity. Yes, I'm stating the bleeding obvious. My inclination is to blame the the too-smart-for-their-own-good buqqers at Mozilla for something in Firefox. No wait, it might be an idiot plug-in coder assumes about the API that those too-smart-for-their-own-good buqqers at Mozilla claim to have put in there. What's your theory on why it crashes? If you don't think it is triggered by an application then what? Are you bothering to metricate your system with the widget that KDE lets you put in your panel, with the other tools and log mechanisms? -- If you can read this, we wasted 32 billion bucks. -- bumper sticker on stealth bomber -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org