Date: Sat, 11 Jul 2009 06:14:20 +0300 From: Giorgos Keramidas <keramida@ceid.upatras.gr> To: kevin <stringflow@gmail.com> Cc: Sam Leffler <sam@freebsd.org>, freebsd-current@freebsd.org Subject: Re: About iwn firmware Message-ID: <874otjq5bn.fsf@kobe.laptop> In-Reply-To: <d4b0fbf00907101115m62bf74b9lc6c2443478240c09@mail.gmail.com> (kevin's message of "Sat, 11 Jul 2009 02:15:22 %2B0800") References: <d4b0fbf00907100639t7a91f4afmf826d3f47b438116@mail.gmail.com> <4A5777F6.5040700@freebsd.org> <d4b0fbf00907101115m62bf74b9lc6c2443478240c09@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 11 Jul 2009 02:15:22 +0800, kevin <stringflow@gmail.com> wrote: >> iwn driver works well when system up.but it is not so robust.it will stop > transfer data and throw some errors in these conditions: > 1 . mount nfs via wireless network,if i transfer a lot of data.it may stop > receiving data after some time. > 2 . wireless network is busy, then some one reboot the wireless AP.it may > throw some errors and stop working. > 3 . Find wireless network works slow and switch to Ethernet,.if try > /etc/rc.d/netif restart, it may throw some errors and stop working. > > all these are fixed by reboot system(reload iwn and iwnfw dose not work at > most time). i also find iwn driver printe a lot of microcode error related > messages when it failed(not easy to reproduce it). > > No official Change Log, i just notice the *description *in gentoo > bug#202818. Gentoo bugs refer to a different kernel altogether, so they are not really very useful, unless they also affect the BSD kernel in a reproducible manner. If you can reproduce some of these bugs with _FreeBSD_, however, please report them and include /var/log/messages output, any dmesg output that could help track the bugs, and/or even kernel backtraces.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?874otjq5bn.fsf>