linux-kernel - Re: i915: 3.2 rc1/2 KMS regression

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: <CAGPN=9RY7h2MTat4pND=k2D6PWZEC5SFXdvOjs1sd89+1hoRVQ@mail.gmail.com>
Date:	Sat, 26 Nov 2011 10:58:11 +0100
From:	Patrik Kullman <patrik.kullman@...il.com>
To:	Keith Packard <keithp@...thp.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: i915: 3.2 rc1/2 KMS regression

Well, booting the broken kernel freezes the machine unless I specify
i915.modeset=0.Do you want a log in that configuration?
I will provide the logs next week when I have my charger back...
2011/11/25 Keith Packard <keithp@...thp.com>
>
> On Fri, 25 Nov 2011 18:29:31 +0100, Patrik Kullman <patrik.kullman@...il.com> wrote:
> > Ok, so I've now bisected, and it turns out that
> > dc22ee6fc18ce0f15424e753e8473c306ece95c1 is the first bad revision.
> >
> > Would it be safe to checkout 3.2-rc3 and git revert
> > dc22ee6fc18ce0f15424e753e8473c306ece95c1 (to test that it's the only
> > bad commit) ?
>
> Yes, that would be very useful. Please send kernel logs with drm.debug=4
> for an older working kernel, a broken kernel and a patched
> kernel with this commit reverted.
>
> --
> keith.packard@...el.com
--
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/