> I installed the kernel with the fix from zesty-proposed
> (4.10.0-22-generic #24-Ubuntu), but after ~4 hours of uptime on that
> kernel, I hit what felt like the same system lockup again. (Or perhaps
> a new version of this lockup that the patch introduces / leaves
> unfixed?)
>
> Here's the ke
I apprciate that this bug has a significant impact for many. However we
have a QA process to test kernels before they get pushed out to
everyone, and it is always risky to skip this testing which is why we
rarely do it. In the case of the fix for this bug the changes required
are fairly substantial
> I'm wondering how did it reach zesty-proposed earlier that artful-
> proposed. On Artful I still do not see an update.
In artful the kernels are just copied forward from zesty once they reach
-updates. Soon artful will switch to 4.11, at which point its kernels
will start going into proposed. Yo
2017.05.21 22:53, JOSHUA CRUNK rašė:
> Have to reset computer via power button.
You can use REISUB sequence to reboot more safely.
https://en.wikipedia.org/wiki/Magic_SysRq_key
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
Tim Passingham, thanks for telling us your story. Ordinary folk are not
very well represented here, in the bug tracker.
Does anybody know any news websites that might be interested in covering
this issue? I emailed the guy who writes for OMG! Ubuntu!, but he didn't
respond so far. It might be a
just hung again, only reisub worked.
On Wed, 17 May 2017, 13:41 Jonas Slivka, <1674...@bugs.launchpad.net>
wrote:
> I'm still experiencing freezes with Seth Forshee's kernel (5-6 times a
> day on relatively heavy load)...
>
> ➜ ~ uname -a
> Linux dell 4.10.0-20-generic #22+lp1674838v201705030839
> I CAN reproduce this particular error, which clearly is NOT the bug we
> are dealing with on this thread, following the same steps. Actually you
> can try this by clicking on "Share this page" icon on firefox and then
> the + icon to install more social actions.
If you can reproduce the error
Murat, are you sure it's the same bug? I experienced a random freeze on
4.8.0-51-generic, but there was nothing in syslog and symptoms were
quite different. What's in your syslog?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
> Hmm, a June 5 release date for this fix seems to be wait too late
> for the severity of this system freeze bug.
This is our normal SRU cycle. Out-of-cycle updates are for the most part
reserved for critical security issues.
> Not sure what regressions using 4.10.0-13 would entailed compared to
On Wed, May 10, 2017 at 02:19:26PM -, Vidar Braut Haarr wrote:
> Will it be included in the next artful kernel, or only zesty? I ask
> because the email subject says "[PATCH 0/4][Zesty SRU]".
>
> And when will it be, roughly? 2 weeks? 3 months? Tomorrow?
Currently artful is using the same ker
Was on multiple i7 2600 with 2 gig swap. Took longer to occur, but still
occurred.
On Apr 18, 2017 7:31 AM, "JockeTF" wrote:
> I'm on a laptop with Intel Ivy Bridge.
>
> I had no swap enabled. I haven't experienced this issue since I created
> a small 1GB swap file. It may be too soon to tell f
11 matches
Mail list logo