All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Lord <liml@rtr.ca>
To: "Ask Bjørn Hansen" <ask@develooper.com>
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: sata_mv with Adaptec AIC-8130/Marvell 88SX6041 ("Badness in __msleep")
Date: Fri, 2 Jun 2006 22:45:49 -0400	[thread overview]
Message-ID: <200606022245.49637.liml@rtr.ca> (raw)
In-Reply-To: <EA69B14D-2874-48EA-BF67-0A96DE690FA6@develooper.com>

On Friday 02 June 2006 21:42, Ask Bjørn Hansen wrote:
> 
> On May 28, 2006, at 19:49, Mark Lord wrote:
> 
> > The attached patch [0.7-backport] is an untested backport of the  
> > latest sata_mv,
> > which should be more reliable than what you've been using. [0.5]
> 
> It works most of the time (where the 0.5 didn't work most of the  
> time), but I still see the "Badness in __msleep" occasionally (and it  
> only detects one of the disks then).    However, the Adaptec BIOS is  
> only seeing one of the disks sometimes, so maybe there's something  
> wrong with the hardware.  The BIOS did detect both drives in the boot  
> that gave the output below though.

Weird.  I cannot make sense of that traceback.  What CPU is this kernel built for?

And does this patch (below) make the "Badness" go away?

Cheers

---
--- linux/drivers/scsi/sata_mv.c.16-backport	2006-05-26 09:15:22.000000000 -0400
+++ linux/drivers/scsi/sata_mv.c	2006-06-02 22:39:07.000000000 -0400
@@ -2022,7 +2022,7 @@
 
 static void mv_phy_reset(struct ata_port *ap)
 {
-	__mv_phy_reset(ap, 1);
+	__mv_phy_reset(ap, 0);
 }
 
 /**

      reply	other threads:[~2006-06-03  2:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-29  2:31 sata_mv with Adaptec AIC-8130/Marvell 88SX6041 ("Badness in __msleep") Ask Bjørn Hansen
2006-05-29  2:49 ` Mark Lord
2006-05-29 19:51   ` Ask Bjørn Hansen
2006-06-03  1:42   ` Ask Bjørn Hansen
2006-06-03  2:45     ` Mark Lord [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=200606022245.49637.liml@rtr.ca \
    --to=liml@rtr.ca \
    --cc=ask@develooper.com \
    --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 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.