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 1665789 - There are "WARNING: CPU: 0 PID: 7 at kernel/hrtimer.c:1506 run_hrtimer_softirq+0x264/0x270" and "Call Trace" in rt kernel line
Summary: There are "WARNING: CPU: 0 PID: 7 at kernel/hrtimer.c:1506 run_hrtimer_softir...
Keywords:
Status: CLOSED DUPLICATE of bug 1665278
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: kernel-rt
Version: 7.7
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Kernel Drivers
QA Contact: Qiao Zhao
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-01-14 02:59 UTC by Pei Zhang
Modified: 2019-01-14 12:34 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-01-14 12:34:04 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Pei Zhang 2019-01-14 02:59:34 UTC 
Description of problem:
Install a rhel7.7 RT-host(guest), there are Call Trace in kernel line. 


Version-Release number of selected component (if applicable):
3.10.0-990.rt56.945.el7.x86_64


How reproducible:
2/2


Steps to Reproduce:
1. Install a rhel7.7 host(guest)

2. Setup rt host(guest). 

After step2, check # dmesg, there are "Call Trace" in kernel line:

[    9.577346] ------------[ cut here ]------------
[    9.577352] WARNING: CPU: 0 PID: 7 at kernel/hrtimer.c:1506 run_hrtimer_softirq+0x264/0x270
[    9.577362] Modules linked in: ip_tables xfs libcrc32c virtio_net virtio_blk crct10dif_pclmul crct10dif_common crc32c_intel ahci serio_raw libahci libata virtio_pci dm_mirror dm_region_hash dm_log dm_mod
[    9.577364] CPU: 0 PID: 7 Comm: ktimersoftd/0 Not tainted 3.10.0-990.rt56.945.el7.x86_64 #1
[    9.577365] Hardware name: Red Hat KVM, BIOS 1.11.0-2.el7 04/01/2014
[    9.577366] Call Trace:
[    9.577373]  [<ffffffff8fd5942f>] dump_stack+0x19/0x1b
[    9.577377]  [<ffffffff8f68784b>] __warn+0xfb/0x120
[    9.577380]  [<ffffffff8f68798d>] warn_slowpath_null+0x1d/0x20
[    9.577382]  [<ffffffff8f6b8dd4>] run_hrtimer_softirq+0x264/0x270
[    9.577386]  [<ffffffff8f691922>] do_current_softirqs+0x1e2/0x410
[    9.577388]  [<ffffffff8f691c10>] run_ksoftirqd+0x30/0x50
[    9.577391]  [<ffffffff8f6bda0f>] smpboot_thread_fn+0x20f/0x2e0
[    9.577393]  [<ffffffff8f6bd800>] ? lg_local_unlock+0x20/0x20
[    9.577395]  [<ffffffff8f6b4551>] kthread+0xd1/0xe0
[    9.577397]  [<ffffffff8f6b4480>] ? kthread_worker_fn+0x170/0x170
[    9.577401]  [<ffffffff8fd6af37>] ret_from_fork_nospec_begin+0x21/0x21
[    9.577403]  [<ffffffff8f6b4480>] ? kthread_worker_fn+0x170/0x170
[    9.577404] ---[ end trace 0000000000000002 ]---


Actual results:
There is "Call Trace" in RT-host and RT-guest kernel line.

Expected results:
There should be no "Call Trace" in RT-host and RT-guest kernel line.

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