2180233 – Centos 3.10.0-693.el7.x86_64 crashes after an SSH connection attempt when running Intel icelake-D 1736

This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 2180233 - Centos 3.10.0-693.el7.x86_64 crashes after an SSH connection attempt when running Intel icelake-D 1736

Summary: Centos 3.10.0-693.el7.x86_64 crashes after an SSH connection attempt when run...

Keywords:
Status:	CLOSED MIGRATED
Alias:	None
Product:	Red Hat Enterprise Linux 7
Classification:	Red Hat
Component:	openssh
Sub Component:
Version:	7.4-Alt
Hardware:	x86_64
OS:	Linux
Priority:	unspecified
Severity:	medium
Target Milestone:	rc
Target Release:	---
Assignee:	Dmitry Belyavskiy
QA Contact:	BaseOS QE Security Team
Docs Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+	depends on / blocked

Reported:	2023-03-21 01:56 UTC by idln
Modified:	2023-09-20 00:47 UTC (History)
CC List:	3 users (show)
Fixed In Version:
Doc Type:	If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:	2023-09-20 00:47:02 UTC
Target Upstream Version:
Embargoed:
Flags:	pm-rhel: mirror+

Attachments	(Terms of Use)
vmcore-dmesg output (72.20 KB, text/plain) 2023-03-21 01:56 UTC, idln	no flags	Details
ssh client log1 (86.50 KB, text/plain) 2023-03-22 09:03 UTC, idln	no flags	Details
this is ssh client log2 (86.50 KB, text/plain) 2023-03-22 09:04 UTC, idln	no flags	Details
ssh server log2 after reboot (940 bytes, text/plain) 2023-03-22 09:06 UTC, idln	no flags	Details
server crash print (45.54 KB, text/plain) 2023-03-23 06:08 UTC, idln	no flags	Details
vmcore.zip.001 (10.00 MB, application/zip) 2023-03-24 02:42 UTC, idln	no flags	Details
vmcore.zip.002 (10.00 MB, application/octet-stream) 2023-03-24 02:44 UTC, idln	no flags	Details
vmcore.zip.003 (2.53 MB, application/octet-stream) 2023-03-24 02:44 UTC, idln	no flags	Details
mce error (78.20 KB, image/png) 2023-03-31 07:57 UTC, idln	no flags	Details
View All

Links
System	ID	Private	Priority	Status	Summary	Last Updated
Red Hat Issue Tracker	RHEL-5284	0	None	Migrated	None	2023-09-20 00:46:53 UTC
Red Hat Issue Tracker	RHELPLAN-152506	0	None	None	None	2023-03-21 01:59:26 UTC

Description idln 2023-03-21 01:56:05 UTC

Created attachment 1952226 [details]
vmcore-dmesg output

Created attachment 1952226 [details]
vmcore-dmesg output

Created attachment 1952226 [details]
vmcore-dmesg output

Description of problem:


Version-Release number of selected component (if applicable):
Centos 7.4 3.10-693
How reproducible:

1. set an IP address, then ssh connect to login it, the kernel will hang or reboot, then behavior normal if do not AC cycle

Steps to Reproduce:
1. AC whole DUT which installed Centos 3.10.0-693
2. Confirm the network is accessable through ping
3. ssh to DUT, the DUT wil hang or reboot 
4. after then, ssh will be normal 

Actual results:
1. Reboot/hang with MCE error everytime after ssh

Expected results:
1. do not reboot or hang

Additional info:
Higher verison Centos 4.x, 5.x can not reproduce

Comment 3 Norbert Pócs 2023-03-21 14:09:37 UTC

Hi,

Too little information given to understand the nature of the bug, but it looks
like an openssh bug.

If you could provide a log from the client (if it's possible then from the
server too) by setting LogLevel=DEBUG3 that would help a lot.

Comment 4 idln 2023-03-22 09:03:20 UTC

Created attachment 1952696 [details]
ssh client log1

