All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kai Krakow <hurikhan77@gmail.com>
To: intel-gfx@lists.freedesktop.org
Subject: system freeze with kernel 3.2-rc7
Date: Mon, 26 Dec 2011 01:43:37 +0100	[thread overview]
Message-ID: <jisks8-sbv.ln1@hurikhan.ath.cx> (raw)

Hello!

I found my system freeze mostly during starting up X and KDE. Sometimes it 
works for some minutes, sometimes it freezes immediatly. When the freeze 
happens, everything is dead (even the reset button does not work, I need to 
power cycle).

I was using libdrm-2.4.27 before, system freeze showed some colorful lines 
running down at the left side of the screen after turning black, then some 
blue flicker in the top 10% of the the screen. System no longer reacts, 
network is dead too.

Now, using libdrm-2.4.29, the system freeze shows other effects: Screen does 
not turn black but starts to flicker and occassionally moves some 
centimeters to the right (wrapping the right-most part to the left) for a 
very short time, then jumping back with some distortions. The rest is the 
same: Complete freeze, even reset button stops working.

Before finding out about the libdrm difference, I tried other intel xorg 
driver versions to no avail, I tried with SNA support and without. No 
difference. I'm now back to intel xorg driver 2.17.0.

I read about the semaphores feature, turned it off: No change. Sometimes the 
system even freezes before displaying the framebuffer splash.

I didn't have such issues with early 3.2 rcs (afair), and not with 3.1 
kernels. After some digging through google I've found you enabled RC6 in 
3.2. I disabled it now, and my system runs wonderfully.

Do you need any specs? I'd be happy to send these. The system is a Z68 Pro 
board with Sandybridge i5-2500K processor, 8 GB of RAM and UEFI firmware. 
Looks like RC6 is not ready for roll-out, at least on some mainboards.

Regards,
Kai

             reply	other threads:[~2011-12-26  0:50 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-26  0:43 Kai Krakow [this message]
2011-12-26  1:09 ` system freeze with kernel 3.2-rc7 Keith Packard
2011-12-26  2:43   ` Kai Krakow
2011-12-26  3:25     ` Keith Packard
2011-12-26 10:59       ` Kai Krakow
2011-12-27  0:54         ` Keith Packard
2011-12-27  3:18           ` Kai Krakow
2011-12-27  6:03             ` Keith Packard
2011-12-27 10:30           ` tino.keitel+xorg
2011-12-27 16:27           ` Tino Keitel
2011-12-28 21:36             ` Kevin
2011-12-30  1:13               ` Kevin
2012-01-02 13:18                 ` Eugeni Dodonov
2012-01-12 18:33 ` Ben Widawsky
2012-01-12 22:57   ` Kai Krakow
2012-01-13  4:04     ` Ben Widawsky

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=jisks8-sbv.ln1@hurikhan.ath.cx \
    --to=hurikhan77@gmail.com \
    --cc=intel-gfx@lists.freedesktop.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.