Your message dated Tue, 12 May 2015 09:55:25 +1000
with message-id <2554127.VhDQXos71X@debstor>
and subject line Re: Bug#782416: Bonded interface hanging on shutdown/restart
has caused the Debian Bug report #782416,
regarding Bonded interface hanging on shutdown/restart
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
782416: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782416
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: ifenslave-2.6
Version: 2.6
One of my servers running Jessie hung on restart today and has been
continuing to do so; rebooting now requires a hard reset be invoked over
IPMI. When shutting down the last message displayed on the console was
"deconfiguring network interfaces".
After doing some digging, the part of the init script that was failing
was the segment that ran `ifdown -a --exclude lo`; if I run this
manually I can trigger the same behaviour. After 120s the system console
reports hung tasks belonging to kworker and ifenslave.
Corresponding to these are faults/call traces reported in dmesg also
belonging to ifenslave. Images of both are available on request (grabbed
these from the BMC as and when I saw them), will try to extract them as
text on the next available reboot slot.
This behaviour only became apparent after the last round of updates went
in - was working/rebooting perfectly fine a week ago. Hardware is an
ASRock E3C224D2I with two Intel i210 NICs (igb driver).
/etc/network/interfaces is as follows:
auto lo
iface lo inet loopback
# The primary network interface
auto bond0
iface bond0 inet static
address 192.168.1.128
netmask 255.255.255.0
network 192.168.1.0
broadcast 192.168.1.255
gateway 192.168.1.1
slaves eth0 eth1
bond_mode active-backup
bond_miimon 250
bond_downdelay 250
bond_updelay 250
ifconfig from the running system as follows:
bond0 Link encap:Ethernet HWaddr d0:50:99:26:4d:08
inet addr:192.168.1.128 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::d250:99ff:fe26:4d08/64 Scope:Link
UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1
RX packets:637 errors:0 dropped:0 overruns:0 frame:0
TX packets:492 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:419400 (409.5 KiB) TX bytes:62871 (61.3 KiB)
eth0 Link encap:Ethernet HWaddr d0:50:99:26:4d:08
UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1
RX packets:637 errors:0 dropped:0 overruns:0 frame:0
TX packets:492 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:419400 (409.5 KiB) TX bytes:62871 (61.3 KiB)
Memory:f7200000-f727ffff
eth1 Link encap:Ethernet HWaddr d0:50:99:26:4d:08
UP BROADCAST SLAVE MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Memory:f7100000-f717ffff
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:2 errors:0 dropped:0 overruns:0 frame:0
TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:188 (188.0 B) TX bytes:188 (188.0 B)
Please let me know if there are any other investigations I can carry out
to verify the cause. I don't know if it's related but the system only
has one NIC plugged in at present.
--- End Message ---
--- Begin Message ---
On Mon, 11 May 2015 19:32:53 Vroomfondel wrote:
> I think this bug might have been fixed with the kernel upgrade to
> linux-image-3.16.0-4-amd64; the server where this went in (before the
> release to stable jessie) had this problem evaporate. As far as I can
> tell there've been no updates to ifupdown since then, so perhaps an
> upgrade to the igb driver...?
>
> Anyway, on at least two systems that were experiencing the bug,
> shutdown/network restart no longer hangs.
Thank you for confirming that this temporary glitch was not in the ifenslave
package.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
--
Regards,
Dmitry Smirnov
GPG key : 4096R/53968D1B
---
It is a fine thing to be honest, but it is also very important to be right.
-- Winston Churchill
signature.asc
Description: This is a digitally signed message part.
--- End Message ---