From: Jeff Garzik <jeff@garzik.org>
To: Jonathan Woithe <jwoithe@physics.adelaide.edu.au>
Cc: 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 07:29:23 -0400 [thread overview]
Message-ID: <4BBF0F93.2010601@garzik.org> (raw)
In-Reply-To: <201004091114.o39BEILl018939@mercury.physics.adelaide.edu.au>
On 04/09/2010 07:14 AM, Jonathan Woithe wrote:
> I'll look into the alternative console methods to see if I can capture a
> full output from the failing kernel. However, it will be at least two weeks
> before I can do this because that's the earliest I'll be physically back at
> the machine for an extended period of time (I could probably run quick tests
> sooner).
We won't be able to help without the full dmesg from the failing kernel...
Jeff
prev parent reply other threads:[~2010-04-09 11:29 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
2010-04-09 11:14 ` Jonathan Woithe
2010-04-09 11:29 ` Jeff Garzik [this message]
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=4BBF0F93.2010601@garzik.org \
--to=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