From owner-freebsd-net@FreeBSD.ORG Thu Mar 15 16:45:41 2012 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 26F37106566B; Thu, 15 Mar 2012 16:45:41 +0000 (UTC) (envelope-from lacombar@gmail.com) Received: from mail-we0-f182.google.com (mail-we0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id 457C48FC0C; Thu, 15 Mar 2012 16:45:40 +0000 (UTC) Received: by wern13 with SMTP id n13so3961907wer.13 for ; Thu, 15 Mar 2012 09:45:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=2R7xK1zJzuNP6Wti45xyzDliBLj5TqUU1EV2LqfVIwE=; b=ESHfatG7S69+2nWejTyRmkJ7parJ/S8ch1e+N3KIuA7OGXSPSRJaGRKPDtVk896X4F Y4+qmKg7AHKwPgmrpk8JIQ46rylaeAQ3GKKHT+2ZqV0oRkse8Gevu15wBE/6WYIb23mu bHryc0rRsTMV393B7gzhT6IAbARbBfiUAf86ldtfCEESKXsdcWyAEpFXzVfnAzrxXJeb EUgcaQ99izWYFykcW1RgDRhnxoRuwKMJ2lEAMVeJljEhOyG+npopv76D6WEjInWkLEPA s3Vnn/HkyE0qsK0o+ganAQMmf0YkJL7XtkgHV+hw2gtBx5Nw3sGIEr3E6xJhWzfVeSlE UAmA== MIME-Version: 1.0 Received: by 10.180.82.132 with SMTP id i4mr27991027wiy.12.1331829939408; Thu, 15 Mar 2012 09:45:39 -0700 (PDT) Received: by 10.216.166.139 with HTTP; Thu, 15 Mar 2012 09:45:39 -0700 (PDT) In-Reply-To: References: Date: Thu, 15 Mar 2012 12:45:39 -0400 Message-ID: From: Arnaud Lacombe To: Jack Vogel Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Cc: Juli Mallett , freebsd-net@freebsd.org Subject: Re: MSI-X + em(4) = Refresh mbufs: hdr dmamap load failure - 22 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Mar 2012 16:45:41 -0000 Hi, On Thu, Mar 15, 2012 at 12:07 PM, Jack Vogel wrote: > You have header split on?? I've not seen this before so something odd > is going on. > AFAIK, you never implemented header-split on em(4), despite hardware supporting it, so that question is pointless. - Arnaud > Jack > > > On Thu, Mar 15, 2012 at 12:39 AM, Juli Mallett wro= te: > >> All, >> >> On both stable/9 and trunk I see that with one of either the 82571EB >> or 82574L I am flooded with messages in the form of: >> >> Refresh mbufs: hdr dmamap load failure - 22 >> >> If I disable msix, then the messages go away. =A0I am not sure why msix >> vs. non-msix would matter in this case unless in the msix case there's >> some kind of case of spurious interrupts causing em_rxeof to be called >> without any packets available. =A0If that happens then perhaps >> e1000_rx_unrefreshed() is called when no buffers have been processed >> and then em_refresh_mbufs wrongly refreshes the whole ring? >> >> This seems like it would be a problem because the >> bus_dmamap_load_mbuf_sg code is called unconditionally, even when a >> new mbuf isn't being allocated. =A0In that case, the mapping already >> exists. =A0Wouldn't it be necessary to unload and then reload the mbuf? >> So either it's a bug that em_refresh_mbufs is being called at all, or >> it's naively reusing mbufs in a way that actually guarantees an error, >> right? =A0Also, in the case where it frees, only m_free is called =97 is >> there never a case where that should be an m_freem? =A0I can imagine >> some, but they are likely impossible with the receive path of the >> driver. =A0(I don't know for sure because the receive path and the mbuf >> refresh code keep changing and I've been unable to keep up.) >> >> I don't know which part it is, of course, because I don't know what >> port it's coming from. =A0Like three other printfs in the driver where >> which device is being used matters tremendously, it uses a bare printf >> and not a device_printf. =A0I could modify the driver, but for now >> disabling msix is easier than continuing to load new kernels to try to >> debug the problem. >> >> Is anyone else seeing this? =A0Has anyone further investigated the >> problem? =A0Is there a patch floating around and I just haven't found >> the right search terms? >> >> Thanks in advance, >> Juli. >> >> PS: Yes, I know this is kind of a crappy bug report, sorry. =A0I've had >> a limited amount of time to investigate so far, and don't want to >> delay reporting it until I am able to get more time with the >> problematic hardware. >> _______________________________________________ >> freebsd-net@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-net >> To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" >> > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"