From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 81644] Random crashes on RadeonSI with Chromium. Date: Sat, 27 Sep 2014 16:45:37 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0000328010==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 280916E268 for ; Sat, 27 Sep 2014 09:45:37 -0700 (PDT) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============0000328010== Content-Type: multipart/alternative; boundary="1411836337.c0eDE0B3.28985"; charset="us-ascii" --1411836337.c0eDE0B3.28985 Date: Sat, 27 Sep 2014 16:45:37 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" 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 before, but would explain why it crashes. It's probably it's fault for not bailing from a bad return gracefully, but maybe the return isn't NULL when it should be, anything is possible. Also interesting in DMesg: [ 8531.831921] radeon 0000:01:00.0: Packet0 not allowed! Is it broken in all of radeonsi, and not only hawaii? I haven't seen this before. This was 500 seconds before my screen died. Still, anything else I should log from DPM and such to try to find what screws up when? -- You are receiving this mail because: You are the assignee for the bug. --1411836337.c0eDE0B3.28985 Date: Sat, 27 Sep 2014 16:45:37 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8"

Comment # 129 on bug 81644 from 
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 before, but would explain why
it crashes. It's probably it's fault for not bailing from a bad return
gracefully, but maybe the return isn't NULL when it should be, anything is
possible.

Also interesting in DMesg:

[ 8531.831921] radeon 0000:01:00.0: Packet0 not allowed!

Is it broken in all of radeonsi, and not only hawaii? I haven't seen this
before. This was 500 seconds before my screen died.

Still, anything else I should log from DPM and such to try to find what screws
up when?

You are receiving this mail because:
  • You are the assignee for the bug.
--1411836337.c0eDE0B3.28985-- --===============0000328010== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel --===============0000328010==--