linux-kernel - Re: BUG in drivers/dma/ioat/dma

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 30 Jun 2010 11:26:54 -0700
From:	Chris Li <lkml@...isli.org>
To:	Dan Williams <dan.j.williams@...el.com>
Cc:	linux-kernel <linux-kernel@...r.kernel.org>,
	david.woodhouse@...el.com
Subject: Re: BUG in drivers/dma/ioat/dma_v2.c:314

On Tue, Jun 29, 2010 at 9:17 PM, Dan Williams <dan.j.williams@...el.com> wrote:
> [ copying David to see if I am barking up the wrong VT-d tree.  This is on a
> MacPro 3,1 according to dmesg so a 5400 series MCH ]
>
> On 6/29/2010 6:07 PM, Chris Li wrote:
>>
>> On Tue, Jun 29, 2010 at 4:57 PM, Dan Williams<dan.j.williams@...el.com>
>> OK. I can't do this test remotely so I will get back to you tomorrow.

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
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
ioatdma 0000:00:0f.0: ioat2_set_chainaddr: chainaddr: ffffe000
------------[ cut here ]------------
WARNING: at drivers/dma/ioat/dma_v2.c:289 ioat2_timer_event+0xbc/0x225
[ioatdma]()
Hardware name: MacPro3,1
0000:00:0f.0: ioat2_timer_event: Channel halted (10)
Modules linked in: ioatdma(+) dca fuse rfcomm sco bridge stp llc bnep
l2cap autofs4 sunrpc cpufreq_ondemand acpi_cpufreq freq_table mperf
ip6t_REJECT nf_conntrack_ipv6 ip6table_filter ip6_tables ipv6 uinput
snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep snd_seq
snd_seq_device btusb i5400_edac snd_pcm bluetooth shpchp snd_timer snd
e1000e soundcore rfkill i2c_i801 edac_core iTCO_wdt snd_page_alloc
applesmc i5k_amb iTCO_vendor_support input_polldev firewire_ohci
firewire_core crc_itu_t radeon ttm drm_kms_helper drm i2c_algo_bit
i2c_core [last unloaded: scsi_wait_scan]
Pid: 0, comm: swapper Not tainted 2.6.35-rc3+ #41
Call Trace:
 <IRQ>  [<ffffffff8104bdac>] warn_slowpath_common+0x85/0x9d
 [<ffffffff8104be67>] warn_slowpath_fmt+0x46/0x48
 [<ffffffff810100a5>] ? sched_clock+0x9/0xd
 [<ffffffffa03ef55b>] ioat2_timer_event+0xbc/0x225 [ioatdma]
 [<ffffffff81069d76>] ? sched_clock_cpu+0xc3/0xce
 [<ffffffff81058a6a>] run_timer_softirq+0x1d6/0x2a5
 [<ffffffffa03ef49f>] ? ioat2_timer_event+0x0/0x225 [ioatdma]
 [<ffffffff8106cc08>] ? ktime_get+0x65/0xbe
 [<ffffffff81051ddb>] __do_softirq+0xe9/0x1ae
 [<ffffffff81070f70>] ? tick_program_event+0x2a/0x2c
 [<ffffffff8100ab1c>] call_softirq+0x1c/0x30
 [<ffffffff8100c18a>] do_softirq+0x46/0x83
 [<ffffffff81051c48>] irq_exit+0x3b/0x7d
 [<ffffffff81433638>] smp_apic_timer_interrupt+0x8d/0x9b
 [<ffffffff8100a5d3>] apic_timer_interrupt+0x13/0x20
 <EOI>  [<ffffffff810115fd>] ? mwait_idle+0x7a/0x87
 [<ffffffff810115af>] ? mwait_idle+0x2c/0x87
 [<ffffffff81008c1f>] cpu_idle+0xaa/0xe4
 [<ffffffff81427eb0>] start_secondary+0x253/0x294
---[ end trace 19d8162e5c74f492 ]---
ioatdma 0000:00:0f.0: Self-test copy timed out, disabling
ioatdma 0000:00:0f.0: Freeing 2 in use descriptors!
ioatdma 0000:00:0f.0: Intel(R) I/OAT DMA Engine init failed
ioatdma 0000:00:0f.0: can't derive routing for PCI INT A

> I was thinking in the BIOS, but appending iommu=off to the kernel
> command-line should also do the trick.

iommu=off cause the kernel not boot properly. BTW, that is why I lost
my machine remotely last night. There is some sata error keep printing on
the console. Let me try to collect that once I reboot the machine again.

> ...but the failure is not intermittent, right?

Happen every time.

>
> Where it fell over is a pretty straightforward usage of the dma engine and
> it is failing on the first transaction that the first channel issues to
> memory.  You should be able to 'modprobe ioatdma' after you boot and watch
> it fail again if my suspicion is correct... if the signature changes that
> would also be good to know.

The delta seems to be this line:
ioatdma 0000:00:0f.0: ioat2_set_chainaddr: chainaddr: ffffe000


Chris

Download attachment "dmesg" of type "application/octet-stream" (58752 bytes)