All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Williams <dan.j.williams@intel.com>
To: Chris Li <lkml@chrisli.org>
Cc: David Woodhouse <dwmw2@infradead.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: BUG in drivers/dma/ioat/dma_v2.c:314
Date: Thu, 22 Jul 2010 15:00:48 -0700	[thread overview]
Message-ID: <4C48BF90.3050100@intel.com> (raw)
In-Reply-To: <AANLkTilmz73V7cc2UiGNUgU9cANzX8u5QP232DcbxGxR@mail.gmail.com>

On 7/22/2010 2:39 PM, Chris Li wrote:
> On Wed, Jul 21, 2010 at 6:15 PM, Dan Williams<dan.j.williams@intel.com>  wrote:
>>
>> Here is v5 with the aforementioned change.
>
> One warning.
>
> CC      drivers/pci/intel-iommu.o
> drivers/pci/intel-iommu.c: In function ‘quirk_ioat_snb_local_iommu’:
> drivers/pci/intel-iommu.c:3037: warning: unused variable ‘i’

Oops, I'll clean that up.

> The dmesg looks good.
>
[..]
> dca service started, version 1.12.1
> ioatdma: Intel(R) QuickData Technology Driver 4.00
> ioatdma 0000:00:0f.0: can't derive routing for PCI INT A
> ioatdma 0000:00:0f.0: PCI INT A: no GSI
> ------------[ cut here ]------------
> WARNING: at drivers/pci/intel-iommu.c:3056
> quirk_ioat_snb_local_iommu+0xae/0xc7()
> Hardware name: MacPro3,1
> BIOS assigned incorrect VT-d unit for Intel(R) QuickData Technology device
[..]
> ---[ end trace c7f418b83f8ca665 ]---
> Disabling lock debugging due to kernel taint
> ioatdma 0000:00:0f.0: setting latency timer to 64
>    alloc irq_desc for 57 on node -1
>    alloc kstat_irqs on node -1
> ioatdma 0000:00:0f.0: irq 57 for MSI/MSI-X
>    alloc irq_desc for 58 on node -1
>    alloc kstat_irqs on node -1
> ioatdma 0000:00:0f.0: irq 58 for MSI/MSI-X
>    alloc irq_desc for 59 on node -1
>    alloc kstat_irqs on node -1
> ioatdma 0000:00:0f.0: irq 59 for MSI/MSI-X
>    alloc irq_desc for 60 on node -1
>    alloc kstat_irqs on node -1
> ioatdma 0000:00:0f.0: irq 60 for MSI/MSI-X
>

Nice, and the driver was able to load normally.  Thanks for the all the 
testing!

David, I'll take this through my tree as a regression fix (since 2.6.32) 
if you have no objections.  Now that we are not hitting a driver load 
failure I think I'll add a WARN() to this init-fail path.  I doubt we 
would have flushed out this problem had the driver been discretely 
handling init failures since day one.

Regards,
Dan

      reply	other threads:[~2010-07-22 22:00 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-28 23:50 BUG in drivers/dma/ioat/dma_v2.c:314 Chris Li
2010-06-29  0:45 ` Dan Williams
2010-06-29  7:17   ` Chris Li
2010-06-29 23:20   ` Chris Li
2010-06-29 23:57     ` Dan Williams
2010-06-30  1:07       ` Chris Li
2010-06-30  4:17         ` Dan Williams
2010-06-30 18:26           ` Chris Li
2010-06-30 18:43             ` Chris Li
2010-06-30 18:43             ` David Woodhouse
2010-06-30 19:40               ` Dan Williams
2010-06-30 20:02                 ` David Woodhouse
2010-06-30 21:44                   ` Dan Williams
2010-06-30 21:59                     ` Chris Li
2010-06-30 22:04                       ` Dan Williams
2010-07-01  6:21                     ` David Woodhouse
2010-07-01  6:51                       ` Dan Williams
2010-07-01  7:12                         ` David Woodhouse
2010-07-01  7:26                           ` Dan Williams
2010-07-01  8:15                             ` David Woodhouse
2010-07-01 17:20                               ` Dan Williams
2010-07-01 17:58                                 ` Chris Li
2010-07-02 19:00                                   ` Chris Li
2010-07-05 10:16                                     ` David Woodhouse
2010-07-06 23:40                                       ` Chris Li
2010-07-07  0:51                                         ` Dan Williams
2010-07-07  0:51                                           ` Chris Li
2010-07-07  0:58                                             ` Dan Williams
2010-07-07  1:03                                               ` Chris Li
2010-07-07  3:22                                                 ` David Woodhouse
2010-07-07  3:40                                           ` David Woodhouse
2010-07-07 17:47                                             ` Dan Williams
2010-07-07 18:07                                               ` David Woodhouse
2010-07-07 21:56                                               ` Chris Li
2010-07-09 21:28                                                 ` Dan Williams
2010-07-09 22:00                                                   ` Chris Li
2010-07-10  0:09                                                   ` David Woodhouse
2010-07-15  5:41                                                     ` Dan Williams
2010-07-16 21:29                                                       ` Chris Li
2010-07-16 22:12                                                       ` David Woodhouse
2010-07-16 22:40                                                         ` Chris Li
2010-07-22  1:15                                                           ` Dan Williams
2010-07-22 21:39                                                             ` Chris Li
2010-07-22 22:00                                                               ` Dan Williams [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4C48BF90.3050100@intel.com \
    --to=dan.j.williams@intel.com \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@chrisli.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.