Kernel Panic with snapshot 20180104

classic Classic list List threaded Threaded
25 messages Options
12
Reply | Threaded
Open this post in threaded view
|

Kernel Panic with snapshot 20180104

Stratos Zolotas
Hi,

I'm getting an always reproducible kernel panic and the system is not
bootable with kernel 4.14.11. Booting with 4.14.9 works.

Was only able to take a photo....

https://photos.app.goo.gl/CplKIGQy6tnvM2c83

Anyone else experiencing this or any hint on what to look?

Stratos.
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Kernel Panic with snapshot 20180104

Jiri Slaby-6
On 01/07/2018, 10:17 AM, Stratos Zolotas wrote:

> Hi,
>
> I'm getting an always reproducible kernel panic and the system is not
> bootable with kernel 4.14.11. Booting with 4.14.9 works.
>
> Was only able to take a photo....
>
> https://photos.app.goo.gl/CplKIGQy6tnvM2c83
>
> Anyone else experiencing this or any hint on what to look?

Could you try to boot with "nopti" kernel option?

Is 4.14.12 better?

thanks,
--
js
suse labs
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Kernel Panic with snapshot 20180104

Stratos Zolotas
On Sun, Jan 7, 2018 at 11:59 AM, Jiri Slaby <[hidden email]> wrote:
> Could you try to boot with "nopti" kernel option?
>

With "nopti" 4.14.11 boots ok.

> Is 4.14.12 better?
>

From which repo should I try 4.14.12 in case it works without the
extra kernel option?

Thanks.
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Kernel Panic with snapshot 20180104

Basil Chupin-2
In reply to this post by Stratos Zolotas
On 07/01/18 20:17, Stratos Zolotas wrote:

> Hi,
>
> I'm getting an always reproducible kernel panic and the system is not
> bootable with kernel 4.14.11. Booting with 4.14.9 works.
>
> Was only able to take a photo....
>
> https://photos.app.goo.gl/CplKIGQy6tnvM2c83
>
> Anyone else experiencing this or any hint on what to look?
>
> Stratos.

Ooops...I just realised that this is Factory list so we are talking here
Tumbleweed, right?

Well, I *still* get this in LEAP 42.3 but not anymore in TW. In TW I am
now running kernel 4.14.12.x *AND* the new BETA version of the nVidia
driver -- 390.12 -- and the nvidia driver compiles and the TW boots
without any problems. (But I haven't allowed TW to be updated to the
latest 'snapshot' -- I might just forego this while the going is good.)

In Leap 42.3 I am also using nvidia driver 390.12 and kernel 4.14.12.0
and I get the error msg you mention above. However, I can compile the
nvidia driver and get 42.3 to boot by using adding to the command line
which compiles the nvidia driver: '--no-unified-memory'.

And this what has got me absolutely bamboozled: both Leap 42.3 and TW
are installed on the same desktop and yet Leap stuffs-up while TW I
managed to get working.

BC


--
Always be nice to people on your way up -- you'll see
the same people on your way down.

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Kernel Panic with snapshot 20180104

Frank Krüger
In reply to this post by Stratos Zolotas
Am 07.01.2018 um 11:12 schrieb Stratos Zolotas:

> On Sun, Jan 7, 2018 at 11:59 AM, Jiri Slaby <[hidden email]> wrote:
>> Could you try to boot with "nopti" kernel option?
>>
>
> With "nopti" 4.14.11 boots ok.
>
>> Is 4.14.12 better?
>>
>
> From which repo should I try 4.14.12 in case it works without the
> extra kernel option?
>
> Thanks.
>
https://download.opensuse.org/repositories/Kernel:/stable/standard/
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Kernel Panic with snapshot 20180104

Stratos Zolotas
Kernel 4.14.12 fails even with "nopti" option for me...

On Sun, Jan 7, 2018 at 12:19 PM, Frank Krüger <[hidden email]> wrote:

