From: Jens Axboe <axboe@suse.de>
To: gmu 2k6 <gmu2006@gmail.com>
Cc: Roman Zippel <zippel@linux-m68k.org>, linux-kernel@vger.kernel.org
Subject: Re: Re: i686 hang on boot in userspace
Date: Tue, 25 Jul 2006 09:32:08 +0200 [thread overview]
Message-ID: <20060725073208.GA10601@suse.de> (raw)
In-Reply-To: <f96157c40607240834i5ba3ca5cma51eec9fa34558bc@mail.gmail.com>
On Mon, Jul 24 2006, gmu 2k6 wrote:
> the problem I have with hangs is related to changes in CFQ and that
> CFQ is now the default. 2.6.17-git12 had the problem but booting
> it with elevator=deadline fixes the hang.
>
> symptoms encountered during git-bisecting between v2.6.17 and v2.6.18-rc1:
> A hang while starting network services
> B hang while trying to login
> 1 on remote console [not SSH] it hang after typing <uid><CR>
> 1 via OpenSSH it hang after typing <pwd><CR> when doing slogin root@<IP>
>
> A is the problem I got in the first place and this seems to be the
> case since 2.6.17-git11 definitely although git-bisect pointed me at
> the following
> changeset which is included since 2.6.17-git12:
>
> caaa5f9f0a75d1dc5e812e69afdbb8720e077fd3
> by Jens Axboe
> titled "[PATCH] cfq-iosched: many performance fixes"
>
> strange enough it also hangs with 2.6.17-git11 which did not include that
> one changeset yet.
So perhaps your bisect isn't 100% trust worthy? Can you do a manual
-gitX bisect to see which 2.6.17-gitX introduced the problem?
Also please put a serial console or similar on the machine, so you can
log + store the sysrq+t output.
--
Jens Axboe
next prev parent reply other threads:[~2006-07-25 7:33 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060714150418.120680@gmx.net>
2006-07-14 19:43 ` i686 hang on boot in userspace john stultz
2006-07-17 10:52 ` Roman Zippel
2006-07-17 11:09 ` Roman Zippel
2006-07-17 13:38 ` Uwe Bugla
2006-07-17 14:17 ` Roman Zippel
2006-07-17 14:59 ` gmu 2k6
2006-07-17 15:21 ` Roman Zippel
2006-07-17 15:58 ` gmu 2k6
2006-07-17 16:02 ` gmu 2k6
2006-07-17 17:03 ` Roman Zippel
2006-07-17 18:15 ` gmu 2k6
2006-07-17 18:17 ` gmu 2k6
2006-07-18 9:38 ` gmu 2k6
2006-07-19 10:26 ` gmu 2k6
2006-07-24 15:34 ` gmu 2k6
2006-07-25 7:32 ` Jens Axboe [this message]
2006-07-25 8:00 ` gmu 2k6
2006-07-25 7:41 ` Jens Axboe
[not found] ` <f96157c40607250120s2554cbc6qbd7c42972b70f6de@mail.gmail.com>
[not found] ` <20060725080002.GD4044@suse.de>
2006-07-25 8:28 ` gmu 2k6
2006-07-25 8:08 ` Jens Axboe
2006-07-25 9:17 ` gmu 2k6
2006-07-25 8:57 ` Jens Axboe
2006-07-25 10:09 ` gmu 2k6
2006-07-25 9:46 ` Jens Axboe
2006-07-25 10:19 ` gmu 2k6
2006-07-25 10:41 ` Jens Axboe
2006-07-25 9:20 ` gmu 2k6
2006-07-25 8:57 ` Jens Axboe
2006-07-25 9:35 ` gmu 2k6
2006-07-25 9:24 ` Jens Axboe
2006-07-25 11:29 ` Jens Axboe
2006-07-25 12:47 ` gmu 2k6
2006-07-25 12:52 ` Jens Axboe
2006-07-25 12:58 ` Jens Axboe
2006-07-25 14:27 ` gmu 2k6
2006-07-25 14:29 ` gmu 2k6
2006-07-25 15:18 ` Jens Axboe
2006-07-25 13:13 ` gmu 2k6
2006-07-25 14:50 ` gmu 2k6
2006-07-25 15:19 ` Jens Axboe
2006-07-25 18:58 ` gmu 2k6
2006-07-25 19:21 ` Jens Axboe
2006-07-25 19:28 ` gmu 2k6
2006-07-25 9:51 ` gmu 2k6
2006-07-25 9:42 ` Jens Axboe
2006-07-17 16:11 ` gmu 2k6
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=20060725073208.GA10601@suse.de \
--to=axboe@suse.de \
--cc=gmu2006@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zippel@linux-m68k.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.