Slashdot Mirror
Linux 3.18 Released, Lockup Bug Still Present
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.
systemd. So the latter two.
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.
I don't know, but it works for me.
My understanding is that they are still trying to narrow it down, but in the process have actually found multiple bugs.
It is official; Netcraft now confirms: *BSD is dying
One more crippling bombshell hit the already beleaguered *BSD community when IDC confirmed that *BSD market share has dropped yet again, now down to less than a fraction of 1 percent of all servers. Coming close on the heels of a recent Netcraft survey which plainly states that *BSD has lost more market share, this news serves to reinforce what we've known all along. *BSD is collapsing in complete disarray, as fittingly exemplified by failing dead last in the recent Sys Admin comprehensive networking test.
You don't need to be a Kreskin to predict *BSD's future. The hand writing is on the wall: *BSD faces a bleak future. In fact there won't be any future at all for *BSD because *BSD is dying. Things are looking very bad for *BSD. As many of us are already aware, *BSD continues to lose market share. Red ink flows like a river of blood.
FreeBSD is the most endangered of them all, having lost 93% of its core developers. The sudden and unpleasant departures of long time FreeBSD developers Jordan Hubbard and Mike Smith only serve to underscore the point more clearly. There can no longer be any doubt: FreeBSD is dying.
Let's keep to the facts and look at the numbers.
OpenBSD leader Theo states that there are 7000 users of OpenBSD. How many users of NetBSD are there? Let's see. The number of OpenBSD versus NetBSD posts on Usenet is roughly in ratio of 5 to 1. Therefore there are about 7000/5 = 1400 NetBSD users. BSD/OS posts on Usenet are about half of the volume of NetBSD posts. Therefore there are about 700 users of BSD/OS. A recent article put FreeBSD at about 80 percent of the *BSD market. Therefore there are (7000+1400+700)*4 = 36400 FreeBSD users. This is consistent with the number of FreeBSD Usenet posts.
Due to the troubles of Walnut Creek, abysmal sales and so on, FreeBSD went out of business and was taken over by BSDI who sell another troubled OS. Now BSDI is also dead, its corpse turned over to yet another charnel house.
All major surveys show that *BSD has steadily declined in market share. *BSD is very sick and its long term survival prospects are very dim. If *BSD is to survive at all it will be among OS dilettante dabblers. *BSD continues to decay. Nothing short of a cockeyed miracle could save *BSD from its fate at this point in time. For all practical purposes, *BSD is dead.
Fact: *BSD is dying
Captcha: obsolete
I've had either this or something similar appear on my AMD box at home (FX-8120, 16GB RAM, 990FX Chipset).
I'm starting to think GNU is the problem with "GNU/Linux" these days.
lol - the 'many eyes' that can examine the source code are only of use when they are actually looking at it.
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.
Well, Linux Users will probably have to learn a lesson from the Windows User community: When the current version sucks, just use an earlier version and ride it out 'til a new and hopefully better one arrives.
We used to have a Bill of Rights. Now, with the rights gone, all we have left is the bill.
Bug happens on some special hw when one runs trinity (a system call fuzzer) long enough. So what? I have been running 3.18 from the start of its merge window and have not seen any problems in it. Instead of sensational click bait article from phoronix, I would rather see a link to kernel newbies or lwn with description what has been changed in this version and what is new.
And IBM continues to dominate the mainframe field.
Wow, APK managed an entire post without bolding or all-caps... Colour me surprised.
Il n'y a pas de Planet B.
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.
Please, never user a Mac.
On desktop, Linux for work, Windows for entertainment.
On servers use Linux, and let the Mac for those idiots that think they think different for using a overpriced closed and unstable system (OSX crashes more than Windows, since due to the way OSX is coded it is trivial to write a program that can block the whole OS and require a hard reboot, eg: by forcing a system deadlock, which lots of sloppy coded Mac apps suffer from, something that you cannot do in Windows, the only way I've seen modern Windows crashing was due to device driver bugs. )
Hmmm, that's interesting... pretty sure the original bug filer was using an AMD quad core since several mails had been about core 3 / core 4 being idle at the time of crash. I may be wrong though, I only read through it at the time it was posted on /.
Makes you wonder if it is a AMD multiple of 4 core bug somehow though, and maybe fixable through microcode patching.
To err is human; effective mayhem requires the root password!
No problem, he's not saying there are bugs in the Linux kernel. He's saying there were bugs in the Linux kernel.
Both you and parent have a point imo, but you seem to be overreacting.
Yes, a bug that affects almost nobody IS less of a problem. It was present in 3.17 and nobody was hit hard enough to even report it.
This is not comparable to projects like GNOME making major controversial changes willingly and repeatedly. This is some odd bug that'll get bisected and fixed soon, that will never affect you, and that doesn't derve all that much press.
Why all the Linux zealots modding good posts down, mod parent up! Great comment. I agree Android is pretty much the only good Linux software out there these days.
Yes, let's use windows on the server, ha ha :)
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!
Beware of bugs in the above code; I have only proved it correct, not tried it.
Guys, do you ever read LKML where this stuff happens? Your GP comment said that they have found multiple bugs. No, they haven't. They are dealing with the very same bug where the watchdog detects a soft lockup. There is no debugger attached at this point, they are just doing bisecting (another powerful tool of course) to find what was the specific patch that introduced the bug. Browse through the LKML archive and search for the subject "frequent lockups in 3.18rc4".
(Apple marketing victim)
LWN: https://lwn.net/Articles/62497...
kernelnewbies: http://kernelnewbies.org/Linux...
omgubuntu: http://www.omgubuntu.co.uk/201...
Obviously spoken by someone who never owned a Mac. Until the CPU fan gave out this summer, I had a Black MacBook (2006) that ran fine for the last eight years. Alas, with a 32-bit processor that's no longer supported, I didn't take it to the Apple Store to get fix. I had no problems switching over to Windows 8.1, as my data was in cross-platform formats. I'm looking forward to a new Mac next year.
I can reproduce it in half an hour on my dell alienware laptop by running my chess program. So no special hardware, no special software.
www.vanheusden.com - home of Multitail, HTTPing, CoffeeSaint, EntropyBroker, rsstail, bsod, listener, nagcon, nagi
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! :)