All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rodney Gordon II <meff@spherevision.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Tejun Heo <htejun@gmail.com>,
	"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
	Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Subject: Re: [BUG] IT8212 libata driver *still* hard-freezes system on boot on 2.6.22 final.
Date: Mon, 09 Jul 2007 07:44:49 -0500	[thread overview]
Message-ID: <1183985089.4190.2.camel@ghreen.sphere> (raw)
In-Reply-To: <20070709131649.5fa63744@the-village.bc.nu>

On Mon, 2007-07-09 at 13:16 +0100, Alan Cox wrote:
> > > It would be useful to know if a kernel built with no DMA support for the
> > > IT8212 behaved as that might give us a clue about what is choking. If you
> > > look in drivers/ata/pata_it821x.c:it821x_init_one you'll see a pair of
> > > lines that say
> > > 
> > > 	mwdma = 0x1f,
> > > 	udma_mask = 0x7f
> > > 
> > > 
> > > remove, rebuild and report..
> > 
> > Alright.
> > 
> > Attachment [0] is a successful boot with those lines removed. (This a
> > good thing or a bad thing? :)
> 
> Thats an interesting question in itself. It does seem to indicate the
> problem is DMA tuning or DMA related and not IRQ routing - which is good
> as of itself.
> 
> > Attachment [1] is a successful boot with the old ata subsystem using the
> > IT8212.
> 
> For the next trick set mwdma_mask = 0x07 but leave UDMA off and see what
> happens. 

Lock.

> Then try with udma_mask = 0x02 which should force the 50MHz
> clock on not the 66MHz clock just in case its clock related.

Lock. :(

> How much RAM do you have ?

1536MB, using highmem 4GB. Please refer to my dmesg attachments in the
last post for more RAM info :)

> Alan

-r


      reply	other threads:[~2007-07-09 12:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-09  1:23 [BUG] IT8212 libata driver *still* hard-freezes system on boot on 2.6.22 final Rodney Gordon II
2007-07-09  7:23 ` Tejun Heo
2007-07-09  9:49 ` Alan Cox
2007-07-09 11:16   ` Rodney Gordon II
2007-07-09 12:16     ` Alan Cox
2007-07-09 12:44       ` Rodney Gordon II [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=1183985089.4190.2.camel@ghreen.sphere \
    --to=meff@spherevision.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=bzolnier@gmail.com \
    --cc=htejun@gmail.com \
    --cc=linux-ide@vger.kernel.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 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.