mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Maciej Piechotka <uzytkownik2@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: How to debug system hangs (bug #15737) on start of composite WM
Date: Tue, 21 Sep 2010 04:06:26 +0100	[thread overview]
Message-ID: <1285038386.3269.4.camel@localhost.localdomain> (raw)

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

I have problems debugging system hangs (bug #15737 -
https://bugzilla.kernel.org/show_bug.cgi?id=15737) which occur on
kernels >=2.6.33 (LTS i.e. 2.6.32 is not affected). 

I cannot manage to debug them especially it actual results evolve along
with changes in userspace (however 2.6.32 is not affected). On various
stages:

    - Second start of composite WM would be either hard hang or will fix
the system (i.e. problem will not be reproduced until next reboot - and
will not be reproduced after hibernation) - recently (for 2 weeks) false
    - First start of X will result in soft hang only - true except some
builds of 2.6.35 with relocatable kernel (???) and very old builds
(2.6.33)
    - Magic SysRQ key does not work on hard hang
    - If second start of WM was successful the DRI after some time will
report bad drawables. It is fixed by reboot - recent (for 2 weeks)
    - Switching to console and back helps (i.e. more often there is no
hang) - possibly voodoo magic but it may help
    - Error messages about failing to pinpoint buffor (cause?
side-effect?)
    - Running X in gdb hangs system (even if it is not on current VT)

Soft hang: X hangs but I can switch to console. Turning off X will stop
it but it takes some time (a minute?). There is nothing in logs (X,
dmesg, system...)
Hard hang: System is not responsive including network, X, sysrq etc.
This is not kernel panic (caps lock and num lock does not blink).

Someone (probably not kernel dev) suggested that it might be connected
with removing BKL.

I am really sorry for spamming but I run out of ideas how to debug this
problem.

Regards


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

                 reply	other threads:[~2010-09-21  3:06 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=1285038386.3269.4.camel@localhost.localdomain \
    --to=uzytkownik2@gmail.com \
    --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