mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: lkml@Think-Future.de
To: Linux Kernel-Liste <linux-kernel@vger.kernel.org>
Subject: kernel/xserver-xorg: X crash while either idle or busy
Date: Thu, 18 Feb 2010 14:20:32 +0100	[thread overview]
Message-ID: <20100218132032.GE2165@localhost> (raw)

  Hi,

This bug report has been posted to the debian bugtracker for the
x-server-org deb package:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=570124

This link contains an extensive bug-report together with any relevant
information available.

The description is:

# Package: xserver-xorg
# Version: 1:7.5+2
# Severity: severe
# 
# Data loss guaranteed. While writing a book, X crashed, part of the book had
# to be re-written.
# 
# Whether using the system or not, X crashes semi-reproducibly. Be it after a 
# suspend-resume cycle or while just browsing the net, using openoffice writer, 
# doing nothing.. It just keeps crashing one day or the other. Mean times between
# crashing is from 2 hours to 2 days, sometimes more, sometimes less.
# 
# When the system crashes after opening the cover/lid it usually takes the whole kernel 
# down. Reboot only.
# 
# Less often but often enough, the crashing X just hangs, locking the
# system up. Reboot only.
# 
# This is occurring since january 2009 (switch-over to linux) over a variety of 
# kernel, kms, intel-drv and X versions. May well be different causes but 
# seems quite the same to us..
# 
# System is a rather usual ACER Extensa 5220 notebook.

A complete bug-report is available via the above link. 

The answer - among other ideas - was that if the kernel is 
hanging/freezing it is supposed to be reported to the lkml.

So posting here, fyi.

Thank you.

Nils


                 reply	other threads:[~2010-02-18 13:20 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20100218132032.GE2165@localhost \
    --to=lkml@think-future.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome