public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Williams <pwil3058@bigpond.net.au>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux-2.6.21 hangs during post boot initialization phase
Date: Fri, 27 Apr 2007 14:12:09 +1000	[thread overview]
Message-ID: <46317819.5020304@bigpond.net.au> (raw)
In-Reply-To: <alpine.LFD.0.98.0704262035410.9964@woody.linux-foundation.org>

Linus Torvalds wrote:
> 
> On Fri, 27 Apr 2007, Peter Williams wrote:
>> The 2.6.21 kernel is hanging during the post boot phase where various daemons
>> are being started (not always the same daemon unfortunately).
>>
>> This problem was not present in 2.6.21-rc7 and there is no oops or other
>> unusual output in the system log at the time the hang occurs.
> 
> Can you use "git bisect" to narrow it down a bit more? It's only 125 
> commits, so bisecting even just three or four kernels will narrow it down 
> to a handful

Yes.  I'm just in the process of reading up on how to do the bisecting 
now.  Should have an answer in a few hours, I guess.

Peter
-- 
Peter Williams                                   pwil3058@bigpond.net.au

"Learning, n. The kind of ignorance distinguishing the studious."
  -- Ambrose Bierce

  reply	other threads:[~2007-04-27  4:12 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-27  2:58 Linux-2.6.21 hangs during post boot initialization phase Peter Williams
2007-04-27  3:36 ` Linus Torvalds
2007-04-27  4:12   ` Peter Williams [this message]
2007-04-27  6:05   ` Peter Williams
2007-04-27 12:22     ` Neil Horman
2007-04-27 12:26       ` Jeff Garzik
2007-04-27 12:52         ` Neil Horman
2007-04-27 14:28       ` Peter Williams
2007-04-27 17:11         ` Neil Horman
2007-04-27 17:46           ` Linus Torvalds
2007-04-27 18:01             ` Jeff Garzik
2007-04-27 23:50           ` Peter Williams
2007-04-28 22:19             ` Neil Horman

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=46317819.5020304@bigpond.net.au \
    --to=pwil3058@bigpond.net.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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