Hyperion Entertainment Message Boards

Posted: **Sat May 01, 2021 7:52 pm**

xeno74 wrote: Sat May 01, 2021 11:17 am You can figure out your graphics card with lspci.

I don't seem to use it correctly.

fienix@Fienix:~$ lspci
bash: lspci: command not found
fienix@Fienix:~$

Synaptic doesn't have it. I'll try Ubuntu later.

Posted: **Sun May 02, 2021 4:01 am**

The command "lspci" doesn't work on Fienix because it isn't included in the img. You can install it with "apt install pciutils" as root.

Posted: **Sun May 02, 2021 8:13 am**

my Linux use Firepro.

ace

Posted: **Sun May 02, 2021 8:25 pm**

xeno74 wrote: Sun May 02, 2021 4:01 am... You can install ["lspci"] with "apt install pciutils" as root.

I had tried "apt-get install lspci." Probably too late for me to (re?)learn how to use apt.

Now "lspci" works, but says nothing about "SI" or "NI," only that it is Cape Verde PRO [Radeon HD 7750/8740 / R7 250E]. I already knew it was 7000 series, and when I look that up it says "Southern Islands," so now I know what SI and NI (6000 series) stand for. Thanks. How long will I remember?

Posted: **Sun May 02, 2021 8:29 pm**

acefnq wrote: Sun May 02, 2021 8:13 am my Linux use Firepro.

ace

Thanks for your answer. Great, that you still use the Firepro.

Posted: **Sun May 02, 2021 8:31 pm**

kilaueabart wrote: Sun May 02, 2021 8:25 pm I had tried "apt-get install lspci." Probably too late for me to (re?)learn how to use apt.

Now "lspci" works, but says nothing about "SI" or "NI," only that it is Cape Verde PRO [Radeon HD 7750/8740 / R7 250E]. I already knew it was 7000 series, and when I look that up it says "Southern Islands," so now I know what SI and NI (6000 series) stand for. Thanks. How long will I remember?

Many thanks for your answer. It seems, that SI graphics cards aren’t affected by the boot issue.

Posted: **Mon May 03, 2021 7:38 am**

Hi All,

I compiled the latest Git kernel today. Unfortunately Xorg always restarts again and again on the X5000. The X1000 isn't affected.

I bisected today.

