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:
ABRT kernel oops is missing Trace in case 00449575
Attched the crash report.
Version-Release number of selected component (if applicable):
abrt version: 1.1.13
architecture: x86_64
cmdline: not_applicable
component: kernel
executable: kernel
kernel: 2.6.32-71.el6.x86_64
package: kernel
reason: WARNING: at net/sched/sch_generic.c:261 dev_watchdog+0x26d/0x280() (Not tainted)
release: Red Hat Enterprise Linux Server release 6.0 (Santiago)
time: 1290298892
uid: 0
How reproducible:
Random
Actual results:
Trace is not included
Expected results:
trace should be included
Additional info:
I am waiting for sosreport from client to get details on this crash.
Size of attached file to the case is 997bytes. Attaching that file with this case. This is different for bug 696166. In bug 696166, c/cpp crash files were not attached at all. In this kernel case, attachment file is small and does not have call trace.
Yogesh, the file you attached indeed contains the following in "backtrace" element:
BUG: soft lockup - CPU#1 stuck for 105s! [nautilus:32765]
Modules linked in: nf_conntrack_ipv4 nf_defrag_ipv4 iptable_filter ip_tables autofs4 vsock(U) vmci(U) vmmemctl(U) pvscsi(U) sunrpc ipt_REJECT ip6t_REJECT nf_conntrack_ipv6 xt_state nf_conntrack ip6table_filter ip6_tables ipv6 dm_mirror dm_region_hash dm_log uinput ppdev parport_pc parport vmware_balloon sg pcnet32 vmxnet(U) mii i2c_piix4 i2c_core ext4 mbcache jbd2 sd_mod crc_t10dif sr_mod cdrom mptspi mptscsih mptbase scsi_transport_spi pata_acpi ata_generic ata_piix dm_mod [last unloaded: nf_defrag_ipv4]
Pid: 32765, comm: nautilus Not tainted (2.6.32-71.18.2.el6.i686 #1) VMware Virtual Platform
EIP: 0073:[<008d144b>] EFLAGS: 00210202 CPU: 1
EIP is at 0x8d144b
EAX: 08cb1e58 EBX: 00971328 ECX: 00000000 EDX: 00000001
ESI: 088d2060 EDI: 088d2058 EBP: bfce7c98 ESP: bfce7c30
DS: 007b ES: 007b FS: 0000 GS: 0033 SS: 007b
CR0: 80050033 CR2: b7829000 CR3: 32686000 CR4: 000006f0
DR0: 00000000 DR1: 00000000 DR2: 00000000 DR3: 00000000
DR6: ffff0ff0 DR7: 00000400
Call Trace:
That is, no backtrace per se.
In order to diagnose this, I need to take a look at /var/log/messages. I guess this file is included in sosreport. So please, if you will succeed in retrieving sosreport for this or similar case, please attach it to this bug.