From: Kasper Sandberg <lkml@metanurb.dk>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Kyle Moffett <mrmacman_g4@mac.com>, Andrew Morton <akpm@osdl.org>,
Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>,
LKML Kernel <linux-kernel@vger.kernel.org>
Subject: Bug in promise_new ide conteroller (was: Re: [BUG] PDC20268 crashing during DMA setup on stock Debian 2.6.12-1-powerpc)
Date: Mon, 21 Nov 2005 22:21:25 +0100 [thread overview]
Message-ID: <1132608085.15938.36.camel@localhost> (raw)
In-Reply-To: <1132520441.6052.41.camel@gaston>
i have a promise controller and it fails too, but only some times (never
during startup).. i get the following errors:
hdf: dma_intr: bad DMA status (dma_stat=75)
hdf: dma_intr: status=0x50 { DriveReady SeekComplete }
ide: failed opcode was: unknown
hdf: dma_timer_expiry: dma status == 0x60
hdf: DMA timeout retry
PDC202XX: Primary channel reset.
hdf: timeout waiting for DMA
and i know for a fact it isnt the indidual controller, as i tried with 2
other brand new ones, and i know it isnt the drives/cables/computer,
since i tried switching it all around, and it keeps happening.
if it does this while reading/writing the system hardlocks..
i wrote promise technical support, which said it could be caused by
sharing interrupts, so i checked, and it did share with my NIC, so i
switched to another pci slot, and now it has its own interrupt, YET it
still keeps doing this..
i would greatly apreciate any help
On Mon, 2005-11-21 at 08:00 +1100, Benjamin Herrenschmidt wrote:
> > This is the only possibility that I can think of, but I'm having a
> > hard time getting enough lines of pre-BUG output. Is there any way
> > to turn off the BUG() lines and just show the printks before that point?
>
> There is a patch from Thibault that fixes it, it should be in 2.6.15-rc2
>
> Ben.
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
prev parent reply other threads:[~2005-11-21 21:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20051017005855.132266ac.akpm@osdl.org>
[not found] ` <1129536482.7620.76.camel@gaston>
[not found] ` <6DFB5723-0042-46FE-811F-BF372B068014@mac.com>
2005-10-19 17:48 ` [BUG] PDC20268 crashing during DMA setup on stock Debian 2.6.12-1-powerpc Kyle Moffett
2005-10-19 22:13 ` Benjamin Herrenschmidt
2005-10-19 23:14 ` Kyle Moffett
2005-10-20 1:36 ` Benjamin Herrenschmidt
2005-11-20 18:29 ` Kyle Moffett
2005-11-20 21:00 ` Benjamin Herrenschmidt
2005-11-21 21:21 ` Kasper Sandberg [this message]
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=1132608085.15938.36.camel@localhost \
--to=lkml@metanurb.dk \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=akpm@osdl.org \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mrmacman_g4@mac.com \
/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.