You are not logged in.

#1 2019-06-12 19:38:11

miomio
Member
Registered: 2016-01-17
Posts: 167

Two kernel panics in ~ 4 hour time frame?

Any idea's on why my laptop is rebooting? Here's the first from earlier today:

Jun 12 15:49:03 gerty dhcpcd[930]: enp0s31f6: fe80::c23e:fff:fecb:21c: no longer a default router
Jun 12 15:49:03 gerty dhcpcd[930]: enp0s31f6: deleting default route via fe80::c23e:fff:fecb:21c
Jun 12 15:49:03 gerty dhcpcd[930]: enp0s31f6: adding default route via fe80::c23e:fff:fecb:21c
Jun 12 16:19:03 gerty dhcpcd[930]: enp0s31f6: fe80::c23e:fff:fecb:21c: no longer a default router
Jun 12 16:19:03 gerty dhcpcd[930]: enp0s31f6: deleting default route via fe80::c23e:fff:fecb:21c
Jun 12 16:19:03 gerty dhcpcd[930]: enp0s31f6: adding default route via fe80::c23e:fff:fecb:21c
Jun 12 16:21:20 gerty dhcpcd[930]: enp0s31f6: fe80::c23e:fff:fecb:21c is unreachable, expiring it
Jun 12 16:23:42 gerty rtkit-daemon[1038]: Supervising 4 threads of 1 processes of 1 users.
Jun 12 16:23:42 gerty rtkit-daemon[1038]: Successfully made thread 2852 of process 1037 owned by '1000' RT at priority 5.
Jun 12 16:23:42 gerty rtkit-daemon[1038]: Supervising 5 threads of 1 processes of 1 users.
Jun 12 16:23:44 gerty kernel: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe B FIFO underrun
Jun 12 16:23:44 gerty kernel: [drm:pipe_config_err [i915]] *ERROR* mismatch in pixel_rate (expected 148500, found 296999)
Jun 12 16:23:44 gerty kernel: [drm:pipe_config_err [i915]] *ERROR* mismatch in shared_dpll (expected 00000000d5607e9d, found 000000006c9a9f07)
Jun 12 16:23:44 gerty kernel: [drm:pipe_config_err [i915]] *ERROR* mismatch in dpll_hw_state.ctrl1 (expected 0x00000003, found 0x00000001)
Jun 12 16:23:44 gerty kernel: [drm:pipe_config_err [i915]] *ERROR* mismatch in base.adjusted_mode.crtc_clock (expected 148500, found 296999)
Jun 12 16:23:44 gerty kernel: [drm:pipe_config_err [i915]] *ERROR* mismatch in port_clock (expected 270000, found 540000)
Jun 12 16:23:44 gerty kernel: ------------[ cut here ]------------
Jun 12 16:23:44 gerty kernel: pipe state doesn't match!
Jun 12 16:23:44 gerty kernel: WARNING: CPU: 0 PID: 999 at drivers/gpu/drm/i915/intel_display.c:12213 intel_atomic_commit_tail+0xd04/0xd80 [i915]
Jun 12 16:23:44 gerty kernel: Modules linked in: 8021q garp mrp stp llc snd_soc_skl snd_soc_hdac_hda snd_hda_ext_core snd_soc_skl_ipc snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core arc4 snd_hda_codec_hdmi snd_compress ac97_bus intel_rapl snd_pcm_dmaengine snd_hda_codec_realtek snd_hda_codec_generic iwlmvm x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_intel mac80211 iTCO_wdt iTCO_vendor_support nls_iso8859_1 mei_wdt kvm_intel nls_cp437 vfat snd_hda_codec fat iwlwifi wmi_bmof btusb intel_wmi_thunderbolt btrtl snd_usb_audio btbcm btintel snd_hda_core intel_cstate snd_usbmidi_lib bluetooth e1000e intel_uncore psmouse snd_hwdep snd_rawmidi snd_seq_device intel_rapl_perf pcspkr input_leds cfg80211 snd_pcm mousedev wacom joydev snd_timer i2c_i801 mei_me tpm_crb ecdh_generic mei thinkpad_acpi intel_xhci_usb_role_switch roles intel_pch_thermal ucsi_acpi typec_ucsi nvram ledtrig_audio typec rfkill wmi tpm_tis snd tpm_tis_core tpm soundcore battery ac evdev rng_core mac_hid
Jun 12 16:23:44 gerty kernel:  pcc_cpufreq crypto_user ip_tables x_tables ext4 crc32c_generic crc16 mbcache jbd2 fscrypto algif_skcipher af_alg hid_generic usbhid hid uas usb_storage dm_crypt dm_mod crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel serio_raw atkbd libps2 aesni_intel aes_x86_64 crypto_simd xhci_pci cryptd glue_helper xhci_hcd i8042 serio sd_mod ahci libahci libata scsi_mod i915 kvmgt vfio_mdev mdev vfio_iommu_type1 vfio kvm irqbypass intel_gtt i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm agpgart
Jun 12 16:23:44 gerty kernel: CPU: 0 PID: 999 Comm: Xorg Tainted: G     U            5.0.13-arch1-1-ARCH #1
Jun 12 16:23:44 gerty kernel: Hardware name: LENOVO, BIOS N1WET51W (1.30 ) 09/14/2018
Jun 12 16:23:44 gerty kernel: RIP: 0010:intel_atomic_commit_tail+0xd04/0xd80 [i915]
Jun 12 16:23:44 gerty kernel: Code: 14 00 00 8d 71 41 48 c7 c7 70 43 57 c0 75 6c e8 82 09 d9 ff e9 7c fb ff ff e8 12 83 5d fa 0f 0b e9 a9 fd ff ff e8 06 83 5d fa <0f> 0b e9 43 fa ff ff e8 fa 82 5d fa 0f 0b 0f b6 44 24 18 e9 75 f9
Jun 12 16:23:44 gerty kernel: RSP: 0018:ffffb5c9c144bb48 EFLAGS: 00010286
Jun 12 16:23:44 gerty kernel: RAX: 0000000000000000 RBX: ffff9473f3585800 RCX: 0000000000000000
Jun 12 16:23:44 gerty kernel: RDX: 0000000000000007 RSI: ffffffffbba96fbc RDI: 00000000ffffffff
Jun 12 16:23:44 gerty kernel: RBP: ffff9473f06c5800 R08: 0000000000000001 R09: 00000000000003ea
Jun 12 16:23:44 gerty kernel: R10: 0000000000000004 R11: 0000000000000000 R12: ffff9473f3584000
Jun 12 16:23:44 gerty kernel: R13: ffff9473f3580800 R14: ffff9473f0268368 R15: ffff9473f0268370
Jun 12 16:23:44 gerty kernel: FS:  00007f170080fdc0(0000) GS:ffff9473f6200000(0000) knlGS:0000000000000000
Jun 12 16:23:44 gerty kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jun 12 16:23:44 gerty kernel: CR2: 00005634c8cf5058 CR3: 000000022e7f4001 CR4: 00000000003606f0
Jun 12 16:23:44 gerty kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Jun 12 16:23:44 gerty kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Jun 12 16:23:44 gerty kernel: Call Trace:
Jun 12 16:23:44 gerty kernel:  intel_atomic_commit+0x2a9/0x2e0 [i915]
Jun 12 16:23:44 gerty kernel:  drm_atomic_helper_set_config+0x80/0x90 [drm_kms_helper]
Jun 12 16:23:44 gerty kernel:  drm_mode_setcrtc+0x191/0x6a0 [drm]
Jun 12 16:23:44 gerty kernel:  ? drm_mode_setplane+0x2a0/0x2a0 [drm]
Jun 12 16:23:44 gerty kernel:  ? drm_mode_getcrtc+0x180/0x180 [drm]
Jun 12 16:23:44 gerty kernel:  drm_ioctl_kernel+0xaf/0xf0 [drm]
Jun 12 16:23:44 gerty kernel:  drm_ioctl+0x25f/0x3f0 [drm]
Jun 12 16:23:44 gerty kernel:  ? drm_mode_getcrtc+0x180/0x180 [drm]
Jun 12 16:23:44 gerty kernel:  ? __switch_to_asm+0x40/0x70
Jun 12 16:23:44 gerty kernel:  ? __switch_to_asm+0x34/0x70
Jun 12 16:23:44 gerty kernel:  do_vfs_ioctl+0xa4/0x630
Jun 12 16:23:44 gerty kernel:  ksys_ioctl+0x60/0x90
Jun 12 16:23:44 gerty kernel:  __x64_sys_ioctl+0x16/0x20
Jun 12 16:23:44 gerty kernel:  do_syscall_64+0x5b/0x170
Jun 12 16:23:44 gerty kernel:  entry_SYSCALL_64_after_hwframe+0x44/0xa9
Jun 12 16:23:44 gerty kernel: RIP: 0033:0x7f1702632cbb
Jun 12 16:23:44 gerty kernel: Code: 0f 1e fa 48 8b 05 a5 d1 0c 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 75 d1 0c 00 f7 d8 64 89 01 48
Jun 12 16:23:44 gerty kernel: RSP: 002b:00007fffcd8dab98 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
Jun 12 16:23:44 gerty kernel: RAX: ffffffffffffffda RBX: 000055c98ddd1060 RCX: 00007f1702632cbb
Jun 12 16:23:44 gerty kernel: RDX: 00007fffcd8dac80 RSI: 00000000c06864a2 RDI: 000000000000000a
Jun 12 16:23:44 gerty kernel: RBP: 00007fffcd8dac80 R08: 0000000000000071 R09: 0000000000000000
Jun 12 16:23:44 gerty kernel: R10: ffffffffffffffc4 R11: 0000000000000246 R12: 00000000c06864a2
Jun 12 16:23:44 gerty kernel: R13: 000000000000000a R14: 000055c98ddd0e20 R15: 000055c98ddd2e20
Jun 12 16:23:44 gerty kernel: ---[ end trace 024da274b409eaf6 ]---
Jun 12 16:26:59 gerty dhcpcd[930]: enp0s31f6: fe80::c23e:fff:fecb:21c is reachable again
-- Reboot --

