From: Jiri Slaby <jirislaby@gmail.com>
To: Dan Williams <dcbw@redhat.com>
Cc: Oliver Pinter <oliver.pntr@gmail.com>,
"John W. Linville" <linville@tuxdriver.com>,
Bruno Randolf <bruno@thinktube.com>,
netdev <netdev@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
ath5k-devel@lists.ath5k.org
Subject: Re: [Wireless, ath5k] 2.6.24-git13 9135f1901ee6449dfe338adf6e40e9c2025b8150
Date: Mon, 04 Feb 2008 23:36:28 +0100 [thread overview]
Message-ID: <47A7936C.9090103@gmail.com> (raw)
In-Reply-To: <1202161934.24527.5.camel@localhost.localdomain>
On 02/04/2008 10:52 PM, Dan Williams wrote:
> On Mon, 2008-02-04 at 22:34 +0100, Oliver Pinter wrote:
>> On 2/4/08, Jiri Slaby <jirislaby@gmail.com> wrote:
>>> On 02/04/2008 03:00 PM, Oliver Pinter (Pintér Olivér) wrote:
>>>> ioctl[SIOCSIWAUTH]: Operation not supported
>>>> WEXT auth param 4 value 0x0 - bind(PF_UNIX): Address already in use
>>> 4 - 0x0 is TKIP, nothing we should worry about.
>>>
>>>> ctrl_iface exists and seems to be in use - cannot override it
>>>> Delete '/var/run/wpa_supplicant/ath0' manually if it is not used anymore
>>>> Failed to initialize control interface '/var/run/wpa_supplicant'.
>>>> You may have another wpa_supplicant process already running or the file
>>> was
>>>> left by an unclean termination of wpa_supplicant in which case you will
>>> need
>>>> to manually remove this file before starting wpa_supplicant again.
>>> Have you?
>> yes
Ok, on one log it can't be bound and connected to, on the others it can be
bound. I think you have 2 wpa/NM/whatever processes there which try to assign.
> Note that the specific behavior of the process requesting scan results
> can sometimes interact badly with the driver. The driver most likely
> needs to cope with this (by caching the BSS list internally for example)
> and handle whatever behavior userspace programs throw at it.
The driver doesn't cope with scanning at all. It doesn't support passive scans.
It's a mac layer who scans (sends probe request for each channel and listens for
probe response for a while) here.
The scan results as Dan mentioned will be appreciated.
prev parent reply other threads:[~2008-02-04 22:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-04 14:00 [Wireless, ath5k] 2.6.24-git13 9135f1901ee6449dfe338adf6e40e9c2025b8150 Oliver Pinter (Pintér Olivér)
2008-02-04 20:25 ` Jiri Slaby
2008-02-04 20:25 ` Jiri Slaby
2008-02-04 21:34 ` Oliver Pinter
2008-02-04 21:40 ` Oliver Pinter
2008-02-04 21:40 ` Oliver Pinter
2008-02-05 8:54 ` Jiri Slaby
2008-02-05 8:54 ` Jiri Slaby
2008-02-04 21:52 ` Dan Williams
2008-02-04 21:52 ` Dan Williams
2008-02-04 22:36 ` Jiri Slaby [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=47A7936C.9090103@gmail.com \
--to=jirislaby@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=ath5k-devel@lists.ath5k.org \
--cc=bruno@thinktube.com \
--cc=dcbw@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
--cc=oliver.pntr@gmail.com \
--cc=torvalds@linux-foundation.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 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.