From: Chr <chunkeey@web.de>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: John W Linville <linville@tuxdriver.com>, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] p54: Fix for TX sequence number problem that resulted from commit 741b4fbc44
Date: Sat, 9 Aug 2008 18:43:41 +0200 [thread overview]
Message-ID: <200808091843.41985.chunkeey@web.de> (raw)
In-Reply-To: <489DBFA9.80608@lwfinger.net>
On Saturday 09 August 2008 18:02:49 Larry Finger wrote:
>
> Mine also crashes with a ping of length 1400, but 1390 and 1410 work
> just fine. I also tested with tcpperf and I am pretty sure that this
> is a transmit problem. When I set the MTU to 1300, then a ping of
> length 1400 works fine. Is this a firmware bug? Which firmware are you
> using? Mine is isl3887usb_bare.
hmm? there are lots of new & old firmwares.
what chip do you have? a ISL3886 + net2280 or a ISL3887?
you can get the firmware version from dmesg, just load the
driver and grep for "p54: FW rev"
my devices:
isl3880 minipci: 2.7.0.0 (best supported) & 2.13.1.0 (unstable)
isl3887 usb: 2.5.8.0(bugs), 2.6.16.0(DELL bugs) and 2.13.2.0 (WIP)
>
> > on-topic: I digged a bit in the logs:
> >
> > http://jbnote.free.fr/prism54usb/data/usbsnoop-logs/
> > and there "usbsnoop_old_drv_ver1.log.bz2"
> > [...]
> > So the problem must be somewhere else! what happens when:
> > if (info->flags & IEEE80211_TX_CTL_ASSIGN_SEQ) {
> > if (info->flags & IEEE80211_TX_CTL_FIRST_FRAGMENT)
> > priv->seqno += 0x10;
> >
> > ieee80211hdr->seq_ctrl &= cpu_to_le16(IEEE80211_SCTL_FRAG);
> > ieee80211hdr->seq_ctrl |= cpu_to_le16(priv->seqno);
> > ieee80211hdr->seq_ctrl &= cpu_to_le16(IEEE80211_SCTL_FRAG);
> > }
> > (yeah a new definition for idiotic! but it's about the same amount of of
> > clock cycles).
>
> This didn't help the "ping -s 1400" problem.
Of course not, but maybe it could help with this 2-3 hour disconnect problem.
Regards,
Chr.
next prev parent reply other threads:[~2008-08-09 16:40 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-05 16:23 [PATCH] p54: Fix for TX sequence number problem that resulted from commit 741b4fbc44 Larry Finger
2008-08-08 8:26 ` Chr
2008-08-08 14:29 ` Larry Finger
2008-08-08 18:38 ` Chr
2008-08-09 16:02 ` Larry Finger
2008-08-09 16:43 ` Chr [this message]
2008-08-09 18:11 ` Larry Finger
2008-08-10 14:19 ` Larry Finger
2008-08-10 22:27 ` Chr
2008-08-10 23:04 ` Larry Finger
2008-08-13 22:15 ` Chr
2008-08-15 18:34 ` Chr
2008-08-15 19:26 ` Johannes Berg
2008-08-15 20:15 ` Chr
2008-08-15 20:17 ` Johannes Berg
2008-08-15 21:06 ` Chr
2008-08-15 21:13 ` Johannes Berg
2008-08-16 0:34 ` Larry Finger
2008-08-16 2:21 ` Chr
2008-08-16 14:00 ` Larry Finger
2008-08-16 14:38 ` Chr
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=200808091843.41985.chunkeey@web.de \
--to=chunkeey@web.de \
--cc=Larry.Finger@lwfinger.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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 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.