All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brett Russ <russb@emc.com>
To: Michael Madore <Michael.Madore@aslab.com>
Cc: Jeff Garzik <jgarzik@pobox.com>,
	linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org,
	Pasi Pirhonen <upi@papat.org>,
	Bogdan Costescu <Bogdan.Costescu@iwr.uni-heidelberg.de>,
	"Mr. Berkley Shands" <bshands@exegy.com>,
	Jim Edwards <jim@networkdesigning.com>,
	scott olson <scotto701@yahoo.com>,
	Lars Magne Ingebrigtsen <larsi@gnus.org>,
	Evgeny Rodichev <er@sai.msu.su>
Subject: Re: [PATCH 2.6.14-rc2 1/2] libata: Marvell spinlock fixes and simplification
Date: Thu, 06 Oct 2005 07:52:40 -0400	[thread overview]
Message-ID: <43451008.2090305@emc.com> (raw)
In-Reply-To: <1128551744.4041.7.camel@drevil.aslab.com>

Michael Madore wrote:
> I assume this patch doesn't address the 'abnormal status 0x80' issue on
> the 6081.

Correct assumption.  This message seems benign as I've seen it and am 
working fine despite it.  I'll take a look soon.

Is the driver working for you on the 6081?

> On the 5081, I still get two machine checks followed by a
> hard lockup when I load the driver.

Would you turn on ATA_DEBUG and ATA_VERBOSE_DEBUG in 
include/linux/libata.h and send along the console output when loading 
the driver?

Thanks,
BR

  reply	other threads:[~2005-10-06 11:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-05 21:06 [PATCH 2.6.14-rc2 0/2] libata: Marvell SATA support (v0.23-0.24) Brett Russ
2005-10-05 21:08 ` [PATCH 2.6.14-rc2 1/2] libata: Marvell spinlock fixes and simplification Brett Russ
2005-10-05 21:17   ` Jeff Garzik
2005-10-05 21:18     ` Jeff Garzik
2005-10-05 22:35   ` Michael Madore
2005-10-06 11:52     ` Brett Russ [this message]
2005-10-10 19:10       ` Michael Madore
2005-10-05 21:08 ` [PATCH 2.6.14-rc2 2/2] libata: Marvell function headers Brett Russ
2005-10-06 12:46 ` [PATCH 2.6.14-rc2 0/2] libata: Marvell SATA support (v0.23-0.24) Bogdan Costescu
2005-10-06 13:13   ` Jeff Garzik
2005-10-06 13:31     ` Brett Russ
2005-10-06 13:36       ` Jeff Garzik
2005-10-06 14:20       ` Bogdan Costescu

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=43451008.2090305@emc.com \
    --to=russb@emc.com \
    --cc=Bogdan.Costescu@iwr.uni-heidelberg.de \
    --cc=Michael.Madore@aslab.com \
    --cc=bshands@exegy.com \
    --cc=er@sai.msu.su \
    --cc=jgarzik@pobox.com \
    --cc=jim@networkdesigning.com \
    --cc=larsi@gnus.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=scotto701@yahoo.com \
    --cc=upi@papat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.