[Bug 60879] [radeonsi] Tahiti LE: GFX block is not functional, CP is okay

2019-09-25 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=60879

GitLab Migration User  changed:

   What|Removed |Added

 Status|REOPENED|RESOLVED
 Resolution|--- |MOVED

--- Comment #181 from GitLab Migration User  ---
-- 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/mesa/mesa/issues/1208.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

[Bug 60879] [radeonsi] Tahiti LE: GFX block is not functional, CP is okay

2019-09-20 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=60879

--- Comment #180 from Alex Deucher  ---
Does booting with pci=noats on the kernel command line in grub help?

-- 
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

[Bug 60879] [radeonsi] Tahiti LE: GFX block is not functional, CP is okay

2019-07-19 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=60879

--- Comment #179 from zaindavid  ---
great post.
http://www.winmilliongame.com
http://www.gtagame100.com
http://www.subway-game.com
http://www.zumagame100.com

-- 
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

[Bug 60879] [radeonsi] Tahiti LE: GFX block is not functional, CP is okay

2019-02-03 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=60879

--- Comment #178 from MAD  ---
Created attachment 143279
  --> https://bugs.freedesktop.org/attachment.cgi?id=143279=edit
Xorg-amdgpu-4.20.6.log

-- 
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel


[Bug 60879] [radeonsi] Tahiti LE: GFX block is not functional, CP is okay

2019-02-03 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=60879

--- Comment #177 from MAD  ---
Created attachment 143278
  --> https://bugs.freedesktop.org/attachment.cgi?id=143278=edit
journalctl-b0-amdgpu-4.20.6.log

-- 
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel


[Bug 60879] [radeonsi] Tahiti LE: GFX block is not functional, CP is okay

2019-02-03 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=60879

--- Comment #176 from MAD  ---
Created attachment 143277
  --> https://bugs.freedesktop.org/attachment.cgi?id=143277=edit
Xorg-radeonsi-4.20.6.log

-- 
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel


[Bug 60879] [radeonsi] Tahiti LE: GFX block is not functional, CP is okay

2019-02-03 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=60879

--- Comment #175 from MAD  ---
Created attachment 143276
  --> https://bugs.freedesktop.org/attachment.cgi?id=143276=edit
journalctl-b0-radeonsi-4.20.6.log

-- 
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel


[Bug 60879] [radeonsi] Tahiti LE: GFX block is not functional, CP is okay

2019-01-31 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=60879

--- Comment #174 from EmilyBrown  ---
Thanks for coming with detailed bug which you faced while starting X server and
what happened after few minutes within screenshots for better reference to find
a solution for other users and experts of it.

Emily,
http://www.dissertationhelp.uk

-- 
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel


[Bug 60879] [radeonsi] Tahiti LE: GFX block is not functional, CP is okay

2018-03-20 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=60879

--- Comment #173 from madmalkav <myhateisbl...@hotmail.com> ---
As it has failed to attract any developer attention in for two years, I have
cancelled the bountysource reward.

From: bugzilla-dae...@freedesktop.org <bugzilla-dae...@freedesktop.org>
Sent: Saturday, November 4, 2017 10:14:28 PM
To: myhateisbl...@hotmail.com
Subject: [Bug 60879] [radeonsi] Tahiti LE: GFX block is not functional, CP is
okay


Comment # 172<https://bugs.freedesktop.org/show_bug.cgi?id=60879#c172> on bug
60879<https://bugs.freedesktop.org/show_bug.cgi?id=60879> from
MAD<mailto:adamc...@tlen.pl>

Created attachment 135239<attachment.cgi?id=135239>
[details]<attachment.cgi?id=135239=edit>
journalctl_amdgpu_4.14.0-041400rc7

I've had more luck with amdgpu. Well kinda. It finally boots without nomodeset
(starting from 4.13 kernel). But falls back to software rendering (Device:
llvmpipe). It also complains that:
amdgpu :01:00.0: SI support provided by radeon.
amdgpu :01:00.0: Use radeon.si_support=0 amdgpu.si_support=1 to override.

But when I start it with:
modprobe.blacklist=radeon radeon.si_support=0 amdgpu.si_support=1

screen freezes, gnome doesn't start and it produces output from attachment.
Something about "dead whales":
lis 04 19:35:39 pc gnome-session-binary[1369]: CRITICAL: We failed, but the
fail whale is dead. Sorry

There is also something about:
lis 04 19:34:09 pc org.gnome.Shell.desktop[1440]: amdgpu_device_initialize:
Cannot parse ASIC IDs, 0xffea./usr/share/libdrm/amdgpu.ids: No such file or
directory


You are receiving this mail because:

  *   You are on the CC list for the bug.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel


