Messages in this thread | | | Date | Mon, 28 Nov 2011 11:28:53 +0100 | Subject | Re: i915: 3.2 rc1/2 KMS regression | From | Patrik Kullman <> |
| |
Ok, so attached are:
3.1.rc6+.dmesg: dmesg from last working commit (before dc22ee6fc18ce0f15424e753e8473c306ece95c1) booted with drm.debug=4
3.2.rc3+.dmesg: dmesg from 3.2 rc3 with dc22ee6fc18ce0f15424e753e8473c306ece95c1 reverted, booted with drm.debug=4
2011/11/26 Patrik Kullman <patrik.kullman@gmail.com>: > 2011/11/26 Keith Packard <keithp@keithp.com>: >> On Sat, 26 Nov 2011 10:55:31 +0100, Patrik Kullman <patrik.kullman@gmail.com> wrote: >>> Well, booting the broken kernel freezes the machine unless I specify >>> i915.modeset=0. >> >> Freezes it so you can't even access it over the network? That would be >> quite surprising. > > As far as I can tell it does, Caps Lock doesn't respond, for example. > Also, the machine doesn't have an Ethernet port, the USB->Ethernet > adapter isn't supported in mainline kernel and I don't have a > convenient way to auto-logon to wireless. > > Hope we can do without this log? > >>> Do you want a log in that configuration? >> >> No, those wouldn't be useful (modeset=0 doesn't do a lot of >> modesetting :-) >> >>> I will provide the logs next week when I have my charger back... >> >> Thanks. >> >> -- >> keith.packard@intel.com >> > [unhandled content-type:application/octet-stream][unhandled content-type:application/octet-stream] | |