System freeze while dbus-daemon execution

Bug #1913933 reported by ch shr
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

I regularly get my system frozen while using. It does not occur on any user interaction I do periodically, so I checked the log files last time it happened:

These are the last 3 kernel log entries before the freeze:

Jan 30 15:34:29 ubuntu kernel: [24749.856278] audit: type=1400 audit(1612017269.344:43): apparmor="DENIED" operation="open" profile="snap.standard-notes.standard-notes" name="/home/chshr/.dotfiles/config/.config/gtk-3.0/settings.ini" pid=21631 comm="standard-notes" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
Jan 30 15:34:29 ubuntu kernel: [24749.903525] audit: type=1107 audit(1612017269.392:44): pid=1236 uid=103 auid=4294967295 ses=4294967295 subj=unconfined msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/" interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" mask="send" name="org.bluez" pid=21631 label="snap.standard-notes.standard-notes"
Jan 30 15:34:29 ubuntu kernel: [24749.903525] exe="/usr/bin/dbus-daemon" sauid=103 hostname=? addr=? terminal=?'
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@

So I think this is related to the dbus-daemon.

If you need any more information, please let me know so I can provide them.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: dbus 1.12.20-1ubuntu1
ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18
Uname: Linux 5.8.0-41-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu50.3
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: GNOME
Date: Sun Jan 31 09:22:49 2021
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=de_DE.UTF-8
 SHELL=/usr/bin/bash
SourcePackage: dbus
UpgradeStatus: Upgraded to groovy on 2021-01-24 (6 days ago)
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu50.3
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: chshr 2241 F.... pulseaudio
 /dev/snd/controlC0: chshr 2241 F.... pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: GNOME
DistroRelease: Ubuntu 20.10
HibernationDevice: RESUME=UUID=a16d1655-2fcf-4952-8a1b-3a45eb9b2c52
MachineType: Micro-Star International Co., Ltd MS-7A34
NonfreeKernelModules: nvidia_modeset nvidia
Package: linux (not installed)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=de_DE.UTF-8
 SHELL=/usr/bin/bash
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-41-generic root=UUID=4542740f-595f-4809-a71b-f170ee2827e3 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18
RelatedPackageVersions:
 linux-restricted-modules-5.8.0-41-generic N/A
 linux-backports-modules-5.8.0-41-generic N/A
 linux-firmware 1.190.3
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: yes
  Hard blocked: no
