Bug 1618985 - abrt happens when try to bring down the physical NICs which have fcoe instance created
Summary: abrt happens when try to bring down the physical NICs which have fcoe instanc...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: fcoe-utils
Version: 29
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Chris Leech
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-08-19 09:09 UTC by lnie
Modified: 2018-08-19 09:58 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2018-08-19 09:58:41 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
abrt dump1 (8.48 KB, application/x-gzip)
2018-08-19 09:09 UTC, lnie
no flags Details
abrt dump2 (8.69 KB, application/x-gzip)
2018-08-19 09:11 UTC, lnie
no flags Details
journal (209.31 KB, text/plain)
2018-08-19 09:11 UTC, lnie
no flags Details

Description lnie 2018-08-19 09:09:59 UTC
Created attachment 1476868 [details]
abrt dump1

Description of problem:
Create fcoe instance on ens2f0 and ens2f1,and run "ifconfig ens2f0/ens2f1 down",
you will see two abrt-notification in the journal

[root@storageqe-13 ~]# journalctl -p 3 | tail
Aug 19 04:44:00 storageqe-13.rhts.eng.bos.redhat.com kernel: in_atomic(): 1, irqs_disabled(): 0, pid: 15311, name: ifconfig
Aug 19 04:44:01 storageqe-13.rhts.eng.bos.redhat.com kernel: BUG: sleeping function called from invalid context at kernel/locking/mutex.c:748
Aug 19 04:44:01 storageqe-13.rhts.eng.bos.redhat.com kernel: in_atomic(): 1, irqs_disabled(): 0, pid: 15311, name: ifconfig
Aug 19 04:44:02 storageqe-13.rhts.eng.bos.redhat.com abrt-notification[15352]: System encountered a non-fatal error in ??()
Aug 19 04:44:03 storageqe-13.rhts.eng.bos.redhat.com abrt-notification[15371]: System encountered a non-fatal error in ??()
Aug 19 04:44:27 storageqe-13.rhts.eng.bos.redhat.com kernel: BUG: sleeping function called from invalid context at kernel/locking/mutex.c:748
Aug 19 04:44:27 storageqe-13.rhts.eng.bos.redhat.com kernel: in_atomic(): 1, irqs_disabled(): 0, pid: 14905, name: kworker/1:5
Aug 19 04:44:29 storageqe-13.rhts.eng.bos.redhat.com abrt-notification[15460]: System encountered a non-fatal error in ??()
Aug 19 04:44:50 storageqe-13.rhts.eng.bos.redhat.com kernel:  rport-5:0-7: blocked FC remote port time out: removing rport
Aug 19 04:45:39 storageqe-13.rhts.eng.bos.redhat.com kernel:  rport-6:0-7: blocked FC remote port time out: removing rport


[root@storageqe-13 ~]# fcoeadm -i
    Description:      82599ES 10-Gigabit SFI/SFP+ Network Connection
    Revision:         01
    Manufacturer:     Intel Corporation
    Serial Number:    001B21591234

    Driver:           ixgbe 5.1.0-k
    Number of Ports:  1

        Symbolic Name:     fcoe v0.1 over ens2f1.802-fcoe
        OS Device Name:    host6
        Node Name:         0x1000001b21591237
        Port Name:         0x2000001b21591237
        Fabric Name:        0x2322000573b27f01
        Speed:             10 Gbit
        Supported Speed:   1 Gbit, 10 Gbit
        MaxFrameSize:      2112 bytes
        FC-ID (Port ID):   0x750004
        State:             Online
    Description:      82599ES 10-Gigabit SFI/SFP+ Network Connection
    Revision:         01
    Manufacturer:     Intel Corporation
    Serial Number:    001B21591234

    Driver:           ixgbe 5.1.0-k
    Number of Ports:  1

        Symbolic Name:     fcoe v0.1 over ens2f0.802-fcoe
        OS Device Name:    host5
        Node Name:         0x1000001b21591236
        Port Name:         0x2000001b21591236
        Fabric Name:        0x2322000573b27f01
        Speed:             10 Gbit
        Supported Speed:   1 Gbit, 10 Gbit
        MaxFrameSize:      2112 bytes
        FC-ID (Port ID):   0x750005
        State:             Online


Version-Release number of selected component (if applicable):
kernel-4.18.0-0.rc8.git2.1.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:

Comment 1 lnie 2018-08-19 09:11:36 UTC
Created attachment 1476869 [details]
abrt dump2

Comment 2 lnie 2018-08-19 09:11:58 UTC
Created attachment 1476870 [details]
journal

Comment 3 lnie 2018-08-19 09:58:41 UTC
Didn't see this crash any more after upgrade to kernel-4.18.1-300.fc29.x86_64,closing


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