From: Don Brace <brace77070@gmail.com>
To: Hannes Reinecke <hare@suse.de>,
"linux-scsi@vger.kernel.org" <Linux-scsi@vger.kernel.org>
Cc: Joerg Roedel <jroedel@suse.de>, Borislav Petkov <bp@suse.de>
Subject: Re: hpsa failure with 4.3.0-rc1
Date: Wed, 30 Sep 2015 09:32:50 -0500 [thread overview]
Message-ID: <560BF292.6090209@pmcs.com> (raw)
In-Reply-To: <560B9202.9080703@suse.de>
I reported this a little while ago:
http://marc.info/?l=linux-kernel&m=144284810906949&w=2
It did clear up between rc1 and rc3.
Not sure what changes were applied in-between.
On 09/30/2015 02:40 AM, Hannes Reinecke wrote:
> Hi all,
>
> trying to boot 4.3.0-rc1 on a system with hpsa results in a swiotlb
> failure:
>
> hpsa 0000:22:00.0: Logical aborts not supported
> hpsa 0000:22:00.0: HP SSD Smart Path aborts not supported
> hpsa 0000:22:00.0: swiotlb buffer is full (sz: 786432 bytes)
> swiotlb: coherent allocation failed for device 0000:22:00.0 size=
> 786432
> CPU: 43 PID: 566 Comm: systemd-udevd Not tainted 4.3.0-rc1-default+ #358
> Hardware name: HP ProLiant BL660c Gen8, BIOS I32 08/20/2012
> ffff88181c314098 ffff8810194cba40 ffffffff8138fad2 00000000000c0
> ffff8810194cba80 ffffffff813ba3d9 ffff881000000008 0000000000000
> 220
> ffff88181c314098 00000000000c0000 ffff8810184101e8 ffff881018410
> 000
> Call Trace:
> [<ffffffff8138fad2>] dump_stack+0x4b/0x69
> [<ffffffff813ba3d9>] swiotlb_alloc_coherent+0x149/0x160
> [<ffffffff8104b7ae>] x86_swiotlb_alloc_coherent+0x3e/0x50
> [<ffffffffa030ef45>] hpsa_init_one+0x915/0x1c90 [hpsa]
> [<ffffffff810d694c>] ? rcu_read_lock_sched_held+0x8c/0xa0
> [<ffffffff813d8550>] local_pci_probe+0x40/0xa0
> [<ffffffff813d951b>] ? pci_match_device+0xdb/0x100
>
> 4.2.0-rc3 worked fine here.
> Needless to say, enabling IOMMU makes the problem go away :-)
>
> Cheers,
>
> Hannes
prev parent reply other threads:[~2015-09-30 14:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-30 7:40 hpsa failure with 4.3.0-rc1 Hannes Reinecke
2015-09-30 9:14 ` Borislav Petkov
2015-09-30 14:32 ` Don Brace [this message]
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=560BF292.6090209@pmcs.com \
--to=brace77070@gmail.com \
--cc=Linux-scsi@vger.kernel.org \
--cc=bp@suse.de \
--cc=hare@suse.de \
--cc=jroedel@suse.de \
/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).