linux-kernel - RE: [REGRESSION] Radeon (Evergreen) Crash with "pin failed" in Kernel 3.10-rc7

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <A3397C8B8B789E45844E7EC5DEAD89D02E5005D8@sausexdag04.amd.com>
Date:	Mon, 1 Jul 2013 12:55:06 +0000
From:	"Deucher, Alexander" <Alexander.Deucher@....com>
To:	Brian Gitonga Marete <marete@...hnix.com>
CC:	LKML <linux-kernel@...r.kernel.org>,
	David Airlie <airlied@...ux.ie>,
	Jerome Glisse <jglisse@...hat.com>
Subject: RE: [REGRESSION] Radeon (Evergreen) Crash with "pin failed" in
 Kernel 3.10-rc7

> -----Original Message-----
> From: Brian Gitonga Marete [mailto:marete@...hnix.com]
> Sent: Saturday, June 29, 2013 3:41 PM
> To: Deucher, Alexander
> Cc: LKML; David Airlie; Jerome Glisse
> Subject: Re: [REGRESSION] Radeon (Evergreen) Crash with "pin failed" in
> Kernel 3.10-rc7
> 
> On Fri, Jun 28, 2013 at 6:45 PM, Brian Gitonga Marete
> <marete@...hnix.com> wrote:
> > On Fri, Jun 28, 2013 at 3:55 PM, Deucher, Alexander
> > <Alexander.Deucher@....com> wrote:
> >>
> >> Can you bisect?
> >>
> >
> 
> Hello Alexander,
> 
> So, it turns out that it is not so easy to reproduce this issue. I
> have been trying to reproduce it with the exact revision of 3.10-rc7
> where I first encountered the problem but with no luck. This of course
> has hampered my bisection since I cannot be sure which revisions to
> mark good/bad. Do you have any suggestions in this regard?
> 
> I however have a UVD-related lockup that I can always reproduce on
> 3.10-rc7: Trying to use UVD with the command: "mplayer -vo vdpau -vc
> ffh264vdpau test.mp4" _always_locks up the same system (same kernel,
> same DRI stack) hard. I will report this in a separate email, though
> nothing at all shows up in the logs for this latter problem due to the
> hard lockup. Suggestions about how to help debug this are also
> welcome.

Please open a bug (https://bugs.freedesktop.org) and attach your xorg log and dmesg output.

Alex


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/