Most recent kernel where this bug did not occur: Nil Distribution: Red Hat Enterprise 4 Hardware Environment: IBM Thinkcenter A51 Software Environment: Linux Problem Description: TG3 cannot be initialized because the upper 32-bit of PCI BAR address get from the hardware is invalid. This fails when kernel try to allocate PCI memory resource. Any Quick fix? Steps to reproduce:
bugme-daemon@bugzilla.kernel.org wrote: > > http://bugzilla.kernel.org/show_bug.cgi?id=5927 > > Summary: TG3 driver unable to get memory resource > Kernel Version: 2.6.15.1 > Status: NEW > Severity: normal > Owner: jgarzik@pobox.com > Submitter: singsingwong2@yahoo.com.hk > > > Most recent kernel where this bug did not occur: Nil > Distribution: Red Hat Enterprise 4 > Hardware Environment: IBM Thinkcenter A51 > Software Environment: Linux > Problem Description: TG3 cannot be initialized because the upper 32-bit of PCI > BAR address get from the hardware is invalid. This fails when kernel try to > allocate PCI memory resource. > Any Quick fix? > Steps to reproduce: Doesn't that mean your hardware is busted? Please share the full dmesg output and output of `lspci -vvxx -s <that device>'
Reply-To: mchan@broadcom.com On Thu, 2006-01-19 at 17:22 -0800, Andrew Morton wrote: > bugme-daemon@bugzilla.kernel.org wrote: > > > > http://bugzilla.kernel.org/show_bug.cgi?id=5927 > > > > Summary: TG3 driver unable to get memory resource > > Kernel Version: 2.6.15.1 > > Status: NEW > > Severity: normal > > Owner: jgarzik@pobox.com > > Submitter: singsingwong2@yahoo.com.hk > > > > > > Most recent kernel where this bug did not occur: Nil > > Distribution: Red Hat Enterprise 4 > > Hardware Environment: IBM Thinkcenter A51 > > Software Environment: Linux > > Problem Description: TG3 cannot be initialized because the upper 32-bit of PCI > > BAR address get from the hardware is invalid. This fails when kernel try to > > allocate PCI memory resource. > > Any Quick fix? > > Steps to reproduce: > > Doesn't that mean your hardware is busted? > It usually means that the BIOS is not initializing the upper 32-bit of the 64-bit BAR properly.
Any update on this problem? Sing, can you attach your boot trace and lspci -vv please (see #1). Thanks.
Please reopen this bug if: - it is still present with kernel 2.6.22 and - you can provide the requested information.