Windows 10 is freezing in the exact same way. I guess something is
broken in this laptop and I'll keep using 3.13.x now and Windows 7 until
2019. If the laptop survives that far :) thanks for the help Stefan!
** Changed in: linux-lts-utopic (Ubuntu)
Status: New => Invalid
--
You received
Sounds more and more odd. Maybe things are related on how long the
system is powered on. It has been a while, but I had that once. Random
freezes but rather shortly after cold boot. Though that was a desktop
and back then it was the connectors of the power supply not all fitted
firmly. So
Hi again. I'm continously trying different scenarios, with and without
text mode, different kernels, wifi on or off, but I can't say for sure
what's going on. A daily image (from 15.4) of Xubuntu Xenial froze after
about an hour of usage and after just a couple of minutes the following
boot. This
Ok, it sounds more like there could be a crash behind the scene and
everything stops working. On the text console bit I was a bit unclear.
What I meant was to switch to text right from the start and do the login
on the text console and also play around while being in text mode. If it
crashes then,
Thanks for the ideas! Did you mean 3.16.0-67 and not -87? I tried -67
now with and without vesafb:mtrr:0. System freezes within minutes in
both cases.
I also tried mainline 3.16.7-ckt26-trusty and added vesafb:mtrr:3 to
this and the system does NOT seem to freeze. This bug is weird.
3.16.0-38 was
Oh, yes. We freeze completely at random. It can freeze at idle after
simply booting, when clicking a link in firefox or when just moving
windows around. Seems very random :/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-utopic
So the change of cache mode for the VESA frambuffer driver is at least
not the only offender. It might even have no impact at all but I would
not be 100% sure, yet. Normally this sounds like something that needs a
bisect (building various kernels at stages between 3.16.0-37 and 38
which you would
Hi! Thanks for your time. I really appreciate it. Attached cat_proc_mtrr shows
'cat /proc/mtrr' directly after boot for
- kernel 3.16.0-37 (not affected kernel)
- kernel 3.16.0-38 (affected kernel)
- kernel 3.16.0-38 + video=vesafb:mtrr:0 (affected + possible workaround)
You were right, the
Odd, in theory that change should only affect the MTRR cache mode of the video
memory for the generic VESA framebuffer driver. And while that is used
initially it gets replaced later on by the special driver for radeon.
Maybe two things: First, after completing boot into an affected kernel,
apport information
** Tags added: apport-collected trusty
** Description changed:
This should have been reported already last year, but here it goes.
Problem:
My laptop is a ASUS N71JA and works perfectly in Windows. Everything was fine
with Xubuntu 14.04 through kernels 3.13 and 3.16
I'm unable to run 'apport-collect 1561902', as it says "Package linux-
lts-utopic not installed and no hook available, ignoring". Any help?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-utopic in Ubuntu.
11 matches
Mail list logo
