From: Jens Axboe <axboe@suse.de>
To: Adam Kropelin <akropel1@rochester.rr.com>
Cc: linux-kernel@vger.kernel.org, Dave Jones <davej@suse.de>
Subject: Re: 2.5.8-dj1 with IDE TCQ doesn't survive boot
Date: Thu, 18 Apr 2002 08:14:05 +0200 [thread overview]
Message-ID: <20020418061405.GF858@suse.de> (raw)
In-Reply-To: <02e001c1e66d$8e927070$02c8a8c0@kroptech.com>
[-- Attachment #1: Type: text/plain, Size: 1058 bytes --]
On Wed, Apr 17 2002, Adam Kropelin wrote:
> Jens,
>
> Tried 2.5.8-dj1 here with IDE TCQ and it doesn't make it through
> bootup. The lockup (no oops) happens at various places, usually during
> a disk-intensive operation like starting PostgreSQL. Disk & chipset
> detection always goes ok; the lockup is much later in the boot cycle.
> Nothing shows up in the logs.
There are two unknowns for me here -- the IBM model you use has not been
tested, and the adapter is the old PIIX3 core which is untested as well.
There are a few things I would like you to try, if you don't mind.
- First try a later kernel, there have been lots of changes since 2.5.8
wrt TCQ. I've attached a patch against 2.5.8-clean (not -dj1), could
you see if that works for you?
- If that doesn't change anything, please also try and disable
CONFIG_BLK_DEV_IDE_TCQ_FULL.
If none of this makes it work, I'm hoping you can setup a serial console
and do some debug logging for me? If you can, I'll let you know how and
what to capture.
Thanks for your report!
--
Jens Axboe
[-- Attachment #2: ata-tcq-258-all-1.bz2 --]
[-- Type: application/x-bunzip2, Size: 36069 bytes --]
next prev parent reply other threads:[~2002-04-18 6:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-18 0:11 2.5.8-dj1 with IDE TCQ doesn't survive boot Adam Kropelin
2002-04-18 6:14 ` Jens Axboe [this message]
2002-04-19 0:45 ` Adam Kropelin
2002-04-19 10:05 ` Martin Dalecki
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=20020418061405.GF858@suse.de \
--to=axboe@suse.de \
--cc=akropel1@rochester.rr.com \
--cc=davej@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