Hi, I have two SuSE 9.3 machines which started to produce the following errors after the latest kernel update: Aug 24 00:04:59 scotty kernel: e100: eth1: e100_watchdog: link down Aug 24 00:13:19 scotty kernel: e100: eth1: e100_watchdog: link down Aug 24 00:14:10 scotty kernel: bonding: bond0: link status definitely down for interface eth1, disabling it Aug 24 00:14:12 scotty kernel: e100: eth1: e100_watchdog: link up, 10Mbps, full-duplex Aug 24 00:14:12 scotty kernel: bonding: bond0: link status definitely up for interface eth1. Aug 24 00:19:46 scotty kernel: e100: eth1: e100_watchdog: link down Aug 24 00:27:33 scotty kernel: bonding: bond0: link status definitely down for interface eth1, disabling it Aug 24 00:27:35 scotty kernel: e100: eth1: e100_watchdog: link up, 100Mbps, full-duplex Aug 24 00:27:35 scotty kernel: bonding: bond0: link status definitely up for interface eth1. Aug 24 00:36:12 scotty kernel: e100: eth1: e100_watchdog: link down Aug 24 00:47:17 scotty kernel: e100: eth1: e100_watchdog: link down Aug 24 00:54:16 scotty kernel: bonding: bond0: link status definitely down for interface eth1, disabling it Aug 24 00:54:18 scotty kernel: e100: eth1: e100_watchdog: link up, 100Mbps, full-duplex (this goes all day long) The second machine was installed only a few days ago and has never used the original kernel in production, but the messages are the same. I'm sure that the switches are not guilty, because the configuration has worked for a long time before (we used SuSE 9.0 on the recently upgraded machine, also with the e100/bonding driver). The NICs are Intel Pro 1000 (eth0) and Intel e100 (eth1) in active backup mode (mode=1, miimon=100) in the shown machine and two Intel e100 in the second machine. The first machine has link failures only on eth1 and the second machine on both. So most probably, this is the e100 driver, but e100.c has not changed in the kernel source packages :-( Security Team: Any hints? Markus