Slashdot is powered by your submissions, so send in your scoop

 


Forgot your password?
Close
typodupeerror
×
Linux

Linux 3.18 Released, Lockup Bug Still Present 106

Posted by samzenpus from the check-it-out dept.
jones_supa writes As anticipated, Linus Torvalds officially released Linux 3.18. The new version is now out there, though that nasty lockup issue has still yet to be resolved. Dave Jones is nearing the end of dissecting the issue, but since it also affects Linux 3.17 and not too many people seem to get hit by the lockups, Linus Torvalds decided to go ahead and do the 3.18 release on schedule. Linus was also concerned that dragging out the 3.18 release would then complicate the Linux 3.19 merge window due to the holidays later this month. Now the Linux 3.19 kernel merge window is open for two weeks of exciting changes.
This discussion has been archived. No new comments can be posted.

Linux 3.18 Released, Lockup Bug Still Present More

Linux 3.18 Released, Lockup Bug Still Present

Comments Filter:

  • Linux on the desktop (Score:5, Funny)

    by nwf ( 25607 ) on Monday December 08, 2014 @04:28PM (#48550483)

    This is just the sort of bug to get people to adopt Linux on the desktop, since it will be more similar to what they expect from Windows.

    • This reminds me of the plotline from Userfriendly where one of the techs develops an OS called "The OS That Doesn't Suck." He eventually gives up this pursuit when it, too, begins to suck.

      • Re: (Score:1)

        by Anonymous Coward

        That would be Absurd Notions [absurdnotions.org], not User Friendly.

        • Ack! Sorry about that! I knew it was an old old webcomic, and that it happened around the time when there were just millions of new UNIX-style operating systems with everyone claiming that theirs was good for a different reason.

    • wait, Windows locks up randomly now?

      • Usually only when it involves an nvidia or AMD GPU driver :)

        • Graphics drivers haven't caused the system to lock up since Windows XP and the new driver model. Now if your graphics driver chokes, you get a second or two of black screen, then everything comes back up normally with a balloon in the system tray telling you it crashed.

          If you mean complete lockups or bluescreens, I've had two of those over five years of running Windows 7, and they were both when I was overclocking (none since).

    • This is just the sort of bug to get people to adopt Linux on the desktop, since it will be more similar to what they expect from Windows.

      Not me! I refuse to use software as immature as version 3 of Linux. Mac is on OS version 10, Windows is about to release version 10, and by golly, I'm not wasting a second of my time on Linux until it catches up!

    • Re: (Score:1)

      by kmoser ( 1469707 )
      So you're saying 2015 will surely be the year of the Linux BSOD?

  • Don't use Bleeding Edge Kernels (Score:5, Insightful)

    by Zombie Ryushu ( 803103 ) on Monday December 08, 2014 @05:06PM (#48550805)

    Don't use Bleeding Edge Kernels on Stable Production systems. I still use Kernels for 3.10, and 3.12 with security updates. I can't have Intermittent unexplained lockups.

    • Re: (Score:1)

      by Anonymous Coward

      Don't use Random capitals in your Sentences. I don't Capitalize random words in My sentences. I don't want To look like I am Schizophrenic.

    • I have used 4 versions of 3.17 of void linux till now as my primary web and office desktop, not one lockup.

      Given that void doesn't feature it, it's obviously a systemd issue. :D

    • Last I heard (admittedly it was on a Slashdot article so it could be wrong) the bug has been present for many years, since the 2.x kernels.

  • Dissecting != Bisecting (Score:1)

    by Anonymous Coward

    Bisecting is a technical term with a specific meaning. Essentially, he is using a binary search through git history to identify when the bug was introduced. Dissecting does not convey this. But I guess it is too much to ask to have the submitter both read and understand TFA.

    • Bisecting is a technical term with a specific meaning. Essentially, he is using a binary search through git history to identify when the bug was introduced. Dissecting does not convey this. But I guess it is too much to ask to have the submitter both read and understand TFA.

      Submitter here. In this case samzenpus has to take the blame, because in my original submission [slashdot.org] the word is "bisecting". :)

      • Yeah, the editors of slashdot are not fluent in computer science lingo that is common within open source where one work with many different version and need to make sure regression not happen e.g. the linux kernel.

        Also if editor had googled the word this statement is visible in the Wikipedia page about bisecting:

        "Not to be confused with Dissection."

        http://en.wikipedia.org/wiki/B... [wikipedia.org]

        Dissection is mostly known as a biological term about using an scalpel to examine plants, animals or humans.

  • I don 't know whether to feel pissed or special (or both), but I've been experiencing this lockup on my lowly little Arch box. (Reverting to a previous kernel always clears it up.) I couldn't find anything in the Arch forums about it, so I appreciate being kept abreast of it here! :)

Slashdot Top Deals

Top Ten Things Overheard At The ANSI C Draft Committee Meetings: (10) Sorry, but that's too useful.

Close