From: "Guo-Fu Tseng" <cooldavid@cooldavid.org>
To: Ben Hutchings <ben@decadent.org.uk>
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, 7 Oct 2011 14:24:26 +0800 [thread overview]
Message-ID: <20111007062340.M45708@cooldavid.org> (raw)
In-Reply-To: <1317961087.4024.28.camel@deadeye>
On Fri, 07 Oct 2011 05:17:52 +0100, Ben Hutchings wrote
> 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
I'll find some time to look into it this weekend.
Thanks for the report. :)
Guo-Fu Tseng
prev parent reply other threads:[~2011-10-07 6:31 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 ` Bug#644281: linux-image-3.0.0-1-amd64: problem after changing mtu size on jme kernel module Ben Hutchings
2011-10-07 6:24 ` Guo-Fu Tseng [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=20111007062340.M45708@cooldavid.org \
--to=cooldavid@cooldavid.org \
--cc=644281@bugs.debian.org \
--cc=ben@decadent.org.uk \
--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 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.