Bug 612271

Summary: Kernel Freeze at Probing edd
Product: [Fedora] Fedora Reporter: Frank Murphy <frankly3d>
Component: kernelAssignee: Justin M. Forbes <jforbes>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: rawhideCC: anton, dougsland, gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-07-18 12:08:49 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Frank Murphy 2010-07-07 18:01:02 UTC
Description of problem: Doesn't boot


It Won't boot, virt-manager guest 32bit rawhide.
stops at checking for edd
has to be forcibly stopped.
No logs whatsoever.
It boots from  F13 kernel's.

virt-man shows no disk, net activity,
cpu almost flatline.


Version-Release number of selected component (if applicable):
kernel-2.6.35-0.24.rc3.git7.fc14
kernel-2.6.35-0.25.rc4.git0.fc14
kernel-2.6.35-0.27.rc4.git0.fc14   


How reproducible:
Always


Steps to Reproduce:
1. Boot
2.
3.
  



Expected results: Normal boot

Additional info: There is someone else thinks it may be related to:
https://bugzilla.redhat.com/show_bug.cgi?id=575417
But I cannot confirm this.

Comment 1 Frank Murphy 2010-07-08 07:44:55 UTC
http://koji.fedoraproject.org/koji/buildinfo?buildID=182181
kernel-2.6.35-0.29.rc4.git0.fc14.i686.rpm as others

perf-2.6.35-0.29.rc4.git0.fc14.i686.rpm  won't install

Comment 2 Frank Murphy 2010-07-09 09:01:17 UTC
http://koji.fedoraproject.org/koji/buildinfo?buildID=182648
kernel-2.6.35-0.31.rc4.git4.fc14.i686.rpm as above
perf.i686 installed after yum erase perf.noarch

Have tries a lot of the usual kernel parametres at grub, no success.

noacpi
noapic
nomsi
ignore_loglevel
debug
initcall_debug
lapic
bios
nobios
bootmem_debug
iommu=*
edd=on\off
debug_objects

Comment 3 Frank Murphy 2010-07-12 15:43:42 UTC
Working back through the kernels this seems to have started with the move to 2.6.35*

This is what virsh picks up from the host in case any use:
$ sudo virsh capabilities
[sudo] password for frank: 
<capabilities>

  <host>
    <cpu>
      <arch>x86_64</arch>
      <model>pentium3</model>
      <topology sockets='1' cores='4' threads='1'/>
      <feature name='lahf_lm'/>
      <feature name='lm'/>
      <feature name='syscall'/>
      <feature name='xtpr'/>
      <feature name='cx16'/>
      <feature name='ssse3'/>
      <feature name='tm2'/>
      <feature name='est'/>
      <feature name='vmx'/>
      <feature name='ds_cpl'/>
      <feature name='monitor'/>
      <feature name='pni'/>
      <feature name='pbe'/>
      <feature name='tm'/>
      <feature name='ht'/>
      <feature name='ss'/>
      <feature name='sse2'/>
      <feature name='acpi'/>
      <feature name='ds'/>
      <feature name='clflush'/>
      <feature name='apic'/>
    </cpu>
--snip--

Comment 4 Chuck Ebbert 2010-07-14 06:57:37 UTC
What kernel is the host running?

Comment 5 Frank Murphy 2010-07-14 07:18:58 UTC
kernel-2.6.33.6-147.fc13.x86_64

Comment 6 Frank Murphy 2010-07-14 08:08:04 UTC
(In reply to comment #5)
> kernel-2.6.33.6-147.fc13.x86_64    

Also tested with:
http://koji.fedoraproject.org/koji/buildinfo?buildID=183346
kernel-2.6.34.1-11.fc13.x86_64.rpm

Comment 7 Frank Murphy 2010-07-16 15:57:13 UTC
Ok, I may have tracked this down to python-virtinst ref:
https://bugzilla.redhat.com/show_bug.cgi?id=611584

I have now sucessfully booted  a 2-6.35* kernel on a newly installed Rawhide.x86_64

So will over the weekend reinstall Rawhide.x86 and report back.

Comment 8 Frank Murphy 2010-07-18 12:08:49 UTC
(In reply to comment #7)
> Ok, I may have tracked this down to python-virtinst ref:
> https://bugzilla.redhat.com/show_bug.cgi?id=611584
> 
> I have now sucessfully booted  a 2-6.35* kernel on a newly installed
> Rawhide.x86_64
> 
> So will over the weekend reinstall Rawhide.x86 and report back.    


Yes, the rawhide boots now it was purely a python-virtinst issue.

Apologies for any noise.