Re: 2.6.12 breaks 8139cp

Kylene Jo Hall
2005-06-28T14:12:14Z

I believe that the reason that unloading the module does not help is
because the module_exit is calling pci_disable in the tpm_remove
function. I'll generate a patch to remove this.

Additionally this version of the driver was doing a bunch of stuff to
the LPC bus that I have since found not to be necessary and removed in
patches that have been applied to the mm tree and were pushed to
mainline this week. Can anyone verify if this is still happening with
the -mm patch?

Regards,
Kylie

On Tue, 2005-06-28 at 14:32 +0200, Pierre Ossman wrote:
> Pierre Ossman wrote:
> > Hmm... it seems that TPM has something to do with the bug. Not sure why
> > though, can't see anything TPM related in dmesg. If I disable the TPM
> > parts in kconfig then the network works just fine.
> >
> > I'm going to do a test of 2.6.12-rc1 through rc6 today to see where the
> > problem appears.
> >
>
> Confirmed this behaviour. The problem appears in rc1 (where the TPM is
> added). Unloading the module doesn't help, once it has been present the
> system needs a reboot for the network card to function properly.
>
> I don't really see how the TPM can screw things up for the network card
> but I'm guessing it breaks something in the chipset (the TPM module gets
> loaded for the LPC bridge).
>
> (added TPM maintainer and list as cc)
>
> Rgds
> Pierre
>