On Fri, Jan 10, 2020 at 08:10:28AM +0100, Christian Zigotzky wrote:
> Hi All,
>
> The SCSI cards work again. [1, 2]
>
> Sorry for bothering you.
No problem, and sorry for not following up earlier. The Christmas
holiday and catch up phase led to a lot of delay.
Thanks a lot for taking care of t
https://bugzilla.kernel.org/show_bug.cgi?id=205201
Michael Ellerman (mich...@ellerman.id.au) changed:
What|Removed |Added
Status|RESOLVED|CLOSED
https://bugzilla.kernel.org/show_bug.cgi?id=205201
Roland (rj.ron...@gmail.com) changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolutio
https://bugzilla.kernel.org/show_bug.cgi?id=205201
--- Comment #17 from Roland (rj.ron...@gmail.com) ---
Kernel 5.5 alpha 1 fixed the issue with Dawicontrol DC-2976 UW SCSI board. Also
a RTL 8169 ethernet card which had similar type of problem with earlier kernels
works now with full (8 GB) Ram.
Hi All,
The SCSI cards work again. [1, 2]
Sorry for bothering you.
Thanks,
Christian
[1]
http://forum.hyperion-entertainment.com/viewtopic.php?f=58&p=49603&sid=1adf9e6d558c136c1ad4ff15c44212ba#p49599
[2] https://bugzilla.kernel.org/show_bug.cgi?id=205201
I think we have to wait to Roland’s test results with his SCSI PCI card.
Christian
Sent from my iPhone
> On 4. Dec 2019, at 09:56, Christoph Hellwig wrote:
>
>> On Wed, Nov 27, 2019 at 08:56:25AM +0200, Mike Rapoport wrote:
>>> On Tue, Nov 26, 2019 at 05:40:26PM +0100, Christoph Hellwig wrote:
On Wed, Nov 27, 2019 at 08:56:25AM +0200, Mike Rapoport wrote:
> On Tue, Nov 26, 2019 at 05:40:26PM +0100, Christoph Hellwig wrote:
> > On Tue, Nov 26, 2019 at 12:26:38PM +0100, Christian Zigotzky wrote:
> > > Hello Christoph,
> > >
> > > The PCI TV card works with your patch! I was able to patch y
On 27 November 2019 at 07:56 am, Mike Rapoport wrote:
Maybe we'll simply force bottom up allocation before calling
swiotlb_init()? Anyway, it's the last memblock allocation.
diff --git a/arch/powerpc/mm/mem.c b/arch/powerpc/mm/mem.c
index 62f74b1b33bd..771e6cf7e2b9 100644
--- a/arch/powerpc/mm
On Wed, Nov 27, 2019 at 08:56:25AM +0200, Mike Rapoport wrote:
> Maybe we'll simply force bottom up allocation before calling
> swiotlb_init()? Anyway, it's the last memblock allocation.
That should work, but I don't think it is the proper fix. The underlying
issue here is that ZONE_DMA/DMA32 siz
On Tue, Nov 26, 2019 at 05:40:26PM +0100, Christoph Hellwig wrote:
> On Tue, Nov 26, 2019 at 12:26:38PM +0100, Christian Zigotzky wrote:
> > Hello Christoph,
> >
> > The PCI TV card works with your patch! I was able to patch your Git kernel
> > with the patch above.
> >
> > I haven't found any err
On Tue, Nov 26, 2019 at 12:26:38PM +0100, Christian Zigotzky wrote:
> Hello Christoph,
>
> The PCI TV card works with your patch! I was able to patch your Git kernel
> with the patch above.
>
> I haven't found any error messages in the dmesg yet.
Thanks. Unfortunately this is a bit of a hack as
On 25 November 2019 at 10:32 am, Mike Rapoport wrote:
On Mon, Nov 25, 2019 at 08:39:23AM +0100, Christoph Hellwig wrote:
On Sat, Nov 23, 2019 at 12:42:27PM +0100, Christian Zigotzky wrote:
Hello Christoph,
Please find attached the dmesg of your Git kernel.
Thanks. It looks like on your platf
On 25 November 2019 at 08:39 am, Christoph Hellwig wrote:
On Sat, Nov 23, 2019 at 12:42:27PM +0100, Christian Zigotzky wrote:
Hello Christoph,
Please find attached the dmesg of your Git kernel.
Thanks. It looks like on your platform the swiotlb buffer isn't
actually addressable based on the b
On 25 November 2019 at 10:32 am, Mike Rapoport wrote:
On Mon, Nov 25, 2019 at 08:39:23AM +0100, Christoph Hellwig wrote:
On Sat, Nov 23, 2019 at 12:42:27PM +0100, Christian Zigotzky wrote:
Hello Christoph,
Please find attached the dmesg of your Git kernel.
Thanks. It looks like on your platf
On 25 November 2019 at 08:39 am, Christoph Hellwig wrote:
On Sat, Nov 23, 2019 at 12:42:27PM +0100, Christian Zigotzky wrote:
Hello Christoph,
Please find attached the dmesg of your Git kernel.
Thanks. It looks like on your platform the swiotlb buffer isn't
actually addressable based on the b
On Mon, Nov 25, 2019 at 08:39:23AM +0100, Christoph Hellwig wrote:
> On Sat, Nov 23, 2019 at 12:42:27PM +0100, Christian Zigotzky wrote:
> > Hello Christoph,
> >
> > Please find attached the dmesg of your Git kernel.
>
> Thanks. It looks like on your platform the swiotlb buffer isn't
> actually a
On Sat, Nov 23, 2019 at 12:42:27PM +0100, Christian Zigotzky wrote:
> Hello Christoph,
>
> Please find attached the dmesg of your Git kernel.
Thanks. It looks like on your platform the swiotlb buffer isn't
actually addressable based on the bus dma mask limit, which is rather
interesting. swiotlb
On 21 November 2019 at 07:02 pm, Christoph Hellwig wrote:
On Thu, Nov 21, 2019 at 05:34:48PM +0100, Christian Zigotzky wrote:
I modified the patch and compiled a new RC8 of kernel 5.4 today. (patch
attached)
We have to wait to Rolands test results with his SCSI PCI card. I tested it
today but m
https://bugzilla.kernel.org/show_bug.cgi?id=205201
--- Comment #16 from Christian Zigotzky (chzigot...@xenosoft.de) ---
Created attachment 286031
--> https://bugzilla.kernel.org/attachment.cgi?id=286031&action=edit
dmesg of Christoph's Git kernel
Christoph Hellwig wrote:
I think we have two so
On 21. Nov 2019, at 19:02, Christoph Hellwig wrote:
On Thu, Nov 21, 2019 at 05:34:48PM +0100, Christian Zigotzky wrote:
I modified the patch and compiled a new RC8 of kernel 5.4 today. (patch
attached)
We have to wait to Rolands test results with his SCSI PCI card. I tested it
today but my TV
On Thu, Nov 21, 2019 at 05:34:48PM +0100, Christian Zigotzky wrote:
> I modified the patch and compiled a new RC8 of kernel 5.4 today. (patch
> attached)
>
> We have to wait to Rolands test results with his SCSI PCI card. I tested it
> today but my TV card doesn't work with this patch.
I think w
Am 21.11.19 um 14:33 schrieb Robin Murphy:
On 21/11/2019 12:21 pm, Christian Zigotzky wrote:
On 21 November 2019 at 01:16 pm, Christian Zigotzky wrote:
On 21 November 2019 at 08:29 am, Christoph Hellwig wrote:
On Sat, Nov 16, 2019 at 08:06:05AM +0100, Christian Zigotzky wrote:
/*
* DMA add
On 21/11/2019 12:21 pm, Christian Zigotzky wrote:
On 21 November 2019 at 01:16 pm, Christian Zigotzky wrote:
On 21 November 2019 at 08:29 am, Christoph Hellwig wrote:
On Sat, Nov 16, 2019 at 08:06:05AM +0100, Christian Zigotzky wrote:
/*
* DMA addressing mode.
*
* 0 : 32 bit addressing
On 21 November 2019 at 01:16 pm, Christian Zigotzky wrote:
On 21 November 2019 at 08:29 am, Christoph Hellwig wrote:
On Sat, Nov 16, 2019 at 08:06:05AM +0100, Christian Zigotzky wrote:
/*
* DMA addressing mode.
*
* 0 : 32 bit addressing for all chips.
* 1 : 40 bit addressing when sup
On 21 November 2019 at 08:29 am, Christoph Hellwig wrote:
On Sat, Nov 16, 2019 at 08:06:05AM +0100, Christian Zigotzky wrote:
/*
* DMA addressing mode.
*
* 0 : 32 bit addressing for all chips.
* 1 : 40 bit addressing when supported by chip.
* 2 : 64 bit addressing when supported by
On Sat, Nov 16, 2019 at 08:06:05AM +0100, Christian Zigotzky wrote:
> /*
> * DMA addressing mode.
> *
> * 0 : 32 bit addressing for all chips.
> * 1 : 40 bit addressing when supported by chip.
> * 2 : 64 bit addressing when supported by chip,
> * limited to 16 segments of 4 GB -> 64
FYI: Source files of the Dawicontrol DC 2976 UW SCSI board (PCI):
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/scsi/sym53c8xx_2?h=v5.4-rc7
/*
* DMA addressing mode.
*
* 0 : 32 bit addressing for all chips.
* 1 : 40 bit addressing when supported by chip.
https://bugzilla.kernel.org/show_bug.cgi?id=205201
--- Comment #15 from Christian Zigotzky (chzigot...@xenosoft.de) ---
FYI: Souce files of the Dawicontrol DC 2976 UW SCSI board (PCI):
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/scsi/sym53c8xx_2?h=v5.4-rc7
/*
https://bugzilla.kernel.org/show_bug.cgi?id=205201
--- Comment #14 from Christian Zigotzky (chzigot...@xenosoft.de) ---
Created attachment 285889
--> https://bugzilla.kernel.org/attachment.cgi?id=285889&action=edit
Patch for renaming the GFP_DMA32 to GFP_DMA
Hi All,
The issue with the BT878 TV
https://bugzilla.kernel.org/show_bug.cgi?id=205201
--- Comment #13 from Christian Zigotzky (chzigot...@xenosoft.de) ---
Christoph,
Now, I can definitely say that this patch does not solve the issue.
Do you have another patch for testing or shall I bisect?
Thanks,
Christian
--
You are receivin
https://bugzilla.kernel.org/show_bug.cgi?id=205201
--- Comment #12 from Christian Zigotzky (chzigot...@xenosoft.de) ---
Hi Christoph,
I have seen that I have activated the kernel config option
CONFIG_ARCH_DMA_ADDR_T_64BIT. That means your code in your patch won't work if
this kernel option is ena
https://bugzilla.kernel.org/show_bug.cgi?id=205201
--- Comment #11 from Christian Zigotzky (chzigot...@xenosoft.de) ---
Christoph,
Do you have another patch for testing or shall I bisect?
Thanks,
Christian
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=205201
--- Comment #10 from Christian Zigotzky (chzigot...@xenosoft.de) ---
Created attachment 285815
--> https://bugzilla.kernel.org/attachment.cgi?id=285815&action=edit
Kernel 5.4-rc6 config for the Cyrus+ board and for the QEMU ppce500 board (CPU:
P
https://bugzilla.kernel.org/show_bug.cgi?id=205201
--- Comment #9 from Christian Zigotzky (chzigot...@xenosoft.de) ---
Created attachment 285813
--> https://bugzilla.kernel.org/attachment.cgi?id=285813&action=edit
dmesg fsl p5040
--
You are receiving this mail because:
You are watching the ass
https://bugzilla.kernel.org/show_bug.cgi?id=205201
--- Comment #8 from Christian Zigotzky (chzigot...@xenosoft.de) ---
Trace:
[ 462.783184] Call Trace:
[ 462.783187] [c001c6c67420] [c00b3358] .report_addr+0xb8/0xc0
(unreliable)
[ 462.783192] [c001c6c67490] [c00b351c]
.d
https://bugzilla.kernel.org/show_bug.cgi?id=205201
--- Comment #7 from Christian Zigotzky (chzigot...@xenosoft.de) ---
Unfortunately this patch doesn't solve the issue.
Error message:
[6.041163] bttv: driver version 0.9.19 loaded
[6.041167] bttv: using 8 buffers with 2080k (520
https://bugzilla.kernel.org/show_bug.cgi?id=205201
--- Comment #6 from Christian Zigotzky (chzigot...@xenosoft.de) ---
FYI because of the issue with some PCI cards (SCSI, TV cards etc):
Christoph Hellwig wrote:
Can you send me the .config and a dmesg? And in the meantime try the patch
below?
>F
https://bugzilla.kernel.org/show_bug.cgi?id=205201
--- Comment #5 from Christophe Leroy (christophe.le...@c-s.fr) ---
I guess:
git bisect bad 8d6973327
git bisect good v4.20
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=205201
--- Comment #4 from Christian Zigotzky (chzigot...@xenosoft.de) ---
Yes, I can. Could you please post the correct commits for starting bisect?
git bisect start
git bisect good ?
git bisect bad ?
Thanks
--
You are receiving this mail because:
https://bugzilla.kernel.org/show_bug.cgi?id=205201
Christophe Leroy (christophe.le...@c-s.fr) changed:
What|Removed |Added
CC||christophe.le
Hello,
Kernel 5.4-rc5: Error message without limitation to 3.5G RAM:
[ 25.654852] bttv 1000:04:05.0: overflow 0xfe077000+4096 of DMA mask
bus mask df00
The kernel configured the bttv card for DMA in the upper region of RAM but the
device believes that it only supports 32-bit
https://bugzilla.kernel.org/show_bug.cgi?id=205201
--- Comment #2 from Christian Zigotzky (chzigot...@xenosoft.de) ---
Error message without limitation to 3.5G RAM:
[ 25.654852] bttv 1000:04:05.0: overflow 0xfe077000+4096 of DMA mask
bus mask df00
The kernel configured the
Hello,
The bug with some PCI devices if you have more than 3.5G installed still exist
in the RC5. Could you please look in the following bug report.
Link: https://bugzilla.kernel.org/show_bug.cgi?id=205201
Thanks,
Christian
https://bugzilla.kernel.org/show_bug.cgi?id=205201
--- Comment #1 from Christian Zigotzky (chzigot...@xenosoft.de) ---
I have the same problem with my analog PCI TV card Typhoon TView RDS + FM
Stereo (BT878 chip) in my AmigaOne X5000. It only works with reducing the mem
size to 3500MB (mem=3500M).
44 matches
Mail list logo