My Oracle Support Banner

After Patching Exalogic Physical Oct 2018 PSU, compute node reboot hangs (Doc ID 2530975.1)

Last updated on NOVEMBER 08, 2019

Applies to:

Oracle Exalogic Elastic Cloud Software - Version 2.0.6.3.181016 to 2.0.6.3.181016
Information in this document applies to any platform.

Symptoms

After Patching Exalogic Physical Oct 2018 PSU in the compute node, the compute node reboot hangs.

We'll see similar stack trace as below:

input: Oracle P3rKM as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.7/2-1.7:1.0/input/input4
generic-usb 0003:0430:A101.0003: input,hidraw0: USB HID v1.11 Keyboard [Oracle P3rKM ] on usb-0000:00:1d.0-1.7/input0
input: Oracle P3rKM as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.7/2-1.7:1.1/input/input5
generic-usb 0003:0430:A101.0004: input,hidraw1: USB HID v1.11 Mouse [Oracle P3rKM ] on usb-0000:00:1d.0-1.7/input1
INFO: task perl:6118 blocked for more than 120 seconds.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
perl D ffff883c64d7e5e8 0 6118 1 0x00000080
ffff883c7bc179c8 0000000000000046 ffff883c7bc179c8 ffffffffa04cbded
0000000000011ac0 ffff883c7bc17fd8 ffff883c7bc16010 0000000000011ac0
ffff883c7bc17fd8 0000000000011ac0 ffff883f04a2c200 ffff883c64d7e040
Call Trace:
[<ffffffffa04cbded>] ? nfs_initiate_write+0xdd/0x150 [nfs]
[<ffffffff8109e3ad>] ? ktime_get_ts+0xad/0xe0
[<ffffffff81112e00>] ? __lock_page+0x70/0x70
[<ffffffff8151150f>] schedule+0x3f/0x60
[<ffffffff815115bc>] io_schedule+0x8c/0xd0
[<ffffffff81112e0e>] sleep_on_page+0xe/0x20
[<ffffffff81511caf>] __wait_on_bit+0x5f/0x90
[<ffffffff81113053>] wait_on_page_bit+0x73/0x80
[<ffffffff81093940>] ? autoremove_wake_function+0x50/0x50
[<ffffffff8111eea5>] ? pagevec_lookup_tag+0x25/0x40
[<ffffffff81113613>] filemap_fdatawait_range+0x113/0x1a0
[<ffffffffa04c6d80>] ? nfs_file_direct_write_iter+0x50/0x50 [nfs]
[<ffffffff8111e041>] ? do_writepages+0x21/0x40
[<ffffffff8111372b>] ? __filemap_fdatawrite_range+0x5b/0x60
[<ffffffff811137a0>] filemap_write_and_wait_range+0x70/0x80
[<ffffffff8119d01d>] vfs_fsync_range+0x5d/0xa0
[<ffffffff8119d0cc>] vfs_fsync+0x1c/0x20
[<ffffffffa04baf04>] nfs_file_flush+0x54/0x80 [nfs]
[<ffffffff8116ef8c>] filp_close+0x3c/0x90
[<ffffffff81072a9f>] put_files_struct+0x7f/0xf0
[<ffffffff81072b64>] exit_files+0x54/0x70
[<ffffffff81074f90>] do_exit+0x1a0/0x460
[<ffffffff81086361>] ? __dequeue_signal+0x111/0x210
[<ffffffff810752a5>] do_group_exit+0x55/0xd0
[<ffffffff81086aaf>] get_signal_to_deliver+0x21f/0x480
[<ffffffff81015a19>] do_signal+0x69/0x190
[<ffffffff810973b0>] ? update_rmtp+0x80/0x80
[<ffffffff81015ba5>] do_notify_resume+0x65/0x80
[<ffffffff8151cb53>] int_signal+0x12/0x17
INFO: task java:6977 blocked for more than 120 seconds.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
java D ffff887c75a467e8 0 6977 6120 0x00000084
ffff887f04505978 0000000000000082 0000000000000000 0000000000000000
0000000000011ac0 ffff887f04505fd8 ffff887f04504010 0000000000011ac0
ffff887f04505fd8 0000000000011ac0 ffff883f06b20300 ffff887c75a46240
Call Trace:
[<ffffffff81112e00>] ? __lock_page+0x70/0x70
[<ffffffff8151150f>] schedule+0x3f/0x60
[<ffffffff815115bc>] io_schedule+0x8c/0xd0
[<ffffffff81112e0e>] sleep_on_page+0xe/0x20
[<ffffffff81511caf>] __wait_on_bit+0x5f/0x90
[<ffffffffa04c7079>] ? nfs_release_request+0x19/0x20 [nfs]
[<ffffffff81113053>] wait_on_page_bit+0x73/0x80
[<ffffffff81093940>] ? autoremove_wake_function+0x50/0x50
[<ffffffff81113efc>] grab_cache_page_write_begin+0x9c/0xd0
[<ffffffffa04bab49>] nfs_write_begin+0x79/0x210 [nfs]
[<ffffffffa04bbffd>] ? nfs_write_end+0x16d/0x2c0 [nfs]
[<ffffffff81135908>] ? ii_iovec_copy_from_user_atomic+0x98/0x170
[<ffffffff81112483>] generic_perform_write+0xc3/0x1c0
[<ffffffff811125ab>] generic_file_buffered_write_iter+0x2b/0x60
[<ffffffff8111529d>] __generic_file_write_iter+0x1fd/0x3f0
[<ffffffff81510dec>] ? __schedule+0x39c/0x720
[<ffffffff81115515>] __generic_file_aio_write+0x85/0xa0
[<ffffffff8111559f>] generic_file_aio_write+0x6f/0xc0
[<ffffffffa04bb941>] nfs_file_write+0xb1/0x1e0 [nfs]
[<ffffffff81170eb2>] do_sync_write+0xe2/0x120
[<ffffffff810a7a72>] ? futex_wake+0x122/0x140
[<ffffffff812042d3>] ? security_file_permission+0x23/0x90
[<ffffffff81171448>] vfs_write+0xc8/0x190
[<ffffffff81171611>] sys_write+0x51/0x90
[<ffffffff810d269b>] ? audit_syscall_exit+0x25b/0x290
[<ffffffff8151c818>] system_call_fastpath+0x16/0x1b
INFO: task java:7516 blocked for more than 120 seconds.

 


However, if they do a 'stop -f /SYS' followed by 'start /SYS' from ILOM, that brings up the compute node cleanly.

 

Changes

 Applied Exalogic Physical Oct 2018 PSU

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.