From: john stultz <johnstul@us.ibm.com>
To: Frans Pop <elendil@planet.nl>
Cc: linux-s390@vger.kernel.org, Roman Zippel <zippel@linux-m68k.org>,
Thomas Gleixner <tglx@linutronix.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [BUG,2.6.28,s390] Fails to boot in Hercules S/390 emulator
Date: Mon, 16 Mar 2009 22:15:01 -0700 [thread overview]
Message-ID: <1237266901.7306.86.camel@localhost.localdomain> (raw)
In-Reply-To: <200903120751.27821.elendil@planet.nl>
On Thu, 2009-03-12 at 07:51 +0100, Frans Pop wrote:
> On Thursday 12 March 2009, John Stultz wrote:
> > * Reverting both 6c9bacb41c10 and 5cd1c9c5cf30 against 2.6-git did not
> > seem to help the issue, as originally reported. I also reverted
> > 49b5cf34727a as well just in case, and it didn't help either.
>
> Hmm, interesting. I think you may have reproduced a similar failure case,
> but not exactly the same as mine. I wonder if what you have reproduced is
> the same as Debian bug report http://bugs.debian.org/511334. That is with
> 2.6.26 which would match the fact that the reverts that work reliably for
> me did not work for you. I've never had any problems with Debian's 2.6.26
> in my configuration.
Hmmm. I have indeed seen issues w/ the 2.6.26 debian kernel, so that
does seem closer to what I'm seeing.
> For me 2.6.28.7 is rock solid with the two reverts. I've attached my
> kernel config and my Hercules config. I think the critical thing in my
> config may be the "TIMERINT 500" setting for Hercules, which is somewhat
> similar to your "goes away if HZ is anything except 250" observation.
I'll have to checkout that option. Does changing HZ value or disabling
NO_HZ change anything for your situation as well?
> > That's about all I can get for today. I'm out of town until Monday, so
> > I'll start digging back into it then.
>
> From your other replies I've seen that I have been way off track at some
> points. It looks as if I have been looking at events too early in the
> boot and been confused by the use of clock->xtime_nsec. My apologies for
> any confusion caused by that.
>
> I have a few more tests I think I can usefully do, but will try harder not
> to confuse the issue with my inexpert ramblings anymore :-P
No, no, this is subtle and optimized code that keeps very high precision
values. Its not trivial stuff, so your confusion is understandable.
thanks
-john
next prev parent reply other threads:[~2009-03-17 5:15 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-08 1:30 [BUG,2.6.28,s390] Fails to boot in Hercules S/390 emulator Frans Pop
2009-03-08 7:21 ` Frans Pop
2009-03-09 15:04 ` Frans Pop
2009-03-11 1:00 ` john stultz
2009-03-11 9:00 ` Frans Pop
2009-03-11 16:03 ` Frans Pop
2009-03-11 17:05 ` Frans Pop
2009-03-11 19:05 ` Frans Pop
2009-03-12 0:34 ` john stultz
2009-03-12 4:47 ` john stultz
2009-03-12 6:51 ` Frans Pop
2009-03-17 5:15 ` john stultz [this message]
2009-03-17 14:39 ` Frans Pop
2009-03-12 0:30 ` john stultz
2009-03-12 0:47 ` john stultz
2009-03-12 1:30 ` Thomas Gleixner
2009-03-12 1:57 ` john stultz
2009-03-12 7:50 ` Thomas Gleixner
2009-03-12 17:05 ` [BUG,2.6.28,s390] Fails to boot in Hercules S/390 emulator - hang traced Frans Pop
2009-03-13 11:48 ` Frans Pop
2009-03-13 17:34 ` Frans Pop
2009-03-17 5:09 ` john stultz
2009-03-18 2:26 ` john stultz
2009-03-18 2:54 ` john stultz
2009-03-18 9:28 ` Martin Schwidefsky
2009-03-18 12:07 ` Frans Pop
2009-03-18 15:48 ` John Stultz
2009-03-23 0:11 ` Frans Pop
2009-03-23 22:19 ` John Stultz
2009-03-24 8:23 ` Martin Schwidefsky
2009-04-14 22:27 ` [PATCH] Avoid possible endless loop when using jiffies clocksource and ONESHOT mode clockevent john stultz
2009-03-18 15:39 ` [BUG,2.6.28,s390] Fails to boot in Hercules S/390 emulator - hang traced John Stultz
2009-03-10 3:09 ` [BUG,2.6.28,s390] Fails to boot in Hercules S/390 emulator John Stultz
2009-03-10 3:37 ` Frans Pop
2009-03-10 3:38 ` John Stultz
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=1237266901.7306.86.camel@localhost.localdomain \
--to=johnstul@us.ibm.com \
--cc=elendil@planet.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=zippel@linux-m68k.org \
/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