Date: Sat, 8 Mar 2008 17:07:10 +0100 From: Daniel Gerzo <danger@FreeBSD.org> To: Daniel Gerzo <danger@FreeBSD.org> Cc: Pyun YongHyeon <pyunyh@gmail.com>, current@FreeBSD.org, yongari@FreeBSD.org Subject: Re[3]: re(4) problem Message-ID: <918167276.20080308170710@rulez.sk> In-Reply-To: <1373272150.20080308001103@rulez.sk> References: <20080306200532.GA84961@cvsup.sk.freebsd.org> <20080307043815.GA92464@cdnetworks.co.kr> <1373272150.20080308001103@rulez.sk>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello, Saturday, March 8, 2008, 12:11:03 AM, has been written: > Hello Pyun, > Friday, March 7, 2008, 5:38:15 AM, you wrote: >> I guess your issue is not related with bus_dma fixes but improper >> handling of link state. Try attached patch and let me know how it >> goes. > The attached patch didn't help, the box is again in the same status. > Can I provide you with some more detailed debugging info, or do you > have some other ideas what could be fixed? > I could probably manage a remote access to that box, but no remote > console is available, and I don't know exactly how to trigger this > scenario, but I think it depends on the amount of traffic being sent > over the device. If I won't hear from anybody in next 24 hours, I will have to replace the network device in this box, in order to get it running properly. However, I don't consider this step as a right solution and I would rather better like to have it fixed in the driver. Thanks. -- Best regards, Daniel mailto:danger@FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?918167276.20080308170710>