On 12/12/06, Steve Wise <[EMAIL PROTECTED]> wrote:
On Tue, 2006-12-12 at 13:04 -0500, Jeff Garzik wrote:
> Alan wrote:
> > On Tue, 12 Dec 2006 10:39:02 -0600
> > Steve Wise <[EMAIL PROTECTED]> wrote:
> >
> >> All,
> >>
> >> Bisecting reveals that this commit causes the problem:
> >
> > Yes we
On Tue, 2006-12-12 at 13:04 -0500, Jeff Garzik wrote:
> Alan wrote:
> > On Tue, 12 Dec 2006 10:39:02 -0600
> > Steve Wise <[EMAIL PROTECTED]> wrote:
> >
> >> All,
> >>
> >> Bisecting reveals that this commit causes the problem:
> >
> > Yes we know. There is a libata patch missing. As I said - if
On Tue, 2006-12-12 at 17:35 +, Alan wrote:
> On Tue, 12 Dec 2006 10:39:02 -0600
> Steve Wise <[EMAIL PROTECTED]> wrote:
>
> > All,
> >
> > Bisecting reveals that this commit causes the problem:
>
> Yes we know. There is a libata patch missing. As I said - if it is still
> missing by -rc1
Alan wrote:
On Tue, 12 Dec 2006 10:39:02 -0600
Steve Wise <[EMAIL PROTECTED]> wrote:
All,
Bisecting reveals that this commit causes the problem:
Yes we know. There is a libata patch missing. As I said - if it is still
missing by -rc1 I'll sort out a diff.
What's the patch? Message-id? I
On Tue, 12 Dec 2006 10:39:02 -0600
Steve Wise <[EMAIL PROTECTED]> wrote:
> All,
>
> Bisecting reveals that this commit causes the problem:
Yes we know. There is a libata patch missing. As I said - if it is still
missing by -rc1 I'll sort out a diff.
Alan
-
To unsubscribe from this list: send
All,
Bisecting reveals that this commit causes the problem:
commit 368c73d4f689dae0807d0a2aa74c61fd2b9b075f
Author: Alan Cox <[EMAIL PROTECTED]>
Date: Wed Oct 4 00:41:26 2006 +0100
PCI: quirks: fix the festering mess that claims to handle IDE quirks
The number of permutations of crap
All,
Bisecting reveals that this commit causes the problem:
commit 368c73d4f689dae0807d0a2aa74c61fd2b9b075f
Author: Alan Cox [EMAIL PROTECTED]
Date: Wed Oct 4 00:41:26 2006 +0100
PCI: quirks: fix the festering mess that claims to handle IDE quirks
The number of permutations of crap
On Tue, 12 Dec 2006 10:39:02 -0600
Steve Wise [EMAIL PROTECTED] wrote:
All,
Bisecting reveals that this commit causes the problem:
Yes we know. There is a libata patch missing. As I said - if it is still
missing by -rc1 I'll sort out a diff.
Alan
-
To unsubscribe from this list: send the
Alan wrote:
On Tue, 12 Dec 2006 10:39:02 -0600
Steve Wise [EMAIL PROTECTED] wrote:
All,
Bisecting reveals that this commit causes the problem:
Yes we know. There is a libata patch missing. As I said - if it is still
missing by -rc1 I'll sort out a diff.
What's the patch? Message-id? I
On Tue, 2006-12-12 at 17:35 +, Alan wrote:
On Tue, 12 Dec 2006 10:39:02 -0600
Steve Wise [EMAIL PROTECTED] wrote:
All,
Bisecting reveals that this commit causes the problem:
Yes we know. There is a libata patch missing. As I said - if it is still
missing by -rc1 I'll sort out a
On Tue, 2006-12-12 at 13:04 -0500, Jeff Garzik wrote:
Alan wrote:
On Tue, 12 Dec 2006 10:39:02 -0600
Steve Wise [EMAIL PROTECTED] wrote:
All,
Bisecting reveals that this commit causes the problem:
Yes we know. There is a libata patch missing. As I said - if it is still
missing
On 12/12/06, Steve Wise [EMAIL PROTECTED] wrote:
On Tue, 2006-12-12 at 13:04 -0500, Jeff Garzik wrote:
Alan wrote:
On Tue, 12 Dec 2006 10:39:02 -0600
Steve Wise [EMAIL PROTECTED] wrote:
All,
Bisecting reveals that this commit causes the problem:
Yes we know. There is a libata
I'm also hitting this running at commit:
commit 7bf65382caeecea4ae7206138e92e732b676d6e5
Author: Andrew Morton <[EMAIL PROTECTED]>
Date: Fri Dec 8 02:41:14 2006 -0800
I was at 2.6.19, then merged up to Linus's tree Friday 12/8 and now I
hit this. I have 2 identical systems with one difference,
On Mon, 11 Dec 2006 14:26:30 +0100
"Alessandro Suardi" <[EMAIL PROTECTED]> wrote:
> I still have this problem in 2.6.19-git17. Is this expected behavior
> or should it have been fixed by now ?
I don't currently have time to track the -git trees. Once 19rc1 appears
I'll take a look and send
On 12/3/06, Alessandro Suardi <[EMAIL PROTECTED]> wrote:
On 12/3/06, Alan <[EMAIL PROTECTED]> wrote:
> > > ACPI: PCI Interrupt :00:1f.2[B] -> Link [LNKB] -> GSI 5 (level, low)
-> IRQ5
> > > PCI: Unable to reserve I/O region #1:[EMAIL PROTECTED] for device
:00:1f.2
> > > ata_piix: probe
On 12/3/06, Alessandro Suardi [EMAIL PROTECTED] wrote:
On 12/3/06, Alan [EMAIL PROTECTED] wrote:
ACPI: PCI Interrupt :00:1f.2[B] - Link [LNKB] - GSI 5 (level, low)
- IRQ5
PCI: Unable to reserve I/O region #1:[EMAIL PROTECTED] for device
:00:1f.2
ata_piix: probe of :00:1f.2
On Mon, 11 Dec 2006 14:26:30 +0100
Alessandro Suardi [EMAIL PROTECTED] wrote:
I still have this problem in 2.6.19-git17. Is this expected behavior
or should it have been fixed by now ?
I don't currently have time to track the -git trees. Once 19rc1 appears
I'll take a look and send Linus
I'm also hitting this running at commit:
commit 7bf65382caeecea4ae7206138e92e732b676d6e5
Author: Andrew Morton [EMAIL PROTECTED]
Date: Fri Dec 8 02:41:14 2006 -0800
I was at 2.6.19, then merged up to Linus's tree Friday 12/8 and now I
hit this. I have 2 identical systems with one difference,
18 matches
Mail list logo
