linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Andrey Gusev <a.gusev1980@mail.ru>
Cc: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
	linux-ide@vger.kernel.org, petkovbb@gmail.com,
	linuxppc-dev@ozlabs.org, David Miller <davem@davemloft.net>
Subject: Re: Delay on intialization ide subsystem(most likely)
Date: Wed, 08 Jul 2009 11:12:42 +1000	[thread overview]
Message-ID: <1247015562.6066.59.camel@pasglop> (raw)
In-Reply-To: <20090708011802.74a7c21b@power-debian>

On Wed, 2009-07-08 at 01:18 +0400, Andrey Gusev wrote:

> I tried this drive on ide1 and ide2, there are same issue. This drive worked
> on P-III before (as separate on channel, with another hard drive and with cdrom)
> and I didn't have any problem with it. There are chunks of dmesg.

Wow... It also fails with MWDMA2 ! That's just plain weird. It fails as
master as well as slave too. Hrm. I wonder if it could be your cable...
Do you have other machines (non-powermac) you can try that drive again
just in case it toast itself in some way too ?

Bart, I don't suppose we know of any problem with those drive models ?
(Q. FireballP LM20.5)

Cheers,
Ben.



  reply	other threads:[~2009-07-08  1:15 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-25 13:02 Delay on intialization ide subsystem(most likely) Andrey Gusev
2009-04-25 14:48 ` Bartlomiej Zolnierkiewicz
2009-04-26 22:20   ` Andrey Gusev
2009-04-27 20:36   ` Andrey Gusev
2009-04-27 21:21     ` Bartlomiej Zolnierkiewicz
2009-04-28  8:26       ` Re[2]: " Андрей Гусев
2009-04-29 21:05       ` Andrey Gusev
2009-05-12 19:50       ` Andrey Gusev
2009-05-13 13:28         ` Bartlomiej Zolnierkiewicz
2009-05-13 17:11           ` Andrey Gusev
2009-05-13 18:46             ` Bartlomiej Zolnierkiewicz
2009-05-15 20:40               ` Andrey Gusev
2009-05-20 15:56                 ` Bartlomiej Zolnierkiewicz
2009-05-30 10:46                   ` Andrey Gusev
2009-06-08 20:20                     ` Bartlomiej Zolnierkiewicz
2009-06-08 23:26                       ` Benjamin Herrenschmidt
2009-06-10 11:44                         ` Bartlomiej Zolnierkiewicz
2009-07-05 11:17                           ` Andrey Gusev
2009-07-06 15:04                             ` Bartlomiej Zolnierkiewicz
2009-07-06 23:23                               ` Benjamin Herrenschmidt
2009-07-07 21:18                                 ` Andrey Gusev
2009-07-08  1:12                                   ` Benjamin Herrenschmidt [this message]
2009-07-13 19:27                                     ` Andrey Gusev
2009-06-10 20:38                       ` Andrey Gusev
2009-06-10 21:46                         ` Benjamin Herrenschmidt
2009-06-10 21:57                           ` Andrey Gusev
2009-06-11  0:44                             ` Benjamin Herrenschmidt
2009-06-20 18:12                               ` Andrey Gusev

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=1247015562.6066.59.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=a.gusev1980@mail.ru \
    --cc=bzolnier@gmail.com \
    --cc=davem@davemloft.net \
    --cc=linux-ide@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=petkovbb@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).