From: Andrew Morton <akpm@linux-foundation.org>
To: Mel Gorman <mel@csn.ul.ie>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org, bzolnier@gmail.com
Subject: Re: 2.6.25-mm1: Failing to probe IDE interface
Date: Mon, 28 Apr 2008 09:59:24 -0700 [thread overview]
Message-ID: <20080428095924.3b7dfb96.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080428164235.GA29229@csn.ul.ie>
On Mon, 28 Apr 2008 17:42:36 +0100 Mel Gorman <mel@csn.ul.ie> wrote:
> An old T21 is failing to boot and the relevant message appears to be
>
> [ 1.929536] Probing IDE interface ide0...
> [ 36.939317] ide0: Wait for ready failed before probe !
> [ 37.502676] ide0: DISABLED, NO IRQ
> [ 37.506356] ide0: failed to initialize IDE interface
>
> The owner of ide-mm-ide-add-struct-ide_io_ports-take-2.patch with the
> "DISABLED, NO IRQ" message is cc'd. I've attached the config, full boot log
> and lspci -v for the machine in question. I'll start reverting some of the
> these patches to see if ide-mm-ide-add-struct-ide_io_ports-take-2.patch
> is really the culprit.
ide-mm-ide-add-struct-ide_io_ports-take-2.patch is now in mainline so a
quicky confirmation would be to test Linus's tree.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2008-04-28 16:59 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-17 23:03 2.6.25-mm1: not looking good Andrew Morton
2008-04-17 23:24 ` Greg KH
2008-04-18 0:48 ` Kay Sievers
2008-04-18 1:12 ` Andrew Morton
2008-04-18 4:07 ` Andrew Morton
2008-04-17 23:24 ` Dan Williams
2008-04-17 23:40 ` Andrew Morton
2008-04-18 0:14 ` Andrew Morton
2008-04-18 3:05 ` Jason Wessel
2008-04-18 7:37 ` Ingo Molnar
2008-04-18 11:46 ` Vegard Nossum
2008-04-18 12:34 ` Ingo Molnar
2008-04-18 12:41 ` Vegard Nossum
2008-04-18 13:02 ` Jason Wessel
2008-04-18 13:22 ` Vegard Nossum
2008-04-18 13:27 ` Jason Wessel
2008-04-18 14:47 ` Vegard Nossum
2008-04-18 16:02 ` Vegard Nossum
2008-04-18 21:54 ` Jason Wessel
2008-04-17 23:55 ` Paul Moore
2008-04-18 0:04 ` Andrew Morton
2008-04-18 14:55 ` Paul Moore
2008-04-18 1:35 ` Andrew Morton
2008-04-18 14:57 ` Paul Moore
2008-04-18 5:49 ` Arjan van de Ven
2008-04-18 6:10 ` Andrew Morton
2008-04-18 7:19 ` Ingo Molnar
2008-04-18 7:28 ` Andrew Morton
2008-04-18 9:28 ` Ingo Molnar
2008-04-18 6:40 ` Pekka Enberg
2008-04-18 6:56 ` Andrew Morton
2008-04-18 7:24 ` Ingo Molnar
2008-04-18 7:25 ` Pekka Enberg
2008-04-18 10:32 ` James Morris
2008-04-18 7:09 ` Ingo Molnar
2008-04-18 7:50 ` Andrew Morton
2008-04-18 7:53 ` Andrew Morton
2008-04-18 7:57 ` Andrew Morton
2008-04-18 9:22 ` Ingo Molnar
2008-04-18 12:18 ` Ingo Molnar
2008-04-18 9:42 ` Pavel Machek
2008-04-18 15:22 ` Alan Stern
2008-04-18 11:07 ` Pavel Machek
2008-04-28 16:42 ` 2.6.25-mm1: Failing to probe IDE interface Mel Gorman
2008-04-28 16:59 ` Andrew Morton [this message]
2008-04-29 9:39 ` Mel Gorman
2008-04-28 18:44 ` Bartlomiej Zolnierkiewicz
2008-04-29 9:43 ` Mel Gorman
2008-04-29 15:49 ` Mel Gorman
2008-04-29 16:58 ` Mel Gorman
2008-04-29 21:37 ` Bartlomiej Zolnierkiewicz
2008-04-30 11:16 ` Mel Gorman
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=20080428095924.3b7dfb96.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bzolnier@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
/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