[Bug 60879] [radeonsi] Tahiti LE: GFX block is not functional, CP is okay

2017-11-04 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=60879

--- Comment #172 from MAD  ---
Created attachment 135239
  --> https://bugs.freedesktop.org/attachment.cgi?id=135239=edit
journalctl_amdgpu_4.14.0-041400rc7

I've had more luck with amdgpu. Well kinda. It finally boots without nomodeset
(starting from 4.13 kernel). But falls back to software rendering (Device:
llvmpipe). It also complains that:
amdgpu :01:00.0: SI support provided by radeon.
amdgpu :01:00.0: Use radeon.si_support=0 amdgpu.si_support=1 to override.

But when I start it with:
modprobe.blacklist=radeon radeon.si_support=0 amdgpu.si_support=1 

screen freezes, gnome doesn't start and it produces output from attachment.
Something about "dead whales":
lis 04 19:35:39 pc gnome-session-binary[1369]: CRITICAL: We failed, but the
fail whale is dead. Sorry

There is also something about:
lis 04 19:34:09 pc org.gnome.Shell.desktop[1440]: amdgpu_device_initialize:
Cannot parse ASIC IDs, 0xffea./usr/share/libdrm/amdgpu.ids: No such file or
directory

-- 
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel


[Bug 60879] [radeonsi] Tahiti LE: GFX block is not functional, CP is okay

2017-11-04 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=60879

--- Comment #171 from MAD  ---
Created attachment 135238
  --> https://bugs.freedesktop.org/attachment.cgi?id=135238=edit
journalctl_radeon_4.14.0-041400rc7

[AMD/ATI] Tahiti LE [Radeon HD 7870 XT]
4.14.0-041400rc7-generic from: http://kernel.ubuntu.com/~kernel-ppa/mainline/
OpenGL version string: 3.0 Mesa 17.3.0-rc2 - padoka PPA

Basically still the same, black screen then:
radeon :01:00.0: ring 0 stalled for more than 10244msec

And then:
radeon :01:00.0: GPU reset succeeded, trying to resume

That's the last line in log file, after this I can no longer connect via ssh.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel


[Bug 60879] [radeonsi] Tahiti LE: GFX block is not functional, CP is okay

2017-09-30 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=60879

--- Comment #170 from David Verelst  ---
Created attachment 134576
  --> https://bugs.freedesktop.org/attachment.cgi?id=134576=edit
journalctl -k amdgpu with linux-amd-staging-git

Also no luck with AMDGPU. Here's the kernel output for booting with
linux-amd-staging-git 4.12.0-2a69a4b35621, (on Arch Linux, see also
https://aur.archlinux.org/packages.php?ID=442065).

-- 
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel


[Bug 60879] [radeonsi] Tahiti LE: GFX block is not functional, CP is okay

2017-09-20 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=60879

David Verelst  changed:

   What|Removed |Added

 CC||david.vere...@gmail.com

--- Comment #169 from David Verelst  ---
Created attachment 134388
  --> https://bugs.freedesktop.org/attachment.cgi?id=134388=edit
dmesg radeon kernel 4.12.13

Not sure if it helps, but here's another dmesg output from radeon + kernel
4.12.13. What does work though is the fallback to llvmpipe, and I end up with a
working system + graphics.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel


[Bug 60879] [radeonsi] Tahiti LE: GFX block is not functional, CP is okay

2017-08-03 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=60879

--- Comment #168 from MAD  ---
Created attachment 133233
  --> https://bugs.freedesktop.org/attachment.cgi?id=133233=edit
dmesg radeon kernel 4.10

-- 
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel


[Bug 60879] [radeonsi] Tahiti LE: GFX block is not functional, CP is okay

2017-08-03 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=60879

--- Comment #167 from MAD  ---
Created attachment 133232
  --> https://bugs.freedesktop.org/attachment.cgi?id=133232=edit
Xorg.log amdgpu kernel 4.10

-- 
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel


[Bug 60879] [radeonsi] Tahiti LE: GFX block is not functional, CP is okay

2017-08-03 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=60879

--- Comment #166 from MAD  ---
Created attachment 133231
  --> https://bugs.freedesktop.org/attachment.cgi?id=133231=edit
dmesg amdgpu kernel 4.10

-- 
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel


[Bug 60879] [radeonsi] Tahiti LE: GFX block is not functional, CP is okay

2017-08-03 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=60879

--- Comment #165 from MAD  ---
4.10.0-28-generic
[AMD/ATI] Tahiti LE [Radeon HD 7870 XT]

I have the same problem with this card. 

On amdgpu I got black screen. But monitor remains on. I can log in via ssh and
all.

On radeon first I get screen full of colourful pixels, then black screen, then
monitor says no-signal and goes stand-by. And then pc hangs and I can no longer
log in via ssh.

On radeon there are a lot of 
radeon :01:00.0: ring 3 stalled for more than 10036msec
kinda logs in dmesg. But on amdgpu there is nothing interesting really. It
seems like it almost works, except for the black screen ;)

