Slashdot Mirror
Ubuntu's Laptop Killing Bug Fixed
jeevesbond writes "Back in October of 2007 we discussed a bug that would dramatically shorten the life of laptops using Ubuntu. Ubuntu users will be glad to know that a fix has finally been released for Ubuntu versions 9.04, 8.10 and 8.04 (LTS). However, as this fix is not yet in the update repositories, anyone wishing to test it should follow these instructions for enabling the 'proposed' repository. Report your results on the original bug report. Happy testing!"
Considering this was a fault of the manufacturers, this story is pure and total flamebait. Just don't bother feeding the trolls; don't reply.
Que the stories of laptop hard drives failing before their time and rebuttals and blame shifting from about 200 people, mingled with "in soviet Russia, hard drive crashes you!" jokes and ordered lists that feature question marks and profit.
Oh, and probably a hot grits joke or two.
weirdest thing I ever saw: scientology advertising on slashdot.
Anti-climactic. What happens to those pesky cracks in the walls?
Modding me -1 troll doesn't make me wrong.
Well, one can squarely blame the HD manufacturers (look at the Seagate disaster) and say they need to fix their hardware.
However, when your stuff doesnt work, regardless who's fault it is, it's still broken. And in cases like Ubuntu vs Windows: it'll work in Windows and not work in Ubuntu. Who do you think the user will fault?
ObUserStory: I bought a T61 Thinkpad. Worked fine in Windows, and not so well in Ubuntu. What didnt work? The right side USB ports. If I was a regular user, I'd remove Ubuntu and put Windows back on. However, Im stubborn... and know that Linux shouldnt go disabling ports at seemingly random. Turns out, it was a ACPI bios bug that did so :( So a BIOS update did the trick and fixed everything.
So yes, it may be a manufacturers fault, but that's not where the blame gets placed all the time..
Marcus smokes all of the crack in the walls and goes on a rampage after discovering a bug in his OS causes his laptop to die.
He shoots everybody in the house before beginning an armed standoff with the SWAT team, then kills 3 cops(one in full riot gear) before a sniper in a police helicopter shoots the gun out of his hand. Stunned but unharmed, Marcus then slips and falls off the roof into his unkempt wading pool before he is transanally disemboweled by the pool's drain.
And since Ubuntu = Linux and Linux = Ubuntu, it is Linux's fault, right?
Or was this issue specific to Ubuntu and not other distros? (Yes, believe it or not, there ARE other distros; although it is hard to tell since so many stories and postings say "Ubuntu" in place of the word "Linux" or "Linux distribution")
Ostensibly, yes. In reality, those laptops had been making much more use of ReiserFS's best friend. I heard they even planned to run off with him.
The fix is already included in the accepted updates:
acpi-support (0.114-0intrepid1) intrepid-proposed; urgency=low
* {ac,battery,resume,start}.d/90-hdparm.sh: don't just check whether
laptop-mode is configured to control the drives, also check whether
laptop-mode itself is *enabled*. Finally closes LP: #59695.
-- Steve Langasek Mon, 05 Jan 2009 10:50:10 +0000
Just run apt-get update && apt-get install acpi-support.
The title and article summary is misleading. It shortens the life of the hard drive, not the laptop itself. Hard drives are cheap, and on most laptops as easy to swap out as the battery with screwdriver in hand.
Its not like Ubuntu is killing the motherboard or screen, its the Hard Drive.
-- 4 8 15 16 23 42
Does it bother anyone that Ubuntu, the community's duly annointed challenger to Microsoft hegemony, had an outstanding bug for fourteen months whose effect was to damage hardware? That's pretty terrible.
Trolling again on slashdot are we Mr. Gates? If you had been paying attention, you would have known about it, since it was all over the internet when it happened.
Gentlemen! You can't fight in here, this is the war room!
For something that was all over the internet, it took an awfully long time to fix.
Reading the posts prior to yours, it seems like most people are saying that Ubuntu really should have fixed this or worked around it, and that there's no excuse.
But it's much easier to jump straight to the conclusion, isn't it? Facts do tend to get in the way...
If you can't handle non-perfect hardware or firmware, then you don't make operating systems.
I don't know, quite a few companies in the past have made a pretty successful run of it.
"transanally disemboweled"
Eww! Eww! Eww!
Eeeeewwwww!!
Ewwww!
To do something right, you often have to roll up your sleeves and get busy.
Apple says 'hi'.
Obviously. But the story's still flamebait. Want a non-flamebait title? "Ubuntu Workaround for Laptop-Killing BIOS Bug Released". See the difference? Subtle but important.
well, in a way. The problem is that the drive makers optimized their power saving algorithms for Windows disk access patterns - as you would expect them to since it is 85% of the market. And they didn't provide knobs to twist for other OSes - including new, more efficient versions of Windows.
The irony is that Linux runs afoul of the hard drive power saving tuning because it is too efficient. The gaps between disk accesses are too long, and trigger a head unload while the OS is still active.
The best fix would be to twist a knob to adjust the inactivity timer - but that isn't available. So the simplest fix is to disable power saving on the disk - fine for laptops used as portable desktops. To keep drive power saving without unloading/loading the heads constantly, you have to configure "laptop mode", which uses memory to cache reads/collect writes so as to provide something like 30 minutes between disk accesses for typical word processing/browsing activities.
I've thought about writing a background process (in python or your favorite script language) that monitors iostat - and reads a raw sector every 9 seconds to keep the disk from thinking we are inactive. At the same time, we have our own Linux oriented inactivity timer, and stop reading the raw sectors when the system is truly inactive (other than our own reads).
Depends on if he wants to give them a hint, or have them form a line.
How can this be modded "insightful"? When systems break down that run other OS's, the hardware or drivers are typically blamed. That's fair territory. But when it's Linux, the double standard kicks in and it's the OS's fault? If the hardware manufacturers aren't supplying proper workarounds or fixes, or aren't even providing the source for their BIOS/Drivers/whatever to the folks who are apparently now expected to fix it, then how the hell are they supposed to make it all work? Magic wands? Insightful my ass. I'd mod this "ignorant".
Why don't you try 8.10, the newest stable release?
Oh wait, it's kdawson.
It shortens the life of your HD, not the laptop itself, you chimp.
I want to delete my account but Slashdot doesn't allow it.
"Ubuntu Workaround for Laptop-Killing BIOS Bug Released"
That title's not quite right. The bug points to a workaround that has existed since the bug was initially reported. Maybe this title: "With new update, Ubuntu make Laptop-Killing BIOS bug workaround automatic".
The funny thing is that the actul bug is an urban myth. People claim that once your hard drive reaches 300k parks it will fail. Note that at the start they were claiming the number to be 100k and now are claiming 600k due to the simple fact that a huge number of people showed up with the number being well over million on perfectly functioning drives.
The drives parked heads when not in use, sometimes, several times a minute, some of them clicked when they did so. It is a feature that reduces power use and protects the hard drive from sudden movement and impacts. It is NOT a bug.
All the claims that it will make you hard drive fail in a year are false and are made by people that have no a slightest clue of hard drive design.
I downloaded the image for a Live CD a few days ago but hadn't installed it -- lucky me -- and I was wondering, are the new Live CD downloads updated yet? Or do I have to apt-get something straight away?
I followed the instructions on Ubuntu's forums (what a pain to locate the actual instructions) (I transcribed what I did and will post them).
The actual problem was that manufactures have messed with their drives and altered the head parking timeout into a "detect if windows went to sleep" method. Basically Windows writes to the disk *all the time* until it sleeps, so the best way to minimize disk use is to park the head almost instantly after any inactivity, as that will park it asap when it sleeps. Furthermore at least 2 manufactures used the timeout control as <= 195 == "on" and >195 == "off".
Ubuntu/Linux wrote a lot less often, but plenty anyway, like every 15 seconds (doing stupid stuff like writing log files). So the head unparked every 15 seconds.
The fact that Windows "worked" led a lot of people to think Windows was doing secret messing with the drives to turn on extra modes that were not in the documentation, and that Ubuntu could not be fixed until this secret was found. However I think somebody could have figured out that it was not doing anything, there were programs (ported from Ubuntu, apparently!) for reading the disk settings under Windows.
It was also known immediatly that setting the disk timeout to 255 stopped this. Who cares if this was not the "secret Windows setting", it was certainly better than how Ubuntu was working at that time. This was known the same day the bug was first talked about! Ubuntu should have immediatly patched it, but somehow the fact that this was not "ideal" caused them to delay for 14 months! That is really bad, guys! I "fixed" mine as best I could with a program I had to run every time I opened the lid (because some stupid startup thing kept turning the timeout back on, and the only way to run my program last was to manually run it!) I eventually decided to go through the hair of actually fixing it and killing off that other thing that tried to do it.
There seemed to be a bunch of conflicting programs, all of them trying to set the disk timeout to 128 or 2. You had to get *all* of them (see next posting for what I did). This is what made it Ubuntu-specific. I sure hope this patch straightens it out so exactly ONE service, and exactly ONE file in /etc, controls the disk timeout!
Yea you can blame Windows all you want, but this was really, really, bad!
And I sure hope the update (which I just did) did not get screwed up by trying to merge with all the changes I did. Have not really checked yet. What a PITA. If they had put out a patch immediatly then they would not have to patch systems that have a hundred different solutions on them.
I'll rephrase. Would you expect that XP or Vista be installable on your laptop? AKA the newest versions.
You actually reaffirmed my statement on laptop support! But you continue to rebuff the my statement? Curious.
Ubuntu is != Linux. Ubuntu is simply a distro. And no they have not been around that long. Release 4.10 was the first release of it. That's stands for Oct 2004. Also they don't actually support people for free. The community does. As you said given sufficient demand that laptop in question would probably have been supported. Clearly demand for your variant is not sufficient.
You see by your very own logic. It should also mean that recent versions of Windows should also install without fault. I don't think they would. Vista won't that's for sure :)
-----------
Please note I did some research for you. Your particular laptop has some serious bios issues. With patches released as late as 2005.
A notable issue which sounds like it might be related to your problem is:
Version 1.70 08-01-2001
In order to support 1GHz CPU this BIOS incorporates changes to address temperature control.
Corrected a problem that, when the computer goes into S4/S5 state (S4+Hibernation, S5=Power Off) the CMOS data would get corrupted.
Corrected a problem that caused the computer to take an extended amount of time to shut down after going into Hibernation
Except that's bullshit.
1) Make any claim on slashdot that a program or piece of hardware doesn't work on windows.
2) Watch as apologists claim that it's not windows fault but bad drivers or bad application.
3) Watch as how people make similar claim about Linux and suddenly the blame is placed squarely on Linux.
There was a news story last week "Ubuntu made women quit online classes" or some similar title, where a women ordered an Ubuntu laptop, didn't even try it out and the news station she got in contact with blamed ubuntu for everything even though it worked out the box.
Hard drives have "recommended" power-saving values specified in their firmware that say after x minutes of idle time, power me down! Ubuntu used these values.
It turns out these default values were way too low (1-5 minutes), so drives would power off and on very frequently, which shortened their lives.
Like Deja Foo? The feeling that you've screwed this up before?
Comment removed based on user account deletion