And most recently:

Jun 12 19:44:28 gerty dhcpcd[954]: enp0s31f6: fe80::c23e:fff:fecb:21c: no longer a default router
Jun 12 19:44:28 gerty dhcpcd[954]: enp0s31f6: deleting default route via fe80::c23e:fff:fecb:21c
Jun 12 19:44:28 gerty dhcpcd[954]: enp0s31f6: adding default route via fe80::c23e:fff:fecb:21c
Jun 12 19:58:54 gerty kernel: [drm:pipe_config_err [i915]] *ERROR* mismatch in pixel_rate (expected 148500, found 296999)
Jun 12 19:58:54 gerty kernel: [drm:pipe_config_err [i915]] *ERROR* mismatch in shared_dpll (expected 00000000e5c6f281, found 00000000ceddb769)
Jun 12 19:58:54 gerty kernel: [drm:pipe_config_err [i915]] *ERROR* mismatch in dpll_hw_state.ctrl1 (expected 0x00000003, found 0x00000001)
Jun 12 19:58:54 gerty kernel: [drm:pipe_config_err [i915]] *ERROR* mismatch in base.adjusted_mode.crtc_clock (expected 148500, found 296999)
Jun 12 19:58:54 gerty kernel: [drm:pipe_config_err [i915]] *ERROR* mismatch in port_clock (expected 270000, found 540000)
Jun 12 19:58:54 gerty kernel: ------------[ cut here ]------------
Jun 12 19:58:54 gerty kernel: pipe state doesn't match!
Jun 12 19:58:54 gerty kernel: WARNING: CPU: 0 PID: 1194 at drivers/gpu/drm/i915/intel_display.c:12213 intel_atomic_commit_tail+0xd04/0xd80 [i915]
Jun 12 19:58:54 gerty kernel: Modules linked in: 8021q garp mrp stp llc arc4 iwlmvm mac80211 btusb btrtl snd_soc_skl btbcm iwlwifi btintel nls_iso8859_1 snd_soc_hdac_hda nls_cp437 snd_hda_ext_core vfat fat bluetooth intel_rapl snd_soc_skl_ipc snd_soc_sst_ipc snd_soc_sst_dsp x86_pkg_temp_thermal intel_powerclamp coretemp snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core snd_usb_audio snd_hda_codec_hdmi iTCO_wdt mei_wdt kvm_intel iTCO_vendor_support wmi_bmof intel_wmi_thunderbolt snd_hda_codec_realtek snd_hda_codec_generic snd_compress ac97_bus snd_usbmidi_lib snd_pcm_dmaengine snd_rawmidi intel_cstate mousedev snd_hda_intel cfg80211 joydev wacom intel_uncore snd_hda_codec snd_seq_device ecdh_generic intel_rapl_perf psmouse input_leds snd_hda_core e1000e snd_hwdep thinkpad_acpi pcspkr snd_pcm i2c_i801 mei_me nvram ledtrig_audio intel_xhci_usb_role_switch roles ucsi_acpi mei typec_ucsi snd_timer intel_pch_thermal wmi typec rfkill tpm_crb snd ac soundcore battery tpm_tis tpm_tis_core tpm evdev rng_core mac_hid
Jun 12 19:58:54 gerty kernel:  pcc_cpufreq crypto_user ip_tables x_tables ext4 crc32c_generic crc16 mbcache jbd2 fscrypto algif_skcipher af_alg hid_generic usbhid hid uas usb_storage dm_crypt dm_mod crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel serio_raw atkbd libps2 aesni_intel xhci_pci aes_x86_64 crypto_simd cryptd glue_helper xhci_hcd i8042 serio sd_mod ahci libahci libata scsi_mod i915 kvmgt vfio_mdev mdev vfio_iommu_type1 vfio kvm irqbypass intel_gtt i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm agpgart
Jun 12 19:58:54 gerty kernel: CPU: 0 PID: 1194 Comm: Xorg Tainted: G     U            5.0.13-arch1-1-ARCH #1
Jun 12 19:58:54 gerty kernel: Hardware name: LENOVO, BIOS N1WET51W (1.30 ) 09/14/2018
Jun 12 19:58:54 gerty kernel: RIP: 0010:intel_atomic_commit_tail+0xd04/0xd80 [i915]
Jun 12 19:58:54 gerty kernel: Code: 14 00 00 8d 71 41 48 c7 c7 70 c3 62 c0 75 6c e8 82 29 d9 ff e9 7c fb ff ff e8 12 03 32 c8 0f 0b e9 a9 fd ff ff e8 06 03 32 c8 <0f> 0b e9 43 fa ff ff e8 fa 02 32 c8 0f 0b 0f b6 44 24 18 e9 75 f9
Jun 12 19:58:54 gerty kernel: RSP: 0018:ffffae0cc17cbb48 EFLAGS: 00010286
Jun 12 19:58:54 gerty kernel: RAX: 0000000000000000 RBX: ffff9bb3a195f000 RCX: 0000000000000000
Jun 12 19:58:54 gerty kernel: RDX: 0000000000000007 RSI: ffffffff89896fbc RDI: 00000000ffffffff
Jun 12 19:58:54 gerty kernel: RBP: ffff9bb4b08ae000 R08: 0000000000000001 R09: 00000000000003ed
Jun 12 19:58:54 gerty kernel: R10: 0000000000000004 R11: 0000000000000000 R12: ffff9bb3a1959000
Jun 12 19:58:54 gerty kernel: R13: ffff9bb3a1958000 R14: ffff9bb4b0488368 R15: ffff9bb4b0488370
Jun 12 19:58:54 gerty kernel: FS:  00007fb5bf413dc0(0000) GS:ffff9bb4b6200000(0000) knlGS:0000000000000000
Jun 12 19:58:54 gerty kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jun 12 19:58:54 gerty kernel: CR2: 00007fb5a7808000 CR3: 000000018f324004 CR4: 00000000003606f0
Jun 12 19:58:54 gerty kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Jun 12 19:58:54 gerty kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Jun 12 19:58:54 gerty kernel: Call Trace:
Jun 12 19:58:54 gerty kernel:  intel_atomic_commit+0x2a9/0x2e0 [i915]
Jun 12 19:58:54 gerty kernel:  drm_atomic_helper_set_config+0x80/0x90 [drm_kms_helper]
Jun 12 19:58:54 gerty kernel:  drm_mode_setcrtc+0x191/0x6a0 [drm]
Jun 12 19:58:54 gerty kernel:  ? drm_mode_setplane+0x2a0/0x2a0 [drm]
Jun 12 19:58:54 gerty kernel:  ? drm_mode_getcrtc+0x180/0x180 [drm]
Jun 12 19:58:54 gerty kernel:  drm_ioctl_kernel+0xaf/0xf0 [drm]
Jun 12 19:58:54 gerty kernel:  drm_ioctl+0x25f/0x3f0 [drm]
Jun 12 19:58:54 gerty kernel:  ? drm_mode_getcrtc+0x180/0x180 [drm]
Jun 12 19:58:54 gerty kernel:  ? __switch_to_asm+0x40/0x70
Jun 12 19:58:54 gerty kernel:  ? __switch_to_asm+0x34/0x70
Jun 12 19:58:54 gerty kernel:  do_vfs_ioctl+0xa4/0x630
Jun 12 19:58:54 gerty kernel:  ksys_ioctl+0x60/0x90
Jun 12 19:58:54 gerty kernel:  __x64_sys_ioctl+0x16/0x20
Jun 12 19:58:54 gerty kernel:  do_syscall_64+0x5b/0x170
Jun 12 19:58:54 gerty kernel:  entry_SYSCALL_64_after_hwframe+0x44/0xa9
Jun 12 19:58:54 gerty kernel: RIP: 0033:0x7fb5c1236cbb
Jun 12 19:58:54 gerty kernel: Code: 0f 1e fa 48 8b 05 a5 d1 0c 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 75 d1 0c 00 f7 d8 64 89 01 48
Jun 12 19:58:54 gerty kernel: RSP: 002b:00007ffc26b42848 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
Jun 12 19:58:54 gerty kernel: RAX: ffffffffffffffda RBX: 000056429d1a8060 RCX: 00007fb5c1236cbb
Jun 12 19:58:54 gerty kernel: RDX: 00007ffc26b42930 RSI: 00000000c06864a2 RDI: 000000000000000a
Jun 12 19:58:54 gerty kernel: RBP: 00007ffc26b42930 R08: 0000000000000071 R09: 0000000000000000
Jun 12 19:58:54 gerty kernel: R10: ffffffffffffffc4 R11: 0000000000000246 R12: 00000000c06864a2
Jun 12 19:58:54 gerty kernel: R13: 000000000000000a R14: 000056429d1a7e20 R15: 000056429d1a9e20
Jun 12 19:58:54 gerty kernel: ---[ end trace afba573dc7ad1e0d ]---
-- Reboot --

