public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Max Krasnyansky <maxk@qualcomm.com>
To: Badari Pulavarty <pbadari@us.ibm.com>
Cc: Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org, hugh@veritas.com,
	Dave Airlie <airlied@linux.ie>
Subject: Re: 2.6.14 X spinning in the kernel
Date: Wed, 16 Nov 2005 13:07:56 -0800	[thread overview]
Message-ID: <437B9FAC.4090809@qualcomm.com> (raw)
In-Reply-To: <437A6609.4050803@us.ibm.com>

Badari Pulavarty wrote:
>> Badari Pulavarty <pbadari@us.ibm.com> wrote:
>>
>>> On Mon, 2005-11-14 at 16:17 -0800, Andrew Morton wrote:
>>>
>>>> Badari Pulavarty <pbadari@us.ibm.com> wrote:
>>>>
>>>>> My 2-cpu EM64T machine started showing this problem again on 2.6.14.
>>>>> On some reboots, X seems to spin in the kernel forever.
>>>>>
>>>>> sysrq-t output shows nothing.
>>>>>
>>>>> X             R  running task       0  3607   3589          3903
>>>>> (L-TLB)
>>>>>
>>>>> top shows:
>>>>> 3607 root      25   0     0    0    0 R 99.1  0.0 262:04.69 X
>>>>>
>>>>>
>>>>> So, I wrote a module to do smp_call_function() on all CPUs
>>>>> to show stacks on them. CPU0 seems to be spinning in exit_mmap().
>>>>> I did this multiple times to collect stacks few times.
>>>>>
>>>>> Is this a known issue ?

I've seen similar problems on dual Opteron HP xw9300/Radeon 7000 PCI box with 2.6.11.12
and latest X from Fedora x86-64 YUM repos.
I haven't done any traces but it sounds like the same problem (ie X server is spinning).
Disabling DRI in xorg.conf fixed it for me.

Max

  reply	other threads:[~2005-11-16 21:08 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-14 23:51 2.6.14 X spinning in the kernel Badari Pulavarty
2005-11-15  0:17 ` Andrew Morton
2005-11-15  0:52   ` Badari Pulavarty
2005-11-15  1:30     ` Andrew Morton
2005-11-15  2:48       ` Dave Airlie
2005-11-15  2:57         ` Andrew Morton
2005-11-15  3:02           ` Dave Airlie
2005-11-15 22:50         ` Badari Pulavarty
2005-11-15  3:10       ` Dave Jones
2005-11-15 22:49       ` Badari Pulavarty
2005-11-16 21:07         ` Max Krasnyansky [this message]
2005-11-16 21:52           ` Badari Pulavarty
2005-11-16 22:11             ` Lee Revell
2005-11-16 22:37               ` Badari Pulavarty
2005-11-16 22:42             ` Dave Airlie
2005-11-16 23:27               ` Badari Pulavarty
2005-11-17  0:10               ` Badari Pulavarty
2005-11-16 15:24 ` Pasi Savolainen

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=437B9FAC.4090809@qualcomm.com \
    --to=maxk@qualcomm.com \
    --cc=airlied@linux.ie \
    --cc=akpm@osdl.org \
    --cc=hugh@veritas.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbadari@us.ibm.com \
    /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