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 1POTd5-0000c9-KI for kexec@lists.infradead.org; Fri, 03 Dec 2010 11:16:44 +0000 Date: Fri, 3 Dec 2010 12:16:38 +0100 From: Stanislaw Gruszka Subject: kdump broken on 2.6.37-rc4 Message-ID: <20101203111623.GA2741@redhat.com> MIME-Version: 1.0 Content-Disposition: inline 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: kexec@lists.infradead.org Cc: linux-kernel@vger.kernel.org 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 _______________________________________________ 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 S932423Ab0LCLQq (ORCPT ); Fri, 3 Dec 2010 06:16:46 -0500 Received: from mx1.redhat.com ([209.132.183.28]:4513 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932347Ab0LCLQp (ORCPT ); Fri, 3 Dec 2010 06:16:45 -0500 Date: Fri, 3 Dec 2010 12:16:38 +0100 From: Stanislaw Gruszka To: kexec@lists.infradead.org Cc: linux-kernel@vger.kernel.org Subject: kdump broken on 2.6.37-rc4 Message-ID: <20101203111623.GA2741@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline 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 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