this is ssh client log1 before execute ssh command

Comment 5 idln 2023-03-22 09:04:26 UTC

Created attachment 1952697 [details]
this is ssh client log2

after execute ssh

Comment 6 idln 2023-03-22 09:06:12 UTC

Created attachment 1952698 [details]
ssh server log2 after reboot

Comment 7 Jakub Jelen 2023-03-22 13:13:20 UTC

Yeah, thats OpenSSH. Please, bump the debug log level (LogLevel DEBUG3 in /etc/ssh/sshd_config for server and -vvv command line switches for client) to see when the issue happens.

Do you have some coredumps?

Comment 8 idln 2023-03-23 06:08:02 UTC

Created attachment 1953004 [details]
server crash print

Comment 9 idln 2023-03-23 06:09:53 UTC

hi Jakub Jelen, 
ssh client output after ssh, i do not know how to get ssh server coredump after reboot.

[root@sw-lab-sha092 liun]# ssh root.1.41 -vvv
OpenSSH_7.4p1, OpenSSL 1.0.2k-fips  26 Jan 2017
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 58: Applying options for *
debug2: resolving "10.21.1.41" port 22
debug2: ssh_connect_direct: needpriv 0
debug1: Connecting to 10.21.1.41 [10.21.1.41] port 22.
debug1: Connection established.
debug1: permanently_set_uid: 0/0
debug1: identity file /root/.ssh/id_rsa type 1
debug1: key_load_public: No such file or directory
debug1: identity file /root/.ssh/id_rsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /root/.ssh/id_dsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /root/.ssh/id_dsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /root/.ssh/id_ecdsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /root/.ssh/id_ecdsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /root/.ssh/id_ed25519 type -1
debug1: key_load_public: No such file or directory
debug1: identity file /root/.ssh/id_ed25519-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_7.4
debug1: Remote protocol version 2.0, remote software version OpenSSH_7.4
debug1: match: OpenSSH_7.4 pat OpenSSH* compat 0x04000000
debug2: fd 3 setting O_NONBLOCK
debug1: Authenticating to 10.21.1.41:22 as 'root'
debug3: hostkeys_foreach: reading file "/root/.ssh/known_hosts"
debug3: record_hostkey: found key type ECDSA in file /root/.ssh/known_hosts:17
debug3: load_hostkeys: loaded 1 keys from 10.21.1.41
debug3: order_hostkeyalgs: prefer hostkeyalgs: ecdsa-sha2-nistp256-cert-v01,ecdsa-sha2-nistp384-cert-v01,ecdsa-sha2-nistp521-cert-v01,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521
debug3: send packet: type 20
debug1: SSH2_MSG_KEXINIT sent

Comment 10 idln 2023-03-24 02:42:57 UTC

Created attachment 1953314 [details]
vmcore.zip.001

Comment 11 idln 2023-03-24 02:44:18 UTC

Created attachment 1953315 [details]
vmcore.zip.002

Comment 12 idln 2023-03-24 02:44:53 UTC

Created attachment 1953316 [details]
vmcore.zip.003

Comment 13 idln 2023-03-24 02:47:21 UTC

Hi, 
Due to the filesize limitaiton, I split the vmcore file into 3 peices,
vmcore.zip.001 vmcore.zip.002 vmcore.zip.003
please unzip these simutaneously, thanks

Comment 14 idln 2023-03-28 06:52:53 UTC

Hi,
Thanks a lot for working on this issue.
Is there any method to replace specific package to bypass this issue? except upgrade to higher Linux kernel?
seems higher kernel version does not have this issue, thanks

Comment 15 idln 2023-03-31 07:57:55 UTC

Created attachment 1954843 [details]
mce error

Comment 17 RHEL Program Management 2023-09-19 23:58:36 UTC

Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 18 RHEL Program Management 2023-09-20 00:47:02 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.

Note You need to log in before you can comment on or make changes to this bug.