(Archived thread, came across through Google, couldn't find a link to request mods to un-archive, so I'm posting a new thread)
I'm having a very similar problem after installing F15 on my EeePC 701.
It's a "spare" computer I thought I could play with systemd on. Previously it was running an old version of Ubuntu, so it's not a straightforward regression. Otoh, I've seen something similar before with older kernels on the same hardware. So my first guess is that it's down to the new kernel.
I'm going to keep playing with this on my own. I've already tried "noapic" and "noapic nolapic". I guess the next step is to try an F14 kernel or approximation thereof.
---------- Post added at 10:58 AM ---------- Previous post was at 10:08 AM ----------
Right! FC14 and FC13 kernels still hang. But the FC13 shows a softlockup message. The hung process is biosdevname. So I disabled that, and the hang seems to be gone.
# chmod -x /sbin/biosdevname
So if it's a regression, its probably due to biosdevname. (Related to the persistent network interface names in F15?). And the next step is to try and reproduce the softlockup message on something closer to a stock F15 kernel.
---------- Post added at 01:39 PM ---------- Previous post was at 10:58 AM ----------
...and it's already been reported. I added my findings (including call trace) as a comment on the existing bug -