From: Erik Tews <erik@debian.franken.de>
To: Zilvinas Valinskas <zilvinas@gemtek.lt>
Cc: Jeff Garzik <jgarzik@pobox.com>,
linux-kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.9 rc2 freezing
Date: Wed, 15 Sep 2004 10:25:50 +0200 [thread overview]
Message-ID: <1095236750.3960.23.camel@localhost.localdomain> (raw)
In-Reply-To: <20040913171649.GA24807@gemtek.lt>
Am Mo, den 13.09.2004 schrieb Zilvinas Valinskas um 19:16:
> On Mon, Sep 13, 2004 at 01:12:13PM -0400, Jeff Garzik wrote:
> > I'm totally blind, because I don't see your network driver in that big
> > list of modules.
> >
> > Your network driver should probably be doing dev_kfree_skb_any()
> > somewhere, but isn't.
> >
> > Jeff
> >
> It is compiled in, see :
>
> CONFIG_E100=y
> CONFIG_E100_NAPI=y
>
> Can it be IPsec related ?
I got a similar problem here, I am running 2.6.9-rc2 with acpi patch. I
got an e1000, ipsec is compiled in, modules loaded, racoon started but
no tunnels configured.
The system freezes when I type apt-get update, in the moment apt-get
tries to connect all the mirrors or resolves them.
I did not see any messages, sysrq was not compiled in, so I cannot check
if it still works.
next prev parent reply other threads:[~2004-09-15 8:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-13 16:55 Zilvinas Valinskas
2004-09-13 17:12 ` Jeff Garzik
2004-09-13 17:16 ` Zilvinas Valinskas
2004-09-15 8:25 ` Erik Tews [this message]
2004-09-15 9:58 ` Zilvinas Valinskas
2004-09-15 14:55 ` Ricky Beam
2004-09-15 15:48 ` Lee Revell
2004-09-15 15:58 ` Jeff Garzik
2004-09-15 16:06 ` Lee Revell
2004-09-15 16:11 ` Jeff Garzik
2004-09-15 16:58 ` Ricky Beam
2004-09-15 17:49 ` Lee Revell
2004-09-15 17:52 ` Jeff Garzik
2004-09-15 17:59 ` Lee Revell
2004-09-16 8:39 ` Helge Hafting
2004-09-17 8:05 ` Zilvinas Valinskas
2004-09-17 13:21 ` Zilvinas Valinskas
2004-09-15 16:59 ` Dave Jones
2004-09-13 17:19 ` Zilvinas Valinskas
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=1095236750.3960.23.camel@localhost.localdomain \
--to=erik@debian.franken.de \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zilvinas@gemtek.lt \
/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
Powered by JetHome