All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nico Schottelius <nico-kernel-20110117@schottelius.org>
To: Nico Schottelius <nico-kernel-20110117@schottelius.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: More display errors in 2.6.38-rc2-00175-g6fb1b30 (was 2.6.38-rc2-00175-g6fb1b30)
Date: Sun, 30 Jan 2011 11:32:41 +0100	[thread overview]
Message-ID: <20110130103241.GA26556@schottelius.org> (raw)
In-Reply-To: <20110128202905.GB3395@schottelius.org>

[-- Attachment #1: Type: text/plain, Size: 712 bytes --]

Nico Schottelius [Fri, Jan 28, 2011 at 09:29:05PM +0100]:
> With 2.6.38-rc2-00175-g6fb1b30 I get a new version of broken
> display I've never seen before: The display looks like a misconfigured
> tv after 2-3 suspends. Switching to a different tty was possible (though
> still same broken display, but allowed a reboot) one time, the other time 
> the system completly froze.


This time I can produce some logs, as only my primary notebook display
is completly broken, the external monitor is working fine.

Attached are xorg, dmesg + kernel config.

I've to emphasize that this used to work better in 2.6.37.

Cheers,

Nico

-- 
PGP key: 7ED9 F7D3 6B10 81D7 0EC5  5C09 D7DC C8E4 3187 7DF0

[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2011-01-30 10:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-28 20:29 New display errors in 2.6.38-rc2-00175-g6fb1b30 Nico Schottelius
2011-01-30 10:32 ` Nico Schottelius [this message]
2011-01-30 11:32   ` More display errors in 2.6.38-rc2-00175-g6fb1b30 (was 2.6.38-rc2-00175-g6fb1b30) Chris Wilson
2011-01-30 12:08     ` Nico Schottelius
2011-01-30 12:25       ` Chris Wilson
2011-02-02 20:28 ` New display errors in 2.6.38-rc2-00175-g6fb1b30 Maciej Rutecki

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=20110130103241.GA26556@schottelius.org \
    --to=nico-kernel-20110117@schottelius.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.