All of lore.kernel.org
 help / color / mirror / Atom feed
From: Romano Giannetti <romano.giannetti@gmail.com>
To: bugme-daemon@bugzilla.kernel.org
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [Bug 10620] VT switching broken - X does not resume (intel chipset)
Date: Tue, 20 May 2008 08:38:47 +0200	[thread overview]
Message-ID: <1211265527.8773.8.camel@localhost> (raw)
In-Reply-To: <20080519214445.BEE7E108062@picon.linux-foundation.org>

On Mon, 2008-05-19 at 14:44 -0700, bugme-daemon@bugzilla.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





           reply	other threads:[~2008-05-20  6:39 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20080519214445.BEE7E108062@picon.linux-foundation.org>]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1211265527.8773.8.camel@localhost \
    --to=romano.giannetti@gmail.com \
    --cc=bugme-daemon@bugzilla.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.