-------- Forwarded Message -------- From: a a <m.alfa...@gmail.com> To: Ben Hutchings <b...@decadent.org.uk> Subject: Re: Bug#932250: linux-image-amd64: random segfaults without taking something down Date: Thu, 18 Jul 2019 13:09:53 +0200 Message-Id: <CANfEg5hbNfNpOXrHStG6b- vui3zbffaw3chtox3+i2xrl4u...@mail.gmail.com>
It shouldnt be overheating, because i have custom setting on cpu heatsink fan and the ram module has a own heatsink. Plus i have fan on case which puls out the excees heat. The segfaults happend at low load, maybe it wasnt above P2 power state. Also i have made sure that the cpu doenst exceed 90°C. Out of tree modules are from virtual box. After disabling overcommit and apparmor i didnt experience a segfault for now. The segfaults started to dissapeer it seams. I fear that this might be a bug tied to certain order of instructions. For example if i enable debug it may change order of instruction and the bug doesnt occur. Reason that i reported this bug with package linux-image-amd64 is that i didnt know about the existence of linux-mage-4.19.0-5-amd64 and i tried to prevent creating bug file for nonexisting package. Should i file another bug and put a link to this report ? št 18. 7. 2019 o 4:04 Ben Hutchings <b...@decadent.org.uk> napísal(a): > Control: tag -1 moreinfo > > On Wed, 2019-07-17 at 01:27 +0200, m.alfa...@gmail.com wrote: > > Package: linux-image-amd64 > > Version: 4.19+105 > > Severity: important > > > > Hi. > > > > Im currently running debian buster kernel and i experienced some > segfaults. > > Segfaults are random, which prevents me from pinpointing the trigger. > > First i tried disabling overcommit on memory, the behavior stoped. > > Today it started during installing updates for libreoffice. Two first > > segfaults were caused by xfdesktop, the two more with gmain. > > Another odd thing is that the error is in libglib and the code is > completly > > identical. The RAM was tested with memtest86+, memtester. Previous > release > > with backport kernel was working perfectly even with overcommit. I > > guess there is a small chance of defective hw. > > Could it be overheating? > > > My next suspect is apparmor. Im going to use the system with disabled > > apparmor to see if this problem persist. > > What about the out-of-tree module you are using? Can you run without > that? > > > Thank you > > > > I hope this helps make debian more stable and reliable. > [...] > > Well, it isn't as helpful as it could be, because you chose to ignore > the request to report a bug against linux-image-4.19.0-5-amd64. > > Ben. > > -- > Ben Hutchings > Any sufficiently advanced bug is indistinguishable from a feature. > > > -- Ben Hutchings Any sufficiently advanced bug is indistinguishable from a feature.
