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 815865 - system crashes without any reason. No specific function was selected
Summary: system crashes without any reason. No specific function was selected
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: kernel
Version: 6.3
Hardware: i386
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Prarit Bhargava
QA Contact: Red Hat Kernel QE team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-04-24 17:06 UTC by Eduardo Pereira
Modified: 2013-11-12 14:16 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-11-12 14:16:16 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
SOSREPORT output (3.50 MB, application/x-xz)
2012-04-25 12:39 UTC, Eduardo Pereira 		no flags Details
View All

Description Eduardo Pereira 2012-04-24 17:06:13 UTC 
User-Agent:       Mozilla/5.0 (X11; Linux x86_64; rv:10.0.3) Gecko/20120305 Firefox/10.0.3

Machine was idle at the time of the crash. 

Reproducible: Didn't try
Comment 2 Eduardo Pereira 2012-04-25 12:21:51 UTC 
I have run SOSREPORT but I am not able to attach its output to the bug report. Is there another way to send this file aside from the attachment box on the report?
Comment 3 Eduardo Pereira 2012-04-25 12:39:52 UTC 
Created attachment 580156 [details]
SOSREPORT output
Comment 4 Eduardo Pereira 2012-04-25 12:40:51 UTC 
SOSREPORT submitted.
Comment 5 Prarit Bhargava 2012-04-27 11:47:40 UTC 
Any messages on the console log?

P.
Comment 6 Eduardo Pereira 2012-04-27 13:28:00 UTC 
The system types a lot of messages, filing the whole screen. But because the only way out of this situation is a power recycle, only a photo of the screen would document the exact messages. I thought the same output would be kept in some of the internal areas of the system and shipped with the SOSREPORT I sent to you. A smart operating system would do that.
Comment 7 Prarit Bhargava 2012-04-30 13:00:50 UTC 
(In reply to comment #6)
> The system types a lot of messages, filing the whole screen. But because the
> only way out of this situation is a power recycle, only a photo of the screen
> would document the exact messages. I thought the same output would be kept in
> some of the internal areas of the system and shipped with the SOSREPORT I sent
> to you. A smart operating system would do that.

I guess Linux isn't a smart operating system.  Please take a pic and post it OR configure your system with kdump to capture a system dump on panic.

P.
Comment 8 Eduardo Pereira 2012-04-30 14:21:46 UTC 
I will follow your suggestion about kdump. But I will have to wait for a new crash, to get the full documentation.
Comment 9 RHEL Program Management 2012-05-04 04:07:39 UTC 
Since RHEL 6.3 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.

Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.
Comment 10 Prarit Bhargava 2012-05-14 13:31:31 UTC 
Hi Eduardo, just checking in to see if you had any luck in reproducing while kdump was on.

Thanks,

P.
Comment 11 Eduardo Pereira 2012-05-16 13:15:52 UTC 
Thanks for asking. But the problem has not shown up again.  I am also a little concerned that setting kdump would increase cycle time and slow down the overall system.
Comment 12 Prarit Bhargava 2012-05-16 13:37:52 UTC 
(In reply to comment #11)
> Thanks for asking. But the problem has not shown up again.  I am also a little
> concerned that setting kdump would increase cycle time and slow down the
> overall system.

I'm not sure what you mean.  kdump doesn't "slow down" a system.  It's something that executes during a panic.

P.
Comment 14 Prarit Bhargava 2013-11-12 14:16:16 UTC 
No further reports on this.  CLOSING.

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