Stubborn Intel Graphics Bug Haunts Ubuntu 12.04
jones_supa writes "The current long-term support version of Ubuntu (12.04) has been experiencing a remarkably tough-to-crack and widely affecting bug related to laptops using an Intel graphics solution. When the lid is closed, every now and then the desktop freezes and only the mouse cursor can be moved. Compiz is usually found hung in the process, switching to a VT afterwards works. The Freedesktop guys are also informed. Have Slashdotters been bitten by this bug and possibly could offer some detective work to help the OSS community find and apply the correct fix?"
I have been reporting that problem for a while, but they just assume that I am an idiot who just doesn't know how to use a computer.
If something is so important that you feel the need to post it on the internet... It probably isn't that important.
I have this issue on my Dell mini netbook, it's one of the older ones that actually shipped with Ubuntu back in early 2010.
The problem seemed to gradually get worse for a while, and at one point the graphical start-up screen stopped working, and the thing just booted in text mode. The most egregious symptoms went away with the most recent kernel update, but it's hard to tell if the hang-on-wake problem is actually fixed, because it was intermittent anyways.
2*3*3*3*3*11*251
How about this one:
KDE 4 has issues with displaying changes made to files in Dolphin. Sometimes the changes show up fine, other times they don't and you have to refresh manually.
Oh and... "Ubuntu" because that magic word has to be inserted for Slashdots "editors" (and I use the term loosely) to care.
There! Now give me a front-page story!
AntiFA: An abbreviation for Anti First Amendment.
PATIENT: Doctor! Doctor! It hurts when I do this...
DOCTOR: Well stop doing that then.
Ah, the old ones...
And this is why I use a Mac. I don't have to worry about any of that unreliable unix-y stuff and shoddy quality from Intel!
I was under the impression that the ubuntu community had their own channels (forums, lists, etc) for this sort of thing. Are we now the help desk for a linux distribution?
Now if ubuntu had been found to have hidden bestiality videos embedded in it somewhere, that would be news.
Come to think of it, maybe that's what the version names are about. I need to find the hidden porn involving a Hoary Hedgehog or a Precise Pangolin!
Silence is a state of mime.
It's an awful problem.
LTS release that can't reliably suspend (which means, it can't suspend) on Lenovo Thinkpads...
Ubuntu fixes this rapidly, in-stream or they cease to be credible.
Thank you Slashdot, for bringing attention to this.
Tired of Political Trolls? Opt Out!
I have to defend the "Works For Me"-closing. It is *very* hard to track bugs which are not showing up on your machine (or any test machine). You never know exactly what that user has already done to the machine prior to the bug occurring and it's hard to get additional information. While it for sure sucks if you get that response, the immediate reaction should be "well, how can I help you find this" and not "I still have that problem" as it happens many times. Also many bug reports which are closed with "works for me" never received any attention from the reporter after reported.
My view is that this is only an individual symptom of a larger scale problem. It seems that there are a lot of old, verified, almost showstopper bugs that just get ignored. I'm too busy/lazy to hunt the links at this point, but for example GNOME3 has probably from the beginning had a bug that it gets very sluggish after a few days, at least on some GPU's/drivers, the kernel's trashing behavior in out-of-memory situations is horrible, the audio stack is a horrible mess etc.
It's probably a wider problem of QA, that may be very difficult to solve. At least as a programmer I'm first to admit that I don't want to use my spare time fixing bugs. Debian's almost draconian policies seem to do quite well in terms of stability, but the desktop often lags behind (this may be unavoidable) and the desktop doesn't seem to be a very high priority for them.
PS. This post in no way suggests that things are better, or aren't a lot worse, in Windows-world and OS X with the controlled hardware platform is a very different situation. Maybe I should check if the grass is really greener in the BSD-side.
Then it is probably another similar bug, but not the same one. When folks like you add "I have this bug too, but everything else is different!" Then you are just adding more noise to the signal that is the bug report.
You have a different problem, it might look similar, report a new bug. Supply the requested information.
On an Acer Aspire 5313. I've been dealing with it simply by doing as the summary suggests: switching to VT and restarting lighttdm. I'd be happy to help any way I can. The problem doesn't seem to happen every time it suspends, but it happens enough to be annoying. Mostly I just use that laptop for browsing the web so it's no big deal, but I can see it being a major issue if somebody was, for example, working on an important document and hadn't saved.
You didn't really need to switch to Fedora over that. What I did when Unity got on my nerves was sudo apt-get install xubuntu-desktop
True, but I see it happen all of the time that a program works on a developer's machine (with all of the development libraries and development tools installed and god-only-knows what custom tweaking).
Competition Good, Monopoly Bad.
I am not convinced that this is just a linux problem. I have a laptop with a Intel HD Graphics adapter (8086:01116) running Window 7 pro, that experiences similar behavior when coming out of suspend. Some times the screen freezes and the mouse moves, other times the mouse freezes but the screen continues to update (for instance alt-tab navigates windows that still respond to the keyboard).
.
Moreover, a kgdb session could likely track this bug down. I'm going to guess that it's a simple locking bug, likely in the intel drivers. Compiz or whatever is performing some operation out of synch with what is "normal" activity and trying to perform a double-lock.
Since cursor operations are tied to a hardware interrupt they still continue to operate.
Another possibility is that the kernel is running at a higher interrupt level in the driver after wakeup, and not locking the iommu/register area away from userspace operations - thus the graphics chip state is getting corrupted and goes into a unknown hardware state. Switching video modes is causing an interrupt which awakens the chip again, and restarting X causes the graphics unit to reset properly.
Yes, I used to be a graphics driver developer for X long, long ago.
I said no... but I missed and it came out yes.
I have Intel integrated graphics and I had similar problems, but following line into grub.conf at the end of kernel line fixed it: pcie_aspm=force i915.i915_enable_rc6=1 i915.lvds_downclock=1 i915.i915_enable_fbc=1
Yes, that would be helpful. Even better is if you have the machine and the user right next to you and shows you how to reproduce the bug, and then leaves the machine with you (and the user leaves the room...or better, the city).
Don't get me wrong, but it can be freaking hard to track stuff which is not happening on your machine...sometimes it's hard enough even if it is reproducible on a machine you have. Race conditions are such a case. I had some in my application I wrote at work (yeah, totally shame on me for not realizing that obvious thing) and some clients did *never* have a problem and others fell over every few hours. Figuring it out was...tricky...reproducing it even more. Another such case are overflows of all kinds which are not immediately wracking the system, but instead corrupting some parts and then slumber for quite some time.
Dude, just stop. I have reported many critical Ubuntu bugs to Launchpad--I'm talking about stupid bugs that should never have happened, should never have been released, could quickly be fixed or reverted--but no one at Ubuntu is responsible for fixing them, or for taking the lead on getting the right people to fix it, so nothing happens. That, or 6 months after you report it, a bot says, "Thank you for helping Ubuntu by reporting this bug. Please test the latest version of the software to see if the bug still exists." You confirm it, and 6 months later, same thing. Meanwhile, no actual effort has been expended to investigate or fix the bug. It's like a slap in the face to the bug reporter: it's saying that his time is worthless, when he's already spent time dealing with and reporting the bug.
So get off your high horse. There are plenty of people like me who do exactly that: we file bugs, we complain when they are ignored, we complain when they are not fixed, we complain when stupid regressions appear, we complain when boneheaded decisions are made to release buggy garbage that shouldn't have seen the light of packages.ubuntu.com--but Ubuntu does what it wants to do. New and shiny is more important than stable and reliable and consistent--even for a Long Term Support release, big fat ugly smelly bugs go ignored, and pleas to release the blatantly obvious fix fall on deaf ears.
If it wasn't for dpkg and apt, I'd gladly try another distro. One of these days I'll probably go back to Debian, where at least packages have maintainers who are supposed to be responsible for them, and bug reporters don't get told to test unchanged software over and over again.
"Those who consume the bulk of goods are those who make them. We must never forget this secret of our prosperity."