segfault in i965_dri.so Has this bug been fixed?

Asked by tomdean on 2019-08-04

I have been running around in circles reading bug reports to see if this has been fixed. I have an application that segfaults after an hour, or so. Done this two times.

As far as I can tell, this has been marked as fixed. Correct?

> uname -a
Linux Meerkat 5.0.0-23-generic #24~18.04.1-Ubuntu SMP Mon Jul 29 16:12:28 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

> lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.2 LTS
Release: 18.04
Codename: bionic

> dmesg -T | tail...
Sun Aug 4 14:45:02 2019] python2[31566]: segfault at 40 ip 00007f0e72c9a1c6 sp 00007ffdb1f6afb0 error 6 in i965_dri.so[7f0e7265a000+a6a000]
[Sun Aug 4 14:45:02 2019] Code: fe ff ff 8b 95 00 ff ff ff f3 0f 10 a5 e0 fe ff ff c7 85 3c ff ff ff 0c 00 00 00 f3 0f 10 9d c0 fe ff ff 4c 89 ad 40 ff ff ff <f3> 0f 11 20 c7 85 34 ff ff ff 04 00 00 00 c6 85 38 ff ff ff 01 f3
[Sun Aug 4 15:37:08 2019] python2[32112]: segfault at 20 ip 00007f94b78b39e4 sp 00007ffd06811b00 error 6 in i965_dri.so[7f94b7271000+a6a000]
[Sun Aug 4 15:37:08 2019] Code: 84 00 00 00 00 00 84 c9 74 7c f3 0f 10 0a f3 0f 10 42 04 0f 2e c8 0f 86 da 00 00 00 66 0f 7e c9 31 f6 0f 1f 40 00 48 83 c2 18 <89> 30 89 48 04 48 83 c0 08 48 39 d7 74 6e 80 bb 5b 97 00 00 00 0f

Question information

Language:
English Edit question
Status:
Answered
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Last query:
2019-08-06
Last reply:
2019-08-06

Do other kernels act the same ? You can boot older kernels from GRUB

tomdean (tomdean) said : #2

On 8/5/19 5:17 AM, actionparsnip wrote:
> Your question #682592 on Ubuntu changed:
> https://answers.launchpad.net/ubuntu/+question/682592
>
> Status: Open => Needs information
>
> actionparsnip requested more information:
> Do other kernels act the same ? You can boot older kernels from GRUB
>
I will test that tonight.

I believe this is the 'partial refresh' bug. It only seems to happen
when I am doing other things and the respective display is not on top.

I tried this three times with the 5.0.0-23-generic kernel. The first
two times it segfault'd after about an hour. The third time, I left it
run unattended, on top, for about two hours.

I will try the 4.15.0-55-generic kernel tonight.

tomdean (tomdean) said : #3

On 8/5/19 5:17 AM, actionparsnip wrote:
> Your question #682592 on Ubuntu changed:
> https://answers.launchpad.net/ubuntu/+question/682592
>
> Status: Open => Needs information
>
> actionparsnip requested more information:
> Do other kernels act the same ? You can boot older kernels from GRUB
>
 > lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.2 LTS
Release: 18.04
Codename: bionic

I booted

 > uname -a
Linux Meerkat 4.15.0-55-generic #60-Ubuntu SMP Tue Jul 2 18:22:20 UTC
2019 x86_64 x86_64 x86_64 GNU/Linux

and started the application, simple_ra.

I ran the application from 10:30 to 12:45, with no problems. During
this time, I did other things, so simple_ra was not always on top and
lots of times was only able to refresh parts of its display area.

I guess the next thing is to boot the 5.0.0-23-generic kernel and try to
reproduce the segfault? Or, is two times enough?

Tom Dean

tomdean (tomdean) said : #4

