From: David Miller <davem@davemloft.net>
To: radek@podgorny.cz
Cc: netdev@vger.kernel.org
Subject: Re: via velocity trivial patch
Date: Fri, 08 May 2009 12:40:41 -0700 (PDT) [thread overview]
Message-ID: <20090508.124041.17500179.davem@davemloft.net> (raw)
In-Reply-To: <4A04184E.5040507@podgorny.cz>
From: Radek Podgorny <radek@podgorny.cz>
Date: Fri, 08 May 2009 13:32:30 +0200
> The "some garbage" are just my words for what Jeff Garzik called "also
> bail if 0xffffffff (hardware fault / hardware unplugged)" in
> http://lkml.indiana.edu/hypermail/linux/kernel/0406.0/0500.html in 2004.
> Should I change that?
>
> Anyway, I've verified this is really happening on my hardware when
> multiple via velocity devices share the same interrupt. The one the
> interrupt is for reads the correct ISR value, the others sometimes read
> 0 and sometimes 0xffffffff. I'm not educated enough to tell why.
>
> Reasons to include the fix:
> 1) Someone smarter than me suggested it (Jeff Garzik).
> 2) Fixed my problem.
> 3) Does not introduce a new problem.
>
> So I'm attaching the patch again. Now with the proper sign-off.
I don't think we should include this until we know why your
card is showing this value in the status register.
Since I assume you aren't unplugging the device showing this
behavior, the only possible remaining reason is "hardware fault"
and we need to understand that better before we start working
around it.
I consider it a good bet that Jeff has no idea why the chip is
doing this either. :-)
next prev parent reply other threads:[~2009-05-08 19:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <49F1A05A.8070802@podgorny.cz>
2009-05-06 21:07 ` via velocity trivial patch Radek Podgorny
2009-05-07 22:02 ` David Miller
2009-05-08 11:32 ` Radek Podgorny
2009-05-08 19:29 ` Francois Romieu
2009-05-10 21:06 ` Radek Podgorny
2009-05-13 13:03 ` Radek Podgorny
2009-05-13 22:32 ` Francois Romieu
2009-05-08 19:40 ` David Miller [this message]
2009-05-08 19:41 ` David Miller
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=20090508.124041.17500179.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=radek@podgorny.cz \
/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