From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pekka Enberg Subject: Re: 2.6.33-rc2: Reported regressions from 2.6.32 Date: Sun, 17 Jan 2010 18:43:40 +0200 Message-ID: <84144f021001170843s67afae24oaabf09e9b13af8db@mail.gmail.com> References: <20100116174821.GA18306@redhat.com> <201001162257.16277.rjw@sisk.pl> <20100117123218.GA3182@redhat.com> <84144f021001170618g708a7c14ob1b222ab1cbdaa20@mail.gmail.com> <20100117161726.5752b181@schatten.dmk.lab> Mime-Version: 1.0 Return-path: DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to:cc :content-type; bh=0366UfD7OkBQq3XP1MSOqqOZ4fmKpb+MKx0+Yg3O4vw=; b=f2666TFp4wyBfgvppSf40ZkwNOj24s//HsSxvdggHvF1lixz82+2T6SjviTMzZ1gpu zv3tPECNsdsncxkkgBjkIcFOglY3jHdanpMZUSeYROsb3pSV93UyTr1/6zU3MAvEhnRi rno6M5NNbp8DuKla9RtfHwYCnYAZv+4y/QFko= In-Reply-To: <20100117161726.5752b181-mGsOIKOveelVRbCss4o9kg@public.gmane.org> Sender: kernel-testers-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-ID: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Florian Mickler Cc: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, kernel-testers-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Linus Torvalds , Jesse Barnes , "Michael S. Tsirkin" Hi Florian, (Please don't trim the cc list.) On Sun, Jan 17, 2010 at 5:17 PM, Florian Mickler wrote: > on which side of the merge? linus or drm? > i.e. it is to be expected to be before the merge, (but on the drm side) > so don't get confused... or did i misunderstood the situation? Like I said, don't read too much into the results but the current situation looks like the regression happened _after_ 2.6.32 but before any of the DRM code was merged to 2.6.33-rc1. I don't think that makes much sense which is why I'm back to testing 2.6.32 more to see if the bug is there already but just harder to trigger for whatever reason. Pekka From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754183Ab0AQQno (ORCPT ); Sun, 17 Jan 2010 11:43:44 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754073Ab0AQQnm (ORCPT ); Sun, 17 Jan 2010 11:43:42 -0500 Received: from mail-fx0-f225.google.com ([209.85.220.225]:48321 "EHLO mail-fx0-f225.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753747Ab0AQQnm (ORCPT ); Sun, 17 Jan 2010 11:43:42 -0500 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=fd1o1rtj5Xr1LljcicjJ8IQFLNoZpDgPFlpzELQeC/FAiIMRbT2WF5BzJCjJWBOC1V hMAmNTYblUg4uVzfjLXILl0IB5VXVGOQksVz01JTarfGx8dOIbNu2zaUIQgsFSaoY1JY wrmQorT7pwoq2MGYnk68Hj2gP7eTCtCuMftFY= MIME-Version: 1.0 In-Reply-To: <20100117161726.5752b181@schatten.dmk.lab> References: <20100116174821.GA18306@redhat.com> <201001162257.16277.rjw@sisk.pl> <20100117123218.GA3182@redhat.com> <84144f021001170618g708a7c14ob1b222ab1cbdaa20@mail.gmail.com> <20100117161726.5752b181@schatten.dmk.lab> Date: Sun, 17 Jan 2010 18:43:40 +0200 X-Google-Sender-Auth: fe053a0ee2590573 Message-ID: <84144f021001170843s67afae24oaabf09e9b13af8db@mail.gmail.com> Subject: Re: 2.6.33-rc2: Reported regressions from 2.6.32 From: Pekka Enberg To: Florian Mickler Cc: linux-kernel@vger.kernel.org, kernel-testers@vger.kernel.org, Linus Torvalds , Jesse Barnes , "Michael S. Tsirkin" Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Florian, (Please don't trim the cc list.) On Sun, Jan 17, 2010 at 5:17 PM, Florian Mickler wrote: > on which side of the merge? linus or drm? > i.e. it is to be expected to be before the merge, (but on the drm side) > so don't get confused... or did i misunderstood the situation? Like I said, don't read too much into the results but the current situation looks like the regression happened _after_ 2.6.32 but before any of the DRM code was merged to 2.6.33-rc1. I don't think that makes much sense which is why I'm back to testing 2.6.32 more to see if the bug is there already but just harder to trigger for whatever reason. Pekka