From: "Jan Beulich" <JBeulich@suse.com>
To: "Yuzhou (C)" <vitas.yuzhou@huawei.com>
Cc: "Zhangleiqiang (Trump)" <zhangleiqiang@huawei.com>,
"Luohao (brian)" <brian.luohao@huawei.com>,
Zhuangyuxin <zhuangyuxin@huawei.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
"Xiaoding (B)" <xiaoding1@huawei.com>,
roger.pau@citrix.com
Subject: Re: xen4.5 dom0pvh test failed
Date: Wed, 28 Jan 2015 09:45:09 +0000 [thread overview]
Message-ID: <54C8BDB5020000780005A384@mail.emea.novell.com> (raw)
In-Reply-To: <47498F109986134D9A5B42B82F405EBB7EDE60B0@SZXEMA502-MBX.china.huawei.com>
>>> On 28.01.15 at 10:19, <vitas.yuzhou@huawei.com> wrote:
> (1). Base on xen4.5, linux3.18.3, dom0pvh=1, dom0_mem=4096000 ; boot
> failed!
> From boot log, I think the disk device can not be scaned.
[ 13.990269] mpt2sas0: no suitable DMA mask for 0000:03:00.0
[ 13.990369] mpt2sas0: failure at drivers/scsi/mpt2sas/mpt2sas_scsih.c:8253/_scsih_probe()!
makes it pretty obvious where to continue looking. It doesn't look
like it's the problem fixed by David's series allowing arch overrides
to dma_get_required_mask(), so perhaps instrumenting the
driver's _base_config_dma_addressing() is the way to go.
Apart from that there appears to be a huge chunk of the log
missing (between these two messages:
[ 0.000000] ACPI: LAPIC (acpi_id[0x30] lapic_id[0xff] disabled
[ 13.438147] Freeing initrd memory: 12056K (ffff880002000000 - ffff880002bc6000)
) and hence it's impossible to tell whether you got a properly sized
SWIOTLB enabled.
Jan
next prev parent reply other threads:[~2015-01-28 9:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-27 2:27 xen4.5 dom0pvh test failed Yuzhou (C)
2015-01-27 8:12 ` Roger Pau Monné
2015-01-27 10:35 ` Yuzhou (C)
2015-01-27 10:52 ` Roger Pau Monné
2015-01-28 3:51 ` Yuzhou (C)
2015-01-28 9:19 ` Yuzhou (C)
2015-01-28 9:45 ` Jan Beulich [this message]
2015-01-28 9:32 ` Jan Beulich
2015-01-29 12:44 ` Yuzhou (C)
2015-01-29 15:36 ` Roger Pau Monné
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=54C8BDB5020000780005A384@mail.emea.novell.com \
--to=jbeulich@suse.com \
--cc=brian.luohao@huawei.com \
--cc=roger.pau@citrix.com \
--cc=vitas.yuzhou@huawei.com \
--cc=xen-devel@lists.xen.org \
--cc=xiaoding1@huawei.com \
--cc=zhangleiqiang@huawei.com \
--cc=zhuangyuxin@huawei.com \
/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.