Re: NetworkManager from fedora-updates-testing broken on F11-XO1
On Thu, 2010-02-25 at 16:58 -0800, Dan Williams wrote: Hmm, doesn't ring a bell immediately. I pushed a fix for the driver thing and am doing another NM build for F11. I'll try to take a look at this after the new build goes through. Even when using the latest build from koji [*], NetworkManager still crashes on resume from suspend. [*] http://koji.fedoraproject.org/koji/buildinfo?buildID=158720 -- // Bernie Innocenti - http://codewiz.org/ \X/ Sugar Labs - http://sugarlabs.org/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: NetworkManager from fedora-updates-testing broken on F11-XO1
On Thu, 2010-02-25 at 14:11 -0300, Bernie Innocenti wrote:
Feb 25 17:01:30 xo-37-38-0f NetworkManager: *** START
**
Feb 25 17:01:30 xo-37-38-0f NetworkManager: Frame 0:
NetworkManager(nm_logging_backtrace+0x45) [0x8078da5]
Feb 25 17:01:30 xo-37-38-0f NetworkManager: Frame 1: NetworkManager
[0x8072f4d]
Feb 25 17:01:30 xo-37-38-0f NetworkManager: Frame 2: [0xb77c6400]
Feb 25 17:01:30 xo-37-38-0f NetworkManager: Frame 3: NetworkManager
[0x8067a5b]
Feb 25 17:01:30 xo-37-38-0f NetworkManager: Frame 4:
/lib/libgobject-2.0.so.0(g_cclosure_marshal_VOID__OBJECT+0x88) [0x93f338]
Feb 25 17:01:30 xo-37-38-0f NetworkManager: Frame 5:
/lib/libgobject-2.0.so.0(g_closure_invoke+0x1b2) [0x932352]
Feb 25 17:01:30 xo-37-38-0f NetworkManager: Frame 6: /lib/libgobject-2.0.so.0
[0x947cf0]
Feb 25 17:01:30 xo-37-38-0f NetworkManager: Frame 7:
/lib/libgobject-2.0.so.0(g_signal_emit_valist+0x7bd) [0x94905d]
Feb 25 17:01:30 xo-37-38-0f NetworkManager: Frame 8:
/lib/libgobject-2.0.so.0(g_signal_emit+0x26) [0x9494e6]
Feb 25 17:01:30 xo-37-38-0f NetworkManager: Frame 9:
NetworkManager(_nm_marshal_VOID__STRING_STRING_POINTER_POINTER+0x9d)
[0x808ab1d]
Feb 25 17:01:30 xo-37-38-0f NetworkManager: Frame 10:
/lib/libgobject-2.0.so.0(g_closure_invoke+0x1b2) [0x932352]
Feb 25 17:01:30 xo-37-38-0f NetworkManager: Frame 11:
/lib/libgobject-2.0.so.0 [0x947cf0]
Feb 25 17:01:30 xo-37-38-0f NetworkManager: Frame 12:
/lib/libgobject-2.0.so.0(g_signal_emit_valist+0x7bd) [0x94905d]
Feb 25 17:01:30 xo-37-38-0f NetworkManager: Frame 13:
/lib/libgobject-2.0.so.0(g_signal_emit+0x26) [0x9494e6]
Feb 25 17:01:30 xo-37-38-0f NetworkManager: Frame 14: NetworkManager
[0x806df19]
Feb 25 17:01:30 xo-37-38-0f NetworkManager: Frame 15: /usr/lib/libhal.so.1
[0x71bc3e3]
Feb 25 17:01:30 xo-37-38-0f NetworkManager: Frame 16:
/lib/libdbus-1.so.3(dbus_connection_dispatch+0x36d) [0x703287d]
Feb 25 17:01:30 xo-37-38-0f NetworkManager: Frame 17:
/usr/lib/libdbus-glib-1.so.2 [0x71ca19d]
Feb 25 17:01:30 xo-37-38-0f NetworkManager: Frame 18:
/lib/libglib-2.0.so.0(g_main_context_dispatch+0x1f8) [0x852308]
Feb 25 17:01:30 xo-37-38-0f NetworkManager: Frame 19: /lib/libglib-2.0.so.0
[0x8559e0]
Feb 25 17:01:30 xo-37-38-0f NetworkManager: Frame 20:
/lib/libglib-2.0.so.0(g_main_loop_run+0x1bf) [0x855e4f]
Feb 25 17:01:30 xo-37-38-0f NetworkManager: Frame 21:
NetworkManager(main+0xe37) [0x8073d97]
Feb 25 17:01:30 xo-37-38-0f NetworkManager: Frame 22:
/lib/libc.so.6(__libc_start_main+0xe6) [0x673a86]
Feb 25 17:01:30 xo-37-38-0f NetworkManager: Frame 23: NetworkManager
[0x80570d1]
Feb 25 17:01:30 xo-37-38-0f NetworkManager: *** END
**
Feb 25 17:02:14 xo-37-38-0f kernel: [ 3523.422953] psmouse serio1: detected
37px jump in x
Ok, I traced it down to ./src/nm-device-olpc-mesh.c:is_companion(), at
the memcmp() line.
their_addr is on the stack, so the invalid pointer must be priv. I can't
debub further without rebuilding the rpm with -g. Any idea what might
have gone wrong here?
static gboolean
is_companion (NMDeviceOlpcMesh *self, NMDevice *other)
{
NMDeviceOlpcMeshPrivate *priv = NM_DEVICE_OLPC_MESH_GET_PRIVATE
(self);
struct ether_addr their_addr;
if (!NM_IS_DEVICE_WIFI (other))
return FALSE;
nm_device_wifi_get_address (NM_DEVICE_WIFI (other), their_addr);
if (memcmp (priv-hw_addr.ether_addr_octet,
their_addr.ether_addr_octet, ETH_ALEN) != 0) {
return FALSE;
}
--
// Bernie Innocenti - http://codewiz.org/
\X/ Sugar Labs - http://sugarlabs.org/
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
Re: NetworkManager from fedora-updates-testing broken on F11-XO1
On Thu, 2010-02-25 at 21:38 -0300, Bernie Innocenti wrote:
On Thu, 2010-02-25 at 14:11 -0300, Bernie Innocenti wrote:
Feb 25 17:01:30 xo-37-38-0f NetworkManager: *** START
**
Feb 25 17:01:30 xo-37-38-0f NetworkManager: Frame 0:
NetworkManager(nm_logging_backtrace+0x45) [0x8078da5]
Feb 25 17:01:30 xo-37-38-0f NetworkManager: Frame 1: NetworkManager
[0x8072f4d]
Feb 25 17:01:30 xo-37-38-0f NetworkManager: Frame 2: [0xb77c6400]
Feb 25 17:01:30 xo-37-38-0f NetworkManager: Frame 3: NetworkManager
[0x8067a5b]
Feb 25 17:01:30 xo-37-38-0f NetworkManager: Frame 4:
/lib/libgobject-2.0.so.0(g_cclosure_marshal_VOID__OBJECT+0x88) [0x93f338]
Feb 25 17:01:30 xo-37-38-0f NetworkManager: Frame 5:
/lib/libgobject-2.0.so.0(g_closure_invoke+0x1b2) [0x932352]
Feb 25 17:01:30 xo-37-38-0f NetworkManager: Frame 6:
/lib/libgobject-2.0.so.0 [0x947cf0]
Feb 25 17:01:30 xo-37-38-0f NetworkManager: Frame 7:
/lib/libgobject-2.0.so.0(g_signal_emit_valist+0x7bd) [0x94905d]
Feb 25 17:01:30 xo-37-38-0f NetworkManager: Frame 8:
/lib/libgobject-2.0.so.0(g_signal_emit+0x26) [0x9494e6]
Feb 25 17:01:30 xo-37-38-0f NetworkManager: Frame 9:
NetworkManager(_nm_marshal_VOID__STRING_STRING_POINTER_POINTER+0x9d)
[0x808ab1d]
Feb 25 17:01:30 xo-37-38-0f NetworkManager: Frame 10:
/lib/libgobject-2.0.so.0(g_closure_invoke+0x1b2) [0x932352]
Feb 25 17:01:30 xo-37-38-0f NetworkManager: Frame 11:
/lib/libgobject-2.0.so.0 [0x947cf0]
Feb 25 17:01:30 xo-37-38-0f NetworkManager: Frame 12:
/lib/libgobject-2.0.so.0(g_signal_emit_valist+0x7bd) [0x94905d]
Feb 25 17:01:30 xo-37-38-0f NetworkManager: Frame 13:
/lib/libgobject-2.0.so.0(g_signal_emit+0x26) [0x9494e6]
Feb 25 17:01:30 xo-37-38-0f NetworkManager: Frame 14: NetworkManager
[0x806df19]
Feb 25 17:01:30 xo-37-38-0f NetworkManager: Frame 15: /usr/lib/libhal.so.1
[0x71bc3e3]
Feb 25 17:01:30 xo-37-38-0f NetworkManager: Frame 16:
/lib/libdbus-1.so.3(dbus_connection_dispatch+0x36d) [0x703287d]
Feb 25 17:01:30 xo-37-38-0f NetworkManager: Frame 17:
/usr/lib/libdbus-glib-1.so.2 [0x71ca19d]
Feb 25 17:01:30 xo-37-38-0f NetworkManager: Frame 18:
/lib/libglib-2.0.so.0(g_main_context_dispatch+0x1f8) [0x852308]
Feb 25 17:01:30 xo-37-38-0f NetworkManager: Frame 19: /lib/libglib-2.0.so.0
[0x8559e0]
Feb 25 17:01:30 xo-37-38-0f NetworkManager: Frame 20:
/lib/libglib-2.0.so.0(g_main_loop_run+0x1bf) [0x855e4f]
Feb 25 17:01:30 xo-37-38-0f NetworkManager: Frame 21:
NetworkManager(main+0xe37) [0x8073d97]
Feb 25 17:01:30 xo-37-38-0f NetworkManager: Frame 22:
/lib/libc.so.6(__libc_start_main+0xe6) [0x673a86]
Feb 25 17:01:30 xo-37-38-0f NetworkManager: Frame 23: NetworkManager
[0x80570d1]
Feb 25 17:01:30 xo-37-38-0f NetworkManager: *** END
**
Feb 25 17:02:14 xo-37-38-0f kernel: [ 3523.422953] psmouse serio1: detected
37px jump in x
Ok, I traced it down to ./src/nm-device-olpc-mesh.c:is_companion(), at
the memcmp() line.
their_addr is on the stack, so the invalid pointer must be priv. I can't
debub further without rebuilding the rpm with -g. Any idea what might
have gone wrong here?
static gboolean
is_companion (NMDeviceOlpcMesh *self, NMDevice *other)
{
NMDeviceOlpcMeshPrivate *priv = NM_DEVICE_OLPC_MESH_GET_PRIVATE
(self);
struct ether_addr their_addr;
if (!NM_IS_DEVICE_WIFI (other))
return FALSE;
nm_device_wifi_get_address (NM_DEVICE_WIFI (other), their_addr);
if (memcmp (priv-hw_addr.ether_addr_octet,
their_addr.ether_addr_octet, ETH_ALEN) != 0) {
return FALSE;
}
Hmm, doesn't ring a bell immediately. I pushed a fix for the driver
thing and am doing another NM build for F11. I'll try to take a look at
this after the new build goes through.
Dan
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
Re: NetworkManager from fedora-updates-testing broken on F11-XO1
On Thu, 2010-02-18 at 09:55 -0800, Dan Williams wrote:
It'll probably take more investigation than I have time for this week,
so I'll just patch NM to accept the invalid driver name ('usb') as a
fallback. Which is the behavior that 0.7.2 had anyway, so you can
consider it a regression in 0.7.2.995. We'll eventually fix libertas
but I don't think we should block this on a libertas fix.
Can you please build a new NetworkManager package in F11 with this
work-around applied?
--
// Bernie Innocenti - http://codewiz.org/
\X/ Sugar Labs - http://sugarlabs.org/
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
Re: NetworkManager from fedora-updates-testing broken on F11-XO1
On Mon, 2010-02-22 at 12:08 -0300, Bernie Innocenti wrote:
On Thu, 2010-02-18 at 09:55 -0800, Dan Williams wrote:
It'll probably take more investigation than I have time for this week,
so I'll just patch NM to accept the invalid driver name ('usb') as a
fallback. Which is the behavior that 0.7.2 had anyway, so you can
consider it a regression in 0.7.2.995. We'll eventually fix libertas
but I don't think we should block this on a libertas fix.
Can you please build a new NetworkManager package in F11 with this
work-around applied?
I've scratch-built custom rpms with a crude patch of mine which seems to
fix the issue:
http://koji.fedoraproject.org/koji/taskinfo?taskID=2006014
diff --git a/src/nm-device-olpc-mesh.c b/src/nm-device-olpc-mesh.c
index edbba81..8554b95 100644
--- a/src/nm-device-olpc-mesh.c
+++ b/src/nm-device-olpc-mesh.c
@@ -935,12 +935,11 @@ nm_device_olpc_mesh_new (const char *udi,
g_return_val_if_fail (udi != NULL, NULL);
g_return_val_if_fail (iface != NULL, NULL);
- g_return_val_if_fail (driver != NULL, NULL);
obj = g_object_new (NM_TYPE_DEVICE_OLPC_MESH,
NM_DEVICE_INTERFACE_UDI, udi,
NM_DEVICE_INTERFACE_IFACE, iface,
- NM_DEVICE_INTERFACE_DRIVER, driver,
+ NM_DEVICE_INTERFACE_DRIVER, driver ? driver : usb,
NM_DEVICE_INTERFACE_MANAGED, managed,
NULL);
if (obj == NULL)
diff --git a/src/nm-device-wifi.c b/src/nm-device-wifi.c
index fdc6f78..53dcd59 100644
--- a/src/nm-device-wifi.c
+++ b/src/nm-device-wifi.c
@@ -3546,12 +3546,11 @@ nm_device_wifi_new (const char *udi,
g_return_val_if_fail (udi != NULL, NULL);
g_return_val_if_fail (iface != NULL, NULL);
- g_return_val_if_fail (driver != NULL, NULL);
obj = g_object_new (NM_TYPE_DEVICE_WIFI,
NM_DEVICE_INTERFACE_UDI, udi,
NM_DEVICE_INTERFACE_IFACE, iface,
- NM_DEVICE_INTERFACE_DRIVER, driver,
+ NM_DEVICE_INTERFACE_DRIVER, driver ? driver : usb,
NM_DEVICE_INTERFACE_MANAGED, managed,
NULL);
if (obj == NULL)
--
// Bernie Innocenti - http://codewiz.org/
\X/ Sugar Labs - http://sugarlabs.org/
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
Re: NetworkManager from fedora-updates-testing broken on F11-XO1
On Wed, 2010-02-17 at 22:44 -0300, Bernie Innocenti wrote:
On Wed, 2010-02-17 at 11:08 -0800, Dan Williams wrote:
On Wed, 2010-02-17 at 10:20 -0300, Bernie Innocenti wrote:
On Mon, 2010-02-15 at 16:15 -0800, Dan Williams wrote:
Not a known issue; but I'll try to reproduce on mine. Unless Daniel
gets there first of course.
I retrieved the log:
I was able to reproduce the issue as well. The problem is that the
libertas driver isn't correctly showing the 'driver' link in sysfs, it's
showing it as 'usb' which is wrong... we may just work around that in
NM, but Id like to figure out why libertas is screwing this up on
F11/F12 first.
Thanks for analyzing this.
As soon as you have a patch, I'd like to test it in my local olpc-2.6
kernel builds.
It'll probably take more investigation than I have time for this week,
so I'll just patch NM to accept the invalid driver name ('usb') as a
fallback. Which is the behavior that 0.7.2 had anyway, so you can
consider it a regression in 0.7.2.995. We'll eventually fix libertas
but I don't think we should block this on a libertas fix.
Dan
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
Re: NetworkManager from fedora-updates-testing broken on F11-XO1
On Mon, 2010-02-15 at 16:15 -0800, Dan Williams wrote: Not a known issue; but I'll try to reproduce on mine. Unless Daniel gets there first of course. I retrieved the log: Feb 17 13:12:29 xo-58-2d-7a kernel: [ 1395.246555] usb 2-4: reset high speed USB device using ehci_hcd and address 11 Feb 17 13:12:29 xo-58-2d-7a kernel: [ 1395.513595] usb 2-1: reset high speed USB device using ehci_hcd and address 15 Feb 17 13:12:29 xo-58-2d-7a kernel: [ 1395.668902] libertas: Not issuing HOST_SLEEP_CFG on XO-1 Feb 17 13:12:29 xo-58-2d-7a kernel: [ 1395.669103] Restarting tasks ... Feb 17 13:12:29 xo-58-2d-7a kernel: [ 1395.674647] ADDRCONF(NETDEV_UP): eth0: link is not ready Feb 17 13:12:29 xo-58-2d-7a NetworkManager: info (eth0): device state change: 1 - 2 (reason 2) Feb 17 13:12:29 xo-58-2d-7a NetworkManager: info (eth0): bringing up device. Feb 17 13:12:29 xo-58-2d-7a NetworkManager: info (eth0): preparing device. Feb 17 13:12:29 xo-58-2d-7a NetworkManager: info (eth0): deactivating device (reason: 2). Feb 17 13:12:29 xo-58-2d-7a NetworkManager: info (eth0): supplicant interface state: starting - ready Feb 17 13:12:29 xo-58-2d-7a NetworkManager: info (eth0): device state change: 2 - 3 (reason 0) Feb 17 13:12:29 xo-58-2d-7a kernel: [ 1395.781623] done. Feb 17 13:12:32 xo-58-2d-7a kernel: [ 1398.691643] libertas: command 0x0010 timed out Feb 17 13:12:32 xo-58-2d-7a kernel: [ 1398.691693] libertas: requeueing command 0x0010 due to timeout (#1) Feb 17 13:12:35 xo-58-2d-7a kernel: [ 1401.691097] libertas: command 0x0010 timed out Feb 17 13:12:35 xo-58-2d-7a kernel: [ 1401.691131] libertas: requeueing command 0x0010 due to timeout (#2) Feb 17 13:12:38 xo-58-2d-7a kernel: [ 1404.691533] libertas: command 0x0010 timed out Feb 17 13:12:38 xo-58-2d-7a kernel: [ 1404.691564] libertas: requeueing command 0x0010 due to timeout (#3) Feb 17 13:12:41 xo-58-2d-7a NetworkManager: info (eth0): now unmanaged Feb 17 13:12:41 xo-58-2d-7a NetworkManager: info (eth0): device state change: 3 - 1 (reason 36) Feb 17 13:12:41 xo-58-2d-7a NetworkManager: info (eth0): cleaning up... Feb 17 13:12:41 xo-58-2d-7a kernel: [ 1407.694409] libertas: command 0x0010 timed out Feb 17 13:12:41 xo-58-2d-7a kernel: [ 1407.694439] libertas: Excessive timeouts submitting command 0x0010 Feb 17 13:12:41 xo-58-2d-7a kernel: [ 1407.694457] Resetting OLPC wireless via EC... Feb 17 13:12:41 xo-58-2d-7a kernel: [ 1407.697589] usb 2-1: USB disconnect, address 15 Feb 17 13:12:41 xo-58-2d-7a kernel: [ 1407.697661] usb8xxx: URB in failure status: -108 Feb 17 13:12:41 xo-58-2d-7a kernel: [ 1407.699907] libertas: PREP_CMD: command 0x0006 failed: -2 Feb 17 13:12:41 xo-58-2d-7a kernel: [ 1407.699925] libertas: SCAN_CMD failed Feb 17 13:12:42 xo-58-2d-7a kernel: [ 1408.494877] usb 2-1: new high speed USB device using ehci_hcd and address 16 Feb 17 13:12:42 xo-58-2d-7a kernel: [ 1408.649132] usb 2-1: configuration #1 chosen from 1 choice Feb 17 13:12:42 xo-58-2d-7a kernel: [ 1408.671368] usb 2-1: firmware: requesting usb8388.bin Feb 17 13:12:43 xo-58-2d-7a kernel: [ 1409.463412] usb8xxx: Firmware ready event received Feb 17 13:12:43 xo-58-2d-7a NetworkManager: info (eth0): driver supports SSID scans (scan_capa 0x01). Feb 17 13:12:43 xo-58-2d-7a NetworkManager: info (eth0): new 802.11 WiFi device (driver: 'usb') Feb 17 13:12:43 xo-58-2d-7a NetworkManager: info (eth0): exported as /org/freedesktop/Hal/devices/net_00_17_c4_58_2d_7a Feb 17 13:12:43 xo-58-2d-7a kernel: [ 1409.471716] libertas: 00:17:c4:58:2d:7a, fw 5.110.22p23, cap 0x03a3 Feb 17 13:12:43 xo-58-2d-7a kernel: [ 1409.480375] libertas: eth0: Marvell WLAN 802.11 adapter Feb 17 13:12:43 xo-58-2d-7a kernel: [ 1409.484180] libertas: Not issuing HOST_SLEEP_CFG on XO-1 Feb 17 13:12:43 xo-58-2d-7a kernel: [ 1409.484949] libertas: PREP_CMD: command 0x0074 failed: 2 Feb 17 13:12:43 xo-58-2d-7a kernel: [ 1409.484965] usb8xxx: Firmware does not seem to support PS mode Feb 17 13:12:48 xo-58-2d-7a NetworkManager: info (eth0): device state change: 1 - 2 (reason 2) Feb 17 13:12:48 xo-58-2d-7a NetworkManager: info (eth0): bringing up device. Feb 17 13:12:48 xo-58-2d-7a NetworkManager: info (eth0): preparing device. Feb 17 13:12:48 xo-58-2d-7a NetworkManager: info (eth0): deactivating device (reason: 2). Feb 17 13:12:48 xo-58-2d-7a NetworkManager: info (eth0): supplicant interface state: starting - ready Feb 17 13:12:48 xo-58-2d-7a NetworkManager: info (eth0): device state change: 2 - 3 (reason 0) Feb 17 13:12:48 xo-58-2d-7a kernel: [ 1414.140573] ADDRCONF(NETDEV_UP): eth0: link is not ready Feb 17 13:13:49 xo-58-2d-7a NetworkManager: WARN nm_signal_handler(): Caught signal 15, shutting down normally. Feb 17 13:13:49 xo-58-2d-7a NetworkManager: info (eth0): now unmanaged Feb 17 13:13:49 xo-58-2d-7a NetworkManager: info (eth0): device state change: 3 - 1 (reason 36) Feb 17 13:13:49 xo-58-2d-7a NetworkManager: info (eth0): cleaning up... Feb 17 13:13:49
Re: NetworkManager from fedora-updates-testing broken on F11-XO1
On Wed, 2010-02-17 at 10:20 -0300, Bernie Innocenti wrote: On Mon, 2010-02-15 at 16:15 -0800, Dan Williams wrote: Not a known issue; but I'll try to reproduce on mine. Unless Daniel gets there first of course. I retrieved the log: I was able to reproduce the issue as well. The problem is that the libertas driver isn't correctly showing the 'driver' link in sysfs, it's showing it as 'usb' which is wrong... we may just work around that in NM, but Id like to figure out why libertas is screwing this up on F11/F12 first. Dan ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: NetworkManager from fedora-updates-testing broken on F11-XO1
On Wed, 2010-02-17 at 11:08 -0800, Dan Williams wrote: On Wed, 2010-02-17 at 10:20 -0300, Bernie Innocenti wrote: On Mon, 2010-02-15 at 16:15 -0800, Dan Williams wrote: Not a known issue; but I'll try to reproduce on mine. Unless Daniel gets there first of course. I retrieved the log: I was able to reproduce the issue as well. The problem is that the libertas driver isn't correctly showing the 'driver' link in sysfs, it's showing it as 'usb' which is wrong... we may just work around that in NM, but Id like to figure out why libertas is screwing this up on F11/F12 first. Thanks for analyzing this. As soon as you have a patch, I'd like to test it in my local olpc-2.6 kernel builds. -- // Bernie Innocenti - http://codewiz.org/ \X/ Sugar Labs - http://sugarlabs.org/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
NetworkManager from fedora-updates-testing broken on F11-XO1
We didn't collect the logs in the field, but in /var/log/messages we found an assertion failure from NM which was more or less like driver ! = NULL, just after logging something about the OLPC mesh device. Wireless wasn't working at all afterwards. The broken package is NetworkManager-0.7.2.995-1.git20100202.fc11 . Reverting to a previous version cured the issue for us. Let me know if this is a known problem or if you need more help tracking it down. It can be reproduced systematically on F11-XO1. -- // Bernie Innocenti - http://codewiz.org/ \X/ Sugar Labs - http://sugarlabs.org/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: NetworkManager from fedora-updates-testing broken on F11-XO1
On Mon, 2010-02-15 at 20:17 -0300, Bernie Innocenti wrote: We didn't collect the logs in the field, but in /var/log/messages we found an assertion failure from NM which was more or less like driver ! = NULL, just after logging something about the OLPC mesh device. Wireless wasn't working at all afterwards. The broken package is NetworkManager-0.7.2.995-1.git20100202.fc11 . Reverting to a previous version cured the issue for us. Let me know if this is a known problem or if you need more help tracking it down. It can be reproduced systematically on F11-XO1. Not a known issue; but I'll try to reproduce on mine. Unless Daniel gets there first of course. Dan ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
