Comment 7 for bug 1181964

Revision history for this message
Bernd Edlinger (bernd-edlinger) wrote :

Hello,

unforutnately, I must admit, that I am no longer able to reproduce this bug here.

what I did was compile & install a locally generated test kernel over the 3.2.0-43 and later
re-install the 3.2.0-43 kernel from the .deb file in /var/cache/apt/archives

and, guess: now the network connects nicely again.

Therefore I do no longer think that the change between 3.2.0-41 and 3.2.0-43 can be connected to
the connectivity problem, because it is just one line of code, in this function, which is apparently
never executed on my machine (I added a printk there, but that was not executed):

--- linux-3.2.0/kernel/events/core.c
+++ linux-3.2.0/kernel/events/core.c
@@ -5164,7 +5164,7 @@

 static int perf_swevent_init(struct perf_event *event)
 {
- int event_id = event->attr.config;
+ u64 event_id = event->attr.config;

        if (event->attr.type != PERF_TYPE_SOFTWARE)
                return -ENOENT;

Therefore the reason must be somewhere else, in case the
network problem comes back, I added the following lines to
/etc/NetworkManager/NetworkManager.conf:

[logging]
level=DEBUG
domains=HW,RFKILL,ETHER,WIFI,BT,MB,DHCP4,DHCP6,PPP,WIFI_SCAN,IP4,IP6,AUTOIP4,DNS,VPN,SHARING,SUPPLICANT,AGENTS,SETTINGS,SUSPEND,CORE,DEVICE,OLPC,WIMAX

maybe that traces will give us some better insight.

Thanks, and Good Bye.