* Luming Yu <luming.yu@xxxxxxxxx>: > On Tue, Jan 12, 2010 at 9:51 AM, Yu, Luming <luming.yu@xxxxxxxxx> 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@xxxxxx] > > Sent: Tuesday, January 12, 2010 3:58 AM > > To: Yu, Luming; Luck, Tony > > Cc: linux-ia64@xxxxxxxxxxxxxxx > > Subject: lockdep support caused an MCA > > > > This patch 2f02b4a12b24c9f077c6d739ac23c9b90840ccca: > > > > Author: Luming Yu <luming.yu@xxxxxxxxx> 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@xxxxxx> > > Signed-off-by: Yu Luming <luming.yu@xxxxxxxxx> > > Signed-off-by: Tony Luck <tony.luck@xxxxxxxxx> > > > > 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 -- To unsubscribe from this list: send the line "unsubscribe linux-ia64" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
|