Jump to content
kakmoster

Call Traces found

10 posts in this topic Last Reply

Recommended Posts

Can't see the call trace in your logs it looks like it was a while back though.

A few suggestions though upgrade 6.5.0 to 6.5.2 in tools/ Update OS there was a lot of patches.

Try running the offical Plex Docker from the App store now Plex inc have their own one, i have run into some odd issues with transcoding problems with linuxserver.io image.

 

the iGPU hardware encoding is great for 720p,1080p and 4k encodings but lower quality content doesn't look that great. But each to their own. :)

If you are trying to speed up transcoding suggestion is map /transcode to /tmp and that will use ram instead of the SSD it shaves a few seconds off the stream start.

Share this post


Link to post
13 hours ago, Maticks said:

Can't see the call trace in your logs it looks like it was a while back though.

A few suggestions though upgrade 6.5.0 to 6.5.2 in tools/ Update OS there was a lot of patches.

Try running the offical Plex Docker from the App store now Plex inc have their own one, i have run into some odd issues with transcoding problems with linuxserver.io image.

 

the iGPU hardware encoding is great for 720p,1080p and 4k encodings but lower quality content doesn't look that great. But each to their own. :)

If you are trying to speed up transcoding suggestion is map /transcode to /tmp and that will use ram instead of the SSD it shaves a few seconds off the stream start.

 

Alright I will upgrade, didn't know 6.5.2 was released. :) I am running the official Plex docker.

 

Almost my content is 1080p or 4k, I direct stream at home to my htpc, it's my sister who need transcoding, she has slower internet. But never transcode in less than 720p to her. 

 

Thank you

Share this post


Link to post

nothing in the diags showing the call trace information other than the addon reporting there is one there.

you might need to check the console for them and pull out some information.

 

Share this post


Link to post
On 5/30/2018 at 3:51 PM, Maticks said:

nothing in the diags showing the call trace information other than the addon reporting there is one there.

you might need to check the console for them and pull out some information.

 

How do I manually get this information?

Share this post


Link to post

Jul  8 18:45:22 DeusVult kernel: Call Trace:
Jul  8 18:45:22 DeusVult kernel: local_pci_probe+0x3c/0x7a
Jul  8 18:45:22 DeusVult kernel: pci_device_probe+0x11b/0x154
Jul  8 18:45:22 DeusVult kernel: driver_probe_device+0x142/0x2a6
Jul  8 18:45:22 DeusVult kernel: __driver_attach+0x68/0x88
Jul  8 18:45:22 DeusVult kernel: ? driver_probe_device+0x2a6/0x2a6
Jul  8 18:45:22 DeusVult kernel: bus_for_each_dev+0x63/0x7a
Jul  8 18:45:22 DeusVult kernel: bus_add_driver+0xe1/0x1c6
Jul  8 18:45:22 DeusVult kernel: driver_register+0x7d/0xaf
Jul  8 18:45:22 DeusVult kernel: ? 0xffffffffa02dc000
Jul  8 18:45:22 DeusVult kernel: do_one_initcall+0x89/0x11e
Jul  8 18:45:22 DeusVult kernel: ? kmem_cache_alloc+0x9f/0xe8
Jul  8 18:45:22 DeusVult kernel: do_init_module+0x51/0x1be
Jul  8 18:45:22 DeusVult kernel: load_module+0x1854/0x1e3f
Jul  8 18:45:22 DeusVult kernel: ? SyS_init_module+0xba/0xe0
Jul  8 18:45:22 DeusVult kernel: SyS_init_module+0xba/0xe0
Jul  8 18:45:22 DeusVult kernel: do_syscall_64+0x6d/0xfe
Jul  8 18:45:22 DeusVult kernel: entry_SYSCALL_64_after_hwframe+0x3d/0xa2
Jul  8 18:45:22 DeusVult kernel: RIP: 0033:0x14bb588958aa
Jul  8 18:45:22 DeusVult kernel: RSP: 002b:00007ffeacc548c8 EFLAGS: 00000246 ORIG_RAX: 00000000000000af
Jul  8 18:45:22 DeusVult kernel: RAX: ffffffffffffffda RBX: 0000000000625e50 RCX: 000014bb588958aa
Jul  8 18:45:22 DeusVult kernel: RDX: 0000000000629be0 RSI: 00000000002202e8 RDI: 0000000000f1fa80
Jul  8 18:45:22 DeusVult kernel: RBP: 0000000000629be0 R08: ffffffffffffffe0 R09: 00007ffeacc52a68
Jul  8 18:45:22 DeusVult kernel: R10: 0000000000623010 R11: 0000000000000246 R12: 0000000000f1fa80
Jul  8 18:45:22 DeusVult kernel: R13: 0000000000625f80 R14: 0000000000040000 R15: 0000000000000000
Jul  8 18:45:22 DeusVult kernel: Code: 00 e8 6a c7 e7 ff 8b 83 28 06 00 00 83 e8 16 83 e0 fd 0f 84 16 02 00 00 48 c7 c6 aa cf 4c a0 48 c7 c7 a7 c9 4c a0 e8 d4 32 c6 e0 <0f> 0b e9 fc 01 00 00 66 3d 00 a3 75 4e 48 c7 c2 49 d0 4c a0 be 
Jul  8 18:45:22 DeusVult kernel: ---[ end trace 3f2b0267604ec704 ]---

 

