From: Jonathan Woithe <jwoithe@physics.adelaide.edu.au>
Message-Id: <201004090436.o394a0ao022460@turbo.physics.adelaide.edu.au>
Subject: Re: 2.6.33: libata issues with VIA SATA/PATA controller
To: jeff@garzik.org (Jeff Garzik)
Date: Fri, 9 Apr 2010 14:06:00 +0930 (CST)
Cc: jwoithe@physics.adelaide.edu.au (Jonathan Woithe),
       linux-kernel@vger.kernel.org,
       linux-ide@vger.kernel.org (Linux IDE mailing list)
In-Reply-To: <4BBEAC83.9060301@garzik.org> from "Jeff Garzik" at Apr 09, 2010 12:26:43 AM
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1357
Lines: 36

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.

> That will show us libata boot messages as well as the failures you are
> seeing, in full detail.

For sure.  In terms of the detailed failure messages what I posted
previously is about all that was shown.

> Also, please try the latest 2.6.34-rc kernel, as that has several fixes 
> for both pata_via and sata_via which did not make 2.6.33.

I'll see if I can squeeze this in this afternoon and report back.

Regards
  jonathan
--
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/