You are not logged in.

#1 2022-08-19 14:28:06

fistrosan
Member
Registered: 2020-04-01
Posts: 171

Help diagnosing computer freezes

From a few days now I have been having seemingly random freezes in my laptop. It usually happened while I was afk so I did not know exactly when it occurred. Today however it happened right before my eyes so I could look at the time stamp in the journal. It happened sometime between 16:03 and 16:06 but I am at a loss as to what the problem is. Seems like it could be related to upower.service but I am not exactly sure. Any help interpreting what the journal says is welcome ! Thanks !

https://0x0.st/oLEy.txt

Offline

#2 2022-08-19 15:09:08

schard
Forum Moderator
From: Hannover
Registered: 2016-05-06
Posts: 1,975
Website

Re: Help diagnosing computer freezes

You got several kernel NULL pointer dereferences in the journal. One around the time your system allegedly froze:

Aug 19 16:03:21 archx1 kernel: BUG: kernel NULL pointer dereference, address: 0000000000000000

Which kernel are you using?


macro_rules! yolo { { $($tokens:tt)* } => { unsafe { $($tokens)* } }; }

Offline

#3 2022-08-19 15:13:49

fistrosan
Member
Registered: 2020-04-01
Posts: 171

Re: Help diagnosing computer freezes

According to uname it's: 5.19.1-arch2-1. Have not upgraded to 5.19.2-arch1-1 just yet. If it is a kernel issue I can try to book with the LTS and see if it still freezes.

Offline

#4 2022-08-19 16:03:33

loqs
Member
Registered: 2014-03-06
Posts: 17,321

Re: Help diagnosing computer freezes

The start of the boot is missing from the journal.  Can you provide that?

Offline

#5 2022-08-19 19:07:22

fistrosan
Member
Registered: 2020-04-01
Posts: 171

Re: Help diagnosing computer freezes

loqs: I can ofc. But maybe you can do something with the available forced boot at 16:10 that comes right after the system froze and is included in the current link ? otherwise I will look for the initial boot which was several hours before ...

Offline

#6 2022-08-19 19:55:10

loqs
Member
Registered: 2014-03-06
Posts: 17,321

Re: Help diagnosing computer freezes

You can filter the journal by boot if it helps., `journalctl -b -1` where -1 is the last boot -2 the boot before that e.t.c..  I wanted to see if the kernel oops at the top of the posted journal is the first one for that boot.
After the reboot picom crashed but the kernel did not.  Unfortunately the system uses multiple out of tree modules that taint the kernel so it may prove more difficult to obtain support if it is a kernel issue.
Edit:
Subsequent crashes can be the result of corruption caused by the initial crash which could be in an unrelated part of the kernel.

Last edited by loqs (2022-08-19 20:01:59)

Offline

#7 2022-08-19 21:37:09

fistrosan
Member
Registered: 2020-04-01
Posts: 171

Re: Help diagnosing computer freezes

loqs: here it is. The boot was around 12:55 and the crash/freeze was at 16:05 (roundabout). I see lots of errors from an old udev rule I made to control the screen brightness but I think this is unrelated. I can see also that the NULL pointer issue mentioned by schard above happens pretty much every 3 minutes.

http://0x0.st/oLUg.txt

Thanks for taking the time to look into this.

Offline

#8 2022-08-21 05:45:48

loqs
Member
Registered: 2014-03-06
Posts: 17,321

Re: Help diagnosing computer freezes

Diagnostic patch adding lots of print calls

