[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#920547: Crashes every few hours




Hi Ben,

On Mon, Jan 28, 2019 at 12:42:37AM +0000, Ben Hutchings wrote:
> On Sat, 26 Jan 2019 20:03:49 +0000 Toni <toni@debian.org> wrote:
> > Package: src:linux
> > Version: 4.19.16-1
> > Severity: critical
> > File: linux-image-4.19.0-2-amd64
> 
> Is this a new problem with version 4.19.16-1?  Or did it happen with
> earlier versions as well?

it happened with the 4.18.* kernel as well. The machine came with Ubuntu
and 4.13 preinstalled, but I wiped it as soon as I could and installed
Debian. So I don't know if it would have worked with Ubuntu - the entire
setup was not suitable for my purposes, but I thought that 4.9 might be
too old for this hardware.

However, the machine came with a 1.3 BIOS, which I updated to 1.6 and
then to 1.7. I think, I had 4.18 together with 1.6 running, but closed
the corresponding bug report when I noticed that both a newer kernel and
a newer BIOS were available. Well, the situation compared has improved a
little, compared to that, but it is still very bad.

> When you say "data loss", are you talking about data in memory or
> corruption of files that were saved and sync'd to disk?

I mean, files on disk were destroyed. I noticed some because I use
etckeeper with git, and suddenly, I could no longer see my update
history because files in /etc/.git were corrupt to the point that no
"git fsck" or "git gc" could resurrect the tree.

> On x86 laptops thermal management is (by default) done by the system
> firmware (BIOS and management engine code).  If you didn't override
> that, and yet the CPU overheats, this is the manufacturer's fault.

Ok... In the BIOS, I set the corresponding parameter from "performance"
to "normal", which I hoped would be a more conservative setting, to
prevent exactly this problem.


Cheers,
Toni


Reply to: