From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tejun Heo Subject: Re: 2.6.32.2 SATA link detect failed, 2.6.32.1 works fine Date: Thu, 24 Dec 2009 16:51:47 +0900 Message-ID: <4B331D93.2010000@kernel.org> References: <4B30134C.1050609@gmail.com> <51f3faa70912211708j200ab584wa835ffe50981415e@mail.gmail.com> <4B31DB17.4050509@kernel.org> <4B331957.7030906@kernel.org> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Return-path: Received: from hera.kernel.org ([140.211.167.34]:39589 "EHLO hera.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754803AbZLXHsR (ORCPT ); Thu, 24 Dec 2009 02:48:17 -0500 In-Reply-To: Sender: linux-ide-owner@vger.kernel.org List-Id: linux-ide@vger.kernel.org To: fengxiangjun Cc: Robert Hancock , linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org Hello, On 12/24/2009 04:45 PM, fengxiangjun wrote: > Hi, I can not capture the full failing boot log. > The kernel panic, and shift + pageup does not work. > > With output to serial console, the problem goes away. Ah... right, I forgot about this. > I think with an initrd, I can reproduce the problem and capture the > full failing boot log. But with an initrd, there's no > problem. Every thing works fine. Hmmm.... can you please try netconsole? Netconsole usually doesn't introduce much delay and should be able to extract the log without affecting timings. Thanks. -- tejun