From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758881AbZEaQMb (ORCPT ); Sun, 31 May 2009 12:12:31 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1756203AbZEaQMX (ORCPT ); Sun, 31 May 2009 12:12:23 -0400 Received: from silver.sucs.swan.ac.uk ([137.44.10.1]:42890 "EHLO silver.sucs.swan.ac.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755896AbZEaQMX (ORCPT ); Sun, 31 May 2009 12:12:23 -0400 Date: Sun, 31 May 2009 17:12:23 +0100 From: Sitsofe Wheeler To: "Rafael J. Wysocki" Cc: Linux Kernel Mailing List , Kernel Testers List , Dave Airlie , DRI , Jesse Barnes , Michel =?iso-8859-1?Q?D=E4nzer?= Subject: Re: [Bug #12765] i915 VT switch with AIGLX causes X lock up Message-ID: <20090531161222.GA4204@sucs.org> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.18 (2008-05-17) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, May 30, 2009 at 09:55:33PM +0200, Rafael J. Wysocki wrote: > This message has been generated automatically as a part of a report > of regressions introduced between 2.6.28 and 2.6.29. > > The following bug entry is on the current list of known regressions > introduced between 2.6.28 and 2.6.29. Please verify if it still should > be listed and let me know (either way). > > > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=12765 > Subject : i915 VT switch with AIGLX causes X lock up > Submitter : Sitsofe Wheeler > Date : 2009-02-21 15:38 (99 days old) > First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=14d200c5e5bd19219d930bbb9a5a22758c8f5bec > References : http://marc.info/?l=linux-kernel&m=123523074304955&w=4 > http://lkml.org/lkml/2009/4/27/317 > Handled-By : Jesse Barnes > Patch : http://patchwork.kernel.org/patch/20197/ Still here in 2.6.30-rc7-00149-g3218911. I have to admit that I thought commit 9b6fe313bfce27d4a261257da70196be0ac2bef5 might fix it but that doesn't appear to have been the case... -- Sitsofe | http://sucs.org/~sits/