Hi Adam, On Sun, 10 Jun 2012 22:39:38 -0700 Adam Williamson wrote: > On Sat, 2012-06-09 at 16:11 +0200, Martin Sourada wrote: > > I used preupgrade for the first time and had a similar experience, > > but nothing one cannot fix... > > > > 1. Prepared the preupgrade process (f16->f17) > > 2. reboot and start upgrade > > 3. upgrade gets stuck on some package (IIRC it was something lisp > > related). No CPU or HDD usage for about half an hour > > 4. got impatient, do a hard reboot start upgrade again > > Don't do this, if you can possibly avoid it. It's never a good idea to > abort an upgrade and restart it (it results in the other weirdness you > hit later). When anaconda is running, a console is available on tty2; > you can fiddle about with processes there to try and unstuck I tried, but unfortunately it didn't occur to me that the package post-install script got hung up so I just jumped to conclusion that it was anaconda that hung up (both CPU, according to top, and HDD were idling, I didn't see anything suspicious in the messages printed on tty's and dmesg)... > whatever's stuck. That sounds somewhat like > https://bugzilla.redhat.com/show_bug.cgi?id=822008 ; there's a fix in > for that bug, but it only got pushed to stable in the last day or so. yeah, I discovered this bug after I sent the previous mail and it's exactly the one I hit... Thanks, Martin -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
