All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Norbert Preining <preining@logic.at>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.26-rc2 hosed X?
Date: Tue, 13 May 2008 23:21:39 -0700	[thread overview]
Message-ID: <20080513232139.812a36dd.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080513103828.GA8288@gamma.logic.tuwien.ac.at>

On Tue, 13 May 2008 12:38:28 +0200 Norbert Preining <preining@logic.at> wrote:

> Hi all,
> 
> I usually follow the -rc series with skipping the -rc1 (waiting for the
> worst errors to be fixed).
> 
> Here now a severe regression with respect to 2.6.25: X seems to be hosed
> in the sense that:
> - switching to console
> - suspend 2 ram
> - suspend 2 disk
> often leaves the computer completely unusable.
> 
> I am using:
> - Debian/sid up2date, i.e. xorg server 7.3
> - intel Chipset 945GM (Acer laptop)
> - intel xorg video driver 2.2.1 and 2.3.1 (both tested)
> 
> Since not even Sysrq is working I cannot get a log file or whatsoever.
> 
> Is that something known, are is there some patch to revert/test?
> 

I'm not aware of anything, no.

First thing to do is to test a more recent kernel, see if we already
fixed it.  Latest mainline would be good.  linux-next would be better. 
2.6.26-rc2-mm1 (hopefully a couple of hours away) would be best.

If we haven't fixed it then I'm afraid our best shot would be for you
to run a bisection (please). 
http://www.kernel.org/doc/local/git-quick.html



  reply	other threads:[~2008-05-14  6:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-13 10:38 2.6.26-rc2 hosed X? Norbert Preining
2008-05-14  6:21 ` Andrew Morton [this message]
2008-05-14  6:23   ` Norbert Preining
2008-05-14  7:00 ` Dave Airlie
2008-05-14  7:06   ` Ingo Molnar
2008-05-14  7:28     ` Norbert Preining
2008-05-14  7:43       ` Norbert Preining
2008-05-20  7:44 ` Romano Giannetti
2008-05-20  8:16   ` Norbert Preining
2008-05-20  9:54     ` Romano Giannetti

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=20080513232139.812a36dd.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=preining@logic.at \
    /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.