Bug#882934: Crash debugging

[Dima Kogan]

Joe  writes:

> OK, it does look like the graphics driver, then. I don't play games, so
> I've never worried about it, and it looks like I'm using the
> xserver-xorg-video-radeon driver. firmware-amd-graphics is installed.
>
> Should I try getting hold of the AMD binary driver? It's onboard
> graphics on a Gigabyte MB, about seven years old.

I found a machine with a radeon gpu. Like yours it's a desktop with an
onboard gpu, and it's about the same vintage even. I tried running with
the "ati" X driver and the "radeon" kernel driver, and things appear to
work ok; nothing crashes.

My GPU is

  01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Park [Mobility Radeon HD 5430] [1002:68e1]

X happily loads the drivers, and things work for me, but our
configurations probably don't match up. What does your 'lspci -nn' say,
and do you have the "radeon" kernel module loaded, and what does
'glxinfo' say, and what does 'dpkg -l "xserver-xorg-video-*"' say and
can I get a copy of the /var/log/Xorg.0.log ?

If you don't care anymore, and want me to go away, tell me that too :)

Bug#882934: Crash debugging

[Dima Kogan]

Joe  writes:

> On Fri, 16 Mar 2018 16:42:43 -0700
> Dima Kogan  wrote:
>
>> Can you try to run pcb without hardware acceleration? You can do this
>> with
>>
>>  LIBGL_ALWAYS_SOFTWARE=true pcb-gtk
>
> Yes, that fixes it. A quick test suggests it is running OK.
>
> OK, it does look like the graphics driver, then. I don't play games, so
> I've never worried about it, and it looks like I'm using the
> xserver-xorg-video-radeon driver. firmware-amd-graphics is installed.
>
> Should I try getting hold of the AMD binary driver? It's onboard
> graphics on a Gigabyte MB, about seven years old.

That's interesting; glad we narrowed down the problem. I don't have any
ATI hardware, so can't reproduce this. I'm assuming no other
applications crash like this? I'm wondering if pcb is doing something
different from other programs.

Can I please get the versions of your graphics driver packages (ones you
mentioned above), and the hardware IDs:

  lspci -nn | grep VGA

Not entirely sure what I can do with that, but it'd be good to have.
I'll try to chase down some ATI hardware. Otherwise you'll be running
experiments for me for a long time.

Bug#882934: Crash debugging

[Dima Kogan]

Let's move this back to the bug list.

Thanks for the debugging traces. I didn't see any smoking gun, but
there're things I'd like to follow-up on to isolate the issue and then
to hopefully allow me to reproduce it.

1. You have a customized gtk configuration that uses a theme no longer
   in Debian. Can you please try to rename your ~/.gtkrc-2.0 file to
   something else to see if that makes the crash go away? I'm guessing
   this doesn't matter, but checking would be good.

2. The crash makes me suspect that something related to graphics is at
   fault. You have a radeon graphics card of some sort it looks like,
   which could explain why I can't reproduce (my hardware is different).
   How old/new is your graphics drivers? Can you try to run pcb without
   hardware acceleration? You can do this with

 LIBGL_ALWAYS_SOFTWARE=true pcb-gtk

   Also please try

 LIBGL_ALWAYS_INDIRECT=true pcb-gtk

Hopefully one of these resolves the crash, which would tell us where to
look next.

Thanks!