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:40:54 -0700 [thread overview]
Message-ID: <200709171240.55260.jbarnes@virtuousgeek.org> (raw)
In-Reply-To: <1190056703.2995.11.camel@chaos>
On Monday, September 17, 2007, Thomas Gleixner wrote:
> On Mon, 2007-09-17 at 12:13 -0700, Jesse Barnes wrote:
> > 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.
>
> Eeek, that sounds scary. Can you add "highres=off" as well ?
with nohz=off and highres=off I get a similar but not quite identical
hang: the mouse pointer still moves around but my desktop is still
hung and glxgears doesn't come up. Behavior is identical without boot
options and with highres=off however (i.e. lossy interrupts in both
cases).
Jesse
next prev parent reply other threads:[~2007-09-17 19:41 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
2007-09-17 19:18 ` Thomas Gleixner
2007-09-17 19:40 ` Jesse Barnes [this message]
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=200709171240.55260.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
Powered by JetHome