On 10/15/20 12:48 AM, Christoph Hellwig wrote:
> On Sun, Oct 11, 2020 at 05:53:37AM +1100, Stephen Rothwell wrote:
>> Hi Naresh,
>>
>> Just adding Christoph and Jim to cc]
>
> Well, a Cc doesn't help on its own. Can you send an actual bug
> report including the setup, warnings and error
On Sun, Oct 11, 2020 at 05:53:37AM +1100, Stephen Rothwell wrote:
> Hi Naresh,
>
> Just adding Christoph and Jim to cc]
Well, a Cc doesn't help on its own. Can you send an actual bug
report including the setup, warnings and error messages, a bisection
result and the usual suspects?
Hello,
Fabio Estevam wrote on Wed, 14 Oct 2020 09:28:49
-0300:
> Hi Florian,
>
> On Sun, Oct 11, 2020 at 6:59 PM Florian Fainelli wrote:
>
> > however the NAND warning still remains. Someone else familiar with these
> > NXP development boards should fix the DTS so as to provide the require
>
Hi Florian,
On Sun, Oct 11, 2020 at 6:59 PM Florian Fainelli wrote:
> however the NAND warning still remains. Someone else familiar with these
> NXP development boards should fix the DTS so as to provide the require
> ECC strength property.
The ECC NAND warning looks like a regression.
I had
+Abhimanyu, Ioana, Fabio
On 10/11/2020 1:36 PM, Jim Quinlan wrote:
On Sat, Oct 10, 2020 at 2:53 PM Stephen Rothwell wrote:
Hi Naresh,
Just adding Christoph and Jim to cc]
On Fri, 9 Oct 2020 19:26:24 +0530 Naresh Kamboju
wrote:
On Fri, 9 Oct 2020 at 19:24, Naresh Kamboju wrote:
On
On Sat, Oct 10, 2020 at 2:53 PM Stephen Rothwell wrote:
>
> Hi Naresh,
>
> Just adding Christoph and Jim to cc]
>
> On Fri, 9 Oct 2020 19:26:24 +0530 Naresh Kamboju
> wrote:
> >
> > On Fri, 9 Oct 2020 at 19:24, Naresh Kamboju
> > wrote:
> > >
> > >
> > >
> > > On Thu, 24 Sep 2020 at 15:26,
Hi Naresh,
Just adding Christoph and Jim to cc]
On Fri, 9 Oct 2020 19:26:24 +0530 Naresh Kamboju
wrote:
>
> On Fri, 9 Oct 2020 at 19:24, Naresh Kamboju wrote:
> >
> >
> >
> > On Thu, 24 Sep 2020 at 15:26, Joerg Roedel wrote:
> > >
> > > On Thu, Sep 24, 2020 at 10:36:47AM +0100, Robin
On Fri, 9 Oct 2020 at 19:24, Naresh Kamboju wrote:
>
>
>
> On Thu, 24 Sep 2020 at 15:26, Joerg Roedel wrote:
> >
> > On Thu, Sep 24, 2020 at 10:36:47AM +0100, Robin Murphy wrote:
> > > Yes, the issue was introduced by one of the changes in "dma-mapping:
> > > introduce DMA range map, supplanting
On Thu, 24 Sep 2020 at 15:26, Joerg Roedel wrote:
>
> On Thu, Sep 24, 2020 at 10:36:47AM +0100, Robin Murphy wrote:
> > Yes, the issue was introduced by one of the changes in "dma-mapping:
> > introduce DMA range map, supplanting dma_pfn_offset", so it only existed in
> > the dma-mapping/for-next
On Thu, Sep 24, 2020 at 10:36:47AM +0100, Robin Murphy wrote:
> Yes, the issue was introduced by one of the changes in "dma-mapping:
> introduce DMA range map, supplanting dma_pfn_offset", so it only existed in
> the dma-mapping/for-next branch anyway.
Okay, alright then.
On 2020-09-24 10:25, Joerg Roedel wrote:
Hi Robin,
On Thu, Sep 24, 2020 at 10:08:46AM +0100, Robin Murphy wrote:
This should be fixed by
https://lore.kernel.org/linux-iommu/daedc9364a19dc07487e4d07b8768b1e5934abd4.1600700881.git.robin.mur...@arm.com/T/#u
(already in linux-next).
Thanks! The
Hi Robin,
On Thu, Sep 24, 2020 at 10:08:46AM +0100, Robin Murphy wrote:
> This should be fixed by
> https://lore.kernel.org/linux-iommu/daedc9364a19dc07487e4d07b8768b1e5934abd4.1600700881.git.robin.mur...@arm.com/T/#u
> (already in linux-next).
Thanks! The question remains why this goes through
Driver
[2.250338] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
[2.256403] e1000e :01:00.0: Adding to iommu group 0
[2.261733] arm-smmu 500.iommu: Cannot accommodate DMA offset
for IOMMU page tables
[2.269752] Unable to handle kernel NULL pointer dereference at
virtual
ing
> [2.222141] hns3: Hisilicon Ethernet Network Driver for Hip08
> Family - version
> [2.229371] hns3: Copyright (c) 2017 Huawei Corporation.
> [2.234716] e1000: Intel(R) PRO/1000 Network Driver
> [2.239598] e1000: Copyright (c) 1999-2006 Intel Corporation.
> [2.24
On 2020-09-21 14:20, Naresh Kamboju wrote:
[...]
[2.256403] e1000e :01:00.0: Adding to iommu group 0
[2.261733] arm-smmu 500.iommu: Cannot accommodate DMA offset
for IOMMU page tables
Ah, I know what's going on there - the dma_range_map stuff has
overlooked a subtlety
: Copyright(c) 1999 - 2015 Intel Corporation.
[2.256403] e1000e :01:00.0: Adding to iommu group 0
[2.261733] arm-smmu 500.iommu: Cannot accommodate DMA offset
for IOMMU page tables
[2.269752] Unable to handle kernel NULL pointer dereference at
virtual address
16 matches
Mail list logo
