On Thu, Apr 18, 2019 at 12:22:55PM -0400, tedheadster wrote:
> On Thu, Apr 18, 2019 at 12:16 PM Christoph Hellwig wrote:
> >
> > On Wed, Apr 17, 2019 at 02:05:29PM -0400, tedheadster wrote:
> > > > Christoph,
> > > > your patch fixed it nicely. No more error messages when I boot with
> > > > 16G
On Thu, Apr 18, 2019 at 12:16 PM Christoph Hellwig wrote:
>
> On Wed, Apr 17, 2019 at 02:05:29PM -0400, tedheadster wrote:
> > > Christoph,
> > > your patch fixed it nicely. No more error messages when I boot with
> > > 16GiB enabled on a 32-bit PAE-enabled system.
> >
> > Christoph,
> > can y
On Wed, Apr 17, 2019 at 02:05:29PM -0400, tedheadster wrote:
> > Christoph,
> > your patch fixed it nicely. No more error messages when I boot with
> > 16GiB enabled on a 32-bit PAE-enabled system.
>
> Christoph,
> can you please submit this patch to be backported to the long-term
> kernels (4
On Sat, Oct 13, 2018 at 11:26 AM tedheadster wrote:
>
> > it seems like we do for some reason never actually enable swiotlb
> > for 32-bit x86. Before my commit the block bounce buffering papered
> > over that for networking, Please try this patch:
> >
> > diff --git a/arch/x86/kernel/pci-swiotl
> it seems like we do for some reason never actually enable swiotlb
> for 32-bit x86. Before my commit the block bounce buffering papered
> over that for networking, Please try this patch:
>
> diff --git a/arch/x86/kernel/pci-swiotlb.c b/arch/x86/kernel/pci-swiotlb.c
> index 661583662430..71c0b01
On Sat, Oct 13, 2018 at 10:09:52AM -0400, tedheadster wrote:
> Christoph,
> here is all of the newly patched dmesg output. I also added
> 'aic7xxx.a9c7xxx=verbose' for extra information.
Hi Matthew,
it seems like we do for some reason never actually enable swiotlb
for 32-bit x86. Before my com
Christoph,
here is all of the newly patched dmesg output. I also added
'aic7xxx.a9c7xxx=verbose' for extra information.
Matthew
[0.00] Linux version 4.18.12.pentium4-xeon-christoph+
(root@pentium4) (gcc version 5.4.0 (Gentoo 5.4.0-r4 p1.8, pie-0.6.5))
#525 SMP PREEMPT Sat Oct 13 09:49:3
Hi Ted,
thanks for the dmesg. This shows your HBA doesn't even support the
odd 39-bit addressing. Now the real question is why we don't use
swiotlb. For that I'd like to see the whole dmesg from the very
beinning if you have it. Also it seems this boot didn't have the
WARN_ON_ONCE I sent you a
> That isn't a limit, just a reporting clause - the real check is this
> line a little above:
>
> if (unlikely(dev && !dma_capable(dev, dma_addr, size))) {
>
> which is purely based on the dma mask. So for some reason we must
> be in 32-bit only mode for the dma-mask, and not actually enab
On Mon, Oct 01, 2018 at 04:57:39PM -0400, tedheadster wrote:
> Christoph,
> I was able to bisect this to your patch "scsi: reduce use of block
> bounce buffers". I am getting the error on a 32-bit Dell PowerEdge
> 6650. It has the aic7xxx integrated onto the motherboard.
>
> Again, here is the e
Christoph,
I was able to bisect this to your patch "scsi: reduce use of block
bounce buffers". I am getting the error on a 32-bit Dell PowerEdge
6650. It has the aic7xxx integrated onto the motherboard.
Again, here is the error:
aic7xxx :00:03.0: dma_direct_map_sg: overflow
0x0003ff8000
On Sun, Sep 30, 2018 at 07:28:50PM -0400, tedheadster wrote:
> Hannes,
> I'm getting the following error in a custom configured 4.18 32-bit
> x86 kernel supporting PAE, with 16GiB physical memory. It loops
> infinitely on the error.
>
> aic7xxx :00:03.0: dma_direct_map_sg: overflow
> 0x0
Hannes,
I'm getting the following error in a custom configured 4.18 32-bit
x86 kernel supporting PAE, with 16GiB physical memory. It loops
infinitely on the error.
aic7xxx :00:03.0: dma_direct_map_sg: overflow
0x0003ff80+65536 of device mask
I have tried enabling the follow
13 matches
Mail list logo
