From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Tejun Heo <tj@kernel.org>
Cc: Pratyush Anand <pratyush.anand@gmail.com>,
linux-pci@vger.kernel.org, linux-ide@vger.kernel.org,
Jesse Barnes <jbarnes@virtuousgeek.org>
Subject: Re: Crash with sata_sil24 driver
Date: Wed, 23 Nov 2011 18:01:34 +0000 [thread overview]
Message-ID: <20111123180134.GJ9581@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20111123162937.GF25780@google.com>
On Wed, Nov 23, 2011 at 08:29:37AM -0800, Tejun Heo wrote:
> On Wed, Nov 23, 2011 at 10:49:00AM +0530, Pratyush Anand wrote:
> > On Tue, Nov 22, 2011 at 8:36 PM, Tejun Heo <tj@kernel.org> wrote:
> > > On Tue, Nov 22, 2011 at 04:40:40PM +0530, Pratyush Anand wrote:
> > >> > 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
It would help if the _full_ set of kernel crash messages were included.
This one has the top chopped off it which normally says _why_ it happened.
I'm not about to waste my time by guessing...
Please provide the _full_ crash log, including the lines which come before
"Modules linked in:"
And no, pci_iomap is not asynchronous. That'd just be damned stupid and
would break virtually all drivers.
next prev parent reply other threads:[~2011-11-23 18:01 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
2011-11-23 5:19 ` Pratyush Anand
2011-11-23 16:29 ` Tejun Heo
2011-11-23 18:01 ` Russell King - ARM Linux [this message]
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=20111123180134.GJ9581@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=pratyush.anand@gmail.com \
--cc=tj@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