I'm not sure what's causing this. I wonder if it happening when my monitor's sleep after inactivity because on both these occasions I was away from desk. Not sure what significance the dhcpd messages have right before each either.

Offline

#2 2019-06-12 19:49:50

seth
Member
Registered: 2012-09-03
Posts: 49,993

Re: Two kernel panics in ~ 4 hour time frame?

At least for the first post there are at least > 3 minutes between the kernel warning and the reboot.
"i915.nuclear_pageflip=false" might prevent the warning, but I doubt it's related to the reboot.

Offline

#3 2019-06-12 22:07:50

miomio
Member
Registered: 2016-01-17
Posts: 167

Re: Two kernel panics in ~ 4 hour time frame?

So strange that these warnings are so close to the reboots. Logical fallacy?

EDIT: I noticed my machine was warm after returning and finding it had rebooted. Maybe if I'd gotten back closer to the reboot I'd have found it hot, because perhaps the CPU was maxing out for some reason related to this and high temp triggered the reboot?

Last edited by miomio (2019-06-12 22:10:34)

Offline

#4 2019-06-12 22:13:52

seth
Member
Registered: 2012-09-03
Posts: 49,993

Re: Two kernel panics in ~ 4 hour time frame?

Are they?
You can infer more data from the timestamps of the next boot - also this should probably happen more often?