On 8/5/19 12:52 PM, tomdean wrote:
> Your question #682592 on Ubuntu changed:
> https://answers.launchpad.net/ubuntu/+question/682592
>
> You gave more information on the question:
> On 8/5/19 5:17 AM, actionparsnip wrote:
>> Your question #682592 on Ubuntu changed:
>> https://answers.launchpad.net/ubuntu/+question/682592
>>
>> Status: Open => Needs information
>>
>> actionparsnip requested more information:
>> Do other kernels act the same ? You can boot older kernels from GRUB
>>
> > lsb_release -a
> No LSB modules are available.
> Distributor ID: Ubuntu
> Description: Ubuntu 18.04.2 LTS
> Release: 18.04
> Codename: bionic
>
> I booted
>
> > uname -a
> Linux Meerkat 4.15.0-55-generic #60-Ubuntu SMP Tue Jul 2 18:22:20 UTC
> 2019 x86_64 x86_64 x86_64 GNU/Linux
>
> and started the application, simple_ra.
>
> I ran the application from 10:30 to 12:45, with no problems. During
> this time, I did other things, so simple_ra was not always on top and
> lots of times was only able to refresh parts of its display area.
>
> I guess the next thing is to boot the 5.0.0-23-generic kernel and try to
> reproduce the segfault? Or, is two times enough?
>
> Tom Dean
>

I booted

 > uname -a
Linux Meerkat 5.0.0-23-generic #24~18.04.1-Ubuntu SMP Mon Jul 29
16:12:28 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

and started the application simple_ra.

As before, I started doing other things so simple_ra was not always on top.
After about an hour,

 > dmesg -T | tail
[Mon Aug 5 16:25:31 2019] pcieport 0000:00:1c.0: device [8086:9d10]
error status/mask=00002001/00002000
[Mon Aug 5 16:25:31 2019] pcieport 0000:00:1c.0: [ 0] RxErr

[Mon Aug 5 16:25:31 2019] pcieport 0000:02:00.0: Refused to change
power state, currently in D3
[Mon Aug 5 16:25:31 2019] pci_bus 0000:03: busn_res: [bus 03] is released
[Mon Aug 5 16:25:31 2019] pci_bus 0000:04: busn_res: [bus 04-38] is
released
[Mon Aug 5 16:25:31 2019] pci_bus 0000:39: busn_res: [bus 39] is released
[Mon Aug 5 16:25:31 2019] pci_bus 0000:02: busn_res: [bus 02-39] is
released
[Mon Aug 5 16:26:39 2019] wlp58s0: AP 60:38:e0:db:a9:7a changed
bandwidth, new config is 2412 MHz, width 1 (2412/0 MHz)
[Mon Aug 5 17:56:59 2019] python2[2994]: segfault at 40 ip
00007f820f4a81c6 sp 00007ffff892e8f0 error 6 in
i965_dri.so[7f820ee68000+a6a000]
[Mon Aug 5 17:56:59 2019] Code: fe ff ff 8b 95 00 ff ff ff f3 0f 10 a5
e0 fe ff ff c7 85 3c ff ff ff 0c 00 00 00 f3 0f 10 9d c0 fe ff ff 4c 89
ad 40 ff ff ff <f3> 0f 11 20 c7 85 34 ff ff ff 04 00 00 00 c6 85 38 ff
ff ff 01 f3

I noticed some strange things in /var/log/syslog. Some time stamps are
not in order. And, a strange message:
Aug 5 17:34:32 Meerkat gnome-shell[2078]: Some code accessed the
property 'WindowPreviewMenu' on the module 'windowPreview'. That
property was defined with 'let' or 'const' inside the module. This was
previously supported, but is not correct according to the ES6 standard.
Any symbols to be exported from a module must be defined with 'var'. The
property access will work as previously for the time being, but please
fix your code anyway.

I suggest you report a bug. Also please make sure that you have the latest BIOS

tomdean (tomdean) said : #6

Is the bug database down? I can not connect.

Can you help with this problem?

Provide an answer of your own, or ask tomdean for more information if necessary.

To post a message you must log in.