> Am 07.01.2018 um 11:12 schrieb Stratos Zolotas:
>> On Sun, Jan 7, 2018 at 11:59 AM, Jiri Slaby <[hidden email]> wrote:
>>> Could you try to boot with "nopti" kernel option?
>>>
>>
>> With "nopti" 4.14.11 boots ok.
>>
>>> Is 4.14.12 better?
>>>
>>
>> From which repo should I try 4.14.12 in case it works without the
>> extra kernel option?
>>
>> Thanks.
>>
> https://download.opensuse.org/repositories/Kernel:/stable/standard/
> --
> To unsubscribe, e-mail: [hidden email]
> To contact the owner, e-mail: [hidden email]
>
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Kernel Panic with snapshot 20180104

Jiri Slaby-6
In reply to this post by Stratos Zolotas
On 01/07/2018, 11:12 AM, Stratos Zolotas wrote:
> On Sun, Jan 7, 2018 at 11:59 AM, Jiri Slaby <[hidden email]> wrote:
>> Could you try to boot with "nopti" kernel option?
>>
>
> With "nopti" 4.14.11 boots ok.

Can you provide us with your /proc/cpuinfo?

>> Is 4.14.12 better?
>>
>
> From which repo should I try 4.14.12 in case it works without the
> extra kernel option?

It is in Kernel:stable yet, pending for tumbleweed:
https://build.opensuse.org/project/monitor?project=Kernel%3Astable

--
js
suse labs
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Kernel Panic with snapshot 20180104

Stratos Zolotas
On Sun, Jan 7, 2018 at 12:46 PM, Jiri Slaby <[hidden email]> wrote:
>
> Can you provide us with your /proc/cpuinfo?
>

AMD FX-8350

cat /proc/cpuinfo
processor       : 0
vendor_id       : AuthenticAMD
cpu family      : 21
model           : 2
model name      : AMD FX(tm)-8350 Eight-Core Processor
stepping        : 0
microcode       : 0x600084f
cpu MHz         : 2100.000
cache size      : 2048 KB
physical id     : 0
siblings        : 8
core id         : 0
cpu cores       : 4
apicid          : 16
initial apicid  : 0
fpu             : yes
fpu_exception   : yes
cpuid level     : 13
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext
fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc
cpuid extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16
sse4_1 sse4_2 popcnt aes xsave avx f16c lahf_lm cmp_legacy svm extapic
cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs xop skinit wdt
lwp fma4 tce nodeid_msr tbm topoext perfctr_core perfctr_nb cpb
hw_pstate vmmcall bmi1 arat npt lbrv svm_lock nrip_save tsc_scale
vmcb_clean flushbyasid decodeassists pausefilter pfthreshold
bugs            : fxsave_leak sysret_ss_attrs null_seg cpu_insecure
bogomips        : 8037.21
TLB size        : 1536 4K pages
clflush size    : 64
cache_alignment : 64
address sizes   : 48 bits physical, 48 bits virtual
power management: ts ttp tm 100mhzsteps hwpstate cpb eff_freq_ro
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Kernel Panic with snapshot 20180104

Andrei Borzenkov
In reply to this post by Stratos Zolotas
07.01.2018 12:17, Stratos Zolotas пишет:
> Hi,
>
> I'm getting an always reproducible kernel panic and the system is not
> bootable with kernel 4.14.11.

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

B> ooting with 4.14.9 works.
>
> Was only able to take a photo....
>
> https://photos.app.goo.gl/CplKIGQy6tnvM2c83
>
> Anyone else experiencing this or any hint on what to look?
>
> Stratos.
>

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Kernel Panic with snapshot 20180104

Stratos Zolotas
On Sun, Jan 7, 2018 at 12:58 PM, Andrei Borzenkov <[hidden email]> 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.

Thanks!
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Kernel Panic with snapshot 20180104

Jiri Slaby-6
On 01/07/2018, 12:07 PM, Stratos Zolotas wrote:
> On Sun, Jan 7, 2018 at 12:58 PM, Andrei Borzenkov <[hidden email]> 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.

--
js
suse labs
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Kernel Panic with snapshot 20180104

