@kiki I don't believe so, I'll keep an a special eye out for it, but I
imagine I would have seen it by now tbh. I think nearly all of the bug
reports come from the upgrade process where the upgrade tool
automatically starts a bug report on launchpad whenever it encounters an
error.
"but perhaps
@kiko You're probably quite right that it's the zfs-dkms package that's
the problem. However removing it now seem's rather fruitless now that
the upgrade is completed (which is the only case where I've personally
seen this bug occur), and the package is not causing any problems/
errors presently
@kiko Interesting thought there! That could be it! I am aware of the
change, however from a users point of view, I believe enabling the
zfsutils-linux package remains the same to actually use ZFS.
Perhaps the issue is the zfs-dkms package should be removed (entirely or
as a dependency of
@rockorequin thanks for the very clear answer! It appears that the
default governor in the newer Ubuntu kernels has become P-state now
then, as opposed to the older ACPI CPUfreq! Now I know that it's simply
changed, I'll be using the new P-state governors! :)
@jsalisbury just installed, I'll let
Is there a way to add the mainline kernel as a true PPA so that we get
updates automatically?
Would this also restore the CPU governors? The only problem I've found
when installing and using the custom kernels directly from the .deb
files (like from http://kernel.ubuntu.com/~kernel-
@jsalisbury Okay I think we're getting somewhere with this! (With this
kernel: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.19-rc3-vivid/)
I haven't had this issue at all and my system has been very stable! XD
If you're still experiencing this I suggest using this to solve the
problem!
--
@jsalisbury am also testing for the past 7-8 hours now and so far has
been stable as well so thanks for the update! :)
I think it would be too early to declare this bug fixed yet though!
However, I recommend everyone gets this kernel (http://kernel.ubuntu.com
Can confirm with a_user that sometimes this problem occurs without
leaving syslog entries :/
--
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/1384342
Title:
kernel messages
@jsalisbury https://bugzilla.kernel.org/show_bug.cgi?id=64431 is this
not already done here? Or does a new one need to be created for the
kernel 3.17 I tested?!?
Also note for anyone else affected, so far no occurrence of this bug in
Kernel 3.18.0-994-generic #201411010205 from
I spoke to soon, I did experience this bug under this kernel
http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-next/current/ -
though I couldn’t find anything in the system log, just experienced the
lock up in the exact same way . Now gone back to this kernel
That's kernel 3.18.0-994-generic #201411010205 from
http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-
nightly/2014-11-01-vivid/ that I'm currently testing! :)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Using a newer kernel does seem to fix the problem: I’ve been using this
kernel (http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-
next/current/) for a few days now without this issue happening once!
--
You received this bug notification because you are a member of Kernel
Packages, which
I'm running on an Intel Haswell i5-4670K and can confirm this happens
intermittently without VT switching but it can often be be made to
happen much more often by doing VT switches.
I'm running the lasest Utopic 3.16.0-24-generic #32-Ubuntu kernel on
x86_64 and I've got a trace from syslog of
I'm also unable to find any segfaults in the Xorg logs which is strange
:/ Also as a sidenote sometimes running 'killall -9 compiz' can help
recovery back to a working VT and stop the lock-up (if there is one -
I'm running multiple desktop sessions), if the compiz on another VT has
crashed!
--
14 matches
Mail list logo
