Bug 2180233
| Summary: | Centos 3.10.0-693.el7.x86_64 crashes after an SSH connection attempt when running Intel icelake-D 1736 | ||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | idln | ||||||||||||||||||||
| Component: | openssh | Assignee: | Dmitry Belyavskiy <dbelyavs> | ||||||||||||||||||||
| Status: | CLOSED MIGRATED | QA Contact: | BaseOS QE Security Team <qe-baseos-security> | ||||||||||||||||||||
| Severity: | medium | Docs Contact: | |||||||||||||||||||||
| Priority: | unspecified | ||||||||||||||||||||||
| Version: | 7.4-Alt | CC: | idln, jjelen, mpitt | ||||||||||||||||||||
| Target Milestone: | rc | Keywords: | Extras, MigratedToJIRA | ||||||||||||||||||||
| Target Release: | --- | Flags: | pm-rhel:
mirror+
|
||||||||||||||||||||
| Hardware: | x86_64 | ||||||||||||||||||||||
| OS: | Linux | ||||||||||||||||||||||
| Whiteboard: | |||||||||||||||||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||||||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||||||||||
| Clone Of: | Environment: | ||||||||||||||||||||||
| Last Closed: | 2023-09-20 00:47:02 UTC | Type: | Bug | ||||||||||||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||||||||||||
| Documentation: | --- | CRM: | |||||||||||||||||||||
| Verified Versions: | Category: | --- | |||||||||||||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||||||||||
| Embargoed: | |||||||||||||||||||||||
| Attachments: |
|
||||||||||||||||||||||
|
Description
idln
2023-03-21 01:56:05 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. Created attachment 1952696 [details]
ssh client log1
this is ssh client log1 before execute ssh command
Created attachment 1952697 [details]
this is ssh client log2
after execute ssh
Created attachment 1952698 [details]
ssh server log2 after reboot
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? Created attachment 1953004 [details]
server crash print
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 Created attachment 1953314 [details]
vmcore.zip.001
Created attachment 1953315 [details]
vmcore.zip.002
Created attachment 1953316 [details]
vmcore.zip.003
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 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 Created attachment 1954843 [details]
mce error
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. 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. |