From: David Woodhouse <dwmw2@infradead.org>
To: Takao Indoh <indou.takao@jp.fujitsu.com>
Cc: kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
iommu@lists.linux-foundation.org
Subject: Re: [PATCH] intel-iommu: Synchronize gcmd value with global command register
Date: Thu, 04 Apr 2013 15:24:49 +0100 [thread overview]
Message-ID: <1365085489.28127.64.camel@i7.infradead.org> (raw)
In-Reply-To: <515D1429.40707@jp.fujitsu.com>
[-- Attachment #1: Type: text/plain, Size: 714 bytes --]
On Thu, 2013-04-04 at 14:48 +0900, Takao Indoh wrote:
>
> - DMAR fault messages floods and second kernel does not boot. Recently I
> saw similar report. https://lkml.org/lkml/2013/3/8/120
Right. So the fix for that is to make the subsequent errors silent,
until/unless we actually get a request to create a mapping for the given
device.
> - igb driver detectes error on linkup and kdump via network fails.
That's a driver bug, IIRC. It was failing to completely reset the
hardware. It's fixed now, isn't it?
> - On a certain platform, though kdump itself works, PCIe error like
> Unexpected Completion is detected and it gets hardware degraded.
More information required.
--
dwmw2
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 6171 bytes --]
next prev parent reply other threads:[~2013-04-04 14:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-21 1:32 Takao Indoh
2013-03-26 14:46 ` Joerg Roedel
2013-03-27 5:02 ` Takao Indoh
2013-03-27 10:31 ` Joerg Roedel
2013-04-01 5:45 ` Takao Indoh
2013-04-02 14:05 ` Joerg Roedel
2013-04-03 7:11 ` Takao Indoh
2013-04-03 8:24 ` David Woodhouse
2013-04-04 5:48 ` Takao Indoh
2013-04-04 14:24 ` David Woodhouse [this message]
2013-04-08 8:57 ` Takao Indoh
2013-04-05 11:06 ` Joerg Roedel
2013-04-10 4:47 ` Takao Indoh
2013-04-15 9:00 ` Takao Indoh
2013-04-15 10:18 ` Joerg Roedel
2013-04-17 8:48 ` Takao Indoh
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=1365085489.28127.64.camel@i7.infradead.org \
--to=dwmw2@infradead.org \
--cc=indou.takao@jp.fujitsu.com \
--cc=iommu@lists.linux-foundation.org \
--cc=kexec@lists.infradead.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
all inboxes | Powered by JetHome®