I think I'm gonna try fresh kernel from padoka ppa next. When I have some free
time.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel


[Bug 60879] [radeonsi] Tahiti LE: GFX block is not functional, CP is okay

2017-03-22 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=60879

--- Comment #164 from Vedran Miletić  ---
*** Bug 70779 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel


[Bug 60879] [radeonsi] Tahiti LE: GFX block is not functional, CP is okay

2016-12-13 Thread bugzilla-dae...@freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=60879

--- Comment #163 from Ayhan  ---
Created attachment 128452
  --> https://bugs.freedesktop.org/attachment.cgi?id=128452=edit
dmesg for linux 4.9 amdgpu driver

The attachment is dmesg of linux 4.9 and AMDGPU driver is in use. After startx,
the colorful scrambled screen happened again, but it stayed still, not
resetting screen for every 5-6 seconds like radeon driver. I issued a reboot
command via SSH shell, it returned into old framebuffer correctly and rebooted
succesfully, unlike the radeon driver case.

Dmesg file is the original one, not the journalctl capture, journalctl
sometimes omits some messages.

This line was written after startx:

[drm] : dce_v6_0_afmt_setmode no impl 

Also that line was omitted by journalctl...

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL: 



[Bug 60879] [radeonsi] Tahiti LE: GFX block is not functional, CP is okay

2016-12-11 Thread bugzilla-dae...@freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=60879

--- Comment #162 from John Steele Scott  ---
I just bit the bullet and swapped out my Radeon HD 7870 XT for an RX 480 due to
this issue. I'll happily donate the 7870 to any developer who would like to put
it to use fixing this bug. Get in touch in the next week or so if interested.
Otherwise I'll try and sell it before Christmas, it's still a good card for
Windows gaming.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL: 



[Bug 60879] [radeonsi] Tahiti LE: GFX block is not functional, CP is okay

2016-12-03 Thread bugzilla-dae...@freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=60879

--- Comment #161 from madmalkav  ---
Ben, I'm afraid the initialization of the conflicting parts of the card is just
delayed in your current install, that's why it fails later. Hope I'm wrong.

If you want support for your tests, #radeon @ irc.freenode.net is always full
of people that will give you a hand with that.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL: 



[Bug 60879] [radeonsi] Tahiti LE: GFX block is not functional, CP is okay

2016-11-25 Thread bugzilla-dae...@freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=60879

--- Comment #160 from Ben  ---
Created attachment 128182
  --> https://bugs.freedesktop.org/attachment.cgi?id=128182=edit
openSuse Tumbleweed - Linux 4.8.10

So I tested my card again by installing openSuse Tumbleweed on my computer
again and I don't know what happened, but I am now able to reach the KDE login
screen.

While the computer is booting up, there are graphical corruptions so I checked
dmesg to see if the card is really ok or not. The driver still has some trouble
with the card, but I am able to get into a graphical environment. How can I
help to completely fix the issue with this card?

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL: 



[Bug 60879] [radeonsi] Tahiti LE: GFX block is not functional, CP is okay

2016-10-15 Thread bugzilla-dae...@freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=60879

