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.

Call trace, possible to identify error source?

Featured Replies

This appeared in my log earlier today, from what is a very error-free server.

Aug  8 10:15:11 unRAID kernel: WARNING: CPU: 4 PID: 2190177 at fs/notify/fdinfo.c:55 show_mark_fhandle+0x79/0xe8
Aug  8 10:15:11 unRAID kernel: Modules linked in: xt_nat xt_tcpudp veth xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo ip6table_nat iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xt_addrtype br_netfilter bridge stp llc md_mod zfs(PO) spl(O) nct6775 nct6775_core hwmon_vid ip6table_filter ip6_tables iptable_filter ip_tables x_tables efivarfs macvtap macvlan tap intel_rapl_common x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel i915 kvm iosf_mbi drm_buddy ttm crct10dif_pclmul i2c_algo_bit crc32_pclmul crc32c_intel ghash_clmulni_intel drm_display_helper sha512_ssse3 sha256_ssse3 sha1_ssse3 aesni_intel drm_kms_helper crypto_simd cryptd mei_pxp mei_hdcp rapl intel_cstate intel_wmi_thunderbolt mxm_wmi i2c_i801 drm e1000e intel_uncore mpt3sas i2c_smbus mei_me ahci intel_gtt mei raid_class agpgart libahci i2c_core scsi_transport_sas thermal fan video wmi backlight acpi_pad acpi_tad button
Aug  8 10:15:11 unRAID kernel: CPU: 4 PID: 2190177 Comm: lsof Tainted: P           O       6.8.12-Unraid #3
Aug  8 10:15:11 unRAID kernel: Hardware name: Micro-Star International Co., Ltd. MS-7B49/Z370 PC PRO (MS-7B49), BIOS 1.B3 11/15/2021
Aug  8 10:15:11 unRAID kernel: RIP: 0010:show_mark_fhandle+0x79/0xe8
Aug  8 10:15:11 unRAID kernel: Code: ff 00 00 00 89 c1 74 04 85 c0 79 22 80 3d 0a 40 2c 01 00 75 5e 89 ce 48 c7 c7 4b 4a 27 82 c6 05 f8 3f 2c 01 01 e8 23 28 d8 ff <0f> 0b eb 45 89 44 24 0c 8b 44 24 04 48 89 ef 31 db 48 c7 c6 89 4a
Aug  8 10:15:11 unRAID kernel: RSP: 0018:ffffc9000899fc30 EFLAGS: 00010282
Aug  8 10:15:11 unRAID kernel: RAX: 0000000000000000 RBX: ffff8881347dc020 RCX: 0000000000000027
Aug  8 10:15:11 unRAID kernel: RDX: 0000000082440510 RSI: ffffffff82258ed4 RDI: 00000000ffffffff
Aug  8 10:15:11 unRAID kernel: RBP: ffff888106ed5258 R08: 0000000000000000 R09: ffffffff82440510
Aug  8 10:15:11 unRAID kernel: R10: 00007fffffffffff R11: 0000000000000000 R12: ffff888106ed5258
Aug  8 10:15:11 unRAID kernel: R13: ffff888106ed5258 R14: ffffffff812f1e37 R15: ffff888105e0c878
Aug  8 10:15:11 unRAID kernel: FS:  00001554f9b5af00(0000) GS:ffff88845ed00000(0000) knlGS:0000000000000000
Aug  8 10:15:11 unRAID kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Aug  8 10:15:11 unRAID kernel: CR2: 00000000004b75d8 CR3: 00000001191dc001 CR4: 00000000003706f0
Aug  8 10:15:11 unRAID kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Aug  8 10:15:11 unRAID kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Aug  8 10:15:11 unRAID kernel: Call Trace:
Aug  8 10:15:11 unRAID kernel: <TASK>
Aug  8 10:15:11 unRAID kernel: ? __warn+0x99/0x11a
Aug  8 10:15:11 unRAID kernel: ? report_bug+0xdb/0x155
Aug  8 10:15:11 unRAID kernel: ? show_mark_fhandle+0x79/0xe8
Aug  8 10:15:11 unRAID kernel: ? handle_bug+0x3c/0x63
Aug  8 10:15:11 unRAID kernel: ? exc_invalid_op+0x13/0x60
Aug  8 10:15:11 unRAID kernel: ? asm_exc_invalid_op+0x16/0x20
Aug  8 10:15:11 unRAID kernel: ? __pfx_inotify_fdinfo+0x10/0x10
Aug  8 10:15:11 unRAID kernel: ? show_mark_fhandle+0x79/0xe8
Aug  8 10:15:11 unRAID kernel: ? __pfx_inotify_fdinfo+0x10/0x10
Aug  8 10:15:11 unRAID kernel: ? seq_vprintf+0x33/0x49
Aug  8 10:15:11 unRAID kernel: ? seq_printf+0x53/0x6e
Aug  8 10:15:11 unRAID kernel: ? preempt_latency_start+0x2b/0x46
Aug  8 10:15:11 unRAID kernel: inotify_fdinfo+0x83/0xaa
Aug  8 10:15:11 unRAID kernel: show_fdinfo.isra.0+0x63/0xab
Aug  8 10:15:11 unRAID kernel: seq_show+0x151/0x172
Aug  8 10:15:11 unRAID kernel: seq_read_iter+0x16e/0x353
Aug  8 10:15:11 unRAID kernel: ? do_filp_open+0x8e/0xb8
Aug  8 10:15:11 unRAID kernel: seq_read+0xe2/0x109
Aug  8 10:15:11 unRAID kernel: vfs_read+0xa3/0x197
Aug  8 10:15:11 unRAID kernel: ? __do_sys_newfstat+0x35/0x5c
Aug  8 10:15:11 unRAID kernel: ksys_read+0x76/0xc2
Aug  8 10:15:11 unRAID kernel: do_syscall_64+0x6c/0xdc
Aug  8 10:15:11 unRAID kernel: entry_SYSCALL_64_after_hwframe+0x78/0x80
Aug  8 10:15:11 unRAID kernel: RIP: 0033:0x1554f9de95cd
Aug  8 10:15:11 unRAID kernel: Code: 41 48 0e 00 f7 d8 64 89 02 b8 ff ff ff ff eb bb 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 80 3d 59 cc 0e 00 00 74 17 31 c0 0f 05 <48> 3d 00 f0 ff ff 77 5b c3 66 2e 0f 1f 84 00 00 00 00 00 48 83 ec
Aug  8 10:15:11 unRAID kernel: RSP: 002b:00007ffcea2d27b8 EFLAGS: 00000246 ORIG_RAX: 0000000000000000
Aug  8 10:15:11 unRAID kernel: RAX: ffffffffffffffda RBX: 000000000043f600 RCX: 00001554f9de95cd
Aug  8 10:15:11 unRAID kernel: RDX: 0000000000000400 RSI: 0000000000446ae0 RDI: 0000000000000007
Aug  8 10:15:11 unRAID kernel: RBP: 00001554f9ecd230 R08: 0000000000000001 R09: 0000000000000000
Aug  8 10:15:11 unRAID kernel: R10: 0000000000000000 R11: 0000000000000246 R12: 00001554f9ecd0e0
Aug  8 10:15:11 unRAID kernel: R13: 0000000000001000 R14: 0000000000000000 R15: 000000000043f600
Aug  8 10:15:11 unRAID kernel: </TASK>
Aug  8 10:15:11 unRAID kernel: ---[ end trace 0000000000000000 ]---

 

 

unraid-diagnostics-20240808-1034.zip

Solved by JorgeB

  • Community Expert
  • Solution

This call trace has been happening to almost everyone running 7.0.0-beta, it happens just once after every boot and it appears to be harmless:

 

 

  • Author

Thanks Jorge.

 

I shall ignore it, though somewhat strange that it has appeared after the server has been running for nearly 18 days.

 

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...

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.