From owner-freebsd-hardware@FreeBSD.ORG Thu Nov 13 15:35:30 2014 Return-Path: Delivered-To: freebsd-hardware@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 8CBE23E9; Thu, 13 Nov 2014 15:35:30 +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 4B047BF2; Thu, 13 Nov 2014 15:35:29 +0000 (UTC) Received: from john by potato.growveg.org with local (Exim 4.84 (FreeBSD)) (envelope-from ) id 1Xovvm-000NSb-TF; Thu, 13 Nov 2014 15:03:30 +0000 Date: Thu, 13 Nov 2014 15:03:30 +0000 From: John To: freebsd-hardware@freebsd.org Subject: msk doesn't work under 10-amd64 but does on i386 Message-ID: <20141113150330.GA65597@potato.growveg.org> Mail-Followup-To: freebsd-hardware@freebsd.org, freebsd-questions@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline 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-questions@freebsd.org X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Nov 2014 15:35:30 -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