public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: kernel list <linux-kernel@vger.kernel.org>, mingo@redhat.com
Cc: Andrew Morton <akpm@osdl.org>
Subject: Re: 2.6.19-rc4-mm1: noidlehz problems
Date: Wed, 1 Nov 2006 13:55:06 +0100	[thread overview]
Message-ID: <20061101125506.GA2133@elf.ucw.cz> (raw)
In-Reply-To: <20061101122319.GA13056@elf.ucw.cz>

Hi!


> First, it would be nice if we had someone listed as a maintainer of
> noidlehz stuff...
> 
> Then... I'm getting strange messages from noidlehz each time I
> unplug/replug AC power (perhaps due to interrupt latency?).
> 
> Disabling NO_HZ and high resolution timers due to timer broadcasting
> (C3 stops local apic)
> Adding 987988k swap on /dev/sda1.  Priority:-1 extents:1
> across:987988k
> Disabling NO_HZ and high resolution timers due to timer broadcasting
> (C3 stops local apic)
> EXT2-fs warning (device sda2): ext2_fill_super: mounting ext3
> filesystem as ext2
...
> Disabling NO_HZ and high resolution timers due to timer broadcasting
> (C3 stops local apic)
> Disabling NO_HZ and high resolution timers due to timer broadcasting
> (C3 stops local apic)
> 
> ...I'd expect one such message, not many of them. Something seems
> seriously wrong there...
> 
> Plus, suspend to RAM and disk is broken in -rc4-mm1. Suspend to RAM
> dies with screaming speaker, suspend to disk returns but machine is
> mostly toast (and screaming, looks like timer problem, beeps never
> end). I'll disable NO_HZ and try again.

Disabling NO_HZ did not help, but I disabled high resolution timers,
and s2ram now works. s2disk also started working.
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2006-11-01 12:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-01 12:23 2.6.19-rc4-mm1: noidlehz problems Pavel Machek
2006-11-01 12:55 ` Pavel Machek [this message]
2006-11-01 13:02 ` Arjan van de Ven
2006-11-01 13:20   ` Pavel Machek
2006-11-01 15:22   ` Matthew Garrett
2006-11-01 20:55     ` Thomas Gleixner

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=20061101125506.GA2133@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.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