Offline

#5 2019-06-12 22:53:57

miomio
Member
Registered: 2016-01-17
Posts: 167

Re: Two kernel panics in ~ 4 hour time frame?

`journalctl --list-boots`:

 -3 ... Wed 2019-06-12 15:34:04 BST—Wed 2019-06-12 16:26:59 BST
 -2 ... Wed 2019-06-12 16:43:17 BST—Wed 2019-06-12 19:58:54 BST
0 ... Wed 2019-06-12 22:23:25 BST—Wed 2019-06-12 23:43:28 BST

... hmm, now I'm not sure whether I'm interpreting this correctly.

Jun 12 16:26:59 gerty dhcpcd[930]: enp0s31f6: fe80::c23e:fff:fecb:21c is reachable again
-- Reboot --
Jun 12 16:43:17 gerty kernel: microcode: microcode updated early to revision 0xcc, date = 2019-04-01
....
Jun 12 19:58:54 gerty kernel: ---[ end trace afba573dc7ad1e0d ]---
-- Reboot --
Jun 12 20:12:39 gerty kernel: microcode: microcode updated early to revision 0xcc, date = 2019-04-01
...

This would mean that the machine was rebooting for 14 and 17 minutes wouldn't it. That's doesn't sound right

Last edited by miomio (2019-06-12 22:54:17)

