supervisor write access in kernel mode

Bug #1885031 reported by Martin Gerdzhev
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

machine froze. Only mouse could be moved.

BUG: kernel NULL pointer dereference, address: 0000000000000000
Jun 24 18:56:43 MartoBeast kernel: #PF: supervisor write access in kernel mode
Jun 24 18:56:43 MartoBeast kernel: #PF: error_code(0x0002) - not-present page

Ubuntu 20.04

Linux MartoBeast 5.4.0-37-generic #41-Ubuntu SMP Wed Jun 3 18:57:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: martin 2649 F.... pulseaudio
 /dev/snd/controlC0: martin 2649 F.... pulseaudio
 /dev/snd/controlC2: martin 2649 F.... pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2019-12-08 (199 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
IwConfig:
 enp4s0 no wireless extensions.

 lo no wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ELITE
NonfreeKernelModules: nvidia_modeset nvidia
Package: linux (not installed)
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=05d2cb45-6b9c-47b3-8102-e6c6a13de26b ro quiet splash acpi_enforce_resources=lax vt.handoff=7
ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-37-generic N/A
 linux-backports-modules-5.4.0-37-generic N/A
 linux-firmware 1.187
RfKill:
 0: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no
Tags: focal
Uname: Linux 5.4.0-37-generic x86_64
UpgradeStatus: Upgraded to focal on 2020-04-24 (61 days ago)
UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo vboxusers
_MarkForUpload: True
dmi.bios.date: 12/06/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F11
dmi.board.asset.tag: Default string
dmi.board.name: X570 AORUS ELITE
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF11:bd12/06/2019:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSELITE:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSELITE:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: Default string
dmi.product.name: X570 AORUS ELITE
dmi.product.sku: Default string
dmi.product.version: -CF
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

Revision history for this message
Martin Gerdzhev (mgerdzhev) wrote :
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1885031

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
tags: added: focal
Revision history for this message
Martin Gerdzhev (mgerdzhev) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected
description: updated
Revision history for this message
Martin Gerdzhev (mgerdzhev) wrote : CRDA.txt

apport information

Revision history for this message
Martin Gerdzhev (mgerdzhev) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Martin Gerdzhev (mgerdzhev) wrote : Lspci.txt

apport information

Revision history for this message
Martin Gerdzhev (mgerdzhev) wrote : Lspci-vt.txt

apport information

Revision history for this message
Martin Gerdzhev (mgerdzhev) wrote : Lsusb.txt

apport information

Revision history for this message
Martin Gerdzhev (mgerdzhev) wrote : Lsusb-t.txt

apport information

Revision history for this message
Martin Gerdzhev (mgerdzhev) wrote : Lsusb-v.txt

apport information

Revision history for this message
Martin Gerdzhev (mgerdzhev) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Martin Gerdzhev (mgerdzhev) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
Martin Gerdzhev (mgerdzhev) wrote : ProcEnviron.txt

apport information

Revision history for this message
Martin Gerdzhev (mgerdzhev) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Martin Gerdzhev (mgerdzhev) wrote : ProcModules.txt

apport information

Revision history for this message
Martin Gerdzhev (mgerdzhev) wrote : PulseList.txt

apport information

Revision history for this message
Martin Gerdzhev (mgerdzhev) wrote : UdevDb.txt

apport information

Revision history for this message
Martin Gerdzhev (mgerdzhev) wrote : WifiSyslog.txt

apport information

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Mauricio Faria de Oliveira (mfo) wrote :

Hi Martin,

Could you please test if the problem still happens with the latest kernel version in focal-proposed? (currently 5.4.0-40-generic)

Something along these lines,

$ echo 'deb http://archive.ubuntu.com/ubuntu bionic-proposed main restricted' | sudo tee /etc/apt/sources.list.d/proposed.list
$ sudo apt update
$ sudo apt install linux-generic
$ sudo rm /etc/apt/sources.list.d/proposed.list

And reboot. You can confirm the running kernel version with:

$ uname -rv

Reference:
https://wiki.ubuntu.com/Testing/EnableProposed

Thanks!

Revision history for this message
Martin Gerdzhev (mgerdzhev) wrote :

Hi Mauricio,
Looks like the latest that I see is 5.4.0-39-generic
Should I still go ahead with that?

Revision history for this message
Martin Gerdzhev (mgerdzhev) wrote :

Nevermind I had to enable the proposed as well.
Installing it now. I will report if I get that issue again.

Revision history for this message
Martin Gerdzhev (mgerdzhev) wrote :

So far haven't been able to reproduce this again.

uname -rv:
`5.4.0-40-generic #44-Ubuntu SMP Tue Jun 23 00:01:04 UTC 2020`

Will update if it happens again.

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

Martin, thanks.

I'll set the bug status to Incomplete for now,
and we can change it if you hit the issue again.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Martin Gerdzhev (mgerdzhev) wrote :

Looks like I still run into this.
I am on 5.4.0-44-generic.
See attached log

Revision history for this message
Mauricio Faria de Oliveira (mfo) wrote :
Download full text (3.7 KiB)

Hey Martin.

The issues reported on comment 1 and commment 24 have different stack trace signatures, and do not seem to be the same issue at all.

I'll thus mark this bug as Invalid as apparently you couldn't reproduce the original issue anymore.

If the new issue is still present with the latest 5.4 kernel in -updates, please feel free to report a new bug.

Thank you!

...

comment 1:

Jun 24 18:56:43 MartoBeast kernel: BUG: kernel NULL pointer dereference, address: 0000000000000000
Jun 24 18:56:43 MartoBeast kernel: #PF: supervisor write access in kernel mode
Jun 24 18:56:43 MartoBeast kernel: #PF: error_code(0x0002) - not-present page
Jun 24 18:56:43 MartoBeast kernel: PGD 0 P4D 0
Jun 24 18:56:43 MartoBeast kernel: Oops: 0002 [#1] SMP NOPTI
Jun 24 18:56:43 MartoBeast kernel: CPU: 4 PID: 114660 Comm: sshd Tainted: P OE 5.4.0-37-generic #41-Ubuntu
Jun 24 18:56:43 MartoBeast kernel: Hardware name: Gigabyte Technology Co., Ltd. X570 AORUS ELITE/X570 AORUS ELITE, BIOS F11 12/06/2019
Jun 24 18:56:43 MartoBeast kernel: RIP: 0010:__rb_erase_color+0x1aa/0x280
...
Jun 24 18:56:43 MartoBeast kernel: Call Trace:
Jun 24 18:56:43 MartoBeast kernel: vma_interval_tree_remove+0x1a0/0x2b0
Jun 24 18:56:43 MartoBeast kernel: __remove_shared_vm_struct+0x32/0x40
Jun 24 18:56:43 MartoBeast kernel: unlink_file_vma+0x41/0x60
Jun 24 18:56:43 MartoBeast kernel: free_pgtables+0x9b/0xf0
Jun 24 18:56:43 MartoBeast kernel: exit_mmap+0xc7/0x1b0
Jun 24 18:56:43 MartoBeast kernel: mmput+0x5d/0x130
Jun 24 18:56:43 MartoBeast kernel: do_exit+0x2fd/0xac0
Jun 24 18:56:43 MartoBeast kernel: ? kill_something_info+0x145/0x170
Jun 24 18:56:43 MartoBeast kernel: do_group_exit+0x47/0xb0
Jun 24 18:56:43 MartoBeast kernel: __x64_sys_exit_group+0x18/0x20
Jun 24 18:56:43 MartoBeast kernel: do_syscall_64+0x57/0x190
Jun 24 18:56:43 MartoBeast kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9
Jun 24 18:56:43 MartoBeast kernel: RIP: 0033:0x7f52319de136

comment 24:

Aug 21 00:04:56 MartoBeast kernel: BUG: unable to handle page fault for address: 0000000900000b64
Aug 21 00:04:56 MartoBeast kernel: #PF: supervisor write access in kernel mode
Aug 21 00:04:56 MartoBeast kernel: #PF: error_code(0x0002) - not-present page
Aug 21 00:04:56 MartoBeast kernel: PGD 0 P4D 0
Aug 21 00:04:56 MartoBeast kernel: Oops: 0002 [#3] SMP NOPTI
Aug 21 00:04:56 MartoBeast kernel: CPU: 3 PID: 4610 Comm: threaded-ml Tainted: P D OE 5.4.0-44-generic #48-Ubuntu
Aug 21 00:04:56 MartoBeast kernel: Hardware name: Gigabyte Technology Co., Ltd. X570 AORUS ELITE/X570 AORUS ELITE, BIOS F20b 07/02/2020
Aug 21 00:04:56 MartoBeast kernel: RIP: 0010:_raw_spin_lock_irqsave+0x23/0x40
...
Aug 21 00:04:56 MartoBeast kernel: Call Trace:
Aug 21 00:04:56 MartoBeast kernel: try_to_wake_up+0x4e/0x6a0
Aug 21 00:04:56 MartoBeast kernel: ? poll_select_finish+0x210/0x210
Aug 21 00:04:56 MartoBeast kernel: ? ttwu_do_wakeup+0x10d/0x150
Aug 21 00:04:56 MartoBeast kernel: default_wake_function+0x12/0x20
Aug 21 00:04:56 MartoBeast kernel: pollwake+0x72/0x90
Aug 21 00:04:56 MartoBeast kernel: ? wake_up_q+0x70/0x70
Aug 21 00:04:56 MartoBeast kernel: __wake_up_common+0x7e/0x140
Aug 21 00:04:56 MartoBeast...

Read more...

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