From: "Michael S. Zick" <lkml@morethan.org>
To: Grozdan <neutrino8@gmail.com>
Cc: Robert Hancock <hancockrwd@gmail.com>,
linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org,
tj@kernel.org, alan@lxorguk.ukuu.org.uk
Subject: Re: Kernel 2.6.30rc7 limits IDE to UDMA33
Date: Sun, 7 Jun 2009 13:46:19 -0500 [thread overview]
Message-ID: <200906071346.28021.lkml@morethan.org> (raw)
In-Reply-To: <c5bd819b0906071124j21270574h44db963bdc0b552d@mail.gmail.com>
On Sun June 7 2009, Grozdan wrote:
> 2009/6/7 Robert Hancock <hancockrwd@gmail.com>:
> > Grozdan wrote:
> >>
> >> 2009/6/6 Robert Hancock <hancockrwd@gmail.com>:
> >>>
> >>> Thing is somehow the GTM detection isn't working now and it apparently
> >>> was
> >>> in 2.6.27.1. I'm not seeing any patches to pata_via or libata-acpi that
> >>> seem
> >>> like they would affect this offhand. Grozdan, would you be able to try
> >>> git
> >>> bisect to try to figure out what changed the behavior?
> >>>
> >>> CCing Tejun in case he has any ideas..
> >>>
> >>
> >> I've no idea how and where to do a git bisect so if someone is willing
> >> to explain in simple steps, I can try...
> >
> > Linus's post on here is a pretty simple explanation:
> >
> > http://kerneltrap.org/node/11753
> >
>
> Yes, it's clear to someone who's familiar with git but not to a noob
> like me. Where do I run this git? After it's finished what to do next?
> How many times do I have to compile kernels? Which kernels exactly?
> After booting a "bad" kernel, what then? etc... From reading the
> article, the guy has to compile 14!! times just to catch a problem
> between kernel 2.6.21 and 2.6.22.
>
The article presumes the simple case of a single commit being the
problem. If the problem involves more than one. . .
Think of doing a binary search in a list of values with duplicate
entries. ;)
> I guess in my case I'll have to
> compile a lot more than 14 times to catch something between kernel
> 2.6.27 and 2.6.30 and honestly I don't have time for this right now.
>
Yes, it can get to be time-consuming unless your lucky.
> However, I did a diff between the pata_via driver of kernel 2.6.27 and
> 2.6.30 and there have been changes to it but I'm not sure if they
> affect the cable detection...
>
That's a start. Now if you knew what you where looking for...
(No offense intended - "diff" doesn't place "here I am" markers.)
The machine I am doing my own tests on uses the pata_via driver and
it detects the udma66 disk drive as a udma33 - - -
But finding this is way down on my list of things to look for -
Someone else is welcome to beat me to it.
Mike
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
>
next prev parent reply other threads:[~2009-06-07 18:46 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-02 22:25 Kernel 2.6.30rc7 limits IDE to UDMA33 Grozdan
2009-06-03 4:05 ` Robert Hancock
2009-06-03 11:35 ` Grozdan
2009-06-03 12:14 ` Alan Cox
2009-06-03 12:52 ` Grozdan
2009-06-03 13:01 ` Alan Cox
2009-06-03 13:15 ` Grozdan
2009-06-03 13:39 ` Grozdan
2009-06-04 14:50 ` Grozdan
2009-06-05 9:05 ` Alan Cox
2009-06-05 10:35 ` Grozdan
2009-06-05 10:42 ` Alan Cox
2009-06-05 12:43 ` Grozdan
2009-06-05 13:21 ` Alan Cox
2009-06-05 14:02 ` Grozdan
2009-06-06 1:07 ` Robert Hancock
2009-06-06 14:56 ` Alan Cox
2009-06-06 18:16 ` Robert Hancock
2009-06-06 22:08 ` Alan Cox
2009-06-07 4:39 ` Grozdan
[not found] ` <4A2BF785.3020402@gmail.com>
2009-06-07 18:24 ` Grozdan
2009-06-07 18:46 ` Michael S. Zick [this message]
2009-06-07 19:54 ` Alan Cox
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=200906071346.28021.lkml@morethan.org \
--to=lkml@morethan.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=hancockrwd@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neutrino8@gmail.com \
--cc=tj@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox