linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ivo van Doorn <ivdoorn@gmail.com>
To: Bas Hulsken <bhulsken@hotmail.com>
Cc: linux-wireless@vger.kernel.org,
	Johannes Berg <johannes@sipsolutions.net>
Subject: Re: hostapd hangs on rt2500pci, leaving the nic in an unstable state
Date: Thu, 10 Apr 2008 18:59:49 +0200	[thread overview]
Message-ID: <200804101859.50470.IvDoorn@gmail.com> (raw)
In-Reply-To: <1207845596.2907.2.camel@Bas>

On Thursday 10 April 2008, Bas Hulsken wrote:
> Hi,
> 
> On Wed, 2008-04-09 at 19:33 +0200, Ivo van Doorn wrote:
> 
> > > Does the patch by Daniel Wagner:
> > > 	rt61pci: rt61pci_beacon_update do not free skb twice
> > > which was send to the linux-wireless mailing list today help?
> > 
> > wait never mind, that was a stupid comment since you are using rt2500pci... :S
> > I'll see if the patch also is applicable for rt2500pci and post that patch if that is
> > the case. :)
> 
> I assume the patch as it applies to rt2500pci is this one: "rt2x00: Only
> free skb when beacon_update fails"

Not really, it was something I found while looking through the beaconing code,
the rt61pci was indeed something that only was bugged in rt61pci, the other
drivers did the beacon handling correctly.

> I've tried it, and it does not solve the problem, still exactly the same
> hang as before.

I expected as much, I'm still looking into other causes for this bug.

Ivo

      reply	other threads:[~2008-04-10 16:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-05 16:22 hostapd hangs on rt2500pci, leaving the nic in an unstable state Bas Hulsken
2008-04-05 17:46 ` Ivo van Doorn
2008-04-06 12:52   ` Bas Hulsken
2008-04-06 15:08     ` Ivo van Doorn
2008-04-07 17:47       ` Bas Hulsken
2008-04-09 17:32         ` Ivo van Doorn
2008-04-09 17:33           ` Ivo van Doorn
2008-04-10 16:39             ` Bas Hulsken
2008-04-10 16:59               ` Ivo van Doorn [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=200804101859.50470.IvDoorn@gmail.com \
    --to=ivdoorn@gmail.com \
    --cc=bhulsken@hotmail.com \
    --cc=johannes@sipsolutions.net \
    --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).