Skip to content
View in the app

A better way to browse. Learn more.
Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.
Unraid Summer Sale in live: 20% off Starter and Unleashed + buy one, get one 50% off

Kernel Panics 6.11.0 - diagnostics attached

brucewillke
in General Support

Featured Replies

I have gotten a few kernel panics over the past few days where a hard reboot is required. 
This is happening frequently enough that I thought I'd get some advice on what I can do here. 
Attached are diags. 

tower-diagnostics-20221006-0908.zip

  • Quote

    • Solved by JorgeB

    Go to solution
    • Community Expert

    Syslog starts over after every boot, enable the syslog server and post that after a crash.

  • Quote
    • Author

    Thank you that explains why I couldn't locate syslogs. 

  • Quote
    • Community Expert

    Also post the permanent syslog, it's not included in the diags.

  • Quote
    • Author

    sorry last time i didn't post syslog, as the setup was imcomplete. Now that I have syslog server working here it is.

    this is the last bit of the entry before I restarted it this morning 


      

    Oct 16 00:00:06 Tower kernel: mdcmd (42): check 
Oct 16 00:00:06 Tower kernel: md: recovery thread: check P Q ...
Oct 16 00:00:34 Tower flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update
Oct 16 00:30:01 Tower Parity Check Tuning: Paused: Scheduled Correcting Parity Check
Oct 16 00:30:06 Tower kernel: mdcmd (43): nocheck pause
Oct 16 00:30:06 Tower kernel: 
Oct 16 00:30:06 Tower kernel: md: recovery thread: exit status: -4
Oct 16 00:30:11 Tower Parity Check Tuning: Send notification: Paused: Scheduled Correcting Parity Check (2.7% completed)  (2.7% completed)
Oct 16 00:30:11 Tower Parity Check Tuning: ... but suppressed as system notifications do not appear to be enabled
Oct 16 00:30:34 Tower flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update
Oct 16 00:42:24 Tower nginx: 2022/10/16 00:42:24 [crit] 11880#11880: *1847692 SSL_do_handshake() failed (SSL: error:141CF06C:SSL routines:tls_parse_ctos_key_share:bad key share) while SSL handshaking, client: 87.236.176.99, server: 0.0.0.0:443
Oct 16 00:53:06 Tower nginx: 2022/10/16 00:53:06 [crit] 11880#11880: *1853479 SSL_do_handshake() failed (SSL: error:141CF06C:SSL routines:tls_parse_ctos_key_share:bad key share) while SSL handshaking, client: 104.152.52.229, server: 0.0.0.0:443
Oct 17 08:39:58 Tower  emhttpd: Starting services...

    attached syslog here and diagnostics again 

    syslog-127.0.0.1-3.log tower-diagnostics-20221017-0845.zip

  • Quote
    • Community Expert
    • Solution

    Unfortunately there's nothing relevant logged, this usually points to a hardware problem, if you haven't yet run memtest.

  • Quote
    • Author

    thanks. running memtest 

  • Quote
    • Author

    memtest has already found a few errors after an hour. 
    ordering new ram today. 

    thank you again. 

  • Quote
    • Like 1
    • Author

    Unfortunately this has arisen again. 
    New ram. MemTest is clear. 


      

    Oct 20 21:35:25 Tower root: plugin: checking: /boot/config/plugins/community.applications/community.applications-2022.10.16-x86_64-1.txz - MD5
