From mboxrd@z Thu Jan 1 00:00:00 1970 From: Danny Milosavljevic Subject: crashkernel; was: /gnu/store/ corruption on crash Date: Mon, 22 Feb 2016 22:46:11 +0100 Message-ID: <20160222224611.3ea6a2b6@scratchpost.org> References: <20160222221125.2d5e9c07@scratchpost.org> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:44214) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aXyJ9-0004Ln-0z for guix-devel@gnu.org; Mon, 22 Feb 2016 16:46:19 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aXyJ5-0006zy-Rp for guix-devel@gnu.org; Mon, 22 Feb 2016 16:46:18 -0500 Received: from dd1012.kasserver.com ([85.13.128.8]:54053) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aXyJ5-0006zm-LK for guix-devel@gnu.org; Mon, 22 Feb 2016 16:46:15 -0500 Received: from localhost (178.115.128.117.wireless.dyn.drei.com [178.115.128.117]) by dd1012.kasserver.com (Postfix) with ESMTPSA id A47DA1CA051D for ; Mon, 22 Feb 2016 22:46:13 +0100 (CET) In-Reply-To: <20160222221125.2d5e9c07@scratchpost.org> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org To: guix-devel@gnu.org On Mon, 22 Feb 2016 22:11:25 +0100 Danny Milosavljevic wrote: > I've got a problem on an X200 where, after I did standby 3 times, it will wake up fine but at the first larger disk access hang the machine. Also, is kdump crashkernel supported in GuixSD? The minimal support would be: pass kernel command line option "crashkernel", for example crashkernel=256M. This reserves a region of memory not to be touched by anyone but the crash analyzer (especially not by DMA). Better support would be (see linux/Documentation/kdump/ ): Enable CONFIG_DEBUG_INFO in the kernel config. The remaining are all already active in GuixSD. For x86_64, after booting, run kexec -p kernelimagefile --initrd=... --append="root=... 1 irqpoll maxcpus=1 reset_devices"