Re: Running ttm_device_test leads to list_add corruption. prev->next should be next (ffffffffc05cd428), but was 6b6b6b6b6b6b6b6b. (prev=ffffa0b1a5c034f0) (kernel 6.7.5)

2024-02-21 Thread Alex Deucher
On Wed, Feb 21, 2024 at 9:13 AM Christian König wrote: > > Am 20.02.24 um 18:43 schrieb Erhard Furtner: > > On Tue, 20 Feb 2024 14:50:04 +0100 > > Christian König wrote: > > > >> Yeah and that's probably the problem. The test is not supposed to be > >> compiled and executed on bare metal, but

Re: Running ttm_device_test leads to list_add corruption. prev->next should be next (ffffffffc05cd428), but was 6b6b6b6b6b6b6b6b. (prev=ffffa0b1a5c034f0) (kernel 6.7.5)

2024-02-21 Thread Christian König
Hi Maxime, Am 21.02.24 um 15:41 schrieb Maxime Ripard: Hi Christian, On Tue, Feb 20, 2024 at 04:03:57PM +0100, Christian König wrote: Am 20.02.24 um 15:56 schrieb Maxime Ripard: On Tue, Feb 20, 2024 at 02:28:53PM +0100, Christian König wrote: [SNIP] This kunit test is not meant to be run on

Re: Running ttm_device_test leads to list_add corruption. prev->next should be next (ffffffffc05cd428), but was 6b6b6b6b6b6b6b6b. (prev=ffffa0b1a5c034f0) (kernel 6.7.5)

2024-02-21 Thread Maxime Ripard
Hi Christian, On Tue, Feb 20, 2024 at 04:03:57PM +0100, Christian König wrote: > Am 20.02.24 um 15:56 schrieb Maxime Ripard: > > On Tue, Feb 20, 2024 at 02:28:53PM +0100, Christian König wrote: > > > [SNIP] > > > This kunit test is not meant to be run on real hardware, but rather just > > > as >

Re: Running ttm_device_test leads to list_add corruption. prev->next should be next (ffffffffc05cd428), but was 6b6b6b6b6b6b6b6b. (prev=ffffa0b1a5c034f0) (kernel 6.7.5)

2024-02-21 Thread Christian König
Am 20.02.24 um 18:43 schrieb Erhard Furtner: On Tue, 20 Feb 2024 14:50:04 +0100 Christian König wrote: Yeah and that's probably the problem. The test is not supposed to be compiled and executed on bare metal, but rather just as unit test through user mode Linux. We probably don't check that

Re: Running ttm_device_test leads to list_add corruption. prev->next should be next (ffffffffc05cd428), but was 6b6b6b6b6b6b6b6b. (prev=ffffa0b1a5c034f0) (kernel 6.7.5)

2024-02-21 Thread Erhard Furtner
On Tue, 20 Feb 2024 16:12:44 +0700 Bagas Sanjaya wrote: > > [0.00] Linux version 6.7.5-Zen3 (root@supah) (gcc (Gentoo > > 13.2.1_p20240113-r1 p12) 13.2.1 20240113, GNU ld (Gentoo 2.41 p5) 2.41.0) > > #1 SMP Mon Feb 19 12:44:46 -00 2024 > > Is it vanilla kernel (i.e. no patches

Re: Running ttm_device_test leads to list_add corruption. prev->next should be next (ffffffffc05cd428), but was 6b6b6b6b6b6b6b6b. (prev=ffffa0b1a5c034f0) (kernel 6.7.5)

2024-02-20 Thread Christian König
Am 20.02.24 um 15:56 schrieb Maxime Ripard: On Tue, Feb 20, 2024 at 02:28:53PM +0100, Christian König wrote: [SNIP] This kunit test is not meant to be run on real hardware, but rather just as stand a long kunit tests within user mode linux. I was assuming that it doesn't even compiles on bare

Re: Running ttm_device_test leads to list_add corruption. prev->next should be next (ffffffffc05cd428), but was 6b6b6b6b6b6b6b6b. (prev=ffffa0b1a5c034f0) (kernel 6.7.5)

2024-02-20 Thread Maxime Ripard
On Tue, Feb 20, 2024 at 02:28:53PM +0100, Christian König wrote: > Am 20.02.24 um 10:12 schrieb Bagas Sanjaya: > > On Mon, Feb 19, 2024 at 11:01:16PM +0100, Erhard Furtner wrote: > > > Greetings! > > > > > > 'modprobe -v ttm-device-test' on my Ryzen 5950X amd64 box and on my Talos > > > II

Re: Running ttm_device_test leads to list_add corruption. prev->next should be next (ffffffffc05cd428), but was 6b6b6b6b6b6b6b6b. (prev=ffffa0b1a5c034f0) (kernel 6.7.5)

2024-02-20 Thread Christian König
Hi Erhard, Am 20.02.24 um 13:45 schrieb Erhard Furtner: On Tue, 20 Feb 2024 16:12:44 +0700 Bagas Sanjaya wrote: [0.00] Linux version 6.7.5-Zen3 (root@supah) (gcc (Gentoo 13.2.1_p20240113-r1 p12) 13.2.1 20240113, GNU ld (Gentoo 2.41 p5) 2.41.0) #1 SMP Mon Feb 19 12:44:46 -00 2024

Re: Running ttm_device_test leads to list_add corruption. prev->next should be next (ffffffffc05cd428), but was 6b6b6b6b6b6b6b6b. (prev=ffffa0b1a5c034f0) (kernel 6.7.5)

2024-02-20 Thread Christian König
Am 20.02.24 um 10:12 schrieb Bagas Sanjaya: On Mon, Feb 19, 2024 at 11:01:16PM +0100, Erhard Furtner wrote: Greetings! 'modprobe -v ttm-device-test' on my Ryzen 5950X amd64 box and on my Talos II (ppc64) leads to immediate list_add corruption. The machines stay useable via VNC but the issue

Re: Running ttm_device_test leads to list_add corruption. prev->next should be next (ffffffffc05cd428), but was 6b6b6b6b6b6b6b6b. (prev=ffffa0b1a5c034f0) (kernel 6.7.5)

2024-02-20 Thread Bagas Sanjaya
On Mon, Feb 19, 2024 at 11:01:16PM +0100, Erhard Furtner wrote: > Greetings! > > 'modprobe -v ttm-device-test' on my Ryzen 5950X amd64 box and on my Talos II > (ppc64) leads to immediate list_add corruption. > > The machines stay useable via VNC but the issue seems to cause memory > corruption