On Fri, 7 Dec 2007 00:10:33 +0100, maximilian attems <[EMAIL PROTECTED]> wrote: > 2.6.23 from unstable install just fine in testing, > please try out, thanks. >
After the first reboot with 2.6.23, I got a crash but then it worked fine during most of the day. But just now, I got this strange error again from the network interface: Dec 7 22:25:21 bora-bora -- MARK -- Dec 7 22:26:24 bora-bora kernel: tg3: eth0: Link is down. Dec 7 22:26:24 bora-bora kernel: tg3: eth0: The system may be re-ordering memory-mapped I/O cycles to the network device, attempting to recover. Please report the problem to the driver maintainer and include system chipset information. Dec 7 22:26:27 bora-bora kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready Dec 7 22:26:28 bora-bora kernel: tg3: eth0: Link is up at 100 Mbps, full duplex. Dec 7 22:26:28 bora-bora kernel: tg3: eth0: Flow control is on for TX and on for RX. Dec 7 22:26:28 bora-bora kernel: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [...] So 2.6.23 seems to work better than 2.6.22-3, but it still produces this strange error that I did not experience before with 2.6.22-2 or earlier kernels. -Raphaël