Code: Select all
```
git bisect start
```
Code: Select all
```
git bisect good 68a32ba14177d4a21c4a9a941cf1d7aea86d436f
```
(Good: drm-next-2021-04-28 with the radeon_nislands_smc patch)
Code: Select all
```
git bisect bad 9ccce092fc64d19504fa54de4fd659e279cc92e7
```
(Bad: orangefs updates -- 2021-05-02 14:13:46)
git bisect good (NISLANDS_SMC_HW_PERFORMANCE_LEVEL levels[1])
git bisect bad (NISLANDS_SMC_HW_PERFORMANCE_LEVEL levels[])
git bisect good (NISLANDS_SMC_HW_PERFORMANCE_LEVEL levels[])
git bisect good (NISLANDS_SMC_HW_PERFORMANCE_LEVEL levels[])
git bisect bad (NISLANDS_SMC_HW_PERFORMANCE_LEVEL levels[1])
git bisect bad (NISLANDS_SMC_HW_PERFORMANCE_LEVEL levels[1]). It stops after loading the dtb and uImage. Maybe a third bug.
git bisect bad (NISLANDS_SMC_HW_PERFORMANCE_LEVEL levels[1]). It stops after loading the dtb and uImage. Maybe a third bug.
git bisect bad (NISLANDS_SMC_HW_PERFORMANCE_LEVEL levels[1]). It stops after loading the dtb and uImage. Maybe a third bug.
git bisect bad (NISLANDS_SMC_HW_PERFORMANCE_LEVEL levels[1]). It stops after loading the dtb and uImage. Maybe a third bug.
git bisect bad (NISLANDS_SMC_HW_PERFORMANCE_LEVEL levels[1]). It stops after loading the dtb and uImage. Maybe a third bug.
[git bisect bad (NISLANDS_SMC_HW_PERFORMANCE_LEVEL levels[1]). It stops after loading the dtb and uImage. Maybe a third bug.
git bisect bad (NISLANDS_SMC_HW_PERFORMANCE_LEVEL levels[1]). It stops after loading the dtb and uImage. Maybe a third bug.
git bisect bad (NISLANDS_SMC_HW_PERFORMANCE_LEVEL levels[1]). It stops after loading the dtb and uImage. Maybe a third bug.

Result: 9be77e11dade414d2fa63750aa5c754fac49d619 is the first bad commit.

Code: Select all

Author: Sebastian Andrzej Siewior <[email protected]>
Date:   Fri Feb 19 17:56:48 2021 +0100

    powerpc/mm: Move the linear_mapping_mutex to the ifdef where it is used
    
    The mutex linear_mapping_mutex is defined at the of the file while its
    only two user are within the CONFIG_MEMORY_HOTPLUG block.
    A compile without CONFIG_MEMORY_HOTPLUG set fails on PREEMPT_RT because
    its mutex implementation is smart enough to realize that it is unused.
    
    Move the definition of linear_mapping_mutex to ifdef block where it is
    used.
    
    Fixes: 1f73ad3e8d755 ("powerpc/mm: print warning in arch_remove_linear_mapping()")
    Signed-off-by: Sebastian Andrzej Siewior <[email protected]>
    Signed-off-by: Michael Ellerman <[email protected]>
    Link: https://lore.kernel.org/r/[email protected]

:040000 040000 b302c47d33c9abc346f8f40a25e1c3fea7aaa1a1 d901ba0772167c5bfcfae83b05b0c8dc31e03b72 M	arch

I was able to revert the first bad commit.

Code: Select all

git revert 9be77e11dade414d2fa63750aa5c754fac49d619

Output:

Code: Select all

[master ef2cc502ccc1] Revert "powerpc/mm: Move the linear_mapping_mutex to the ifdef where it is used"
 1 file changed, 1 insertion(+), 1 deletion(-)

Unfortunately the revert of the first bad commit doesn't solve the issue.

Cheers,
Christian

Posted: **Mon May 03, 2021 4:12 pm**

I reverted the first PowerPC updates for the kernel 5.13 with the following command:

Code: Select all

git revert c70a4be130de333ea079c59da41cc959712bb01c -m 1

After that, Xorg works without any problems. This issue is somewhere in the PowerPC udpates.

Posted: **Mon May 03, 2021 4:43 pm**

Hi All,

I bisected again today.

Code: Select all
```
git bisect start
```
Code: Select all
```
git bisect good 68a32ba14177d4a21c4a9a941cf1d7aea86d436f
```
(Good: drm-next-2021-04-28 with the radeon_nislands_smc patch)
Code: Select all
```
git bisect bad c70a4be130de333ea079c59da41cc959712bb01c
```
(Bad: Merge tag 'powerpc-5.13-1' -- 2021-04-30 12:22:28)
git bisect good (NISLANDS_SMC_HW_PERFORMANCE_LEVEL levels[1])
git bisect good (NISLANDS_SMC_HW_PERFORMANCE_LEVEL levels[])
git bisect good (NISLANDS_SMC_HW_PERFORMANCE_LEVEL levels[])
git bisect good (NISLANDS_SMC_HW_PERFORMANCE_LEVEL levels[])
git bisect bad (NISLANDS_SMC_HW_PERFORMANCE_LEVEL levels[1])
git bisect good (NISLANDS_SMC_HW_PERFORMANCE_LEVEL levels[1])
git bisect good (NISLANDS_SMC_HW_PERFORMANCE_LEVEL levels[1])
git bisect bad (NISLANDS_SMC_HW_PERFORMANCE_LEVEL levels[1])
git bisect good (NISLANDS_SMC_HW_PERFORMANCE_LEVEL levels[1])
git bisect bad (NISLANDS_SMC_HW_PERFORMANCE_LEVEL levels[1])
git bisect bad (NISLANDS_SMC_HW_PERFORMANCE_LEVEL levels[1])
git bisect good (NISLANDS_SMC_HW_PERFORMANCE_LEVEL levels[1])

Result: 887f3ceb51cd34109ac17bfc98695162e299e657 is the first bad commit.

Code: Select all

Author: Christophe Leroy <[email protected]>
Date:   Fri Mar 19 11:06:58 2021 +0000

    powerpc/signal32: Convert do_setcontext[_tm]() to user access block
    
    Add unsafe_get_user_sigset() and transform PPC32 get_sigset_t()
    into an unsafe version unsafe_get_sigset_t().
    
    Then convert do_setcontext() and do_setcontext_tm() to use
    user_read_access_begin/end.
    
    Signed-off-by: Christophe Leroy <[email protected]>
    Signed-off-by: Michael Ellerman <[email protected]>
    Link: https://lore.kernel.org/r/9273ba664db769b8d9c7540ae91395e346e4945e.1616151715.git.christophe.leroy@csgroup.eu

:040000 040000 70b717cd4e7540b3979b05dbe25a276dde0dfd16 91a5ce612e5bb3abcb0721b9990e6ce1643dacc1 M	arch

I wasn't able to revert the first bad commit.

The first bad commit is a part of the PowerPC updates 5.13-1.

Xorg doesn't start anymore in a virtual e5500 QEMU machine with Fedora 28 and restarts again and again in a virtual e5500 QEMU machine with MintPPC.

I reported this issue to the PowerPC kernel developers today.

Link: [FSL P50x0] Xorg always restarts again and again after the the PowerPC updates 5.13-1

Cheers,
Christian

Posted: **Tue May 04, 2021 12:10 pm**

Christophe wrote: I'm not sure you can conclude anything here. There is a problem in that commit, but it is fixed by 525642624783 ("powerpc/signal32: Fix erroneous SIGSEGV on RT signal return") which is the last commit of powerpc-5.13-1.

So any bisect from there will for sure point to 887f3ceb51cd ("powerpc/signal32: Convert do_setcontext[_tm]() to user access block") but that's unconclusive. If the problem is still there at the HEAD of powerpc-5.13-1, the problem is likely somewhere else.

I think you need to do the bisect again with a cherry-pick of 525642624783 at each step.

As you suspect the problem to be specific to powerpc, I can do

git bisect start -- arch/powerpc

You said that powerpc-5.13-1 is bad so you can narrow the search I think:

git bisect bad powerpc-5.13-1 or git bisect bad c70a4be130de333ea079c59da41cc959712bb01c
git bisect good 887f3ceb51cd3~

Thanks
Christophe

OK, I will try it again.

Code: Select all
```
git bisect start -- arch/powerpc
```
Code: Select all
```
git bisect good 887f3ceb51cd3~
```

Code: Select all

git bisect bad c70a4be130de333ea079c59da41cc959712bb01c

git bisect bad (NISLANDS_SMC_HW_PERFORMANCE_LEVEL levels[1])
git bisect bad (NISLANDS_SMC_HW_PERFORMANCE_LEVEL levels[1]) It stops after loading the dtb and uImage. Maybe a third bug.

OK, there is another issue after the second bisecting step. The boot stops after loading the dtb and uImage file. I can't solve 2 issues with bisecting at the same time.

I reported the result to the PowerPC kernel developers today.

Link: [FSL P50x0] Xorg always restarts again and again after the the PowerPC updates 5.13-1

Cheers,
Christian

Hyperion Entertainment Message Boards

Kernel 5.13

Re: Kernel 5.13

Re: Kernel 5.13

Re: Kernel 5.13

Re: Kernel 5.13

Re: Kernel 5.13

Re: Kernel 5.13

Re: Kernel 5.13

Re: Kernel 5.13

Re: Kernel 5.13

Re: Kernel 5.13