On 07/07/11 11:36, YongHyeon PYUN wrote:
On Thu, Jul 07, 2011 at 11:26:08AM -0500, Nathan Whitehorn wrote:
On 07/07/11 11:07, Marius Strobl wrote:
On Thu, Jul 07, 2011 at 09:34:39AM -0500, Nathan Whitehorn wrote:
This breaks one of my gem devices (chip=0x0021106b) when the controller
is initia
On 07/07/11 11:07, Marius Strobl wrote:
On Thu, Jul 07, 2011 at 09:34:39AM -0500, Nathan Whitehorn wrote:
This breaks one of my gem devices (chip=0x0021106b) when the controller
is initialized from FreeBSD (netbooting works fine, and the controller
stays working after that), with "cannot disable
On Thu, Jul 07, 2011 at 11:26:08AM -0500, Nathan Whitehorn wrote:
> On 07/07/11 11:07, Marius Strobl wrote:
> >On Thu, Jul 07, 2011 at 09:34:39AM -0500, Nathan Whitehorn wrote:
> >>This breaks one of my gem devices (chip=0x0021106b) when the controller
> >>is initialized from FreeBSD (netbooting wo
On Thu, Jul 07, 2011 at 09:34:39AM -0500, Nathan Whitehorn wrote:
> This breaks one of my gem devices (chip=0x0021106b) when the controller
> is initialized from FreeBSD (netbooting works fine, and the controller
> stays working after that), with "cannot disable RX MAC" or "cannot
> disable RX M
This breaks one of my gem devices (chip=0x0021106b) when the controller
is initialized from FreeBSD (netbooting works fine, and the controller
stays working after that), with "cannot disable RX MAC" or "cannot
disable RX MAC or hash filter" messages.
-Nathan
On 06/28/11 11:16, Marius Strobl wr
Author: marius
Date: Tue Jun 28 16:16:43 2011
New Revision: 223648
URL: http://svn.freebsd.org/changeset/base/223648
Log:
- In gem_reset_rx() also reset the RX MAC which is necessary in order to
get it out of a stuck condition that can be caused by GEM_MAC_RX_OVERFLOW.
- In gem_reset_rxdma
