Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
kernel: multipathd[7473]: segfault at 7f3c29fc587c ip 00007f3c2caeea9f sp 00007f3c2e479660 error 4 in libgcc_s-8-20190507.so.1[7f3c2cadf000+17000]
Version-Release number of selected component (if applicable):
RHEL-8.1.0-20190523.0
How reproducible:
once
Steps to Reproduce:
1.setup multipath
2.Loading scsi_debug module for simulation of mpath
3.Waiting for udev to create /dev/sdX
4./etc/multipath.conf updated
defaults {
#Enable multibus is for mutlbus testing
path_grouping_policy multibus
user_friendly_names yes
}
blacklist {
device {
vendor .*
product .*
}
}
blacklist_exceptions {
device {
vendor Linux
product scsi_debug
}
}
5.Restarting multiapth and reload configuration
6. for X in `seq 1 ${ROUNDS}`;do
service multipathd stop
multipath -F
service multipathd start
done
Found segfault of multipathd when multipathd shutdown test round 11
Actual results:
FAIL: Found segfault of multipathd
May 24 06:47:57 intel-chiefriver-01 kernel: multipathd[7473]: segfault at 7f3c29fc587c ip 00007f3c2caeea9f sp 00007f3c2e479660 error 4 in libgcc_s-8-20190507.so.1[7f3c2cadf000+17000]
Expected results:
No segfault
Additional info:
beaker job:https://beaker.engineering.redhat.com/recipes/6909956#task93420453
test log:http://beaker-archive.host.prod.eng.bos.redhat.com/beaker-logs/2019/05/35596/3559642/6909956/93420461/taskout.log
console log:http://beaker-archive.host.prod.eng.bos.redhat.com/beaker-logs/2019/05/35596/3559642/6909956/console.log
I have never been able to reproduce this. If you could reproduce it, and capture the core, or at least the backtrace, that would be really helpful. I believe that the crash backtrace should be available in the journalctl output.
Description of problem: kernel: multipathd[7473]: segfault at 7f3c29fc587c ip 00007f3c2caeea9f sp 00007f3c2e479660 error 4 in libgcc_s-8-20190507.so.1[7f3c2cadf000+17000] Version-Release number of selected component (if applicable): RHEL-8.1.0-20190523.0 How reproducible: once Steps to Reproduce: 1.setup multipath 2.Loading scsi_debug module for simulation of mpath 3.Waiting for udev to create /dev/sdX 4./etc/multipath.conf updated defaults { #Enable multibus is for mutlbus testing path_grouping_policy multibus user_friendly_names yes } blacklist { device { vendor .* product .* } } blacklist_exceptions { device { vendor Linux product scsi_debug } } 5.Restarting multiapth and reload configuration 6. for X in `seq 1 ${ROUNDS}`;do service multipathd stop multipath -F service multipathd start done Found segfault of multipathd when multipathd shutdown test round 11 Actual results: FAIL: Found segfault of multipathd May 24 06:47:57 intel-chiefriver-01 kernel: multipathd[7473]: segfault at 7f3c29fc587c ip 00007f3c2caeea9f sp 00007f3c2e479660 error 4 in libgcc_s-8-20190507.so.1[7f3c2cadf000+17000] Expected results: No segfault Additional info: beaker job:https://beaker.engineering.redhat.com/recipes/6909956#task93420453 test log:http://beaker-archive.host.prod.eng.bos.redhat.com/beaker-logs/2019/05/35596/3559642/6909956/93420461/taskout.log console log:http://beaker-archive.host.prod.eng.bos.redhat.com/beaker-logs/2019/05/35596/3559642/6909956/console.log