Red Hat Bugzilla – Bug 603685
second kernel crash
Last modified: 2011-05-13 09:37:19 EDT
Created attachment 423792 [details]
in the last two day we've got a kernel crash under high load. we've got only photo of the screen...
is there an updated kernel for beta 6?
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release. Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release. This request is not yet committed for
*** Bug 603684 has been marked as a duplicate of this bug. ***
*** Bug 603687 has been marked as a duplicate of this bug. ***
The 'D' taint means you've previously encountered some other oops or BUG() so what you captured on the screen may not be the root cause of the problem.
looking in /var/log/messages, or dmesg, may yield the original problem. If not, attaching a serial console might gather more information.
this always happened after high load eg. build gcc in mock.
messages and dmesg doesn't contain anything.
how can i attach serial console and why i'll get more info?
i can reproduce this crash in a an hour. what can i do to give you more info?
(In reply to comment #7)
> i can reproduce this crash in a an hour. what can i do to give you more info?
Levente, please hook your system up to a serial console and capture the full panic. As Eric said, "D" taint indicates that a previous panic occurred which has likely scrolled off the screen.
can you tell me how can i capture through serial console?
which kind of serial cable to use (we've got all kind of) and how can i capture the full panic?
Created attachment 431241 [details]
sosreport for this machine
after we upgrade to beta2 we always got reboot (not crash) on this machine while try to rebuild glibc with:
mock -r rhel-6-i386 --define "rhel 6" --define ".el6 1" --define "dist .el6" --rebuild glibc-2.12-1.2.el6.src.rpm
Created attachment 431473 [details]
serial console how to
This issue has been proposed when we are only considering blocker
issues in the current Red Hat Enterprise Linux release. It has
been denied for the current Red Hat Enterprise Linux release.
** If you would still like this issue considered for the current
release, ask your support representative to file as a blocker on
your behalf. Otherwise ask that it be considered for the next
Red Hat Enterprise Linux release. **
the problem goes away with newer kernel updates.
this bug can be closed as 'current release'
could you close this bug?
Closing according to comment 13.