From: poma <pomidorabelisima@gmail.com>
To: Hayes Wang <hayeswang@realtek.com>,
nic_swsd <nic_swsd@realtek.com>,
sean darcy <seandarcy2@gmail.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
Community support for Fedora users
<users@lists.fedoraproject.org>
Subject: Re: NETDEV WATCHDOG: internal(r8152): transmit queue 0 timed out
Date: Fri, 16 Jan 2015 13:09:34 +0100 [thread overview]
Message-ID: <54B8FF7E.2010901@gmail.com> (raw)
In-Reply-To: <0835B3720019904CB8F7AA43166CEEB2EE6935@RTITMBSV03.realtek.com.tw>
On 16.01.2015 10:37, Hayes Wang wrote:
> poma [mailto:pomidorabelisima@gmail.com]
>> Sent: Friday, January 16, 2015 4:25 PM
> [...]
>>> This looks like a USB problem. Is there a way to get usb (or
>>> NetworkManager) to reinitialize the driver when this happens?
>>
>> I would ask these people for advice, therefore.
>
> Our hw engineers need to analyse the behavior of the device.
> However, I don't think you have such instrument to provide
> the required information. If we don't know the reason, we
> couldn't give you the proper solution. Besides, your solution
> would work if and only if reloading the driver is helpful.
>
> The issue have to debug from the hardware, and I have no idea
> about what the software could do before analysing the hw. Maybe
> you could try the following driver first to check if it is useful.
>
> http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=2&PNid=13&PFid=56&Level=5&Conn=4&DownTypeID=3&GetDown=false
>
> Best Regards,
> Hayes
>
Thanks for your response, Mr. Hayes.
Mr. Sean, please download and check if "timeout" is still present with built RTL8153 module from REALTEK site, as Mr. Hayes proposed.
http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=2&PNid=13&PFid=56&Level=5&Conn=4&DownTypeID=3&GetDown=false#2
r8152.53-2.03.0.tar.bz2
Procedure - should be equal for both, Fedora 21 & 20:
$ uname -r
3.17.8-300.fc21.x86_64
$ su -c 'yum install kernel-devel'
$ tar xf r8152.53-2.03.0.tar.bz2
$ cd r8152-2.03.0/
$ make
$ su
# cp 50-usb-realtek-net.rules /etc/udev/rules.d/
# udevadm trigger --action=add
# modprobe -rv r8152
# cp r8152.ko /lib/modules/$(uname -r)/updates/
# depmod
# modprobe -v r8152
poma
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
next prev parent reply other threads:[~2015-01-16 12:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m99j1v$n60$1@ger.gmane.org>
2015-01-16 8:24 ` NETDEV WATCHDOG: internal(r8152): transmit queue 0 timed out poma
[not found] ` <54B8CAC2.6020406-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-01-16 9:37 ` Hayes Wang
2015-01-16 12:09 ` poma [this message]
2015-01-16 16:40 ` sean darcy
2015-01-16 23:57 ` sean darcy
2015-01-17 8:56 ` poma
[not found] ` <54BA23CE.70001-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-02-04 0:20 ` poma
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=54B8FF7E.2010901@gmail.com \
--to=pomidorabelisima@gmail.com \
--cc=hayeswang@realtek.com \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nic_swsd@realtek.com \
--cc=seandarcy2@gmail.com \
--cc=users@lists.fedoraproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.