mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kay Sievers <kay.sievers@vrfy.org>
To: Christian Kujau <evil@g-house.de>
Cc: kay.sievers@suse.de, linux-kernel@vger.kernel.org, gregkh@suse.de
Subject: Re: [x86_64] strange delays since 2.6.15 (was: Re: ohci1394: aborting transmission)
Date: Wed, 12 Jul 2006 23:14:08 +0200	[thread overview]
Message-ID: <1152738848.3195.32.camel@pim.off.vrfy.org> (raw)
In-Reply-To: <Pine.NEB.4.64.0607122134150.3497@vaio.testbed.de>

On Wed, 2006-07-12 at 22:01 +0100, Christian Kujau wrote:
> Hello all,
> 
> I am still having these strange boot-delays which I reported in [0] when 
> I was under the assumption that ohci1394 was to blame, simply because 
> "ohci1394: aborting transmission" was the last message before the 
> 3minute delay during bootup happened. I've found out that the actual 
> problem started way earlier (2.6.14->2.6.15) and I have bisected my way 
> down to this patchset:
> 
> a7fd67062efc5b0fc9a61368c607fa92d1d57f9e is first bad commit
> diff-tree a7fd67062efc5b0fc9a61368c607fa92d1d57f9e (from 
> d8539d81aeee4dbdc0624a798321e822fb2df7ae)
> Author: Kay Sievers <kay.sievers@suse.de>
> Date:   Sat Oct 1 14:49:43 2005 +0200
> 
>      [PATCH] add sysfs attr to re-emit device hotplug event

Looks like a broken udev/system-init setup, which may hang until a
timeout, while it tries to coldplug devices. When you back out the
patch, coldplug will just fail, that's why the behavior is different.

I'm pretty sure, it has nothing to do with this patch itself. You may
want to look in your bootscripts where it hangs, not in the kernel.

Kay


  reply	other threads:[~2006-07-12 21:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-10  4:29 ohci1394: aborting transmission Christian Kujau
2006-07-10  7:38 ` Stefan Richter
2006-07-10  7:55   ` Christian Kujau
2006-07-10 13:19     ` Stefan Richter
2006-07-12 12:02       ` [x86_64] strange delays since 2.6.15 (was: Re: ohci1394: aborting transmission) Christian Kujau
2006-07-12 21:01         ` Christian Kujau
2006-07-12 21:14           ` Kay Sievers [this message]
2006-07-13  3:36             ` Christian Kujau

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=1152738848.3195.32.camel@pim.off.vrfy.org \
    --to=kay.sievers@vrfy.org \
    --cc=evil@g-house.de \
    --cc=gregkh@suse.de \
    --cc=kay.sievers@suse.de \
    --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

all inboxes | Powered by JetHome®