https://bugs.freedesktop.org/show_bug.cgi?id=81644
--- Comment #148 from Gedalya ---
See https://code.google.com/p/chromium/issues/detail?id=404357
In my case it was definitely crashing with mesa 10.2. In all cases it seemed to
be triggered by chromium. Bug 85647 is talking about something that
https://bugs.freedesktop.org/show_bug.cgi?id=81644
Aaron B changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=81644
--- Comment #146 from Aaron B ---
Go figure after saying that, I maximized a youtube video and it died when on
radeon.dpm=0. So just...guess this can just die. -_-
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=81644
--- Comment #145 from Aaron B ---
I'm just going to end my comments here, if someone wants to know more like
asking me to test or testing a patch related, let me know.
With radeon.dpm=0, this crash is "fixed" and never happens at all, past 4
https://bugs.freedesktop.org/show_bug.cgi?id=81644
--- Comment #144 from Aaron B ---
Is it possible at all that the problem is related to using DDR3-1866 RAM? I
mean I'm trying to think of why you guys at AMD can't encounter it, while I
can't stay away from it. That is basically the only piece
https://bugs.freedesktop.org/show_bug.cgi?id=81644
--- Comment #143 from Aaron B ---
So, what to do with this bug report? Keep it open, and when you guys think it
may be fixed with a commit, just ask here? I just re-built Mesa with today's
commits, and it's just back to crashing like crazy. :)
https://bugs.freedesktop.org/show_bug.cgi?id=81644
--- Comment #142 from Alexandre Demers ---
(In reply to comment #141)
> If someone has a way to reliably reproduce the 'Packet0 not allowed!' error,
> please file a separate report for that. Or, if you know at least which
> process triggers it,
https://bugs.freedesktop.org/show_bug.cgi?id=81644
--- Comment #141 from Michel D?nzer ---
If someone has a way to reliably reproduce the 'Packet0 not allowed!' error,
please file a separate report for that. Or, if you know at least which process
triggers it, you can run that process with the
https://bugs.freedesktop.org/show_bug.cgi?id=81644
--- Comment #140 from Aaron B ---
I dunno, I've had all those bugs, and when I'm stable, none happen to my
knowldge. I think they're all same things, different ways of triggering. Or,
maybe we do have multiple bugs.
https://bugs.freedesktop.org/show_bug.cgi?id=81644
--- Comment #139 from Alexandre Demers ---
Created attachment 107099
--> https://bugs.freedesktop.org/attachment.cgi?id=107099=edit
Xorg log when it froze
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=81644
--- Comment #138 from Alexandre Demers ---
(In reply to comment #135)
> (In reply to comment #134)
> > I'd like to test disabling UVD. I'll dig in the kernel to report UVD as
> > disabled for SI for this test. This should narrow where we have to
https://bugs.freedesktop.org/show_bug.cgi?id=81644
--- Comment #137 from Aaron B ---
I'm gonna try with more DPM to make sure the combo of DPM and DMA isn't what is
causing it. I'm getting many more consistent crashes with Chrome. Also, seems
by bug report here is a dup of this one just posted
https://bugs.freedesktop.org/show_bug.cgi?id=81644
--- Comment #136 from Alex Deucher ---
(In reply to comment #131)
> I have just played a youtube video (coincidentally the youtube message from
> AMD's John Byrne regarding Catalyst!) and I have just checked that the
> following messages show up
https://bugs.freedesktop.org/show_bug.cgi?id=81644
--- Comment #135 from Christian K?nig ---
(In reply to comment #134)
> I'd like to test disabling UVD. I'll dig in the kernel to report UVD as
> disabled for SI for this test. This should narrow where we have to look for
> this bug.
Sometimes
https://bugs.freedesktop.org/show_bug.cgi?id=81644
--- Comment #134 from Alexandre Demers ---
I'd like to test disabling UVD. I'll dig in the kernel to report UVD as
disabled for SI for this test. This should narrow where we have to look for
this bug.
--
You are receiving this mail because:
https://bugs.freedesktop.org/show_bug.cgi?id=81644
--- Comment #133 from Grigori Goronzy ---
I'm not really sure the failing UVD resets are even related to the hangs. UVD
also sometimes fails to reset properly for me after the DMA block hangs. GPU
reset just isn't that reliable on SI right now
https://bugs.freedesktop.org/show_bug.cgi?id=81644
--- Comment #132 from Alexandre Demers ---
(In reply to comment #131)
> I have just played a youtube video (coincidentally the youtube message from
> AMD's John Byrne regarding Catalyst!) and I have just checked that the
> following messages
https://bugs.freedesktop.org/show_bug.cgi?id=81644
--- Comment #131 from Jos? Su?rez ---
I have just played a youtube video (coincidentally the youtube message from
AMD's John Byrne regarding Catalyst!) and I have just checked that the
following messages show up in the dmesg log:
[ 2053.298531]
https://bugs.freedesktop.org/show_bug.cgi?id=81644
--- Comment #130 from Jos? Su?rez ---
Oh, by the way, since I see UVD comments, just to be clear, I don't have GPU
acceleration enabled in Flash.
--
You are receiving this mail because:
You are the assignee for the bug.
-- next
https://bugs.freedesktop.org/show_bug.cgi?id=81644
--- Comment #129 from Aaron B ---
Didn't mention it last night, but in my logs were this in my system log were
messages about msc number being wrong, which we've seen before. But I also saw
a "Chromium segfault" error which I haven't seen
https://bugs.freedesktop.org/show_bug.cgi?id=81644
--- Comment #128 from Christian K?nig ---
(In reply to comment #127)
> Thank you Christian for your quick explanation. Can we suspect the problem
> to be withing the UVD code then if:
> - crashes are mostly happening when watching videos (flash
https://bugs.freedesktop.org/show_bug.cgi?id=81644
--- Comment #127 from Alexandre Demers ---
(In reply to comment #126)
> (In reply to comment #119)
> > Small question Alex Deucher or Christian may answer: is it normal ring 5 is
> > completely in a different GPU's memory address area?
> > [
https://bugs.freedesktop.org/show_bug.cgi?id=81644
--- Comment #126 from Christian K?nig ---
(In reply to comment #119)
> Small question Alex Deucher or Christian may answer: is it normal ring 5 is
> completely in a different GPU's memory address area?
> [9.353518] radeon :01:00.0: fence
https://bugs.freedesktop.org/show_bug.cgi?id=81644
--- Comment #125 from Jos? Su?rez ---
Created attachment 106947
--> https://bugs.freedesktop.org/attachment.cgi?id=106947=edit
X.org log
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part
https://bugs.freedesktop.org/show_bug.cgi?id=81644
--- Comment #124 from Jos? Su?rez ---
Just for an easier read:
Radeon HD 7870 GHZ Edition 2 GB
FX 8150 @ 3700 MHz
16 GB RAM
Linux 3.17-rc5, with mesa 10.4~git1409200730.4eb2bb compiled with llvm
3.6~svn217413 on Kubuntu 14.04 with all the
https://bugs.freedesktop.org/show_bug.cgi?id=81644
--- Comment #123 from Jos? Su?rez ---
(In reply to comment #122)
> Created attachment 106946 [details]
> Dmesg log
I am experiencing the same problem described in comment 116. I only use firefox
and I am getting hangs consistently whenever I
https://bugs.freedesktop.org/show_bug.cgi?id=81644
--- Comment #122 from Jos? Su?rez ---
Created attachment 106946
--> https://bugs.freedesktop.org/attachment.cgi?id=106946=edit
Dmesg log
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part
https://bugs.freedesktop.org/show_bug.cgi?id=81644
--- Comment #121 from Aaron B ---
Created attachment 106942
--> https://bugs.freedesktop.org/attachment.cgi?id=106942=edit
DPM Crash log/watch script output.
First log with that script, no markers needed as you can see in the log when
the DPM
https://bugs.freedesktop.org/show_bug.cgi?id=81644
--- Comment #120 from Aaron B ---
I don't know how much it'll help, but I have this running in the background to
try to see whatever causes it. It doesn't help much considering I don't have a
marker/way to input when the crash starts to happen,
https://bugs.freedesktop.org/show_bug.cgi?id=81644
--- Comment #119 from Alexandre Demers ---
Small question Alex Deucher or Christian may answer: is it normal ring 5 is
completely in a different GPU's memory address area?
[9.353518] radeon :01:00.0: fence driver on ring 0 use gpu addr
https://bugs.freedesktop.org/show_bug.cgi?id=81644
--- Comment #118 from Alexandre Demers ---
(In reply to comment #117)
> Well, I'm still on Chromium, and I've forced my GPU from the backlist,
> because if you don't then it doesn't use all accel so it should be okay.
> Anyways, I turned off DPM
https://bugs.freedesktop.org/show_bug.cgi?id=81644
--- Comment #117 from Aaron B ---
Well, I'm still on Chromium, and I've forced my GPU from the backlist, because
if you don't then it doesn't use all accel so it should be okay. Anyways, I
turned off DPM and have no crashing at all, Chromium
https://bugs.freedesktop.org/show_bug.cgi?id=81644
--- Comment #116 from Alexandre Demers ---
I've been reading the comments in fast forward, and I'm sure I'm hitting the
same bug.
For info, I'm using a 7950 on Arch 64. I'm running Xorg server 1.16.1. Mesa,
drm and ddx are all from the latest
https://bugs.freedesktop.org/show_bug.cgi?id=81644
--- Comment #115 from Aaron B ---
Haha, was it the SI power state ULV one? I was worried I accidentally posted in
that and this was a reply. No crashes so far, I'll report tomorrow if I have
any, but it seems stable with DPM off. But we'll
https://bugs.freedesktop.org/show_bug.cgi?id=81644
--- Comment #114 from Alexandre Demers ---
(In reply to comment #113)
> I commented out every "return ret;" of si_dpm_set_power_state() in si_dpm.c.
> After booting this modified kernel, I can confirm this is the only error
> reported in
https://bugs.freedesktop.org/show_bug.cgi?id=81644
--- Comment #113 from Alexandre Demers ---
I commented out every "return ret;" of si_dpm_set_power_state() in si_dpm.c.
After booting this modified kernel, I can confirm this is the only error
reported in si_dpm_set_power_state(): every other
https://bugs.freedesktop.org/show_bug.cgi?id=81644
--- Comment #112 from Aaron B ---
OKay, I'm testing it now. Can't game at any good framerate, but that is fine.
If I get no crashes here, does that mean the random crashes are from changes in
power state? It would make sense, sense most of the
https://bugs.freedesktop.org/show_bug.cgi?id=81644
--- Comment #111 from Alex Deucher ---
(In reply to comment #110)
> I found this post, stating some of the ASUS hardware comes PRE-OVERCLOCKED
> from the factory. Good chance this is the cause of my instability?
>
>
https://bugs.freedesktop.org/show_bug.cgi?id=81644
--- Comment #110 from Aaron B ---
I found this post, stating some of the ASUS hardware comes PRE-OVERCLOCKED from
the factory. Good chance this is the cause of my instability?
https://bugs.freedesktop.org/show_bug.cgi?id=81644
--- Comment #109 from Aaron B ---
Crashing still persists with -mtune=native and -march=native on my kernel and
mesa 64, and mesa 32 with LLVM 3.5 from Arch's repos. :c
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=81644
--- Comment #108 from Aaron B ---
I have seen the comment, once LLVM becomes unbroken, and GCC becomes unbroken,
and everything doesn't suck, I'll recompile it all. But right now, LLVM is
broken, and even when compiled, doesn't link right with
https://bugs.freedesktop.org/show_bug.cgi?id=81644
--- Comment #107 from smoki ---
@Aaron B
Can i suggest something to try if helps, because this bug geting very big,
unreproducable for some people and seems like goes nowhere... so if you build
your mesa, try to build it with -mtune=native
https://bugs.freedesktop.org/show_bug.cgi?id=81644
--- Comment #106 from Aaron B ---
LibreOffice triggers the bug much, much more than Chromium and VLC. Trying to
make a few work documents and update my resume, and it's just not doable.
--
You are receiving this mail because:
You are the
https://bugs.freedesktop.org/show_bug.cgi?id=81644
--- Comment #105 from Aaron B ---
Nobody reproducing this still? I just had another X dying when booting
up/starting to transfer GPU data in CSS for a map and I got a new error in
between other usuals:
r600_ring_test: *ERROR* Radeon: ring test
https://bugs.freedesktop.org/show_bug.cgi?id=81644
--- Comment #104 from Maciej ---
Easy way to reproduce (though takes some time) is watching any video using
mplayer with xv. After few minutes (or an hour) it will hang. Same goes for
flash videos, fire up 5 or 6 at once and in no time it should
https://bugs.freedesktop.org/show_bug.cgi?id=81644
--- Comment #103 from Aaron B ---
It seems the more often the build has this bug, the most it ALSO randomly has
"blank" and "garbled" frames. Every so often, the screen will shift, or
sometimes seem to just go completely blank. I notice in the
https://bugs.freedesktop.org/show_bug.cgi?id=81644
--- Comment #102 from Emil Velikov ---
(In reply to comment #101)
> Emil Velikov
>
> Not sure what difference would it make to file a bug at launchpad from where
> they will point me right here. Aren't all Mesa devs right here anyway? I'm
>
https://bugs.freedesktop.org/show_bug.cgi?id=81644
--- Comment #101 from Maciej ---
(In reply to comment #98)
> > If you want complete usability on your hardware, you should just go windows
> then, FWIW.
This here is where Linux desktop issues start - You people drive new users away
from this
https://bugs.freedesktop.org/show_bug.cgi?id=81644
--- Comment #100 from Aaron B ---
I also would like to note that, I just had 2 crashes. Chromium. So it still
exists, just seems to happen rarer and rarer for me.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=81644
--- Comment #99 from Emil Velikov ---
Maciej
Just a friendly note from a guy not involved with the radeon drivers or the AMD
team.
There is software development and distribution. As the latter differs greatly
it is somewhat unexpected for
https://bugs.freedesktop.org/show_bug.cgi?id=81644
--- Comment #98 from Aaron B ---
I'm giving you details on how to more help us, and if you can run Linux in any
way, and understand how the command line works even remotely, and how packages
work, going to a better system/learning one little
https://bugs.freedesktop.org/show_bug.cgi?id=81644
--- Comment #97 from Maciej ---
(In reply to comment #96)
> Just a while ago, I was the same way, sort. The main thing is to get away
> from the not-as-good package manager in Ubuntu, and go with Arch like I did.
> Package support is amazing
https://bugs.freedesktop.org/show_bug.cgi?id=81644
--- Comment #96 from Aaron B ---
Just a while ago, I was the same way, sort. The main thing is to get away from
the not-as-good package manager in Ubuntu, and go with Arch like I did. Package
support is amazing because of the AUR, which build
https://bugs.freedesktop.org/show_bug.cgi?id=81644
--- Comment #95 from Maciej ---
(In reply to comment #94)
> Maybe the crash actually happens because of glamor rendering - setting
> R600_DEBUG won't do anything in that case.
>
> Does this patch to Mesa make any difference?
>
>
https://bugs.freedesktop.org/show_bug.cgi?id=81644
--- Comment #94 from Grigori Goronzy ---
Maybe the crash actually happens because of glamor rendering - setting
R600_DEBUG won't do anything in that case.
Does this patch to Mesa make any difference?
https://bugs.freedesktop.org/show_bug.cgi?id=81644
--- Comment #93 from Maciej ---
(In reply to comment #91)
> I'm sorry to hear that. We're working on it, but since we haven't been able
> to reproduce these issues, we need your help for testing: Does the
> environment variable R600_DEBUG=nodma
https://bugs.freedesktop.org/show_bug.cgi?id=81644
--- Comment #92 from Aaron B ---
Like I said, I tried. But, it's too hard to reproduce. Unless you do it over a
2 week time span, it's so difficult to find. Maybe he could do it better since
his builds seem to crash more if it's completely
https://bugs.freedesktop.org/show_bug.cgi?id=81644
--- Comment #91 from Michel D?nzer ---
(In reply to comment #89)
> Could someone please fix this already? Mesa 10.2.x, 10.3-RC and git are
> simply unusable on 7770.
I'm sorry to hear that. We're working on it, but since we haven't been able to
https://bugs.freedesktop.org/show_bug.cgi?id=81644
--- Comment #90 from Aaron B ---
My testing has been delayed since they pushed LLVM 3.5 to stable on Arch, but
they changed one of the function's parameters. Then, 3.6 compiles perfectly for
64-bit, yet when compiling 32-bit, it fails to link.
https://bugs.freedesktop.org/show_bug.cgi?id=81644
--- Comment #89 from Maciej ---
Could someone please fix this already? Mesa 10.2.x, 10.3-RC and git are simply
unusable on 7770.
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
https://bugs.freedesktop.org/show_bug.cgi?id=81644
--- Comment #88 from Aaron B ---
(In reply to comment #87)
> (In reply to comment #86)
> > https://bugs.freedesktop.org/show_bug.cgi?id=83500
>
> I think in the meantime Grigori has seen GPU hangs even with that patch
> though, with 2D tiling.
https://bugs.freedesktop.org/show_bug.cgi?id=81644
--- Comment #87 from Michel D?nzer ---
(In reply to comment #86)
> https://bugs.freedesktop.org/show_bug.cgi?id=83500
I think in the meantime Grigori has seen GPU hangs even with that patch though,
with 2D tiling.
However, can you avoid the
https://bugs.freedesktop.org/show_bug.cgi?id=81644
--- Comment #86 from Aaron B ---
1 day since I compiled mesa with the 2nd patch here, all is well and stable.
https://bugs.freedesktop.org/show_bug.cgi?id=83500
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=81644
--- Comment #85 from Aaron B ---
I won't. I just am the typical programmer...it takes a while to trace it, but
why not just look for other broken stuff? Someone else has to have better
ability to do it and find what is causing it before I take a
https://bugs.freedesktop.org/show_bug.cgi?id=81644
--- Comment #84 from Cl?ment Gu?rin ---
Awesome work Aaron, don't give up!
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
https://bugs.freedesktop.org/show_bug.cgi?id=81644
--- Comment #83 from Aaron B ---
This bisect put me here, which looks like it didn't go as planned again...
http://cgit.freedesktop.org/mesa/mesa/commit/?id=78578b759943cb198d34eedc00b3408c1599f6ec
I'm going to give up for now, maybe when I
https://bugs.freedesktop.org/show_bug.cgi?id=81644
--- Comment #82 from Aaron B ---
I'm still bisecting, but I just want to say I suck at it and I'll probably need
at least 2 bisects to the same point, if not more. I'm trying to be patient,
but on the old Mesa's the glitch just takes so long to
https://bugs.freedesktop.org/show_bug.cgi?id=81644
--- Comment #81 from Michel D?nzer ---
(In reply to comment #80)
> Hmm, okay, I'll try again. I'll test for about 8 hours this time.
Thanks. Basically, you need to test for at least as long as it's ever taken for
the problem to appear. A
https://bugs.freedesktop.org/show_bug.cgi?id=81644
--- Comment #80 from Aaron B ---
(In reply to comment #79)
> Aaron, most likely the bisection didn't work because you marked commits as
> good which would have shown the problem after more testing. I'm afraid
> you'll have to test longer before
https://bugs.freedesktop.org/show_bug.cgi?id=81644
--- Comment #79 from Michel D?nzer ---
Aaron, most likely the bisection didn't work because you marked commits as good
which would have shown the problem after more testing. I'm afraid you'll have
to test longer before declaring a commit as
https://bugs.freedesktop.org/show_bug.cgi?id=81644
--- Comment #78 from Marek Ol??k ---
(In reply to comment #77)
> Took a few hours, but only one shot thankfully.
>
> first bad commit: [0e7b0f2a0ad3818d02907746a86568c264c97701] meta: Refactor
> binding of renderbuffer as texture image
>
>
https://bugs.freedesktop.org/show_bug.cgi?id=81644
--- Comment #77 from Aaron B ---
Took a few hours, but only one shot thankfully.
first bad commit: [0e7b0f2a0ad3818d02907746a86568c264c97701] meta: Refactor
binding of renderbuffer as texture image
https://bugs.freedesktop.org/show_bug.cgi?id=81644
--- Comment #76 from Aaron B ---
Ah, okay. Yeah, dropped to LLVM 3.4 and we're good to go. I'll report any
results I find interesting or believe may be problematic soon, along with my
bisect paths. I have 4 days off, so I'll probably be posting
https://bugs.freedesktop.org/show_bug.cgi?id=81644
--- Comment #75 from Michel D?nzer ---
(In reply to comment #72)
> Yeah, but I build it with yaourt, which likes to contain it's gits elsewhere
> and apparently deletes them every time as you can't keep a clone unless it's
> in the same session.
https://bugs.freedesktop.org/show_bug.cgi?id=81644
--- Comment #74 from Michel D?nzer ---
(In reply to comment #73)
> Could it be I'm using LLVM 3.6 [...]
Yes, only released versions of LLVM can be supported by released versions of
Mesa. Even LLVM 3.5 is only being released now, so you might
https://bugs.freedesktop.org/show_bug.cgi?id=81644
--- Comment #73 from Aaron B ---
I'm not having any luck bisecting, because I can't even get mesa-10.1.4 to
compile. I recompiled LLVM with R600 and everything, but still no dice. Could
it be I'm using LLVM 3.6 or should there be no functional
https://bugs.freedesktop.org/show_bug.cgi?id=81644
--- Comment #72 from Aaron B ---
(In reply to comment #71)
> (In reply to comment #70)
> > https://drive.google.com/file/d/0B1laUfqMuZQBeWpHSDYtV2N3RjQ/edit?usp=sharing
>
> Can you reproduce the crash by feeding those traces to glretrace?
>
>
https://bugs.freedesktop.org/show_bug.cgi?id=81644
--- Comment #71 from Michel D?nzer ---
(In reply to comment #70)
> https://drive.google.com/file/d/0B1laUfqMuZQBeWpHSDYtV2N3RjQ/edit?usp=sharing
Can you reproduce the crash by feeding those traces to glretrace?
(In reply to comment #69)
> If
https://bugs.freedesktop.org/show_bug.cgi?id=81644
--- Comment #70 from Aaron B ---
Wrong file. This is the right file:
https://drive.google.com/file/d/0B1laUfqMuZQBeWpHSDYtV2N3RjQ/edit?usp=sharing
--
You are receiving this mail because:
You are the assignee for the bug.
-- next
https://bugs.freedesktop.org/show_bug.cgi?id=81644
Aaron B changed:
What|Removed |Added
Attachment #105581|0 |1
is obsolete|
https://bugs.freedesktop.org/show_bug.cgi?id=81644
Aaron B changed:
What|Removed |Added
Attachment #105569|0 |1
is obsolete|
https://bugs.freedesktop.org/show_bug.cgi?id=81644
--- Comment #68 from Michel D?nzer ---
(In reply to comment #67)
> This what you're looking for?
No, we're looking for the /home/aaron/chromium.*.trace file generated by
apitrace corresponding to the crash.
BTW, can you try if Mesa 10.1 is
https://bugs.freedesktop.org/show_bug.cgi?id=81644
--- Comment #67 from Aaron B ---
Created attachment 105569
--> https://bugs.freedesktop.org/attachment.cgi?id=105569=edit
API trace of a crash.
> (In reply to comment #65)
> > I don't know what changed, if anything, but I did upgrade Chrome
https://bugs.freedesktop.org/show_bug.cgi?id=81644
--- Comment #66 from Christian K?nig ---
(In reply to comment #65)
> I don't know what changed, if anything, but I did upgrade Chrome about 3
> days ago, and now the past 2 days ever since I saw them mentioning more then
> 3-4 crashes a day, I'm
https://bugs.freedesktop.org/show_bug.cgi?id=81644
--- Comment #65 from Aaron B ---
I don't know what changed, if anything, but I did upgrade Chrome about 3 days
ago, and now the past 2 days ever since I saw them mentioning more then 3-4
crashes a day, I'm running into 15-20 crashes a day. I
https://bugs.freedesktop.org/show_bug.cgi?id=81644
--- Comment #64 from Christian K?nig ---
(In reply to comment #58)
> I would also like to add, if this happens three times in quick succession
> (Have chrome running with an OpenGL game starting/Level loading in a game)
> it'll sometimes have 3
https://bugs.freedesktop.org/show_bug.cgi?id=81644
--- Comment #63 from Michel D?nzer ---
(In reply to comment #61)
> tl;dr Mesa 10.1.4 is the last version that doesn't cause the problem.
If somebody could bisect that regression between Mesa 10.1 and 10.2, that would
be very helpful. See
https://bugs.freedesktop.org/show_bug.cgi?id=81644
Damian Nowak changed:
What|Removed |Added
CC||nowaker at geozone.pl
--- Comment #62
https://bugs.freedesktop.org/show_bug.cgi?id=81644
--- Comment #61 from Damian Nowak ---
My story: https://bugs.freedesktop.org/show_bug.cgi?id=65963#c4
tl;dr Mesa 10.1.4 is the last version that doesn't cause the problem.
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=81644
--- Comment #60 from Aaron B ---
I mean, if it helps, every crash is always during a situation where new
graphics information would be loaded up to the card, that can't me that much of
the Mesa code since I'd imagine the most complex part is all
https://bugs.freedesktop.org/show_bug.cgi?id=81644
--- Comment #59 from Aaron B ---
*Still active OB in VM"* Just had about 3 crashes in 2 hours. This is a joke of
a bug that it seems nobody cares, and probably affects all SI, and probably
R600 users.
--
You are receiving this mail because:
https://bugs.freedesktop.org/show_bug.cgi?id=81644
--- Comment #58 from Aaron B ---
I would also like to add, if this happens three times in quick succession (Have
chrome running with an OpenGL game starting/Level loading in a game) it'll
sometimes have 3 quick fail and recovers. If it does
https://bugs.freedesktop.org/show_bug.cgi?id=81644
--- Comment #57 from Maciej ---
Well, after a day the bug is back, so xserver update didn't help.
@Cl?ment Gu?rin - I have this bug on default Chrome, turning on HW just makes
it more frequent.
--
You are receiving this mail because:
You are
https://bugs.freedesktop.org/show_bug.cgi?id=81644
--- Comment #56 from Cl?ment Gu?rin ---
I had this bug because I forced hw acceleration ON in Chromium (about:flags).
Now that everything is set as default it's stable as rock. No crash in two
days, before that it was more like 5-6 crashes a
https://bugs.freedesktop.org/show_bug.cgi?id=81644
--- Comment #55 from Aaron B ---
1.16* Whoops, not talking the kernel.
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
https://bugs.freedesktop.org/show_bug.cgi?id=81644
--- Comment #54 from Aaron B ---
I'm on 3.16 and have been for a while, it definitely is still in there.
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was
https://bugs.freedesktop.org/show_bug.cgi?id=81644
--- Comment #53 from Maciej ---
I upgraded xserver from 1.15 to 1.16 today and it looks like issue is gone. I
even tried to reproduce the bug by running multiple flash instances and it
didn't hang. Can anyone confirm that this bug doesn't occur
https://bugs.freedesktop.org/show_bug.cgi?id=81644
--- Comment #52 from Aaron B ---
Nope, still having daily crashes with Chromium and VLC. Although I haven't been
able to build mesa 32 or 64 in a week because git always hangs at 99 damn
percent.
--
You are receiving this mail because:
You are
https://bugs.freedesktop.org/show_bug.cgi?id=81644
--- Comment #51 from Maciej ---
Any news? Mesa from 10.2 and up is still unusable on 7770.
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
https://bugs.freedesktop.org/show_bug.cgi?id=81644
--- Comment #50 from Michel D?nzer ---
(In reply to comment #49)
> I may have found a way to reliably trigger this bug. [...]
Please file your own report. In the unlikely case that it is indeed the same
bug as this report is about, it'll be
1 - 100 of 150 matches
Mail list logo
