Comment 172 for bug 541511
Revision history for this message
| Dimitry Verkholashin (dimitrygv) wrote Re: [Bug 541511] Re: MASTER: [i855] GPU lockup (apport-crash) | #172 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
c'mon you know it is a security bug that relates to Xorg (intel i915GM) ,
GDM, compiz, emerald and Ubuntu update manager (every crash is tied to
update manager or maybe the way it uses network and choice of algorithms to
verify your integrity sums of packages). every symptom had been reproduced
and can be reproduced again. i am running on some legacy equipment. let's
see if it works on UNIX without GDM
On Wed, Apr 21, 2010 at 2:16 AM, Bryce Harrington <<email address hidden>
> wrote:
> We don't need further confirmations from people seeing the issue.
>
> Also, we don't need further reports of how it was worked around; we know
> there's several ways of working around it. Unfortunately what works for
> one person doesn't for another.
>
> This has been an extremely frustrating bug from a developer perspective,
> probably almost as frustrating as it is from a user perspective. It
> seems whenever we make a change to fix something for one set of users,
> it just causes breakage for some other set. There does not seem to be
> any particular combination of knob settings that makes things functional
> for *all* users.
>
> So what we've opted to do is turn off KMS for this hardware but pretty
> much leave all other settings to defaults. So people for whom this
> configuration works will have 3D and all the usual -intel functionality,
> just not the boot prettiness. For the set of users that find this is
> not a good configuration, we've documented the issue in the release
> notes with a link to the various workarounds people have found, here:
>
> https:/
>
> If anyone discovers additional workarounds, or has ideas on improving
> this documentation, please feel welcome to edit this page. It may help
> your fellow 8xx users.
>
> It is our hope that there will come to be upstream fixes that are viable
> to backport. If we get enough fixes that we feel confident, we *might*
> re-enable KMS for 8xx chips on lucid at some point.
>
> There are likely to be a lot of patches flying around. If you wish to
> provide them in a PPA, that's cool. Just be mindful that our goal
> ultimately is to get a fix into Lucid, and time you can put towards that
> goal could help a lot.
>
> The nature of this bug is such that it's really sensitive to
> conditions. So you may find a configuration or patch that makes the
> issue totally go away on your system and someone else's, but breaks
> things on 3 other people's systems with exactly the same hardware. So
> getting a patch that fixes it for *everyone* is going to be really
> tough.
>
> --
> MASTER: [i855] GPU lockup (apport-crash)
> https:/
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>
> Status in X.org xf86-video-intel: Confirmed
> Status in “xserver-
> Status in “xserver-
>
> Bug description:
> Binary package hint: xserver-
>
> This is a MASTER bug report, i.e. not a real bug report, but a tool to help
> manage other bug reports.
>
> Most bug reports on i855 are probably due to the CPU/GPU incoherency
> problem that is now consolidated upstream at
> http://
> from a bug report for i845). For now, we mark all automatically reported GPU
> lockups on i855 as duplicates of this unless there is a reason not to. There
> are some tests you may do to help upstream with this issue, and I will come
> back with instructions here. For those of you who know how to patch and
> compile a kernel you may look at comment #30 (and #6 for what kind of
> feedback they want) in the upstream bug report. Actually, if someone could
> volunteer to build an ubuntu-packaged kernel with this patch for others to
> test, that would be nice.
>
> There is a similar master bug report for i845 at bug 541492.
>
>
>
> To unsubscribe from this bug, go to:
> https:/
>