I upgraded an 8-STABLE box to r206119 and am now unable to boot
multi-user. I found that it hangs at line 58/59 of
/etc/rc.d/initrandom:
( ps -fauxww; sysctl -a; date; df -ib; dmesg; ps -fauxww ) \
| dd of=/dev/random bs=8k 2>/dev/null
when I run each of these commands by hand, I get only as far as
'sysctl -a', which seems to exit normally but leaves my keyboard
unresponsive (actually acting like I'm leaning on the <enter> key).
more digging reveals 'sysctl dev.uart' to be what triggers it.
this is the entirety of dev.uart from r204154:
dev.uart.0.%desc: 16550 or compatible
dev.uart.0.%driver: uart
dev.uart.0.%location: handle=\_SB_.PCI0.UAR1
dev.uart.0.%pnpinfo: _HID=PNP0501 _UID=1
dev.uart.0.%parent: acpi0
dev.uart.0.wake: 0
seems about the same from r206119.
I've attached boot output from r206119.
Any ideas? any other info I need to provide?
thanks much,
Jeff
whoops--either I didn't or it got tanked. sorry.
http://web.mr-happy.com/mlf/20100405-boot-r206119.txt
Jeff
> Hi,
>
> I upgraded an 8-STABLE box to r206119 and am now unable to boot
> multi-user. I found that it hangs at line 58/59 of
> /etc/rc.d/initrandom:
>
> ( ps -fauxww; sysctl -a; date; df -ib; dmesg; ps -fauxww ) \
> | dd of=/dev/random bs=8k 2>/dev/null
>
> when I run each of these commands by hand, I get only as far as
> 'sysctl -a', which seems to exit normally but leaves my keyboard
> unresponsive (actually acting like I'm leaning on the <enter> key).
> more digging reveals 'sysctl dev.uart' to be what triggers it.
kern/143040 looks similar.
--
Mikolaj Golub
Ah, you're right, it does. Could someone please take a look at that
PR then? Looks like it was submitted in January but hasn't been
assigned yet.
thanks,
Jeff