Offline

#6 2019-06-13 03:22:58

euromatlox
Member
Registered: 2017-02-10
Posts: 110

Re: Two kernel panics in ~ 4 hour time frame?

Seems like it's Lenovo computer in question. I recently had to replace my PS/2 keyboard and mouse to USB keyboard and mouse, because USB-2xPS2 adapter begun to have problems. Actually one adapter works, but it must be connected after booting the computer (not working if connected when booting). Computer: Lenovo Thinkpad T440s.

So if some USB stuff connected, and not necessary for booting, try without that stuff to have some possible causes sorted out.

Offline

#7 2019-06-13 05:32:24

seth
Member
Registered: 2012-09-03
Posts: 49,993

Re: Two kernel panics in ~ 4 hour time frame?

I assume what happens is that you leave the system, some fancy screensaver shows up, causes the flipping warning and then at some later point the system reboots - maybe failing to S3/S4?
I'd check the power management / screensaver settings and whether you can reproduce this by leaving the system unattended (though still keeping an eye on it)

Offline

#8 2019-06-13 09:14:58

miomio
Member
Registered: 2016-01-17
Posts: 167

Re: Two kernel panics in ~ 4 hour time frame?

seth wrote:

I assume what happens is that you leave the system, some fancy screensaver shows up

No, no. Don't have a screensaver. When I said monitors go to sleep, I think the Linux kernel sends HDMI control commands to monitors to put them in sleep.

