Re: [opensuse-factory] Re: Changes with boot/init for 10.3 ? Kernel locks in 10.3, not in 10.2 ?
On Wednesday 15 August 2007 02:23:05 am Warren Stockton wrote: > > 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.) > Thanks for the pointer, that worked but not for the reasons I expected. Once I set PROMPT_FOR_CONFIRM, I was able to step through the service startup and boot properly with both the -default kernel and my own custom kernel. I didn't need to use noapic. However, booting without PROMPT_FOR_CONFIRM and without noapic produces a total lock that occurs at some point between .localfs and .udev-retry, but there are no error messages thrown and nothing indicated in the logs that would point to where the issue is. Booting with noapic and without PROMPT_FOR_CONFIRM also allows a normal boot, though with the stability issues my system experiences with noapic. Bizarre. The only thing I can think is that the parallel booting of services is somehow causing an error condition in the kernel that doesn't occur when boot prompting forces a delay between service starts, or something along those lines? I'll do a round of trial and error, disabling each boot.xxx service one by one to see if I can narrow it down, and maybe disabling parallel services as well. As far as the issue with the clock, I do remember running into that with earlier kernels, I think it first cropped up in 2.6.20, there was some change made that involved acpi, the clock and hpet or something along those lines; I remember eliminating the problem by judiciously tweaking my .config settings, but the problem seemed to have disappeared for me in recent kernels. Any other pointers appreciated... Thanks, KV - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Re: Changes with boot/init for 10.3 ? Kernel locks in 10.3, not in 10.2 ?
On Wednesday 15 August 2007 12:54, Kevin Valko wrote: > and maybe disabling parallel > services as well. I would start with that. Than you have better chance to find service that makes trouble. -- Regards, Rajko. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Re: Changes with boot/init for 10.3 ? Kernel locks in 10.3, not in 10.2 ?
On Wednesday 15 August 2007 09:10:45 pm Rajko M. wrote: > On Wednesday 15 August 2007 12:54, Kevin Valko wrote: > > and maybe disabling parallel > > services as well. > > I would start with that. > Than you have better chance to find service that makes trouble. Disabling parallel services did allow the system to boot normally without requiring interactive confirmations, so there is definitely a conflict happening somewhere with the boot services running in parallel. Unfortunately I'm not sure which one, I tried disabling a number of them individually but the boot still hard-locked when parallel services were enabled, I guess I can try to change the S/K sequences in boot.d, to see if grouping the services (the culprit lies in S12) instead of all together can point out the issue. G. On the plus side, disabling parallel loading didn't have a too significant impact on my boot time, it's still more or less in line with what I had in 10.2, so it's hardly the end of the world, but it is kind of a drag since faster booting is one of the significant improvements for 10.3. Cheers, KV - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Re: Changes with boot/init for 10.3 ? Kernel locks in 10.3, not in 10.2 ?
On Wednesday 15 August 2007 22:22, Kevin Valko wrote: > On Wednesday 15 August 2007 09:10:45 pm Rajko M. wrote: > > On Wednesday 15 August 2007 12:54, Kevin Valko wrote: > > > and maybe disabling parallel > > > services as well. > > > > I would start with that. > > Than you have better chance to find service that makes trouble. > > Disabling parallel services did allow the system to boot normally without > requiring interactive confirmations, so there is definitely a conflict > happening somewhere with the boot services running in parallel. > > Unfortunately I'm not sure which one, I tried disabling a number of them > individually but the boot still hard-locked when parallel services were > enabled, I guess I can try to change the S/K sequences in boot.d, to see if > grouping the services (the culprit lies in S12) instead of all together can > point out the issue. G. > > On the plus side, disabling parallel loading didn't have a too significant > impact on my boot time, it's still more or less in line with what I had in > 10.2, so it's hardly the end of the world, but it is kind of a drag since > faster booting is one of the significant improvements for 10.3. > > Cheers, > KV Hi Kevin, If parallel booting makes problem, than is some of scripts the culprit. It doesn't wait for it's dependencies to be performed. Grouping services will not help much as they are not ran sequentially anyway, but cleaning log files, booting and after lockup, booting Live CD and looking in logs may help to debug issue. The other method to isolate script would be add echo command to scripts that will give on the screen script name. For instance echo $0 >> /tmp/startup.log That will at least tell what was loaded before lockup and it will be preserved after new boot. -- Regards, Rajko. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Re: Changes with boot/init for 10.3 ? Kernel locks in 10.3, not in 10.2 ?
On Wed, 15 Aug 2007, Rajko M. wrote: > On Wednesday 15 August 2007 22:22, Kevin Valko wrote: > > On Wednesday 15 August 2007 09:10:45 pm Rajko M. wrote: > > > On Wednesday 15 August 2007 12:54, Kevin Valko wrote: > > > > and maybe disabling parallel > > > > services as well. > > > > > > I would start with that. > > > Than you have better chance to find service that makes trouble. > > > > Disabling parallel services did allow the system to boot normally without > > requiring interactive confirmations, so there is definitely a conflict > > happening somewhere with the boot services running in parallel. > > > > Unfortunately I'm not sure which one, I tried disabling a number of them > > individually but the boot still hard-locked when parallel services were > > enabled, I guess I can try to change the S/K sequences in boot.d, to see if > > grouping the services (the culprit lies in S12) instead of all together can > > point out the issue. G. > > > > On the plus side, disabling parallel loading didn't have a too significant > > impact on my boot time, it's still more or less in line with what I had in > > 10.2, so it's hardly the end of the world, but it is kind of a drag since > > faster booting is one of the significant improvements for 10.3. > > > > Cheers, > > KV > > Hi Kevin, > > If parallel booting makes problem, than is some of scripts the culprit. > It doesn't wait for it's dependencies to be performed. Grouping services will > not help much as they are not ran sequentially anyway, but cleaning log > files, booting and after lockup, booting Live CD and looking in logs may help > to debug issue. > > The other method to isolate script would be add echo command to scripts that > will give on the screen script name. For instance > echo $0 >> /tmp/startup.log > > That will at least tell what was loaded before lockup and it will be > preserved > after new boot. maybe a sync after the echo would be a good idea -- Mit freundlichen Gruessen, Andreas Vetter Fakultaet fuer Physik und Astronomie Tel: +49 (0)931 888-5890 Universitaet WuerzburgFax: +49 (0)931 888-5508 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Re: Changes with boot/init for 10.3 ? Kernel locks in 10.3, not in 10.2 ?
2007/8/16, Kevin Valko <[EMAIL PROTECTED]>: > On Wednesday 15 August 2007 09:10:45 pm Rajko M. wrote: > > On Wednesday 15 August 2007 12:54, Kevin Valko wrote: > > > and maybe disabling parallel > > > services as well. > > > > I would start with that. > > Than you have better chance to find service that makes trouble. > > Disabling parallel services did allow the system to boot normally without > requiring interactive confirmations, so there is definitely a conflict > happening somewhere with the boot services running in parallel. > > Unfortunately I'm not sure which one, I tried disabling a number of them > individually but the boot still hard-locked when parallel services were > enabled, I guess I can try to change the S/K sequences in boot.d, to see if > grouping the services (the culprit lies in S12) instead of all together can > point out the issue. G. > > On the plus side, disabling parallel loading didn't have a too significant > impact on my boot time, it's still more or less in line with what I had in > 10.2, so it's hardly the end of the world, but it is kind of a drag since > faster booting is one of the significant improvements for 10.3. > What are the "parallel services"? Yesterday I installed 10.3 beta1 x86-64 in a four cores system without problems, and it works fine with the original kernel. (H8DA8 SuperMicro motherboard with AMD 8131/8111 chipset with 2 Opterons dual core 270). In other system, I could'nt install it, because a inmature support of the MSI and the ahci driver on the kernel, and this problem appear in the most of the distros. Regards - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Re: Changes with boot/init for 10.3 ? Kernel locks in 10.3, not in 10.2 ?
On Thursday 16 August 2007 06:04, Andreas Vetter wrote: > > The other method to isolate script would be add echo command to scripts > > that will give on the screen script name. For instance > > echo $0 >> /tmp/startup.log > > > > That will at least tell what was loaded before lockup and it will be > > preserved after new boot. > > maybe a sync after the echo would be a good idea Yes. It will be. One more line that will mark regular end of the script would be good too, but than one needs script that will change all scripts in /etc/init.d, or change scripts manually and save set for future. Than on next release use diff and look only scripts that are changed. I wonder what openSUSE developers use for debugging of start up? -- Regards, Rajko. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
