From: WANG Chao <chaowang@redhat.com>
To: Yinghai Lu <yinghai@kernel.org>
Cc: CAI Qian <caiqian@redhat.com>, kexec <kexec@lists.infradead.org>,
LKML <linux-kernel@vger.kernel.org>,
"H. Peter Anvin" <hpa@linux.intel.com>,
Dave Young <dyoung@redhat.com>, Vivek Goyal <vgoyal@redhat.com>
Subject: Re: 3.9-rc1: crash kernel panic - not syncing: Can not allocate SWIOTLB buffer earlier and can't now provide you with the DMA bounce buffer
Date: Fri, 08 Mar 2013 15:33:22 +0800 [thread overview]
Message-ID: <51399442.1080609@redhat.com> (raw)
In-Reply-To: <CAE9FiQVPaG5P7mG9HoFzCkaxF62hkU5hEtq_FhdT7n+38aNs9A@mail.gmail.com>
On 03/08/2013 03:27 PM, Yinghai Lu wrote:
> On Thu, Mar 7, 2013 at 11:20 PM, WANG Chao <chaowang@redhat.com> wrote:
>>>
>>> looks like your system DO have DMAR table, please enable dmar
>>> remapping in your kernel config.
>>
>> I've already got following config:
>> CONFIG_DMAR_TABLE=y
>> CONFIG_INTEL_IOMMU=y
>> CONFIG_IRQ_REMAP=y
>>
>> but I don't have intel_iommu=on in kernel cmdline. IIRC, iommu will prevent
>> 2nd kernel from booting ...
>
> Did you put intel_iommu=on on first and second cpu both?
I tried, 2nd kernel didn't boot and keep splitting errors like these:
[ 2.106939] DMAR: No ATSR found
[ 2.110121] IOMMU 0 0xfed90000: using Queued invalidation
[ 2.115522] IOMMU 1 0xfed91000: using Queued invalidation
[ 2.120919] IOMMU: Setting RMRR:
[ 2.124162] IOMMU: Setting identity map for device 0000:00:02.0 [0xab800000
- 0xaf9fffff]
[ 2.133099] IOMMU: Setting identity map for device 0000:00:1d.0 [0xaac95000
- 0xaacb2fff]
[ 2.141305] IOMMU: Setting identity map for device 0000:00:1a.0 [0xaac95000
- 0xaacb2fff]
[ 2.149503] IOMMU: Setting identity map for device 0000:00:14.0 [0xaac95000
- 0xaacb2fff]
[ 2.157690] IOMMU: Prepare 0-16MiB unity mapping for LPC
[ 2.163011] IOMMU: Setting identity map for device 0000:00:1f.0 [0x0 - 0xffffff
[Errors, here we go]
[ 2.170932] dmar: DRHD: handling fault status reg 3
[ 2.170933] PCI-DMA: Intel(R) Virtualization Technology for Directed I/O
[ 2.182486] dmar: DMAR:[DMA Write] Request device [00:02.0] fault addr ffffe000
[ 2.182486] DMAR:[fault reason 05] PTE Write access is not set
[ 2.195705] dmar: DRHD: handling fault status reg 3
[ 2.200570] dmar: DMAR:[DMA Read] Request device [00:02.0] fault addr ff873000
[ 2.200570] DMAR:[fault reason 06] PTE Read access is not set
[ 2.213618] dmar: DRHD: handling fault status reg 3
[..]
Thanks,
WANG Chao
>
> Thanks
>
> Yinghai
>
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2013-03-08 7:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <51397D1D.5030602@redhat.com>
2013-03-08 6:03 ` 3.9-rc1: crash kernel panic - not syncing: Can not allocate SWIOTLB buffer earlier and can't now provide you with the DMA bounce buffer CAI Qian
2013-03-08 6:32 ` Yinghai Lu
2013-03-08 6:36 ` Yinghai Lu
2013-03-08 7:20 ` WANG Chao
2013-03-08 7:27 ` Yinghai Lu
2013-03-08 7:33 ` WANG Chao [this message]
2013-03-08 7:50 ` Yinghai Lu
[not found] ` <5139D5A0.6000600@redhat.com>
2013-03-08 18:24 ` Yinghai Lu
2013-03-08 19:39 ` Yinghai Lu
2013-03-11 3:42 ` WANG Chao
2013-03-11 13:14 ` Konrad Rzeszutek Wilk
2013-03-08 7:52 ` 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=51399442.1080609@redhat.com \
--to=chaowang@redhat.com \
--cc=caiqian@redhat.com \
--cc=dyoung@redhat.com \
--cc=hpa@linux.intel.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vgoyal@redhat.com \
--cc=yinghai@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