I'm getting also call traces on the i915, noticed since 6.5.3 series. Did a post here: https://lime-technology.com/forums/topic/72427-call-trace-on-653-series/

Looks like the i915 driver / module is funky after 6.5.2 for more users other then me on unraid.

Since hardware transcoding is still working properly, i muted the error.

 

 

Share this post


Link to post
18 hours ago, SiNtEnEl said:

Jul  8 18:45:22 DeusVult kernel: Call Trace:
Jul  8 18:45:22 DeusVult kernel: local_pci_probe+0x3c/0x7a
Jul  8 18:45:22 DeusVult kernel: pci_device_probe+0x11b/0x154
Jul  8 18:45:22 DeusVult kernel: driver_probe_device+0x142/0x2a6
Jul  8 18:45:22 DeusVult kernel: __driver_attach+0x68/0x88
Jul  8 18:45:22 DeusVult kernel: ? driver_probe_device+0x2a6/0x2a6
Jul  8 18:45:22 DeusVult kernel: bus_for_each_dev+0x63/0x7a
Jul  8 18:45:22 DeusVult kernel: bus_add_driver+0xe1/0x1c6
Jul  8 18:45:22 DeusVult kernel: driver_register+0x7d/0xaf
Jul  8 18:45:22 DeusVult kernel: ? 0xffffffffa02dc000
Jul  8 18:45:22 DeusVult kernel: do_one_initcall+0x89/0x11e
Jul  8 18:45:22 DeusVult kernel: ? kmem_cache_alloc+0x9f/0xe8
Jul  8 18:45:22 DeusVult kernel: do_init_module+0x51/0x1be
Jul  8 18:45:22 DeusVult kernel: load_module+0x1854/0x1e3f
Jul  8 18:45:22 DeusVult kernel: ? SyS_init_module+0xba/0xe0
Jul  8 18:45:22 DeusVult kernel: SyS_init_module+0xba/0xe0
Jul  8 18:45:22 DeusVult kernel: do_syscall_64+0x6d/0xfe
Jul  8 18:45:22 DeusVult kernel: entry_SYSCALL_64_after_hwframe+0x3d/0xa2
Jul  8 18:45:22 DeusVult kernel: RIP: 0033:0x14bb588958aa
Jul  8 18:45:22 DeusVult kernel: RSP: 002b:00007ffeacc548c8 EFLAGS: 00000246 ORIG_RAX: 00000000000000af
Jul  8 18:45:22 DeusVult kernel: RAX: ffffffffffffffda RBX: 0000000000625e50 RCX: 000014bb588958aa
Jul  8 18:45:22 DeusVult kernel: RDX: 0000000000629be0 RSI: 00000000002202e8 RDI: 0000000000f1fa80
Jul  8 18:45:22 DeusVult kernel: RBP: 0000000000629be0 R08: ffffffffffffffe0 R09: 00007ffeacc52a68
Jul  8 18:45:22 DeusVult kernel: R10: 0000000000623010 R11: 0000000000000246 R12: 0000000000f1fa80
Jul  8 18:45:22 DeusVult kernel: R13: 0000000000625f80 R14: 0000000000040000 R15: 0000000000000000
Jul  8 18:45:22 DeusVult kernel: Code: 00 e8 6a c7 e7 ff 8b 83 28 06 00 00 83 e8 16 83 e0 fd 0f 84 16 02 00 00 48 c7 c6 aa cf 4c a0 48 c7 c7 a7 c9 4c a0 e8 d4 32 c6 e0 <0f> 0b e9 fc 01 00 00 66 3d 00 a3 75 4e 48 c7 c2 49 d0 4c a0 be 
Jul  8 18:45:22 DeusVult kernel: ---[ end trace 3f2b0267604ec704 ]---

 

I'm getting also call traces on the i915, noticed since 6.5.3 series. Did a post here: https://lime-technology.com/forums/topic/72427-call-trace-on-653-series/

Looks like the i915 driver / module is funky after 6.5.2 for more users other then me on unraid.

Since hardware transcoding is still working properly, i muted the error.

 

 

All right, it began when I activated the beta/alpha support driver, it seems to work flawlessly for me aswell. Just gonna mute it for the moment as well then. 

  • Like 1

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now