end kernel panic not syncing attempted to kill init exit code 0x00000009 and the pc dont turn off

Bug #1969275 reported by wajih ghai
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Low
Unassigned

Bug Description

the pc can not be turn off untill i will force hiw to push the button for severla second and if not the screen freeze on this bug end kernel panic not syncing attempted to kill init exit code 0x00000009

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-5.4.0-107-generic 5.4.0-107.121~18.04.1
ProcVersionSignature: Ubuntu 5.4.0-107.121~18.04.1-generic 5.4.174
Uname: Linux 5.4.0-107-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.27
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Apr 16 16:32:04 2022
InstallationDate: Installed on 2021-09-23 (205 days ago)
InstallationMedia: Ubuntu 18.04.6 LTS "Bionic Beaver" - Release amd64 (20210915)
SourcePackage: linux-signed-hwe-5.4
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
wajih ghai (romulus23) wrote :
affects: ubuntu → linux-signed-hwe-5.4 (Ubuntu)
Revision history for this message
Mauricio Faria de Oliveira (mfo) wrote :

Thanks for the bug report.

Can you please upload a picture of the screen during freeze?

We need more information from the 'kernel panic' message.

affects: linux-signed-hwe-5.4 (Ubuntu) → linux (Ubuntu)
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
wajih ghai (romulus23) wrote :

ok this is the screen after reboot or shut down

Revision history for this message
wajih ghai (romulus23) wrote :

ok this is the screen after reboot or shut down

Revision history for this message
Mauricio Faria de Oliveira (mfo) wrote (last edit ):

Thanks!

The picture in comment #4 contains the full stack trace.

Some technical analysis for reference. Don't worry about it.
Please see the next comment for suggestions, for now.

...

When returning to userspace from the exit_group() syscall
(as per: orig rax == 0xe7 == 231 -> sys_exit_group; see [1]),
the work to release the last reference to a file closed
(per fput() bits) called into the DRM handling (apparently
the file might be /dev/drm*, I guess), which called into
the _nouveau_driver (the implementation), which owns the
majority of the trace from there.

Finally, the nouveau probably performed an incorrect
memory access (per CR2, showing what seems to be an over
flowed pointer).

This crashed the kernel.

[1]
$ grep 231 git/linux/arch/x86/entry/syscalls/syscall_64.tbl
231 common exit_group sys_exit_group

Revision history for this message
Mauricio Faria de Oliveira (mfo) wrote :

This seems to be a nouveau/nvidia drivers topic.

I'm not a graphics expert, but if I recall correctly,
the opensource `nouveau` driver is usually disabled in
favor of the proprietary `nvidia` drivers, which seem
to work better on the Nvidia cards/gpus.

I can't provide the detailed steps right now, but just
searching for 'how to install nvidia drivers on 18.04'
gave many results which seem to be accurate about
add a PPA, apt install, nouveau check/disable, and done.

That should help you out. :)

Hope this helps!

...

P.S.:

This is not to say the nouveau driver shouldn't be fixed,
but I'd guess that due to the wider/more common usage of
the nvidia drivers, that'd be a lower relative priority.

Changed in linux (Ubuntu):
importance: Undecided → Low
status: Incomplete → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.