Bug 586823 - kernel panic during initial package installation
Summary: kernel panic during initial package installation
Status: CLOSED DUPLICATE of bug 574570
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: kernel   
(Show other bugs)
Version: 6.0
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Prarit Bhargava
QA Contact: Red Hat Kernel QE team
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-04-28 12:40 UTC by Matthias Schroder
Modified: 2010-05-03 18:16 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-05-03 18:16:06 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
screen shot of traceback (705.39 KB, image/jpeg)
2010-04-28 20:55 UTC, Matthias Schroder
no flags Details
log from serial console (31.97 KB, text/x-log)
2010-05-03 15:29 UTC, Matthias Schroder
no flags Details

Description Matthias Schroder 2010-04-28 12:40:50 UTC
Description of problem: kernel panic during initial package installation


Version-Release number of selected component (if applicable): 2.6.32-19.el6.x86_64


How reproducible: 100%


Steps to Reproduce:
1. Try to install
2.
3.
  
Actual results: panic


Expected results: installed RH6beta


Additional info: I use a kickstart file with a somewhat complex kickstart file, allowing me to boot several different OSes. That works if I install the i386 version, but fails when I try to install x86_64.

Comment 2 RHEL Product and Program Management 2010-04-28 14:28:57 UTC
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
inclusion.

Comment 3 Bill Nottingham 2010-04-28 15:43:10 UTC
What was the panic?

Comment 4 Matthias Schroder 2010-04-28 20:55:39 UTC
Created attachment 409965 [details]
screen shot of traceback

I don't know how to 'classify' the panic, but I have a screenshot of the trace. Unfortunately I did not have a tripod for my phone, so the quality is not the best. But it should be sufficient.

Comment 5 Prarit Bhargava 2010-04-30 14:23:11 UTC
Matthias,  unfortunately the beginning of the panic is not on the screen.  Is there any chance you could hook this system up to another system via a serial connection?

P.

Comment 6 Matthias Schroder 2010-04-30 15:45:50 UTC
Hi Prarit,

yes, that can be done. But I have no idea how to do the necessary configuration, can you point me to some documentation?

Matthias

Comment 7 Prarit Bhargava 2010-05-03 14:25:35 UTC
Hi Matthias

Here you go:

https://nmi.cs.wisc.edu/node/878

P.

Comment 8 Matthias Schroder 2010-05-03 15:29:24 UTC
Created attachment 411037 [details]
log from serial console

Hi Prarit,

the log from the serial console is attached. I was struggling because the PC next to the one in question has a non-working serial port :(

I hope the log is helpful.

Cheers,

Matthias

Comment 9 Prarit Bhargava 2010-05-03 18:16:06 UTC
Hi Matthias,

The log was useful -- thank you for providing it.  When reporting a panic or an oops, it is *very* useful for you to supply us with a console log.  It makes debugging a lot easier :)

The good news is that your problem has already been fixed by another engineer in BZ 574570.  A work-around for your issue is to install and boot with "nmi_watchdog=0" as a kernel option.

Also, if you can boot the system (and I know in this particular instance you were unable too) supplying a 'sosreport' (type sosreport on the command line) for the system is also useful.  It provides us with a lot of information about your system and we use it to determine what could be broken.

Thanks again,

P.

*** This bug has been marked as a duplicate of bug 574570 ***


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