All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Mallick, Asit K" <asit.k.mallick@intel.com>
To: linux-ia64@vger.kernel.org
Subject: RE: [Linux-ia64] Kernel panic in dtlb_fault
Date: Wed, 10 Jan 2001 03:15:16 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590693005014@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590678205904@msgid-missing>

The TLB code got re-arranged a bit and I will take a look at why the
DISABLE_VHPT is not working.

Thanks,
Asit


> -----Original Message-----
> From: Uros Prestor [mailto:uros@turbolinux.com]
> Sent: Tuesday, January 09, 2001 4:41 PM
> To: davidm@hpl.hp.com
> Cc: linux-ia64@linuxia64.org
> Subject: Re: [Linux-ia64] Kernel panic in dtlb_fault
> 
> 
> David Mosberger wrote:
> 
> >   Uros> The IP points inside the dtlb_fault code.  Any ideas what's
> >   Uros> going on here?  The panic happens both with SMP and UP
> >   Uros> kernels.  I have disabled the VHPT (CONFIG_DISABLE_VHPT=y).
> >   Uros> Anything else I am missing?
> >
> > I don't think I tested the kernel with DISABLE_VHPT.
> 
> Enabling VHPT solved the problem.
> 
> Thanks,
> Uros
> 
> --
> Uros Prestor
> uros@turbolinux.com
> 
> 
> 
> 
> _______________________________________________
> Linux-IA64 mailing list
> Linux-IA64@linuxia64.org
> http://lists.linuxia64.org/lists/listinfo/linux-ia64
> 



  parent reply	other threads:[~2001-01-10  3:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-09 23:03 [Linux-ia64] Kernel panic in dtlb_fault Uros Prestor
2001-01-10  0:40 ` Uros Prestor
2001-01-10  3:15 ` Mallick, Asit K [this message]
2001-01-11  1:14 ` Mallick, Asit K
2001-01-11 19:09 ` Uros Prestor
2001-01-11 19:35 ` David Mosberger
2001-01-11 20:12 ` Uros Prestor
2001-01-11 20:23 ` Mallick, Asit K
2001-01-11 22:10 ` Mallick, Asit K
2001-01-12 19:36 ` Uros Prestor
2001-01-15 23:08 ` Mallick, Asit K

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-105590693005014@msgid-missing \
    --to=asit.k.mallick@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.