Oct 20 21:35:25 Tower root: plugin: running: /boot/config/plugins/community.applications/community.applications-2022.10.16-x86_64-1.txz
Oct 20 21:35:25 Tower root: plugin: running: anonymous
Oct 20 21:35:25 Tower root: plugin: community.applications.plg updated
Oct 20 21:51:24 Tower flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update
Oct 20 22:29:24 Tower flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update
Oct 20 23:17:25 Tower flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update
Oct 20 23:19:25 Tower flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update
Oct 21 00:00:06 Tower kernel: mdcmd (37): check 
Oct 21 00:00:25 Tower flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update
Oct 21 00:30:01 Tower Parity Check Tuning: Paused: Scheduled Correcting Parity Check
Oct 21 00:30:06 Tower kernel: mdcmd (38): nocheck pause
Oct 21 00:30:06 Tower kernel: 
Oct 21 00:30:06 Tower kernel: md: recovery thread: exit status: -4
Oct 21 00:30:11 Tower Parity Check Tuning: Send notification: Paused: Scheduled Correcting Parity Check (15.9% completed)  (15.9% completed)
Oct 21 00:30:11 Tower Parity Check Tuning: ... but suppressed as system notifications do not appear to be enabled
Oct 21 00:30:25 Tower flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update
Oct 21 02:14:03 Tower kernel: mce: [Hardware Error]: Machine check events logged
Oct 21 02:17:41 Tower kernel: mce: [Hardware Error]: Machine check events logged
Oct 21 02:19:54 Tower kernel: mce: [Hardware Error]: Machine check events logged
Oct 21 02:20:13 Tower kernel: mce: [Hardware Error]: Machine check events logged
Oct 21 02:22:18 Tower kernel: mce_notify_irq: 1 callbacks suppressed
Oct 21 02:22:18 Tower kernel: mce: [Hardware Error]: Machine check events logged
Oct 21 02:26:35 Tower kernel: mce: [Hardware Error]: Machine check events logged
Oct 21 02:28:05 Tower kernel: mce: [Hardware Error]: Machine check events logged
Oct 21 02:30:18 Tower kernel: usb 1-9: USB disconnect, device number 4
Oct 21 02:30:19 Tower kernel: usb 1-9: new full-speed USB device number 7 using xhci_hcd
Oct 21 02:30:19 Tower kernel: input: MSI PRO CARBON 10 as /devices/pci0000:00/0000:00:14.0/usb1/1-9/1-9:1.0/0003:1462:7B10.0003/input/input6
Oct 21 02:30:19 Tower kernel: hid-generic 0003:1462:7B10.0003: input,hiddev96,hidraw1: USB HID v1.10 Device [MSI PRO CARBON 10] on usb-0000:00:14.0-9/input0
Oct 21 02:30:29 Tower kernel: mce: [Hardware Error]: Machine check events logged
Oct 21 02:40:25 Tower kernel: mce: [Hardware Error]: Machine check events logged
Oct 21 02:40:44 Tower kernel: mce: [Hardware Error]: Machine check events logged
Oct 21 03:25:27 Tower kernel: mce_notify_irq: 1 callbacks suppressed
Oct 21 03:25:27 Tower kernel: mce: [Hardware Error]: Machine check events logged
Oct 21 03:33:36 Tower kernel: mce: [Hardware Error]: Machine check events logged
Oct 21 03:40:01 Tower  crond[1525]: exit status 1 from user root /usr/local/sbin/mover &> /dev/null
Oct 21 03:40:28 Tower kernel: mce: [Hardware Error]: Machine check events logged
Oct 21 03:42:47 Tower kernel: mce: [Hardware Error]: Machine check events logged
Oct 21 03:45:56 Tower kernel: mce: [Hardware Error]: Machine check events logged
Oct 21 03:47:46 Tower kernel: mce: [Hardware Error]: Machine check events logged
Oct 21 03:48:39 Tower kernel: mce: [Hardware Error]: Machine check events logged
Oct 21 03:49:44 Tower kernel: mce: [Hardware Error]: Machine check events logged
Oct 21 03:50:18 Tower kernel: mce: [Hardware Error]: Machine check events logged
Oct 21 03:52:08 Tower kernel: mce: [Hardware Error]: Machine check events logged
Oct 21 03:53:59 Tower kernel: mce: [Hardware Error]: Machine check events logged
Oct 21 03:54:52 Tower kernel: mce: [Hardware Error]: Machine check events logged
Oct 21 03:55:54 Tower kernel: mce: [Hardware Error]: Machine check events logged
Oct 21 03:58:43 Tower kernel: mce: [Hardware Error]: Machine check events logged
Oct 21 03:59:05 Tower kernel: mce: [Hardware Error]: Machine check events logged
Oct 21 04:04:10 Tower kernel: mce_notify_irq: 1 callbacks suppressed
Oct 21 04:04:10 Tower kernel: mce: [Hardware Error]: Machine check events logged
Oct 21 04:04:20 Tower kernel: mce: [Hardware Error]: Machine check events logged
Oct 21 04:06:15 Tower kernel: mce_notify_irq: 1 callbacks suppressed
Oct 21 04:06:15 Tower kernel: mce: [Hardware Error]: Machine check events logged
Oct 21 04:06:58 Tower kernel: mce: [Hardware Error]: Machine check events logged
Oct 21 04:08:39 Tower kernel: mce: [Hardware Error]: Machine check events logged
Oct 21 04:10:51 Tower kernel: mce: [Hardware Error]: Machine check events logged
Oct 21 04:11:49 Tower kernel: mce: [Hardware Error]: Machine check events logged
Oct 21 04:15:02 Tower kernel: BUG: kernel NULL pointer dereference, address: 0000000000000000
Oct 21 04:15:02 Tower kernel: #PF: supervisor write access in kernel mode
Oct 21 04:15:02 Tower kernel: #PF: error_code(0x0002) - not-present page
Oct 21 04:15:02 Tower kernel: PGD 0 P4D 0 
Oct 21 04:15:02 Tower kernel: Oops: 0002 [#1] PREEMPT SMP NOPTI
Oct 21 04:15:02 Tower kernel: CPU: 15 PID: 27113 Comm: Plex Script Hos Tainted: P           O      5.19.14-Unraid #1
Oct 21 04:15:02 Tower kernel: Hardware name: Micro-Star International Co., Ltd. MS-7B10/MEG Z390 GODLIKE (MS-7B10), BIOS 1.D2 11/16/2021
Oct 21 04:15:02 Tower kernel: RIP: 0010:put_prev_task+0xb/0x1b
Oct 21 04:15:02 Tower kernel: Code: 65 48 2b 04 25 28 00 00 00 74 05 e8 e3 48 75 00 48 8d 65 e8 5b 41 5c 41 5d 5d c3 cc cc cc cc 48 39 b7 70 09 00 00 74 02 0f 0b <48> 8b 86 a8 02 00 00 48 8b 40 30 ff e0 0f 1f 00 48 39 96 a8 02 00
Oct 21 04:15:02 Tower kernel: RSP: 0018:ffffc900009c7d18 EFLAGS: 00010046
Oct 21 04:15:02 Tower kernel: RAX: 0000000000000000 RBX: ffff88813ddf30c0 RCX: 0000000000000009
Oct 21 04:15:02 Tower kernel: RDX: 0000000102ad2766 RSI: ffff88813ddf30c0 RDI: ffff88902ddebfc0
Oct 21 04:15:02 Tower kernel: RBP: ffffc900009c7d70 R08: ffff8881b809e400 R09: 0000000000000184
Oct 21 04:15:02 Tower kernel: R10: 0000000000000000 R11: 0000000000000000 R12: ffff88902ddebfc0
Oct 21 04:15:02 Tower kernel: R13: 0000000000000000 R14: 0000000000000001 R15: ffff88813ddf3678
Oct 21 04:15:02 Tower kernel: FS:  0000147ea597db38(0000) GS:ffff88902ddc0000(0000) knlGS:0000000000000000
Oct 21 04:15:02 Tower kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Oct 21 04:15:02 Tower kernel: CR2: 0000000000000000 CR3: 00000003675d8003 CR4: 00000000003706e0
Oct 21 04:15:02 Tower kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Oct 21 04:15:02 Tower kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Oct 21 04:15:02 Tower kernel: Call Trace:
Oct 21 04:15:02 Tower kernel: <TASK>
Oct 21 04:15:02 Tower kernel: __schedule+0x1d7/0x5f6
Oct 21 04:15:02 Tower kernel: ? hrtimer_start_range_ns+0x1d4/0x23e
Oct 21 04:15:02 Tower kernel: schedule+0x8e/0xc3
Oct 21 04:15:02 Tower kernel: schedule_hrtimeout_range_clock+0x7d/0xc6
Oct 21 04:15:02 Tower kernel: ? hrtimer_init_sleeper+0x41/0x41
Oct 21 04:15:02 Tower kernel: do_epoll_wait+0x220/0x557
Oct 21 04:15:02 Tower kernel: ? ep_timeout_to_timespec+0x97/0x97
Oct 21 04:15:02 Tower kernel: do_compat_epoll_pwait.part.0+0xb/0x5f
Oct 21 04:15:02 Tower kernel: __x64_sys_epoll_pwait+0x64/0x8e
Oct 21 04:15:02 Tower kernel: do_syscall_64+0x68/0x81
Oct 21 04:15:02 Tower kernel: entry_SYSCALL_64_after_hwframe+0x63/0xcd
Oct 21 04:15:02 Tower kernel: RIP: 0033:0x147ea8f76739
Oct 21 04:15:02 Tower kernel: Code: c0 0f 85 24 00 00 00 49 89 fb 48 89 f0 48 89 d7 48 89 ce 4c 89 c2 4d 89 ca 4c 8b 44 24 08 4c 8b 4c 24 10 4c 89 5c 24 08 0f 05 <c3> e9 d5 cb ff ff 41 57 41 56 53 48 81 ec 90 00 00 00 49 89 f6 b8
Oct 21 04:15:02 Tower kernel: RSP: 002b:0000147ea597cab8 EFLAGS: 00000246 ORIG_RAX: 0000000000000119
Oct 21 04:15:02 Tower kernel: mce: [Hardware Error]: Machine check events logged
Oct 21 04:15:02 Tower kernel: RAX: ffffffffffffffda RBX: 0000000000000119 RCX: 0000147ea8f76739
Oct 21 04:15:02 Tower kernel: RDX: 00000000000003ff RSI: 0000147ea5944450 RDI: 0000000000000006
Oct 21 04:15:02 Tower kernel: RBP: 0000147ea597cb80 R08: 0000000000000000 R09: 0000000000000008
Oct 21 04:15:02 Tower kernel: R10: 00000000000000c8 R11: 0000000000000246 R12: 0000147ea597db38

     

  • Quote
    • Community Expert
    4 minutes ago, brucewillke said: 
    mce: [Hardware Error]: Machine check events logged

    This suggests that there's still some hardware issue.

  • Quote
    • Like 1

    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.
    Note: Your post will require moderator approval before it will be visible.

    Guest
    Reply to this topic...
    Go to topic listing

    Account

    Navigation

    Search

    Search

    Configure browser push notifications
    Chrome (Android)
    1. Tap the lock icon next to the address bar.
    2. Tap Permissions → Notifications.
    3. Adjust your preference.
    Chrome (Desktop)
    1. Click the padlock icon in the address bar.
    2. Select Site settings.
    3. Find Notifications and adjust your preference.