I wrote:
> About 6 minutes after booting (on two occasions; I don't
> guarantee that this doesn't vary), a process that appears
> in the output of "ps" as "[swi4: clock sio]" begins to
> use about 3/4 of the machine's CPU. I think it does so
> more or less instantaneously. It continues to do so
>
> Can I suggest that if you get no replies on questions@ that you try
> hackers@ (you may need to subscribe to post, not sure).
>
> What's going on here is not normal so even someone with tons of FreeBSD
> experience may never have seen something like this. I know I never
> have. Most posters
I wrote:
> About 6 minutes after booting (on two occasions; I don't
> guarantee that this doesn't vary), a process that appears
> in the output of "ps" as "[swi4: clock sio]" begins to
> use about 3/4 of the machine's CPU. I think it does so
> more or less instantaneously. It continues to do so
> i
I wrote, inter alia,
> About 6 minutes after booting (on two occasions; I don't
> guarantee that this doesn't vary), a process that appears
> in the output of "ps" as "[swi4: clock sio]" begins to
> use about 3/4 of the machine's CPU. I think it does so
> more or less instantaneously. It continues
ying to mount root from ufs:/dev/ad0s1a
-- dmesg output ends --
I would be grateful for any insight into what's going wrong and how
(if at all) it can be fixed or worked around. I'm not subscribed to
-questions or to -stable, so would prefer to be cc'ed, but I&#
the Wrong Thing.
(Well, actually, I just tried the latter, and it worked.
To get ethereal to actually install, it was also necessary
to work around a bit of breakage in the version of "sed"
I have, which has presumably been repaired in more recent
4.x releases. Anyw
