linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Justin Madru <jdm64@gawab.com>
To: "Chatre, Reinette" <reinette.chatre@intel.com>
Cc: linux-wireless@vger.kernel.org, linux@vger.kernel.org
Subject: Re: [regression: 2.6.25-rc6: iwl3945]
Date: Fri, 21 Mar 2008 20:54:08 -0700	[thread overview]
Message-ID: <47E482E0.6010905@gawab.com> (raw)
In-Reply-To: <D936D925018D154694D8A362EEB0892003F6F7A4@orsmsx416.amr.corp.intel.com>

Chatre, Reinette wrote:
> On Wednesday, March 19, 2008 3:36 PM, Justin Madru  wrote:
>
>   
>> Mar 18 11:00:02 dell kernel: printk: 1 messages suppressed.
>> Mar 18 11:00:02 dell kernel: wlan0_rename: RX too short data
>> frame payload
>>     
>
> These messages are printed by the mac80211 stack when it receives little
> more than a 802.11 header ...
>  
>   
>> A 1-min Wireshark network dump (my address was 10.68.1.211):
>>    http://jdserver.homelinux.org/linux/wireshark-1min
>>     
>
> This capture does not show the 802.11 headers ... the frames start with
> their 802.3 (Ethernet) headers. Did you take this capture on the host
> self? If so, the capture will only show frames received by this host,
> but unfortunately the frames that cause the message to be displayed have
> already been dropped at this point. Is it possible to get a capture of
> everything that goes over the air? You will need a second wireless
> device that is in monitor mode in order to see this traffic. 
>
> Thanks!
>
> Reinette
>
>   

Yeah, I should have known that. I did take the capture from the kernel 
that didn't work. I'll try another capture on a kernel that doesn't give 
that message. And I'll set it to capture all packets over the air. It'll 
have to be on Monday or Tuesday when I'm at the Uni.

Justin

      reply	other threads:[~2008-03-22  3:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-19 22:35 [regression: 2.6.25-rc6: iwl3945] Justin Madru
2008-03-20 18:44 ` Chatre, Reinette
2008-03-22  3:54   ` Justin Madru [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=47E482E0.6010905@gawab.com \
    --to=jdm64@gawab.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linux@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).