On Thursday, 14 of February 2008, Alexey Dobriyan wrote:
> On Wed, Feb 13, 2008 at 11:52:46PM +0100, Rafael J. Wysocki wrote:
> > On Monday, 4 of February 2008, Alexey Dobriyan wrote:
> > > Commit c40a22e0ce5eb400f27449e59e43d021bee58b8d aka
> > > "PCI: Fix bus resource assignment on 32 bits with
On Wed, 2008-02-13 at 23:52 +0100, Rafael J. Wysocki wrote:
> On Monday, 4 of February 2008, Alexey Dobriyan wrote:
> > Commit c40a22e0ce5eb400f27449e59e43d021bee58b8d aka
> > "PCI: Fix bus resource assignment on 32 bits with 64b resources"
> > renders one tg3-equipped box networkless here.
>
>
On Wed, Feb 13, 2008 at 11:52:46PM +0100, Rafael J. Wysocki wrote:
> On Monday, 4 of February 2008, Alexey Dobriyan wrote:
> > Commit c40a22e0ce5eb400f27449e59e43d021bee58b8d aka
> > "PCI: Fix bus resource assignment on 32 bits with 64b resources"
> > renders one tg3-equipped box networkless here.
On Monday, 4 of February 2008, Alexey Dobriyan wrote:
> Commit c40a22e0ce5eb400f27449e59e43d021bee58b8d aka
> "PCI: Fix bus resource assignment on 32 bits with 64b resources"
> renders one tg3-equipped box networkless here.
Has it been fixed already or is it still happening with the current
On Monday, 4 of February 2008, Alexey Dobriyan wrote:
Commit c40a22e0ce5eb400f27449e59e43d021bee58b8d aka
PCI: Fix bus resource assignment on 32 bits with 64b resources
renders one tg3-equipped box networkless here.
Has it been fixed already or is it still happening with the current mainline?
On Thursday, 14 of February 2008, Alexey Dobriyan wrote:
On Wed, Feb 13, 2008 at 11:52:46PM +0100, Rafael J. Wysocki wrote:
On Monday, 4 of February 2008, Alexey Dobriyan wrote:
Commit c40a22e0ce5eb400f27449e59e43d021bee58b8d aka
PCI: Fix bus resource assignment on 32 bits with 64b
On Wed, 2008-02-13 at 23:52 +0100, Rafael J. Wysocki wrote:
On Monday, 4 of February 2008, Alexey Dobriyan wrote:
Commit c40a22e0ce5eb400f27449e59e43d021bee58b8d aka
PCI: Fix bus resource assignment on 32 bits with 64b resources
renders one tg3-equipped box networkless here.
Has it been
On Wed, Feb 13, 2008 at 11:52:46PM +0100, Rafael J. Wysocki wrote:
On Monday, 4 of February 2008, Alexey Dobriyan wrote:
Commit c40a22e0ce5eb400f27449e59e43d021bee58b8d aka
PCI: Fix bus resource assignment on 32 bits with 64b resources
renders one tg3-equipped box networkless here.
Has
On Thu, Feb 07, 2008 at 08:15:26AM +1100, Benjamin Herrenschmidt wrote:
>
> >
> > BTW, "[PATCH] x86_32: fix regression caused by trim ram according to mtrr
> > on system with 4G more RAM"
> > http://marc.info/?l=linux-kernel=120229095121673=2
> > fixes this box too and I have back all 4G of RAM
On Thu, Feb 07, 2008 at 08:15:26AM +1100, Benjamin Herrenschmidt wrote:
BTW, [PATCH] x86_32: fix regression caused by trim ram according to mtrr
on system with 4G more RAM
http://marc.info/?l=linux-kernelm=120229095121673w=2
fixes this box too and I have back all 4G of RAM as a
>
> BTW, "[PATCH] x86_32: fix regression caused by trim ram according to mtrr on
> system with 4G more RAM"
> http://marc.info/?l=linux-kernel=120229095121673=2
> fixes this box too and I have back all 4G of RAM as a bonus. :-)
You mean you no longer have a problem or does your tg3 issue still
On Feb 6, 2008 2:05 AM, Alexey Dobriyan <[EMAIL PROTECTED]> wrote:
>
> On Wed, Feb 06, 2008 at 07:49:52AM +1100, Benjamin Herrenschmidt wrote:
> >
> > > so x86_64 will work well?
> > >
> > > the problem is that BIOS does not assign one resource for you tg3. and
> > > kernel
On Wed, Feb 06, 2008 at 07:49:52AM +1100, Benjamin Herrenschmidt wrote:
>
> > so x86_64 will work well?
> >
> > the problem is that BIOS does not assign one resource for you tg3. and
> > kernel pcibios_assign_to_unassign (?) try
> > to assign resource to your card.
>
> But the kernel shouldn't
On Wed, Feb 06, 2008 at 07:49:52AM +1100, Benjamin Herrenschmidt wrote:
so x86_64 will work well?
the problem is that BIOS does not assign one resource for you tg3. and
kernel pcibios_assign_to_unassign (?) try
to assign resource to your card.
But the kernel shouldn't try to assign
On Feb 6, 2008 2:05 AM, Alexey Dobriyan [EMAIL PROTECTED] wrote:
On Wed, Feb 06, 2008 at 07:49:52AM +1100, Benjamin Herrenschmidt wrote:
so x86_64 will work well?
the problem is that BIOS does not assign one resource for you tg3. and
kernel pcibios_assign_to_unassign (?) try
to
BTW, [PATCH] x86_32: fix regression caused by trim ram according to mtrr on
system with 4G more RAM
http://marc.info/?l=linux-kernelm=120229095121673w=2
fixes this box too and I have back all 4G of RAM as a bonus. :-)
You mean you no longer have a problem or does your tg3 issue still
Looks like your attachment got currupted for some reason (got here as a
corrupted bzip2 file that was encoded as plain text).
Ben.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
> so x86_64 will work well?
>
> the problem is that BIOS does not assign one resource for you tg3. and
> kernel pcibios_assign_to_unassign (?) try
> to assign resource to your card.
But the kernel shouldn't try to assign a resource in the 64 bits space
to a card behind a bridge... at least not
On Feb 5, 2008 1:17 AM, Alexey Dobriyan <[EMAIL PROTECTED]> wrote:
> On Tue, Feb 05, 2008 at 08:54:33AM +1100, Benjamin Herrenschmidt wrote:
> >
> > On Mon, 2008-02-04 at 18:12 +0300, Alexey Dobriyan wrote:
> > > Commit c40a22e0ce5eb400f27449e59e43d021bee58b8d aka
> > > "PCI: Fix bus resource
On Feb 5, 2008 1:17 AM, Alexey Dobriyan [EMAIL PROTECTED] wrote:
On Tue, Feb 05, 2008 at 08:54:33AM +1100, Benjamin Herrenschmidt wrote:
On Mon, 2008-02-04 at 18:12 +0300, Alexey Dobriyan wrote:
Commit c40a22e0ce5eb400f27449e59e43d021bee58b8d aka
PCI: Fix bus resource assignment on 32
so x86_64 will work well?
the problem is that BIOS does not assign one resource for you tg3. and
kernel pcibios_assign_to_unassign (?) try
to assign resource to your card.
But the kernel shouldn't try to assign a resource in the 64 bits space
to a card behind a bridge... at least not a
Looks like your attachment got currupted for some reason (got here as a
corrupted bzip2 file that was encoded as plain text).
Ben.
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
And I could also use the lspci output without the patch.
Thanks,
Ben.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at
Oh and send me the output of /proc/iomem as well.
Cheers,
Ben.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at
On Mon, 2008-02-04 at 18:12 +0300, Alexey Dobriyan wrote:
> Commit c40a22e0ce5eb400f27449e59e43d021bee58b8d aka
> "PCI: Fix bus resource assignment on 32 bits with 64b resources"
> renders one tg3-equipped box networkless here.
>
> tg3.c:v3.87 (December 20, 2007)
> tg3:
Commit c40a22e0ce5eb400f27449e59e43d021bee58b8d aka
"PCI: Fix bus resource assignment on 32 bits with 64b resources"
renders one tg3-equipped box networkless here.
tg3.c:v3.87 (December 20, 2007)
tg3: (:02:05.0) phy probe failed, err -19
tg3: Problem fetching
Commit c40a22e0ce5eb400f27449e59e43d021bee58b8d aka
PCI: Fix bus resource assignment on 32 bits with 64b resources
renders one tg3-equipped box networkless here.
tg3.c:v3.87 (December 20, 2007)
tg3: (:02:05.0) phy probe failed, err -19
tg3: Problem fetching invariants
On Mon, 2008-02-04 at 18:12 +0300, Alexey Dobriyan wrote:
Commit c40a22e0ce5eb400f27449e59e43d021bee58b8d aka
PCI: Fix bus resource assignment on 32 bits with 64b resources
renders one tg3-equipped box networkless here.
tg3.c:v3.87 (December 20, 2007)
tg3: (:02:05.0) phy
And I could also use the lspci output without the patch.
Thanks,
Ben.
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at
Oh and send me the output of /proc/iomem as well.
Cheers,
Ben.
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at
30 matches
Mail list logo