Tags: groovy
Uname: Linux 5.8.0-41-generic x86_64
UpgradeStatus: Upgraded to groovy on 2021-01-24 (6 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 07/02/2020
dmi.bios.release: 5.14
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: A.LR
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: B350 PC MATE(MS-7A34)
dmi.board.vendor: Micro-Star International Co., Ltd
dmi.board.version: 2.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd
dmi.chassis.version: 2.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.LR:bd07/02/2020:br5.14:svnMicro-StarInternationalCo.,Ltd:pnMS-7A34:pvr2.0:rvnMicro-StarInternationalCo.,Ltd:rnB350PCMATE(MS-7A34):rvr2.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr2.0:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7A34
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 2.0
dmi.sys.vendor: Micro-Star International Co., Ltd

Revision history for this message
ch shr (chshr) wrote :
description: updated
affects: dbus (Ubuntu) → linux (Ubuntu)
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 1913933

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
Revision history for this message
ch shr (chshr) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected
description: updated
Revision history for this message
ch shr (chshr) wrote : CRDA.txt

apport information

Revision history for this message
ch shr (chshr) wrote : CurrentDmesg.txt

apport information

Revision history for this message
ch shr (chshr) wrote : IwConfig.txt

apport information

Revision history for this message
ch shr (chshr) wrote : Lspci.txt

apport information

Revision history for this message
ch shr (chshr) wrote : Lspci-vt.txt

apport information

Revision history for this message
ch shr (chshr) wrote : Lsusb.txt

apport information

Revision history for this message
ch shr (chshr) wrote : Lsusb-t.txt

apport information

Revision history for this message
ch shr (chshr) wrote : Lsusb-v.txt

apport information

Revision history for this message
ch shr (chshr) wrote : PaInfo.txt

apport information

Revision history for this message
ch shr (chshr) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
ch shr (chshr) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
ch shr (chshr) wrote : ProcInterrupts.txt

apport information

Revision history for this message
ch shr (chshr) wrote : ProcModules.txt

apport information

Revision history for this message
ch shr (chshr) wrote : PulseList.txt

apport information

Revision history for this message
ch shr (chshr) wrote : UdevDb.txt

apport information

Revision history for this message
ch shr (chshr) wrote : WifiSyslog.txt

apport information

Revision history for this message
ch shr (chshr) wrote : acpidump.txt

apport information

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
ch shr (chshr)
description: updated
Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :
Revision history for this message
ch shr (chshr) wrote :

Thank you, i did install the latest mainline kernel. Do you need another dump of all the log files?

Or should i now wait if the issue appears again?

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Just wait until the issue re-appeared.

Revision history for this message
ch shr (chshr) wrote :

Hey, I just wanted to say the issue reappears again. Not on a regular basis, quite random. I am trying to figure out, when it occurs and if it's a hardware issue.

Revision history for this message
ch shr (chshr) wrote :

Hi update from my site:

so I think the issue might be unrelated to dbus-daemon. Why do I think that?

* I installed Linux Mint 20.1 on the same machine, reasons do not matter here
* I got the same freezes on the system
* I updated the kernel to 5.11 and still have the same freezes happen every other day.

It happens randomly and the syslog always has these ascii NUL characters, but I learned that this is just a symptom rather than a cause.

I will do a memtest soon so I can see if this is faulty hardware (though the Windows 10 installation on a separate disk works just fine).

Cheers

Revision history for this message
ch shr (chshr) wrote :

Ok I upgraded from Linuxmint 20.1 to 20.2 yesterday and everything went smooth. But unfortunately the freeze is back. This time, the system rebooted automatically, so no hard freeze.
On startup I got the following error on screen short before the OS boots:

[ 0.116029] mce: [Hardware Error]: Machine check events logged
[ 0.116031] mce: [Hardware Error]: CPU 2: Machine Check: 0 Bank 5: bea0000000000108
[ 0.116036] mce: [Hardware Error]: TSC 0 ADDR 1ffffa3166546 MISC d0130fff00000000 SYND 4d000000 IPID 500b000000000
[ 0.116040] mce: [Hardware Error]: PROCESSOR 2:800f11 TIME 1625854872 SOCKET 0 APIC 4 microcode 8001138
[ 0.124031] mce: [Hardware Error]: Machine check events logged
[ 0.124032] mce: [Hardware Error]: CPU 5: Machine Check: 0 Bank 5: bea0000000000108
[ 0.124035] mce: [Hardware Error]: TSC 0 ADDR 1ffffa28ec31c MISC d0130fff00000000 SYND 4d000000 IPID 500b000000000
[ 0.124040] mce: [Hardware Error]: PROCESSOR 2:800f11 TIME 1625854872 SOCKET 0 APIC c microcode 8001138
[ 0.467090] RAS: Correctable Errors collector initialized.

But I cannot get any conclusion from this other than there is something wrong with the CPU. Is this related to the kernel then and is this here the right place to post this? If no, where could I look for more information on this?

Revision history for this message
ch shr (chshr) wrote :

Edit: This information is also written to the kernel.log and was not written there before the upgrade to Linuxmint 20.1. The kernel version I am running now is 5.11.0-22-generic. I upgraded to this same kernel already a few weeks ago still on Mint 20.1

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

IIRC the CPU power saving on first gen Ryzen needs to be disabled to get a stable system...

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.