Bug 1081450

Summary: <During shutdown system locks with NMI
Product: [openSUSE] openSUSE Tumbleweed Reporter: Philippe Condé <conde.philippe>
Component: KernelAssignee: E-mail List <kernel-maintainers>
Status: RESOLVED FIXED QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P5 - None CC: conde.philippe, tiwai
Version: CurrentFlags: tiwai: needinfo? (conde.philippe)
Target Milestone: ---   
Hardware: x86-64   
OS: openSUSE Factory   
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: screenshot Kernel panic nmi

Description Philippe Condé 2018-02-18 07:06:18 UTC
Created attachment 760479 [details]
screenshot  Kernel panic nmi

With all kernels 4.l5 when I start a shutdown with "shutdown -r now" from the console (ALT-CRL-F1) I receive a kernel panic with a NMI.

System is a HP proliant ML350p with tumbleweed with default kernel.
System updated always with "zypper dup"

No message in logs found

Video is a Nvidia Quadro 4100m running with nouveau driver.
last line on screen is 
nouveau:0000:0a:00.0 DRM: GPU Lockup _ switching to software fbcon

After some time (10-15 seconds) the system starts all fans at maximum speed.

I must then do a hard reset.

I attach here a screenshot of with the kernel Panic
Current kernel
Linux hpprol2 4.15.3-1-default #1 SMP PREEMPT Tue Feb 13 07:58:49 UTC 2018 (8d4f579) x86_64 x86_64 x86_64 GNU/Linux

Comment 1 Takashi Iwai 2018-02-22 16:40:34 UTC
Possibly some nouveau regression in 4.15, I remember of a similar other bug report, too.
Comment 2 Takashi Iwai 2018-02-22 16:41:40 UTC
Does it happen always?  If yes, it's worth to report to upstream, e.g. bugzilla.freedesktop.org (component DRI/Nouveau).  Care to report it there?
Comment 3 Philippe Condé 2018-02-22 22:30:31 UTC

yes it occurs always. last kernel tested is  
4.15.4-1-default #1 SMP PREEMPT Sat Feb 17 09:02:00 UTC 2018 (7169cf1) x86_64 x86_64 x86_64 GNU/Linux.

I suppose that I need to create an account on bugzilla.freedesktop.org and then  report the  problem

Comment 4 Philippe Condé 2018-03-14 20:42:31 UTC

Problem is solved with new kernel 4.15.6.

Philippe Condé.