Mailinglist Archive: opensuse-factory (508 mails)
| < Previous | Next > |
Re: [opensuse-factory] systemd
- From: Peter Czanik <pczanik@xxxxxxxxxxxxxx>
- Date: Tue, 14 Dec 2010 11:59:07 +0100
- Message-id: <4D074DFB.7060001@xxxxxxxxxxxxxx>
Hello,
On 12/14/2010 11:42 AM, Kay Sievers wrote:
least for the last two boots. Without it the machine hangs with or
without a kernel panic message on screen during the boot or right after
the login: prompt is printed.
Bye,
CzP
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-factory+help@xxxxxxxxxxxx
On 12/14/2010 11:42 AM, Kay Sievers wrote:
On Tue, 2010-12-14 at 11:36 +0100, Peter Czanik wrote:Hehe. Once I use the above settings, systemd seems to boot perfectly, at
Hello,Yeah, isolated computational load is a very different situation from
On 12/14/2010 10:27 AM, Kay Sievers wrote:
Without systemd the same system easily survives stress testing (cdI just had a few more kernel panics mentioning different applications,Yeah, could be. It is not unlikely, that the massive parallel startup
so I suspect that it's rather something kernel related.
makes such problems more apparent. A few others have reported similar
issues.
/usr/src/linux && make -j 100 :-) ) without locking up.
booting up -- where we have heavy parallel kernel module load, device
initialization, and service startup going on.
If possible, try, if removing:
quiet
and adding:
systemd.log_level=debug systemd.log_target=kmsg
to the kernel commandline reveals something on the console.
It might slow down the bootup enough, so that it works-- or it might
show where it hangs.
least for the last two boots. Without it the machine hangs with or
without a kernel panic message on screen during the boot or right after
the login: prompt is printed.
Bye,
CzP
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-factory+help@xxxxxxxxxxxx
| < Previous | Next > |