Description of problem: Create fcoe instances on the NICs of the server,then run the following command,you will see abrt happens >>> fcoe.unconfigure_soft_fcoe() INFO: [2018-08-19 09:11:23] Running: 'service lldpad stop'... Redirecting to /bin/systemctl stop lldpad.service Warning: Stopping lldpad.service, but it can still be activated by: lldpad.socket INFO: [2018-08-19 09:11:24] Running: 'service fcoe stop'... Redirecting to /bin/systemctl stop fcoe.service INFO: [2018-08-19 09:11:24] Running: 'service fcoe status|grep "Active: active" '... Redirecting to /bin/systemctl status fcoe.service INFO: [2018-08-19 09:11:24] Running: 'chkconfig lldpad off'... Note: Forwarding request to 'systemctl disable lldpad.service'. INFO: [2018-08-19 09:11:24] Running: 'chkconfig fcoe off'... Note: Forwarding request to 'systemctl disable fcoe.service'. INFO: [2018-08-19 09:11:24] Running: 'rm -rf /etc/fcoe/cfg-ens2f0'... INFO: [2018-08-19 09:11:24] Running: 'rm -rf /etc/fcoe/cfg-ens2f1'... INFO: [2018-08-19 09:11:24] Running: 'modprobe -r ixgbe'... INFO: [2018-08-19 09:11:25] Running: 'modprobe ixgbe'... True [root@storageqe-13 abrt]# journalctl -p 3 | tail -n 20 Aug 19 09:01:27 storageqe-13.rhts.eng.bos.redhat.com kernel: rport-6:0-5: blocked FC remote port time out: removing rport Aug 19 09:11:24 storageqe-13.rhts.eng.bos.redhat.com dhclient[7465]: receive_packet failed on ens2f1: Network is down Aug 19 09:11:24 storageqe-13.rhts.eng.bos.redhat.com dhclient[7234]: receive_packet failed on ens2f0: Network is down Aug 19 09:11:24 storageqe-13.rhts.eng.bos.redhat.com kernel: sd 5:0:0:0: rejecting I/O to offline device Aug 19 09:11:25 storageqe-13.rhts.eng.bos.redhat.com kernel: print_req_error: I/O error, dev sdb, sector 20971392 Aug 19 09:11:25 storageqe-13.rhts.eng.bos.redhat.com kernel: sd 5:0:1:0: rejecting I/O to offline device Aug 19 09:11:25 storageqe-13.rhts.eng.bos.redhat.com kernel: print_req_error: I/O error, dev dm-3, sector 20971392 Aug 19 09:11:25 storageqe-13.rhts.eng.bos.redhat.com kernel: print_req_error: I/O error, dev dm-3, sector 20971392 Aug 19 09:11:25 storageqe-13.rhts.eng.bos.redhat.com kernel: Buffer I/O error on dev dm-3, logical block 2621424, async page read Aug 19 09:11:26 storageqe-13.rhts.eng.bos.redhat.com systemd-coredump[7923]: Process 7774 (lldpad) of user 0 dumped core. Stack trace of thread 7774: #0 0x000055f74a4ceaec ecp22_start.cold.10 (lldpad) #1 0x000055f74a502898 evb22_timer (lldpad) #2 0x000055f74a4e11aa timer (lldpad) #3 0x000055f74a4d4b31 eloop_run (lldpad) #4 0x000055f74a4cefc2 main (lldpad) #5 0x00007f1c7348d413 __libc_start_main (libc.so.6) #6 0x000055f74a4cf21a _start (lldpad) Aug 19 09:11:26 storageqe-13.rhts.eng.bos.redhat.com abrt-notification[8007]: Process 5393 (lldpad) crashed in ecp22_start.cold.10() Version-Release number of selected component (if applicable): kernel-4.18.1-300.fc29.x86_64 fcoe-utils-1.0.32-6.fc29.x86_64 How reproducible: always Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Created attachment 1476903 [details] abrt dump
The problem seems become more serious,there are plenty of abrt dump created once [root@storageqe-16 ~]# ls /var/spool/abrt oops-2018-09-16-05:57:06-659-0 oops-2018-09-16-05:57:18-659-1 oops-2018-09-16-05:57:34-659-0 oops-2018-09-16-07:03:36-659-1 oops-2018-09-16-07:03:49-659-1 oops-2018-09-16-07:04:05-659-0 oops-2018-09-16-05:57:06-659-1 oops-2018-09-16-05:57:24-659-0 oops-2018-09-16-05:57:37-659-1 oops-2018-09-16-07:03:39-659-0 oops-2018-09-16-07:03:53-659-1 oops-2018-09-16-07:04:07-659-0 oops-2018-09-16-05:57:10-659-1 oops-2018-09-16-05:57:26-659-0 oops-2018-09-16-05:57:40-659-0 oops-2018-09-16-07:03:42-659-1 oops-2018-09-16-07:03:56-659-0 oops-2018-09-16-07:04:09-659-0 oops-2018-09-16-05:57:13-659-0 oops-2018-09-16-05:57:28-659-0 oops-2018-09-16-05:57:42-659-0 oops-2018-09-16-07:03:46-659-0 oops-2018-09-16-07:03:59-659-1 oops-2018-09-16-05:57:15-659-0 oops-2018-09-16-05:57:31-659-1 oops-2018-09-16-07:03:33-659-1 oops-2018-09-16-07:03:46-659-1 oops-2018-09-16-07:04:02-659-0 [root@storageqe-16 ~]# journalctl -p 3 ... Sep 16 07:03:28 storageqe-16.rhts.eng.bos.redhat.com kernel: ULP_STOP Sep 16 07:03:28 storageqe-16.rhts.eng.bos.redhat.com kernel: bnx2fc: DESTROY success Sep 16 07:03:29 storageqe-16.rhts.eng.bos.redhat.com dhclient[2377]: receive_packet failed on ens2f1: Network is down Sep 16 07:03:29 storageqe-16.rhts.eng.bos.redhat.com kernel: ULP_STOP Sep 16 07:03:29 storageqe-16.rhts.eng.bos.redhat.com kernel: ULP_STOP Sep 16 07:03:31 storageqe-16.rhts.eng.bos.redhat.com kernel: bnx2fc: DESTROY success Sep 16 07:03:33 storageqe-16.rhts.eng.bos.redhat.com abrt-notification[3370]: System encountered a non-fatal error in device_del() Sep 16 07:03:35 storageqe-16.rhts.eng.bos.redhat.com abrt-notification[3391]: System encountered a non-fatal error in ??() Sep 16 07:03:36 storageqe-16.rhts.eng.bos.redhat.com abrt-notification[3402]: System encountered a non-fatal error in device_del() Sep 16 07:03:39 storageqe-16.rhts.eng.bos.redhat.com abrt-notification[3424]: System encountered a non-fatal error in ??() Sep 16 07:03:40 storageqe-16.rhts.eng.bos.redhat.com abrt-notification[3444]: System encountered a non-fatal error in ??() Sep 16 07:03:42 storageqe-16.rhts.eng.bos.redhat.com abrt-notification[3455]: System encountered a non-fatal error in device_del() Sep 16 07:03:44 storageqe-16.rhts.eng.bos.redhat.com abrt-notification[3482]: System encountered a non-fatal error in ??() Sep 16 07:03:47 storageqe-16.rhts.eng.bos.redhat.com abrt-notification[3505]: System encountered a non-fatal error in device_del() Sep 16 07:03:48 storageqe-16.rhts.eng.bos.redhat.com abrt-notification[3524]: System encountered a non-fatal error in ??() Sep 16 07:03:49 storageqe-16.rhts.eng.bos.redhat.com abrt-notification[3537]: System encountered a non-fatal error in device_del() Sep 16 07:03:51 storageqe-16.rhts.eng.bos.redhat.com abrt-notification[3559]: System encountered a non-fatal error in ??() Sep 16 07:03:53 storageqe-16.rhts.eng.bos.redhat.com abrt-notification[3570]: System encountered a non-fatal error in device_del() Sep 16 07:03:55 storageqe-16.rhts.eng.bos.redhat.com abrt-notification[3592]: System encountered a non-fatal error in ??() Sep 16 07:03:57 storageqe-16.rhts.eng.bos.redhat.com abrt-notification[3612]: System encountered a non-fatal error in ??() Sep 16 07:03:59 storageqe-16.rhts.eng.bos.redhat.com abrt-notification[3627]: System encountered a non-fatal error in device_del() Sep 16 07:04:01 storageqe-16.rhts.eng.bos.redhat.com abrt-notification[3649]: System encountered a non-fatal error in ??() Sep 16 07:04:04 storageqe-16.rhts.eng.bos.redhat.com abrt-notification[3670]: System encountered a non-fatal error in ??() Sep 16 07:04:05 storageqe-16.rhts.eng.bos.redhat.com abrt-notification[3691]: System encountered a non-fatal error in ??() Sep 16 07:04:08 storageqe-16.rhts.eng.bos.redhat.com abrt-notification[3713]: System encountered a non-fatal error in ??() Sep 16 07:04:09 storageqe-16.rhts.eng.bos.redhat.com kernel: ULP_STOP Sep 16 07:04:10 storageqe-16.rhts.eng.bos.redhat.com abrt-notification[3760]: System encountered a non-fatal error in ??()
Created attachment 1483681 [details] journal
Created attachment 1483682 [details] abrt dumps
This message is a reminder that Fedora 29 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '29'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 29 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.