BUG: unable to handle kernel NULL pointer dereference at 0000000000000070

Bug #1765683 reported by Hicham Ben
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Hard to forcefully reboot ubuntu after starting it up.
No clue what caused this.

ProblemType: KernelOops
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-15-generic 4.15.0-15.16
ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
Uname: Linux 4.15.0-15-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
Annotation: Your system might become unstable now and might need to be restarted.
ApportVersion: 2.20.9-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: gdm 1139 F.... pulseaudio
                      hicham 1716 F.... pulseaudio
 /dev/snd/controlC0: gdm 1139 F.... pulseaudio
                      hicham 1716 F.... pulseaudio
Date: Fri Apr 20 13:31:11 2018
DuplicateSignature: BUG: unable to handle kernel NULL pointer dereference at location RIP: _nv002366kms+0x5e/0x100 [nvidia_modeset] RSP: ffff9a7cc312fd00
Failure: oops
InstallationDate: Installed on 2018-04-18 (2 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
IwConfig:
 enp0s31f6 no wireless extensions.

 lo no wireless extensions.
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-15-generic.efi.signed root=UUID=d5f38b3a-0e58-474f-9b1f-f0c6a3e1a509 ro quiet splash vt.handoff=1
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: kerneloops-daemon N/A
RfKill:

SourcePackage: linux
Title: BUG: unable to handle kernel NULL pointer dereference at 0000000000000070
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/24/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P7.30
dmi.board.name: Z170 Extreme3
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP7.30:bd11/24/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ170Extreme3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

Revision history for this message
Hicham Ben (maghrebi-h) wrote :
tags: removed: need-duplicate-check
Revision history for this message
Hicham Ben (maghrebi-h) wrote :

To write more properly:
I started my system up, logged in with my credentials and after that was successfull I was stuck in a black screen for a long period of time. 5-8 mins.
I force shut down my system and rebooted.
Then it actually worked.

Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Can you reproduce this bug, or was it a one time event?

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
Hicham Ben (maghrebi-h) wrote :

I believe it was a one time event.
The last reboot before it, I finished updating my system and shut it off correctly.
So this happened right after the next boot.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
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.