From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Pavel Machek <pavel@ucw.cz>
Cc: Mikael Pettersson <mikpe@it.uu.se>,
linux-kernel@vger.kernel.org, johnstul@us.ibm.com
Subject: Re: [BUG] APM resume breakage from 2.6.18-rc1 clocksource changes
Date: Sun, 09 Jul 2006 23:51:24 +0100 [thread overview]
Message-ID: <1152485484.27368.100.camel@localhost.localdomain> (raw)
In-Reply-To: <20060709214439.GC2495@elf.ucw.cz>
Ar Sul, 2006-07-09 am 23:44 +0200, ysgrifennodd Pavel Machek:
> Step 0: could we get some sanity checks into that loop? I'm pretty
> sure we'll face some TSCs going backwards... panic-king the box at
> that point is okay, but infinite loop is not...
If it goes backwards print a warning and carry on, a panic is as useless
for most users as a hang
next prev parent reply other threads:[~2006-07-09 22:34 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-09 20:58 [BUG] APM resume breakage from 2.6.18-rc1 clocksource changes Mikael Pettersson
2006-07-09 21:20 ` john stultz
2006-07-09 21:31 ` Valdis.Kletnieks
2006-07-09 21:44 ` Pavel Machek
2006-07-09 22:51 ` Alan Cox [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-07-09 23:52 Mikael Pettersson
2006-07-10 7:55 ` Pavel Machek
2006-07-10 17:58 ` john stultz
2006-07-10 18:08 ` Pavel Machek
2006-07-10 18:19 ` john stultz
2006-07-10 22:37 ` Roman Zippel
2006-07-10 22:50 ` john stultz
2006-07-10 22:59 ` Roman Zippel
2006-07-11 8:07 ` Thomas Gleixner
2006-07-11 9:29 ` Roman Zippel
2006-07-11 11:07 ` Thomas Gleixner
2006-07-11 23:31 ` Roman Zippel
2006-07-12 0:42 ` john stultz
2006-07-13 20:27 ` Thomas Gleixner
2006-07-13 22:05 ` john stultz
2006-07-14 6:56 ` Thomas Gleixner
2006-07-16 15:52 ` Roman Zippel
2006-07-16 15:50 ` Roman Zippel
2006-07-16 16:09 ` Thomas Gleixner
2006-07-16 16:15 ` Roman Zippel
2006-07-10 23:17 ` Pavel Machek
2006-07-09 23:53 Mikael Pettersson
2006-07-10 23:36 Mikael Pettersson
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=1152485484.27368.100.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@it.uu.se \
--cc=pavel@ucw.cz \
/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