[Bug 79980] Random radeonsi crashes

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=79980

Martin Peres  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |MOVED

--- Comment #240 from Martin Peres  ---
-- 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/drm/amd/issues/506.

-- 
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 79980] Random radeonsi crashes

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79980

--- Comment #239 from Marti Raudsepp  ---
(In reply to agapito from comment #238)
> I had this bug again :S 

There is no "this bug". Please report a separate bug for your exact
circumstances. This one is being ignored by developers because there are many
different causes.

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

[Bug 79980] Random radeonsi crashes

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79980

--- Comment #238 from agapito  ---
I had this bug again :S 

Using KDE 5, i had 2 crashes when i changed speed animation in systemsettings5
- screens and monitor - compositor options. 

My system is Archlinux 64 bits, kernel 3.19.3 and mesa 10.5.2. I can't report
any dmesg or log, my system completely freezes.

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

[Bug 79980] Random radeonsi crashes

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79980

--- Comment #237 from Marti Raudsepp  ---
(In reply to Tom Guder from comment #235)
> i get random freezes only in dota2. Other OpenGL applications run well.

Please report a separate bug for your exact circumstances. This one is being
ignored by developers because there are many different causes.

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

[Bug 79980] Random radeonsi crashes

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79980

--- Comment #236 from Tom Guder  ---
Same with kernel 3.14.35-1-lts. Dota2 crashes everytimes within one minute
spectating a game and freezes the screen and keyboard. Networking works.

Bests
Tom

[  129.619475] radeon :02:00.0: GPU fault detected: 147 0x000a4401
[  129.619479] radeon :02:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR  
0x0100
[  129.619480] radeon :02:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS
0x0A044001
[  129.619482] VM fault (0x01, vmid 5) at page 16777216, read from TC (68)
[  129.619484] radeon :02:00.0: GPU fault detected: 146 0x020a440c
[  129.619485] radeon :02:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR  
0x
[  129.619486] radeon :02:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS
0x

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

[Bug 79980] Random radeonsi crashes

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79980

--- Comment #235 from Tom Guder  ---
Hello,

i get random freezes only in dota2. Other OpenGL applications run well.
Archlinux, 3.18.6-1-ARCH #1 SMP PREEMPT Sat Feb 7 08:44:05 CET 2015 x86_64
GNU/Linux

[11008.894953] radeon :02:00.0: GPU fault detected: 147 0x000c4402
[11008.894956] radeon :02:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR  
0x0010
[11008.894958] radeon :02:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS
0x0C044002
[11008.894959] VM fault (0x02, vmid 6) at page 1048576, read from TC (68)
[11008.894961] radeon :02:00.0: GPU fault detected: 147 0x058c4801
[11008.894962] radeon :02:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR  
0x000AA85A
[11008.894963] radeon :02:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS
0x0C0C8002
[11008.894964] VM fault (0x02, vmid 6) at page 698458, read from TC (200)
[11019.062287] radeon :02:00.0: ring 4 stalled for more than 1msec
[11019.062291] radeon :02:00.0: GPU lockup (current fence id
0x00013609 last fence id 0x0001360a on ring 4)
[11019.062312] radeon :02:00.0: failed to get a new IB (-35)
[11019.062315] [drm:radeon_cs_ib_fill] *ERROR* Failed to get ib !
[11019.556350] radeon :02:00.0: Saved 780 dwords of commands on ring 0.
. 
. 
. 

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

[Bug 79980] Random radeonsi crashes

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79980

--- Comment #234 from Marti Raudsepp  ---
(In reply to Morgan Jones from comment #232)
> Same symptoms with a Hawaii device (R9 290X).

There are no "same symptoms" in this bug report, it's a mix of multiple
different symptoms and issues. Please report a new bug for your problem.

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

[Bug 79980] Random radeonsi crashes

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79980

--- Comment #233 from Morgan Jones  ---
Also, it's worth noting that my crashes are pretty reproducible when running
Chromium without --disable-gpu if compton is running. Disabled compton and
haven't had any so far.

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

[Bug 79980] Random radeonsi crashes

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79980

--- Comment #232 from Morgan Jones  ---
Same symptoms with a Hawaii device (R9 290X).

dmesg:

[20174.016203] Watchdog[15659]: segfault at 0 ip 7fa1902fbb0b sp
7fa17a6dd560 error 6 in chromium[7fa18c04+6497000]

lspci:

01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI]
Hawaii XT [Radeon R9 290X]

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

[Bug 79980] Random radeonsi crashes

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79980

--- Comment #231 from Marti Raudsepp  ---
(In reply to Liss from comment #230)
> Looks like I have similar issue with Radeon 8850M. I already filled bug
> 88364, but I'm not sure should I mark it as duplicate

(In reply to Andrew from comment #229)
> My dmesg output is similar to an attachments to this bug. Do I need to
> create a new bug in this case?

Please report all issues you have as separate bugs! This bug mixes together
multiple issues and symptoms, so it's almost useless.

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

[Bug 79980] Random radeonsi crashes

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79980

--- Comment #230 from Liss  ---
Looks like I have similar issue with Radeon 8850M. I already filled bug 88364,
but I'm not sure should I mark it as duplicate because I'm not sure that it is
same problem.

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

[Bug 79980] Random radeonsi crashes

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79980

--- Comment #229 from Andrew  ---
My dmesg output is similar to an attachments to this bug. Do I need to create a
new bug in this case?

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

[Bug 79980] Random radeonsi crashes

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79980

--- Comment #228 from Michel Dänzer  ---
(In reply to Andrew from comment #227)
> The monitor switches repeatedly: no signal/black screen/no signal/black
> screen/... In wine starcraft 2 with gallium nine 100% repeatability(7 of 7
> launches).

That's not a random crash but a reproducible one, probably a Mesa bug. Please
file a separate report for that.

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

[Bug 79980] Random radeonsi crashes

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79980

--- Comment #227 from Andrew  ---
The monitor switches repeatedly: no signal/black screen/no signal/black
screen/... In wine starcraft 2 with gallium nine 100% repeatability(7 of 7
launches). Sorry for my English.

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

[Bug 79980] Random radeonsi crashes

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79980

--- Comment #226 from Tilman Sauerbeck  ---
(In reply to Tilman Sauerbeck from comment #225)
> (In reply to Michel Dänzer from comment #223)
> 
> > For those still having problems, the kernel patches
> > http://lists.freedesktop.org/archives/dri-devel/2015-January/074968.html and
> > http://lists.freedesktop.org/archives/dri-devel/2015-January/074969.html
> > might be worth a try.
> 
> I applied
> http://lists.freedesktop.org/archives/dri-devel/2015-January/074969.html on
> top of kernel 3.18.4, and got:

Oops, I tested with 3.18.2 (the latest stable release as of today).

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

[Bug 79980] Random radeonsi crashes

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79980

--- Comment #225 from Tilman Sauerbeck  ---
(In reply to Michel Dänzer from comment #223)

> For those still having problems, the kernel patches
> http://lists.freedesktop.org/archives/dri-devel/2015-January/074968.html and
> http://lists.freedesktop.org/archives/dri-devel/2015-January/074969.html
> might be worth a try.

I applied
http://lists.freedesktop.org/archives/dri-devel/2015-January/074969.html on top
of kernel 3.18.4, and got:

radeon :01:00.0: GPU fault detected: 146 0x0008080c
radeon :01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x
radeon :01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0800800C
VM fault (0x0c, vmid 4) at page 0, read from 'TC0' (0x54433000) (8)

(following by an unsuccessful attempt to unwedge the GPU, but I guess the lines
above are what's really interesting).

This is with Mesa built from 8d2542fc9d5af4db355b67cc2a1ff2f413685a27 on a
bonaire xtx.

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

[Bug 79980] Random radeonsi crashes

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79980

--- Comment #224 from Gedalya  ---
Filed debian bug:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774784

Might need to file a separate bug for the linux package.

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

[Bug 79980] Random radeonsi crashes

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79980

--- Comment #223 from Michel Dänzer  ---
(In reply to fdb4c415 from comment #222)
> VM fault (0x04, vmid 1) at page 30481, read from DMA1 (61)
> 
> I have the latest debian test 64 bit installed:

There's a good chance that a newer upstream version of Mesa would help for your
problem, if not fix it completely.

For those still having problems, the kernel patches
http://lists.freedesktop.org/archives/dri-devel/2015-January/074968.html and
http://lists.freedesktop.org/archives/dri-devel/2015-January/074969.html might
be worth a try.

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

[Bug 79980] Random radeonsi crashes

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79980

--- Comment #222 from fdb4c415 at opayq.com ---
I would like to inform you I got the same problem. My box freezes randomly.
Keyboard is almost dead, mouse sometimes working (pointer moves, but cannot
click on anything) and usually I can only ssh into that box - to reboot it.
Sometimes Ctrl-Alt-F1 works and I can log in, but sometimes not. The monitor
switches repeatedly: no signal/black screen/no signal/black screen/...
In the log I can see quite similar messages:
radeon :01:00.0: GPU lockup (waiting for 0x2258 last fence id
0x2255 on ring 0)
VM fault (0x04, vmid 1) at page 30481, read from DMA1 (61)

I have the latest debian test 64 bit installed:
Linux  3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt2-1 (2014-12-08) x86_64
GNU/Linux
and I have:
VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde
PRO [Radeon HD 7750 / R7 250E]

Is there any way 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 79980] Random radeonsi crashes

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79980

--- Comment #221 from darkbasic  ---
Of course since 'radeonsi: Disable asynchronous DMA except for PIPE_BUFFER' the
vast majority of crashes disappeared.

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

[Bug 79980] Random radeonsi crashes

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79980

--- Comment #220 from agapito  ---
Since mesa 10.3.4 update i don't have this bug anymore on Archlinux. I've been
"stable" for more than two weeks.  

http://www.mesa3d.org/relnotes/10.3.4.html

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

[Bug 79980] Random radeonsi crashes

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79980

--- Comment #219 from Michel Dänzer  ---
Might be worth trying the Mesa patches I attached to bug 85647.

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

[Bug 79980] Random radeonsi crashes

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79980

--- Comment #218 from Sean Rhone  ---
Just a bit of feedback, but my 7850 seems relatively stable under Xubuntu 14.10
+ 3.18rc3 + Paulo's mesa PPA.

General desktop usage and web browsing over the past week resulted in no
crashes or GPU hangs, but I did have a slightly weird issue with fullscreened
flash video (while fullscreen once the player OSD disappears, moving the mouse
would freeze the video, but double-clicking it to un-fullscreen it was fine and
it played back normally).

Was watching a fullscreen video through Plex's web interface (I think videos
playback with HTML5?), I had a couple of GPU hangs (right term?) and restarts,
but they were really quick (black screen for about 2 seconds, then restore as
if nothing happened). If I recall right, there were about 2 or 3 hangs over a
37-minute period.

I'm using Google Chrome (not Chromium) 40.0.2202.3 dev (64-bit) with
--ignore-gpu-blacklist enabled. Just checking chrome:gpu, I noticed:

Log Messages
[2523:2523:1104/211347:ERROR:sandbox_linux.cc(301)] : InitializeSandbox()
called with multiple threads in process gpu-process
[2523:2523:1104/211636:WARNING:x11_util.cc(1490)] : X error received: serial
59083, error_code 3 (BadWindow (invalid Window parameter)), request_code 4,
minor_code 0 (X_DestroyWindow)
[2523:2523:1104/221802:ERROR:gpu_video_decode_accelerator.cc(299)] : Not
implemented reached in void
content::GpuVideoDecodeAccelerator::Initialize(const media::VideoCodecProfile,
IPC::Message *)HW video decode acceleration not available.
[2523:2529:1104/225251:ERROR:gpu_watchdog_thread.cc(253)] : The GPU process
hung. Terminating after 1 ms.
GpuProcessHostUIShim: The GPU process crashed!
GpuProcessHostUIShim: The GPU process crashed!

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

[Bug 79980] Random radeonsi crashes

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79980

Cilyan Olowen  changed:

   What|Removed |Added

 CC||gaknar at gmail.com

--- Comment #217 from Cilyan Olowen  ---
Created attachment 108795
  --> https://bugs.freedesktop.org/attachment.cgi?id=108795=edit
Last 300 lines of dmesg on a Radeon 6970

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

[Bug 79980] Random radeonsi crashes

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79980

--- Comment #216 from Cilyan Olowen  ---
Not sure if it is related, but I have the same log on dmesg while playing
Minecraft with Radeon 6970 (Northern Island, if I'm not mistaken). Linux
3.17.1, temp sensor around 57°C, not critical.

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

[Bug 79980] Random radeonsi crashes

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79980

--- Comment #215 from initzero at gmail.com ---
For me it's also Southern Islands related.
Up2date Archlinux + Oland: unstable
Up2date Archlinux + Kaveri: stable

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

[Bug 79980] Random radeonsi crashes

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79980

--- Comment #214 from Aaron B  ---
I'll duplicate my Bugs to Bug #85647 to start over, I KNOW I have that bug at
minimum. I'll  stay off of other "Random RadeonSI" crash reports until we
resole it there.

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

[Bug 79980] Random radeonsi crashes

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79980

--- Comment #213 from Michel Dänzer  ---
(In reply to Marti Raudsepp from comment #212)
> (In reply to Michel Dänzer from comment #210)
> > One thing I find interesting is that only Southern Islands seems affected.
> 
> And Pitcairn too.

Pitcairn is Southern Islands, just like Cape Verde and Tahiti.


> (In reply to Michel Dänzer from comment #207)
> > In general, it's much better to track things separately.
> 
> Should the two bugs resolved as "duplicate" be de-duplicated then? Bug 80141
> and Bug 82886.

I reopened 82886, but Aaron already has his own report (about Chromium, but it
may or may not turn out to be the same problem).

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

[Bug 79980] Random radeonsi crashes

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79980

--- Comment #212 from Marti Raudsepp  ---
(In reply to Jacob from comment #211)
> I looked back through kern.log and found the last time I encountered a
> crash, which happened to be with kernel 3.15.10 from the Ubuntu repo.
> That crash seemed to have been caused by dpm:
> [drm:si_dpm_set_power_state] *ERROR* si_set_sw_state failed

Jacob, please report a separate bug about your symptoms.

(In reply to Michel Dänzer from comment #210)
> One thing I find interesting is that only Southern Islands seems affected.

And Pitcairn too.

(In reply to Michel Dänzer from comment #207)
> In general, it's much better to
> track things separately.

Should the two bugs resolved as "duplicate" be de-duplicated then? Bug 80141
and Bug 82886.

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

[Bug 79980] Random radeonsi crashes

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79980

--- Comment #211 from Jacob  ---
I looked back through kern.log and found the last time I encountered a crash,
which happened to be with kernel 3.15.10 from the Ubuntu repo.
That crash seemed to have been caused by dpm:
[drm:si_dpm_set_power_state] *ERROR* si_set_sw_state failed

The 3.15.10 version isn't part of the source, so I instead looked through the
list of changes and found that the last set of changes made to drm, landed in
kernel 3.16-rc6.

So I installed the rc6 image and has now been running it for some time, but ran
into yet another issue, which is unrelated to this bug.

[ 6533.114483] alloc_contig_range test_pages_isolated(1bc800, 1bca8c) failed
[ 6533.114492] alloc_contig_range test_pages_isolated(1bc800, 1bca8d) failed
[ 6533.114500] alloc_contig_range test_pages_isolated(1bc800, 1bca8e) failed
[ 6533.114506] alloc_contig_range test_pages_isolated(1bc800, 1bca8f) failed
[ 6533.114511] alloc_contig_range test_pages_isolated(1bc800, 1bca90) failed
[ 6533.114516] alloc_contig_range test_pages_isolated(1bc800, 1bca91) failed
And so on.
It pretty much causes frequent 2-5 second hangs, even while I'm writing this
message. Just moving the cursor, causes such a hang. Changing workspace and the
hang lasts 40 seconds.
In other words, bisecting the dpm issue would be very difficult, since I would
more than likely run into this issue as well.

The last change made to drm/radeon/dpm were merged into 3.16-rc1, and it only
affect si hardware.

Suppose this issue could be moved to another bug entry, if it hasn't already
been fixed.

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

[Bug 79980] Random radeonsi crashes

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79980

--- Comment #210 from Michel Dänzer  ---
One thing I find interesting is that only Southern Islands seems affected. At
least I can't see any mentions of Bonaire, Kaveri, Kabini or Hawaii being
affected in this report or other related ones.

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

[Bug 79980] Random radeonsi crashes

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79980

--- Comment #209 from Michel Dänzer  ---
(In reply to Marti Raudsepp from comment #208)
> So *TELL* users that clearly, to make individual bug reports.

What do you think I'm doing what feels like every day? :}

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

[Bug 79980] Random radeonsi crashes

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79980

--- Comment #208 from Marti Raudsepp  ---
(In reply to Michel Dänzer from comment #207)
> In general, it's much better to
> track things separately. Once several unrelated issues are mixed up in a
> single report, it's very hard to untangle and keep track of it.

So *TELL* users that clearly, to make individual bug reports. Close this bug if
necessary. Direct your users instead of going "oh well, users can't report bugs
and we can't do anything about it".

When I was beginning to see these issues, I asked around in #radeon whether I
should report a new bug, and I was told to see this bug instead. Of course that
was another misled user.

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

[Bug 79980] Random radeonsi crashes

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79980

--- Comment #207 from Michel Dänzer  ---
(In reply to Marti Raudsepp from comment #194)
> Shouldn't it be up to the developers to try and make sense of the reports and
> split up the bug entry appropriately?

We are doing that all the time. However, users tend to focus too much on some
symptom(s) they have as well and ignore any differences. It's understandable,
but unfortunate.


> Should there be one report per affected user, or is there a better way to
> group them together?

I can't think of anything better than that. In general, it's much better to
track things separately. Once several unrelated issues are mixed up in a single
report, it's very hard to untangle and keep track of it.

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

[Bug 79980] Random radeonsi crashes

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79980

--- Comment #206 from Aaron B  ---
I believe Firefox and Chromium both suffer from the same issue myself, we've
been treating it that way at least, and Firefox users have never reported any
changes different with patches and updates, so I believe the same issue is
being talked about as with Chromium. I think it has to do with video being sent
to the GPU at all, which with RadeonSI and any modern browsers, any accelerated
browser probably will have the same problems.

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

[Bug 79980] Random radeonsi crashes

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79980

--- Comment #205 from agapito  ---
(In reply to Alex Deucher from comment #204)
> crash what do you mean?  Segfault?  System hang?  GPU hang?  GPU page fault?
> Something else?

My bug is not Chromium related. 4 months ago, my browser was Firefox and i had
the same bug. Always is the same behaviour. Sometimes with videos, or games,
flash content... It´s totally random.

I think it happens often when I click anywhere or i resize a windows with vdpau
content, then my system is freezed 5 seconds (I can move the mouse, but the
windows or programs are not responding) after 5 seconds, my screen shows
garbage like this:  https://bugs.freedesktop.org/attachment.cgi?id=101226  or
my monitor turns off completely. Sometimes i can reboot with reisub, sometimes
i need a hard reset. Some months ago i posted a picture of my dmesg output
https://bugs.freedesktop.org/attachment.cgi?id=104145

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

[Bug 79980] Random radeonsi crashes

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79980

--- Comment #204 from Alex Deucher  ---
(In reply to agapito from comment #203)
> (In reply to Jacob from comment #199)
> > (In reply to agapito from comment #198)
> > > 2 days without crashes... Now 2 crashes in 5 minutes. I will start using 
> > > my
> > > intel graphic card again.
> > 
> > Do you know what exactly you're doing when the crashes occur?
> 
> Yeah, on both occasions, I was trying to write a message in a forum.
> (Chromium)

If it's happens mostly with chromium, it may be bug 81644.  When you say crash
what do you mean?  Segfault?  System hang?  GPU hang?  GPU page fault? 
Something else?

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

[Bug 79980] Random radeonsi crashes

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79980

--- Comment #203 from agapito  ---
(In reply to Jacob from comment #199)
> (In reply to agapito from comment #198)
> > 2 days without crashes... Now 2 crashes in 5 minutes. I will start using my
> > intel graphic card again.
> 
> Do you know what exactly you're doing when the crashes occur?

Yeah, on both occasions, I was trying to write a message in a forum. (Chromium)

(In reply to farmboy0+freedesktop from comment #202)
> I am declaring kernel 3.18-rc2 preliminary stable for me again.
> My card is an HD 7750 Pro Cape Verde.
> I am using 3.18-rc2 with the lower-cased firmware for verde + TAHITI_uvd.
> Mesa and Llvm is from recent git.

I thought 3.18-rc2 was stable, but is not...

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

[Bug 79980] Random radeonsi crashes

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79980

--- Comment #202 from farmboy0+freedesktop at googlemail.com ---
I am declaring kernel 3.18-rc2 preliminary stable for me again.
My card is an HD 7750 Pro Cape Verde.
I am using 3.18-rc2 with the lower-cased firmware for verde + TAHITI_uvd.
Mesa and Llvm is from recent git.

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

[Bug 79980] Random radeonsi crashes

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79980

--- Comment #201 from Aaron B  ---
Not that it is very prominent, but I also plan on switching to a 780 Ti or
similar, if the AMD guys can show their management how many people are not only
going to hurt the company, but support the competition it might show AMD it's
worth it to get you guys more help over all.

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

[Bug 79980] Random radeonsi crashes

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79980

--- Comment #200 from darkbasic  ---
I had the very same behaviour with any 3.17+ kernel: sometimes it doesn't
crashes for days, others it crashes multiple times per minute. It doesn't
matter what you do, it just crashes (even starting your desktop environment is
enough sometimes).
I will probably buy a Nvidia GTX 970 while waiting for the new unified driver,
then I will try the open source path once again: hopefully having the
proprietary driver using the very same kernel code will force AMD to take
stability into higher consideration.

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

[Bug 79980] Random radeonsi crashes

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79980

--- Comment #199 from Jacob  ---
(In reply to agapito from comment #198)
> 2 days without crashes... Now 2 crashes in 5 minutes. I will start using my
> intel graphic card again.

Do you know what exactly you're doing when the crashes occur?

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

[Bug 79980] Random radeonsi crashes

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79980

--- Comment #198 from agapito  ---
2 days without crashes... Now 2 crashes in 5 minutes. I will start using my
intel graphic card again.

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

[Bug 79980] Random radeonsi crashes

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79980

--- Comment #197 from agapito  ---
After 2 days,3.18 rc2 crashed... Arggg this bug is crazy.

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

[Bug 79980] Random radeonsi crashes

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79980

--- Comment #196 from Alex Deucher  ---
There are other bug reports related to stability issues specifically with
chrome, firefox, and video playback in certain cases which may not be related. 
Those bugs may be better fits depending on the exact nature of the issue you
are seeing.

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

[Bug 79980] Random radeonsi crashes

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79980

--- Comment #195 from Aaron B  ---
Assuming my issue is separate, and your fixes were fixed, ever since my issue
was the only issue pertaining to random crashes, mostly by video players/web
browsers, it seemed the AMD guys never could reproduce it. After some time with
nobody else on the bug report, a few appeared with the same problem, and
reported the exact same results. Somewhere after that though, I think there
were more "Random crashes" bugs. I'd bet the ones who joined in a little later
have the same bug as me, the more current random crashes are probably not the
same though.

Maybe we should kill these reports, and make a couple with titles more
appropriate, funnel people there, and start over. :)

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

[Bug 79980] Random radeonsi crashes

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79980

--- Comment #194 from Marti Raudsepp  ---
(In reply to Alex Deucher from comment #193)
> Unfortunately, this bug has become a dumping ground for any kind of
> stability issue with radeonsi so I'm not really sure how useful it is
> anymore.  I suspect there are actually multiple issues that are now all
> mixed up.

What's the way forward? Shouldn't it be up to the developers to try and make
sense of the reports and split up the bug entry appropriately?

Should there be one report per affected user, or is there a better way to group
them together?

Christian König from comment #175 made one suggestion, is that what we should
be doing?
> In general you can split the issues into two categories one is with VM
> faults in the logs and the other ones are without.

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

[Bug 79980] Random radeonsi crashes

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79980

--- Comment #193 from Alex Deucher  ---
(In reply to Aaron B from comment #192)
> I guess it is possible there are many different crash types. I'm still
> crashing left and right. Is everyone else still stable? If so, looks like
> I'll leave you guys here alone to mark your problem fixedand find which
> one I need to be living in for bug reports again. :)

Unfortunately, this bug has become a dumping ground for any kind of stability
issue with radeonsi so I'm not really sure how useful it is anymore.  I suspect
there are actually multiple issues that are now all mixed up.

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

[Bug 79980] Random radeonsi crashes

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79980

--- Comment #192 from Aaron B  ---
I guess it is possible there are many different crash types. I'm still crashing
left and right. Is everyone else still stable? If so, looks like I'll leave you
guys here alone to mark your problem fixedand find which one I need to be
living in for bug reports again. :)

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

[Bug 79980] Random radeonsi crashes

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79980

--- Comment #191 from agapito  ---
3.17.1 still affected :S  I had a crash just 5 minutes ago. 

Well, i will use 3.18 rc2 because i didn't have any crash yet.

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

[Bug 79980] Random radeonsi crashes

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79980

--- Comment #190 from Daniel Kozak  ---
(In reply to agapito from comment #189)
> This is strange because 5 days ago i was starting to use intel graphic card
> because i had a lot of lock-ups with 3.17.1 and 3.18 rc1 kernels. When 3.18
> rc2 was launched i returned to radeon driver and this bug disappeared under
> 3.18 rc2, but now i am using 3.17.1 and it seems stable... Maybe this bug is
> a mesa problem, and not a kernel problem. Mesa 10.3.2 arrived to archlinux 3
> days ago.
> 
> Changes from 10.3.1 to 10.3.2:
> 
> Brian Paul (3):
>   mesa: fix spurious wglGetProcAddress / GL_INVALID_OPERATION error
>   st/wgl: add WINAPI qualifiers on wgl function typedefs
>   glsl: fix several use-after-free bugs
> 
> Daniel Manjarres (1):
>   glx: Fix glxUseXFont for glxWindow and glxPixmaps
> 
> Dave Airlie (1):
>   mesa: fix GetTexImage for 1D array depth textures
> 
> Emil Velikov (3):
>   docs: Add sha256 sums for the 10.3.1 release
>   Update VERSION to 10.3.2
>   Add release notes for the 10.3.2 release
> 
> Ilia Mirkin (4):
>   gm107/ir: add dnz emission for fmul
>   gk110/ir: add dnz flag emission for fmul/fmad
>   nouveau: 3d textures are unsupported, limit 3d levels to 1
>   st/gbm: fix order of arguments passed to is_format_supported
> 
> Kenneth Graunke (3):
>   i965: Add a BRW_MOCS_PTE #define.
>   i965: Use BDW_MOCS_PTE for renderbuffers.
>   i965: Fix register write checks.
> 
> Marek Olšák (2):
>   st/mesa: use pipe_sampler_view_release for releasing sampler views
>   glsl_to_tgsi: fix the value of gl_FrontFacing with native integers
> 
> Michel Dänzer (4):
>   radeonsi: Clear sampler view flags when binding a buffer
>   r600g,radeonsi: Always use GTT again for PIPE_USAGE_STREAM buffers
>   winsys/radeon: Use separate caching buffer manager for each set of
> flags
>   r600g: Drop references to destroyed blend state

I don't think so. I try tio downgrade mesa, linux-firmware and lots of other
packages, but even with vdpau vlc, html5 youtube videos or flash videos I am
unable to frozen my system again (I really try it hard all day). It must be
some HW problem or some wierd HW state or something completly different.

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

[Bug 79980] Random radeonsi crashes

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79980

--- Comment #189 from agapito  ---
This is strange because 5 days ago i was starting to use intel graphic card
because i had a lot of lock-ups with 3.17.1 and 3.18 rc1 kernels. When 3.18 rc2
was launched i returned to radeon driver and this bug disappeared under 3.18
rc2, but now i am using 3.17.1 and it seems stable... Maybe this bug is a mesa
problem, and not a kernel problem. Mesa 10.3.2 arrived to archlinux 3 days ago.

Changes from 10.3.1 to 10.3.2:

Brian Paul (3):
  mesa: fix spurious wglGetProcAddress / GL_INVALID_OPERATION error
  st/wgl: add WINAPI qualifiers on wgl function typedefs
  glsl: fix several use-after-free bugs

Daniel Manjarres (1):
  glx: Fix glxUseXFont for glxWindow and glxPixmaps

Dave Airlie (1):
  mesa: fix GetTexImage for 1D array depth textures

Emil Velikov (3):
  docs: Add sha256 sums for the 10.3.1 release
  Update VERSION to 10.3.2
  Add release notes for the 10.3.2 release

Ilia Mirkin (4):
  gm107/ir: add dnz emission for fmul
  gk110/ir: add dnz flag emission for fmul/fmad
  nouveau: 3d textures are unsupported, limit 3d levels to 1
  st/gbm: fix order of arguments passed to is_format_supported

Kenneth Graunke (3):
  i965: Add a BRW_MOCS_PTE #define.
  i965: Use BDW_MOCS_PTE for renderbuffers.
  i965: Fix register write checks.

Marek Olšák (2):
  st/mesa: use pipe_sampler_view_release for releasing sampler views
  glsl_to_tgsi: fix the value of gl_FrontFacing with native integers

Michel Dänzer (4):
  radeonsi: Clear sampler view flags when binding a buffer
  r600g,radeonsi: Always use GTT again for PIPE_USAGE_STREAM buffers
  winsys/radeon: Use separate caching buffer manager for each set of flags
  r600g: Drop references to destroyed blend state

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

[Bug 79980] Random radeonsi crashes

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79980

--- Comment #188 from Aaron B  ---
It's random for a reason, it acts like a buffer over run or leak or something
that isn't easily produced, as it changes how often it happens every installed
package. But I've had worse luck on 3.18-rc2, it's just my install is more
prone to it this build where it seems others haven't crashed yet, but give it
time. Make sure you run HTML5 youtube for an hour or so. ;) :)

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

[Bug 79980] Random radeonsi crashes

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79980

--- Comment #187 from Daniel Kozak  ---
After reinstall my arch workstation, I am unable to reproduce this issue
anymore. Even with same mesa, linux, and linux-firmware versions as before.

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

[Bug 79980] Random radeonsi crashes

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79980

--- Comment #186 from Jacob  ---
(In reply to agapito from comment #184)
> (In reply to Michel Dänzer from comment #182)
> > Can you bisect which commit in 3.18-rc2 fixed it for you?
> 
> Sorry, I do not know how to do it. But these are the changes between RC1
> (still crashing) and RC2 (stable):
> 
>  drm/radeon: reduce sparse false positive warnings
>  Revert "drm/radeon: drop btc_get_max_clock_from_voltage_dependency_table"
>  Revert "drm/radeon/dpm: drop clk/voltage dependency filters for SI"
>  drm/radeon: initialize sadb to NULL in the audio code
>  drm/radeon: fix speaker allocation setup
>  drm/radeon: use gart memory for DMA ring tests
>  drm/radeon: fix vm page table block size calculation
> 
> I am not an expert, but probably: drm/radeon: use gart memory for DMA ring
> tests; could be the good commit.
> 
> (In reply to Aaron B from comment #183)
> > 3.18 is still crashing for me, I doubt it is fixed.
> 
> rc2 crashed for you? After 24 hours I am still stable.

https://wiki.ubuntu.com/Kernel/KernelBisection
This guide helped me. Might help you too.

In short, you just have to clone the Linux repository, run "git bisect start
 ", then compile the kernel and test it.
If it crashes, then run "git bisect bad", and recompile.
If you think you've tested it long enough and the version is stable, then run
"git bisect good", and recompile.
Continue to do so until no revisions are left to be tested

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

[Bug 79980] Random radeonsi crashes

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79980

--- Comment #185 from Michel Dänzer  ---
(In reply to agapito from comment #184)
> > Can you bisect which commit in 3.18-rc2 fixed it for you?
> 
> Sorry, I do not know how to do it.

Search the web for 'git bisect howto'. One gotcha is that you'll need to run
'git bisect good' for bad kernels and vice versa, because git bisect can only
isolate good -> bad transitions.


> I am not an expert, but probably: drm/radeon: use gart memory for DMA ring
> tests; could be the good commit.

That should have no effect once the driver is initialized. None of the changes
between rc1 and rc2 seem like obvious candidates.

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

[Bug 79980] Random radeonsi crashes

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79980

--- Comment #184 from agapito  ---
(In reply to Michel Dänzer from comment #182)
> Can you bisect which commit in 3.18-rc2 fixed it for you?

Sorry, I do not know how to do it. But these are the changes between RC1 (still
crashing) and RC2 (stable):

 drm/radeon: reduce sparse false positive warnings
 Revert "drm/radeon: drop btc_get_max_clock_from_voltage_dependency_table"
 Revert "drm/radeon/dpm: drop clk/voltage dependency filters for SI"
 drm/radeon: initialize sadb to NULL in the audio code
 drm/radeon: fix speaker allocation setup
 drm/radeon: use gart memory for DMA ring tests
 drm/radeon: fix vm page table block size calculation

I am not an expert, but probably: drm/radeon: use gart memory for DMA ring
tests; could be the good commit.

(In reply to Aaron B from comment #183)
> 3.18 is still crashing for me, I doubt it is fixed.

rc2 crashed for you? After 24 hours I am still stable.

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

[Bug 79980] Random radeonsi crashes

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79980

--- Comment #183 from Aaron B  ---
3.18 is still crashing for me, I doubt it is fixed.

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

[Bug 79980] Random radeonsi crashes

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79980

--- Comment #182 from Michel Dänzer  ---
(In reply to Maximilian Böhm from comment #179)
> Just want to remind you that there is a Mesa connection somehow.

I've seen that mentioned before, but the answer is always the same: Please
bisect Mesa.


(In reply to agapito from comment #180)
> I know it's early to say this but 3.18 rc2 solved this bug for me.

Can you bisect which commit in 3.18-rc2 fixed it for you?

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

[Bug 79980] Random radeonsi crashes

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79980

--- Comment #181 from agapito  ---
After 5 hours i am still stable. I've played L4D2, unigine valley, watched
vdpau content, flash videos, Google Earth, chromium with a lot of tabs, kwin
effects...

HD7950 under Archlinux with 3.18 rc2 kernel and mesa 10.3.2

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

[Bug 79980] Random radeonsi crashes

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79980

--- Comment #180 from agapito  ---
I know it's early to say this but 3.18 rc2 solved this bug for me.

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

[Bug 79980] Random radeonsi crashes

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79980

--- Comment #179 from Maximilian Böhm  ---
Just want to remind you that there is a Mesa connection somehow. Either it's a
kernel call only later Mesa versions implement or it's a Mesa issue – I'm
stable for *months* now on Linux 3.16/3.17 and this downgraded packages on Arch
Linux with a Radeon HD 7770:
ati-dri-10.1.4-1-x86_64.pkg.tar.xz
clang-3.4.1-2-x86_64.pkg.tar.xz
lib32-llvm-libs-3.4.1-1-x86_64.pkg.tar.xz
lib32-mesa-10.1.4-1-x86_64.pkg.tar.xz
lib32-mesa-libgl-10.1.4-1-x86_64.pkg.tar.xz
llvm-3.4.1-2-x86_64.pkg.tar.xz
llvm-libs-3.4.1-2-x86_64.pkg.tar.xz
mesa-10.1.4-1-x86_64.pkg.tar.xz
mesa-demos-8.1.0-2-x86_64.pkg.tar.xz
mesa-libgl-10.1.4-1-x86_64.pkg.tar.xz

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

[Bug 79980] Random radeonsi crashes

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79980

--- Comment #178 from Jacob  ---
The "supposedly" random crashes I encountered with 3.15-rc3 weren't really
random at all. I came to a somewhat sad realization that only one application
actually crashed with it, so the bisection has mostly been a waste.

I've personally been stable on 3.14.20, and according to DJ Dunn, the issue has
now hit 3.14.22, so I'm gonna check 21 and 22 to see if it crashes for me as
well, and this time make sure it's application independent.

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

[Bug 79980] Random radeonsi crashes

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79980

--- Comment #177 from sam tygier  ---
Seeing this lock up on Debian Jessie when watching youtube HTML5 videos in
firefox.
kernel
Linux oberon 3.16-3-amd64 #1 SMP Debian 3.16.5-1 (2014-10-10) x86_64 GNU/Linux
Mesa 10.2.8-1
libdrm-radeon1 2.4.58-2
xserver-xorg-video-radeon 1:7.5.0-1
On a [AMD/ATI] Cape Verde PRO [Radeon HD 7750 / R7 250E]

I have logs which i can post, but it looks like you already have quite a few.

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

[Bug 79980] Random radeonsi crashes

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79980

--- Comment #176 from Jacob  ---
(In reply to Christian K?nig from comment #175)
> (In reply to Jacob from comment #174)
> > Considering the crash occurs within an hour or two on the last kernel, but
> > only occurs every few hours on 3.15, it makes you wonder if the two issues
> > are even related.
> > Nonetheless, I'll report the result from the bisection once I got it
> 
> Kernel 3.15 has some known VM issues which are only fixed in 3.16.
> Independent of that I think we indeed have multiple different issues that
> seems to be hard to distinct.
> 
> In general you can split the issues into two categories one is with VM
> faults in the logs and the other ones are without.

Seems the one I'm bisecting for now would be the one without then.
Whenever it crashes, I get nothing in the logs at all. Nothing in dmesg, in
xorg.log or in the kern.log. Nothing at all

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

[Bug 79980] Random radeonsi crashes

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79980

--- Comment #175 from Christian K?nig  ---
(In reply to Jacob from comment #174)
> Considering the crash occurs within an hour or two on the last kernel, but
> only occurs every few hours on 3.15, it makes you wonder if the two issues
> are even related.
> Nonetheless, I'll report the result from the bisection once I got it

Kernel 3.15 has some known VM issues which are only fixed in 3.16. Independent
of that I think we indeed have multiple different issues that seems to be hard
to distinct.

In general you can split the issues into two categories one is with VM faults
in the logs and the other ones are without.

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

[Bug 79980] Random radeonsi crashes

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79980

--- Comment #174 from Jacob  ---
Considering the crash occurs within an hour or two on the last kernel, but only
occurs every few hours on 3.15, it makes you wonder if the two issues are even
related.
Nonetheless, I'll report the result from the bisection once I got it

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

[Bug 79980] Random radeonsi crashes

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79980

--- Comment #173 from Jacob  ---
(In reply to darkbasic from comment #171)
> On my system with 3.17+ sometimes it takes days to crash while sometimes it
> crashes after a few minutes. Only 3.15 did *always* crash in a couple of
> minutes. I remember 3.15-rc1-pre didn't crash, so the bad commit should be
> somewhere around 3.15-rc0 and 3.15-rc2.

Takes about a couple hours for me to crash 3.15-rc3, "sadly" not minutes.
3.15-rc2 didn't crash on me,  so I'm currently doing a bisection

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

[Bug 79980] Random radeonsi crashes

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79980

--- Comment #172 from darkbasic  ---
Sorry I meant 3.15-rc0 and 3.15-rc*3*.

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

[Bug 79980] Random radeonsi crashes

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79980

--- Comment #171 from darkbasic  ---
On my system with 3.17+ sometimes it takes days to crash while sometimes it
crashes after a few minutes. Only 3.15 did *always* crash in a couple of
minutes. I remember 3.15-rc1-pre didn't crash, so the bad commit should be
somewhere around 3.15-rc0 and 3.15-rc2.

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

[Bug 79980] Random radeonsi crashes

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79980

--- Comment #170 from Jacob  ---
(In reply to DJ Dunn from comment #168)
> if this helps any, I've been seeing the same error on my gentoo box, its
> near constant on 3.16+ kernels within 2 or 3 min of loging in X but, ive
> been seeing it very rarely (once every few hours) on 3.14.22 but still
> seeing it, and I never seen it happen on 3.14.19
> 
> gentoo box with mesa-10.3.1 xorg-server-1.16.1

Could you test 3.14.20 and 3.14.21, to see if the issue also occur in any of
those, then do a bisection between the first version where the crashes started
to occur, and the version prior to it?

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

[Bug 79980] Random radeonsi crashes

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79980

--- Comment #169 from DJ Dunn  ---
my card is HD7870

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

[Bug 79980] Random radeonsi crashes

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79980

--- Comment #168 from DJ Dunn  ---
if this helps any, I've been seeing the same error on my gentoo box, its near
constant on 3.16+ kernels within 2 or 3 min of loging in X but, ive been seeing
it very rarely (once every few hours) on 3.14.22 but still seeing it, and I
never seen it happen on 3.14.19

gentoo box with mesa-10.3.1 xorg-server-1.16.1

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

[Bug 79980] Random radeonsi crashes

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79980

--- Comment #167 from agapito  ---
3.18 rc1 still affected.

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

[Bug 79980] Random radeonsi crashes

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79980

--- Comment #166 from Michel D?nzer  ---
(In reply to Jacob from comment #164)
> I ran a bisection between the two releases, and the result was the following:
> Bisecting: 120 revisions left to test after this (roughly 7 steps)

That's not the result but just an early step of the bisection. :) As the above
says, Git estimates that you'll need to test around 7 more kernels before there
is a result. BTW, make sure to only run 'bisect good' after you've tested a
kernel long enough to be sure it's not affected by the problem. If you mark a
commit as good which is actually bad, the bisection will fail.

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

[Bug 79980] Random radeonsi crashes

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79980

--- Comment #165 from Marti Raudsepp  ---
After upgrading to kernel 3.17.1, these GPU hangs/crashes still occur, but now
it doesn't hang the whole machine any more. Sometimes it recovers from the GPU
hang completely, sometimes it just drops me into a text console. Thanks, that's
an improvement.

I am using Radeon R9 270 on Arch Linux.

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

[Bug 79980] Random radeonsi crashes

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79980

--- Comment #164 from Jacob  ---
So after testing 3.15-rc2 for about 3 days without any crashes, I decided to
once again test 3.15-rc3 to see if it would crash on me again, which it did.
The OS just stopped responding to anything, then my monitors went black, just
like it has done for me on 3.16 and 3.17 as well.

I ran a bisection between the two releases, and the result was the following:
Bisecting: 120 revisions left to test after this (roughly 7 steps)
[3fe89d2e768792a924d3c1e9310ba0b4448cb78e] Merge tag 'fixes-3.15-rc3' of
git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc

Seems weird that arm got anything to do with this issue, but even after running
"git bisect bad" until the end, it doesn't pick out anything committed to
drm/radeon.
Nonetheless, I compiled the kernel, and I'll now test it to see if it'll crash
or not, then run git bisect bad until the kernel gets stable once again.

I'll report back if I either manage to compile a kernel which is stable, or if
I don't

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

[Bug 79980] Random radeonsi crashes

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79980

--- Comment #163 from Jacob  ---
(In reply to Michel D?nzer from comment #162)
> (In reply to Jacob from comment #161)
> > The last image I tried was 3.15-rc2, which didn't crash on me during
> > 18-hours of uptime
> 
> Can you try 3.15-rc2 again for even longer, to make sure it wasn't just luck?
> 
> If it's consistent, it would be really helpful if you could bisect between
> 3.15-rc2 and 3.15-rc3.

I'll do that; try rc2 for a couple days, see if I can get it to crash, then try
rc3 again to see if I can crash that again just for good measure, then do a
bisection between the two, if rc2 turns out to be stable and rc3 does not

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

[Bug 79980] Random radeonsi crashes

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79980

--- Comment #162 from Michel D?nzer  ---
(In reply to Jacob from comment #161)
> The last image I tried was 3.15-rc2, which didn't crash on me during
> 18-hours of uptime

Can you try 3.15-rc2 again for even longer, to make sure it wasn't just luck?

If it's consistent, it would be really helpful if you could bisect between
3.15-rc2 and 3.15-rc3.

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

[Bug 79980] Random radeonsi crashes

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79980

--- Comment #161 from Jacob  ---
(In reply to Michel D?nzer from comment #160)
> (In reply to Jacob from comment #153)
> > I've tried using different kernel versions the past few days and I've failed
> > to trigger the crash with any kernel prior to 3.15-rc3.
> 
> What was the closest earlier version you tried?

The last image I tried was 3.15-rc2, which didn't crash on me during 18-hours
of uptime

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

[Bug 79980] Random radeonsi crashes

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79980

--- Comment #160 from Michel D?nzer  ---
(In reply to Jacob from comment #153)
> I've tried using different kernel versions the past few days and I've failed
> to trigger the crash with any kernel prior to 3.15-rc3.

What was the closest earlier version you tried?

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

[Bug 79980] Random radeonsi crashes

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79980

--- Comment #159 from Malte Schr?der  ---
VDPAU doesn't make a difference, still crashes.

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

[Bug 79980] Random radeonsi crashes

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79980

--- Comment #158 from Malte Schr?der  ---
(In reply to agapito from comment #157)
> (In reply to Malte Schr?der from comment #156)
> >> I've set aspm=0 for the radeon module and the system has been running for
> > some hours straight.
> 
> Not for me.

Yeah, it just crashed on me again. So I was just lucky. I also tried disabling
dynclks and dpm, no effect. What I did differently yesterday is I had very
litte browser (Debian Iceweasel) usage. Today I had some Youtube running when
the crash happened. In fact the crashes happen most time when whatching stuff
on Youtube, i.e. when Iceweasel uses vdpau through gstreamer. I now removed
mesa vdpau drivers. I will report back if this changes anything.

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

[Bug 79980] Random radeonsi crashes

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79980

--- Comment #157 from agapito  ---
(In reply to Malte Schr?der from comment #156)
>> I've set aspm=0 for the radeon module and the system has been running for
> some hours straight.

Not for me.

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

[Bug 79980] Random radeonsi crashes

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79980

--- Comment #156 from Malte Schr?der  ---
Hi, with kernel v3.17 these crashes where much more frequent for me too. Now
I've set aspm=0 for the radeon module and the system has been running for some
hours straight.

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

[Bug 79980] Random radeonsi crashes

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79980

--- Comment #155 from agapito  ---
With kernel 3.16.5 i have this bug every 2 hours approximately. With kernel
3.17 every 20 minutes.

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

[Bug 79980] Random radeonsi crashes

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79980

--- Comment #154 from Jacob  ---
(In reply to agapito from comment #152)
> IMPORTANT
> 
> This was my first message in this bug report: 
> 
> I have the same problem with my HD 7950; using hangouts, playing Left for
> Dead 2, or watching a flash video my screen goes crazy with vertical lines
> or grey fog. Started when i upgraded to testing repo (Archlinux) and
> downloaded the newest linux-firmware package, who includes TAHITI_mc2.bin. I
> suffered this bug on kernels 3.14 and 3.15. 
> 
> --
> 
> In Archlinux i was stable with kernel 3.14, and the problem started when i
> was using the new firmware. I thought that the new firmware was the cause of
> this bug, but NO, because i had the same bug using the old firmare, so this
> bug it was caused by one of this radeon commits backported to kernel 3.14.6
> (the first kernel using newest firmware). I am 100% sure.
> 
> 
> https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/log/
> ?id=refs/tags/v3.14.21=1300

I've just compared the git messages from your link and from
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.15-rc3-utopic/CHANGES and it
seems like the commits made to drm/radeon, are the only commits these two
kernel versions have in common.
Only seven of them are part of 3.15-rc3, which crashed on me yesterday, so it
would seem like the crashes are caused by one of those commits

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

[Bug 79980] Random radeonsi crashes

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79980

--- Comment #153 from Jacob  ---
I've tried using different kernel versions the past few days and I've failed to
trigger the crash with any kernel prior to 3.15-rc3. Today after a few hours of
used, my system just locked up again and my screens went black, forcing me to
reboot the machine, same thing I've experienced with 3.16 and 3.17 so I believe
this is where the bug originated.
However, it seems like when I booted up, nothing has been written to kern.log
nor does any errors show up in xorg.log, and dmesg shows me nothing.
I got the image from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.15-rc3-utopic/ which also
shows what changes were made to this release.
The issue might have originated here, but it could very well be that I've
missed something.

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

[Bug 79980] Random radeonsi crashes

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79980

--- Comment #152 from agapito  ---
IMPORTANT

This was my first message in this bug report: 

I have the same problem with my HD 7950; using hangouts, playing Left for Dead
2, or watching a flash video my screen goes crazy with vertical lines or grey
fog. Started when i upgraded to testing repo (Archlinux) and downloaded the
newest linux-firmware package, who includes TAHITI_mc2.bin. I suffered this bug
on kernels 3.14 and 3.15. 

--

In Archlinux i was stable with kernel 3.14, and the problem started when i was
using the new firmware. I thought that the new firmware was the cause of this
bug, but NO, because i had the same bug using the old firmare, so this bug it
was caused by one of this radeon commits backported to kernel 3.14.6 (the first
kernel using newest firmware). I am 100% sure.


https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/log/?id=refs/tags/v3.14.21=1300

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

[Bug 79980] Random radeonsi crashes

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79980

--- Comment #151 from initzero at gmail.com ---
Same issues with my OLAND card here.
Archlinux, Mesa 10.3, Xorg 1.16.1 and Radeon 7.5.0.

Kernel 3.14.20 is still stable, 3.16.X and 3.17 may run for approx. 1hr and
finally crash during normal desktop usage (Gnome 3.14 + Browser + ...). Didn't
check 3.15 recently.

Sooner or later someone needs to bisect that sucker! :)

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

[Bug 79980] Random radeonsi crashes

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79980

--- Comment #150 from darkbasic  ---
3.14 is stable with my HD 7950 but some users reported they are stable only
with 3.13 (I don't remember their card)

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

[Bug 79980] Random radeonsi crashes

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79980

--- Comment #149 from mmstickman at gmail.com ---
Perhaps you should revert to 3.14 LTS until this issue is fixed. I don't have
any issues running 3.14 with my 7950.

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

[Bug 79980] Random radeonsi crashes

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79980

--- Comment #148 from darkbasic  ---
I just had to book my flight 3 times with HD 7950 because it loves crashing
when I use Chromium (plugins disabled).

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

[Bug 79980] Random radeonsi crashes

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79980

--- Comment #147 from mmstickman at gmail.com ---
I'm getting VM Faults within minutes of idling in i3wm now with my 7950 in
3.17. My AMD A4-5000 laptop is unaffected by these bugs, however.

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

[Bug 79980] Random radeonsi crashes

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79980

--- Comment #146 from Daniel Kozak  ---
I am able to reproduce, just start VLC with some video and wait. After some
secs or few minutes it happens

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

[Bug 79980] Random radeonsi crashes

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79980

--- Comment #145 from Daniel Kozak  ---
Same issue with my HD 7770 on 3.16 and 3.17 (much often). Even trying to write
this comment here cause crash. So I am unable to write more details on this pc,
because of time to crash is reali tiny :(

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

[Bug 79980] Random radeonsi crashes

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79980

--- Comment #144 from darkbasic  ---
Unfortunately it doesn't help, on the contrary I just got a new instability
world record: it crashed in *KDM*! Yes of course, I didn't even had time to
type my username!
I never checked GTX 970's price so often: one day or another I will find a good
offer and I will say goodbye to radeoncrash forever.

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

[Bug 79980] Random radeonsi crashes

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79980

--- Comment #143 from Edward  ---
(In reply to darkbasic from comment #140)
> Do you disable the onboard video in the bios or somewhere else?

In the bios. In my case (asrock z77 extreme6) I have to disable the entry "IGPU
Multi-Monitor"

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

[Bug 79980] Random radeonsi crashes

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79980

--- Comment #142 from Jacob  ---
(In reply to Michel D?nzer from comment #141)
> (In reply to Jacob from comment #137)
> > It seems to happen on any kernel newer than 3.13, least in my case.
> 
> Can you bisect which change between 3.13 and 3.14 caused the instability for
> you?

I've only downloaded kernel images as .deb files from
http://kernel.ubuntu.com/~kernel-ppa/mainline/
How would I go about bisecting which change caused the instability?

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

[Bug 79980] Random radeonsi crashes

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=79980

Michel D?nzer  changed:

   What|Removed |Added

 CC||jacobsvenningsen15 at hotmail.
   ||com

--- Comment #141 from Michel D?nzer  ---
(In reply to Jacob from comment #137)
> It seems to happen on any kernel newer than 3.13, least in my case.

Can you bisect which change between 3.13 and 3.14 caused the instability for
you?

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