From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752328Ab2ATIYU (ORCPT ); Fri, 20 Jan 2012 03:24:20 -0500 Received: from na3sys010aog110.obsmtp.com ([74.125.245.88]:41657 "HELO na3sys010aog110.obsmtp.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1751187Ab2ATIYQ (ORCPT ); Fri, 20 Jan 2012 03:24:16 -0500 MIME-Version: 1.0 In-Reply-To: References: From: Roland Dreier Date: Fri, 20 Jan 2012 00:23:52 -0800 Message-ID: Subject: Re: kernel BUG at drivers/iommu/intel-iommu.c:1767 on F16 3.1.1-2.fc16.x86_64 To: Albert Strasheim Cc: linux-rdma@vger.kernel.org, LKML , David Woodhouse Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Jan 19, 2012 at 12:57 AM, Albert Strasheim wrote: > Just checking up on this issue. Is there any further testing or > information we can provide to help make a fix happen? I'm not likely to be much help on VT-d issues, but maybe it would be useful to dump all the values in the BUG_ON if its going to trigger, ie just before BUG_ON(addr_width < BITS_PER_LONG && (iov_pfn + nr_pages - 1) >> addr_width); add if (addr_width < BITS_PER_LONG && (iov_pfn + nr_pages - 1) >> addr_width) pr_err("VT-d BUG! addr_width %d < %d (iov_pfn 0x%lx nr_pages %ld)\n", addr_width, BITS_PER_LONG, iov_pfn, nr_pages); and report what that prints. - R.