From: "Boris Petkov" <petkovbb@googlemail.com>
To: Santiago Vila <sanvila@unex.es>
Cc: bzolnier@gmail.com, axboe@kernel.dk, linux-ide@vger.kernel.org
Subject: Re: Bug 11581
Date: Tue, 14 Oct 2008 13:53:40 +0200 [thread overview]
Message-ID: <9ea470500810140453m6e1f7eb6raf179ee78414e19e@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0810141314590.2555@cantor.unex.es>
On Tue, Oct 14, 2008 at 1:18 PM, Santiago Vila <sanvila@unex.es> wrote:
> [ Sorry for the delay, yesterday it was a non-working day here, so
> rebooting the computer was a little bit dangerous ].
>
>> Ok, it seems that your drive gets puzzled after receiving a GET_CONFIGURATION
>> command. Lets see whether this is the real cause of the problem. Here's a yet
>> another version of the inquisitive patch :) which drops such commands. Please
>> rebuild with it and send me the dmesg. Thanks.
>
> Hurrah!
>
> There is no waiting time during boot anymore, and the drive hdc now works.
Ok, we see now where the problem hides. Nice! However, IIRC, you can boot 2.6.18
with the same Debian unstable setup (correct?) which means that the drive
receives the same commands. So, it seems that there is something in the way the
command is sent to the drive that puzzles it. I'll try to cook up a
debugging patch for 2.6.18 for you to apply so that we can make sure it does
execute GET_CONFIGURATION properly.
Thanks a lot for your work!
--
Regards/Gruss,
Boris
next prev parent reply other threads:[~2008-10-14 11:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-04 9:12 Bug 11581 Borislav Petkov
[not found] ` <Pine.LNX.4.64.0810051147470.2543@cantor.unex.es>
2008-10-10 6:16 ` Borislav Petkov
2008-10-10 10:23 ` Santiago Vila
2008-10-12 7:15 ` Borislav Petkov
2008-10-14 11:18 ` Santiago Vila
2008-10-14 11:53 ` Boris Petkov [this message]
2008-10-14 15:11 ` Santiago Vila
2008-10-26 15:46 ` Borislav Petkov
2008-10-27 11:58 ` Santiago Vila
2008-10-27 13:02 ` Boris Petkov
2008-10-28 11:04 ` Santiago Vila
2008-11-10 6:34 ` Borislav Petkov
2008-11-10 12:02 ` Santiago Vila
2008-11-11 7:11 ` Borislav Petkov
2008-11-11 10:17 ` Santiago Vila
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=9ea470500810140453m6e1f7eb6raf179ee78414e19e@mail.gmail.com \
--to=petkovbb@googlemail.com \
--cc=axboe@kernel.dk \
--cc=bzolnier@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=petkovbb@gmail.com \
--cc=sanvila@unex.es \
/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