X11 system lockup with 5.11.0 kernel

X11 system lockup with 5.11.0 kernel

[Bob Tracy]

All,

First an apology for being "dark" for so long.  There are still a few of
us out here using Alpha computers...

Another apology for the crappy "bug report" that follows, but first, a
little background information.  I'm not in the habit of running X11 on
my PWS 433au these days, except for periodically verifying "lightdm" and
"afterstep" still work.  The natural order of things is "increased bloat
over time", and the elephant barely walks these days, much less dances,
i.e., even an extremely lightweight window manager like AfterStep is
barely usable on my PWS.

Everything worked as well as it's going to for kernel versions up
through v5.10.0.  When I boot on v5.11.0, "lightdm" starts, the screen
goes blank as usual, I get a mouse pointer as usual, and shortly after
that, the system locks up solid (completely nonresponsive except for
being able to ping it -- can't login remotely).  Recovery is via the
reset switch at that point :-(.

It doesn't seem to be a userspace problem: rebooting the system on the
old v5.10.0 kernel works fine.  Nothing is showing up in any of the
system logs, unfortunately, so I'm at a loss how to troubleshoot this
further.

The PWS has the same Radeon 7500 video card in it that I've had for
years.

Any ideas/help appreciated, as always.  In the meantime, my default
strategy is to press on with trying the v5.12 release candidates
(standard kernel.org source tree).

Respectfully,
--Bob

Re: X11 system lockup with 5.11.0 kernel

[Bob Tracy]

On Wed, Mar 24, 2021 at 09:48:46AM -0500, Bob Tracy wrote:
> (...) 
> Everything worked as well as it's going to for kernel versions up
> through v5.10.0.  When I boot on v5.11.0, "lightdm" starts, the screen
> goes blank as usual, I get a mouse pointer as usual, and shortly after
> that, the system locks up solid (completely nonresponsive except for
> being able to ping it -- can't login remotely).  Recovery is via the
> reset switch at that point :-(.
> (...)

Same results for 5.12.0-rc4 kernel.

--Bob

Re: X11 system lockup with 5.11.0 kernel

[Maciej W. Rozycki]

On Thu, 25 Mar 2021, Bob Tracy wrote:

> > Everything worked as well as it's going to for kernel versions up
> > through v5.10.0.  When I boot on v5.11.0, "lightdm" starts, the screen
> > goes blank as usual, I get a mouse pointer as usual, and shortly after
> > that, the system locks up solid (completely nonresponsive except for
> > being able to ping it -- can't login remotely).  Recovery is via the
> > reset switch at that point :-(.
> > (...)
> 
> Same results for 5.12.0-rc4 kernel.

 I think the only feasible way of determining what has happened here is 
that you track the offending change down by bisecting the upstream kernel 
repository with `git bisect'.  Once you have it someone may help, either 
the author of the change, or the relevant maintainer, or someone else at 
<linux-kernel@vger.kernel.org>.

  Maciej

Re: X11 system lockup with 5.11.0 kernel

[Bob Tracy]

On Wed, Mar 31, 2021 at 11:04:42AM +0200, Maciej W. Rozycki wrote:
>  I think the only feasible way of determining what has happened here is 
> that you track the offending change down by bisecting the upstream kernel 
> repository with `git bisect'.

That would normally be what I would do, and it may yet happen.  Problem
is, I don't have a 64-bit system with enough disk space to do the kernel
builds with a cross-compiler, and local (native) builds on the PWS are
taking 36+ hours each these days.  Unless I get *really* lucky with the
bisects, the task will take a couple of weeks.

Anyway, I've whined enough :-).  Might as well get started...

--Bob

Re: X11 system lockup with 5.11.0 kernel

[Michael Cree]

On Sun, Apr 04, 2021 at 11:47:58PM -0500, Bob Tracy wrote:
> On Wed, Mar 31, 2021 at 11:04:42AM +0200, Maciej W. Rozycki wrote:
> >  I think the only feasible way of determining what has happened here is 
> > that you track the offending change down by bisecting the upstream kernel 
> > repository with `git bisect'.
> 
> That would normally be what I would do, and it may yet happen.  Problem
> is, I don't have a 64-bit system with enough disk space to do the kernel
> builds with a cross-compiler, and local (native) builds on the PWS are
> taking 36+ hours each these days.  Unless I get *really* lucky with the
> bisects, the task will take a couple of weeks.

Confirmed that v5.11.0 hard locks up on presenting the X-Desktop
login screen whereas v5.10.0 is fine. This is on a XP1000 with
a Radeon HD4350.

I've started a git bisection but it will take some time.

Cheers
Michael.

Re: X11 system lockup with 5.11.0 kernel

[Michael Cree]

On Mon, Apr 05, 2021 at 04:55:15PM +1200, Michael Cree wrote:
> On Sun, Apr 04, 2021 at 11:47:58PM -0500, Bob Tracy wrote:
> > On Wed, Mar 31, 2021 at 11:04:42AM +0200, Maciej W. Rozycki wrote:
> > >  I think the only feasible way of determining what has happened here is 
> > > that you track the offending change down by bisecting the upstream kernel 
> > > repository with `git bisect'.
> > 
> > That would normally be what I would do, and it may yet happen.  Problem
> > is, I don't have a 64-bit system with enough disk space to do the kernel
> > builds with a cross-compiler, and local (native) builds on the PWS are
> > taking 36+ hours each these days.  Unless I get *really* lucky with the
> > bisects, the task will take a couple of weeks.
> 
> Confirmed that v5.11.0 hard locks up on presenting the X-Desktop
> login screen whereas v5.10.0 is fine. This is on a XP1000 with
> a Radeon HD4350.

And the first bad commit is:

0fe3cf3a53b5c1205ec7d321be1185b075dff205 is the first bad commit
commit 0fe3cf3a53b5c1205ec7d321be1185b075dff205
Author: Christian König <christian.koenig@amd.com>
Date:   Sat Oct 24 13:12:23 2020 +0200

    drm/radeon: switch to new allocator v2
    
    It should be able to handle all cases here.
    
    v2: fix debugfs as well
    
    Signed-off-by: Christian König <christian.koenig@amd.com>
    Reviewed-by: Dave Airlie <airlied@redhat.com>
    Reviewed-by: Madhav Chauhan <madhav.chauhan@amd.com>
    Tested-by: Huang Rui <ray.huang@amd.com>
    Link: https://patchwork.freedesktop.org/patch/397088/?series=83051&rev=1

:040000 040000 4e643ef861b921392bc67be21a42298c91c7ff7a b36453567c3176a3cd50fa0b23886b0fd642560d M	drivers

Cheers
Michael.

Re: X11 system lockup with 5.11.0 kernel

[Kirsten Bromilow]

Please stop sending these emails! You have the wrong email address 

Sent from my iPhone

> On 5 Apr 2021, at 10:58, Michael Cree <mcree@orcon.net.nz> wrote:
> 
> On Mon, Apr 05, 2021 at 04:55:15PM +1200, Michael Cree wrote:
>>> On Sun, Apr 04, 2021 at 11:47:58PM -0500, Bob Tracy wrote:
>>> On Wed, Mar 31, 2021 at 11:04:42AM +0200, Maciej W. Rozycki wrote:
>>>> I think the only feasible way of determining what has happened here is 
>>>> that you track the offending change down by bisecting the upstream kernel 
>>>> repository with `git bisect'.
>>> 
>>> That would normally be what I would do, and it may yet happen.  Problem
>>> is, I don't have a 64-bit system with enough disk space to do the kernel
>>> builds with a cross-compiler, and local (native) builds on the PWS are
>>> taking 36+ hours each these days.  Unless I get *really* lucky with the
>>> bisects, the task will take a couple of weeks.
>> 
>> Confirmed that v5.11.0 hard locks up on presenting the X-Desktop
>> login screen whereas v5.10.0 is fine. This is on a XP1000 with
>> a Radeon HD4350.
> 
> And the first bad commit is:
> 
> 0fe3cf3a53b5c1205ec7d321be1185b075dff205 is the first bad commit
> commit 0fe3cf3a53b5c1205ec7d321be1185b075dff205
> Author: Christian König <christian.koenig@amd.com>
> Date:   Sat Oct 24 13:12:23 2020 +0200
> 
>    drm/radeon: switch to new allocator v2
> 
>    It should be able to handle all cases here.
> 
>    v2: fix debugfs as well
> 
>    Signed-off-by: Christian König <christian.koenig@amd.com>
>    Reviewed-by: Dave Airlie <airlied@redhat.com>
>    Reviewed-by: Madhav Chauhan <madhav.chauhan@amd.com>
>    Tested-by: Huang Rui <ray.huang@amd.com>
>    Link: https://patchwork.freedesktop.org/patch/397088/?series=83051&rev=1
> 
> :040000 040000 4e643ef861b921392bc67be21a42298c91c7ff7a b36453567c3176a3cd50fa0b23886b0fd642560d M    drivers
> 
> Cheers
> Michael.
> 

Re: X11 system lockup with 5.11.0 kernel

[Christian König]

That is a known issue fixed in follow up 5.11.x kernels.

Regards,
Christian.

Am 05.04.21 um 11:58 schrieb Michael Cree:
> On Mon, Apr 05, 2021 at 04:55:15PM +1200, Michael Cree wrote:
>> On Sun, Apr 04, 2021 at 11:47:58PM -0500, Bob Tracy wrote:
>>> On Wed, Mar 31, 2021 at 11:04:42AM +0200, Maciej W. Rozycki wrote:
>>>>   I think the only feasible way of determining what has happened here is
>>>> that you track the offending change down by bisecting the upstream kernel
>>>> repository with `git bisect'.
>>> That would normally be what I would do, and it may yet happen.  Problem
>>> is, I don't have a 64-bit system with enough disk space to do the kernel
>>> builds with a cross-compiler, and local (native) builds on the PWS are
>>> taking 36+ hours each these days.  Unless I get *really* lucky with the
>>> bisects, the task will take a couple of weeks.
>> Confirmed that v5.11.0 hard locks up on presenting the X-Desktop
>> login screen whereas v5.10.0 is fine. This is on a XP1000 with
>> a Radeon HD4350.
> And the first bad commit is:
>
> 0fe3cf3a53b5c1205ec7d321be1185b075dff205 is the first bad commit
> commit 0fe3cf3a53b5c1205ec7d321be1185b075dff205
> Author: Christian König <christian.koenig@amd.com>
> Date:   Sat Oct 24 13:12:23 2020 +0200
>
>      drm/radeon: switch to new allocator v2
>      
>      It should be able to handle all cases here.
>      
>      v2: fix debugfs as well
>      
>      Signed-off-by: Christian König <christian.koenig@amd.com>
>      Reviewed-by: Dave Airlie <airlied@redhat.com>
>      Reviewed-by: Madhav Chauhan <madhav.chauhan@amd.com>
>      Tested-by: Huang Rui <ray.huang@amd.com>
>      Link: https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpatchwork.freedesktop.org%2Fpatch%2F397088%2F%3Fseries%3D83051%26rev%3D1&amp;data=04%7C01%7Cchristian.koenig%40amd.com%7Ce271ea2552a640dfec1408d8f81964a3%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637532135545775310%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&amp;sdata=UYwXgn6lAsES4q8p944kP0Y%2BGzqHRwSMXgrQvZXwXzM%3D&amp;reserved=0
>
> :040000 040000 4e643ef861b921392bc67be21a42298c91c7ff7a b36453567c3176a3cd50fa0b23886b0fd642560d M	drivers
>
> Cheers
> Michael.

Re: X11 system lockup with 5.11.0 kernel

[Michael Cree]

On Tue, Apr 06, 2021 at 09:08:10AM +0200, Christian König wrote:
> That is a known issue fixed in follow up 5.11.x kernels.

Well, it's intriguing that you say that because the latest 5.11.x
kernel available from www.kernel.org (i.e. 5.11.11) is also bad
and locks up hard when X is started on my Alpha XP1000.

Cheers
Michael.

> Am 05.04.21 um 11:58 schrieb Michael Cree:
> > On Mon, Apr 05, 2021 at 04:55:15PM +1200, Michael Cree wrote:
> > > On Sun, Apr 04, 2021 at 11:47:58PM -0500, Bob Tracy wrote:
> > > > On Wed, Mar 31, 2021 at 11:04:42AM +0200, Maciej W. Rozycki wrote:
> > > > >   I think the only feasible way of determining what has happened here is
> > > > > that you track the offending change down by bisecting the upstream kernel
> > > > > repository with `git bisect'.
> > > > That would normally be what I would do, and it may yet happen.  Problem
> > > > is, I don't have a 64-bit system with enough disk space to do the kernel
> > > > builds with a cross-compiler, and local (native) builds on the PWS are
> > > > taking 36+ hours each these days.  Unless I get *really* lucky with the
> > > > bisects, the task will take a couple of weeks.
> > > Confirmed that v5.11.0 hard locks up on presenting the X-Desktop
> > > login screen whereas v5.10.0 is fine. This is on a XP1000 with
> > > a Radeon HD4350.
> > And the first bad commit is:
> > 
> > 0fe3cf3a53b5c1205ec7d321be1185b075dff205 is the first bad commit
> > commit 0fe3cf3a53b5c1205ec7d321be1185b075dff205
> > Author: Christian König <christian.koenig@amd.com>
> > Date:   Sat Oct 24 13:12:23 2020 +0200
> > 
> >      drm/radeon: switch to new allocator v2
> >      It should be able to handle all cases here.
> >      v2: fix debugfs as well
> >      Signed-off-by: Christian König <christian.koenig@amd.com>
> >      Reviewed-by: Dave Airlie <airlied@redhat.com>
> >      Reviewed-by: Madhav Chauhan <madhav.chauhan@amd.com>
> >      Tested-by: Huang Rui <ray.huang@amd.com>
> >      Link: https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpatchwork.freedesktop.org%2Fpatch%2F397088%2F%3Fseries%3D83051%26rev%3D1&amp;data=04%7C01%7Cchristian.koenig%40amd.com%7Ce271ea2552a640dfec1408d8f81964a3%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637532135545775310%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&amp;sdata=UYwXgn6lAsES4q8p944kP0Y%2BGzqHRwSMXgrQvZXwXzM%3D&amp;reserved=0
> > 
> > :040000 040000 4e643ef861b921392bc67be21a42298c91c7ff7a b36453567c3176a3cd50fa0b23886b0fd642560d M	drivers
> > 
> > Cheers
> > Michael.
> 

Re: X11 system lockup with 5.11.0 kernel

[Kirsten Bromilow]

Please stop sending these emails. They are not Relevant to me. Thanks 

Sent from my iPhone

> On 6 Apr 2021, at 10:57, Christian König <christian.koenig@amd.com> wrote:
> 
> That is a known issue fixed in follow up 5.11.x kernels.
> 
> Regards,
> Christian.
> 
>> Am 05.04.21 um 11:58 schrieb Michael Cree:
>>> On Mon, Apr 05, 2021 at 04:55:15PM +1200, Michael Cree wrote:
>>> On Sun, Apr 04, 2021 at 11:47:58PM -0500, Bob Tracy wrote:
>>>> On Wed, Mar 31, 2021 at 11:04:42AM +0200, Maciej W. Rozycki wrote:
>>>>>  I think the only feasible way of determining what has happened here is
>>>>> that you track the offending change down by bisecting the upstream kernel
>>>>> repository with `git bisect'.
>>>> That would normally be what I would do, and it may yet happen.  Problem
>>>> is, I don't have a 64-bit system with enough disk space to do the kernel
>>>> builds with a cross-compiler, and local (native) builds on the PWS are
>>>> taking 36+ hours each these days.  Unless I get *really* lucky with the
>>>> bisects, the task will take a couple of weeks.
>>> Confirmed that v5.11.0 hard locks up on presenting the X-Desktop
>>> login screen whereas v5.10.0 is fine. This is on a XP1000 with
>>> a Radeon HD4350.
>> And the first bad commit is:
>> 
>> 0fe3cf3a53b5c1205ec7d321be1185b075dff205 is the first bad commit
>> commit 0fe3cf3a53b5c1205ec7d321be1185b075dff205
>> Author: Christian König <christian.koenig@amd.com>
>> Date:   Sat Oct 24 13:12:23 2020 +0200
>> 
>>     drm/radeon: switch to new allocator v2
>>          It should be able to handle all cases here.
>>          v2: fix debugfs as well
>>          Signed-off-by: Christian König <christian.koenig@amd.com>
>>     Reviewed-by: Dave Airlie <airlied@redhat.com>
>>     Reviewed-by: Madhav Chauhan <madhav.chauhan@amd.com>
>>     Tested-by: Huang Rui <ray.huang@amd.com>
>>     Link: https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpatchwork.freedesktop.org%2Fpatch%2F397088%2F%3Fseries%3D83051%26rev%3D1&amp;data=04%7C01%7Cchristian.koenig%40amd.com%7Ce271ea2552a640dfec1408d8f81964a3%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637532135545775310%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&amp;sdata=UYwXgn6lAsES4q8p944kP0Y%2BGzqHRwSMXgrQvZXwXzM%3D&amp;reserved=0
>> 
>> :040000 040000 4e643ef861b921392bc67be21a42298c91c7ff7a b36453567c3176a3cd50fa0b23886b0fd642560d M    drivers
>> 
>> Cheers
>> Michael.
> 

Re: X11 system lockup with 5.11.0 kernel

[Christian König]

Am 06.04.21 um 11:14 schrieb Michael Cree:
> On Tue, Apr 06, 2021 at 09:08:10AM +0200, Christian König wrote:
>> That is a known issue fixed in follow up 5.11.x kernels.
> Well, it's intriguing that you say that because the latest 5.11.x
> kernel available from https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.kernel.org%2F&data=04%7C01%7Cchristian.koenig%40amd.com%7C4bc7eae6b1c14259a35608d8f8dc6908%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637532973258538981%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&sdata=hgwidEjS4X1IBGx7koSUTWW0y3WHAN4AT4moJvf%2BK3s%3D&reserved=0 (i.e. 5.11.11) is also bad
> and locks up hard when X is started on my Alpha XP1000.

Well *that* is rather interesting. We have considered dropping Alpha 
support because we couldn't find somebody with that hardware any more.

The patch you mentioned has the following bug fix associated with it:

commit e0658f970a7f3d85431c6803b7d5169444fb11b0
Author: Christian König <christian.koenig@amd.com>
Date:   Tue Jan 5 18:55:47 2021 +0100

     drm/radeon: stop re-init the TTM page pool

     Drivers are not supposed to init the page pool directly any more.

     Signed-off-by: Christian König <christian.koenig@amd.com>
     Reviewed-by: Huang Rui <ray.huang@amd.com>
     Link: https://patchwork.freedesktop.org/patch/412153/

Please make sure that you got this, but when 5.11.11 doesn't work either 
I would expect that.

Do you have a full dmesg of the system?

Thanks,
Christian.

>
> Cheers
> Michael.
>
>> Am 05.04.21 um 11:58 schrieb Michael Cree:
>>> On Mon, Apr 05, 2021 at 04:55:15PM +1200, Michael Cree wrote:
>>>> On Sun, Apr 04, 2021 at 11:47:58PM -0500, Bob Tracy wrote:
>>>>> On Wed, Mar 31, 2021 at 11:04:42AM +0200, Maciej W. Rozycki wrote:
>>>>>>    I think the only feasible way of determining what has happened here is
>>>>>> that you track the offending change down by bisecting the upstream kernel
>>>>>> repository with `git bisect'.
>>>>> That would normally be what I would do, and it may yet happen.  Problem
>>>>> is, I don't have a 64-bit system with enough disk space to do the kernel
>>>>> builds with a cross-compiler, and local (native) builds on the PWS are
>>>>> taking 36+ hours each these days.  Unless I get *really* lucky with the
>>>>> bisects, the task will take a couple of weeks.
>>>> Confirmed that v5.11.0 hard locks up on presenting the X-Desktop
>>>> login screen whereas v5.10.0 is fine. This is on a XP1000 with
>>>> a Radeon HD4350.
>>> And the first bad commit is:
>>>
>>> 0fe3cf3a53b5c1205ec7d321be1185b075dff205 is the first bad commit
>>> commit 0fe3cf3a53b5c1205ec7d321be1185b075dff205
>>> Author: Christian König <christian.koenig@amd.com>
>>> Date:   Sat Oct 24 13:12:23 2020 +0200
>>>
>>>       drm/radeon: switch to new allocator v2
>>>       It should be able to handle all cases here.
>>>       v2: fix debugfs as well
>>>       Signed-off-by: Christian König <christian.koenig@amd.com>
>>>       Reviewed-by: Dave Airlie <airlied@redhat.com>
>>>       Reviewed-by: Madhav Chauhan <madhav.chauhan@amd.com>
>>>       Tested-by: Huang Rui <ray.huang@amd.com>
>>>       Link: https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpatchwork.freedesktop.org%2Fpatch%2F397088%2F%3Fseries%3D83051%26rev%3D1&amp;data=04%7C01%7Cchristian.koenig%40amd.com%7C4bc7eae6b1c14259a35608d8f8dc6908%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637532973258538981%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&amp;sdata=A0AQyT01bn4CjQeeQuanoh1xGdq%2FEHdE%2FggHzxEzaIA%3D&amp;reserved=0
>>>
>>> :040000 040000 4e643ef861b921392bc67be21a42298c91c7ff7a b36453567c3176a3cd50fa0b23886b0fd642560d M	drivers
>>>
>>> Cheers
>>> Michael.

Re: X11 system lockup with 5.11.0 kernel

[John Paul Adrian Glaubitz]

Hi Christian!

On 4/6/21 12:15 PM, Christian König wrote:
> Am 06.04.21 um 11:14 schrieb Michael Cree:
>> On Tue, Apr 06, 2021 at 09:08:10AM +0200, Christian König wrote:
>>> That is a known issue fixed in follow up 5.11.x kernels.
>> Well, it's intriguing that you say that because the latest 5.11.x
>> kernel available from https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.kernel.org%2F&data=04%7C01%7Cchristian.koenig%40amd.com%7C4bc7eae6b1c14259a35608d8f8dc6908%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637532973258538981%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&sdata=hgwidEjS4X1IBGx7koSUTWW0y3WHAN4AT4moJvf%2BK3s%3D&reserved=0 (i.e. 5.11.11) is also bad
>> and locks up hard when X is started on my Alpha XP1000.
> 
> Well *that* is rather interesting. We have considered dropping Alpha support
> because we couldn't find somebody with that hardware any more.

There are plenty of us within the Gentoo, Debian and NetBSD projects, just ask :-).

We're also supporting everything else that most commercial vendors consider obsolete
such as PA-RISC, M68k, big-endian PowerPC (32 and 64 bits) SPARC and so on, in case
you need testing there.

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaubitz@debian.org
`. `'   Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
  `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Re: X11 system lockup with 5.11.0 kernel

[Bob Tracy]

On Tue, Apr 06, 2021 at 12:19:29PM +0200, John Paul Adrian Glaubitz wrote:
> We're also supporting everything else that most commercial vendors consider obsolete
> such as PA-RISC, M68k, big-endian PowerPC (32 and 64 bits) SPARC and so on, in case
> you need testing there.

(Mostly including the above just as a reference to the most recent
posting in this thread...)

As of mainline kernel 5.12.0, the fix I (we) have been waiting for still
hasn't been included.  My alpha still locks up when X11 starts.

Stuck at kernel version 5.10.0 for the time being.

Respectfully,
--Bob

Re: X11 system lockup with 5.11.0 kernel

[Maciej W. Rozycki]

On Wed, 2 Jun 2021, Bob Tracy wrote:

> > We're also supporting everything else that most commercial vendors consider obsolete
> > such as PA-RISC, M68k, big-endian PowerPC (32 and 64 bits) SPARC and so on, in case
> > you need testing there.
> 
> (Mostly including the above just as a reference to the most recent
> posting in this thread...)
> 
> As of mainline kernel 5.12.0, the fix I (we) have been waiting for still
> hasn't been included.  My alpha still locks up when X11 starts.
> 
> Stuck at kernel version 5.10.0 for the time being.

 I have lost track about this issue, so please fill me in as to whether 
the offending commit causing the regression has been bisected or not.

  Maciej

Re: X11 system lockup with 5.11.0 kernel

[Bob Tracy]

On Thu, Jun 03, 2021 at 03:15:05PM +0200, Maciej W. Rozycki wrote:
>  I have lost track about this issue, so please fill me in as to whether 
> the offending commit causing the regression has been bisected or not.

It has.  Michael Cree reported the following back on April 5th:

And the first bad commit is:

0fe3cf3a53b5c1205ec7d321be1185b075dff205 is the first bad commit
commit 0fe3cf3a53b5c1205ec7d321be1185b075dff205
Author: Christian König <christian.koenig@amd.com>
Date:   Sat Oct 24 13:12:23 2020 +0200

    drm/radeon: switch to new allocator v2
    
    It should be able to handle all cases here.
    
    v2: fix debugfs as well
    
    Signed-off-by: Christian König <christian.koenig@amd.com>
    Reviewed-by: Dave Airlie <airlied@redhat.com>
    Reviewed-by: Madhav Chauhan <madhav.chauhan@amd.com>
    Tested-by: Huang Rui <ray.huang@amd.com>
    Link: https://patchwork.freedesktop.org/patch/397088/?series=83051&rev=1

:040000 040000 4e643ef861b921392bc67be21a42298c91c7ff7a b36453567c3176a3cd50fa0b23886b0fd642560d M	drivers

--Bob

Re: X11 system lockup with 5.11.0 kernel

[Bob Tracy]

On Fri, Jun 04, 2021 at 12:18:58AM -0500, Bob Tracy wrote:
> On Thu, Jun 03, 2021 at 03:15:05PM +0200, Maciej W. Rozycki wrote:
> >  I have lost track about this issue, so please fill me in as to whether 
> > the offending commit causing the regression has been bisected or not.
> 
> It has.  Michael Cree reported the following back on April 5th:
> 
> And the first bad commit is:
> 
> 0fe3cf3a53b5c1205ec7d321be1185b075dff205 is the first bad commit
> commit 0fe3cf3a53b5c1205ec7d321be1185b075dff205
> Author: Christian König <christian.koenig@amd.com>
> Date:   Sat Oct 24 13:12:23 2020 +0200
> 
>     drm/radeon: switch to new allocator v2
>     
>     It should be able to handle all cases here.
>     
>     v2: fix debugfs as well
>     
>     Signed-off-by: Christian König <christian.koenig@amd.com>
>     Reviewed-by: Dave Airlie <airlied@redhat.com>
>     Reviewed-by: Madhav Chauhan <madhav.chauhan@amd.com>
>     Tested-by: Huang Rui <ray.huang@amd.com>
>     Link: https://patchwork.freedesktop.org/patch/397088/?series=83051&rev=1
> 
> :040000 040000 4e643ef861b921392bc67be21a42298c91c7ff7a b36453567c3176a3cd50fa0b23886b0fd642560d M	drivers

There were a few follow-up messages in this thread that left me with the
impression there *may* have been a patch submitted, although Christian
complained at the time he was having problems locating Alpha hardware to
test with.

The current (5.12.0 kernel) problem symptoms show some "improvement".
I at least got to the point that the login screen displayed, but it
had a bit of pixelation/distortion in a few areas indicative of "bad
things about to happen".  Then I got the expected system lock-up,
just as I originally reported: had to hit the reset switch to recover.

--Bob

Re: X11 system lockup with 5.11.0 kernel

[Bob Tracy]

Quick update: if this issue was ever fixed, the patch hasn't made it
into the mainline kernel as of 5.13.0.  I'm still getting the system
lock-up when X11 starts, and have to hit the reset switch to recover.

For whatever it might be worth, the mainline 5.10.0 kernel continues
to work properly alongside all the user space changes in "sid" that
have happened since late last year.

Respectfully,
--Bob

On Fri, Jun 04, 2021 at 12:37:14AM -0500, Bob Tracy wrote:
> On Fri, Jun 04, 2021 at 12:18:58AM -0500, Bob Tracy wrote:
> > On Thu, Jun 03, 2021 at 03:15:05PM +0200, Maciej W. Rozycki wrote:
> > >  I have lost track about this issue, so please fill me in as to whether 
> > > the offending commit causing the regression has been bisected or not.
> > 
> > It has.  Michael Cree reported the following back on April 5th:
> > 
> > And the first bad commit is:
> > 
> > 0fe3cf3a53b5c1205ec7d321be1185b075dff205 is the first bad commit
> > commit 0fe3cf3a53b5c1205ec7d321be1185b075dff205
> > Author: Christian König <christian.koenig@amd.com>
> > Date:   Sat Oct 24 13:12:23 2020 +0200
> > 
> >     drm/radeon: switch to new allocator v2
> >     
> >     It should be able to handle all cases here.
> >     
> >     v2: fix debugfs as well
> >     
> >     Signed-off-by: Christian König <christian.koenig@amd.com>
> >     Reviewed-by: Dave Airlie <airlied@redhat.com>
> >     Reviewed-by: Madhav Chauhan <madhav.chauhan@amd.com>
> >     Tested-by: Huang Rui <ray.huang@amd.com>
> >     Link: https://patchwork.freedesktop.org/patch/397088/?series=83051&rev=1
> > 
> > :040000 040000 4e643ef861b921392bc67be21a42298c91c7ff7a b36453567c3176a3cd50fa0b23886b0fd642560d M	drivers
> 
> There were a few follow-up messages in this thread that left me with the
> impression there *may* have been a patch submitted, although Christian
> complained at the time he was having problems locating Alpha hardware to
> test with.
> 
> The current (5.12.0 kernel) problem symptoms show some "improvement".
> I at least got to the point that the login screen displayed, but it
> had a bit of pixelation/distortion in a few areas indicative of "bad
> things about to happen".  Then I got the expected system lock-up,
> just as I originally reported: had to hit the reset switch to recover.

Re: X11 system lockup with 5.11.0 kernel

[Michael Cree]

I had intended to assist in testing with real hardware but there
are other issues due to the 5.10 kernel on Alpha that need fixing
first and I am working on that.  I am hoping to come back to this
and can run some tests in the near future.

Cheers,
Michael.

On Thu, Jul 01, 2021 at 07:41:09AM -0500, Bob Tracy wrote:
> Quick update: if this issue was ever fixed, the patch hasn't made it
> into the mainline kernel as of 5.13.0.  I'm still getting the system
> lock-up when X11 starts, and have to hit the reset switch to recover.
> 
> For whatever it might be worth, the mainline 5.10.0 kernel continues
> to work properly alongside all the user space changes in "sid" that
> have happened since late last year.
> 
> Respectfully,
> --Bob
> 
> On Fri, Jun 04, 2021 at 12:37:14AM -0500, Bob Tracy wrote:
> > On Fri, Jun 04, 2021 at 12:18:58AM -0500, Bob Tracy wrote:
> > > On Thu, Jun 03, 2021 at 03:15:05PM +0200, Maciej W. Rozycki wrote:
> > > >  I have lost track about this issue, so please fill me in as to whether 
> > > > the offending commit causing the regression has been bisected or not.
> > > 
> > > It has.  Michael Cree reported the following back on April 5th:
> > > 
> > > And the first bad commit is:
> > > 
> > > 0fe3cf3a53b5c1205ec7d321be1185b075dff205 is the first bad commit
> > > commit 0fe3cf3a53b5c1205ec7d321be1185b075dff205
> > > Author: Christian König <christian.koenig@amd.com>
> > > Date:   Sat Oct 24 13:12:23 2020 +0200
> > > 
> > >     drm/radeon: switch to new allocator v2
> > >     
> > >     It should be able to handle all cases here.
> > >     
> > >     v2: fix debugfs as well
> > >     
> > >     Signed-off-by: Christian König <christian.koenig@amd.com>
> > >     Reviewed-by: Dave Airlie <airlied@redhat.com>
> > >     Reviewed-by: Madhav Chauhan <madhav.chauhan@amd.com>
> > >     Tested-by: Huang Rui <ray.huang@amd.com>
> > >     Link: https://patchwork.freedesktop.org/patch/397088/?series=83051&rev=1
> > > 
> > > :040000 040000 4e643ef861b921392bc67be21a42298c91c7ff7a b36453567c3176a3cd50fa0b23886b0fd642560d M	drivers
> > 
> > There were a few follow-up messages in this thread that left me with the
> > impression there *may* have been a patch submitted, although Christian
> > complained at the time he was having problems locating Alpha hardware to
> > test with.
> > 
> > The current (5.12.0 kernel) problem symptoms show some "improvement".
> > I at least got to the point that the login screen displayed, but it
> > had a bit of pixelation/distortion in a few areas indicative of "bad
> > things about to happen".  Then I got the expected system lock-up,
> > just as I originally reported: had to hit the reset switch to recover.

Re: X11 system lockup with 5.11.0 kernel

[Bob Tracy]

On Mon, Sep 06, 2021 at 11:00:27AM +1200, Michael Cree wrote:
> I had intended to assist in testing with real hardware but there
> are other issues due to the 5.10 kernel on Alpha that need fixing
> first and I am working on that.  I am hoping to come back to this
> and can run some tests in the near future.

I am delighted to report that this issue has finally been resolved
as of the 5.14.0 mainline kernel.

There is a completely unrelated annoyance involving APC UPSs and a
flood of "hid-generic: <device_id> control queue full" messages on
the console.  This was reported and fixed as of 01 Sep 2021, but
the fix hasn't made it into mainline yet :-(.

Respectfully,
--Bob