From: Justin Madru <jdm64@gawab.com>
To: linux-wireless@vger.kernel.org, linux@vger.kernel.org
Subject: [regression: 2.6.25-rc6: iwl3945]
Date: Wed, 19 Mar 2008 15:35:43 -0700 [thread overview]
Message-ID: <47E1953F.9020202@gawab.com> (raw)
Hi,
I've been testing out the 2.6.25-rc kernel, and I've run into a possible
regression.
When I connect to my University's wireless network, I get the following
in my system logs
(This is just in one min. and it continues until I turn the computer off):
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
Mar 18 11:00:06 dell kernel: printk: 1 messages suppressed.
Mar 18 11:00:06 dell kernel: wlan0_rename: RX too short data frame payload
Mar 18 11:00:12 dell kernel: printk: 3 messages suppressed.
Mar 18 11:00:12 dell kernel: wlan0_rename: RX too short data frame payload
Mar 18 11:00:17 dell kernel: printk: 2 messages suppressed.
Mar 18 11:00:17 dell kernel: wlan0_rename: RX too short data frame payload
Mar 18 11:00:20 dell kernel: printk: 4 messages suppressed.
Mar 18 11:00:20 dell kernel: wlan0_rename: RX too short data frame payload
Mar 18 11:00:26 dell kernel: wlan0_rename: RX too short data frame payload
Mar 18 11:00:32 dell kernel: printk: 3 messages suppressed.
Mar 18 11:00:32 dell kernel: wlan0_rename: RX too short data frame payload
Mar 18 11:00:36 dell kernel: printk: 3 messages suppressed.
Mar 18 11:00:36 dell kernel: wlan0_rename: RX too short data frame payload
Mar 18 11:00:42 dell kernel: wlan0_rename: RX too short data frame payload
Mar 18 11:00:46 dell kernel: printk: 1 messages suppressed.
Mar 18 11:00:46 dell kernel: wlan0_rename: RX too short data frame payload
Mar 18 11:00:51 dell kernel: printk: 2 messages suppressed.
Mar 18 11:00:51 dell kernel: wlan0_rename: RX too short data frame payload
Mar 18 11:00:56 dell kernel: printk: 5 messages suppressed.
Mar 18 11:00:56 dell kernel: wlan0_rename: RX too short data frame payload
Mar 18 11:01:02 dell kernel: printk: 5 messages suppressed.
This didn't happen when I was using the 2.6.23 or 2.6.24 kernels. Also
it only _(or almost only)_ happens on the Uni. network. At home (where
the problem doesn't happen) my wireless router is a Hawking HWR54G. I
have no idea what the Uni. router is. On both, I connect to an
unencrypted network, but at the Uni. it redirects to a login page where
I have to log on before I can actually use the Internet. Also, even
though I get this flood of kernel messages, I can still use the Internet.
My network card is a Intel 3945ABG.
I was told by another developer (related to another regression I've
found) that the problem could be something about "pipe programming timing".
(see: http://lkml.org/lkml/2008/3/12/290 and
http://lkml.org/lkml/2008/3/14/201)
A 1-min Wireshark network dump (my address was 10.68.1.211):
http://jdserver.homelinux.org/linux/wireshark-1min
My config file:
http://jdserver.homelinux.org/linux/config-2.6.25-rc6
Detailed system information:
http://jdserver.homelinux.org/linux/sysinfo-2.6.25-rc6.txt
Justin
next reply other threads:[~2008-03-19 22:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-19 22:35 Justin Madru [this message]
2008-03-20 18:44 ` [regression: 2.6.25-rc6: iwl3945] Chatre, Reinette
2008-03-22 3:54 ` Justin Madru
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=47E1953F.9020202@gawab.com \
--to=jdm64@gawab.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linux@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).