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.

Bug 2218877

Summary: `dis -l` not working after executing `bt`
Product: Red Hat Enterprise Linux 8 Reporter: Íñigo Huguet <ihuguet>
Component: crashAssignee: lijiang
Status: CLOSED NOTABUG QA Contact: xiaoying yan <yiyan>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 8.9CC: dcaratti, jieli, jtornosm, lijiang, xiawu
Target Milestone: rcKeywords: Triaged
Target Release: ---Flags: pm-rhel: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-07-24 09:26:17 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:

Description Íñigo Huguet 2023-06-30 11:42:51 UTC 
Trying to debug a panic in the driver brcmfmac, it is not possible to see the source code of the driver after executing bt.

crash version: 7.3.2-8.el8   gdb version: 7.6

Reproducer:
$ crash /usr/lib/debug/lib/modules/4.18.0-499.el8.x86_64/vmlinux /var/crash/127.0.0.1-2023-06-28-07\:25\:40/vmcore
crash> mod -s brcmfmac
crash> bt
crash> dis -l brcmf_fw_complete_request  <--- line numbers of original sources not shown

It works well if not excecuting `bt`:
$ crash /usr/lib/debug/lib/modules/4.18.0-499.el8.x86_64/vmlinux /var/crash/127.0.0.1-2023-06-28-07\:25\:40/vmcore
crash> mod -s brcmfmac
crash> dis -l brcmf_fw_complete_request  <--- it shows the line numbers of original sources

Once I execute `bt` once, it doesn't work anymore.

This bug seems to be fixed in more recent vesions of crash and/or gdb. If I inspect the same kernel dump from a RHEL 9 system with crash version: 8.0.3-1.el9 and gdb version: 10.2, the problem doesn't happen.