From: Prarit Bhargava <prarit@sgi.com>
To: Philip Armstrong <phil@kantaka.co.uk>
Cc: Bartlomiej Zolnierkiewicz <bzolnier@elka.pw.edu.pl>,
maximilian attems <debian@sternwelten.at>,
linux-ide@vger.kernel.org, 289770@bugs.debian.org
Subject: Re: (fwd) Re: Bug#289770: kernel-image-2.6.10-1-686: 2.6.10 fails to set up DMA on my IBM thinkpad
Date: Wed, 12 Jan 2005 08:46:32 -0500 [thread overview]
Message-ID: <41E52A38.9060108@sgi.com> (raw)
In-Reply-To: <20050112133524.GA27287@kantaka.co.uk>
Philip and Bartlomiej,
I've been tracking an almost identical problem on my IA64 platform with
a bk pull that is about a month old.
I tracked it down to a duplicate vector request of 0x38 = 56 by the
mmtimer -- take a look at /proc/interrupts, /proc/ioports, /proc/iomem
and see if anything has requested the specific area that your CD is
trying to get.
My output looked like:
SGIIOC4: IDE controller at PCI slot 0000:01:01.0, revision 79
ide0: BM-DMA at 0xc00001080c200140-0xc00001080c200163
Probing IDE interface ide0...
hda: MATSHITADVD-ROM SR-8588, ATAPI CD/DVD-ROM drive
ide0: Disabled unable to get IRQ 56.
Probing IDE interface ide0...
hda: MATSHITADVD-ROM SR-8588, ATAPI CD/DVD-ROM drive
hda: IRQ probe failed (0x4ffffffe)
Probing IDE interface ide1...
ide1: Wait for ready failed before probe !
Probing IDE interface ide2...
ide2: Wait for ready failed before probe !
Probing IDE interface ide3...
ide3: Wait for ready failed before probe !
Probing IDE interface ide4...
ide4: Wait for ready failed before probe !
Probing IDE interface ide5...
ide5: Wait for ready failed before probe !
ide0: DISABLED, NO IRQ
Bartlomiej, just a thought:
I think that the output of the failures of the probes for non-existant
interfaces ide1-ide5 could be suppressed, no?
What would you think if we only output the "failed before probe"
messages for interfaces that return -EBUSY from wait_hwif_ready? It
would make the system boot a lot "prettier":)
P.
>
>Does the kernel know what the 'something' is? Should I be routing
>around in /proc looking for something specific?
>
>cheers,
>
>Phil
>
>
>
next prev parent reply other threads:[~2005-01-12 13:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-11 19:53 (fwd) Re: Bug#289770: kernel-image-2.6.10-1-686: 2.6.10 fails to set up DMA on my IBM thinkpad maximilian attems
2005-01-12 12:02 ` Philip Armstrong
2005-01-12 12:52 ` Bartlomiej Zolnierkiewicz
2005-01-12 12:58 ` Bartlomiej Zolnierkiewicz
2005-01-12 13:35 ` Philip Armstrong
2005-01-12 13:46 ` Prarit Bhargava [this message]
2005-01-12 13:50 ` Bartlomiej Zolnierkiewicz
2005-01-12 17:56 ` Philip Armstrong
2005-01-12 13:48 ` Bartlomiej Zolnierkiewicz
2005-02-10 20:02 ` Philip Armstrong
2005-02-11 6:55 ` Marcin Kuk
2005-02-10 20:08 ` Philip Armstrong
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=41E52A38.9060108@sgi.com \
--to=prarit@sgi.com \
--cc=289770@bugs.debian.org \
--cc=bzolnier@elka.pw.edu.pl \
--cc=debian@sternwelten.at \
--cc=linux-ide@vger.kernel.org \
--cc=phil@kantaka.co.uk \
/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.