Bug 2185510

Summary:	The "bt pid" does not print enough stack trace
Product:	Red Hat Enterprise Linux 9	Reporter:	lijiang
Component:	crash	Assignee:	lijiang
Status:	CLOSED MIGRATED	QA Contact:	xiaoying yan <yiyan>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	9.2	CC:	crwood, denli, jieli, ruyang
Target Milestone:	rc	Keywords:	MigratedToJIRA, 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-09-25 18:56:44 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 lijiang 2023-04-10 04:53:16 UTC

Description of problem:

> Hi, Crystal 
> 
> > logged in today), so you'll get the short version.  The crash tool is for
> > some reason having trouble dealing with a retpoline in __wake_up_common(). 
> > Someone should look into that.
> > 
> Could you please point out what problems the crash tool encountered? I would
> like to have a look and check if this can be improved in crash-utility, or
> may provide some helpful debug information for you.

With the vmcore in http://registry.kni-qe-0.lab.eng.rdu2.redhat.com:8080/images/bz2175676/127.0.0.1-2023-03-08-15:12:25/
I get this:

crash> bt 493113
PID: 493113   TASK: ff2e34ecbd3ca2c0  CPU: 27   COMMAND: "sriov_fec_daemo"
 #0 [ff77abc4e81cfb08] __schedule at ffffffff81b239cb
 #1 [ff77abc4e81cfb70] schedule at ffffffff81b23e2d
 #2 [ff77abc4e81cfb88] schedule_timeout at ffffffff81b2c9e8
    RIP: 000000000047cdbb  RSP: 000000c0000975a8  RFLAGS: 00000216
    RAX: ffffffffffffffda  RBX: 000000c00004e000  RCX: 000000000047cdbb
    RDX: 000000000000000c  RSI: 000000c000097798  RDI: 0000000000000009
    RBP: 000000c0000975f8   R8: 0000000000000001   R9: 000000c00098d680
    R10: 000000000000000c  R11: 0000000000000216  R12: 000000c000097688
    R13: 0000000000000000  R14: 000000c0006c3520  R15: 00007f5e359946b7
    ORIG_RAX: 0000000000000001  CS: 0033  SS: 002b
crash> 

The stack trace should go on well beyond that.  And yes, I still see it when building crash from upstream git.

The current issue was encountered/reported by Crystal.

(see bz2175676, comment#17 and comment#30).

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:
The "bt pid" should print a full backtrace.

Additional info:

Comment 1 RHEL Program Management 2023-09-25 17:50:21 UTC

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.

Comment 2 RHEL Program Management 2023-09-25 18:56:44 UTC

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.