From: Kylene Jo Hall <kjhall@us.ibm.com>
To: Pierre Ossman <drzeus-list@drzeus.cx>
Cc: Bjorn Helgaas <bjorn.helgaas@hp.com>,
LKML <linux-kernel@vger.kernel.org>,
jgarzik@pobox.com, tpmdd-devel@lists.sourceforge.net
Subject: Re: 2.6.12 breaks 8139cp
Date: Tue, 28 Jun 2005 09:09:48 -0500 [thread overview]
Message-ID: <1119967788.6382.7.camel@localhost.localdomain> (raw)
In-Reply-To: <42C1434F.2010003@drzeus.cx>
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
>
next prev parent reply other threads:[~2005-06-28 14:12 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-22 21:03 2.6.12 breaks 8139cp Pierre Ossman
2005-06-22 21:34 ` Bjorn Helgaas
2005-06-23 7:50 ` Pierre Ossman
2005-06-23 12:59 ` Felipe W Damasio
2005-06-23 17:43 ` Bjorn Helgaas
2005-06-23 22:14 ` Pierre Ossman
2005-06-25 2:03 ` Ed Sweetman
2005-06-25 2:18 ` Ed Sweetman
2005-06-25 2:32 ` Ed Sweetman
2005-06-25 3:15 ` Jeff Garzik
2005-06-25 10:34 ` Pierre Ossman
2005-06-26 13:31 ` Ed Sweetman
2005-06-28 6:28 ` Pierre Ossman
2005-06-28 12:32 ` Pierre Ossman
2005-06-28 14:09 ` Kylene Jo Hall [this message]
2005-06-28 14:40 ` Pierre Ossman
2005-06-28 15:08 ` Kylene Jo Hall
2005-06-28 16:51 ` Pierre Ossman
2005-06-28 17:03 ` Kylene Jo Hall
2005-06-29 7:03 ` Pierre Ossman
2005-06-28 17:23 ` Chris Wright
2005-06-28 20:29 ` 2.6.12 breaks 8139cp [PATCH 1 of 2] Kylene Jo Hall
2005-06-28 20:34 ` Chris Wright
2005-06-28 22:10 ` Kylene Jo Hall
2005-06-29 8:22 ` Pierre Ossman
2005-06-29 14:32 ` Kylene Jo Hall
[not found] ` <20050705153512.GJ9046@shell0.pdx.osdl.net>
2005-07-07 20:01 ` Kylene Jo Hall
2005-07-08 6:14 ` Chris Wright
2005-06-28 20:30 ` 2.6.12 breaks 8139cp [PATCH 2 " Kylene Jo Hall
2005-06-23 17:17 ` 2.6.12 breaks 8139cp Roberto Oppedisano
2005-06-23 18:00 ` Bjorn Helgaas
2005-06-23 20:38 ` Ed Sweetman
2005-06-23 20:55 ` Bjorn Helgaas
2005-06-23 21:14 ` Ed Sweetman
2005-06-23 21:07 ` Roberto Oppedisano
-- strict thread matches above, loose matches on Subject: below --
2005-06-26 13:46 Nick Warne
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=1119967788.6382.7.camel@localhost.localdomain \
--to=kjhall@us.ibm.com \
--cc=bjorn.helgaas@hp.com \
--cc=drzeus-list@drzeus.cx \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tpmdd-devel@lists.sourceforge.net \
/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