I updated the kernel to 4.3 today but still got two crashes since then.
I also created /etc/mkinitcpio.conf and put "i915" in the file but that
did not change anything.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in
Public bug reported:
After upgrade 4.3.0 stable, this problem happened.
Actually I have another big problem.
When the monitor goes black, it never wakes up.
To overcome problem I have to reboot system.
Ctrl+Alt+F1 or other combinations never overcome the problem.
ProblemType: Package
Public bug reported:
The touchpad is not responsive at all. It worked fine with chomium os
but not ubuntu. I'm totally willing to work with you guys to get this
fixed. Ubuntu 14.04.3 LTS
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu
*** This bug is a duplicate of bug 1510970 ***
https://bugs.launchpad.net/bugs/1510970
@aldebx, sure, when I have a moment. I'm currently using xfce (xubuntu
desktop) to avoid problems.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg
I hope this doesn't necro this thread. But I can add some information
around this bug, and possible fixes for those plagued by it.
I had this problem, and it developed after accidentally deleting my home
directory, and rebuilding it piecemeal from an old backup (so it may be
configuration
Also have this bug
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1431714
Title:
[xorg-edgers] Held broken packages (libgbm1) from Xorg-edgers PPA
To manage notifications about this bug go to:
Sorry for the delay, but I was able to generate a backtrace as described
by Dirk Seidel in comment #7 and comment #8. The backtrace is attached.
** Attachment added: "gdb-X.txt"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1510998/+attachment/4512905/+files/gdb-X.txt
--
You received
actually you have three options:
* current kernel --> freezes
* current kernel + pstates-parameter -> warmer cpu
* kernel 3.16 --> no issues
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
It is quite hard for me to compare. Before I found this "magic" kernel
parameter, my notebook was usualy frozen before CPU could get any
warmer.. Since yesterday, I haven't seen more than 45C on all cores,
while working in office apps or watching a movie. I guess, this
temperature is not an issue
Currently I use kernel 3.16.0-4 (Debian Jessie default) and since that
change (before I had kernel 4.2) I do not experience any system freeze.
For now my computer (ASROCK SBC-211P, BYT CPU) is working second day
without any crash. Before, I had Kernel 4.2 on which I had system freeze
after 2min
3.16 working well on my DELL Inspiron 3646:
I've had little to no trouble ... even stressing the system using:
glmark2 --run-forever
I got my 3.16 kernel here:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.16.7-ckt18-utopic/
I'm currently using Ubuntu 15.10 with the 3.16 kernel.
Hope
Same here with random freezes. Tried intel_pstate=disabled which works.
However, cutting the max GPU frequency to about 50% also works for me.
Video seems smoother compared to pstate=disabled. YMMV
Running 64 bit Mint 17.2/Cinnamon on ASUS T100-CHI linux-4.2.5 w/Ubuntu
base and T100 specific
To cap frequency I read the max (779 for mine) from
cat /sys/class/drm/card0/gt_max_freq_mhz
To set pick a lower value (as root)
echo 423 > /sys/kernel/debug/dri/0/i915_max_freq
I tried lower values in 100 Mhz steps until I found stability (to 423 in
my case).
I think you could just put back
Every kernel above 3.16.x just fails.
3.16.x - no freeze
> 3.16.x - freezes no later than six hours after video launch.
I checked many kernel versions: 3.16.x, 3.17.x, 3.18.x, 3.19.x, 4.0.x,
4.1.x, 4.2.x and latest 4.3. None of described above kernel parameters
works.
For tests I used ASROCK
Me too... random freezes with Gentoo on a Biostar J1900MH2. Used as a
HTPC/mythfrontend, so any kernel too old to provide audio over HDMI is
not OK. I have been testing different BIOS settings and kernel configs.
Currently running 4.2.4
--
You received this bug notification because you are a
Given Luka Karinja's results, I checked my kernel args to see if
something else could account for my results. I found -
i915.i915_enable_rc6=1 i915.lvds_downclock=1 i915.semaphores=1
i915.i915_enable_fbc=1.
rc6=1 seems to be known to add instability, perhaps the freq cap offset
that. I've
I have found a setting that controls the random freezes, at least on my
board. Disabling "IGD Turbo Enable" under NorthBridge options in the
BIOS. Otherwise, the BIOS is set to the defaults.
Different kernel .configs had no effect. I have enabled all Baytrail
options and boot from an EFI stub.
I still get rare freezes on ubuntu with linux-image-generic-lts-utopic
(kernel 3.16.0). Does pstates=disabled only effect Intel-CPUs or AMDs as
well? I am searching for a general setup that doesnt effect AMD-cpus but
Intel Baytrail only.
--
You received this bug notification because you are a
3.16 working well on my DELL Inspiron 3646:
I've had little to no trouble ... even stressing the system using:
glmark2 --run-forever
I got my 3.16 kernel here:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.16.7-ckt18-utopic/
I'm currently using Ubuntu 15.10 with the 3.16 kernel.
Hope
Lowering i915_max_freq, even setting it to min still freezes my T100TAF (Atom
Z3735).
I haven't experienced any freezes with pstate=disabled, but performance is
really affected
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
(In reply to John from comment #102)
> Given Luka Karinja's results, I checked my kernel args to see if something
> else could account for my results. I found - i915.i915_enable_rc6=1
> i915.lvds_downclock=1 i915.semaphores=1 i915.i915_enable_fbc=1.
i915.i915_enable_rc6 and i915.i915_enable_fbc
(In reply to Jani Nikula from comment #105)
> i915.i915_enable_rc6 and i915.i915_enable_fbc have been renamed
> i915.enable_rc6 and i915.enable_fbc, respectively, since v3.15 so those have
> had no impact.
>
> These days all of those are considered debug options, and we taint the
> kernel if
How to limit the GPU frequency?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1453298
Title:
Xubuntu freeze once a day
To manage notifications about this bug go to:
Same here with random freezes. Tried intel_pstate=disabled which works.
However, cutting the max GPU frequency to about 50% also works for me.
Video seems smoother compared to pstate=disabled. YMMV
Running 64 bit Mint 17.2/Cinnamon on ASUS T100-CHI linux-4.2.5 w/Ubuntu
base and T100 specific
I still get rare freezes on ubuntu with linux-image-generic-lts-utopic
(kernel 3.16.0). Does pstates=disabled only effect Intel-CPUs or AMDs as
well? I am searching for a general setup that doesnt effect AMD-cpus but
Intel Baytrail only.
--
You received this bug notification because you are a
Yes, both are installed. Looking at the segmentation fault hotspot log
from my java application, it says libwayland and mesa-egl are being
loaded. I don't have gnome-session-wayland even installed and mesa
shouldn't be loaded if fglrx is being used. I've attached the java log
as well.
**
I got similar errors here mostly with skype and keepassx.
I guess we're not alone
http://askubuntu.com/questions/693588/some-applications-become-garbled-and-unusable
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1510021/+attachment/4512851/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1510021/+attachment/4512850/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "Xrandr.txt"
https://bugs.launchpad.net/bugs/1510021/+attachment/4512857/+files/Xrandr.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1510021
apport information
** Attachment added: "DpkgLog.txt"
https://bugs.launchpad.net/bugs/1510021/+attachment/4512840/+files/DpkgLog.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1510021
apport information
** Attachment added: "GconfCompiz.txt"
https://bugs.launchpad.net/bugs/1510021/+attachment/4512841/+files/GconfCompiz.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "xdpyinfo.txt"
https://bugs.launchpad.net/bugs/1510021/+attachment/4512858/+files/xdpyinfo.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1510021
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1510021/+attachment/4512852/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "MonitorsUser.xml.txt"
https://bugs.launchpad.net/bugs/1510021/+attachment/4512849/+files/MonitorsUser.xml.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
Interesting indeed! Seeing as things worked fine in Vivid I'm assuming it's
some sort of kernel thing.
Thanks for adding the info.
Regards,
Maarten
On Wed, Nov 4, 2015 at 6:01 PM Gareth Woolridge <
gareth.woolri...@canonical.com> wrote:
> Run as requested (with the MiniDP to VGA) adaptor
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1510021/+attachment/4512839/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "LightdmGreeterLog.txt"
https://bugs.launchpad.net/bugs/1510021/+attachment/4512844/+files/LightdmGreeterLog.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "LightdmGreeterLogOld.txt"
https://bugs.launchpad.net/bugs/1510021/+attachment/4512845/+files/LightdmGreeterLogOld.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "LightdmLog.txt"
https://bugs.launchpad.net/bugs/1510021/+attachment/4512846/+files/LightdmLog.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "LightdmDisplayLog.txt"
https://bugs.launchpad.net/bugs/1510021/+attachment/4512843/+files/LightdmDisplayLog.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
Run as requested (with the MiniDP to VGA) adaptor connected.
Interestingly I tried this with a colleagues generic el cheapo MiniDP to
{VGA,HDMI,DVI} adaptor and successfully got my monitors native
resolution.
So for me at least it appears that the limited resolution issue only
occurs with an
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1510021/+attachment/4512847/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1510021
Title:
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1510021/+attachment/4512854/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1510021
apport information
** Attachment added: "XorgLogOld.txt"
https://bugs.launchpad.net/bugs/1510021/+attachment/4512856/+files/XorgLogOld.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "XorgLog.txt"
https://bugs.launchpad.net/bugs/1510021/+attachment/4512855/+files/XorgLog.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1510021
apport information
** Attachment added: "xserver.devices.txt"
https://bugs.launchpad.net/bugs/1510021/+attachment/4512859/+files/xserver.devices.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
apport information
** Tags added: apport-collected ubuntu
** Description changed:
In Vivid on connection of external display using displayport to VGA
adaptor all resolutions upto max of my monitor were supported.
Since upgrade to Wily while my internal display operates correctly the
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1510021/+attachment/4512842/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1510021/+attachment/4512848/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1510021
Title:
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1510021/+attachment/4512853/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
I have the same problem and I have the crash file in /var/crash, should
I upload it?
** Changed in: xorg (Ubuntu)
Status: Expired => Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
*** This bug is a duplicate of bug 1510970 ***
https://bugs.launchpad.net/bugs/1510970
I am sorry, but for the moment, I cannot reproduce this bug. I have no
explanation for that. However I can say that there is no files in
/var/crash related to the problem. I will check it if I can reproduce
the bug shows up mainly when i dock the windows to left side of the
screen where I also have the sidebar. However, sometimes on the other
side too. Couldn't figure out in which cases.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in
Public bug reported:
On: Ubuntu 15.10
After some random amount of time (at first correlated with actions such
as switching between screens, max-/minimising windows, but now also
sometimes not), the display server seems to die completely, restarting
after a few seconds to dump me at the login
xorg does seem not to find the nvidia driver:
from XorgLog.txt:
[ 1644.929] (EE) Failed to load module "nvidia" (module does not exist, 0)
But I guess this should not be a problem, since it is using nouveau
driver in the end?
But then there is also this error in the same file:
[ 1645.014]
I have updated to Ubuntu 15.10 and installed the library xserver-xort-
input-libinput but the ultranav doesn't work fully. The functionality I
get is
L
L
L
LLLl
So the right mouse button is on the bottom right and the middle
button/scrolling doesn't
57 matches
Mail list logo
