From: Dan Williams <dcbw@redhat.com>
To: Sebastian Siewior <ipw+2200@ml.breakpoint.cc>
Cc: "Chatre, Reinette" <reinette.chatre@intel.com>,
"Zhu, Yi" <yi.zhu@intel.com>,
James Ketrenos <jketreno@linux.intel.com>,
linux-wireless@vger.kernel.org,
ipw2100-devel@lists.sourceforge.net
Subject: Re: ipw2200 stalls on high load
Date: Tue, 05 Feb 2008 23:56:47 -0500 [thread overview]
Message-ID: <1202273807.9259.0.camel@localhost.localdomain> (raw)
In-Reply-To: <20080205235344.GA2507@Chamillionaire.breakpoint.cc>
On Wed, 2008-02-06 at 00:53 +0100, Sebastian Siewior wrote:
> * Dan Williams | 2008-02-05 10:09:14 [-0500]:
>
> >That would mean that count never gets above 8, and that the RX queue is
> >never restocked. The (count >= 8) part might be specific to the
> >3945/4965 drivers, since they apparently restock the RX queue in blocks
> >of 8. Can you try to change the:
> >
> >if (count >= 8)
> >
> >to
> >
> >if (count)
> >
> >and see what that does for you? Also, can you log the value of
> >"ipw_rx_queue_space (priv->rxq)" on the same line as your "fill_rx
> >block" printk?
>
> This gives the following from time to time:
> | [ 3327.863414] fill_rx block, count: 0x00000000 i: 0x0000000e, ipw_rx_queue_space: 0x00000011
> | [ 3329.704780] fill_rx block, count: 0x00000000 i: 0x00000003, ipw_rx_queue_space: 0x00000011
> | [ 3331.532242] fill_rx block, count: 0x00000000 i: 0x0000001a, ipw_rx_queue_space: 0x00000011
> | [ 3333.306232] fill_rx block, count: 0x00000000 i: 0x00000009, ipw_rx_queue_space: 0x00000011
> | [ 3335.062033] fill_rx block, count: 0x00000000 i: 0x00000018, ipw_rx_queue_space: 0x00000011
> | [ 3336.983284] fill_rx block, count: 0x00000000 i: 0x0000000e, ipw_rx_queue_space: 0x00000011
> | [ 3338.792414] fill_rx block, count: 0x00000000 i: 0x00000005, ipw_rx_queue_space: 0x00000011
> | [ 3340.624946] fill_rx block, count: 0x00000000 i: 0x00000012, ipw_rx_queue_space: 0x00000011
> | [ 3343.179358] fill_rx block, count: 0x00000000 i: 0x00000015, ipw_rx_queue_space: 0x00000011
>
> and I had no firmware restart this time. It seems that it got fixed :)
> thx.
Ok, I'll prepare a final patch then.
Thanks,
Dan
next prev parent reply other threads:[~2008-02-06 4:57 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-26 13:29 ipw2200 stalls on high load Sebastian Siewior
2008-01-28 18:40 ` Chatre, Reinette
2008-01-30 22:57 ` Sebastian Siewior
2008-02-01 22:29 ` Chatre, Reinette
2008-02-04 12:37 ` Dan Williams
2008-02-04 18:23 ` Chatre, Reinette
2008-02-04 22:45 ` Sebastian Siewior
2008-02-04 23:24 ` Dan Williams
2008-02-05 8:35 ` Sebastian Siewior
2008-02-05 15:09 ` Dan Williams
2008-02-05 16:50 ` [Ipw2100-devel] " Cahill, Ben M
2008-02-05 23:53 ` Sebastian Siewior
2008-02-06 4:56 ` Dan Williams [this message]
2008-02-08 7:50 ` Sebastian Siewior
2008-01-28 18:53 ` [Ipw2100-devel] " Cahill, Ben M
2008-01-28 22:54 ` Sebastian Siewior
2008-01-30 22:48 ` Sebastian Siewior
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=1202273807.9259.0.camel@localhost.localdomain \
--to=dcbw@redhat.com \
--cc=ipw+2200@ml.breakpoint.cc \
--cc=ipw2100-devel@lists.sourceforge.net \
--cc=jketreno@linux.intel.com \
--cc=linux-wireless@vger.kernel.org \
--cc=reinette.chatre@intel.com \
--cc=yi.zhu@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