From: Robert Hancock <hancockr@shaw.ca>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.28-rc3 (x86_64) on current Fedora 9 (i386)
Date: Sat, 08 Nov 2008 14:48:46 -0600 [thread overview]
Message-ID: <4915FB2E.7020206@shaw.ca> (raw)
In-Reply-To: <1226157728.6060.7.camel@dhcppc0>
Thomas Meyer wrote:
> Hi,
>
> Cross compiled with gcc-4.2.4.
>
> nm-applet seems to constantly fail to connect my wlan:
>
> [ 415.702723] rndis_wlan 1-6.3:1.0: rndis media connect
> [ 415.731909] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
> [ 415.732700] wpa_supplicant[3416]: segfault at fff40000 ip 000000004f612fd6 sp 00000000fff3c108 error 4 in libc-2.8.so[4f59c000+163000]
> [ 415.749491] rndis_wlan 1-6.3:1.0: rndis media disconnect
> [ 426.664267] wlan0: no IPv6 routers present
> [ 431.701722] rndis_wlan 1-6.3:1.0: rndis media connect
> [ 431.726008] wpa_supplicant[4055]: segfault at ffcc9000 ip 000000004f612fd6 sp 00000000ffcc6698 error 4 in libc-2.8.so[4f59c000+163000]
> [ 431.740094] rndis_wlan 1-6.3:1.0: rndis media disconnect
> [ 437.705723] rndis_wlan 1-6.3:1.0: rndis media connect
> [ 437.735135] wpa_supplicant[4160]: segfault at ffd88000 ip 000000004f612fd6 sp 00000000ffd83b98 error 4 in libc-2.8.so[4f59c000+163000]
> [ 437.754987] rndis_wlan 1-6.3:1.0: rndis media disconnect
> [ 443.705723] rndis_wlan 1-6.3:1.0: rndis media connect
> [ 443.735113] wpa_supplicant[4167]: segfault at fffa7000 ip 000000004f612fd6 sp 00000000fffa4978 error 4 in libc-2.8.so[4f59c000+163000]
> [ 443.751981] rndis_wlan 1-6.3:1.0: rndis media disconnect
> [ 459.705722] rndis_wlan 1-6.3:1.0: rndis media connect
> [ 459.736240] wpa_supplicant[4173]: segfault at ffe7d000 ip 000000004f612fd6 sp 00000000ffe7a048 error 4 in libc-2.8.so[4f59c000+163000]
> [ 459.750979] rndis_wlan 1-6.3:1.0: rndis media disconnect
>
> The same kernel not cross compiled (with the supplied Fedora gcc) works correctly with the nm-applet...
>
> Kernel or user land bug?
>
> Also I get this strange error messages:
> [ 23.767645] ioctl32(rhgb:2177): Unknown cmd fd(13) cmd(0000530b){t:'S';sz:0} arg(4eed91aa) on /dev/pts/0
> [ 23.767652] ioctl32(rhgb:2177): Unknown cmd fd(13) cmd(0000530b){t:'S';sz:0} arg(4eed91af) on /dev/pts/0
> [ 23.767657] ioctl32(rhgb:2177): Unknown cmd fd(13) cmd(0000530b){t:'S';sz:0} arg(4eed91b6) on /dev/pts/0
>
> [ 46.273767] ioctl32(hald-probe-stor:2750): Unknown cmd fd(4) cmd(00005320){t:'S';sz:0} arg(00000004) on /dev/sr0
>
> [ 525.336420] ioctl32(gnome-terminal:4419): Unknown cmd fd(20) cmd(0000530b){t:'S';sz:0} arg(4eed91aa) on /dev/pts/1
> [ 525.336427] ioctl32(gnome-terminal:4419): Unknown cmd fd(20) cmd(0000530b){t:'S';sz:0} arg(4eed91af) on /dev/pts/1
> [ 525.336432] ioctl32(gnome-terminal:4419): Unknown cmd fd(20) cmd(0000530b){t:'S';sz:0} arg(4eed91b6) on /dev/pts/1
>
> Should I care about these messages?
Those ones are 32-bit processes doing ioctls which don't have
compat_ioctl handling in the kernel, which would be needed for them to
work on a 64-bit kernel.
prev parent reply other threads:[~2008-11-08 21:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-08 15:22 2.6.28-rc3 (x86_64) on current Fedora 9 (i386) Thomas Meyer
2008-11-08 15:32 ` Arjan van de Ven
2008-11-09 14:36 ` Thomas Meyer
2008-11-08 20:48 ` Robert Hancock [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=4915FB2E.7020206@shaw.ca \
--to=hancockr@shaw.ca \
--cc=linux-kernel@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