uname -a
Linux merlin 4.10.0-28-generic #32-Ubuntu SMP Fri Jun 30 05:32:18 UTC 2017
x86_64 x86_64 x86_64 GNU/Linux
Same symptoms as reported about. Firefox freezes and causes the system
to freeze.
Cannot get Firefox to work. I have had to install Chrome in order to
access web.
Have sent
@Robbie
It's not the same, please file a new bug.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1674838
Title:
kernel BUG at /build/linux-
I believe I may still be encountering this bug, this seems to happen any
time the system is under significant load. Attached is my kern.log from
right after the NMI watchdog soft lockups start. Please let me know if I
should submit additional logs from the next time this happens, or submit
a new
** Changed in: linux-hwe-edge (Ubuntu Zesty)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1674838
Title:
kernel BUG at /build/linux-
Seth has fixed my installation problem, so all my 4 17.04 4.10.0.22
systems are now being used. I'll report if I get any further crashes
(but I don't expect any).
See #1696132 if you are interested in what the problem was.
--
You received this bug notification because you are a member of
I have 4 17.04 systems. The one that had this bug is the only one which
has an installation problem with 4.10.0-22. Maybe a coincidence, maybe
not?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
@tim-8aw3u04umo no installation issue here. I used: 'sudo apt update &&
sudo apt upgrade'.
uname -r reports "4.10.0-22-generic"
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1674838
** Also affects: ubuntu-power-systems
Importance: Undecided
Status: New
** Changed in: ubuntu-power-systems
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
This bug was fixed in the package linux-hwe-edge - 4.10.0-22.24~16.04.1
---
linux-hwe-edge (4.10.0-22.24~16.04.1) xenial; urgency=low
* linux-hwe-edge: 4.10.0-22.24~16.04.1 -proposed tracker (LP:
#1691149)
* linux: 4.10.0-22.24 -proposed tracker (LP: #1691146)
* Fix NVLINK2
This bug was fixed in the package linux-hwe-edge - 4.10.0-22.24~16.04.1
---
linux-hwe-edge (4.10.0-22.24~16.04.1) xenial; urgency=low
* linux-hwe-edge: 4.10.0-22.24~16.04.1 -proposed tracker (LP:
#1691149)
* linux: 4.10.0-22.24 -proposed tracker (LP: #1691146)
* Fix NVLINK2
I have now reported the installation error using the automated report
system - #1696132
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1674838
Title:
kernel BUG at /build/linux-
There's a problem with this new version - it won't install on the one
system I have that is affected by the bug. The installation error is:
dpkg: error processing archive
/var/cache/apt/archives/linux-headers-4.10.0-22_4.10.0-22.24_all.deb (--unpack):
unable to open
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1674838
Title:
kernel BUG at /build/linux-
This bug was fixed in the package linux - 4.10.0-22.24
---
linux (4.10.0-22.24) zesty; urgency=low
* linux: 4.10.0-22.24 -proposed tracker (LP: #1691146)
* Fix NVLINK2 TCE route (LP: #1690155)
- powerpc/powernv: Fix TCE kill on NVLink2
* CVE-2017-0605
- tracing: Use
Is there a delay in getting 4.10.0-22 to stable release? I had
previously understood it was expected yesterday (June 5th).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1674838
Title:
When it should be available for 16.04?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1674838
Title:
kernel BUG at /build/linux-
7LGLH_/linux-4.10.0/include/linux/swapops.h:129
This bug was fixed in the package linux - 4.10.0-22.24
---
linux (4.10.0-22.24) zesty; urgency=low
* linux: 4.10.0-22.24 -proposed tracker (LP: #1691146)
* Fix NVLINK2 TCE route (LP: #1690155)
- powerpc/powernv: Fix TCE kill on NVLink2
* CVE-2017-0605
- tracing: Use
Folks, just enable the Proposed channel for the next four days (until
this is released into stable on the 5th). You can disable it again
afterwards. This is what I've been doing, and haven't run into this
issue again (or any other problems with Proposed).
--
You received this bug notification
Got bitten by this again today. Ubuntu 17.04, 4.10.0-21-generic
#23-Ubuntu SMP Fri Apr 28 16:14:22 UTC 2017 x86_64 x86_64 x86_64
GNU/Linux. Firefox again.
I think this is issue is critical enough to expedite the release of
fixed kernel, posthaste.
--
You received this bug notification because
I was also experiencing this issue with the official 4.10.0-21-generic
kernel; I ran the ~lp1674838 kernel for several days, and have been
running the -22-generic test kernel for a couple without problems.
--
You received this bug notification because you are a member of Kernel
Packages, which
I just experienced this bug on 4.10.0-21-generic #23-Ubuntu.
My Firefox stopped responding, and when trying to kill Firefox the
Firefox process became un-killable used 25% CPU time and N/A memory.
CPU: 3 PID: 2558 Comm: firefox Tainted: G OE
4.10.0-21-generic #23-Ubuntu
This is the
I've seen this bug in the scenario described in comment #218. In my
case, there was always a frozen Firefox around, but all the other
processes running in the system where also reacting slowly or frozen.
--
You received this bug notification because you are a member of Kernel
Packages, which is
It's strange that I hit this at least once every two days, but server has been
working for weeks now.
Is there already a description of what common scenarios are when this bug is
hit, i.e., is it already reproducible?
--
You received this bug notification because you are a member of Kernel
I'm getting a freeze with the same symptoms described in this bug
report, but with this message
May 31 02:37:27 walter kernel: [410240.819651] NMI watchdog:
BUG: soft lockup - CPU#14 stuck for 22s! [JS Helper:23856]
I'm running 4.10.0-21-generic.
I will duplicate my bug report (bug #1677491)
Been affecting me as well -- will try the alternate kernels.
Kernel that's crashing:
axyjo@frost:~$ uname -a
Linux frost 4.10.0-21-generic #23-Ubuntu SMP Fri Apr 28 16:14:22 UTC 2017
x86_64 x86_64 x86_64 GNU/Linux
--
You received this bug notification because you are a member of Kernel
I tried to install 4.10.0-22 on the one system we have that was
regularly crashing, but it gets installation errors (being unable to
access files in /usr/src/linux-headers-4.10.0-22), so I cannot verify if
it would fix the run-time crashes. I was unable to work round this in a
short enough time
As much as I want the -22 to fix all problems, it does not.
However, my crashes does currently not leave a trace in the logs.
Sticking to -13 keeps my workhorse running riddled of any crash or
freeze problems.
The simplest way to describe what is going on is that all I/O gets stuck
and that my
@Tim - To be fair, Ubuntu LTS without the hwe-edge is perfectly stable.
However, it is true that all this process was a bit disappointing, and I
ended up moving to debian sid, which seems to be a quite stable
experience so far.
--
You received this bug notification because you are a member of
for those of you like me who were reluctant to add testing into the
sources list (because of course it could break something else) and
couldn't find the deb packages because they didn't provide any direct
link, here is a little script I had to write that downloads and installs
the kernel
I've been running "-proposed" for quite a while now without the kernel
oops, hence changed the tag to "verification-done-zesty".
** Tags removed: verification-needed-zesty
** Tags added: verification-done-zesty
--
You received this bug notification because you are a member of Kernel
Packages,
> If verification is not done by 5 working days from today, this fix
will be dropped from the source code, and this bug will be closed.
never go full retard, dude
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag
(Thanks @Rocko - I'd filed
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1693357 but I've
now marked that as a duplicate of the bug you mentioned.)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
@dholbert: your lockup looks like
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1680904 (and the
upstream bug is https://bugs.freedesktop.org/show_bug.cgi?id=100516).
It's a bug in the Intel graphics drivers that unfortunately is present
in both kernels 4.10 and 4.11, but should be fixed in
> 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
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
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 kern.log from
@ddstreet, sforshee: Thanks for the replies. Given that this also
affects LTS installations that use the HWE stack, shouldn't this have as
high a priority as critical security issues? I'd consider this a
critical usability issue; there are tons of people running LTS,
particularly on servers, for
I now have 23 hours of uptime thanks to 4.10.0-22 #24 from zesty
proposed. That's a zesty record for me :)
thanks.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1674838
Title:
kernel
This may not be a security issue, but it certainly is critical to normal
users who don't have access to information here, let alone temporary
patches or proposed changes.
Maybe ubuntu only want techies using their systems, and would prefer
normal users went elsewhere? I'll certainly have to
> 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.
I'm wondering how did it reach zesty-proposed earlier that artful-
proposed. On Artful I still do not see an update.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1674838
Title:
kernel
> Question: Given that this is quite a critical bug, is there any reason this
> hasn't been put into the main archives sooner?
I'm not the right person to ask that, but you can see Seth's comment 139
above.
"This is our normal SRU cycle. Out-of-cycle updates are for the most part
reserved for
@ddstreet: Installed from zesty-proposed, testing it how. Question:
Given that this is quite a critical bug, is there any reason this hasn't
been put into the main archives sooner? It is quite a bad user
experience, especially for novice users that won't find this bug nor
know how to do a
Just had something similar to Patrick's in #100 above, but this time on
9 different GPFs on kernel 4.10.0-21. The locations are all quite
different, but I wonder if there is something common there:
May 23 14:34:02 thornback kernel: [ 1371.525043] general protection fault:
[#1] SMP
May 23
Not that I can recommend it to anyone else, but I did update to
4.10.0-22.24 on xenial 16.04.2 by pointing the to the zesty 17.04
proposed repo. Hasn't crashed in the 5 minutes I've been running it.
Caveat emptor.
--
You received this bug notification because you are a member of Kernel
Packages,
> It seems it's not yet in the xenial-proposed repo yet, but probably will be
> there
> soon-ish I guess?
Yes, there was a technical issue with the build, but it seems minor and so
looks like it should be ready soon-ish. It will be listed here when it's in
the -proposed repository:
I followed the instructions at https://wiki.ubuntu.com/Testing/EnableProposed .
I did the "Selective upgrading from -proposed" section before "enabling
proposed", then installed 4.10.0-22.24 via synaptic.
This went smoothly for me. Thanks @ddstreet for the link.
@kwang-m-yi I can't speak for
@ddstreet: It seems it's not yet in the xenial-proposed repo yet, but
probably will be there soon-ish I guess?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1674838
Title:
kernel BUG
Thanks. Installed and being used on a system that didn't display the
fault, to check before inflicting on my other half.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1674838
Title:
Just as an FYI to everyone still commenting in this bug, this is fixed in
kernel 4.10.0-22.24:
https://launchpad.net/ubuntu/+source/linux/4.10.0-22.24
which is in the -proposed repository:
https://wiki.ubuntu.com/Testing/EnableProposed
and as Seth said in comments above, is scheduled for
Very strange bug - occurred several times with the 4.10.0-20 and
4.10.0-21 kernels on the Intel Core i5-2400, but did not appear with the
same kernels on the Intel Core 2 Duo E6700.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
This bug affects my laptop running 17.04, which is an upgrade from an
earlier installation. I appear to have no other kernels available in the
repository that do not have this bug, and there's no way I'm installing
an untrusted kernel.
Considering how long this bug has been open, this is getting
@munbi - thanks. That doesn't seem to work for me on a different
system, but pressing and holding Alt, PrintScreen and r, releasing all,
then all of Alt, PrintScreen and e, the the same for b, etc, seemed to
work. I didn't see the GUI collapse, but it did reboot. I guess the
rest happened
For anyone else wondering, here's what seemed to work (don't really know
if it is the correct approach):
1. Download select .deb files from the page mentioned in comment #180:
http://people.canonical.com/~sforshee/lp1674838/
Specifically:
For those of us that just want to use Ubuntu without having to care what a
"kernel" is, could someone kindly explain how to install the fix from comment
#108? Just download all the .deb files from that web-page and install them
with the software updater or software center?
Thank you.
--
You
@Tim, this is what works for me on a Dell Latitude E6540:
1. Left hand: Press and hold “Fn” key (between Ctrl and the Windows key)
2. Right hand: Press and hold “Alt” + “SysRq” keys (Stamp)
3. Left hand: Release “Fn” key
4. Left hand: Press and release “r” key. (Screenshot dialogs may start
Sorry - I now understand that I have to press all 3 keys at the same
time.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1674838
Title:
kernel BUG at /build/linux-
I don't understand that article. It says press Alt+SysReq and another
key, and that SysReq is the PrintScreen key.
If I press Alt + PrintScreen it asks to print the screen - I have no
chance to enter another key. Can someone clarify this? I'm sure it's
obvious.
--
You received this bug
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 Kernel
Packages, which is subscribed to linux in
> tkb608 (tkb608) wrote on 2017-05-19:
> @kwang-m-yi Good point, I had forgotten that new installs of 16.04.2 would
> automatically get HWE and therefore this bug.
Although that's true, @kwang-m-yi talked about hwe-edge; and the "edge" variant
is not installed by default on 16.04.2.
As
Another vote for this needs releasing now!
Before I tracked down the cause and found this bug report I'd spent
hours trying to diagnose the reason for my machines instability. I'd re-
installed Ubuntu over the previous version, when that didn't work got a
new hard disk and did a totally new clean
I find it absolutely astonishing that a bug that is easy to trigger, can
cause data loss, and requires a hard reboot is treated with a lower
priority than security bugs.
Surely Ubuntu 17.04 should be flagged "not suitable for production
machines" until this issue is fixed?
--
You received this
And even if the patched kernel is installed by those few users that
manage to find this bug report, or one of its many duplicates, it gets
replaced by 4.10.0.21 which reinstates the bug. Only installing 4.11
keeps the problem away.
--
You received this bug notification because you are a member
This issue is not solved until fixed kernel appears in stable
repositories. This is exactly why new people are arriving and will do so
for a few more weeks.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
This should be marked "SOLVED!".
It appears that newcomers are arriving at this ticket to report same old
problem, without realizing it has been fixed in a replacement kernel
offered by Seth Forshee. The problem is now understood and there is no
need to guess about installing alternative kernels
Mint Cinnamon 18.1 user here. Just mentioning that so as to make it
easier for other people doing a Google search to find this thread, since
it was pretty hard for me to find. Same problem as everyone else,
swapops.h:129!. For me particularly, khugepaged goes to Uninterruptible
Sleep (D) state
Hi.
The relevant line in the kern.log of the affected server
(4.10.0-21-generic) was:
kernel BUG at /build/linux-
lz1RHE/linux-4.10.0/include/linux/swapops.h:129!
I switched to the 4.11 mainline kernel:
Linux 4.11.2-041102-generic #201705201036 SMP Sat May 20 14:38:21 UTC 2017
x86_64 x86_64
So, how will we know when this patch drops into a distribution kernel?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1674838
Title:
kernel BUG at /build/linux-
I have experienced freeze with Linux vinco 4.10.0-21-generic
#23~16.04.1-Ubuntu SMP Tue May 2 12:57:17 UTC 2017 x86_64 x86_64 x86_64
GNU/Linux while browsing with Firefox.
In addition to "invalid opcode: [#1] SMP", there are:
"NMI watchdog: BUG: soft lockup - CPU#6 stuck for 23s!
hm, my computer hanged up even with the kernel 21
Linux chrome 4.10.0-21-generic #23-Ubuntu SMP Fri Apr 28 16:14:22 UTC 2017
x86_64 x86_64 x86_64 GNU/Linux
The symptoms were very similar - firefox in the foreground and computer
locked up but there where no usual swapon oops record in the syslog
@kwang-m-yi Good point, I had forgotten that new installs of 16.04.2
would automatically get HWE and therefore this bug.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1674838
Title:
Thanks to all for the advice. I'll trying saving the last used kernel
using grub.
Is there like to be any problem running a 4.8 version kernel with 17.04?
It seems OK so far.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
I'm also grateful for the free service provided by Ubuntu here, although
I must object ! The release being LTS or not is irrelevant to this
problem as we are obviously in the support lifecycle of the zesty
release. The release being non-LTS is not an indicator of instability,
or at least it should
@Tim - What Patrick said... Or prevent the kernel package from being updated
until the fix is included:
https://askubuntu.com/questions/18654/how-to-prevent-updating-of-a-specific-package
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Just to add, even 16.04 LTS is affected by this bug, as if you install
linux-hwe-edge, you install the same bugged kernel. For me, the next
time I wipe my machine, it won't be ubuntu, simply because this type of
bug is unacceptable for a daily driver.
--
You received this bug notification
@Tim
Add/set in /etc/default/grub:
GRUB_DEFAULT=saved
GRUB_SAVEDEFAULT=true
and run "sudo update-grub" to have GRUB remember the kernel you booted
last time.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Thanks for the responses to my comments. I appreciate that this is not
the LTS version, and I didn't have to pay to get it.
I have two approaches to updating. Either stay fully up to date on the
most recent versions and risk having issues with ever changing versions,
or never update at all. I
One more happy week of success with
http://kernel.ubuntu.com/~jsalisbury/lp1674838.
I understand Tim Passingham's frustration, but can I turn the question a
different way? I want to know "why didn't this problem affect all
Ubuntu users? Why just us?" A particular motherboard is to blame?
Also,
I'm supportive of the idea that this is a show song bug. But you know,
free software, and not a LTS version. So maybe take it down a notch.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
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 tale of ordinary folk - just users.
We have 4 systems running 17.04 - 3 xubuntu and 1 ubuntu. 3 are fine.
Now one regularly locks up and has to be manually rebooted. The other 3
are fine. I initially reported against #1687267, (now marked as a
duplicate of this) including a crash log.
The
@selinger Yeah, hard to kind old kernels.
https://launchpad.net/~canonical-kernel-
team/+archive/ubuntu/ppa/+build/12106252
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1674838
Title:
> critical [...] bug
Totally agree.
> security bug
It's a critical bug, but not a security issue.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1674838
Title:
kernel BUG at
I believe that a kernel that crashes every 1-4 hours is a critical
security bug, so an update should be released immediately, rather than
some time in June.
I was unable to install linux-image-4.10.0-13, because it no longer
seems to be in the repository.
I am still experiencing this bug with
My apologies, I think I was confused before. I saw another hang with
similar symptoms and I think confirmation bias made me assume I'm seeing
this bug again without double checking everything carefully. Sorry
about that!
Now I verified I'm running the right kernel, I'll report if I see the
@Ehsan,
Hi. You are running the original test kernel for this BUG, which turned
out not to resolve the problem.
Please switch to @Seth Forshee's kernel as linked to #108:
http://people.canonical.com/~sforshee/lp1674838/
That kernel identifies itself as: 4.10.0-20-generic
@ehsan, what do you mean? I can't see any error in the kern.log, which
corresponds to the ones we would expect in this thread. Not every kernel
panic is caused by the issue in this ticket.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
I am also experiencing the hang still with the lp1674838 kernel:
$ cat /proc/version
Linux version 4.10.0-21-generic (root@gomeisa) (gcc version 6.3.0 20170406
(Ubuntu 6.3.0-12ubuntu2) ) #23~lp1674838 SMP Mon May 1 16:13:17 UTC 2017
Please see the attached kern.log, for example around May 17
Ran into this bug during high load on 4.10.0-21
Followed @sxc731 Advice from...
https://bugs.launchpad.net/ubuntu/zesty/+source/linux/+bug/1674838/comments/138
Things seem good now.
Thanks for the good work here. Look forward to the fix dropping.
--
You received this bug notification because
@jonas-slivka that's not related to this ticket.
You have a different bug:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1677673
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
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
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 SMP Wed May 3 13:41:02
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
Attaching kern.log with stack trace.
** Attachment added:
Same as Adrian, here, I've been testing Seth Forshee's kernel for 4+
days experimenting no more crash (versus 2/3 crash a day).
$ uname -a
Linux tignasse 4.10.0-20-generic #22+lp1674838v201705030839 SMP Wed May 3
13:41:02 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
--
You received this bug
Just to add another confirmation regarding Seth Forshee's kernel, I've
be up for 11 days now with it and was crashing every 1 or 2 days (since
upgrading to Zesty).
Uptime
16:39:28 up 11 days, 6:54, 2 users, load average: 0.99, 0.91, 0.99
uname -r
4.10.0-20-generic
uname -a
Linux adrian-AMD
** Changed in: linux-hwe-edge (Ubuntu Zesty)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1674838
Title:
kernel BUG at /build/linux-
> One issue with Seth Forshee's kernel is that it doesn't work with secure
> boot, so people might have to disable that temporarily) to be able to
> boot...
Yes, however the kernel which should be available in -proposed sometime
next week will have a signed counterpart.
Also while I'm commenting
One issue with Seth Forshee's kernel is that it doesn't work with secure
boot, so people might have to disable that temporarily) to be able to
boot...
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
This happens to me with 4.10.0-20 in Zesty KDE. It happens to me with a fresh
install and only when using a fresh firefox profile, with and without flash
enabled (and having a lot of tabs open); it leaves a zombie process after
manually killing it, but then the system locks in about a minute.
> 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
1 - 100 of 245 matches
Mail list logo
