Mailinglist Archive: opensuse-factory (509 mails)
| < Previous | Next > |
[opensuse-factory] Re: Changes with boot/init for 10.3 ? Kernel locks in 10.3, not in 10.2 ?
- From: Warren Stockton <wns@xxxxxxxxxxx>
- Date: Wed, 15 Aug 2007 00:23:05 -0600
- Message-id: <200708150023.06129.wns@xxxxxxxxxxx>
On Tuesday 14 August 2007 23:43:15 Kevin Valko wrote:
> Strange issue, but I've been running into problems with 10.3 since updating
> to beta 1 from 10.2.
>
> I suspect, but am not sure, that my issues are somehow related to the new
> modular mkinit process, it's more or less the only difference I can find in
> my boot logs as compared to 10.2. The lockups occur almost immediately
> after all the various xxx.sh scripts start running, but not always at the
> same point (which makes it harder to figure out where the problem is).
Try setting "PROMPT_FOR_CONFIRM=yes" in /etc/sysconfig/boot. You might want
to set CONFIRM_PROMPT_TIMEOUT to something longer than 5 seconds for the
first couple of boots.
I had similar problems on a HP dv6400 with some of the 10.3alpha kernels. In
my case it turned out to be /etc/init.d/boot.clock and I could lock the
system at will by running hwclock --systohc or hwclock --hctosys
(I don't have the problem on the current 10.3beta1 kernel and could never
quite nail down the root cause when I was seeing the problem on earlier
kernels.)
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-factory+help@xxxxxxxxxxxx
> Strange issue, but I've been running into problems with 10.3 since updating
> to beta 1 from 10.2.
>
> I suspect, but am not sure, that my issues are somehow related to the new
> modular mkinit process, it's more or less the only difference I can find in
> my boot logs as compared to 10.2. The lockups occur almost immediately
> after all the various xxx.sh scripts start running, but not always at the
> same point (which makes it harder to figure out where the problem is).
Try setting "PROMPT_FOR_CONFIRM=yes" in /etc/sysconfig/boot. You might want
to set CONFIRM_PROMPT_TIMEOUT to something longer than 5 seconds for the
first couple of boots.
I had similar problems on a HP dv6400 with some of the 10.3alpha kernels. In
my case it turned out to be /etc/init.d/boot.clock and I could lock the
system at will by running hwclock --systohc or hwclock --hctosys
(I don't have the problem on the current 10.3beta1 kernel and could never
quite nail down the root cause when I was seeing the problem on earlier
kernels.)
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-factory+help@xxxxxxxxxxxx
| < Previous | Next > |