All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kai Krakow <hurikhan77@gmail.com>
To: intel-gfx@lists.freedesktop.org
Subject: Re: system freeze with kernel 3.2-rc7
Date: Thu, 12 Jan 2012 23:57:40 +0100	[thread overview]
Message-ID: <1454u8-3sn.ln1@hurikhan.ath.cx> (raw)
In-Reply-To: 20120112183315.GA10370@bolo_yeung.jf.intel.com

Ben Widawsky <ben@bwidawsk.net> schrieb:

> On Mon, Dec 26, 2011 at 01:43:37AM +0100, Kai Krakow wrote:
>> 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).
[...]
> Can you please try this kernel:
> git://people.freedesktop.org/~bwidawsk/drm-intel context-support
> 
> You probably need to manually enable rc6. We were given some hint that
> we may not be setting up contexts properly. The above branch should
> create a default context (amongst other stuff which won't happen in this
> case).

Since that branch seems to be based off 3.2-rc6 I didn't need to enable RC6, 
it was on by default.

But I'm sorry to inform you that this still makes my system board freeze 
during KDE login, sometimes early, sometimes late during loading of the 
desktop.

My system freezes completely: Keyboard dead, SysRq shortcuts dead, screen 
goes blank (or shows funny lightshows before blanking), even the hard disk 
LED freezes. I need to power cycle to get back into a working state. If I 
only use the reset switch, the board behaves strange after reboot. The reset 
button sometimes takes a few seconds to make the system reboot when frozen.

All this tells me that something really bad goes on within the 
CPU/GPU/chipset during freeze which even survives a board reset. Only power 
cycling helps.

Keith got the specs of my system and wanted to "mirror" it for development. 
Maybe he could find out better what happens. I have no idea how to debug 
that because everything freezes so badly.

Regards,
Kai

  reply	other threads:[~2012-01-12 23:03 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-26  0:43 system freeze with kernel 3.2-rc7 Kai Krakow
2011-12-26  1:09 ` 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 [this message]
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=1454u8-3sn.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.