All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joerg Roedel <joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
To: Andrew Oakley <andrew-WCNZvuCk18ErewFq2K+F1F6hYfS7NtTn@public.gmane.org>
Cc: iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [git pull] IOMMU Updates for v3.7-rc1
Date: Wed, 10 Oct 2012 09:30:22 +0200	[thread overview]
Message-ID: <20121010073022.GB16151@8bytes.org> (raw)
In-Reply-To: <20121009224532.1e515664-IjT0q3EH84DI7ueSY2wKCeWwSe/Luo9VmGrBRn/+eNheoWH0uzbU5w@public.gmane.org>

Hi Andrew,

On Tue, Oct 09, 2012 at 10:45:32PM +0100, Andrew Oakley wrote:
> On Fri, 5 Oct 2012 17:23:12 +0200
> Joerg Roedel <joro-zLv9SwRftAIdnm+yROfE0A-XMD5yJDbdMReXY1tMh2IBg@public.gmane.org> wrote:

> 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.

Can you please boot with 'amd_iommu_dump nointremap' on your kernel
command line and post dmesg? I guess your ACPI table is broken in some
way.

The problem seen on VT-d exists on AMD too, but I have a workaround for
that in the code already. This must be something else...

Thanks,

	Joerg

WARNING: multiple messages have this Message-ID (diff)
From: Joerg Roedel <joro@8bytes.org>
To: Andrew Oakley <andrew@ado.is-a-geek.net>
Cc: iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [git pull] IOMMU Updates for v3.7-rc1
Date: Wed, 10 Oct 2012 09:30:22 +0200	[thread overview]
Message-ID: <20121010073022.GB16151@8bytes.org> (raw)
In-Reply-To: <20121009224532.1e515664@ado-amd-gentoo.moore.slainvet.net>

Hi Andrew,

On Tue, Oct 09, 2012 at 10:45:32PM +0100, Andrew Oakley wrote:
> On Fri, 5 Oct 2012 17:23:12 +0200
> Joerg Roedel <joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org> wrote:

> 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.

Can you please boot with 'amd_iommu_dump nointremap' on your kernel
command line and post dmesg? I guess your ACPI table is broken in some
way.

The problem seen on VT-d exists on AMD too, but I have a workaround for
that in the code already. This must be something else...

Thanks,

	Joerg



  parent reply	other threads:[~2012-10-10  7:30 UTC|newest]

Thread overview: 16+ 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-05 15:23 ` Joerg Roedel
2012-10-09 21:45 ` Andrew Oakley
     [not found]   ` <20121009224532.1e515664-IjT0q3EH84DI7ueSY2wKCeWwSe/Luo9VmGrBRn/+eNheoWH0uzbU5w@public.gmane.org>
2012-10-10  7:30     ` Joerg Roedel [this message]
2012-10-10  7:30       ` Joerg Roedel
2012-10-10  8:58       ` Andrew Oakley
     [not found]         ` <20121010095823.140fdd98-IjT0q3EH84DI7ueSY2wKCeWwSe/Luo9VmGrBRn/+eNheoWH0uzbU5w@public.gmane.org>
2012-10-10 13:32           ` Joerg Roedel
2012-10-10 13:32             ` Joerg Roedel
     [not found]             ` <20121010133249.GC16151-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2012-10-10 19:11               ` Andrew Oakley
2012-10-10 19:11                 ` Andrew Oakley
     [not found]                 ` <20121010201131.091d5a1f-IjT0q3EH84DI7ueSY2wKCeWwSe/Luo9VmGrBRn/+eNheoWH0uzbU5w@public.gmane.org>
2012-10-10 22:02                   ` Andrew Oakley
2012-10-10 22:02                     ` Andrew Oakley
     [not found]                     ` <20121010230231.2fb3c3b9-IjT0q3EH84DI7ueSY2wKCeWwSe/Luo9VmGrBRn/+eNheoWH0uzbU5w@public.gmane.org>
2012-10-10 22:05                       ` [PATCH] iommu/amd: Workaround wrong IOAPIC devid in IVRS andrew-WCNZvuCk18ErewFq2K+F1F6hYfS7NtTn
2012-10-10 22:05                         ` andrew
2012-10-11  9:32                       ` [git pull] IOMMU Updates for v3.7-rc1 Joerg Roedel
2012-10-11  9:32                         ` 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=20121010073022.GB16151@8bytes.org \
    --to=joro-zlv9swrftaidnm+yrofe0a@public.gmane.org \
    --cc=andrew-WCNZvuCk18ErewFq2K+F1F6hYfS7NtTn@public.gmane.org \
    --cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.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.