Offline

#9 2019-06-13 09:23:01

miomio
Member
Registered: 2016-01-17
Posts: 167

Re: Two kernel panics in ~ 4 hour time frame?

euromatlox wrote:

Seems like it's Lenovo computer in question. I recently had to replace my PS/2 keyboard and mouse to USB keyboard and mouse, because USB-2xPS2 adapter begun to have problems. Actually one adapter works, but it must be connected after booting the computer (not working if connected when booting). Computer: Lenovo Thinkpad T440s.

So if some USB stuff connected, and not necessary for booting, try without that stuff to have some possible causes sorted out.

Yes, I have the dock with lots of USB devices connected. Thinking about it, I have a lot of USB stuff plugged in, and there are keyboard/mouse related events:

Jun 12 22:23:35 gerty systemd-logind[884]: Watching system buttons on /dev/input/event5 (MOSART Semi. 2.4G Keyboard Mouse)
Jun 12 22:23:35 gerty systemd-logind[884]: Watching system buttons on /dev/input/event7 (MOSART Semi. 2.4G Keyboard Mouse Consumer Control)


Jun 12 22:23:25 gerty kernel: usb 1-4.4.1: new full-speed USB device number 6 using xhci_hcd
Jun 12 22:23:25 gerty kernel: usb 1-4.4.1: New USB device found, idVendor=062a, idProduct=4101, bcdDevice= 2.03
Jun 12 22:23:25 gerty kernel: usb 1-4.4.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Jun 12 22:23:25 gerty kernel: usb 1-4.4.1: Product: 2.4G Keyboard Mouse
Jun 12 22:23:25 gerty kernel: usb 1-4.4.1: Manufacturer: MOSART Semi.


