linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Collins <paul@burly.ondioline.org>
To: reinette chatre <reinette.chatre@intel.com>
Cc: "linux-wireless\@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: iwlagn: possible regressions from 2.6.29 in 2.6.30
Date: Sat, 04 Jul 2009 18:39:11 +1200	[thread overview]
Message-ID: <87tz1thrzk.fsf@bulky.wgtn.ondioline.org> (raw)
In-Reply-To: <87k52t9ynp.fsf@jenny.ondioline.org> (Paul Collins's message of "Wed, 01 Jul 2009 09:53:14 +1200")

Paul Collins <paul@burly.ondioline.org> writes:

> reinette chatre <reinette.chatre@intel.com> writes:
>>> When I say "packets > 250 bytes" I mean 250-byte packets as claimed by
>>> "ping -s 222 mygateway":
>>> 
>>>         PING cornelius.lan (10.2.4.1) 222(250) bytes of data.
>>> 
>>> The above will work, but "ping -s 223 cornelius" yields no replies.
>>
>> Are you saying this works before suspend, but not after resume? What do
>> you usually do to get this working again?
>
> Yes, normally it works great; I can ping with packet sizes up to the
> MTU.  However, after suspend/resume and reassociation, "ping -s 223" or
> greater does not work.  I get replies with "-s 222" or less,
> i.e. packets of 250 bytes or less.
>
> To get it working again I do "ifdown wlan0" followed by "ifup wlan0",
> which does the equivalent of "ip set link wlan0 down/up" and applying
> the network configuration.
>
> I will give the patch a shot when I get home.

I thought at first that the patch had moved the problem from reliably
reproducible to intermittently reproducible, but it looks like it was
simply intermittently reproducible the whole time.  So, no change with
the patch applied.

-- 
Paul Collins
Wellington, New Zealand

Dag vijandelijk luchtschip de huismeester is dood

  reply	other threads:[~2009-07-04  6:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-30  5:30 iwlagn: possible regressions from 2.6.29 in 2.6.30 Paul Collins
2009-06-30 16:17 ` reinette chatre
2009-06-30 21:53   ` Paul Collins
2009-07-04  6:39     ` Paul Collins [this message]
2009-08-03 21:08       ` reinette chatre

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=87tz1thrzk.fsf@bulky.wgtn.ondioline.org \
    --to=paul@burly.ondioline.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=reinette.chatre@intel.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).