--- Comment #159 from madmalkav  ---
(In reply to Michel Dänzer from comment #158)
> Double-check that you're really building current Git master, and that your
> self-built radeonsi_dri.so is getting picked up.

You are probably right, but for personal reasons I won't continue testing
things for this bug. I hope some of other affected users step up and continue
the tests.

I will remain subscribed to the bug so I can grant the bounty if someone gets
to fix it.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL: 



[Bug 60879] [radeonsi] Tahiti LE: GFX block is not functional, CP is okay

2016-10-12 Thread bugzilla-dae...@freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=60879

--- Comment #158 from Michel Dänzer  ---
(In reply to madmalkav from comment #157)
> I've tried agd5f's 4.9 wip beanch with latest Mesa. Wflinfo fails with an
> "amdgpu: unkown family" error, no Gallium dump log, error on dmesg:

Which Mesa Git commit is that exactly? It looks like it's before SI support was
added to the amdgpu winsys code. Double-check that you're really building
current Git master, and that your self-built radeonsi_dri.so is getting picked
up.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL: 



[Bug 60879] [radeonsi] Tahiti LE: GFX block is not functional, CP is okay

2016-10-11 Thread bugzilla-dae...@freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=60879

--- Comment #157 from madmalkav  ---
Created attachment 127226
  --> https://bugs.freedesktop.org/attachment.cgi?id=127226=edit
Xorg log with lastest 4.9-wip kernel and mesa master branch

I've tried agd5f's 4.9 wip beanch with latest Mesa. Wflinfo fails with an
"amdgpu: unkown family" error, no Gallium dump log, error on dmesg:

[  353.579289] wflinfo[1529]: segfault at 8 ip 7f8260c8dd6a sp
7ffe2f8d74f0 error 4 in radeonsi_dri.so[7f8260912000+8fc000]

If I try to start X, similar errors appears.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL: 



[Bug 60879] [radeonsi] Tahiti LE: GFX block is not functional, CP is okay

2016-10-09 Thread bugzilla-dae...@freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=60879

--- Comment #156 from smoki  ---

 Or it was 3 weeks ago :D anyway who knows some magic touches like this might
change something:


https://cgit.freedesktop.org/~agd5f/linux/commit/?h=amd-staging-4.7=d207295db45b576eddf60749c0c24fc8528f3c80

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL: 



[Bug 60879] [radeonsi] Tahiti LE: GFX block is not functional, CP is okay

2016-10-09 Thread bugzilla-dae...@freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=60879

--- Comment #155 from smoki  ---

 At this point people might wanna try amdgpu driver too from agd5f tree... i
think i saw some commits for harvested chips there maybe week ago.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL: 



[Bug 60879] [radeonsi] Tahiti LE: GFX block is not functional, CP is okay

2016-10-09 Thread bugzilla-dae...@freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=60879

--- Comment #154 from madmalkav  ---
Nothing. More people doing tests surely will help, getting one of this cards to
a developer will be great, but I can't afford that at the moment -come on, AMD,
you surely have one or two on a basement...-

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL: 



[Bug 60879] [radeonsi] Tahiti LE: GFX block is not functional, CP is okay

2016-10-09 Thread bugzilla-dae...@freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=60879

--- Comment #153 from Vedran Miletić  ---
(In reply to madmalkav from comment #151)
> Created attachment 124324 [details]
> dmesg after the mesa dump
> 
> No more "Ring stalled..." messages with kernel 4.7rc1

madmalkav, any more recent findings?

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL: 



[Bug 60879] [radeonsi] Tahiti LE: GFX block is not functional, CP is okay

2016-10-09 Thread bugzilla-dae...@freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=60879

--- Comment #152 from clogged.drainpipe at gmail.com ---
Tahiti LE is still broken, after 3 years. Not trying to be a dick, but FFS, at
this point ALL the other cards based on very similar chips(7950, 7970, 280X)
work very well, and yet this one is still broken. I mean really, once you have
all the work well done for all similar cards, how can it be so hard to bring
this one to life?
I just upgraded from a HD4890 to a Tahiti LE card. I did not bother to check
how well it is supported under Linux before buying it, because I assumed that
all GCN1 cards are very well supported via radeonsi. Now I found out, that my
card is probably the only one that is not supported at all, so to say I am mad
would be an understatement.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL: 



[Bug 60879] [radeonsi] Tahiti LE: GFX block is not functional, CP is okay

2016-06-05 Thread bugzilla-dae...@freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=60879

--- Comment #151 from madmalkav  ---
Created attachment 124324
  --> https://bugs.freedesktop.org/attachment.cgi?id=124324=edit
dmesg after the mesa dump

No more "Ring stalled..." messages with kernel 4.7rc1

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL: 



[Bug 60879] [radeonsi] Tahiti LE: GFX block is not functional, CP is okay

2016-06-05 Thread bugzilla-dae...@freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=60879

--- Comment #150 from madmalkav  ---
Created attachment 124323
  --> https://bugs.freedesktop.org/attachment.cgi?id=124323=edit
New Mesa dump with Kernel 4.7rc1, mesa-git, llvm-svn

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL: 



[Bug 60879] [radeonsi] Tahiti LE: GFX block is not functional, CP is okay

2016-04-28 Thread bugzilla-dae...@freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=60879

--- Comment #149 from bhaallord at arcor.de ---
Are there any new information about this bug? I would like to use my GPU again.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL: 



[Bug 60879] [radeonsi] Tahiti LE: GFX block is not functional, CP is okay

2016-03-11 Thread bugzilla-dae...@freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=60879

Marek Olšák  changed:

   What|Removed |Added

Summary|[radeonsi] X11 can't start  |[radeonsi] Tahiti LE: GFX
   |with acceleration enabled   |block is not functional, CP
   ||is okay

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL: