From: "Toralf Förster" <toralf.foerster@gmx.de>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: ibm-acpi-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: ThinkPad T400 : should kernel option "reboot=pci" be hard coded ?
Date: Wed, 9 Jun 2010 13:43:48 +0200 [thread overview]
Message-ID: <201006091343.48924.toralf.foerster@gmx.de> (raw)
In-Reply-To: <20100607141103.GA9477@srcf.ucam.org>
Hi,
Matthew Garrett wrote at 16:11:03
> On Mon, Jun 07, 2010 at 11:22:21AM +0200, Toralf Förster wrote:
> > Since some kernel version (IIRC since 2.6.31) it is necessary to boot the
> > linux kernel with that option to prevent an extra 9 seconds delay during
> > reboot.
> > I found this tip on the LKML -and now I'm wondering whether this option
> > should be hard coded in the kernel sources b/c it seems to be necessary
> > for current kernels too.
>
> No, the best thing to do would be to figure out what changed to require
> the extra 9 seconds. Are you able to work out which the last kernel
> release without this timeout was?
The delay exists since 2.6.27, versions before them I can't test due to
udev-149 which don't work together with version < 2.6.27.
Since version 2.6.29 that kernel boot parameter avoids the extra delay, 2.6.28
needs the 9 sec pause independend from what I specify during boot.
--
MfG/Kind regards
Toralf Förster
pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3
next prev parent reply other threads:[~2010-06-09 11:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-07 9:22 Toralf Förster
2010-06-07 14:11 ` Matthew Garrett
2010-06-09 11:43 ` Toralf Förster [this message]
2010-07-14 5:01 ` Pedro Ribeiro
2011-03-01 8:40 ` Toralf Förster
2011-03-01 12:35 ` Matthew Garrett
2011-03-01 20:28 ` [ibm-acpi-devel] " Henrique de Moraes Holschuh
2010-06-09 13:26 ` Nick Bowler
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=201006091343.48924.toralf.foerster@gmx.de \
--to=toralf.foerster@gmx.de \
--cc=ibm-acpi-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@srcf.ucam.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
all inboxes | Powered by JetHome®