From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: hda interrupt timeouts on sa1110 + sa1111 board
Date: Wed, 27 Oct 2010 21:27:59 +0100 [thread overview]
Message-ID: <20101027202759.GC24573@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20101025211239.GD879@boggieman.bredbandsbolaget.se>
On Mon, Oct 25, 2010 at 11:12:39PM +0200, Kristoffer Ericson wrote:
> Greetings,
>
> First off I havent bisected this yet, but sounds more than likely
> that it comes with the sa1111.c changes. It works fine in v2.6.34 also.
>
> As you can see it progresses a bit but keeps loosing interrupts.
I don't see anything in the sa1111 core, soc_common, or sa11* pcmcia
code which would cause this change of behaviour. I think it may
require a bisect to find what change broke this.
> [ 37.136325] setting trigger mode 3 for irq 51 failed (sa1111_type_highirq+0x0/0x90)
> [ 37.182938] setting trigger mode 3 for irq 53 failed (sa1111_type_highirq+0x0/0x90)
These are fine - the soc_common code intentionally tries to set the type
to rising, then both edges - the idea being that we get rising edge if
the hardware doesn't support both edges.
> [ 40.662432] jornada720_pcmcia_configure_socket(): config socket 1 vcc 33 vpp 0
> [ 40.767874] jornada720_pcmcia_configure_socket(): config socket 1 vcc 33 vpp 0
> [ 41.220300] hda: SanDisk SDCFX3-8192, CFA DISK drive
> [ 42.002086] ide0 at 0xc8840000-0xc8840007,0xc884000e on irq 49
> [ 42.071940] isa bounce pool size: 16 pages
> [ 42.133597] hda: max request size: 128KiB
> [ 42.191639] hda: 16007040 sectors (8195 MB) w/1KiB Cache, CHS=15880/16/63
> [ 72.340242] hda: lost interrupt
And this suggests no interrupts what so ever are coming from the drive.
next prev parent reply other threads:[~2010-10-27 20:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-25 21:12 hda interrupt timeouts on sa1110 + sa1111 board Kristoffer Ericson
2010-10-27 20:27 ` Russell King - ARM Linux [this message]
2010-10-27 21:04 ` Kristoffer Ericson
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=20101027202759.GC24573@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.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