[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110203185516.GA2560@schottelius.org>
Date: Thu, 3 Feb 2011 19:55:16 +0100
From: Nico Schottelius <nico-kernel-20110117@...ottelius.org>
To: Jesse Barnes <jbarnes@...tuousgeek.org>
Cc: "Rafael J. Wysocki" <rjw@...k.pl>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Kernel Testers List <kernel-testers@...r.kernel.org>,
Maciej Rutecki <maciej.rutecki@...il.com>,
Florian Mickler <florian@...kler.org>,
Nico Schottelius <nico-kernel-20110117@...ottelius.org>
Subject: Re: [Bug #28102] New display errors in 2.6.38-rc2-00175-g6fb1b30
Chris Wilson <chris@...is-wilson.co.uk>:
> This should hopefully find the culprit:
> $ git bisect start drivers/gpu/drm/i915/intel_display.c
> $ git bisect good v2.6.37
> $ git bisect bad
Just went that path, compiled 2.6.37-rc4-00292-g3c8cdf9
and suspended which resulted in a completly dead device
(no ping, no ctrlaltdel possible), i.e. different fatal situation.
I'm a bit confused, not sure whether this is related to
the broken display issue or not.
As the tests always cost a quite lengthy fsck run, I'd
love to go a different way from 2.6.37, if anybody has
a better hint.
Cheers,
Nico
--
PGP key: 7ED9 F7D3 6B10 81D7 0EC5 5C09 D7DC C8E4 3187 7DF0
--
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/
Powered by blists - more mailing lists