public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Frans Pop <elendil@planet.nl>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: linux-s390@vger.kernel.org,
	Hendrik Brueckner <brueckner@linux.vnet.ibm.com>,
	Ingo Molnar <mingo@elte.hu>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [BUG,2.6.29-rc7,s390] System goes into endless loop during boot or logon
Date: Mon, 9 Mar 2009 17:18:08 +0100	[thread overview]
Message-ID: <200903091718.10045.elendil@planet.nl> (raw)
In-Reply-To: <1236613902.8389.675.camel@laptop>

On Monday 09 March 2009, Peter Zijlstra wrote:
> > Hmmm. Your commit log message for
> > ca109491f612aab5c8152207631c0444f63da97f does explicitly mention the
> > risk of an infinite loop, as does a comment in
> > hrtimer_enqueue_reprogram().
> >
> > Any chance the cause is there? Any way to test for that?
>
> a6037b61c2f5fc99c57c15b26d7cfa58bbb34008 should have fixed the
> mentioned issue (along with the deadlock mentioned in the changelog).

OK. Thanks for explaining.

> Doesn't this s390 thing have a sysrq key you can press to get some
> traces out?

As mentioned in my first reply this morning, AFAIK I have no way to 
trigger the kernel's sysrq function.

The emulator does have an option to trace what's running on it. The 
problem is that I have no idea myself how to translate that output to 
what the kernel is doing, nor what would be needed to be able to do such 
a translation. If someone else does know how to use it, I'd be happy to 
provide the info.

Note that the last few days I've been tracing two other issues that 
appeared since 2.6.26 in the same environment, both of which are timing 
related. See:
- http://lkml.org/lkml/2009/3/9/112
  which fixes http://marc.info/?t=123629272600002&r=1&w=2
- http://lkml.org/lkml/2009/3/9/166

Hope that helps,
FJP

  reply	other threads:[~2009-03-09 16:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200903080835.14032.elendil@planet.nl>
     [not found] ` <200903080853.10704.elendil@planet.nl>
2009-03-09  1:53   ` [BUG,2.6.29-rc7,s390] System goes into endless loop during boot or logon Frans Pop
2009-03-09  8:25     ` Peter Zijlstra
2009-03-09  9:25       ` Frans Pop
2009-03-09  9:33         ` Hendrik Brueckner
2009-03-09  9:46           ` Frans Pop
2009-03-12 15:28         ` Jan Glauber
2009-03-12 14:46           ` Frans Pop
2009-03-12 18:35             ` Frans Pop
2009-03-09 15:43       ` Frans Pop
2009-03-09 15:51         ` Peter Zijlstra
2009-03-09 16:18           ` Frans Pop [this message]
2009-03-20 19:17     ` [BUG,2.6.29-rc7,s390] SOLVED -- " Frans Pop

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=200903091718.10045.elendil@planet.nl \
    --to=elendil@planet.nl \
    --cc=a.p.zijlstra@chello.nl \
    --cc=brueckner@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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