From: Pavel Machek <pavel@ucw.cz>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.31: booting on a PIII Celeron?
Date: Tue, 29 Sep 2009 18:03:12 +0200 [thread overview]
Message-ID: <20090929160312.GA14405@elf.ucw.cz> (raw)
In-Reply-To: <4AC20CD0.8030801@msgid.tls.msk.ru>
Hi!
>>> So the celeron machine lacks "apic" flag. And in my
>>> kernel config, apic is enabled:
>>> CONFIG_X86_LOCAL_APIC=y
>>> CONFIG_X86_IO_APIC=y
>>> (but not on the command line like apic=force)
>> try 'noapic nolapic' to see if it helps?
>
> Neither (nor both) changes anything. It just reboots
> instantly right after "Loading initrd..." message from
> the bootloader.
Ok, you may want to try bisection...
> Ok, one more thing to mention. 2.6.31 introduced a
> somewhat annoying feature, -- the screen (console)
> blinks at the very start of the boot process (I mean
> text mode, no any framebuffers or the like). Here,
> the screen blinks as usual for .31, I can see everything
> back including that "Loading initrd" line, and only
> after this the system reboots. No more messages
> gets printed, including "kernel command line:",
> "Initializing cgroup subsys" or "Linux version ...".
> I switched CPU clock to 200MHz (minimum clock rate
> this motherboard supports using jumpers) and I can
> see the whole thing like in slow motion.
Hmm, can you try enabling earlyprintk?
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2009-09-29 16:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-28 15:26 2.6.31: booting on a PIII Celeron? Michael Tokarev
2009-09-28 15:29 ` Michael Tokarev
2009-09-28 16:36 ` Pavel Machek
2009-09-28 16:41 ` Cyrill Gorcunov
2009-09-29 13:34 ` Michael Tokarev
2009-09-29 16:03 ` Pavel Machek [this message]
2009-10-02 10:44 ` LZMA on PIII-Celeron is broken [was: 2.6.31: booting on a PIII Celeron?] Michael Tokarev
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=20090929160312.GA14405@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mjt@tls.msk.ru \
/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