From owner-freebsd-bugs@FreeBSD.ORG Mon Feb 16 22:48:16 2015 Return-Path: Delivered-To: freebsd-bugs@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 E3D1C410 for ; Mon, 16 Feb 2015 22:48:16 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 C8C31DBE for ; Mon, 16 Feb 2015 22:48:16 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t1GMmG4j044429 for ; Mon, 16 Feb 2015 22:48:16 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 197535] [re] [panic] if_re (Realtek 8168) causes memory write after free and kernel panic Date: Mon, 16 Feb 2015 22:48:16 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: marius@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: mfc-stable10? X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Feb 2015 22:48:17 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197535 --- Comment #6 from Marius Strobl --- Your rev. 0x4c000000 MAC coming up with broken firmware could be another reason, which would be unfortunate, though, as these images are GPLed. However, the Atom E3800 errata has an entry (VLI30 in the non-NDA October 2013 version of that document) suggesting that the MMU will not behave correctly when employing super pages, which would be a more plausible cause for the problems you are experiencing. Thus, I'd give a kernel with super page usage disabled a try. Last time I tested, unfortunately, the corresponding loader tunable didn't take effect. So manually setting pg_ps_enabled to 0 in sys/amd64/amd64/pmap.c and recompiling likely is safest in order to do so. -- You are receiving this mail because: You are the assignee for the bug.