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 1084467 - ABRT does not inform user about uselessness of full '?' kernel oopses
Summary: ABRT does not inform user about uselessness of full '?' kernel oopses
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: abrt
Version: 6.5
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: ---
Assignee: Jakub Filak
QA Contact: BaseOS QE - Apps
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-04-04 12:17 UTC by Alexander Todorov
Modified: 2016-12-01 00:46 UTC (History)
5 users (show)

Fixed In Version: abrt-2.0.8-25.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-10-14 08:05:36 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
/var/spool/abrt (9.36 MB, application/x-gzip)
2014-04-07 12:00 UTC, Alexander Todorov
no flags Details
~/.abrt/spool (18.55 MB, application/x-gzip)
2014-04-07 14:00 UTC, Alexander Todorov
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1022181 1 None None None 2021-01-20 06:05:38 UTC
Red Hat Product Errata RHBA-2014:1572 0 normal SHIPPED_LIVE abrt bug fix and enhancement update 2014-10-14 01:27:32 UTC

Internal Links: 1022181

Description Alexander Todorov 2014-04-04 12:17:41 UTC
Description of problem:

For some reason my computer crashed (see bug #1084465 which I filed manually). When I rebooted ABRT reported lots of crashes detected so I went ahead to report the first one (the one at the bottom). ABRT says:

--- Running report_Bugzilla ---
Essential element 'global_uuid' is missing, can't continue
(exited with 1)


Version-Release number of selected component (if applicable):
abrt-2.0.8-21.el6.x86_64



I have no idea what is wrong and how to even try to fix it.

Comment 1 Jakub Filak 2014-04-04 12:32:09 UTC
Could you please attach the entire dump directory? It should be located in /var/spool/abrt/ directory. Also, please provide me with the output of the following command:

$ grep abrt /var/log/messages

Comment 2 Alexander Todorov 2014-04-07 12:00:45 UTC
Created attachment 883595 [details]
/var/spool/abrt

Comment 3 Alexander Todorov 2014-04-07 12:01:59 UTC
(In reply to Jakub Filak from comment #1)
> Also, please provide me with the output of the
> following command:
> 
> $ grep abrt /var/log/messages

Nothing found with this command.

Comment 4 Jakub Filak 2014-04-07 13:32:49 UTC
(In reply to Alexander Todorov from comment #3)
Thank you! Could you also please attach '~/.abrt/spool' directory?

Comment 5 Alexander Todorov 2014-04-07 14:00:51 UTC
Created attachment 883628 [details]
~/.abrt/spool

coredump files removed b/c they take a lot of space

Comment 6 Jakub Filak 2014-04-07 15:09:57 UTC
ABRT prevented you from reporting the oops because the oops' backtrace consists only from frames prefix with '?' symbol. Such frames are considered as unreliable ,and therefore, in your case, the entire backtrace is considered as not-good-enough to be reported into Bugzilla.

There is room for improvement such that ABRT should provide you with an explanation similar to the above.

Comment 7 Alexander Todorov 2014-04-08 11:13:58 UTC
Hi Jakub,
is there any way to fix this ? e.g. install the corresponding -debuginfo packages and regenerate the info? (how can I do that)

Comment 8 Jakub Filak 2014-04-08 11:26:54 UTC
I am sorry, but this is unfixable. A kernel oops is generated by kernel which writes the backtrace to a log file. ABRT just makes a copy of the oops data written to the log file.

Comment 9 Jakub Filak 2014-06-27 13:13:47 UTC
Upstream commit a47c36be2a32a95357cbd9668c4db8f5b26dfdae fixes this issue.

Comment 12 errata-xmlrpc 2014-10-14 08:05:36 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2014-1572.html


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