i had the same problem in my netbook which also have the same amd chip
A10-8700p with r7 m360 i try centos 7, fedora 23-24, mint 17-18,ubuntu
all have the same network problem(both wireless and wire ) display
problem battery drain very low sound and all of disto show black screen
at first startup
** Description changed:
I regularly get Xorg freezes if I log in immediately after booting, and
only when when running dual 4k displays (internal and external). If I
- alt-ctrl-F1 to virtual console and enter a catchall
+ alt-ctrl-F1 to virtual console, login and enter a catchall
$
Issue no longer occurs with kernel 4.4.0-28-generic. Marking status as
invalid.
** Changed in: xorg (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
** Summary changed:
- Xorg freeze
+ Xorg freezes regularly on login, more likely immediately after boot
** Description changed:
- The intel video drivers have been steadily improving, but I occasionally
- get freezes. I get them more often when logging in immediately after
- booting, and only
# cat /sys/kernel/debug/dri/0/i915_error_state
no error state collected
--
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/1600414
Title:
Xorg freezes regularly on login, more likely immediately
Public bug reported:
The intel video drivers have been steadily improving, but I occasionally
get freezes. I get them more often when logging in immediately after
booting, and only when running dual 4k displays (internal and external).
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg
I submitted this bug report via ssh while X is hung.
--
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/1600414
Title:
Xorg freeze
To manage notifications about this bug go to:
Roger Merritt, could you please capture the full failed boot output via
https://wiki.ubuntu.com/DebuggingKernelBoot ?
** Tags added: kernel-fixed-upstream kernel-fixed-upstream-4.4.13
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a
Sorry, I need to proofread more carefully. It's kernel 4.7rc6. The complete
line from the grub menu is:
Ubuntu, with Linux 4.7.0-0407004c6-generic
I've installed 4.4.13, and it, too, seems to be working normally.
On Thu, Jul 7, 2016 at 6:14 PM, Christopher M. Penalver <
Oh, boy. I did it again. That should have been ...040700*r*c6-generic.
On Thu, Jul 7, 2016 at 6:14 PM, Christopher M. Penalver <
christopher.m.penal...@gmail.com> wrote:
> Roger Merritt:
> >"successfully installed the mainline kernel 4.6-rc6"
>
> Did you test 4.7-rc6, or 4.6-rc6?
>
>
> In the Ubuntu Quality mailing list a couple of people suggested this is a
> duplicate
> of https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1543046
I have disabled intel-powerclamp and intel-rapl entirely and I am not
affected by that issue anymore (no spamming of the kernel log) (btw,
Public bug reported:
boot system error
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libsm6:i386 2:1.2.2-1
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
Date: Fri Jul 8 15:42:34 2016
elementary OS 0.4 Loki Beta (Ubuntu 16.04 based) is also effected.
--
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/1568604
Title:
Mouse cursor lost when unlocking with Intel
** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-landing-036
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1584784
Title:
Using NBS, X apps under Unity8 need interaction to
This bug affects me too. The external monitor connected via HDMI to a
Lenovo Thinkpad X1 yoga reports: "Please change your input timing to
1920x1200@60Hz", and xrandr shows that the monitor is being served at
1920x1200 59.95*+, which is a bizarre number that is almost 60Hz. Using
linux kernel
It does remember them as you see in the restore list, but because the
app isn't told its shutting down it doesn't clean up. I would expect
Xmit could do something about this?
** Also affects: libertine (Ubuntu)
Importance: Undecided
Status: New
** Changed in: frieza
Status: New
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1575391
** Tags added: iso-testing
--
You received this bug notification because you are a member of Ubuntu-X,
which is
Stein-Magne Pedersen, to see if this is already resolved, could you
please test http://cdimage.ubuntu.com/daily-live/current/ and advise to
the results?
** Tags removed: bios-outdated-1604
** Tags added: latest-bios-1604
** Description changed:
The mouse pointer is fine at boot, but after
** Changed in: mesa (Ubuntu)
Assignee: (unassigned) => Timo Aaltonen (tjaalton)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1585942
Title:
Mesa causes a segmentation fault on arm64
Sorry for not responding earlier.
I have updated my bios but the issue still remains.
Output from terminal:
1604
10/16/2012
I can't give any more spesific details than my original post. But I can
say that I disabled the fglrx drivers and the problem went away, but I
don't get the benefits of my
** Changed in: linux (Ubuntu)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Timo Aaltonen (tjaalton)
** Also affects: libdrm (Ubuntu)
Importance: Undecided
Status: New
** Also affects: mesa (Ubuntu)
Importance: Undecided
If you've been on 16.04 for some time and it worked fine until some
update, then the only plausible update breaking it is likely the kernel.
You should have earlier 4.4 kernels installed, try them to see if it
goes away. And check dmesg after suspend, corrupt rendering might mean
there's a GPU
Btw. why has this issue low priority only? It's nearly as bad as if
xserver crashes, including possible loss of unsaved data. User has to
reboot which can only be done "blind" or by pressing a hardware power
button (which can be harmful in itsself again).
--
You received this bug notification
I had the same issue for a long time in 14.04 at least together with
kernel 4.2 (and very likely 3.19 and maybe even before if I remember
right).
It is still not fixed in ubuntu 16.04, kernel 4.4.0-28-generic.
I get this problem mostly after suspend. But I rarely get the invisible
characters
24 matches
Mail list logo
