linux-kernel - Re: 2.6.30-rc2 + xorg-intel-2.7.0 + DRM_I915

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] [thread-next>] [day] [month] [year] [list]

Message-ID:  <20090427234947.394f774f@schatten>
Date:	Mon, 27 Apr 2009 23:49:47 +0200
From:	Florian Mickler <florian@...kler.org>
To:	linux-kernel@...r.kernel.org
Cc:	xorg@...edesktop.org
Subject:  Re: 2.6.30-rc2 + xorg-intel-2.7.0 + DRM_I915_KMS = corruption

On Sun, 19 Apr 2009 07:27:35 +0100
Alex Bennee <kernel-hacker@...nee.com> wrote:

> Heading the warnings in the menuconfig I did try and ensure I have all
> the up to date parts of user-space. With KMS enabled GDM starts up but
> then corrupts the display with vertical lines. Disabling the kernel
> config and everything starts up fine, UXA acceleration seems OK and
> the speed of compiz is finally back up to ~60fps thanks to the A17
> fix.
> 
> Am I missing another bit of user space for KMS to work properly?
> 
> I am seeing a:
> 
> [    6.751092] BUG: using smp_processor_id() in preemptible [00000000]
> code: modprobe/3078
> [    6.751100] caller is smp_call_function_many+0x29/0x1bd
> [    6.751103] Pid: 3078, comm: modprobe Not tainted 2.6.30-rc2-ajb
> #56
> 
> But I think it's unrelated to any X woes. Shall detail in another
> message.
> 

hm, are you using the xf86-video-intel git-branch "2.7"? if i use that,
i need a kernel fix queued in eanholts for-linus git-tree or else i
also get unusable X. 

i assumed that this was because of some not-yet-released fixes
on the 2.7-branch which will get released as soon as erics queue is
merged? but i didn't double check ...  maybe the released version is
also broken in this regard for me....


--
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/