Hide Forgot
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.
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.
What was the panic?
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.
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.
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
Hi Matthias Here you go: https://nmi.cs.wisc.edu/node/878 P.
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
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 ***