From: Shaun Jackman <sjackman@gmail.com>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Jeff Garzik <jgarzik@pobox.com>, Tejun Heo <htejun@gmail.com>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: Trouble shooting a ten minute boot delay (SiI3112)
Date: Fri, 12 Aug 2005 18:39:13 -0700 [thread overview]
Message-ID: <7f45d939050812183911812222@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0508122113510.16845@yvahk01.tjqt.qr>
2005/8/12, Jan Engelhardt <jengelh@linux01.gwdg.de>:
> >I tried earlyprintk=vga, but it didn't provide any extra information.
> >Although, CONFIG_EARLY_PRINTK is disabled in my .config. Does it need
> >to be set to CONFIG_EARLY_PRINTK=y for earlyprintk=vga to work?
>
> I think yes, otherwise there would not be a .config entry at all.
>
> >I haven't tried Sysrq+T yet. I'll report back.
>
> Mind that it is unlikely to get a good trace at this stage, but it's worth the
> try.
I compiled a vanilla 2.6.12.4 kernel, enabled EARLY_PRINTK and
rebooted with earlyprintk=vga. The kernel didn't display any extra
information before the delay.
$ uname -a
Linux quince 2.6.12.4 #1 Fri Aug 12 13:02:40 PDT 2005 i686 GNU/Linux
$ cat /proc/cmdline
root=/dev/md0 ro nodma earlyprintk=vga
$ grep EARLY_PRINTK /boot/config-2.6.12.4
CONFIG_EARLY_PRINTK=y
I tried Alt-SysRq-T but there was no response. SYSRQ is enabled.
$ grep SYSRQ /boot/config-2.6.12.4
CONFIG_MAGIC_SYSRQ=y
Cheers,
Shaun
next prev parent reply other threads:[~2005-08-13 1:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-09 23:31 Trouble shooting a ten minute boot delay (SiI3112) Shaun Jackman
2005-08-12 2:47 ` Tejun Heo
2005-08-12 8:00 ` Shaun Jackman
2005-08-12 8:03 ` Jeff Garzik
2005-08-12 17:44 ` Shaun Jackman
2005-08-12 18:39 ` Jan Engelhardt
2005-08-12 19:08 ` Shaun Jackman
2005-08-12 19:14 ` Jan Engelhardt
2005-08-13 1:39 ` Shaun Jackman [this message]
2005-08-13 2:55 ` Steven Rostedt
2005-08-15 22:34 ` Shaun Jackman
-- strict thread matches above, loose matches on Subject: below --
2005-08-16 12:37 Etienne Lorrain
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=7f45d939050812183911812222@mail.gmail.com \
--to=sjackman@gmail.com \
--cc=htejun@gmail.com \
--cc=jengelh@linux01.gwdg.de \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.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