From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mx1.redhat.com ([209.132.183.28]) by canuck.infradead.org with esmtp (Exim 4.72 #1 (Red Hat Linux)) id 1POZAv-0001GJ-H9 for kexec@lists.infradead.org; Fri, 03 Dec 2010 17:12:02 +0000 Date: Fri, 3 Dec 2010 18:11:48 +0100 From: Stanislaw Gruszka Subject: Re: kdump broken on 2.6.37-rc4 Message-ID: <20101203171147.GA2299@redhat.com> References: <20101203111623.GA2741@redhat.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: kexec-bounces@lists.infradead.org Errors-To: kexec-bounces+dwmw2=infradead.org@lists.infradead.org To: Maxim Uvarov Cc: kexec@lists.infradead.org, linux-kernel@vger.kernel.org On Fri, Dec 03, 2010 at 06:46:09PM +0300, Maxim Uvarov wrote: > 2010/12/3 Stanislaw Gruszka : > > On my T-60 laptop, i686 system with 2.6.37-rc4 kernel, > > "echo c > /proc/sysrq-trigger" just hung the system. Kdump > > works on 2.6.36. Is this known issue? If not, what info > > I should provide to solve it (I think the easiest way > > to solve the problem would be bisect) ? > > > > Stanislaw > > > > I tested x86 QEMU yesterday with the latest git. It worked. > Might be something target specific.., What does console print? Here is the photo http://people.redhat.com/sgruszka/20101203_005.jpg There are two BUGs, first "sleeping function called from invalid context" and then "unable to handle null pointer dereference". Stanislaw _______________________________________________ kexec mailing list kexec@lists.infradead.org http://lists.infradead.org/mailman/listinfo/kexec From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753601Ab0LCRME (ORCPT ); Fri, 3 Dec 2010 12:12:04 -0500 Received: from mx1.redhat.com ([209.132.183.28]:47644 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753461Ab0LCRMC (ORCPT ); Fri, 3 Dec 2010 12:12:02 -0500 Date: Fri, 3 Dec 2010 18:11:48 +0100 From: Stanislaw Gruszka To: Maxim Uvarov Cc: kexec@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: kdump broken on 2.6.37-rc4 Message-ID: <20101203171147.GA2299@redhat.com> References: <20101203111623.GA2741@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-12-10) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Dec 03, 2010 at 06:46:09PM +0300, Maxim Uvarov wrote: > 2010/12/3 Stanislaw Gruszka : > > On my T-60 laptop, i686 system with 2.6.37-rc4 kernel, > > "echo c > /proc/sysrq-trigger" just hung the system. Kdump > > works on 2.6.36. Is this known issue? If not, what info > > I should provide to solve it (I think the easiest way > > to solve the problem would be bisect) ? > > > > Stanislaw > > > > I tested x86 QEMU yesterday with the latest git. It worked. > Might be something target specific.., What does console print? Here is the photo http://people.redhat.com/sgruszka/20101203_005.jpg There are two BUGs, first "sleeping function called from invalid context" and then "unable to handle null pointer dereference". Stanislaw