Description of problem: See bug 1154518 for more details. This problem prevents 'grub2-mkconfig' from finishing, and happened between 18.0.0.rc0.git6.1 and 18.0.0.rc0.git9.1, and is still present in 18.0.0.rc1.git0 Version-Release number of selected component (if applicable): 18.0.0.rc0.git9.1 through 18.0.0.rc1.git0 How reproducible: Every time Steps to Reproduce: 1. Run the os-prober script 2. 3. Actual results: Never finishes (Needs a 'pkill -hup os-prober' to finish with cleanup.) Expected results: Listing of bootable operating systems on the computer. Additional info: This problem (or something else) also keeps google-chrome from starting, if you have installed it.
I can't recreate this on my rawhide system with 3.18.0-0.rc1.git1.1.fc22. When I run os-prober, it exits silently and does not hang. Would it be possible for you to strace the run of os-prober to see where it's hanging? Also, it might be beneficial to use sysrq-t to get a backtrace of all current process on the machine. Please attach the output for those as a plain text file.
Created attachment 949600 [details] strace output Attached is a compressed tar of the output of a 'strace -Dt -o os_prober -ff os-prober' command. (It's in compressed, directory format because that command created 499 files.) I could find no command 'sysrq-t' (or 'sysr*') for listing running processes. In lieu thereof, I have included in the archive, files 'os-prober.{before,during,after}' of the output of a 'pstree -ap'. Looking at that output suggests (to me, at least) that the os-prober program might be hanging trying to find an os on a btrfs drive (formatted by btrfs, not the partition manager) with which I've been playing. (There is no OS on it.) I tried unmounting that drive, but os-prober "helpfully" mounts any unmounted drive attached to the system. On the other hand, I can't believe that a btrfs problem would preven google-chrome from executing. (With no error messages.) P.S.: This is with the 18.0 rc1.2 kernel.
Please try the 3.18.0-0.rc2.git1.1 kernel that is current building. There was an upstream RCU issue that was causing hangs for a number of people.
I just ran a 'yum update' on my "rawhide" system that installed 3.18.0-0.rc2.git0.1, which still exhibits the problem. If your reference to git1.1 (nsted of git0.1) is correct, I'll have to wait 'till that kernel hits the 'rawhide' repo. On the other hand, if your reference to git1.1 was a typo, then there's no joy with git0.1. . .
(In reply to Peter Trenholme from comment #4) > I just ran a 'yum update' on my "rawhide" system that installed > 3.18.0-0.rc2.git0.1, which still exhibits the problem. > > If your reference to git1.1 (nsted of git0.1) is correct, I'll have to wait > 'till that kernel hits the 'rawhide' repo. > > On the other hand, if your reference to git1.1 was a typo, then there's no > joy with git0.1. . . 3.18.0-0.rc2.git1.1 was not a typo. Please let me know when you test that.
O.K.: Today's update installed rc2.git1.1, and both os-prober and google-chrome now work. (There are other, new, problems: reboot and shutdown both hang, and GUI login does not display. Those are, however, probably just "rawhide" stuff, not related to this, and - hopefully - common enough to not need a bug report.) Anyhow, I marked this "closed, upstream" Thanks.