Jiri Slaby-6
In reply to this post by Stratos Zolotas
On 01/07/2018, 11:41 AM, Stratos Zolotas wrote:
> Kernel 4.14.12 fails even with "nopti" option for me...

Which is bad as nopti is implicitly set for all AMD cpus since 4.14.12.

Could you take a photo again?

thanks,
--
js
suse labs
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Kernel Panic with snapshot 20180104

Stratos Zolotas
On Sun, Jan 7, 2018 at 2:54 PM, Jiri Slaby <[hidden email]> wrote:
>
> Could you take a photo again?
>

With kernel 4.14.12 and teamviewrd service enabled.

https://photos.app.goo.gl/Z6T7K54IzHfah40Z2
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Kernel Panic with snapshot 20180104

Knurpht-openSUSE
In reply to this post by Jiri Slaby-6
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 <[hidden email]>
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

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

openSUSE Board Member
openSUSE Forums Team


--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Kernel Panic with snapshot 20180104

Patrick Shanahan-2
* Knurpht - Gertjan Lettink <[hidden email]> [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 <[hidden email]>
> 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:
  > 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
 
--
(paka)Patrick Shanahan       Plainfield, Indiana, USA          @ptilopteri
http://en.opensuse.org    openSUSE Community Member    facebook/ptilopteri
Registered Linux User #207535                    @ http://linuxcounter.net
Photos: http://wahoo.no-ip.org/piwigo                    paka @ IRCnet freenode
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Kernel Panic with snapshot 20180104

John Paul Adrian Glaubitz
In reply to this post by Stratos Zolotas
Hi Stratos!

On 01/07/2018 10:17 AM, Stratos Zolotas wrote:
> Was only able to take a photo....
>
> https://photos.app.goo.gl/CplKIGQy6tnvM2c83
>
> Anyone else experiencing this or any hint on what to look?

On a sidenote: A very useful feature of the Linux kernel in these situations
is the netconsole [1] which allows to use a second computer on the network as a
text terminal for the early kernel boot and is very helpful to capture kernel
backraces in case of a panic.

Adrian

> [1] https://wiki.archlinux.org/index.php/Netconsole
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Kernel Panic with snapshot 20180104

Knurpht-openSUSE
In reply to this post by Patrick Shanahan-2
Op zondag 7 januari 2018 18:18:48 CET schreef Patrick Shanahan:

> * Knurpht - Gertjan Lettink <[hidden email]> [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
> > > > <[hidden email]>
> >
> > 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: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Kernel Panic with snapshot 20180104

Andrei Borzenkov
In reply to this post by Knurpht-openSUSE
07.01.2018 19:03, Knurpht - Gertjan Lettink пишет:

> 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 <[hidden email]>
> 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
>

There is also at least one report that latest Intel microcode results in
unbootable system:

https://bugzilla.opensuse.org/show_bug.cgi?id=1074919.
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Kernel Panic with snapshot 20180104

John Paul Adrian Glaubitz
In reply to this post by Stratos Zolotas
On 01/07/2018 11:57 AM, Stratos Zolotas wrote:
> On Sun, Jan 7, 2018 at 12:46 PM, Jiri Slaby <[hidden email]> wrote:
>>
>> Can you provide us with your /proc/cpuinfo?
>>
>
> AMD FX-8350

You should be safe turning PTI off permanently on AMD CPUs, it is
actually disabled by default on AMD CPUs in recent kernels [1].

Nevertheless, please file a bug report, preferably in the upstream
kernel bug tracker reporting this issue.

Adrian

> [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=694d99d40972f12e59a3696effee8a376b79d7c8
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Kernel Panic with snapshot 20180104

ASSI
In reply to this post by Jiri Slaby-6
Jiri Slaby writes:
> Could you try to boot with "nopti" kernel option?

That saved me today when I tried to update my old Athlon64 based machine
from 20180104 to 20180109.  It would always panic after the installation
of a 32bit package from Gtk.

> Is 4.14.12 better?

Looks good so far, but I haven't run many things.


Regards
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

DIY Stuff:
http://Synth.Stromeko.net/DIY.html

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

12