You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It happens on the initiator's side when the target server is unexpectedly rebooted on OL8 UEK6. We tested using different OS and iSCSI node.session.nr_sessions parameters and came to conclusion that only UEK6 with nr_sessions > 1 is affected. The failure frequency is about 5 failures for 25 reboots (20%).
The summary of the configurations we tested is below:
OS
Kernel
Kernel Acronym
node.session.nr_sessions
Kernel panic?
OL7
3.10.0-1160.119.1.0.1.el7.x86_64
RHCK
4
😃No
OL8
5.4.17-2136.334.6.1.el8uek.x86_64
UEK6
1
😃No
OL8
5.4.17-2136.334.6.1.el8uek.x86_64
UEK6
2
😡Yes
OL8
5.4.17-2136.334.6.1.el8uek.x86_64
UEK6
4
😡Yes
RHEL8
4.18.0-553.8.1.el8_10.x86_64
RHCK
4
😃No
OL9
5.15.0-205.149.5.4.el9uek.x86_64
UEK7
4
😃No
RHEL9
5.14.0-427.16.1.el9_4.x86_64
RHCK
4
😃No
These specific kernel traces are from Azure but we have encountered this issue on AWS too, so that it is not Azure specific.
The text was updated successfully, but these errors were encountered:
GitHub Issues is not an official support channel and we don't offer
product support here. If you're not yet an Oracle Linux customer,
consider signing up at https://linux.oracle.com.
Even if you're not a customer, if we can confirm that an issue is a
bug we will do our best to fix it and to update this issue
once it has been fixed. We don't guarantee a fix or feedback and
for now, we will close this issue. If you have Oracle Linux support,
please use support.oracle.com to report issues.
Traces with the latest
5.4.17-2136.334.6.1.el8uek.x86_64
UEK6 kernel.kernel NULL pointer dereference
unable to handle page fault for address
Details
It happens on the initiator's side when the target server is unexpectedly rebooted on OL8 UEK6. We tested using different OS and iSCSI
node.session.nr_sessions
parameters and came to conclusion that only UEK6 withnr_sessions > 1
is affected. The failure frequency is about 5 failures for 25 reboots (20%).The summary of the configurations we tested is below:
node.session.nr_sessions
3.10.0-1160.119.1.0.1.el7.x86_64
5.4.17-2136.334.6.1.el8uek.x86_64
5.4.17-2136.334.6.1.el8uek.x86_64
5.4.17-2136.334.6.1.el8uek.x86_64
4.18.0-553.8.1.el8_10.x86_64
5.15.0-205.149.5.4.el9uek.x86_64
5.14.0-427.16.1.el9_4.x86_64
These specific kernel traces are from Azure but we have encountered this issue on AWS too, so that it is not Azure specific.
The text was updated successfully, but these errors were encountered: