Public bug reported:
Binary package hint: ifupdown
This bug has only happened after upgrading to Intrepid.
My computer has two network cards. I have one set to a static IP
because I am usually behind a router. The other interface is configured
via DHCP in case I want to connect to my cable modem directly.
I do realize that the problem is likely the fact that I have "auto eth1"
set. However, my configuration has been this way for a long time in
Hardy without issue. Intrepid seems to not only have an extremely long
timeout in DHCP, but it does not say anything in the console (like
getting IP address on eth0). And, none of the boot process runs in the
background while it is trying to acquire an IP address -- even though it
does have an IP address on one of its interfaces.
Worst of all, this cannot be interrupted with ctrl-C or backslash. A
few times I have tried Alt-SysRQ-k and this has just caused the entire
system to halt since for some reason the secure access key decided to
kill the init process.
Also, I see from dmesg that something was sending out a bunch of multicast UDP
packets onto vnet0.
Anyway I'm going to report back next time I reboot if it boots quickly
without using dhcp on eth1. Forgot to do that last time around.
eth0
02:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8056 PCI-E
Gigabit Ethernet Controller (rev 12)
Subsystem: ASUSTeK Computer Inc. Device 81f8
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort-
<MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 32 bytes
Interrupt: pin A routed to IRQ 2298
Region 0: Memory at fe9fc000 (64-bit, non-prefetchable) [size=16K]
Region 2: I/O ports at c800 [size=256]
Expansion ROM at fe9c0000 [disabled] [size=128K]
Capabilities: <access denied>
Kernel driver in use: sky2
Kernel modules: sky2
eth1
05:02.0 Ethernet controller: Intel Corporation 82557/8/9/0/1 Ethernet Pro 100
(rev 0c)
Subsystem: Intel Corporation Device 0040
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 64 (2000ns min, 14000ns max), Cache Line Size: 32 bytes
Interrupt: pin A routed to IRQ 18
Region 0: Memory at febff000 (32-bit, non-prefetchable) [size=4K]
Region 1: I/O ports at e800 [size=64]
Region 2: Memory at febc0000 (32-bit, non-prefetchable) [size=128K]
[virtual] Expansion ROM at f0000000 [disabled] [size=64K]
Capabilities: <access denied>
Kernel driver in use: e100
Kernel modules: eepro100, e100
auto lo
iface lo inet loopback
auto eth1
iface eth1 inet static
address 192.168.1.2
netmask 255.255.255.0
gateway 192.168.1.1
auto eth0
iface eth0 inet dhcp
hwaddress ether xx:xx:xx:xx:xx:xx
dmesg (from when I started to hit some alt-sysrq keys (already about 10
seconds or more after it was hanging... you can see the delays in the
timestamps)
** Affects: ifupdown (Ubuntu)
Importance: Undecided
Status: New
--
ifup: dhcp on boot cannot be interrupted
https://bugs.launchpad.net/bugs/285346
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
