Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757783AbYHHNpG (ORCPT ); Fri, 8 Aug 2008 09:45:06 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753780AbYHHNot (ORCPT ); Fri, 8 Aug 2008 09:44:49 -0400 Received: from 166-70-238-42.ip.xmission.com ([166.70.238.42]:54773 "EHLO ns1.wolfmountaingroup.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753051AbYHHNot (ORCPT ); Fri, 8 Aug 2008 09:44:49 -0400 Message-ID: <36420.166.70.238.45.1218201795.squirrel@webmail.wolfmountaingroup.com> In-Reply-To: <37357.166.70.238.45.1218201115.squirrel@webmail.wolfmountaingroup.com > References: <82e4877d0808072133q58150665r355c9bf140d0b42c@mail.gmail.com> <37357.166.70.238.45.1218201115.squirrel@webmail.wolfmountaingroup.com> Date: Fri, 8 Aug 2008 07:23:15 -0600 (MDT) Subject: Re: [ANNOUNCE] mdb-2.6.27-rc2-ia32-08-07-08.patch From: jmerkey@wolfmountaingroup.com To: jmerkey@wolfmountaingroup.com Cc: "Parag Warudkar" , jmerkey@wolfmountaingroup.com, "Linux Kernel Mailing List" User-Agent: SquirrelMail/1.4.6 MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT X-Priority: 3 (Normal) Importance: Normal Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1224 Lines: 43 >> Jeff, >> >> This definitely looks interesting and it even worked for me - breaking >> in couple of times, trying various commands and resuming back to X all >> works. Never tried a kernel debugger before but most things were >> obvious after I figured out that I need to be on the VT to be able to >> press break and be dropped into the debugger. >> >> That said, it triggers soft lockups on all the suspended CPUs - not a >> big deal and probably expected, but I guess that can be cured by >> touching the soft lockup watch dog or something? > > Yep. > > It does with this kprobes interface, I noticed it last night. I will run > this down. I am touching the watchdog in the keyboard handler. > > Jeff Reproduced it. It just spits out the noisy message but the system continues and the processors resume running. This is is an esoteric issue, but I will run it down. It does not happen on kernel versions prior to 2.6.26. Jeff > >> >> Thanks >> >> Parag >> > > > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/