From: Ben Hutchings <ben@decadent.org.uk>
To: Guo-Fu Tseng <cooldavid@cooldavid.org>
Cc: 644281@bugs.debian.org, kantacki <kantacki@o2.pl>,
netdev <netdev@vger.kernel.org>
Subject: Re: Bug#644281: linux-image-3.0.0-1-amd64: problem after changing mtu size on jme kernel module
Date: Fri, 07 Oct 2011 05:17:52 +0100 [thread overview]
Message-ID: <1317961087.4024.28.camel@deadeye> (raw)
In-Reply-To: <20111004181353.3212.57206.reportbug@ASUS>
[-- Attachment #1: Type: text/plain, Size: 815 bytes --]
On Tue, 2011-10-04 at 20:13 +0200, kantacki wrote:
> Package: linux-2.6
> Version: 3.0.0-3
> Severity: important
> Tags: upstream
>
> Hello,
>
> When I try to execute:
> ifconfig eth0 mtu 4000 up
> or
> ifconfig eth0 mtu 7198 up
> my nic stops working and changing back to mtu 1500 does not help.
> To use my nic again I have to execute:
> rmmod jme
> modprome jme
> and the the command ifconfig eth0 mtu 1500 $IP up works and enables the network
>
> My network card is Jmicron
[...]
Can you look into this, please?
It appears that jme_change_mtu() doesn't stop the RX path and doesn't
immediately reallocate RX buffers, and I think it should. Maybe that's
not the problem though.
Ben.
--
Ben Hutchings
For every action, there is an equal and opposite criticism. - Harrison
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next parent reply other threads:[~2011-10-07 4:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20111004181353.3212.57206.reportbug@ASUS>
2011-10-07 4:17 ` Ben Hutchings [this message]
2011-10-07 6:24 ` Bug#644281: linux-image-3.0.0-1-amd64: problem after changing mtu size on jme kernel module Guo-Fu Tseng
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=1317961087.4024.28.camel@deadeye \
--to=ben@decadent.org.uk \
--cc=644281@bugs.debian.org \
--cc=cooldavid@cooldavid.org \
--cc=kantacki@o2.pl \
--cc=netdev@vger.kernel.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).