From owner-freebsd-questions@FreeBSD.ORG Sat Nov 15 17:44:00 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1292BBA0 for ; Sat, 15 Nov 2014 17:44:00 +0000 (UTC) Received: from mail-la0-x235.google.com (mail-la0-x235.google.com [IPv6:2a00:1450:4010:c03::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A2A6B19D for ; Sat, 15 Nov 2014 17:43:59 +0000 (UTC) Received: by mail-la0-f53.google.com with SMTP id mc6so16711420lab.12 for ; Sat, 15 Nov 2014 09:43:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=fon2RbnskgaAy6/Lwp2sXC6VD6KveQqtEGxF/JgFtCM=; b=vCDvlaQduIB4q4aEovUkyfYUwQTjRLiuN4d0oKaQbyuKgFzdEqZmJRZLXz+aMR0jdw rfkVpTq76ve7Qsd8r1//yuswBXbCR67f3mi37ctiCOabGiPWeBWVaiBGHcxTruQjqZVn QzniPZkA96VM3eQkMtibTAXTNeZMyVh328tRg5NZHcGqkeXJlheofTazD5UIojS6tlTc 6gX0rXt3IFM37VxHww8tbdwd2IeX7859gcRgKDRUk0q2M0Ed0iSN2GsSrLYbOfo3RGBq JFe0C9cD2XCxsQoVzpx6EZXPJT0PC7vEnXOI+u539tihTTIJw9dNugRY8DkQZfehXEnu /fVg== X-Received: by 10.112.169.106 with SMTP id ad10mr14900269lbc.13.1416073437658; Sat, 15 Nov 2014 09:43:57 -0800 (PST) Received: from blazon-pc.rw.local ([78.84.244.14]) by mx.google.com with ESMTPSA id ar4sm9071679lbc.48.2014.11.15.09.43.57 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 15 Nov 2014 09:43:57 -0800 (PST) Message-ID: <546790DC.4010108@gmail.com> Date: Sat, 15 Nov 2014 19:43:56 +0200 From: Alnis Morics User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: freebsd-questions@freebsd.org Subject: Re: msk doesn't work under 10-amd64 but does on i386 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit 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: Sat, 15 Nov 2014 17:44:00 -0000 >Hello list, > >I have a notebook machine that I've converted to act as a small >low-power server because its hinges have worn out. It's an atom samsung >notebook. The cpu identifies as: > >Intel(R) Atom(TM) CPU N450 @ 1.66GHz > >it is 64-bit capable: > >Extended feature flags set 1 (CPUID.80000001H:EDX): 20000000 >EM64T Intel Extended Memory 64 Technology > >so I installed the 10.1-R amd64 memstick. All goes well, it reboots, I >ssh into it and things are fine for a few minnutes but then I get the >following at the console: > >mmsk0: watchdog timeout > >and I lose the connection, can't ping anything including its gateway >from the device. A reboot will restore connectivity for a short period >but the same thing happens again. I tried with the latest 11 snapshot >and also tried with 10.0-R amd64 and get the same result. Then I tried >with the 10.1-R i386 (in other words, 32 bit) memstick and everything >works fine. > >Why the difference? >-- >John 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. -Alnis