mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Randy Dunlap <randy.dunlap@oracle.com>, linux-kernel@vger.kernel.org
Subject: Re: Lossy interrupts on x86_64
Date: Mon, 17 Sep 2007 12:13:21 -0700	[thread overview]
Message-ID: <200709171213.21511.jbarnes@virtuousgeek.org> (raw)
In-Reply-To: <1189616795.4302.1.camel@chaos>

On Wednesday, September 12, 2007, Thomas Gleixner wrote:
> does it make any difference when you boot the box with:
>
> nohz=off
>
> on the kernel command line ?

Yeah, that makes a difference:  the box hangs when I start receiving 
vblank interrupts instead.  However it's not a hard hang, I think X 
just becomes unresponsive.  I can still hit the power button on the 
laptop and the machine shuts down gracefully, but ctl-alt-delete and 
ctl-alt-backspace don't work.  So X is probably still up and in charge 
of input but may not be getting any more timeslices or something.

So to summarize:

2.6.23-rc5:  works
2.6.23-0.171.rc5.git1.fc8 w/o boot options:  lossy interrupts
2.6.23-0.171.rc5.git1.fc8 nohz=off:  hang when starting 3d apps using
                                     vblank interrupts

Sorry it took so long for me to get back to you, I've been out of range 
for a few days...

Thanks,
Jesse

  reply	other threads:[~2007-09-17 19:14 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-12 15:33 Jesse Barnes
2007-09-12 16:01 ` Randy Dunlap
2007-09-12 16:29   ` Jesse Barnes
2007-09-12 17:06     ` Thomas Gleixner
2007-09-17 19:13       ` Jesse Barnes [this message]
2007-09-17 19:18         ` Thomas Gleixner
2007-09-17 19:40           ` Jesse Barnes
2007-09-20 19:22           ` Jesse Barnes
2007-09-20 19:50             ` Thomas Gleixner
2007-09-21  0:40               ` Jesse Barnes
2007-09-14 17:35     ` Chuck Ebbert
2007-09-13 13:40 ` Chris Snook
2007-09-17 19:24   ` Jesse Barnes

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=200709171213.21511.jbarnes@virtuousgeek.org \
    --to=jbarnes@virtuousgeek.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=randy.dunlap@oracle.com \
    --cc=tglx@linutronix.de \
    /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

all inboxes | Powered by JetHome®