From owner-freebsd-net@freebsd.org Sun Feb 21 12:50:44 2016 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BF8FAAAF1F4 for ; Sun, 21 Feb 2016 12:50:44 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from mail-pf0-x22e.google.com (mail-pf0-x22e.google.com [IPv6:2607:f8b0:400e:c00::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9674F15BF for ; Sun, 21 Feb 2016 12:50:44 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by mail-pf0-x22e.google.com with SMTP id e127so77440685pfe.3 for ; Sun, 21 Feb 2016 04:50:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:date:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=pUAAZE8k7ZGYmd7TDbc4MdbavSAzpDhEQCi3aprr+Gk=; b=cmPDR9+Dxy1g9oYXnwJ5KNNNwRRI39WSSYAfUbo4n4fRHEPdsbxvBbN2QkZFrc9lQs Lrsg37oY0y5kzO9UjVv0tNHbq2GjtELSgf5DSYgpEan8zlz26gTxgw8qgvMtkI+ofPiV pGRFIbodjE7vFiQzRaFvm9p78Dq7WTq8btrt7LnxWOeD3+A6SdjZX7nJP4qwF/sYw/Ae E0cqxkocK+1REITdhIeN3L2iBcBE2FAuwl/OgEBEMaCd7OaJQW1cemjUi3AENAx3KRm8 cBDEpqJoJ5bcT7s0kv+KhDdYvdPgqtjh4iW62WVm4g70tM4LirfpV2ta2KQ2u3tssVfd K9sw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:date:to:cc:subject:message-id:reply-to :references:mime-version:content-type:content-disposition :in-reply-to:user-agent; bh=pUAAZE8k7ZGYmd7TDbc4MdbavSAzpDhEQCi3aprr+Gk=; b=bsnlUBC1bOd82HEL0dVa6cz1YUlL+Yqj6/X5klhP7kKKCdutZN/pZgK/+XLicr58uv pojfAP8zZJra71ayWB9pC+SklW+nmREZMtsufqdcvOTVku4MwVVIpOodIKCrYQAxOugL OjpcxbDGPxekXQXLgB2LxUhUJHFhptcVVfKEfSl7dhyfZOYYykjKnt8LNxvX6yFmeOiN 4K7s+Uae07O+Xj5DG61xe74S+S80WGuC/C/rL7VUR22oMWSNw9taEB1TnmMXfKRw9MhF xtA5CHW50fHog9QvAcUM/3RbG3aBa3k0mEt2ukzWJzM/oFA2+Uia9ZYsuh6D3LQ+L7qZ Mdeg== X-Gm-Message-State: AG10YORcIutJCB+pbt4tCCdqffYwY820BKWkoCYRWj9Ae97bM/2vYpy+hoPNs8IQzDGG8w== X-Received: by 10.98.13.216 with SMTP id 85mr30667607pfn.143.1456059044201; Sun, 21 Feb 2016 04:50:44 -0800 (PST) Received: from localhost ([106.247.248.2]) by smtp.gmail.com with ESMTPSA id bx1sm30108254pab.33.2016.02.21.04.50.40 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 21 Feb 2016 04:50:42 -0800 (PST) From: YongHyeon PYUN X-Google-Original-From: "YongHyeon PYUN" Received: by localhost (sSMTP sendmail emulation); Sun, 21 Feb 2016 21:50:35 +0900 Date: Sun, 21 Feb 2016 21:50:35 +0900 To: Tino Engel Cc: "freebsd-net@freebsd.org" Subject: Re: Support for Killer E2400 Ethernet Message-ID: <20160221125035.GA1753@michelle.fasterthan.co.kr> Reply-To: pyunyh@gmail.com References: <20160219012612.GA1267@michelle.fasterthan.co.kr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Feb 2016 12:50:44 -0000 On Fri, Feb 19, 2016 at 08:23:28PM +0100, Tino Engel wrote: > Thanks very much for the quick reply. > > So let me shed some words on your input: > > First: Limiting the memory size did not help at all, nothing changed. > Unfortunetly I cannot post the whole results of the sysctl, since I cannot get this box into the net, and it is quite too much to type it by hand. > Is there any special value you are interested in? > I'm not sure, just wanted to know these counters to guess what would be causing the issue. Probably error related counters would be helpful(sysctl -d dev.alc.0.stats will show description for each counters). > Then I applied your patch. > The requested output is: > alc0: DMA CFG : 0x0c347c54 > Could you verbose boot your kernel and show me the output of alc(4) related ones? It will show you read request/TLP payload size as well as PCI/Chip revision information. > The bad thing: The error still persists. :( > It always writes "DMA write error" now followed by "DMA CFG : ..." > > One more thing: > The ping -s command results in the same error as trying to fetch something from the internet. > 'ping -s 1472' was one of known way that reliably trigger the issue on E2200(and now E2400). > Do you have any further ideas? > Not yet. Thanks.