From: Andrew Oakley <andrew@ado.is-a-geek.net>
To: Joerg Roedel <joro@8bytes.org>
Cc: iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [git pull] IOMMU Updates for v3.7-rc1
Date: Tue, 9 Oct 2012 22:45:32 +0100 [thread overview]
Message-ID: <20121009224532.1e515664@ado-amd-gentoo.moore.slainvet.net> (raw)
In-Reply-To: <20121005152312.GA4649@8bytes.org>
On Fri, 5 Oct 2012 17:23:12 +0200
Joerg Roedel <joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org> wrote:
> IOMMU Updates for Linux v3.7-rc1
>
> This time the IOMMU updates contain a bunch of fixes and cleanups to
> various IOMMU drivers and the DMA debug code. New features are the
> code for IRQ remapping support with the AMD IOMMU (preperation for
> that was already merged in the last release) and a debugfs interface
> to export some statistics in the NVidia Tegra IOMMU driver.
I'm getting a kernel panic here when I try to boot from master
(9aadf84) in in your IOMMU tree. I'll try booting the tagged commit in
case it's the merge that caused the problem but I'm not particularly
hopeful.
I have got interrupt remapping support enabled and the IOMMU enabled,
the chipset is an RD890 (890FX).
I think the relevant bit of the kernel output is here:
ACPI: Core revision 20120711
..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Kernel panic - not syncing: timer doesn't work through Interrupt-remapped IO-APIC
Pid: 1, comm: swapper/0 Not tainted 3.6.0+ #2
Call Trace:
[<ffffffff8163f617>] ? panic+0xc5/0x1d0
[<ffffffff8163f76e>] ? printk+0x4c/0x51
[<ffffffff81c96b52>] ? setup_IO_APIC+0x325/0x710
[<ffffffff81c947b5>] ? native_smp_prepare_cpus+0x2b9/0x334
[<ffffffff81c87b53>] ? kernel_init+0x59/0x190
[<ffffffff81643b84>] ? kernel_thread_helper+0x4/0x10
[<ffffffff81c87afa>] ? start_kernel+0x2c7/0x2c7
[<ffffffff81643b80>] ? gs_change+0x13/0x13
There is a patch to fix a similar problem (32ab31e) for the Intel IRQ
remapping code but I don't know if this is likely to be the same issue
or not.
I've posted the full kernel log, kernel config and lspci output in case
they are useful:
http://adoakley.name/amd-iommu/dmesg.txt
http://adoakley.name/amd-iommu/kernel_config.txt
http://adoakley.name/amd-iommu/lspci.txt
Thanks
--
Andrew Oakley
next prev parent reply other threads:[~2012-10-09 22:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-05 15:23 [git pull] IOMMU Updates for v3.7-rc1 Joerg Roedel
2012-10-09 21:45 ` Andrew Oakley [this message]
2012-10-10 7:30 ` Joerg Roedel
2012-10-10 8:58 ` Andrew Oakley
2012-10-10 13:32 ` Joerg Roedel
2012-10-10 19:11 ` Andrew Oakley
2012-10-10 22:02 ` Andrew Oakley
2012-10-10 22:05 ` [PATCH] iommu/amd: Workaround wrong IOAPIC devid in IVRS andrew
2012-10-11 9:32 ` [git pull] IOMMU Updates for v3.7-rc1 Joerg Roedel
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=20121009224532.1e515664@ado-amd-gentoo.moore.slainvet.net \
--to=andrew@ado.is-a-geek.net \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).