diff --git a/drivers/power/supply/power_supply_sysfs.c b/drivers/power/supply/power_supply_sysfs.c
index 4239591e1522..9ba375e8dd4f 100644
--- a/drivers/power/supply/power_supply_sysfs.c
+++ b/drivers/power/supply/power_supply_sysfs.c
@@ -273,15 +273,21 @@ static ssize_t power_supply_show_property(struct device *dev,
 					  struct device_attribute *attr,
 					  char *buf) {
 	ssize_t ret;
+	pr_info("dev ptr %px,  attr ptr %px.\n",dev,attr);
 	struct power_supply *psy = dev_get_drvdata(dev);
+	pr_info("psy ptr %px.\n",psy);
 	struct power_supply_attr *ps_attr = to_ps_attr(attr);
+	pr_info("ps_attr ptr %px.\n",ps_attr);
 	enum power_supply_property psp = dev_attr_psp(attr);
+	pr_info("psp set.\n");
 	union power_supply_propval value;
 
 	if (psp == POWER_SUPPLY_PROP_TYPE) {
+		pr_info("psp == POWER_SUPPLY_PROP_TYPE.\n");
 		value.intval = psy->desc->type;
 	} else {
 		ret = power_supply_get_property(psy, psp, &value);
+		pr_info("power_supply_get_property return %zx.\n",ret);
 
 		if (ret < 0) {
 			if (ret == -ENODATA)
@@ -302,13 +308,16 @@ static ssize_t power_supply_show_property(struct device *dev,
 
 	switch (psp) {
 	case POWER_SUPPLY_PROP_USB_TYPE:
+		pr_info("psp == POWER_SUPPLY_PROP_USB_TYPE.\n");
 		ret = power_supply_show_usb_type(dev, psy->desc,
 						&value, buf);
 		break;
 	case POWER_SUPPLY_PROP_MODEL_NAME ... POWER_SUPPLY_PROP_SERIAL_NUMBER:
+		pr_info("psp == POWER_SUPPLY_PROP_MODEL_NAME ... POWER_SUPPLY_PROP_SERIAL_NUMBER.\n");
 		ret = sprintf(buf, "%s\n", value.strval);
 		break;
 	default:
+		pr_info("psp default case.\n");
 		ret = sprintf(buf, "%d\n", value.intval);
 	}
 

kernel with patch applied
https://drive.google.com/file/d/1iJZkCw … sp=sharing linux-5.19.2.arch1-2.2-x86_64.pkg.tar.zst
https://drive.google.com/file/d/1V6C0_O … sp=sharing linux-headers-5.19.2.arch1-2.2-x86_64.pkg.tar.zst

Offline

#9 2022-08-21 07:27:41

seth
Member
Registered: 2012-09-03
Posts: 51,017

Re: Help diagnosing computer freezes

There's also an enourmous amount of

Process '/bin/chgrp wheel /sys/class/backlight/intel_backlight/brightness' failed with exit code 1.

I assume there's now "acpi_video0" instead of "intel_backlight"?
Might relate to https://bbs.archlinux.org/viewtopic.php?id=278933 - is the battery/power supply correctly updated?

Offline

#10 2022-08-21 14:53:23

fistrosan
Member
Registered: 2020-04-01
Posts: 171

Re: Help diagnosing computer freezes

Loqs and Seth. Thanks again. Let me see.
a) It is intel_backlight actually. I don't know why the udev rule I have set up spits out so many exit codes, but it is doing what it is supposed to do: change the group ownership in /sys/class/backlight/intel_backlight/brightness to wheel so that I can, as non-root, change the brightness in my laptop screen. I just checked and the group is root,wheel (whereas otherwise should be root,root), I tested it with echo 0 >  /sys/class/backlight/intel_backlight/brightness as a regular user and the screen goes blank.
b) In my case the battery status is updated correctly. Just tested it.
c) However, from what I understand from loqs message there seems to be some bug in the kernel pertaining the power supply (?). That could be consistent with the fact that the laptop never freezes while on regular power supply of 135 W. However, it freezes mostly at work where I am connected with a double power supply (135W and 60 W) via the thunderbolt docking station ... maybe it makes sense, dunno ... At any rate loqs, I can use makepkg to install the patched kernel ? will that automatically create the images in /boot or should I create those myself with mkinitcpio ? Will this patch appear upstream and be included in future updates with pacman ?
Thanks again to you both.

Offline

#11 2022-08-21 15:56:31

seth
Member
Registered: 2012-09-03
Posts: 51,017

Re: Help diagnosing computer freezes

You can install the linked packages w/ "pacman -U"

Offline

#12 2022-08-25 15:53:29

Avatar
Member
Registered: 2010-04-02
Posts: 31

Re: Help diagnosing computer freezes

Hi,

I hope it's okay for me to jump in on the thread. I've been plagued by what I think is the same issue on my Lenovo T580, kernel 5.19.3-arch1-1.
The hang is rather random and happens perhaps once or twice during a working day. If I leave my laptop on during the night, I've found it in that state every morning.
When I power cycle after the hang has happened I see nothing of interest in the kernel log about the oops.
I do however see similar kernel oops in the current boot:
journalctl -b 0
https://0x0.st/o9gx.txt

Would it be useful for me build a kernel with the above patch?
I'm not sure if my case matches closely enough.
Let me know if I can provide any additional info

Regards,

Offline

#13 2022-08-25 18:22:52

seth
Member
Registered: 2012-09-03
Posts: 51,017

Re: Help diagnosing computer freezes

Aug 25 17:38:46 naix kernel: BUG: kernel NULL pointer dereference, address: 0000000000000000
Aug 25 17:38:46 naix kernel: #PF: supervisor instruction fetch in kernel mode
Aug 25 17:38:46 naix kernel: #PF: error_code(0x0010) - not-present page
Aug 25 17:38:46 naix kernel: PGD 0 P4D 0 
Aug 25 17:38:46 naix kernel: Oops: 0010 [#1] PREEMPT SMP PTI
Aug 25 17:38:46 naix kernel: CPU: 0 PID: 633 Comm: upowerd Not tainted 5.19.3-arch1-1 #1 83cb97ae0c76841ed5ae1e3429386aa2a602dddd
Aug 25 17:38:46 naix kernel: Hardware name: LENOVO 20L90044ZA/20L90044ZA, BIOS N27ET35W (1.21 ) 04/30/2019
Aug 25 17:38:46 naix kernel: RIP: 0010:0x0
Aug 25 17:38:46 naix kernel: Code: Unable to access opcode bytes at RIP 0xffffffffffffffd6.
Aug 25 17:38:46 naix kernel: RSP: 0018:ffffc304c0ea3c88 EFLAGS: 00010202
Aug 25 17:38:46 naix kernel: RAX: 0000000000000000 RBX: ffffffff92f84d08 RCX: ffffffff92f84d08
Aug 25 17:38:46 naix kernel: RDX: ffffc304c0ea3c90 RSI: 0000000000000004 RDI: ffff9f51d1108000
Aug 25 17:38:46 naix kernel: RBP: 0000000000000004 R08: ffff9f51d1108038 R09: ffff9f51c4069240
Aug 25 17:38:46 naix kernel: R10: 0000000000000000 R11: 0000000000000001 R12: ffff9f51c023f000
Aug 25 17:38:46 naix kernel: R13: ffff9f51d1108038 R14: ffffffff92f84d08 R15: ffff9f51d1108000
Aug 25 17:38:46 naix kernel: FS:  00007f1b4ea45740(0000) GS:ffff9f5520600000(0000) knlGS:0000000000000000
Aug 25 17:38:46 naix kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Aug 25 17:38:46 naix kernel: CR2: ffffffffffffffd6 CR3: 0000000111cfa004 CR4: 00000000003706f0
Aug 25 17:38:46 naix kernel: Call Trace:
Aug 25 17:38:46 naix kernel:  <TASK>
Aug 25 17:38:46 naix kernel:  power_supply_show_property+0xbf/0x240
Aug 25 17:38:46 naix kernel:  dev_attr_show+0x19/0x40
Aug 25 17:38:46 naix kernel:  sysfs_kf_seq_show+0xa4/0xf0
Aug 25 17:38:46 naix kernel:  seq_read_iter+0x123/0x450
Aug 25 17:38:46 naix kernel:  new_sync_read+0x134/0x1c0
Aug 25 17:38:46 naix kernel:  vfs_read+0x148/0x190
Aug 25 17:38:46 naix kernel:  ksys_read+0x6f/0xf0
Aug 25 17:38:46 naix kernel:  do_syscall_64+0x5c/0x90
Aug 25 17:38:46 naix kernel:  ? handle_mm_fault+0xb2/0x280
Aug 25 17:38:46 naix kernel:  ? do_user_addr_fault+0x1db/0x690
Aug 25 17:38:46 naix kernel:  ? exc_page_fault+0x74/0x170
Aug 25 17:38:46 naix kernel:  entry_SYSCALL_64_after_hwframe+0x63/0xcd
Aug 25 17:38:46 naix kernel: RIP: 0033:0x7f1b4ec95e2c
Aug 25 17:38:46 naix kernel: Code: ec 28 48 89 54 24 18 48 89 74 24 10 89 7c 24 08 e8 d9 bd f8 ff 48 8b 54 24 18 48 8b 74 24 10 41 89 c0 8b 7c 24 08 31 c0 0f 05 <48> 3d 00 f0 ff ff 77 34 44 89 c7 48 89 44 24 08 e8 2f be f8 ff 48
Aug 25 17:38:46 naix kernel: RSP: 002b:00007ffde5882260 EFLAGS: 00000246 ORIG_RAX: 0000000000000000
Aug 25 17:38:46 naix kernel: RAX: ffffffffffffffda RBX: 0000564e143bd130 RCX: 00007f1b4ec95e2c
Aug 25 17:38:46 naix kernel: RDX: 0000000000001000 RSI: 0000564e1440f2e0 RDI: 000000000000000e
Aug 25 17:38:46 naix kernel: RBP: 00007ffde5882390 R08: 0000000000000000 R09: 0000000000000020
Aug 25 17:38:46 naix kernel: R10: 0000000000001000 R11: 0000000000000246 R12: 0000000000000000
Aug 25 17:38:46 naix kernel: R13: 0000000000000000 R14: 0000000000000000 R15: 000000000000000e
Aug 25 17:38:46 naix kernel:  </TASK>
Aug 25 17:38:46 naix kernel: Modules linked in: ccm snd_hda_codec_hdmi snd_ctl_led snd_hda_codec_realtek snd_hda_codec_generic snd_soc_avs snd_soc_skl snd_soc_hdac_hda snd_hda_ext_core iwlmvm snd_soc_sst_ipc intel_tcc_cooling snd_soc_sst_dsp x86_pkg_temp_thermal snd_soc_acpi_intel_match rmi_smbus intel_powerclamp snd_soc_acpi coretemp rmi_core mac80211 kvm_intel snd_soc_core libarc4 snd_compress iTCO_wdt ac97_bus kvm uvcvideo snd_pcm_dmaengine intel_pmc_bxt iwlwifi mei_hdcp irqbypass snd_hda_intel think_lmi cdc_mbim intel_wmi_thunderbolt iTCO_vendor_support hid_logitech_hidpp mei_pxp snd_intel_dspcfg videobuf2_vmalloc ee1004 btusb crct10dif_pclmul snd_intel_sdw_acpi videobuf2_memops crc32_pclmul intel_rapl_msr i2c_i801 iwlmei videobuf2_v4l2 snd_hda_codec firmware_attributes_class wmi_bmof ghash_clmulni_intel btrtl cdc_wdm aesni_intel crypto_simd cryptd rapl intel_cstate intel_uncore psmouse pcspkr e1000e btbcm mousedev cfg80211 i2c_smbus snd_hda_core thunderbolt cdc_ncm mei_me btintel uas
Aug 25 17:38:46 naix kernel:  videobuf2_common cdc_ether btmtk mei usb_storage intel_pch_thermal videodev bluetooth usbnet thinkpad_acpi cdc_acm snd_usb_audio mii ecdh_generic ledtrig_audio platform_profile i915 snd_usbmidi_lib tpm_crb snd_hwdep snd_rawmidi processor_thermal_device_pci_legacy snd_seq_device joydev drm_buddy processor_thermal_device mc processor_thermal_rfim ttm rfkill processor_thermal_mbox snd_pcm tpm_tis drm_display_helper tpm_tis_core ucsi_acpi snd_timer processor_thermal_rapl typec_ucsi int3403_thermal intel_rapl_common snd tpm vfat cec typec int340x_thermal_zone intel_xhci_usb_role_switch fat hid_logitech_dj soundcore intel_soc_dts_iosf intel_gtt roles rng_core video mac_hid wmi int3400_thermal acpi_pad acpi_thermal_rel dm_multipath sg crypto_user fuse ip_tables x_tables usbhid ext4 crc32c_generic crc16 mbcache jbd2 dm_mod serio_raw atkbd nvme libps2 vivaldi_fmap crc32c_intel xhci_pci nvme_core xhci_pci_renesas i8042 serio
Aug 25 17:38:46 naix kernel: Unloaded tainted modules: acpi_cpufreq():1 acpi_cpufreq():1 acpi_cpufreq():1 acpi_cpufreq():1 acpi_cpufreq():1 acpi_cpufreq():1 acpi_cpufreq():1 acpi_cpufreq():1 pcc_cpufreq():1 pcc_cpufreq():1 pcc_cpufreq():1 pcc_cpufreq():1 acpi_cpufreq():1 acpi_cpufreq():1 pcc_cpufreq():1 acpi_cpufreq():1 acpi_cpufreq():1 pcc_cpufreq():1 pcc_cpufreq():1 acpi_cpufreq():1 pcc_cpufreq():1 acpi_cpufreq():1 fjes():1 fjes():1 acpi_cpufreq():1 pcc_cpufreq():1 acpi_cpufreq():1 fjes():1 pcc_cpufreq():1 acpi_cpufreq():1 pcc_cpufreq():1 acpi_cpufreq():1 asus_ec_sensors():1 fjes():1 fjes():1 acpi_cpufreq():1 pcc_cpufreq():1 pcc_cpufreq():1 fjes():1 acpi_cpufreq():1 fjes():1 acpi_cpufreq():1 pcc_cpufreq():1 fjes():1 pcc_cpufreq():1 acpi_cpufreq():1 asus_ec_sensors():1 pcc_cpufreq():1 acpi_cpufreq():1 fjes():1 acpi_cpufreq():1
Aug 25 17:38:46 naix kernel: CR2: 0000000000000000
Aug 25 17:38:46 naix kernel: ---[ end trace 0000000000000000 ]---

Yes, but you can also just use the packages loqs has shared.

Offline

#14 2022-08-25 19:43:02

Avatar
Member
Registered: 2010-04-02
Posts: 31

Re: Help diagnosing computer freezes

Thanks Seth.
I would have preferred to build the packages myself for both the learning experience and the security reasons but on my 2 attempts so far I've come back to find the laptop hung again.
I've installed the binaries and I see the debug logs in journalctl, I'll wait for it to hang again.

Offline

#15 2022-08-25 21:24:03

Avatar
Member
Registered: 2010-04-02
Posts: 31

Re: Help diagnosing computer freezes

The oops has now happened again without a hang
In case this state is useful:
https://0x0.st/o9I0.txt

I'm leaving the laptop on for the night, tomorrow morning I can paste the new log after it hangs.

Offline

#16 2022-08-26 06:25:55

Avatar
Member
Registered: 2010-04-02
Posts: 31

Re: Help diagnosing computer freezes

This morning I came back to a hung system as expected.
Though as I saw before the log contains no useful info as far as I can see.
Last few lines end

Aug 26 05:33:10 naix kernel: psp == POWER_SUPPLY_PROP_MODEL_NAME ... POWER_SUPPLY_PROP_SERIAL_NUMBER.
Aug 26 05:33:10 naix kernel: dev ptr ffff950602c2e038,  attr ptr ffffffffa2786518.
Aug 26 05:33:10 naix kernel: psy ptr ffff950602c2e000.
Aug 26 05:33:10 naix kernel: ps_attr ptr ffffffffa27864f0.
Aug 26 05:33:10 naix kernel: psp set.
Aug 26 05:33:10 naix kernel: power_supply_get_property return 0.
Aug 26 05:33:10 naix kernel: psp == POWER_SUPPLY_PROP_MODEL_NAME ... POWER_SUPPLY_PROP_SERIAL_NUMBER.
Aug 26 05:33:10 naix kernel: dev ptr ffff950602c2e038,  attr ptr ffffffffa2786570.
Aug 26 05:33:10 naix kernel: psy ptr ffff950602c2e000.
Aug 26 05:33:10 naix kernel: ps_attr ptr ffffffffa2786548.
Aug 26 05:33:10 naix kernel: psp set.
Aug 26 05:33:10 naix kernel: power_supply_get_property return 0.
Aug 26 05:33:10 naix kernel: psp == POWER_SUPPLY_PROP_MODEL_NAME ... POWER_SUPPLY_PROP_SERIAL_NUMBER.

Longer log here:
https://0x0.st/o9U6.txt

Is the kernel crashing without being able to sync the oops?
I thought that would only happen if the problem occurs at the filesystem level.

Offline

#17 2022-08-26 06:33:55

seth
Member
Registered: 2012-09-03
Posts: 51,017

Re: Help diagnosing computer freezes

Did you reboot the system hard (power cut, pressing the power button until the system powers off) after the hang?
This will for sure prevent the journal from being synced to disk, in case try https://wiki.archlinux.org/title/Keyboa … el_(SysRq) instead.

Offline

#18 2022-08-26 06:38:45

KloolK
Member
Registered: 2022-08-24
Posts: 27

Re: Help diagnosing computer freezes

This seems to be same issue we are having in https://bbs.archlinux.org/viewtopic.php?pid=2053814

I also can't get any journal entries from the actual crash, only the Oopses that don't cause a crash. SysRq does not work and I have to cut the power in order to reboot.

Offline

#19 2022-08-26 06:52:21

seth
Member
Registered: 2012-09-03
Posts: 51,017

Re: Help diagnosing computer freezes

You'll then need https://wiki.archlinux.org/title/Kdump unless you can "force" the system to hang while the console w/ the system messages is visible ( and maybe https://wiki.archlinux.org/title/Genera … bug_output )
The oopses might be symptom of the same cause but not directly relate to the halt.

Offline

#20 2022-08-26 07:09:19

Avatar
Member
Registered: 2010-04-02
Posts: 31

Re: Help diagnosing computer freezes

seth wrote:

Did you reboot the system hard (power cut, pressing the power button until the system powers off) after the hang?

I did yes, I have no other way of resetting it.
I've enabled sysreq, but it seems to have no effect once the system has hung. I've tested it before it hangs and I can do emergency sync and reboot.

Offline

#21 2022-08-26 19:04:07

fistrosan
Member
Registered: 2020-04-01
Posts: 171

Re: Help diagnosing computer freezes

Hi all. I see people have been having similar issues to mine. I am on a Lenovo X1 carbon gen 7th. Sorry I have not been more communicative but I am on holidays and I will not be able to test loqs diagnostics until Monday. All I can say for the moment is that, so far from home, where I use the single-entry power brick I have had no issues whatsoever in almost a week. Problems always appeared when connecting to the double-entry power provided by the thunderbolt docking station.

Offline

#22 2022-08-26 19:38:02

KloolK
Member
Registered: 2022-08-24
Posts: 27

Re: Help diagnosing computer freezes

fistrosan wrote:

Hi all. I see people have been having similar issues to mine. I am on a Lenovo X1 carbon gen 7th. Sorry I have not been more communicative but I am on holidays and I will not be able to test loqs diagnostics until Monday. All I can say for the moment is that, so far from home, where I use the single-entry power brick I have had no issues whatsoever in almost a week. Problems always appeared when connecting to the double-entry power provided by the thunderbolt docking station.

Please also have a look into this thread: https://bbs.archlinux.org/viewtopic.php … 3#p2053933
We are currently bisecting the responsible commit there and I just noticed the same behavior regarding the docking station.

Enjoy the rest of your vacation smile

Offline

#23 2022-08-26 20:03:32

seth
Member
Registered: 2012-09-03
Posts: 51,017

Offline

#24 2022-08-29 13:47:21

fistrosan
Member
Registered: 2020-04-01
Posts: 171

Re: Help diagnosing computer freezes

Hi y'all. So far no problems nor freezes after being at work for 5+ hours. A couple of weeks ago it would have frozen already a couple of times. Journal does not show any issues with NULL pointers, power supply, nor upower.service ... magically solved ? I did not even get to install loqs kernel. Running now on 5.19.2-arch1-1 and it seems issues have been resolved from 5.19.1-arch2-1 ... shall I mark as solved ?

Offline

#25 2022-08-30 15:49:09

Avatar
Member
Registered: 2010-04-02
Posts: 31

Re: Help diagnosing computer freezes

I'm still running into the issue.
I looked into kdump, I hope I did it correctly smile
I couldn't figure out how to get kdump working with the arch kernel so I built the stock upstream kernel 5.19.4
My system crashed a few minutes ago and this is the dump I get from the the crash utility

      KERNEL: /home/pico/kernelbuild/linux-5.19.4/vmlinux
    DUMPFILE: /root/crashdump-2022-08-30-17:28:03  [PARTIAL DUMP]
        CPUS: 8
        DATE: Tue Aug 30 16:52:12 SAST 2022
      UPTIME: 06:44:23
LOAD AVERAGE: 0.34, 0.34, 0.45
       TASKS: 1715
    NODENAME: naix
     RELEASE: 5.19.4debugsym
     VERSION: #1 SMP PREEMPT_DYNAMIC Sat Aug 27 00:23:27 SAST 2022
     MACHINE: x86_64  (2000 Mhz)
      MEMORY: 15.7 GB
       PANIC: "Oops: 0010 [#1] PREEMPT SMP PTI" (check log for details)
         PID: 1
     COMMAND: "systemd"
        TASK: ffff9bf48026a100  [THREAD_INFO: ffff9bf48026a100]
         CPU: 6
       STATE: TASK_RUNNING (PANIC)

crash> bt
PID: 1      TASK: ffff9bf48026a100  CPU: 6   COMMAND: "systemd"
 #0 [ffffbd34c008bab0] machine_kexec at ffffffffab4709e0
 #1 [ffffbd34c008bb08] __crash_kexec at ffffffffab56c59e
 #2 [ffffbd34c008bbd0] crash_kexec at ffffffffab56d68c
 #3 [ffffbd34c008bbd8] oops_end at ffffffffab430b85
 #4 [ffffbd34c008bbf8] page_fault_oops at ffffffffab47fd2f
 #5 [ffffbd34c008bc78] exc_page_fault at ffffffffabfdc7c4
 #6 [ffffbd34c008bca0] asm_exc_page_fault at ffffffffac001266
    [exception RIP: unknown or invalid address]
    RIP: 0000000000000000  RSP: ffffbd34c008bd50  RFLAGS: 00010202
    RAX: 0000000000000000  RBX: ffffffffad184c88  RCX: ffffffffad184c88
    RDX: ffffbd34c008bd58  RSI: 0000000000000004  RDI: ffff9bf4e365d800
    RBP: 0000000000000004   R8: ffff9bf4e365d838   R9: ffff9bf6e957e540
    R10: 0000000000000000  R11: 0000000000000000  R12: ffff9bf6ea36d000
    R13: ffff9bf4e365d838  R14: ffffffffad184c88  R15: ffff9bf4e365d800
    ORIG_RAX: ffffffffffffffff  CS: 0010  SS: 0018
 #7 [ffffbd34c008bd50] power_supply_show_property at ffffffffabcf25ef
 #8 [ffffbd34c008bd98] dev_attr_show at ffffffffabbbb7c9
 #9 [ffffbd34c008bdb0] sysfs_kf_seq_show at ffffffffab81e8c4
#10 [ffffbd34c008bdc8] seq_read_iter at ffffffffab799973
#11 [ffffbd34c008be20] new_sync_read at ffffffffab7658b4
#12 [ffffbd34c008beb0] vfs_read at ffffffffab768518
#13 [ffffbd34c008bee8] ksys_read at ffffffffab768b5f
#14 [ffffbd34c008bf20] do_syscall_64 at ffffffffabfd815c
#15 [ffffbd34c008bf50] entry_SYSCALL_64_after_hwframe at ffffffffac00009f
    RIP: 00007f34b190fe2c  RSP: 00007ffdc252f700  RFLAGS: 00000246
    RAX: ffffffffffffffda  RBX: 00005635c712fab0  RCX: 00007f34b190fe2c
    RDX: 0000000000001001  RSI: 00005635c712fab0  RDI: 0000000000000045
    RBP: 0000000000000045   R8: 0000000000000000   R9: 00007f34b19f2280
    R10: 00007f34b19f2280  R11: 0000000000000246  R12: 0000000000001001
    R13: ffffffffffffffff  R14: 00000000003ffffe  R15: 0000000000000002
    ORIG_RAX: 0000000000000000  CS: 0033  SS: 002b

Please let me know if I can provide any additional info.

Offline

Board footer

Powered by FluxBB