public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Clayton <chris2553@googlemail.com>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: Alan Stern <stern@rowland.harvard.edu>,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	SCSI development list <linux-scsi@vger.kernel.org>,
	USB list <linux-usb@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	James Bottomley <James.Bottomley@hansenpartnership.com>,
	Hannes Reinecke <hare@suse.de>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux1394-devel@lists.sourceforge.net
Subject: Re: 2,6.26-rc4-git2 - long pause during boot
Date: Tue, 10 Jun 2008 19:00:43 +0000	[thread overview]
Message-ID: <200806101900.43572.chris2553@googlemail.com> (raw)
In-Reply-To: <484D8019.3090900@s5r6.in-berlin.de>

On Monday 09 June 2008, Stefan Richter wrote:
> Alan Stern wrote:
> > In fact the log shows that the 30-second delay occurs in the middle of
> > ohci1394 (Firewire) initialization, not USB initialization:
> >
> > Jun  8 05:26:35 upstairs kernel: ohci1394: fw-host0: OHCI-1394 1.1 (PCI):
> > IRQ=[22]  MMIO=[fbfff000-fbfff7ff]  Max Packet=[2048]  IR/IT
> > contexts=[4/8] Jun  8 05:26:35 upstairs kernel: ohci_hcd 0000:02:0a.0:
> > urb f71cb680 path 2 ep1in 5e160000 cc 5 --> status -62 Jun  8 05:26:35
> > upstairs kernel: hub 1-2:1.0: transfer --> -62
> > Jun  8 05:27:08 upstairs kernel: driver: '0000:02:0b.0': driver_bound:
> > bound to device 'ohci1394' Jun  8 05:27:08 upstairs kernel: bus: 'pci':
> > really_probe: bound device 0000:02:0b.0 to driver ohci1394
>
> The log at http://lkml.org/lkml/2008/6/6/317 shows two pauses.  One in
> the middle of USB related messages with no FireWire stuff around
> (17:25:19 to 17:25:44).  The other with parport, ieee1394, USB messages
> around it (17:25:44 to 17:26:31).
>
>  From there, the last 17:25:44 message is strange:  The device
> 00110666000013cc which is the controller is reported as being removed.
> Chris, did you do something at this point?

Ah sorry, that's a legacy of when I had considerably less ram than 2GB. I only 
use firewire on the rare occasion that I want to grab some video from my camera 
and I use the parallel port even less frequently. So one of the last things 
that happens in my rc.local init script is that I unload the related drivers.

>
> Also, in http://lkml.org/lkml/2008/6/1/2 you reported a patch which
> changes the SCSI core's interaction with the driver core as first bad
> commit.  Did you check that going before this commit removes _all_ the
> pauses, even those around USB or FireWire messages?  Or did you only
> check whether disk drives appear quickly?

When I was bisecting, I assessed good or bad based on whether I experienced the 
long pause during boot up. You may have seen my reply to James a short while 
ago that I have bisected again and arrived at the same patch.

Thanks,

Chris



-- 
Beauty is in the eye of the beerholder.

  parent reply	other threads:[~2008-06-10 19:03 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 [this message]
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
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=200806101900.43572.chris2553@googlemail.com \
    --to=chris2553@googlemail.com \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=akpm@linux-foundation.org \
    --cc=hare@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=linux1394-devel@lists.sourceforge.net \
    --cc=rjw@sisk.pl \
    --cc=stefanr@s5r6.in-berlin.de \
    --cc=stern@rowland.harvard.edu \
    /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