Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
On Mon, Sep 28, 2009 at 01:03:26PM +0200, Jeroen Groenewegen van der Weyden wrote: > Thank you, I hear what you are saying. > > One more thing I noticed when testing with DRBD 8.3.3RC2 the behaviour > is different. Probably only by "accident" and some different timing. > The target machine does not stall but simply disconnects > all network interfaces. The var/log/messages show the included in the > snippet below. > > Do you think with this information the bnx2 module is faulty? Well, what do _you_ think, after you put the > kernel: ------------[ cut here ]------------ > kernel: WARNING: at net/sched/sch_generic.c:219 dev_watchdog+0x139/0x1eb() > kernel: NETDEV WATCHDOG: eth0 (bnx2): transmit timed out > kernel: bnx2: eth0 NIC Copper Link is Down > kernel: br0: port 1(eth0) entering disabled state into your favorite search engine or bugzilla search interface, and browsed through the first few hits? -- : Lars Ellenberg : LINBIT | Your Way to High Availability : DRBD/HA support and consulting http://www.linbit.com DRBD® and LINBIT® are registered trademarks of LINBIT, Austria. __ please don't Cc me, but send to list -- I'm subscribed