From: Vitaly Bordug <vbordug@ru.mvista.com>
To: Laurent Pinchart <laurent.pinchart@tbox.biz>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: fs_enet driver "generating" bad interrupts on 2.6.19
Date: Fri, 1 Dec 2006 22:45:16 +0300 [thread overview]
Message-ID: <20061201224516.70206c49@localhost.localdomain> (raw)
In-Reply-To: <200612011418.26201.laurent.pinchart@tbox.biz>
[-- Attachment #1: Type: text/plain, Size: 535 bytes --]
On Fri, 1 Dec 2006 14:18:26 +0100
Laurent Pinchart wrote:
>
> The problem wasn't visible with the 2.6.18 kernel. The number of bad
> interrupts didn't increase with outbound FCC traffic.
>
> Has anyone noticed the same problem ?
>
So, not reproduced on 8272ads and 8560ads FCC's with current kernel.
They are arch/powerpc though.
Bad irq's may be relevant to the fact that ppc/ has some cascaded IRQ's that were not adopted to genirq rework,
but that should be expressed in 2.6.18 too....
--
Sincerely, Vitaly
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2006-12-01 19:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-01 13:18 fs_enet driver "generating" bad interrupts on 2.6.19 Laurent Pinchart
2006-12-01 17:00 ` Vitaly Bordug
2006-12-01 19:45 ` Vitaly Bordug [this message]
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=20061201224516.70206c49@localhost.localdomain \
--to=vbordug@ru.mvista.com \
--cc=laurent.pinchart@tbox.biz \
--cc=linuxppc-embedded@ozlabs.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;
as well as URLs for NNTP newsgroup(s).