Gitweb:     
http://git.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=0f9fe9b7148f95f018ae2c97f7fa1a35364ea785
Commit:     0f9fe9b7148f95f018ae2c97f7fa1a35364ea785
Parent:     04d86d6fc0477f217d60667adfc26f1f56264cc9
Author:     Alan Cox <[EMAIL PROTECTED]>
AuthorDate: Fri Nov 30 15:23:16 2007 +0000
Committer:  Jeff Garzik <[EMAIL PROTECTED]>
CommitDate: Sat Dec 1 17:44:10 2007 -0500

    libata: Fix early use of port printk. (Was Re: ata4294967295: failed to 
start port (errno=-19))
    
    On Fri, 30 Nov 2007 14:34:11 +0200 (EET)
    Meelis Roos <[EMAIL PROTECTED]> wrote:
    
    > > Can you stick a stack trace in at that point ? That would help diagnose
    > > it a great deal quicker.
    >
    > Finally done - found out hard way that BUG() is too bad and
    > dump_st5ack() suits me better.
    
    Thanks. This should fix the real cause, and also allow for port start to
    fail politely with -ENODEV.
    
    Signed-off-by: Alan Cox <[EMAIL PROTECTED]>
    Signed-off-by: Jeff Garzik <[EMAIL PROTECTED]>
---
 drivers/ata/libata-core.c |    5 ++---
 1 files changed, 2 insertions(+), 3 deletions(-)

diff --git a/drivers/ata/libata-core.c b/drivers/ata/libata-core.c
index 53d1101..b514a80 100644
--- a/drivers/ata/libata-core.c
+++ b/drivers/ata/libata-core.c
@@ -6967,12 +6967,11 @@ int ata_host_start(struct ata_host *host)
                if (ap->ops->port_start) {
                        rc = ap->ops->port_start(ap);
                        if (rc) {
-                               ata_port_printk(ap, KERN_ERR, "failed to "
-                                               "start port (errno=%d)\n", rc);
+                               if (rc != -ENODEV)
+                                       dev_printk(KERN_ERR, host->dev, "failed 
to start port %d (errno=%d)\n", i, rc);
                                goto err_out;
                        }
                }
-
                ata_eh_freeze_port(ap);
        }
 
-
To unsubscribe from this list: send the line "unsubscribe git-commits-head" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to