There are two ways this could be addressed. Both require changes to the
apport hook (in xdiagnose):
1. Change the udev rule to trigger on a different combination of
events. (I have an email somewhere discussing what exactly needs
done... I'll have to locate that again.) The possible drawback of this
approach may be that it might hide some valid bugs; not sure.
2. Parse the i915_error_state file prior to filing the bug report, and
programmatically evaluate whether it's a valid report before trying to
send it in. However, I think this might still result in a popup to the
user, which would still present an irritant. Yet, it may be a more
comprehensive way to deal with invalid gpu error states in general.
Potentially we could do both #1 and #2, which might give the best all
around solution. Some experimentation may be needed to get the gpu
hook properly tuned.
Since the apport hook is turned off in the release, there's no point to
SRUing any changes made for this.
** Changed in: xdiagnose (Ubuntu Q-series)
Importance: Undecided => High
** Changed in: xdiagnose (Ubuntu Q-series)
Status: New => Triaged
** Changed in: xdiagnose (Ubuntu Q-series)
Assignee: (unassigned) => Bryce Harrington (bryce)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/983640
Title:
False GPU lockups captured by apport gpu hook unnecessarily
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdiagnose/+bug/983640/+subscriptions
_______________________________________________
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help : https://help.launchpad.net/ListHelp
