Bug 105235 - shutdown gives a NMI and locks (nouveau?)
Summary: shutdown gives a NMI and locks (nouveau?)
Status: RESOLVED INVALID
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/other (show other bugs)
Version: XOrg git
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-02-24 14:07 UTC by Philippe Condé
Modified: 2019-10-14 13:20 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
photo of ht ekernel panic messages/ NMI (1.08 MB, image/jpeg)
2018-02-24 14:07 UTC, Philippe Condé
no flags Details

Description Philippe Condé 2018-02-24 14:07:41 UTC
Created attachment 137579 [details]
photo of ht ekernel panic messages/ NMI

Hello 
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 and two screens
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 with the kernel Panic (jpg)
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
Regards
Philippe
Comment 1 Martin Peres 2019-10-14 13:20:03 UTC
Hi,

Freedesktop's Bugzilla instance is EOLed and open bugs are about to be migrated to http://gitlab.freedesktop.org.

To avoid migrating out of date bugs, I am now closing all the bugs that did not see any activity in the past year. If the issue is still happening, please create a new bug in the relevant project at https://gitlab.freedesktop.org/drm (use misc by default).

Sorry about the noise!


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.