https://bugs.freedesktop.org/show_bug.cgi?id=12037
GitLab Migration User <gitlab-migration(a)fdo.invalid> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |MOVED
--- Comment #1 from GitLab Migration User <gitlab-migration(a)fdo.invalid> ---
-- GitLab Migration Automatic Message --
This bug has been migrated to freedesktop.org's GitLab instance and has been
closed from further activity.
You can subscribe and participate further through the new bug through this link
to our GitLab instance:
https://gitlab.freedesktop.org/openchrome/old-bug-database/issues/6.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=12021
GitLab Migration User <gitlab-migration(a)fdo.invalid> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |MOVED
--- Comment #4 from GitLab Migration User <gitlab-migration(a)fdo.invalid> ---
-- GitLab Migration Automatic Message --
This bug has been migrated to freedesktop.org's GitLab instance and has been
closed from further activity.
You can subscribe and participate further through the new bug through this link
to our GitLab instance:
https://gitlab.freedesktop.org/openchrome/old-bug-database/issues/5.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=11531
GitLab Migration User <gitlab-migration(a)fdo.invalid> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |MOVED
Status|NEW |RESOLVED
--- Comment #2 from GitLab Migration User <gitlab-migration(a)fdo.invalid> ---
-- GitLab Migration Automatic Message --
This bug has been migrated to freedesktop.org's GitLab instance and has been
closed from further activity.
You can subscribe and participate further through the new bug through this link
to our GitLab instance:
https://gitlab.freedesktop.org/openchrome/old-bug-database/issues/4.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=10967
GitLab Migration User <gitlab-migration(a)fdo.invalid> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |MOVED
--- Comment #2 from GitLab Migration User <gitlab-migration(a)fdo.invalid> ---
-- GitLab Migration Automatic Message --
This bug has been migrated to freedesktop.org's GitLab instance and has been
closed from further activity.
You can subscribe and participate further through the new bug through this link
to our GitLab instance:
https://gitlab.freedesktop.org/openchrome/old-bug-database/issues/3.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=10966
GitLab Migration User <gitlab-migration(a)fdo.invalid> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |MOVED
Status|NEW |RESOLVED
--- Comment #19 from GitLab Migration User <gitlab-migration(a)fdo.invalid> ---
-- GitLab Migration Automatic Message --
This bug has been migrated to freedesktop.org's GitLab instance and has been
closed from further activity.
You can subscribe and participate further through the new bug through this link
to our GitLab instance:
https://gitlab.freedesktop.org/openchrome/old-bug-database/issues/2.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=1633
GitLab Migration User <gitlab-migration(a)fdo.invalid> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |MOVED
--- Comment #3 from GitLab Migration User <gitlab-migration(a)fdo.invalid> ---
-- GitLab Migration Automatic Message --
This bug has been migrated to freedesktop.org's GitLab instance and has been
closed from further activity.
You can subscribe and participate further through the new bug through this link
to our GitLab instance:
https://gitlab.freedesktop.org/openchrome/old-bug-database/issues/1.
--
You are receiving this mail because:
You are the assignee for the bug.
tree: git://people.freedesktop.org/~agd5f/linux.git amd-mainline-dkms-5.0
head: a51a5ad4b8daf0dd0a437d51a19c2baa98953675
commit: fbb2398b29e0de236e9ee3ad48385095ebcb2a84 [2219/3724] drm/amd/autoconf: fix in-build error for O=...
config: ia64-allmodconfig (attached as .config)
compiler: ia64-linux-gcc (GCC) 7.4.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git checkout fbb2398b29e0de236e9ee3ad48385095ebcb2a84
# save the attached .config to linux build tree
GCC_VERSION=7.4.0 make.cross ARCH=ia64
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp(a)intel.com>
All errors (new ones prefixed by >>):
>> configure: error: in `drivers/gpu/drm/ttm/dkms':
>> configure: error: C compiler cannot create executables
See `config.log' for more details
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
https://bugs.freedesktop.org/show_bug.cgi?id=111730
Bug ID: 111730
Summary: Xorg does not render with mesa 19.1.7
Product: Mesa
Version: 19.1
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: major
Priority: not set
Component: Drivers/DRI/i915
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: edoars(a)gmail.com
QA Contact: dri-devel(a)lists.freedesktop.org
Created attachment 145423
--> https://bugs.freedesktop.org/attachment.cgi?id=145423&action=edit
screenshot
After updating to mesa 19.1.7 Xorg won't render anything except the shape of
the windows (see screenshot attached).
This happen only with mesa 19.1.7, both downgrading to 19.1.6 and upgrading to
19.3 solve the issue.
I will attach logs of the system when booting with mesa 19.1.7.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=111386
Bug ID: 111386
Summary: Mesa 19.1.1 introduced Tearing
Product: Mesa
Version: 19.1
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/DRI/i915
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: dave.diamond00(a)gmail.com
QA Contact: dri-devel(a)lists.freedesktop.org
Hi, I landed here by suggestion of another user of the OS which I'm using:
Manjaro Linux [1]
Let's start with my system specs:
https://pastebin.com/5MuBGinn
Since the upgrade of Mesa package to 19.1.1, my graphics (Intel i915) begun to
suffer of video tearing: before of such update I never experienced video
Tearing, thanks to the compositor (the one shipped by default on XFCE and also
if using Compton instead).
To get rid of video tearing I had to enable the <Option "TearFree" "true"> in
the /etc/X11/xorg.conf.d/20-intel.conf file.
Furthermore seems that another user of Manjaro, encountered the same issue of
Mesa:
https://forum.manjaro.org/t/stable-update-2019-07-03-kernels-systemd-pamac-…
[1] https://forum.manjaro.org/t/i915-graphics-and-tearing/98500
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=110971
Bug ID: 110971
Summary: GPU HANG: ecode 6:1:0xfffffffe, in spring-main [8656],
hang on rcs0
Product: Mesa
Version: 19.1
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: critical
Priority: medium
Component: Drivers/DRI/i915
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: Chris.Rebischke(a)archlinux.org
QA Contact: dri-devel(a)lists.freedesktop.org
Created attachment 144614
--> https://bugs.freedesktop.org/attachment.cgi?id=144614&action=edit
crash dump from /sys/class/drm/card0/error
I get unspecified GPU hangs while playing games. It mostly occurs when my CPU
starts throttling:
[ 5838.889104] mce: CPU0: Package temperature above threshold, cpu clock
throttled (total events = 100749)
[ 5838.889108] mce: CPU2: Package temperature above threshold, cpu clock
throttled (total events = 100749)
[ 5838.889110] mce: CPU3: Package temperature above threshold, cpu clock
throttled (total events = 100749)
[ 5838.889112] mce: CPU1: Package temperature above threshold, cpu clock
throttled (total events = 100749)
[ 5900.819612] mce: CPU2: Core temperature above threshold, cpu clock throttled
(total events = 16235)
[ 5900.819613] mce: CPU3: Core temperature above threshold, cpu clock throttled
(total events = 16235)
[ 5900.827685] mce: CPU2: Core temperature/speed normal
[ 5900.827686] mce: CPU3: Core temperature/speed normal
[ 6138.891505] mce: CPU1: Package temperature above threshold, cpu clock
throttled (total events = 171156)
[ 6138.891506] mce: CPU0: Package temperature above threshold, cpu clock
throttled (total events = 171156)
[ 6138.891528] mce: CPU2: Package temperature above threshold, cpu clock
throttled (total events = 171156)
[ 6138.891529] mce: CPU3: Package temperature above threshold, cpu clock
throttled (total events = 171156)
[ 6176.479565] i915 0000:00:02.0: GPU HANG: ecode 6:1:0xfffffffe, in
spring-main [8656], hang on rcs0
[ 6176.479570] [drm] GPU hangs can indicate a bug anywhere in the entire gfx
stack, including userspace.
[ 6176.479572] [drm] Please file a _new_ bug report on bugs.freedesktop.org
against DRI -> DRM/Intel
[ 6176.479573] [drm] drm/i915 developers can then reassign to the right
component if it's not a kernel issue.
[ 6176.479574] [drm] The gpu crash dump is required to analyze gpu hangs, so
please always attach it.
[ 6176.479575] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[ 6176.479642] i915 0000:00:02.0: Resetting chip for hang on rcs0
[ 6422.644956] i915 0000:00:02.0: Resetting chip for hang on rcs0
[ 6438.888919] mce: CPU3: Package temperature/speed normal
[ 6438.888920] mce: CPU2: Package temperature/speed normal
[ 6438.888924] mce: CPU1: Package temperature/speed normal
[ 6438.888926] mce: CPU0: Package temperature/speed normal
--
You are receiving this mail because:
You are the assignee for the bug.