Jun 12 22:23:25 gerty kernel: hid-generic 0003:062A:4101.0001: input,hidraw0: USB HID v1.10 Keyboard [MOSART Semi. 2.4G Keyboard Mouse] on usb-0000:00:14.0-4.4.1/input0
Jun 12 22:23:25 gerty kernel: input: MOSART Semi. 2.4G Keyboard Mouse as /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1:1.1/0003:062A:4101.0002/input/input7
Jun 12 22:23:25 gerty kernel: input: MOSART Semi. 2.4G Keyboard Mouse Consumer Control as /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1:1.1/0003:062A:4101.0002/input/input8
Jun 12 22:23:25 gerty kernel: input: MOSART Semi. 2.4G Keyboard Mouse System Control as /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1:1.1/0003:062A:4101.0002/input/input9
Jun 12 22:23:25 gerty kernel: input: MOSART Semi. 2.4G Keyboard Mouse as /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.1/1-4.4.1:1.1/0003:062A:4101.0002/input/input10
Jun 12 22:23:25 gerty kernel: hid-generic 0003:062A:4101.0002: input,hiddev0,hidraw1: USB HID v1.10 Mouse [MOSART Semi. 2.4G Keyboard Mouse] on usb-0000:00:14.0-4.4.1/input1

A little strange why this hasn't caused problems before though. I'll check previous months journal logs make sure these events are there so to rule them out being new. Also, I just noticed brave-browser is causing core dumps a lot so sosmething isn't right there, but I will need to see if this is happening around the same time as the reboots. Could be unrelated.

Offline

#10 2019-06-13 20:40:26

euromatlox
Member
Registered: 2017-02-10
Posts: 110

Re: Two kernel panics in ~ 4 hour time frame?

I noticed that there are some recent firmware updates available for Lenovo laptops (like mine T440s). The readme-file however tells me that no need to update (my laptop). Also for Lenovo dock (I have Pro Dock) is a firmware update, correcting some issue with external monitor. However installing that dock update requires Windows, and it's unclear if the problem affects Linux usage at all.

Last edited by euromatlox (2019-06-13 20:41:41)

Offline

Board footer

Powered by FluxBB