From: Dan Williams <dcbw@redhat.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Jean Tourrilhes <jt@hpl.hp.com>, Jouni Malinen <j@w1.fi>,
linux-wireless@vger.kernel.org
Subject: Re: wext 64-bit: network manager and wpa_supplicant
Date: Thu, 20 Sep 2007 11:50:33 -0400 [thread overview]
Message-ID: <1190303433.2016.10.camel@xo-3E-67-34.localdomain> (raw)
In-Reply-To: <1190292526.18521.52.camel@johannes.berg>
On Thu, 2007-09-20 at 14:48 +0200, Johannes Berg wrote:
> Ahrg. So I was complaining about NM not displaying any networks when
> that umlaut-network I talked about earlier was present. But all that was
> just wrong, the real problem seems to be that NM doesn't work on 64-bit
> platforms. Is there any fix for it? It really should be going into a
> 0.6.5.1 version or something so distributions will ship it.
You mean it doesn't work correctly when handling ioctls on 64-bit
platforms? Or is just plain broken in non-ioctl ways?
Dan
> Same seems to go for wpa_supplicant, Debian is shipping 0.6.0 which only
> triggers this in the kernel log:
>
> [ 787.877417] ioctl32(wpa_supplicant:5846): Unknown cmd fd(3) cmd(00008b32){t:8b;sz:0} arg(ffb58418) on socket:[14569]
> [ 787.877763] ioctl32(wpa_supplicant:5846): Unknown cmd fd(3) cmd(00008b32){t:8b;sz:0} arg(ffb58418) on socket:[14569]
> [ 787.877817] ioctl32(wpa_supplicant:5846): Unknown cmd fd(3) cmd(00008b32){t:8b;sz:0} arg(ffb58418) on socket:[14569]
> [ 795.264145] ioctl32(wpa_supplicant:5846): Unknown cmd fd(3) cmd(00008b32){t:8b;sz:0} arg(ffb58458) on socket:[14569]
> [ 795.264243] ioctl32(wpa_supplicant:5846): Unknown cmd fd(3) cmd(00008b32){t:8b;sz:0} arg(ffb58458) on socket:[14569]
> [ 795.264291] ioctl32(wpa_supplicant:5846): Unknown cmd fd(3) cmd(00008b32){t:8b;sz:0} arg(ffb58458) on socket:[14569]
>
> And even the wpa_supplicant git version still seems to parse everything
> itself without any 64-bit workarounds as far as I can tell. I keep
> building wpa_supplicant for 64-bit just to test... Any chance to finally
> get fixes into the stable versions distros are shipping?
>
> Thanks,
> johannes
next prev parent reply other threads:[~2007-09-20 15:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-20 12:48 wext 64-bit: network manager and wpa_supplicant Johannes Berg
2007-09-20 15:50 ` Dan Williams [this message]
2007-09-20 16:16 ` Johannes Berg
2007-09-20 16:55 ` Jean Tourrilhes
2007-09-20 17:01 ` Johannes Berg
2007-09-20 20:56 ` Jean Tourrilhes
2007-09-21 14:36 ` Johannes Berg
2007-09-26 23:51 ` Jean Tourrilhes
2007-09-27 7:31 ` Johannes Berg
2007-10-09 9:15 ` Johannes Berg
2007-10-10 2:20 ` Jouni Malinen
2007-10-10 8:46 ` Johannes Berg
2007-10-10 19:21 ` Jean Tourrilhes
2007-10-01 14:18 ` Dan Williams
2007-10-01 18:18 ` Jean Tourrilhes
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=1190303433.2016.10.camel@xo-3E-67-34.localdomain \
--to=dcbw@redhat.com \
--cc=j@w1.fi \
--cc=johannes@sipsolutions.net \
--cc=jt@hpl.hp.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