Enhanced Security Measures in Place:   To ensure a safer experience, we’ve implemented additional, temporary security measures for all users.

error message after Panorama boot

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

error message after Panorama boot

L3 Networker

Hi Anyone can help to take a look at the below error message after Panorama started to boot? Thanks

 

 

[<ffffffff8114bb1d>] ext3_writeback_writepage+0xc4/0x159
[<ffffffff810b80bd>] __writepage+0xe/0x26
[<ffffffff810b8561>] write_cache_pages+0x25d/0x36a
[<ffffffff810b80af>] ? mapping_tagged+0xf/0xf
[<ffffffff810b86a7>] generic_writepages+0x39/0x51
[<ffffffff810b9937>] do_writepages+0x20/0x27
[<ffffffff8111257e>] __writeback_single_inode+0x4f/0x1c3
[<ffffffff8111305b>] writeback_sb_inodes+0x1bf/0x2f8
[<ffffffff8111320e>] __writeback_inodes_wb+0x7a/0xb0
[<ffffffff811133f8>] wb_writeback+0x115/0x26a
[<ffffffff81113afe>] wb_do_writeback+0x12d/0x1b8
[<ffffffff81113c07>] bdi_writeback_workfn+0x7e/0x185
[<ffffffff81053e42>] process_one_work+0x1df/0x354
[<ffffffff81054add>] worker_thread+0x1d5/0x2c1
[<ffffffff81054908>] ? rescuer_thread+0x272/0x272
[<ffffffff81058fba>] kthread+0xb5/0xbd
[<ffffffff81058f05>] ? kthread_create_on_node+0x10e/0x10e
[<ffffffff814ae6d8>] ret_from_fork+0x58/0x90
[<ffffffff81058f05>] ? kthread_create_on_node+0x10e/0x10e
INFO: task kjournald:653 blocked for more than 120 seconds.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
ffff88042ace3c68 0000000000000046 ffff88042ace3fd8 ffff88042ace3fd8
0000000000012340 ffff88042b230280 ffff88042adbe4f0 ffff88042aef2808
0000000000000001 ffff88042aef27d8 0000000010200001 ffff88042ace3bd0
Call Trace:
[<ffffffff811f7363>] ? elv_rb_add+0x5f/0x61
[<ffffffff8120e149>] ? cfq_add_rq_rb+0x62/0x88
[<ffffffff8120e34e>] ? cfq_insert_request+0x1df/0x395
[<ffffffff81031511>] ? kvm_clock_read+0x1f/0x21
[<ffffffff8103151c>] ? kvm_clock_get_cycles+0x9/0xb
[<ffffffff81117788>] ? generic_block_bmap+0x40/0x40
[<ffffffff814a6eb8>] schedule+0x64/0x66
[<ffffffff814a70a2>] io_schedule+0x8a/0xc8
[<ffffffff81117791>] sleep_on_buffer+0x9/0xd
[<ffffffff814a5731>] __wait_on_bit+0x41/0x71
[<ffffffff814a57d7>] out_of_line_wait_on_bit+0x76/0x81
[<ffffffff81117788>] ? generic_block_bmap+0x40/0x40
[<ffffffff81059a0a>] ? autoremove_wake_function+0x2f/0x2f
[<ffffffff81117829>] __wait_on_buffer+0x21/0x23
[<ffffffff811a5621>] journal_commit_transaction+0x94a/0xf4d
[<ffffffff811a8a42>] kjournald+0xd7/0x23f
[<ffffffff810599db>] ? wake_up_bit+0x25/0x25
[<ffffffff811a896b>] ? commit_timeout+0xb/0xb
[<ffffffff81058fba>] kthread+0xb5/0xbd
[<ffffffff81058f05>] ? kthread_create_on_node+0x10e/0x10e
[<ffffffff814ae6d8>] ret_from_fork+0x58/0x90
[<ffffffff81058f05>] ? kthread_create_on_node+0x10e/0x10e

 

1 accepted solution

Accepted Solutions

Cyber Elite
Cyber Elite

Hello @kevinospf

 

thanks for posting.

 

The closest I could find is this KB.

The pattern of error you posted looks similar to the one in the KB. Could you check first KVM host side?

 

Kind Regards

Pavel

Help the community: Like helpful comments and mark solutions.

View solution in original post

1 REPLY 1

Cyber Elite
Cyber Elite

Hello @kevinospf

 

thanks for posting.

 

The closest I could find is this KB.

The pattern of error you posted looks similar to the one in the KB. Could you check first KVM host side?

 

Kind Regards

Pavel

Help the community: Like helpful comments and mark solutions.
  • 1 accepted solution
  • 876 Views
  • 1 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!