public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: David Mosberger <davidm@hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Re: Lockups on 2.4.1
Date: Wed, 21 Feb 2001 21:02:28 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590693005184@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590693005175@msgid-missing>

>>>>> On Wed, 21 Feb 2001 10:58:22 -0800, "Chris McDermott" <mcdermoc@us.ibm.com> said:

  Chris> Anyway, I have ITPs connected to the IBM hardware and have
  Chris> noticed that when the lockup occurs, and we lose video, at
  Chris> least one of the CPUs is executing in flush_tlb_no_ptcg() or
  Chris> handle_IPI(), in the 'do' loop where TLB entries are being
  Chris> purged. What I have observed is that the end address and the
  Chris> start address are in completely different regions. Usually,
  Chris> the start address is in region register 1 (address of
  Chris> 0x2000XXXXXXXXXXXX) and the end address is in region register
  Chris> 3 (address of 0x6000XXXXXXXXXXXX). I don't know if this is
  Chris> the same problem I am seeing on the Lion, but I plan to
  Chris> connect and ITP and a serial console (although we haven't
  Chris> been able to get one to work yet on the Lion with BIOS 71) to
  Chris> see if the symptoms are the same.

This is good info, thanks a lot!  flush_tlb_range() should *never* be
called with an address range that spans entire regions.  So this is
clearly the immediate problem.  The question is of course how it got
there.

I'm just a couple of hours away from hopping on a plane to
Switzerland, and won't be back till Tuesday and am currently busy
tracking down two Heisenbugs which are keeping me from releasing an
updated kernel diff. If someone investigates this some more until in
the meantime, please keep us all posted.

	--david


  parent reply	other threads:[~2001-02-21 21:02 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-21 16:05 [Linux-ia64] Re: Lockups on 2.4.1 Bill Nottingham
2001-02-21 17:16 ` Gerrit Huizenga
2001-02-21 17:57 ` David Mosberger
2001-02-21 18:58 ` Chris McDermott
2001-02-21 21:02 ` David Mosberger [this message]
2001-02-23 15:19 ` Jun Nakajima
2001-02-23 19:06 ` Seth, Rohit
2001-02-23 19:20 ` Michael Madore
2001-02-23 19:48 ` Seth, Rohit
2001-02-23 20:00 ` Jesse Barnes
2001-02-24 13:39 ` Francis Galiegue
2001-02-24 14:44 ` Francis Galiegue
2001-02-24 18:45 ` Michael Madore
2001-02-24 23:18 ` Joseph V Moss
2001-02-25  2:43 ` Francis Galiegue
2001-02-26 20:52 ` Jim Wilson
2001-03-07  3:51 ` [linux-ia64] " Tom King
2001-03-07 20:34 ` Jim Wilson
2001-03-08  3:45 ` Tom King

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=marc-linux-ia64-105590693005184@msgid-missing \
    --to=davidm@hpl.hp.com \
    --cc=linux-ia64@vger.kernel.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