linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: reinette chatre <reinette.chatre@intel.com>
To: Marcel Holtmann <holtmann@linux.intel.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: Issue with ifconfig down and 4965 driver
Date: Thu, 04 Dec 2008 09:23:46 -0800	[thread overview]
Message-ID: <1228411426.28477.13.camel@rc-desk> (raw)
In-Reply-To: <1228389591.28839.1.camel@violet.holtmann.net>

On Thu, 2008-12-04 at 03:19 -0800, Marcel Holtmann wrote:
> Hi Reinette,
> 
> > > > > >> so I am running a 2.6.28-rc4 kernel and every time I stop
> > > > > >> wpa_supplicant or call ifconfig down on the 4965 card, I get a user
> > > > > >> noticeable delay (mouse freezes). Seems that some part inside the
> > > > > >> driver is actively sleeping with a busy-loop. This is really not an
> > > > > >> acceptable behavior since it is a day-to-day task to bring the device
> > > > > >> down. And for power concerns, we really wanna allow to bring down the
> > > > > >> interface.
> > > > > >>
> > > > > >
> > > > > > Please add your information to
> > > > > > http://www.intellinuxwireless.org/bugzilla/show_bug.cgi?id=1790
> > > > > 
> > > > > all information are already in the Bugzilla. It is nothing fancy and
> > > > > easy to reproduce. Do we have a patch for it?
> > > > > 
> > > > 
> > > > http://marc.info/?l=linux-wireless&m=122824886623698&w=2
> > > 
> > > so I finally got around testing the patch. It is great that it reduces
> > > the time drastically, but I think that it is still not good enough. So I
> > > don't care how long it takes to bring the device down. My concern is
> > > that we are busy-looping during this time. Meaning the kernel is not
> > > responding to anything. Simple symptom is that the mouse is stuck.
> > > 
> > 
> > We have found that this one patch is not the full solution. More work is
> > currently being done with activity tracked at
> > http://www.intellinuxwireless.org/bugzilla/show_bug.cgi?id=1790
> 
> I quickly checked Mohamed's last patch. It actually makes it worse on my
> system.

Thank you very much for testing - I will let him know. Would it be
possible to add your feedback to that bug report for visibility to
everybody tracking that problem? Not everybody there are subscribed to
linux-wireless and other people testing the patch (see last comment #12)
reports that the issue is solved for them.

Thank you very much

Reinette



      reply	other threads:[~2008-12-04 17:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-13  4:14 Issue with ifconfig down and 4965 driver Marcel Holtmann
2008-11-13  5:48 ` reinette chatre
2008-11-13  9:45   ` Marcel Holtmann
2008-12-02 20:27     ` reinette chatre
2008-12-03 23:38       ` Marcel Holtmann
2008-12-03 23:56         ` reinette chatre
2008-12-04 11:19           ` Marcel Holtmann
2008-12-04 17:23             ` reinette chatre [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=1228411426.28477.13.camel@rc-desk \
    --to=reinette.chatre@intel.com \
    --cc=holtmann@linux.intel.com \
    --cc=linux-wireless@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).