On Fri, 07 Dec 2007, Raphaël Quinet wrote: > 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:
hmm did you run memtest on your box? > 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. hmm above warants an entry in bugzilla.kernel.org for tg3 please tell us the resulting bugnumber. thanks -- maks
