From: Nikos Chantziaras <realnc@arcor.de>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: Switching to clocksource tsc: takes AGES on boot
Date: Tue, 14 Feb 2012 14:30:15 +0200 [thread overview]
Message-ID: <jhdk4s$a9h$1@dough.gmane.org> (raw)
In-Reply-To: <751EC8EC-5905-40A3-88E8-8FED89F6C5DB@gmail.com>
On 14/02/12 14:15, LK wrote:
> On 120214, at 13:01, Nikos Chantziaras wrote:
>> On 14/02/12 12:48, LK wrote:
>>>
>>> How do i get rid of that?
>>> It takes one minute on boot, that is awful.
>> If you boot with "acpi=off", does the problem go away? What kernel version are you using?
> No it does not. After the root=/dev/sda5, in grub menu.lst, right ?
Yep.
> Kernel version 3.2.1-r2
> Maybe some setting in kernel settings?
You might want to post to LKML about this. There was a related problem
in 2.6.39, but you're using a recent kernel which has already fixed that
problem. So you're seeing something new.
You can also try the Linux kernel bugtracker:
https://bugzilla.kernel.org/
>>> PS: How do i deamonize a service on startup? DHCPCD for example?
>> It has a service. You add it to the default runlevel:
>> rc-update add dhcpcd default
> It is started automatically, but cant it be ran in the background? It takes some time which isnt necessary. Thanks so far anyway.
Reading the dhcpcd man page says:
-b, --background
Background immediately. This is useful for startup
scripts which don't disable link messages for carrier
status.
So to use that option, edit /etc/conf.d/net and use:
dhcpcd_eth0="--background"
and see if it helps.
next prev parent reply other threads:[~2012-02-14 12:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-14 10:48 [gentoo-user] Switching to clocksource tsc: takes AGES on boot LK
2012-02-14 12:01 ` [gentoo-user] " Nikos Chantziaras
2012-02-14 12:15 ` LK
2012-02-14 12:30 ` Nikos Chantziaras [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-02-15 0:07 mike
2012-02-15 14:52 ` LK
2012-02-15 16:17 ` mike
2012-02-15 17:46 ` LK
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='jhdk4s$a9h$1@dough.gmane.org' \
--to=realnc@arcor.de \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox