From: Kevin Hilman <khilman@mvista.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Thomas Gleixner <tglx@linutronix.de>,
"linux-omap-open-source@linux.omap.com"
<linux-omap-open-source@linux.omap.com>,
linux-arm-kernel@lists.arm.linux.org.uk,
Russell King <rmk@arm.linux.org.uk>
Subject: Re: [patchset] Generic IRQ Subsystem: -V5
Date: Fri, 19 May 2006 15:11:15 -0700 [thread overview]
Message-ID: <1148076675.9331.35.camel@vence.internal.net> (raw)
In-Reply-To: <20060519145310.GB12703@elte.hu>
On Fri, 2006-05-19 at 16:53 +0200, Ingo Molnar wrote:
> This is Version 5 of the genirq patch-queue, against 2.6.17-rc4.
I've tested -V5 on various OMAP boards (1710/H3, 1623/H2, and 5912/OSK)
and all have the same network TX timeout problems when booting using
nfsroot. Eventually, they boot to a prompt, but continue to have
periodic timeouts when accessing NFS files.
On all 3 boards, the network driver is the smc91x and the IRQ is a GPIO
interrupt.
Just and FYI... I'm still digging for root cause.
Kevin
parent reply other threads:[~2006-05-19 22:11 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20060519145310.GB12703@elte.hu>]
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=1148076675.9331.35.camel@vence.internal.net \
--to=khilman@mvista.com \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-omap-open-source@linux.omap.com \
--cc=mingo@elte.hu \
--cc=rmk@arm.linux.org.uk \
--cc=tglx@linutronix.de \
/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