Mailinglist Archive: opensuse-factory (447 mails)

< Previous Next >
Re: [opensuse-factory] Kernel Panic with snapshot 20180104
  • From: Knurpht - Gertjan Lettink <knurpht@xxxxxxxxxxxx>
  • Date: Sun, 07 Jan 2018 18:55:52 +0100
  • Message-id: <5124679.LDfuzvBeQJ@knurpht-hp>
Op zondag 7 januari 2018 18:18:48 CET schreef Patrick Shanahan:
* Knurpht - Gertjan Lettink <knurpht@xxxxxxxxxxxx> [01-07-18 11:04]:
Op zondag 7 januari 2018 12:20:47 CET schreef Jiri Slaby:
On 01/07/2018, 12:07 PM, Stratos Zolotas wrote:
On Sun, Jan 7, 2018 at 12:58 PM, Andrei Borzenkov
<arvidjaar@xxxxxxxxx>

wrote:
Your screenshot shows that kernel panics when starting specific
process
(teamviewerd); you should be able to disable this service.

Oh yes, again a closed source issue. That did the trick. Kernel
4.14.11 boots now with "nopti" option after disabling the service
start

No user space program (provided it does not write to /dev/mem or
something) shall be able to crash the kernel. It is the PTI patchset
suspect here -- there is a lot of issues with that crap arising.

Yup, a sudden increase of posts about freezes, kernel-panic, spontanious
reboots in the forums as well. Both for Tumbleweed and Leap.
Users can test the
nopti
nospec
noefi
boot options by hitting 'e' in GRUB, as a commandline parameter, after
'showopts' .

All these options have been reported to work as well as not to work. Some

report that even booting a previous kernel doesn't work. Of course booting
into a btrfs snapshot does work for those who use btrfs.
FWIW Reported by Debian users as well

no problem here:

Neither here. Just noticed.

> inxi

CPU~Hexa core Intel Core i7 970 (-HT-MCP-) speed/max~1596/3193 MHz
Kernel~4.14.11-1-default x86_64 Up~2:04 Mem~11046.1/36189.5MB
HDD~13638.2GB(10.0% used) Procs~457 Client~Shell inxi~2.3.40
nvidia gt450 and NVIDIA-Linux-x86_64-390.12.run


--
Gertjan Lettink, a.k.a. Knurpht

openSUSE Board Member
openSUSE Forums Team


--
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-factory+owner@xxxxxxxxxxxx

< Previous Next >