From: Lance Lassetter <lancelassetter@gmail.com>
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: netdev@vger.kernel.org
Subject: Re: r8169 with 3.9.0-rc9
Date: Wed, 1 May 2013 16:28:07 -0500 [thread overview]
Message-ID: <20130501212803.GA3342@gmail.com> (raw)
In-Reply-To: <20130501121502.GA5456@electric-eye.fr.zoreil.com>
On Wed, May 01, 2013 at 02:15:02PM +0200, Francois Romieu wrote:
> Lance Lassetter <lancelassetter@gmail.com> :
> [...]
> > Any luck with this ?
>
> This is not the usual AMD iommu + realtek NIC problem.
>
> This is not the usual "I upgraded from 2.6 and my Realtek NIC stopped working".
>
> This is not "recent Realtek NIC support is wet".
>
> This is not an "old Realtek PCI NIC stopped working" only problem.
>
> This is an AMD box.
>
> May I assume that you used an up-to-date Fedora 17 before migrating to
> Fedora 18 when it was published ?
>
> --
> Ueimor
Ueimor,
Yes, it was an up to date Fedora 17. I know this is probably redundant but I also tried Realtek firmware from a Debian Sid box onto the Fedora 18 using testing repos with vanilla stable kernel to the same result.
Should I file a Red Hat bug? Manually change IRQs, what do you think?
Regards,
Lance
next prev parent reply other threads:[~2013-05-01 21:28 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-26 13:23 r8169 with 3.9.0-rc9 Lance Lassetter
2013-04-26 20:50 ` Francois Romieu
2013-04-27 4:12 ` Lance Lassetter
2013-04-28 1:12 ` Lance Lassetter
2013-05-01 10:07 ` Lance Lassetter
2013-05-01 12:15 ` Francois Romieu
2013-05-01 21:28 ` Lance Lassetter [this message]
2013-05-01 22:31 ` Francois Romieu
2013-05-02 2:18 ` Lance Lassetter
2013-05-02 22:18 ` Francois Romieu
2013-05-03 4:24 ` Lance Lassetter
2013-05-05 15:17 ` Lance Lassetter
2013-05-05 16:02 ` Lance Lassetter
2013-05-05 19:33 ` Francois Romieu
2013-05-09 17:14 ` Lance Lassetter
2013-05-09 17:50 ` Lance Lassetter
2013-05-10 19:02 ` Lance Lassetter
2013-05-14 3:04 ` Lance Lassetter
2013-05-17 14:35 ` Lance Lassetter
2013-05-24 4:45 ` Lance Lassetter
2013-06-04 2:16 ` Lance Lassetter
2013-05-02 2:23 ` Lance Lassetter
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=20130501212803.GA3342@gmail.com \
--to=lancelassetter@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=romieu@fr.zoreil.com \
/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).