From owner-freebsd-questions@FreeBSD.ORG Mon Nov 17 14:09:51 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A1C64840; Mon, 17 Nov 2014 14:09:51 +0000 (UTC) Received: from potato.growveg.org (potato.growveg.org [62.49.247.163]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5E4BCA72; Mon, 17 Nov 2014 14:09:51 +0000 (UTC) Received: from john by potato.growveg.org with local (Exim 4.84 (FreeBSD)) (envelope-from ) id 1XqMzp-0006zn-0u; Mon, 17 Nov 2014 14:09:37 +0000 Date: Mon, 17 Nov 2014 14:09:36 +0000 From: John To: freebsd-questions@freebsd.org Subject: Re:msk0 doesn't work under10-amd64 but does on i386 Message-ID: <20141117140936.GA26696@potato.growveg.org> Reply-To: john@potato.growveg.org Mail-Followup-To: freebsd-questions@freebsd.org, freebsd-hardware@freebsd.org References: <546790DC.4010108@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <546790DC.4010108@gmail.com> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: John X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: john@potato.growveg.org X-SA-Exim-Scanned: No (on potato.growveg.org); SAEximRunCond expanded to false Cc: freebsd-hardware@freebsd.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Nov 2014 14:09:51 -0000 On Sat, Nov 15, 2014 at 07:43:56PM +0200, Alnis Morics wrote: > The same problem here, with the same netbook. AFAIK, it's an issue > with Marvell Technologies NICs; there are some PRs > (https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166727). For me, > 9.x realeases and 10.1-RC3 worked well with this NIC but 10.0-RELEASE > and 10.1-RELEASE don't. Some people have fully or partially solved > this problem with other Marvell NICs by tweaking some kernel settings. > I, too, tried them but thtey didn't help. Thanks for the reply. That's really interesting. 32-bit is fine for me though so I haven't spent a lot of time looking for a fix. -- John