Message-ID: <4BBEC35E.8060002@daa.com.au>
Date: Fri, 09 Apr 2010 14:04:14 +0800
From: James Andrewartha <jamesa@daa.com.au>
Organization: Data Analysis Australia
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.9) Gecko/20100317 Lightning/1.0b1 Thunderbird/3.0.4
MIME-Version: 1.0
To: Jonathan Woithe <jwoithe@physics.adelaide.edu.au>
CC: Jeff Garzik <jeff@garzik.org>, linux-kernel@vger.kernel.org,
       Linux IDE mailing list <linux-ide@vger.kernel.org>
Subject: Re: 2.6.33: libata issues with VIA SATA/PATA controller
References: <201004090436.o394a0ao022460@turbo.physics.adelaide.edu.au>
In-Reply-To: <201004090436.o394a0ao022460@turbo.physics.adelaide.edu.au>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1176
Lines: 29

On 9/04/2010 12:36 PM, Jonathan Woithe wrote:
> Hi Jeff
> 
>> A complete dmesg is definitely useful.
> 
> It's at the end of my previous post.
> 
>> Posting one from the failing kernel would be preferred, though.
> 
> Any ideas as to how I can capture it?  Since the SATA disc interfaces stop
> working long before they are mounted none of the early boot messages make it
> to disc.  All the interesting bits are therefore scrolled into the bit
> bucket.
> 
> A serial console might be doable (is there documentation about how to set
> one up?) but that would take some time to arrange - I'm only physically at
> the machine in question sporadically and I'd have to rustle up another PC
> ready for my next visit.  It could be done, but might take some time.

Netconsole is the easiest way to get dmesg when disks aren't working - see
Documentation/networking/netconsole.txt for details on how to set it up.

-- 
James Andrewartha
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/