mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kyle Moffett <mrmacman_g4@mac.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Andrew Morton <akpm@osdl.org>,
	Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>,
	LKML Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [BUG] PDC20268 crashing during DMA setup on stock Debian 2.6.12-1-powerpc
Date: Wed, 19 Oct 2005 19:14:19 -0400	[thread overview]
Message-ID: <75FE9776-B88F-453E-9616-850097DB0138@mac.com> (raw)
In-Reply-To: <1129760024.7620.219.camel@gaston>


On Oct 19, 2005, at 18:13:44, Benjamin Herrenschmidt wrote:
> On Wed, 2005-10-19 at 13:48 -0400, Kyle Moffett wrote:
>
>> Do you have any other ideas WRT this bug?  I've been browsing  
>> around in the code a bit, and I plan to try diffing my 2.6.8.1  
>> version of the files against the latest Debian to see what  
>> changed, although I suspect it will be a relatively fat hunk of  
>> changes.  Thanks for your
>> help!
>>
>
> Nope. The lspci output looks perfectly normal. I looks like a  
> mixture of issues with BM DMA being disabled for a reason I haven't  
> figured out and then the code crashing because it doesn't like BM- 
> DMA being disabled ...

BusMaster-DMA definitely should be enabled on that card.  After a lot  
of looking through icky IDE code, I've determined that the reason for  
the crash is that if there is a "mate", or another IDE bus on the  
same card, then hwif->dma_master is set to hwif->mate->dma_base on  
the secondary channel.  Since DMA explicitly wasn't enabled on the  
primary channel, hwif->dma_master on the secondary is 0 even though  
dma is enabled, and therefore we hit that BUG().

Therefore it seems that the only issue is ide_get_or_set_dma_base is  
returning 0 when it should return a valid DMA base.  In that  
function, the only ways that function can even theoretically return 0  
without printing any weird error messages is "if (hwif->mmio)" or "if  
(hwif->mate && hwif->mate->dma_base)".  The latter can't happen  
before hwif->mate is set up (since the problem is while initializing  
the primary).  Could hwif->mmio be nonzero somehow?  The only drivers  
that seem to set it are pci/sgiioc4, pci/siimage, ppc/pmac, and a  
couple misc arch drivers.

I see a couple theoretical possibilities:
   * hwif->mate and hwif->mate->dma_base are set for the primary  
while still initializing it (before any secondary is set up.
   * hwif->mmio is set somehow even though it shouldn't be, is the  
value ever pre-initialized to 0?

> Again, best is you pour printk's all over setup-pci.c and ide-dma.c  
> to figure out what's going on...

I wish I could but the machine is remote and in-production, so it's  
hard to have time to do much with it.  I'm trying as best I can to  
walk through the sources by hand, specifically with regards to  
changes between the two.  I'm hoping I can come up with a good enough  
guess by Thanksgiving, so that when I have a week near the server to  
test things out I can make significant progress.

Cheers,
Kyle Moffett

--
I have yet to see any problem, however complicated, which, when you  
looked at it in the right way, did not become still more complicated.
   -- Poul Anderson




  reply	other threads:[~2005-10-19 23:14 UTC|newest]

Thread overview: 8+ 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     ` Kyle Moffett
2005-10-19 22:13       ` Benjamin Herrenschmidt
2005-10-19 23:14         ` Kyle Moffett [this message]
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                 ` Bug in promise_new ide conteroller (was: Re: [BUG] PDC20268 crashing during DMA setup on stock Debian 2.6.12-1-powerpc) Kasper Sandberg
2005-10-15 22:29 [BUG] PDC20268 crashing during DMA setup on stock Debian 2.6.12-1-powerpc Kyle Moffett

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=75FE9776-B88F-453E-9616-850097DB0138@mac.com \
    --to=mrmacman_g4@mac.com \
    --cc=B.Zolnierkiewicz@elka.pw.edu.pl \
    --cc=akpm@osdl.org \
    --cc=benh@kernel.crashing.org \
    --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

all inboxes | Powered by JetHome®