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.
present on?
I'm curious to know if it is merely glitchy hardware, sloppy coding, or a sign of something more malicious.
No lockup yet on my affected system... crap... nvm... just locked up
Kernel panic - not syncing: Watchdog detected hard LOCKUP on cpu 3
CPU: 3 PID: 17176 Comm: trinity-c95 Not tainted 3.17.0+ #87
0000000000000000 00000000f3a61725 ffff880244606bf0 ffffffff9583e9fa
ffffffff95c67918 ffff880244606c78 ffffffff9583bcc0 0000000000000010
ffff880244606c88 ffff880244606c20 00000000f3a61725 0000000000000000
Call Trace:
[] dump_stack+0x4e/0x7a
[] panic+0xd4/0x207
[] watchdog_overflow_callback+0x118/0x120
[] __perf_event_overflow+0xae/0x340
[] ? perf_event_task_disable+0xa0/0xa0
[] ? x86_perf_event_set_period+0xbf/0x150
[] perf_event_overflow+0x14/0x20
[] intel_pmu_handle_irq+0x206/0x410
[] perf_event_nmi_handler+0x2b/0x50
[] nmi_handle+0xd2/0x390
[] ? nmi_handle+0x5/0x390
[] ? _raw_spin_lock_irqsave+0x80/0x90
[] default_do_nmi+0x72/0x1c0
[] do_nmi+0xb8/0x100
[] end_repeat_nmi+0x1e/0x2e
[] ? _raw_spin_lock_irqsave+0x80/0x90
[] ? _raw_spin_lock_irqsave+0x80/0x90
[] ? _raw_spin_lock_irqsave+0x80/0x90
> [] lock_hrtimer_base.isra.18+0x25/0x50
[] hrtimer_try_to_cancel+0x33/0x1f0
[] hrtimer_cancel+0x1a/0x30
[] tick_nohz_restart+0x17/0x90
[] __tick_nohz_full_check+0xc3/0x100
[] nohz_full_kick_work_func+0xe/0x10
[] irq_work_run_list+0x44/0x70
[] irq_work_run+0x2a/0x50
[] update_process_times+0x5b/0x70
[] tick_sched_handle.isra.20+0x25/0x60
[] tick_sched_timer+0x41/0x60
[] __run_hrtimer+0x81/0x480
[] ? tick_sched_do_timer+0xb0/0xb0
[] hrtimer_interrupt+0x117/0x270
[] local_apic_timer_interrupt+0x37/0x60
[] smp_apic_timer_interrupt+0x3f/0x50
[] apic_timer_interrupt+0x6f/0x80
[] ? lock_release_holdtime.part.28+0x9a/0x160
[] ? rcu_is_watching+0x27/0x60
[] kill_pid_info+0xf5/0x130
[] ? kill_pid_info+0x5/0x130
[] SYSC_kill+0x103/0x330
[] ? SYSC_kill+0xac/0x330
[] ? context_tracking_user_exit+0x52/0x1a0
[] ? trace_hardirqs_on_caller+0x16d/0x210
[] ? trace_hardirqs_on+0xd/0x10
[] ? syscall_trace_enter+0x14d/0x330
[] SyS_kill+0xe/0x10
[] tracesys+0xdd/0xe2
Kernel Offset: 0x14000000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff)
Yes!
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.
3.19, so wow.
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
So Linux has a bug, big deal. It'l be fixed soon. Unlike Winblows which sucks so badly, but idiots keep buying into this crap. Because, windows is dumbed down for idiots.
This sort of disingenuous comments, this snark coming from a position of weakness, isn't even a little bit cute and is only funny because of how dorky it is.
It's like an American pretending not to understand prices in USD and instead asking shopkeepers to convert to bitcoin first.
"Microsoft Windows? Never heard of it."
lots of laughs trollfriend.
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.
This is actually a FEATURE, not a BUG. It's there so stupid fucken n00bs don't break their CPUs!
Shut up and eat yer pinecone!
Android, and Chromebooks.
http://validator.w3.org/check?uri=http%3A%2F%2Fwww.slashdot.org Errors found while checking this document as HTML5!
And IBM continues to dominate the mainframe field.
Windows hasn't kicked any asses, they just piss off users into ditching it for Linux.
Wow, APK managed an entire post without bolding or all-caps... Colour me surprised.
Il n'y a pas de Planet B.
Android
Did you read his post? He specifically called out Android:
The only thing Linux has going for it these days is Android
and Chromebooks.
No, Chromebooks have done very little for Linux on the desktop. In fact the OS is so limited that no desktop computers even run it, just lowend laptops. Chromebooks cant do anything you cant do on Windows or OSX and are far more limited in what applications they can run, they are a race to the bottom competing on price alone.
whoa, that was a joke dude. Why are you getting so defensive? Did I hit a nerve?
Millions of people with access to the Linux source code have failed to locate the bug. That sucks!
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.
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.
People like you are a pox on open source software today.
Just because it doesn't affect you and the small number of Linux systems that you use, that does not mean that it doesn't cause problems for other people. It clearly does, otherwise there wouldn't be investigation into why it's happening.
Your attitude is fucking idiotic, and very harmful. It's just like what we see out of the Mozilla community. Many Firefox users describe how Firefox uses a huge amount of CPU and/or memory on their systems, but dickfaces like you just say, "It doesn't happen on my system, so it can't possibly happen on yours!" And what have we seen these Firefox users do, when shown such complete disrespect? They ditched Firefox and move to Chrome.
Your shitty attitude is now spreading throughout the Linux ecosystem. It ruined GNOME. It's in the process of ruining Debian, thanks to all of that systemd bullshit. Now it's even affecting the kernel itself.
You're part of the reason why so many people are fed up with Linux and its open source ecosystem, and are moving to FreeBSD. The FreeBSD community takes problems like this seriously. They don't have your piss-poor attitude when it comes to real problems like this one.
You are nut. FreeBSD is not a business so never going out of business.
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 :)
What?! Holidays being used as an accuse is unacceptable!
Must have kernel releases on a consistent schedule. No breaks for these devs. Slackers...
At least that's what my bosses want.
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.
they just piss off users into ditching it for Linux.
+5 funny.
Maybe because it's not true? Don't be an asshole.
There is some wisdom to that comment. Instead of trying to build enterprise-level systems with lack of developers, the open source community might wind up with more stable system by sticking with something more simple. Linux Mint grabbed GNOME2 which became MATE, and it has been hugely successful. Simple, fast, stable.
I have to admit that I got a bit nervous. I guess it's time for me to grab a beer from the local supermarket and relax a bit. :)
set your PS1, you filthy casual.
LWN: https://lwn.net/Articles/62497...
kernelnewbies: http://kernelnewbies.org/Linux...
omgubuntu: http://www.omgubuntu.co.uk/201...
Millions of companies do, and uniformly they report significant ongoing cost savings after switching from Linux. Linux is only "free" if your time has no value and as this "ongoing lockup bug" demonstrates, when you use a hobbyist level OS, you get hobbyist level programmers making hobbyist level mistakes.
Good point. Linux is a lot like the mainframe. It still exists and is used in some places to limited success (and with massive and ongoing cost), but its marketshare is stagnant and the industry is finally waking up to the realization that it has made a bad bet. It turns out closed source software is actually a lot better than open source software and that all the claims made by the open source people were laughably wrong. When you use software written by amateurs and hobbyists, it turns out you end up with software written by amateurs and hobbyists. Surprise!
Totally true. Linux seems like more of a research project than a well engineered system.
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! :)
Why don't we see articles titled "Windows released, bug still present"?
e.g.: Windows has allegedly supported Unicode since NT 4.0 yet Windows Search still cannot find text in big endian UCS2 files and can only find ASCII text in UTF8 files.
Anyone who talks about "wins" in this context is a moron. But someone thinks we need salespeople, too, I guess...