[Bug 350639] [NEW] Kubuntu 8.04.2 fails to properly initialize network interfaces
pedro rezende
prezende at unb.br
Sat Mar 28 23:38:04 UTC 2009
Public bug reported:
This is a bug report on a consistent failure of kubuntu 8.04.2 to
properly initialize network services. A summary description of the
problem follows:
Settings:
1- Computer named "servidor" running kubuntu 8.04.2 has two nics, consistently assigned to eth0 and eth1 as per /etc/udev/rules.d/70-persistent-net.rules:
# PCI device 0x1039:0x0900 (sis900)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:11:5b:36:c7:75", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
# PCI device 0x10ec:0x8139 (8139too)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:08:54:de:ca:67", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1".
2- Nics in servidor are physically connected as follows:
eth0 (sis900) is onboard a PC Chips M836G motherboard, connected to a cable modem/router provided by the ISP, with connectivity via DHCP;
eth1 (8139too) is an external card, connected to a local ethernet hub, for the purpose of setting up a local network in which servidor operates as bridge (or router, proxy, etc.);
3- Setup described above works as intended, with no problems, with other
distros (i.e., several versions of Mandriva) running on servidor,
including at this time through a dual boot installation. Therefore,
problems with the cards themselves are not the issue.
kubuntu 8.04.2 Behavior:
1- If the local hub connected to eth1 is powered *on* at boot time, eth0
fails to initialize (only eth1 is initialized, with IP4 address assigned
to 0.0.0.0). This is shown by KNetworkManager applet, and confirmed by
attempts to run services which require internet connectivity, such as
apt-get
2- If the local hub connected to eth1 is powered *off* at boot time,
eth0 initializes properly, succeeding in requesting and obtaining a
valid IP address from the corresponding ISP. In this case eth1 is not
initialized, as shown by KNetworkManager applet (the corresponding entry
is grayed out), as expected by the fact that the ethernet hub connected
to it is powered off
3- If servidor is booted with the local hub turned on, eth0 can later be
initialized by right-clicking on the KNetworkManager applet system icon
and selecting the eth0 interface for activation; however, if this is
done then eth1 gets deactivated, as indicated by the corresponding entry
being no longer ticked out (only eth0 becomes ticked).
Preliminary analysis:
A) All attempts by sudo to set a(ny) nic to initialize at boot are ignored by KNetworkManagement. When opened, KNetworkManagement allways show all nic configuration options deselected, for all nics, regardless of what has been priorly "saved". Attempts to run knetworkmanager from sudo su (to get error msgs when trying to save option settings) return the following msg:
-------------------------
root at servidor:/etc/udev/rules.d# knetworkmanager
No protocol specified
kdeinit: Can't connect to the X Server.
kdeinit: Might not terminate at end of session.
No protocol specified
kded: cannot connect to X server :0.0
kded: ERROR: KUniqueApplication: Registering failed!
kded: ERROR: Communication problem with kded, it probably crashed.
No protocol specified
knetworkmanager: cannot connect to X server :0.0
DCOP aborting call from 'anonymous-7075' to 'knetworkmanager'
ERROR: Communication problem with knetworkmanager, it probably crashed.
root at servidor:/etc/udev/rules.d#
--------------------------
B) A systemlog from a boot leading (consistently) to behavior 1, i.e, with the local ethernet hub turned on (log_hub_on), and a systemlog from a boot leading (consistently) to behavior 2, i.e. with local ethernet hub turned off (log_hub_off), are included in "logs.txt" attached. These logs are compared below w.r.t. elements looking suspicious in association with this bug. In chronological order:
Line 131 (in both logs) shows a suspicious ACPI checksum error warning:
kernel [ 24.773449] ACPI Warning (tbutils-0217): Incorrect checksum in table [OEMB] - 12, should be 09 [20070126]
Line 218, after SCSI subsystem inicialization, the two logs begin to differ regarding the order of actions:
-----------------------------
With the ethernet hub turned on (log_hub_on.txt), following SCSI initialization and before loading libdata the usbfs drivers are registered:
--------hub on:---------------
219 kernel [ 28.767376] usbcore: registered new interface driver usbfs
220 kernel [ 28.767439] usbcore: registered new interface driver hub
221 kernel [ 28.801530] libata version 3.00 loaded.
--------hub off:--------------
219 kernel [ 28.801530] libata version 3.00 loaded.
------------------------------
With the ethernet hub turned on (log_hub_on.txt), after libdata loading and before registering scsi and ata drivers new device drivers for the nics eth0, eth1 are registered (in this order):
--------hub on:---------------
222 kernel [ 28.818655] usbcore: registered new device driver usb
223 kernel [ 28.824214] sis900.c: v1.08.10 Apr. 2 2006
224 kernel [ 28.824402] ACPI: PCI Interrupt 0000:00:04.0[A] -> GSI 19 (level, low) -> IRQ 17
225 kernel [ 28.825572] 0000:00:04.0: Realtek RTL8201 PHY transceiver found at address 1.
226 kernel [ 28.837172] 0000:00:04.0: Using transceiver found at address 1 as default
227 kernel [ 28.841457] eth0: SiS 900 PCI Fast Ethernet at 0xd800, IRQ 17, 00:11:5b:36:c7:75
228 kernel [ 28.848426] 8139too Fast Ethernet driver 0.9.28
229 kernel [ 28.848580] ACPI: PCI Interrupt 0000:00:0b.0[A] -> GSI 18 (level, low) -> IRQ 16
230 kernel [ 28.849513] eth1: RealTek RTL8139 at 0xd400, 00:08:54:de:ca:67, IRQ 16
231 kernel [ 28.849520] eth1: Identified 8139 chip type 'RTL-8100B/8139D'
232 kernel [ 28.867286] 8139cp: 10/100 PCI Ethernet driver v1.3 (Mar 22, 2004)
233 kernel [ 28.883313] pata_sis 0000:00:02.5: version 0.5.2
234 kernel [ 28.892248] scsi0 : pata_sis
--------hub off:--------------
220 kernel [ 27.316203] pata_sis 0000:00:02.5: version 0.5.2
221 kernel [ 27.336012] scsi0 : pata_sis
------------------------------
With the hub turned on (log_hub_on.txt), after scsi0:pata_sis and before configuration of ata1 devices, ohci_hcd, scsi1, fd0 are registered (in this order):
--------hub on:----------------
235 kernel [ 28.901472] ohci_hcd: 2006 August 04 USB 1.1 'Open' Host Controller (OHCI) Driver
kernel [ 28.921052] scsi1 : pata_sis
kernel [ 28.922511] ata1: PATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma 0xffa0 irq 14
kernel [ 28.922519] ata2: PATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0xffa8 irq 15
kernel [ 29.075405] Floppy drive(s): fd0 is 1.44M
kernel [ 29.083413] ata1.00: ATA-6: SAMSUNG SV4002H, QP100-07, max UDMA/100
kernel [ 29.083424] ata1.00: 78242976 sectors, multi 16: LBA
kernel [ 29.095050] FDC 0 is a post-1991 82077
243 kernel [ 29.099514] ata1.00: configured for UDMA/100
--------hub off:--------------
222 kernel [ 27.354693] scsi1 : pata_sis
kernel [ 27.356136] ata1: PATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma 0xffa0 irq 14
kernel [ 27.356144] ata2: PATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0xffa8 irq 15
kernel [ 27.520298] ata1.00: ATA-6: SAMSUNG SV4002H, QP100-07, max UDMA/100
kernel [ 27.520311] ata1.00: 78242976 sectors, multi 16: LBA
kernel [ 27.536269] ata1.00: configured for UDMA/100
kernel [ 27.552002] usbcore: registered new interface driver usbfs
kernel [ 27.552070] usbcore: registered new interface driver hub
kernel [ 27.585757] usbcore: registered new device driver usb
kernel [ 27.600970] sis900.c: v1.08.10 Apr. 2 2006
kernel [ 27.613057] 8139too Fast Ethernet driver 0.9.28
kernel [ 27.640997] ohci_hcd: 2006 August 04 USB 1.1 'Open' Host Controller (OHCI) Driver
kernel [ 27.879801] Floppy drive(s): fd0 is 1.44M
235 kernel [ 27.899397] FDC 0 is a post-1991 82077
------------------------------
Note: With the hub turned off (log_hub_off.txt) the nic drivers are registered after ata1 devices are configured and before ohci_hcd and fd0 are registered, with the notable difference from when the ethernet local hub is turned on (when the nic drivers are registered between those two actions in inverted order) that no PCI interrupt is triggering the use *as default* of a transciever found at address associated with eth1. (line 225, log_hub_on.txt).
------------------------------
C) All attempts to capture logs with error msgs appearing at shutdown have failed. This includes setting BOOTLOGD_ENABLE=Yes at /etc/default/bootlogd, and shutting down with sudo su # shutdown -h now > shutdown.log (file is allways empty). Worthy of note are some error msgs captured by hand (reread over several shutdowns):
Network manager <degug>: nm_print_open_socks : open socks list
Network manager <degug>: nm_print_open_socks : open socks list done
Network manager <info>: deactivating eth1
Network manager <info>: deactivating eth0
Network manager: nm_dbus_signal_device_status_change assertion cbdata->data->dbus_connection failed
Network manager <warn>: nm_hda1_deinit(): libha1 shutdown failed: connection is closed
Network manager: nm_dbus_signal_device_status_change assertion cbdata->data->dbus_connection failed
Network manager: nm_dbus_signal_device_status_change assertion cbdata->data->dbus_connection failed
Network manager: nm_dbus_signal_device_status_change assertion cbdata->data->dbus_connection failed
Network manager: nm_dbus_init(): can not get the system bus. Make sure the system message daemon is running (SYSKLOGD and DBUS are RUNNING!!!)
Seldom and randomly a system call traceback degug msg is shown:
nm_signal_handler caught signal 6
no debug symbol found
no debug symbol found (several)
debugmsg libtree enabled
no debug symbol found
no debug symbol found (several)
in __kernel_vsyscall
D) Booting with noapic option makes no difference regarding these behaviors (no connection if the local ethernet hub is turned on at boot time). Worthy of note, booting with noapic option causes the sequence of ations when setting up network interfaces, described in item A above, to be the same as when apic is running and the ethernet hub is turned off (described in lines 219-235 in log_hub_off.txt), exept for an added configuration of interrupt 11, but nonetheless eth0 is down when any user logs in.
E) Booting with inverted external physical connections only makes matter worse: if eth0 (onboard sis900) is connected to the local ethernet hub and eth1 (8139too card), to the modem/router connected to the ISP, then in no way eth1 can be activated. Even with the local ethernet hub (connected to eth0) turned off, eth1 comes up with a random IP (outside the ISP network range) and with no IP for gateway.
** Affects: knetworkmanager (Ubuntu)
Importance: Undecided
Status: New
--
Kubuntu 8.04.2 fails to properly initialize network interfaces
https://bugs.launchpad.net/bugs/350639
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to knetworkmanager in ubuntu.
More information about the kubuntu-bugs
mailing list