All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Pratyush Anand <pratyush.anand@gmail.com>
Cc: linux-pci@vger.kernel.org, linux-ide@vger.kernel.org,
	Jesse Barnes <jbarnes@virtuousgeek.org>
Subject: Re: Crash with sata_sil24 driver
Date: Tue, 22 Nov 2011 07:06:13 -0800	[thread overview]
Message-ID: <20111122150613.GA322@google.com> (raw)
In-Reply-To: <CAHM4w1nZ7GgutiuDiTCKu9wUuphn8qOiWgmCYVXXvwW1q8CgoA@mail.gmail.com>

Hello,

(cc'ing Jesse)

On Tue, Nov 22, 2011 at 04:40:40PM +0530, Pratyush Anand wrote:
> > I am using various PCIe card based on Silicon Image 3124/3132 to
> > test my PCIe host. This card is working with most of my host controler.
> > I use sata_sil24 driver to enable the card, with one modification of
> > commenting line [pcie_set_readrq(pdev, 4096);]
> >
> > I had sent a patch for it , which is still unanswered.
> > http://comments.gmane.org/gmane.linux.kernel.pci/10300

Yeah, that's something lifted from proprietary driver and it's
likely to be wrong.  Jesse, is there a way to find out the safe
maximum value for readrq?  I'm a bit reluctant to drop it as pcie
variants of these chips are bottlenecked on the host bus pretty badly.

> > Anyway, this mail is regarding another issue.
> >
> > I am still having problem when I use above driver (with above patch),
> > in following
> > situation.
> >
> > My SOC is having cortex-a9 dual core. When I work with CPU freq 500
> > MHz, it works
> > well. But with 600 MHz it crashes. Crash log is at the end of mail.
> >
> > I did further debugging. I found that if I put some delay after
> > calling of sil24_init_controller(host); in function sil24_init_one, it
> > works well.
> >
> > My question is.
> > does sil24_init_controller insure perfact initilization?
> > or we missing to check some status register which might be needed
> > before ata_host_activate.
> > ----------------------------------------------------------------------------------------------------------------
> > Modules linked in:
> > CPU: 0    Not tainted  (2.6.37-lsp-3.2.2-rc-dirty #7)
> > PC is at sil24_scr_read+0x38/0x50
> > LR is at sil24_port_base+0x14/0x2c
> > pc : [<80255e10>]    lr : [<80255d44>]    psr: 80000013

Hmm... this is weird.  All init happens in the same thread.  There's
no race condition involved here.  I'm not too familiar with arm.  Can
you please track down what is causing the crash?  ie. is it memory
access to kernel data structure or io region?

Thanks.

-- 
tejun

  reply	other threads:[~2011-11-22 15:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAHM4w1kc+5aYWH-09BPTXZdo8+iguFjORKs7mMhG7hea2UU8yQ@mail.gmail.com>
2011-11-22 11:10 ` Crash with sata_sil24 driver Pratyush Anand
2011-11-22 15:06   ` Tejun Heo [this message]
2011-11-23  5:19     ` Pratyush Anand
2011-11-23 16:29       ` Tejun Heo
2011-11-23 18:01         ` Russell King - ARM Linux
2011-11-24  3:32           ` Pratyush Anand
2011-11-23 22:47         ` Jesse Barnes
2011-11-24  1:48           ` Tejun Heo
2011-11-24  4:36             ` Pratyush Anand
2011-12-15  3:44               ` Pratyush Anand
2012-01-05  6:54                 ` Pratyush Anand

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=20111122150613.GA322@google.com \
    --to=tj@kernel.org \
    --cc=jbarnes@virtuousgeek.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=pratyush.anand@gmail.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.