git top: 9135f1901ee6449dfe338adf6e40e9c2025b8150
[ 399.582185] wpa_supplicant[4383]: segfault at 30 ip 080697ca sp
bf87a690 error 4 in wpa_supplicant[8048000+4c000]
[ 406.277199] wpa_supplicant[4384]: segfault at 30 ip 080697ca sp
bfc13a30 error 4 in wpa_supplicant[8048000+4c000]
[ 407.586375] wpa_supplicant[4385]: segfault at 30 ip 080697ca sp
bf9ed000 error 4 in wpa_supplicant[8048000+4c000]
[ 411.671037] wpa_supplicant[4386]: segfault at 30 ip 080697ca sp
bf8f3710 error 4 in wpa_supplicant[8048000+4c000]
[ 412.569843] wpa_supplicant[4387]: segfault at 30 ip 080697ca sp
bfc19a30 error 4 in wpa_supplicant[8048000+4c000]
[ 413.118874] wpa_supplicant[4388]: segfault at 30 ip 080697ca sp
bfc9cab0 error 4 in wpa_supplicant[8048000+4c000]
home:~# wpa_supplicant -Dwext -iath0 -c /etc/wpa_supplicant/wpa_supplicant.conf
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 4 value 0x0 - bind(PF_UNIX): Address already in use
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.
Szegmens hiba
--
Thanks,
Oliver
On 02/04/2008 03:00 PM, Oliver Pinter (Pint?r Oliv?r) wrote:
> git top: 9135f1901ee6449dfe338adf6e40e9c2025b8150
>
> [ 399.582185] wpa_supplicant[4383]: segfault at 30 ip 080697ca sp
> bf87a690 error 4 in wpa_supplicant[8048000+4c000]
> [ 406.277199] wpa_supplicant[4384]: segfault at 30 ip 080697ca sp
> bfc13a30 error 4 in wpa_supplicant[8048000+4c000]
> [ 407.586375] wpa_supplicant[4385]: segfault at 30 ip 080697ca sp
> bf9ed000 error 4 in wpa_supplicant[8048000+4c000]
> [ 411.671037] wpa_supplicant[4386]: segfault at 30 ip 080697ca sp
> bf8f3710 error 4 in wpa_supplicant[8048000+4c000]
> [ 412.569843] wpa_supplicant[4387]: segfault at 30 ip 080697ca sp
> bfc19a30 error 4 in wpa_supplicant[8048000+4c000]
> [ 413.118874] wpa_supplicant[4388]: segfault at 30 ip 080697ca sp
> bfc9cab0 error 4 in wpa_supplicant[8048000+4c000]
Seems like wpa_supplicant is broken. Is this a regression?
> home:~# wpa_supplicant -Dwext -iath0 -c /etc/wpa_supplicant/wpa_supplicant.conf
ath0? udev renamed it?
> 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?
I guess ltrace would help here. And maybe strace...
On 2/4/08, Jiri Slaby <[email protected]> wrote:
> On 02/04/2008 03:00 PM, Oliver Pinter (Pint?r Oliv?r) wrote:
> > git top: 9135f1901ee6449dfe338adf6e40e9c2025b8150
> >
> > [ 399.582185] wpa_supplicant[4383]: segfault at 30 ip 080697ca sp
> > bf87a690 error 4 in wpa_supplicant[8048000+4c000]
> > [ 406.277199] wpa_supplicant[4384]: segfault at 30 ip 080697ca sp
> > bfc13a30 error 4 in wpa_supplicant[8048000+4c000]
> > [ 407.586375] wpa_supplicant[4385]: segfault at 30 ip 080697ca sp
> > bf9ed000 error 4 in wpa_supplicant[8048000+4c000]
> > [ 411.671037] wpa_supplicant[4386]: segfault at 30 ip 080697ca sp
> > bf8f3710 error 4 in wpa_supplicant[8048000+4c000]
> > [ 412.569843] wpa_supplicant[4387]: segfault at 30 ip 080697ca sp
> > bfc19a30 error 4 in wpa_supplicant[8048000+4c000]
> > [ 413.118874] wpa_supplicant[4388]: segfault at 30 ip 080697ca sp
> > bfc9cab0 error 4 in wpa_supplicant[8048000+4c000]
>
> Seems like wpa_supplicant is broken. Is this a regression?
yes, but with madwifi is all ok
>
> > home:~# wpa_supplicant -Dwext -iath0 -c
> /etc/wpa_supplicant/wpa_supplicant.conf
>
> ath0? udev renamed it?
yes
>
> > 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
>
> I guess ltrace would help here. And maybe strace...
>
strace attached and wpa_supplicant more verbose output
--
Thanks,
Oliver
On 2/4/08, Oliver Pinter <[email protected]> wrote:
> On 2/4/08, Jiri Slaby <[email protected]> wrote:
> > On 02/04/2008 03:00 PM, Oliver Pinter (Pint?r Oliv?r) wrote:
> > > git top: 9135f1901ee6449dfe338adf6e40e9c2025b8150
> > >
> > > [ 399.582185] wpa_supplicant[4383]: segfault at 30 ip 080697ca sp
> > > bf87a690 error 4 in wpa_supplicant[8048000+4c000]
> > > [ 406.277199] wpa_supplicant[4384]: segfault at 30 ip 080697ca sp
> > > bfc13a30 error 4 in wpa_supplicant[8048000+4c000]
> > > [ 407.586375] wpa_supplicant[4385]: segfault at 30 ip 080697ca sp
> > > bf9ed000 error 4 in wpa_supplicant[8048000+4c000]
> > > [ 411.671037] wpa_supplicant[4386]: segfault at 30 ip 080697ca sp
> > > bf8f3710 error 4 in wpa_supplicant[8048000+4c000]
> > > [ 412.569843] wpa_supplicant[4387]: segfault at 30 ip 080697ca sp
> > > bfc19a30 error 4 in wpa_supplicant[8048000+4c000]
> > > [ 413.118874] wpa_supplicant[4388]: segfault at 30 ip 080697ca sp
> > > bfc9cab0 error 4 in wpa_supplicant[8048000+4c000]
> >
> > Seems like wpa_supplicant is broken. Is this a regression?
>
> yes, but with madwifi is all ok
> >
> > > home:~# wpa_supplicant -Dwext -iath0 -c
> > /etc/wpa_supplicant/wpa_supplicant.conf
> >
> > ath0? udev renamed it?
>
> yes
> >
> > > 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
> >
> > I guess ltrace would help here. And maybe strace...
> >
>
> strace attached and wpa_supplicant more verbose output
> --
> Thanks,
> Oliver
>
02:01.0 Ethernet controller: Atheros Communications, Inc. AR5212
802.11abg NIC (rev 01)
Subsystem: D-Link System Inc D-Link AirPlus DWL-G520 Wireless
PCI Adapter(rev.B)
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium
>TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 168 (2500ns min, 7000ns max), Cache Line Size: 32 bytes
Interrupt: pin A routed to IRQ 18
Region 0: Memory at e4000000 (32-bit, non-prefetchable) [size=64K]
Capabilities: [44] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=2 PME-
02:01.0 Ethernet controller: Atheros Communications, Inc. AR5212
802.11abg NIC (rev 01)
00: 8c 16 13 00 06 00 90 02 01 00 00 02 08 a8 00 00
10: 00 00 00 e4 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 01 50 00 00 86 11 13 3a
30: 00 00 00 00 44 00 00 00 00 00 00 00 0b 01 0a 1c
40: 00 00 00 00 01 00 c2 01 00 40 00 c6 00 00 00 00
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
--
Thanks,
Oliver
On Mon, 2008-02-04 at 22:34 +0100, Oliver Pinter wrote:
> On 2/4/08, Jiri Slaby <[email protected]> wrote:
> > On 02/04/2008 03:00 PM, Oliver Pinter (Pintér Olivér) wrote:
> > > git top: 9135f1901ee6449dfe338adf6e40e9c2025b8150
> > >
> > > [ 399.582185] wpa_supplicant[4383]: segfault at 30 ip 080697ca sp
> > > bf87a690 error 4 in wpa_supplicant[8048000+4c000]
> > > [ 406.277199] wpa_supplicant[4384]: segfault at 30 ip 080697ca sp
> > > bfc13a30 error 4 in wpa_supplicant[8048000+4c000]
> > > [ 407.586375] wpa_supplicant[4385]: segfault at 30 ip 080697ca sp
> > > bf9ed000 error 4 in wpa_supplicant[8048000+4c000]
> > > [ 411.671037] wpa_supplicant[4386]: segfault at 30 ip 080697ca sp
> > > bf8f3710 error 4 in wpa_supplicant[8048000+4c000]
> > > [ 412.569843] wpa_supplicant[4387]: segfault at 30 ip 080697ca sp
> > > bfc19a30 error 4 in wpa_supplicant[8048000+4c000]
> > > [ 413.118874] wpa_supplicant[4388]: segfault at 30 ip 080697ca sp
> > > bfc9cab0 error 4 in wpa_supplicant[8048000+4c000]
> >
> > Seems like wpa_supplicant is broken. Is this a regression?
>
> yes, but with madwifi is all ok
> >
> > > home:~# wpa_supplicant -Dwext -iath0 -c
> > /etc/wpa_supplicant/wpa_supplicant.conf
> >
> > ath0? udev renamed it?
>
> yes
> >
> > > 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
> >
> > I guess ltrace would help here. And maybe strace...
> >
>
> strace attached and wpa_supplicant more verbose output
It doesn't look like the driver is returning _any_ scan results. What
does '/sbin/iwlist wlan0 scan' show from the command line. If the
driver isn't returning scan results to the supplicant, there's not much
the supplicant can do. You may need to ensure the interface is up
before scanning.
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.
Dan
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 <[email protected]> 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.
On 02/04/2008 10:40 PM, Oliver Pinter wrote:
> On 2/4/08, Oliver Pinter <[email protected]> wrote:
>> On 2/4/08, Jiri Slaby <[email protected]> wrote:
>>> On 02/04/2008 03:00 PM, Oliver Pinter (Pint?r Oliv?r) wrote:
>>>> [ 413.118874] wpa_supplicant[4388]: segfault at 30 ip 080697ca sp
>>>> bfc9cab0 error 4 in wpa_supplicant[8048000+4c000]
>>> Seems like wpa_supplicant is broken. Is this a regression?
>> yes, but with madwifi is all ok
And this... madwifi goes through ported bsd net80211. So which latest git you
tried worked for you when this is a regression, please?