public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Alex Chiang <achiang@hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: lockdep support caused an MCA
Date: Thu, 14 Jan 2010 05:01:42 +0000	[thread overview]
Message-ID: <20100114050142.GE27766@ldl.fc.hp.com> (raw)
In-Reply-To: <20100111195825.GE10162@ldl.fc.hp.com>

* Luming Yu <luming.yu@gmail.com>:
> On Tue, Jan 12, 2010 at 9:51 AM, Yu, Luming <luming.yu@intel.com> wrote:
> > Let me check if I can get access to an HP rx8640 to re-spin the patch.
> >
> >
> > -----Original Message-----
> > From: Alex Chiang [mailto:achiang@hp.com]
> > Sent: Tuesday, January 12, 2010 3:58 AM
> > To: Yu, Luming; Luck, Tony
> > Cc: linux-ia64@vger.kernel.org
> > Subject: lockdep support caused an MCA
> >
> > This patch 2f02b4a12b24c9f077c6d739ac23c9b90840ccca:
> >
> > Author: Luming Yu <luming.yu@intel.com>  2009-12-04 09:14:30
> >
> >    [IA64] lockdep support
> >
> >    Basic functionality for lockdep on ia64.
> >
> >    Known issues:
> >    0. dynamic allocate per CPU area in lockdep.
> >    1. lock held in leave kernel.
> >    2. enabling CONFIG_DEBUG_LOCKDEP triggers the lockdep warning.
> >    3. Need to implement save_stack functions
> >    4. Replace some cpp macros with inline functions
> >    5. Add nmi_enter/nmi_exit
> >
> >    Signed-off-by: Bob Picco <bob.picco@hp.com>
> >    Signed-off-by: Yu Luming <luming.yu@intel.com>
> >    Signed-off-by: Tony Luck <tony.luck@intel.com>
> >
> > causes a very early MCA on an HP rx8640.
> >
> > Unfortunately, even with early_printk turned on, the machine
> > encounters the MCA and reboots before any output occurs, so I
> > don't have any further information.
> >
> > I haven't done any other triage on this as the patch has already
> > been dropped from Tony's tree, but I'd be happy to test the next
> > go-around.
> 
> I have managed to get the patch run on a HP rx8640 system with
> latest next tree + ia64-lockdep patch. The following is the part of
> boot log with lockdep footprints..The interesting thing is
> lockdep code seems to have detected possible recursive locking
> with the kernel on the platform.

How many cells was your system? Mine was 2 cells (for a total of
16 CPUs). I just mention this because booting on a 1 cell config
is quite different from a multi-cell config.

Thanks for getting it going though.

/ac


  parent reply	other threads:[~2010-01-14  5:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-11 19:58 lockdep support caused an MCA Alex Chiang
2010-01-12  1:51 ` Yu, Luming
2010-01-14  4:03 ` Luming Yu
2010-01-14  5:01 ` Alex Chiang [this message]
2010-01-14  5:15 ` Luming Yu

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=20100114050142.GE27766@ldl.fc.hp.com \
    --to=achiang@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