From owner-freebsd-bugs@FreeBSD.ORG  Mon Feb 16 11:58:18 2015
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
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 552132D6
 for <freebsd-bugs@FreeBSD.org>; Mon, 16 Feb 2015 11:58:18 +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 35C19C31
 for <freebsd-bugs@FreeBSD.org>; Mon, 16 Feb 2015 11:58:18 +0000 (UTC)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t1GBwIK0097816
 for <freebsd-bugs@FreeBSD.org>; Mon, 16 Feb 2015 11:58:18 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 11:58:18 +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: luca.pizzamiglio@gmail.com
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: <bug-197535-8-yJRdthqqUj@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-197535-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-197535-8@https.bugs.freebsd.org/bugzilla/>
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 <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Feb 2015 11:58:18 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197535

--- Comment #5 from luca.pizzamiglio@gmail.com ---
Thanks for patch!
I tested it and unfortunately it doesn't any difference.

I tested the board on Linux and it works.
I shortly looked in the re Linux driver and it seems that they have the ability
to dynamically load a known firmware on the chip and they do it for this
specific chip. It could be the case that my 0x4c000000 card has a different
firmware version.
I'll try to get more information on that side.

It really seems that the network card is writing received packets (via DMA?) in
unexpected memory addresses overwriting portion of the kernel and causing the
panics.

-- 
You are receiving this mail because:
You are the assignee for the bug.