public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alexander Zhaunerchyk <alex.vizor@gmail.com>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Kernel Testers List <kernel-testers@vger.kernel.org>,
	Maciej Rutecki <maciej.rutecki@gmail.com>,
	Florian Mickler <florian@mickler.org>
Subject: Re: [Bug #36452] Artifacts with 3.0-rc1 on SandyBridge
Date: Wed, 15 Jun 2011 21:59:41 +0300	[thread overview]
Message-ID: <4DF9011D.6050107@gmail.com> (raw)
In-Reply-To: <20110615114329.7429ff43@jbarnes-desktop>

I can't bisect. I tried to bisect other other bug but with some commits 
I can't even boot, kernel hangs in panic.

On 15.06.2011 21:43, Jesse Barnes wrote:
> On Sun, 12 Jun 2011 22:30:52 +0200 (CEST)
> "Rafael J. Wysocki"<rjw@sisk.pl>  wrote:
>
>> This message has been generated automatically as a part of a summary report
>> of recent regressions.
>>
>> The following bug entry is on the current list of known regressions
>> from 2.6.39.  Please verify if it still should be listed and let the tracking team
>> know (either way).
>>
>>
>> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=36452
>> Subject		: Artifacts with 3.0-rc1 on SandyBridge
>> Submitter	: Alex Zhavnerchik<alex.vizor@gmail.com>
>> Date		: 2011-06-01 13:55 (12 days old)
> Can you try bisecting this one?
>

  reply	other threads:[~2011-06-15 18:59 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-12 20:23 3.0-rc2: Reported regressions from 2.6.39 Rafael J. Wysocki
2011-06-12 20:23 ` [Bug #36302] SandyBridge can't do s2disk with linux 3.0-rc1 Rafael J. Wysocki
2011-06-12 20:30 ` [Bug #36452] Artifacts with 3.0-rc1 on SandyBridge Rafael J. Wysocki
2011-06-15 18:43   ` Jesse Barnes
2011-06-15 18:59     ` Alexander Zhaunerchyk [this message]
2011-06-15 21:15       ` Florian Mickler
2011-06-12 20:30 ` [Bug #36982] 3.0-rc1 problem with usb, cdrom Rafael J. Wysocki
2011-06-12 20:30 ` [Bug #36972] 3.0-rc1: DMAR errors from iwlagn Rafael J. Wysocki
2011-06-13 20:09   ` Jeremy Fitzhardinge
2011-06-13 21:21     ` Rafael J. Wysocki
2011-06-12 20:30 ` [Bug #37222] 3.0.0-rc1-git3 -- kernel/sched.c:619 invoked rcu_dereference_check() without protection! Rafael J. Wysocki
     [not found]   ` <BANLkTikjZ7O6SFmD2e-YnMztGHoGZL69qg@mail.gmail.com>
2011-06-13  2:00     ` Lin Ming
2011-06-13 17:26       ` Rafael J. Wysocki
2011-06-12 20:30 ` [Bug #37242] lockdep deadlock warning in shutdown Rafael J. Wysocki
2011-06-12 20:30 ` [Bug #37232] [3.0-rc1][NMI/DMAR][iwlagn] errors - PCI system error (SERR) for reason a1 on CPU 0 Rafael J. Wysocki
2011-06-19  2:34   ` Shawn Starr
2011-06-19 13:46     ` Rafael J. Wysocki
  -- strict thread matches above, loose matches on Subject: below --
2011-06-26 21:18 3.0-rc4: Reported regressions from 2.6.39 Rafael J. Wysocki
2011-06-26 21:23 ` [Bug #36452] Artifacts with 3.0-rc1 on SandyBridge Rafael J. Wysocki
2011-06-29 16:47   ` Jesse Barnes
2011-06-29 17:02     ` Alexander Zhaunerchyk
2011-06-29 19:28       ` Rafael J. Wysocki

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4DF9011D.6050107@gmail.com \
    --to=alex.vizor@gmail.com \
    --cc=florian@mickler.org \
    --cc=jbarnes@virtuousgeek.org \
    --cc=kernel-testers@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maciej.rutecki@gmail.com \
    --cc=rjw@sisk.pl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox