From: Chris Clayton <chris2553@googlemail.com>
To: "Grant Grundler" <grundler@google.com>
Cc: "James Bottomley" <James.Bottomley@hansenpartnership.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-scsi@vger.kernel.org, "Hannes Reinecke" <hare@suse.de>,
"Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: 2,6.26-rc4-git2 - long pause during boot
Date: Tue, 10 Jun 2008 18:46:24 +0000 [thread overview]
Message-ID: <200806101846.24650.chris2553@googlemail.com> (raw)
In-Reply-To: <da824cf30806082151n12898443p1a780a431e99712f@mail.gmail.com>
On Monday 09 June 2008, Grant Grundler wrote:
> On Fri, Jun 6, 2008 at 10:35 AM, Chris Clayton <chris2553@googlemail.com>
wrote:
> >...
> > Yes, I still get the boot pause and the delay in desktop icons appearing
> > when a usb-storage device is plugged in with -rc5. A boot log is
> > attached. Is there some sort of verbose scsi boot messaging that I can
> > switch on? I've looked but I'm damned if I can find anything in 'make
> > menuconfig'.
>
> SCSI_CONSTANTS and SCSI_LOGGING might help.
> Both live in the SCSI options menu. Read the Kconfig help on how
> to use SCSI_LOGGING.
>
> Can you please also enable CONFIG_PRINTK_TIME ?
I've enabled CONFIG_PRINTK_TIME and will look into the SCSI options.
Thanks
>
> Using the timestamps in /var/log/messages is ok but not the most
> reliable place to get somewhat accurate time stamps of events.
>
> hth,
> grant
--
Beauty is in the eye of the beerholder.
next prev parent reply other threads:[~2008-06-10 18:49 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-01 4:15 2,6.26-rc4-git2 - long pause during boot Chris Clayton
2008-06-06 5:17 ` Andrew Morton
2008-06-06 6:07 ` Chris Clayton
2008-06-06 6:21 ` Andrew Morton
2008-06-06 6:25 ` Andrew Morton
2008-06-06 15:22 ` James Bottomley
2008-06-06 18:03 ` Andrew Morton
2008-06-06 18:40 ` James Bottomley
2008-06-07 5:16 ` Chris Clayton
2008-06-08 6:19 ` Chris Clayton
2008-06-08 18:37 ` James Bottomley
2008-06-09 23:07 ` Greg KH
2008-06-10 18:49 ` Chris Clayton
2008-06-10 22:06 ` Chris Clayton
2008-06-10 22:19 ` Alan Stern
2008-06-11 18:58 ` Chris Clayton
2008-06-11 19:15 ` Greg KH
2008-06-11 19:24 ` James Bottomley
2008-06-11 19:29 ` Stefan Richter
2008-06-11 19:36 ` James Bottomley
2008-06-13 6:56 ` Chris Clayton
2008-06-13 14:12 ` James Bottomley
2008-06-11 19:33 ` Greg KH
2008-06-11 19:51 ` Chris Clayton
2008-06-11 21:04 ` Stefan Richter
2008-06-11 21:46 ` Stefan Richter
2008-06-11 22:03 ` Stefan Richter
2008-06-14 6:03 ` Chris Clayton
2008-06-09 14:46 ` Alan Stern
2008-06-09 19:10 ` Stefan Richter
2008-06-09 19:40 ` Alan Stern
2008-06-09 21:35 ` Chris Clayton
2008-06-10 19:00 ` Chris Clayton
2008-06-10 19:38 ` Stefan Richter
2008-06-06 14:11 ` James Bottomley
2008-06-06 14:42 ` Rafael J. Wysocki
2008-06-06 17:42 ` Chris Clayton
2008-06-06 17:35 ` Chris Clayton
2008-06-09 4:51 ` Grant Grundler
2008-06-10 18:46 ` Chris Clayton [this message]
2008-06-06 10:45 ` Rafael J. Wysocki
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=200806101846.24650.chris2553@googlemail.com \
--to=chris2553@googlemail.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=akpm@linux-foundation.org \
--cc=grundler@google.com \
--cc=hare@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=rjw@sisk.pl \
/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