From: James Andrewartha <jamesa@daa.com.au>
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
Date: Fri, 09 Apr 2010 14:04:14 +0800 [thread overview]
Message-ID: <4BBEC35E.8060002@daa.com.au> (raw)
In-Reply-To: <201004090436.o394a0ao022460@turbo.physics.adelaide.edu.au>
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
next prev parent reply other threads:[~2010-04-09 6:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-09 0:43 2.6.33: libata issues with VIA SATA/PATA controller Jonathan Woithe
2010-04-09 4:26 ` Jeff Garzik
2010-04-09 4:36 ` Jonathan Woithe
2010-04-09 6:04 ` James Andrewartha [this message]
2010-04-09 11:14 ` Jonathan Woithe
2010-04-09 11:29 ` Jeff Garzik
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4BBEC35E.8060002@daa.com.au \
--to=jamesa@daa.com.au \
--cc=jeff@garzik.org \
--cc=jwoithe@physics.adelaide.edu.au \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox