From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753888Ab1AYOtM (ORCPT ); Tue, 25 Jan 2011 09:49:12 -0500 Received: from mail-fx0-f46.google.com ([209.85.161.46]:46802 "EHLO mail-fx0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753530Ab1AYOtL (ORCPT ); Tue, 25 Jan 2011 09:49:11 -0500 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=Kz22r68jnexfMW8YgsoAd64hU0P9G+6UB670G4rQOvi4A5vBfJbUiXysJNewwfNwqh lFWU2FsJb3yCQpSEn6K3xD4//4JrkCMLIJbz7gLmWtwuc8sqXISdC4+fJlGeJsbXN0dd YFLDzsW5YNdjJTCgWfoxNGy/ZR3LqKQmEoso4= Date: Tue, 25 Jan 2011 15:49:05 +0100 From: Tejun Heo To: "Ahmed S. Darwish" Cc: "H. Peter Anvin" , Thomas Gleixner , Ingo Molnar , X86-ML , Tony Luck , Dave Jones , Andrew Morton , Randy Dunlap , Willy Tarreau , Willy Tarreau , Dirk Hohndel , Dirk.Hohndel@intel.com, IDE-ML , LKML Subject: Re: [PATCH 0/2][concept RFC] x86: BIOS-save kernel log to disk upon panic Message-ID: <20110125144905.GC27510@htj.dyndns.org> References: <20110125134748.GA10051@laptop> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20110125134748.GA10051@laptop> User-Agent: Mutt/1.5.20 (2009-06-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello, On Tue, Jan 25, 2011 at 03:47:48PM +0200, Ahmed S. Darwish wrote: > The main problem, it seems, is that the BIOS "Reset controller" command is not > enough to restore disk hardware to a state understandable by the BIOS code. I doubt many BIOSen would implement this properly. It's something no one ever uses and modern controllers have a lot more states and are more complex to reset. > - Is it possible to re-initialize the disk hardware to its POST > state (thus make the BIOS services work reliably) while keeping > system RAM unmodified? I'm afraid this can't be made reliable. Nobody uses it and the stuff we do during pci initialization is enough to leave some BIOSen clueless. > - If not, can we do it manually by reprogramming the controllers? It would be only theoretically possible. We'll basically have to write deinitialization routine for different controllers, which of course would be super-cold path and not many people would test. I'm afraid this is gonna be something which works sometimes (or even more times than not) but can't ever be made reliable. I think it would be better to head toward usb or other kind of early console. Thanks. -- tejun