linux-kernel - Re: [Bug 10620] VT switching broken - X does not resume (intel chipset)

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

Message-Id: <1211265527.8773.8.camel@localhost>
Date:	Tue, 20 May 2008 08:38:47 +0200
From:	Romano Giannetti <romano.giannetti@...il.com>
To:	bugme-daemon@...zilla.kernel.org
Cc:	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [Bug 10620] VT switching broken - X does not resume (intel
	chipset)

On Mon, 2008-05-19 at 14:44 -0700, bugme-daemon@...zilla.kernel.org
wrote:
> Notice that git bisect accepts a path, so that it will only bisect between the
> commits that affect to a given path. If you are sure that it's a drm-related
> thing, you can try to do bisection on drivers/char/drm

I know. The problem was that I didn't know if this was due to the drm,
video, acpi or x86... so it seems that is quite restricted now.

To resume (see http://bugzilla.kernel.org/show_bug.cgi?id=10620 )

- VT switching is broken after gnome has started (acceleration?)

- the symptom is that the X VT stays black, which just the cursor (and
sometime some residual bit of the panel) shown.

- it happens almost all the time with suspend/resume

- sometime you can kill the X server with ctrl-alt-backspace, sometime
you have to reboot.

My (painful) bisect stopped here:

good 50704516f334d5036c09b0ecc0064598f7c5596f
bad  d9c04d678418fe42646de641f499209ca00fd94f

but then 2c14f28be2a3f2a2e9861b156d64fbe2bc7000c3 makes my laptop oops on boot.

Romano




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