Re: need help with rawhide anaconda problem

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 05/08/2014 07:54 AM, Gene Czarcinski wrote:
I recently completed an update for grubby.c so that it can now handle /btrfs on a btrfs subvol:
https://bugzilla.redhat.com/show_bug.cgi?id=1094489

To test this updated grubby, I have patched anaconda 20.25.15-1 (Fedora 20) and 21.35-1 (Fedora 21 rawhide) to re-enable btrfs in stage2_device_types for grub2. I then created an updates.img as well as updated anaconda RPMs with the grubby and anaconda RPMs in a local repository. For Fedora 20 I also rebuilt grub2-2.02 RPMs and they are in the local prepository also [this version of grub2 is needed to correctly support booting a btrfs subvol].

I use the respective updates.img files as updates when booting the Fedora 20 DVD or the boot.iso from rawhide.

Lets keep things simple and do a GUI install of LXDE on a qemu-kvm virtual system with 1 processor, 2GB memory and 8GB virtio disk.

With a Fedora 20 install (which includes updates and points to the local repository), everything works as expected.

With the Fedora rawhide install [either using boot.iso + updates.img or a rebuild/updates distribution DVD iso or a liveinstall from an updated livecd-LXDE iso redon an a USB stick) things do finally work OK but there are a couple of "pauses" that do not make sense.

These pauses occur when entering and leaving custom partitioning. A grey panel is displayed but nothing is happening. There is some vcpu usage but not much. An I can switch to the other virtual terminals including CNTL-ALT-F2 where I can execute commands. I see nothing on the other virtual terminals that indicates a problem. I also see nothing in the host system's /var/log/messages. After a long, long time things start working again.

BTW, does anyone know what to magic dance you need to do so that specifying inst.debug=1 on the kernel cmdline will result in a debug button on anaconda's panel?
I believe I have found the problem but not how to fix it.

On the rawhide install in the program.log, I am seeing lots and lots of "udevadm settle --timeout=300" messages. There are groups of them from 3 to 7/8 between other messages that indicate something positive being done.

I see few of these on a corresponding Fedora 20 install and those are followed by a DEBUG message saying rc=0.

Suggestions?

Gene

_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/anaconda-devel-list




[Index of Archives]     [Kickstart]     [Fedora Users]     [Fedora Legacy List]     [Fedora Maintainers]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]
  Powered by Linux