Bad RIP Value, RIP: 0033:0x7f767e8f732b

hi,

can you please give more context?

where and when do you see this error?
did it start happening after upgrades?
can you also post the full stack trace?
mathgrad said:
04-05-2021 and intel-microcode installed.
Click to expand...
please post also pveversion -v output
 
Under root login it is printing stack traces to the shell.
It's been happening for a while but I haven't been able to address this issue until now.
How do I get the stack trace?
 

Attachments

mathgrad said:
Under root login it is printing stack traces to the shell.
It's been happening for a while but I haven't been able to address this issue until now.
How do I get the stack trace?
Click to expand...
Oh, ran dmesg and got this stack trace after a google search indicating that's what to do?
 

Attachments

thank you for the outputs.

[ 5923.762015] Call Trace:
[ 5923.762577] __schedule+0x2e6/0x700
[ 5923.763041] schedule+0x33/0xa0
[ 5923.763514] schedule_timeout+0x152/0x330
[ 5923.764008] ? __next_timer_interrupt+0xd0/0xd0
[ 5923.764582] io_schedule_timeout+0x1e/0x50
[ 5923.765126] __cv_timedwait_common+0x138/0x170 [spl]
[ 5923.765689] ? wait_woken+0x80/0x80
[ 5923.766266] __cv_timedwait_io+0x19/0x20 [spl]
[ 5923.766991] zio_wait+0x139/0x280 [zfs]
[ 5923.767693] dsl_pool_sync+0x45f/0x510 [zfs]
[ 5923.768431] spa_sync+0x5a4/0xfe0 [zfs]
[ 5923.769208] ? spa_txg_history_init_io+0x104/0x110 [zfs]
[ 5923.769995] txg_sync_thread+0x2e1/0x4a0 [zfs]
[ 5923.770803] ? txg_thread_exit.isra.13+0x60/0x60 [zfs]
[ 5923.771539] thread_generic_wrapper+0x74/0x90 [spl]
[ 5923.772296] kthread+0x120/0x140
[ 5923.773100] ? __thread_exit+0x20/0x20 [spl]
[ 5923.773895] ? kthread_park+0x90/0x90
[ 5923.775211] ret_from_fork+0x35/0x40
[ 6407.083174] INFO: task journal-offline:1095415 blocked for more than 120 seconds.
[ 6407.085317] Tainted: P O 5.4.106-1-pve #1
[ 6407.087419] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 6407.089605] journal-offline D 0 1095415 11257 0x00000320
[ 6407.091940] Call Trace:
[ 6407.094235] __schedule+0x2e6/0x700
[ 6407.096604] schedule+0x33/0xa0
[ 6407.098981] io_schedule+0x16/0x40
[ 6407.101382] wait_on_page_bit+0x141/0x210
[ 6407.103931] ? file_fdatawait_range+0x30/0x30
[ 6407.106436] wait_on_page_writeback+0x43/0x90
[ 6407.109003] __filemap_fdatawait_range+0xae/0x120
[ 6407.111551] filemap_write_and_wait_range+0x5c/0xb0
[ 6407.114329] zpl_fsync+0x3c/0xa0 [zfs]
[ 6407.116919] vfs_fsync_range+0x48/0x80
[ 6407.119530] ? __fget_light+0x59/0x70
[ 6407.122090] do_fsync+0x3d/0x70
[ 6407.124636] __x64_sys_fsync+0x14/0x20
[ 6407.127185] do_syscall_64+0x57/0x190
[ 6407.129742] entry_SYSCALL_64_after_hwframe+0x44/0xa9
[ 6407.132392] RIP: 0033:0x7f767e8f732b
[ 6407.135070] Code: Bad RIP value.
Click to expand...
see this thread also from couple weeks ago [0] with the same call trace.

* how often do you get this error? can you remember when it first showed up? if you have the syslogs you can grep through them for txg_sync_thread or 'Call Trace'
Code: 
zgrep txg_sync_thread /var/log/syslog.*.gz
zgrep 'Call trace:' /var/log/syslog.*.gz

* is your server under high i/o load when this error shows up?
* disks too slow? what kind of disks do you have? if you have consumer grade HDD then it can be too slow


[0]: https://forum.proxmox.com/threads/pve-kernel-error.86349/
 
Not to date myself but they're 6gb/s SAS constellation drives, I don't know how long the error has been occurring but did show up after a apt upgrade command. I recently had an I/O bug that wasn't entering/displaying characters properly inside a VM. I'll open a new thread for that issue also.
 
You must log in or register to reply here.
Top Bottom