age **refcounted_page)
> +{
> +bool writable;
> +
> +return __kvm_faultin_pfn(slot, gfn, FOLL_WRITE, &writable,
> refcounted_page);
> +}
> +
> int kvm_read_guest_page(struct kvm *kvm, gfn_t gfn, void *data, int offset,
> int len);
> int kvm_read_guest(struct kvm *kvm, gpa_t gpa, void *data, unsigned long len);
>
> base-commit: 2c3412e999738bfd60859c493ff47f5c268814a3
> --
This patch works. Tested-by: Christian Zigotzky
Thanks
gfn_t gfn, struct page **refcounted_page)
> +{
> +bool writable;
> +
> +return __kvm_faultin_pfn(slot, gfn, FOLL_WRITE, &writable,
> refcounted_page);
> +}
> +
> int kvm_read_guest_page(struct kvm *kvm, gfn_t gfn, void *data, int offset,
>int len);
> int kvm_read_guest(struct kvm *kvm, gpa_t gpa, void *data, unsigned long len);
>
> base-commit: 2c3412e999738bfd60859c493ff47f5c268814a3
> --
This patch works. Tested-by: Christian Zigotzky
Thanks
On 01/01/25 14:30, Christian Zigotzky wrote:
Hello Paolo,
First, I wish you a Happy New Year. Thanks a lot for your patch! I
patched the RC5 of kernel 6.13 with your patch and KVM HV works! :-)
kvm_hv_final.patch:
virt/kvm/kvm_main.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions
Hello Paolo,
First, I wish you a Happy New Year. Thanks a lot for your patch! I
patched the RC5 of kernel 6.13 with your patch and KVM HV works! :-)
kvm_hv_final.patch:
virt/kvm/kvm_main.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/virt/kvm/kvm_main.c b/virt/kvm/
Hi All,
I have compiled the RC5 of kernel 6.13 [1] with the latest revert patch. [2]
After that, I successfully tested the following QEMU/KVM HV components.
- Guest performance: good
- Guest boot time: short
- KVM HV works (-enable-kvm)
- SMP works (-smp 4)
- QEMU User Networking (SLIRP) via Vi
Hi All,
I found out which area is responsible for the KVM HV issue while
reducing the revert patch.
If I replace the following line in the file
'a/arch/powerpc/kvm/e500_mmu_host.c' then KVM HV works again.
- pfn = __kvm_faultin_pfn(slot, gfn, FOLL_WRITE, NULL, &page);
+ pfn =
On 27/12/24 06:20, Paolo Bonzini wrote:
Please test the kvm-e500-bisection-rebase branch of
https://git.kernel.org/pub/scm/virt/kvm/kvm.git, which has the patch
applied already:
- first test commit 0096d3855a5e80b9d4e43e5a291e8c79aa4abbc2, and report if it
fails
- then the entire branch, bise
On 26/12/24 08:00, Paolo Bonzini wrote:
Il mer 25 dic 2024, 13:48 Christian Zigotzky <mailto:chzigot...@xenosoft.de>> ha scritto:
> But do you see anything on the host dmesg (without and with the
> patch), for example a WARN?
Unfortunately no log during the start
On 24/12/24 12:42, Paolo Bonzini wrote:
On 12/24/24 12:05, Christian Zigotzky wrote:
Hello Paolo,
Thanks a lot for your patch.
I tested it with the RC4 of kernel 6.13 today but unfortunately it
doesn't solve the KVM HV issue. The guest system doesn't boot and I
can't see any
On 23/12/24 16:37, Paolo Bonzini wrote:
On Mon, Dec 23, 2024 at 3:41 PM Christian Zigotzky
wrote:
Bisecting: a merge base must be tested
[e9001a382fa2c256229adc68d55212028b01d515] Merge tag
'kvmarm-fixes-6.12-3' of
git://git.kernel.org/pub/scm/linux/kernel/git/kvmarm/kvmarm into
On 22/12/24 18:49, Paolo Bonzini wrote:
>
> Go on with
> git checkout -b bisection-rebase b467ab82a9fde4b46c0cd2c299220857afb0e0d4
> git rebase v6.12
> # check that it boots. if it fails to boot, please report this. if it
succeds, continue:
> git bisect start
> git bisect bad bisection-rebase
>
On 22/12/24 09:55, Paolo Bonzini wrote:
On 20/12/24 13:48, Christian Zigotzky wrote:
Maybe the kvm updates [1] from Paolo Bonzini are responsible for this
issue.
+ Paolo Bonzini
I have found some changes in the e500_mmu_host.c file
(a/arch/powerpc/ kvm/e500_mmu_host.c) in the kvm updates [1
On 20/12/24 13:08 Christian Zigotzky wrote:
On 18/12/24 15:41, Christian Zigotzky wrote:
On 18/12/24 12:10, Christian Zigotzky wrote:
Hello,
The KVM HV host module doesn't work anymore since the PowerPC
updates 6.13-1 [1] and PowerPC MM updates [2].
We have tested it with our FSL
On 18/12/24 15:41, Christian Zigotzky wrote:
On 18/12/24 12:10, Christian Zigotzky wrote:
Hello,
The KVM HV host module doesn't work anymore since the PowerPC updates
6.13-1 [1] and PowerPC MM updates [2].
We have tested it with our FSL P5020/P5040 boards [3].
The guest kernel doesn&#
On 18/12/24 12:10, Christian Zigotzky wrote:
Hello,
The KVM HV host module doesn't work anymore since the PowerPC updates
6.13-1 [1] and PowerPC MM updates [2].
We have tested it with our FSL P5020/P5040 boards [3].
The guest kernel doesn't boot. There is no output via
Hello,
The KVM HV host module doesn't work anymore since the PowerPC updates
6.13-1 [1] and PowerPC MM updates [2].
We have tested it with our FSL P5020/P5040 boards [3].
The guest kernel doesn't boot. There is no output via the serial
connection and no output via the graphics card. (QEMU)
On 14 October 2024 at 3:11pm, Christian Zigotzky wrote:
>> On 14 October 2024 at 3:00pm, Alex Deucher
wrote:
>>
>> Can whoever wrote this send it out as a proper patch?
>>
>> Alex
>>
> Patch source:
https://lists.freedesktop.org/archives/dri-devel/2024-October/473314.html
+ ville.syrjala
On 14 October 2024 at 3:00pm, Alex Deucher wrote:
Can whoever wrote this send it out as a proper patch?
Alex
Patch source:
https://lists.freedesktop.org/archives/dri-devel/2024-October/473314.html
On 11 October 2024 at 01:49am, Jeff Johnson wrote:
Can you provide links to all 3 patches?
6.12-rc2 was back merged to my ath.git project, but then my laptop
stopped booting correctly and I discovered a few Radeon KASAN reports.
Based upon my search of lore I found:
20241003060650.18454-1-wuhoi
://github.com/chzigotzky/kernels/releases/tag/v6.12.0-rc2-2
We need 3 patches for the Radeon DRM driver currently.
Please test it.
Thanks,
Christian
> On 08 October 2024 at 11:00am, Christian Zigotzky
> wrote:
>
> Hi All,
>
> I have released the RC2 of kernel 6.12 with
Hi All,
I have released the RC2 of kernel 6.12 with Christian Koenig’s patch for the
X1000 and X5000.
Download and further information:
https://github.com/chzigotzky/kernels/releases/tag/v6.12.0-rc2
Please test the kernels because of the second Radeon DRM driver issue.
Thanks,
Christian
> Am
On 06 October 2024 at 8:01pm, Christian Zigotzky wrote:
On 06 October 2024 at 7:37pm, Christophe Leroy wrote:
Le 06/10/2024 à 18:56, Christian Zigotzky a écrit :
Hello Wu Hoi Pok,
Thanks a lot for your patch. Unfortunately there is a new issue
after patching the RC1. Could you please fix
On 06 October 2024 at 7:37pm, Christophe Leroy wrote:
Le 06/10/2024 à 18:56, Christian Zigotzky a écrit :
Hello Wu Hoi Pok,
Thanks a lot for your patch. Unfortunately there is a new issue after
patching the RC1. Could you please fix the following issue?
Thanks,
Christian
---
Linux fienix
On 03 October 2024 at 08:06 am, Wu Hoi Pok wrote:
This is a fix patch not tested yet,
for a bug I introduce in previous rework of radeon driver.
The bug is a null dereference in 'aux.dev', which is the
'device' not registered, resulting in kernel panic. By having
'late_register', the connector sh
Hi All,
I compiled a new RC1 of kernel 6.12 with this patch today. Please test it.
Downloads:
- https://github.com/chzigotzky/kernels/releases/tag/v6.12.0-rc1-2
- https://www.xenosoft.de/linux-image-6.12-rc1-2-X1000_X5000.tar.gz
Thanks,
Christian
On 04 October 2024 at 4:00pm, Alex Deucher wro
On 02 October 2024 at 3:43pm, Hoi Pok Wu wrote:
Thanks to Christophe.
I have figured out what happened.
The connector is registered before the device,
where drm_connector_register() states that,
drm_dev_register() has to be called before it.
Assuming this is the fix, I will send the patch for t
On 30 September 2024 3:27pm, Alex Deucher wrote:
+ Wu Hoi Pok
This is likely related to the drm device rework.
Alex
—-
Hi All,
I was able to revert the drm-next-2024-09-19 updates for the RC1 of kernel 6.12.
This kernel works on all machines without any problems.
This means, the new R
> On 26 September 2024 at 6:38pm, Christian Zigotzky
> wrote:
>
> On 26 September 2024 at 5:50pm, Alex Deucher wrote:
>
> Can you attach your dmesg output? There was a regression in the dma
> subsystem what was fixed by this commit:
>
> commit b348b6d17fd1d5d8
Hello,
I tested the latest Git kernel with my VAPOR-X Radeon HD5870 1GB GDDR5 PCI-E
DUAL DVI-I/HDMI/DP on my PASEMI Nemo board today.
Unfortunately it has the same issue like my FSL P5040 board.
I think it depends on which graphics card is used.
It could be, that FSL P5020 boards are also affec
On 28 September 2024 at 01:46pm, Christian Zigotzky wrote:
Am 28.09.24 um 10:42 schrieb Christophe Leroy:
Hi Christian,
Le 28/09/2024 à 09:40, Christian Zigotzky a écrit :
On 28 September 2024 at 09:21am, Christian Zigotzky wrote:
>
>> On Sun, Sep 22, 2024 at 12:28 AM Christian
Am 28.09.24 um 10:42 schrieb Christophe Leroy:
Hi Christian,
Le 28/09/2024 à 09:40, Christian Zigotzky a écrit :
On 28 September 2024 at 09:21am, Christian Zigotzky wrote:
>
>> On Sun, Sep 22, 2024 at 12:28 AM Christian Zigotzky
>> wrote:
>>>
>>> Hi All,
On 22 September 2024 at 08:48 am, Christian Zigotzky wrote:
On 21 September 2024 at 06:15 am, Christian Zigotzky wrote:
Hi All,
The lastest Git kernel doesn't boot anymore after the latest DRM
updates (drm-next-2024-09-19). [1]
I tested it with an AMD Radeon HD 6970 (Cayman XT) and wi
32 on PPC64.
Reported-by: Christian Zigotzky
Closed:
https://lore.kernel.org/linuxppc-dev/047b7503-af0c-4bb0-b12a-2f6b1e461...@csgroup.eu/T/
Fixes: b163596a5b6f ("powerpc/vdso32: Add crtsavres")
Signed-off-by: Christophe Leroy
---
arch/powerpc/lib/crtsavres.S | 2 +-
1 file changed, 1
Hi All,
The compiling of the latest Git kernel doesn’t work anymore for our FSL
P5020/P5040 boards [1] since the random-6.12-rc1 updates [2].
Error messages:
arch/powerpc/kernel/vdso/vdso32.so.dbg: dynamic relocations are not supported
make[2]: *** [arch/powerpc/kernel/vdso/Makefile:75:
arch/
On 19 September 2024 at 2:29 pm, Christian Zigotzky wrote:
Hi All,
The compiling of the latest Git kernel doesn’t work anymore for our
FSL P5020/P5040 boards [1] since the random-6.12-rc1 updates [2].
Error messages:
arch/powerpc/kernel/vdso/vdso32.so.dbg: dynamic relocations are not
Hi All,
The compiling of the latest Git kernel doesn’t work anymore for our FSL
P5020/P5040 boards [1] since the random-6.12-rc1 updates [2].
Error messages:
arch/powerpc/kernel/vdso/vdso32.so.dbg: dynamic relocations are not
supported
make[2]: *** [arch/powerpc/kernel/vdso/Makefile:75:
a
On 10.07.24 17:05, Rob Herring wrote:
On Tue, Jul 9, 2024 at 9:53 PM Christian Zigotzky
wrote:
Hi All,
The RC7 of kernel 6.10 boots without any problems [1] if we use the
second irq patch [2]. Is it possible to add this patch to the mainline
kernel?
Yes, sent it to Linus yesterday.
Rob
Hi All,
The RC7 of kernel 6.10 boots without any problems [1] if we use the
second irq patch [2]. Is it possible to add this patch to the mainline
kernel?
Thanks,
Christian
[1] https://forum.hyperion-entertainment.com/viewtopic.php?p=58643#p58643
[2]
https://github.com/chzigotzky/kernels/bl
On 6. Jul 2024, at 06:15, Christian Zigotzky wrote:
Our tester has tested the second irq patch again and the kernel boots. We will
test it again to be sure that it really works. ;-)
Second irq patch:
diff --git a/drivers/of/irq.c b/drivers/of/irq.c
index 462375b293e47..c94203ce65bb3 100644
On 05.07.24 03:19, Michael Ellerman wrote:
Right, I had some debug code that I removed before posting.
This version should compile :}
cheers
diff --git a/arch/powerpc/kernel/prom_init.c b/arch/powerpc/kernel/prom_init.c
index fbb68fc28ed3..965d58c54fab 100644
--- a/arch/powerpc/kernel/prom_ini
Types corrected and html removed
On 05.07.24 03:19, Michael Ellerman wrote:
>
>
> Right, I had some debug code that I removed before posting.
>
> This version should compile :}
>
> cheers
>
> diff --git a/arch/powerpc/kernel/prom_init.c
b/arch/powerpc/kernel/prom_init.c
> index fbb68fc28ed3..96
On 05.07.24 03:19, Michael Ellerman wrote:
>
>
> Right, I had some debug code that I removed before posting.
>
> This version should compile :}
>
> cheers
>
> diff --git a/arch/powerpc/kernel/prom_init.c
b/arch/powerpc/kernel/prom_init.c
> index fbb68fc28ed3..965d58c54fab 100644
> --- a/arch/pow
How about the other patch[1], which would be far preferable?
M.
[1] https://lore.kernel.org/all/86ed8ba2sp.wl-...@kernel.org
- - - -
Marc,
We will test the patch as soon as possible.
Christian
- - - -
Our tester has reported, that it doesn’t boot.
Link: https://forum.hyperion-entertainm
How about the other patch[1], which would be far preferable?
M.
[1] https://lore.kernel.org/all/86ed8ba2sp.wl-...@kernel.org
- - - -
Marc,
We will test the patch as soon as possible.
Christian
- - - -
Our tester has reported, that it doesn’t boot.
Link: https://forum.hyperion-entertainm
[snip]
My earlier request for valuable debug information still stands. But
while you're at it, can you please give the following hack a go?
M.
--- a/drivers/of/irq.c
+++ b/drivers/of/irq.c
@@ -282,8 +282,10 @@ int of_irq_parse_raw(const __be32 *addr, struct
of_phandle_args *out_irq)
On 04.07.24 20:27, Christian Zigotzky wrote:
On 04.07.24 13:53, Michael Ellerman wrote:
Christian Zigotzky writes:
On 02.07.24 18:54, Marc Zyngier wrote:
On Sun, 30 Jun 2024 11:21:55 +0100,
Christian Zigotzky wrote:
Hello,
There is an issue with the identification of ATA drives with our
On 04.07.24 10:28, Marc Zyngier wrote:
On Thu, 04 Jul 2024 05:10:46 +0100,
Christian Zigotzky wrote:
On 02.07.24 18:54, Marc Zyngier wrote:
On Sun, 30 Jun 2024 11:21:55 +0100,
Christian Zigotzky wrote:
Hello,
There is an issue with the identification of ATA drives with our
P.A. Semi Nemo
On 04.07.24 13:53, Michael Ellerman wrote:
Christian Zigotzky writes:
On 02.07.24 18:54, Marc Zyngier wrote:
On Sun, 30 Jun 2024 11:21:55 +0100,
Christian Zigotzky wrote:
Hello,
There is an issue with the identification of ATA drives with our
P.A. Semi Nemo boards [1] after the
commit &qu
On 02.07.24 18:54, Marc Zyngier wrote:
On Sun, 30 Jun 2024 11:21:55 +0100,
Christian Zigotzky wrote:
Hello,
There is an issue with the identification of ATA drives with our
P.A. Semi Nemo boards [1] after the
commit "of/irq: Factor out parsing of interrupt-map parent
phandle+args
On 03.07.24 12:41, Marc Zyngier wrote:
On Wed, 03 Jul 2024 11:26:17 +0100,
Christian Zigotzky wrote:
On 3. Jul 2024, at 08:40, Marc Zyngier wrote:
This isn't a DTS. This is a listing of all the nodes, not something I
can use to feed the kernel. I explained how to generate it.
Downloa
On 3. Jul 2024, at 08:40, Marc Zyngier wrote:
This isn't a DTS. This is a listing of all the nodes, not something I
can use to feed the kernel. I explained how to generate it.
Download the compiled device tree for the Nemo board:
http://www.xenosoft.de/fdt-nemo-board.zip
No, thank you.
———
Hello Marc,
On 02.07.24 18:54, Marc Zyngier wrote:
On Sun, 30 Jun 2024 11:21:55 +0100,
Christian Zigotzky wrote:
Hello,
There is an issue with the identification of ATA drives with our
P.A. Semi Nemo boards [1] after the
commit "of/irq: Factor out parsing of interrupt-map parent
phandle
Hello Marc,
On 02.07.24 21:49, Marc Zyngier wrote:
On 2024-07-02 18:55, Christian Zigotzky wrote:
Hello Marc,
Thank you for your reply.
On 02.07.24 17:19, Marc Zyngier wrote:
Please provide the device tree for your platform. It isn't possible to
debug this without it, no matter how
Hello Marc,
Thank you for your reply.
On 02.07.24 17:19, Marc Zyngier wrote:
Christian,
On Sun, 30 Jun 2024 11:21:55 +0100,
Christian Zigotzky wrote:
Hello,
There is an issue with the identification of ATA drives with our
P.A. Semi Nemo boards [1] after the
commit "of/irq: Facto
Hello,
There is an issue with the identification of ATA drives with our P.A.
Semi Nemo boards [1] after the
commit "of/irq: Factor out parsing of interrupt-map parent phandle+args
from of_irq_parse_raw()" [2].
Error messages:
ata2.00: failed to IDENTIFY (I/O error, err_mask=0x4)
ata2.00: qc
On 30.05.24 14:51, Michael Ellerman wrote:
Christian Zigotzky writes:
On 28.05.24 22:00, Christian Zigotzky wrote:
Hi All,
Xorg doesn't start anymore since the RC1 of kernel 6.10. We tested it
with the VirtIO GPU and with some Radeon cards.
Another error message: Failed to start
On 28.05.24 22:00, Christian Zigotzky wrote:
Hi All,
Xorg doesn't start anymore since the RC1 of kernel 6.10. We tested it
with the VirtIO GPU and with some Radeon cards.
Another error message: Failed to start Setup Virtual Console.
Maybe this is the
On 28.05.24 22:00, Christian Zigotzky wrote:
Hi All,
Xorg doesn't start anymore since the RC1 of kernel 6.10. We tested it
with the VirtIO GPU and with some Radeon cards.
Another error message: Failed to start Setup Virtual Console.
Maybe this is the
Hi All,
Xorg doesn't start anymore since the RC1 of kernel 6.10. We tested it
with the VirtIO GPU and with some Radeon cards.
Another error message: Failed to start Setup Virtual Console.
Maybe this is the issue: + CONFIG_ARCH_HAS_KERNEL_FPU_SUPPORT=y
Tested with FSL P5040, FSL P5020, and PA
Christophe Leroy writes:
Hi Christian, hi Hari,
Le 04/04/2024 à 19:44, Christian Zigotzky a écrit :
Shall we use CONFIG_CRASH_DUMP to get int crashing_cpu = -1;?
Further information:
https://lists.ozlabs.org/pipermail/linuxppc-dev/2024-March/269985.html
<https://lists.ozlabs.org/piperm
Shall we use CONFIG_CRASH_DUMP to get int crashing_cpu = -1;?
Further information:
https://lists.ozlabs.org/pipermail/linuxppc-dev/2024-March/269985.html
— Christian
disable_threadbit = 0;
long start = mftb();
long now;
+ int crashing_cpu = -1;
local_irq_disable();
hard_irq_disable();
-
-- Christian
On 25 March 2024 at 10:14 am, Christian Zigotzky wrote:
We have configured (kernel config):
# CONFIG_CRASH_DUMP is not set
def CONFIG_CRASH_DUMP
/* This keeps a track of which one is the crashing cpu. */
int crashing_cpu = -1;
#endif
-
-- Christian
On 25 March 2024 at 08:15 am, Christian Zigotzky wrote:
Thanks a lot for the hint.
Could you please add #include to
arch/powerpc/platforms
Thanks a lot for the hint.
Could you please add #include to
arch/powerpc/platforms/85xx/smp.c for the next PowerPC fixes?
Christian
On 25 March 2024 at 07:43 am, Christophe Leroy wrote:
Hi,
Le 25/03/2024 à 06:18, Christian Zigotzky a écrit :
I have created a patch:
--- a/arch/powerpc
= mftb();
long now;
+ int crashing_cpu = -1;
local_irq_disable();
hard_irq_disable();
---
-- Christian
On 25 March 2024 at 05:48 am, Christian Zigotzky wrote:
Hi All,
Compiling of the RC1 of kernel 6.9 doesn’t work anymore for our FSL
P5020/P5040 boards [1] since the
Hi All,
The Compiling of the RC1 of kernel 6.9 doesn’t work anymore for our FSL
P5020/P5040 boards [1] since the PowerPC updates 6.9-2 [2].
Error messages:
arch/powerpc/platforms/85xx/smp.c: In function 'mpc85xx_smp_kexec_cpu_down':
arch/powerpc/platforms/85xx/smp.c:401:13: error: 'crashing_c
ike that.
-- Linus Torvalds
Geert,
Your patch works! :-) Thanks a lot!
I tested it with the virtio-vga and with the virtio-gpu-pci device in a
virtual ppce500 QEMU/KVM HV machine with an e5500 CPU today.
Tested-by: Christian Zigotzky
Cheers,
Christian
On 13 November 2023 at 01:48 pm, Geert Uytterhoeven wrote:
Hi Christian,
On Sun, Nov 12, 2023 at 3:23 PM Christian Zigotzky
wrote:
On 07 November 2023 at 09:36 am, Christian Zigotzky wrote:
I have found out that fbdev no longer works with virtio-gpu-pci and
virtio-vga. It is not a problem
+ Helge Deller
+ Gerd Knorr
+ Geert Uytterhoeven
On 07 November 2023 at 09:36 am, Christian Zigotzky wrote:
Hello,
I have found out that fbdev no longer works with virtio-gpu-pci and
virtio-vga. It is not a problem with the penguin logos.
Could you please check fbdev in QEMU virtual
03:45 pm, Christian Zigotzky wrote:
Hello,
There is a fbdev issue with the virtio-gpu-pci and virtio-vga. (The
penguins are not displayed at boot time)
Error message: [ 0.889302] virtio-pci :00:02.0: [drm] *ERROR*
fbdev: Failed to setup generic emulation (ret=-2)
The kernel 6.6 final
Hello,
There is a fbdev issue with the virtio-gpu-pci and virtio-vga. (The
penguins are not displayed at boot time)
Error message: [ 0.889302] virtio-pci :00:02.0: [drm] *ERROR*
fbdev: Failed to setup generic emulation (ret=-2)
The kernel 6.6 final doesn't have this issue.
Please c
On 03.07.23 07:21, Michael Ellerman wrote:
On Fri, 05 May 2023 12:18:17 -0500, Rob Herring wrote:
Commit e4ab08be5b49 ("powerpc/isa-bridge: Remove open coded "ranges"
parsing") broke PASemi Nemo board booting. The issue is the ISA I/O
range was not getting mapped as the logic to handle no "range
Hello Adrian,
On 29 June 2023 at 12:17 pm, John Paul Adrian Glaubitz wrote:
What version of AmigaOS is that?
AmigaOS 4.1
Maybe the RDB is corrupted? Did you try on a freshly created RDB?
Good idea! I recreated the RDB with the Media Toolbox on the
sb600sata.device, 0. (AmigaOne X1000)
Unfor
Hello,
The access to partitions on disks with an Amiga partition table (via
the Rigid Disk Block RDB) doesn't work anymore on my Cyrus+ board with a
FSL P50x0 PowerPC SoC [1] and on my P.A. Semi Nemo board [2] after the
block updates 2023-06-23 [3].
parted -l
Model: ATA ST2000DM001-9YN1 (s
e.kernel.org/all/301595ad-0edf-2113-b55f-f5b8051ed...@xenosoft.de/
Reported-by: Christian Zigotzky
Signed-off-by: Rob Herring
---
Untested, but I think this should fix the issue.
arch/powerpc/kernel/isa-bridge.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/arch/powerpc/kern
On 03 May 2023 at 08:15 pm, Rob Herring wrote:
On Wed, May 3, 2023 at 12:40 PM Christian Zigotzky
wrote:
On 3. May 2023, at 18:51, Rob Herring wrote:
On Wed, May 3, 2023 at 11:27 AM Christophe Leroy
wrote:
+Rob as he's the commit's Author.
Le 03/05/2023 à 17:46, Christian
> On 3. May 2023, at 19:28, Christian Zigotzky wrote:
>
>
>
>>> On 3. May 2023, at 18:51, Rob Herring wrote:
>>>
>>> On Wed, May 3, 2023 at 11:27 AM Christophe Leroy
>>> wrote:
>>>
>>> +Rob as he's the commi
> On 3. May 2023, at 18:51, Rob Herring wrote:
>
> On Wed, May 3, 2023 at 11:27 AM Christophe Leroy
> wrote:
>>
>> +Rob as he's the commit's Author.
>>
>>> Le 03/05/2023 à 17:46, Christian Zigotzky a écrit :
>>> On 02 May 2023 at
On 02 May 2023 at 11:28 am, Michael Ellerman wrote:
Christian Zigotzky writes:
Hello,
Our PASEMI Nemo board [1] doesn't boot with the PowerPC updates 6.4-1 [2].
The kernel hangs right after the booting Linux via __start() @
0x ...
I was able to revert the PowerPC update
On 06 January 2023 at 03:41 pm, Jiri Kosina wrote:
On Fri, 6 Jan 2023, Christian Zigotzky wrote:
Hello,
The reboot issue is still present in the RC2 of kernel 6.2. We still need the
usbhid.patch. [1]
Please check the bad commit. [2]
Ankit,
have you tested with all the devices that you
/linux.git/commit/?h=v6.1&id=f6d910a89a2391e5ce1f275d205023880a33d3f8
On 22 December 2022 at 11:42 am, Christian Zigotzky wrote:
Hello,
The Nemo board [1] doesn't reboot anymore since the final kernel 6.1.
The reboot works with the RC8 of kernel 6.1.
Actually, a reboot works bu
> On 3. Jan 2023, at 05:04, Christian Zigotzky wrote:
>
> On 02 January 2023 at 04:32 am, Christian Zigotzky wrote:
>> On 01 January 2023 at 07:11 pm, Sean Anderson wrote:
>>
>> Thank you for testing this. Unfortunately, I have no P-series hardware,
>> so I w
On 02 January 2023 at 04:32 am, Christian Zigotzky wrote:
On 01 January 2023 at 07:11 pm, Sean Anderson wrote:
Thank you for testing this. Unfortunately, I have no P-series hardware,
so I was unable to test the 10gec/dtsec parts of this conversion. I had
hoped that this would get tested by
On 01 January 2023 at 07:11 pm, Sean Anderson wrote:
Thank you for testing this. Unfortunately, I have no P-series hardware,
so I was unable to test the 10gec/dtsec parts of this conversion. I had
hoped that this would get tested by someone with the hardware (at NXP)
before now, but it seems you
Hi All,
The DPAA Ethernet doesn’t work anymore on our FSL P5020/P5040 boards [1]
since the first updates after the final kernel 6.1 [2].
We bisected yesterday [3] and found the problematic commit [4]. I was
able to revert it. After that the DPAA Ethernet works again. I created a
patch for reve
Hello,
The Nemo board [1] doesn't reboot anymore since the final kernel 6.1.
The reboot works with the RC8 of kernel 6.1.
Actually, a reboot works but the CFE firmware is not loaded. Maybe there
is still something in the memory after the reboot.
I bisected today. [2]
The commit "HID: usbhid:
Further information:
https://lists.nongnu.org/archive/html/qemu-ppc/2022-12/msg0.html
-- Christian
On 04 December 2022 at 12:33 pm, Christian Zigotzky wrote:
Hi All,
We regularly use QEMU with KVM HV on our A-EON AmigaOne X5000 machines
(book3e). It works fast and without any problems
Hi All,
We regularly use QEMU with KVM HV on our A-EON AmigaOne X5000 machines
(book3e). It works fast and without any problems.
Screenshot tour of QEMU/KVM HV on our AmigaOnes:
- https://i.ibb.co/m4vgwNT/Kernel-6-1-rc3-Power-PC.png
- https://i.ibb.co/Fwdjf7Z/Kernel-6-0-rc6-Power-PC.png
- htt
On 30 October 2022 at 02:30 pm, Christian Zigotzky wrote:
On 29 October 2022 at 01:44 pm, Christian Zigotzky wrote:
On 17 October 2022 at 09:53 am, Christian Zigotzky wrote:
On 17. Oct 2022, at 02:43, Michael Ellerman
wrote:
Previously BIG_ENDIAN && GENERIC_CPU would use -mcpu=power5
On 29 October 2022 at 01:44 pm, Christian Zigotzky wrote:
On 17 October 2022 at 09:53 am, Christian Zigotzky wrote:
On 17. Oct 2022, at 02:43, Michael Ellerman wrote:
Previously BIG_ENDIAN && GENERIC_CPU would use -mcpu=power5, now it
uses
-mcpu=power4.
Maybe this is the issue. We w
On 29 October 2022 at 5:33 pm, Segher Boessenkool wrote:
On Mon, Oct 17, 2022 at 09:53:04AM +0200, Christian Zigotzky wrote:
On 17. Oct 2022, at 02:43, Michael Ellerman wrote:
Previously BIG_ENDIAN && GENERIC_CPU would use -mcpu=power5, now it uses
-mcpu=power4.
Maybe this is the i
On 29 October 2022 at 01:44 pm, Christian Zigotzky wrote:
On 17 October 2022 at 09:53 am, Christian Zigotzky wrote:
On 17. Oct 2022, at 02:43, Michael Ellerman wrote:
Previously BIG_ENDIAN && GENERIC_CPU would use -mcpu=power5, now it
uses
-mcpu=power4.
Maybe this is the issue. We w
at 18:51, Segher Boessenkool
>>>> wrote:
>>>
>>> On Fri, Oct 14, 2022 at 06:11:21PM +0200, Christian Zigotzky wrote:
>>>> make oldconfig has asked because of the CPU family. I choosed GENERIC for
>>>> my P.A. Semi PWRficient PA6T-1682M.
No, it’s not fine. We used the POWER4 CPU config before.
— Christian
> On 16. Oct 2022, at 18:51, Segher Boessenkool
> wrote:
>
> On Fri, Oct 14, 2022 at 06:11:21PM +0200, Christian Zigotzky wrote:
>> make oldconfig has asked because of the CPU family. I choosed GENERIC fo
valds/linux/blob/master/arch/powerpc/platforms/Kconfig.cputype
— Christian
> On 13. Oct 2022, at 11:42, Christian Zigotzky wrote:
>
> Hi Christophe,
>
> Thanks a lot for your answer. OK, now, I know, that I don’t need to test it.
> After the boot of the latest git kernel, my syst
> On 15. Oct 2022, at 11:51, Andrew Donnellan wrote:
>
> On Thu, 2022-10-13 at 11:42 +0200, Christian Zigotzky wrote:
>> Hi Christophe,
>>
>> Thanks a lot for your answer. OK, now, I know, that I don’t need to
>> test it. After the boot of the latest git k
Edit: fixed typos.
> On 13. Oct 2022, at 11:42, Christian Zigotzky wrote:
>
> Hi Christophe,
>
> Thanks a lot for your answer. OK, now, I know, that I don’t need to test it.
> After the boot of the latest git kernel, my system was extremely damaged.
> Some config
phe Leroy
> wrote:
>
>
>
>> Le 13/10/2022 à 09:03, Christian Zigotzky a écrit :
>> Hi Andrew,
>>
>> Does this patch also affect 64-bit kernels?
>>
>> We use often 32-bit userlands with 64-bit kernels.
>
> As far as I understand, it was al
Hi Andrew,
Does this patch also affect 64-bit kernels?
We use often 32-bit userlands with 64-bit kernels.
Cheers,
Christian
> On 12. Oct 2022, at 09:56, Andrew Donnellan wrote:
>
> On Wed, 2022-10-12 at 08:51 +0200, Christian Zigotzky wrote:
>> Hi All,
>>
>>
Hi All,
I use the Nemo board with a PASemi PA6T CPU and have some issues since the
first PowerPC updates for the kernel 6.1.
I successfully compiled the git kernel with the first PowerPC updates two days
ago.
Unfortunately this kernel is really dangerous. Many things for example Network
Manag
1 - 100 of 534 matches
Mail list logo
