From: Pekka Pietikainen <pp@ee.oulu.fi>
To: netdev@oss.sgi.com
Subject: rwlock recursion on CPU#0, netfilter related?
Date: Sun, 25 Sep 2005 13:58:34 +0300 [thread overview]
Message-ID: <20050925105834.GA15243@ee.oulu.fi> (raw)
Just to get a wider audience, somewhere between 2.6.13-git4 and current
(2.6.14-rc2-git4 is the last one I tested, which seems to have some
fixes in this are wrt. git3, but problem remains) my x86_64
crashes quite quickly after boot. Using Fedora devel kernels, I can
probably whip up a vanilla kernel if the maintainers in this area
prefer that.
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=167835
and
https://bugzilla.redhat.com/bugzilla/attachment.cgi?id=119228
apart from the crashes I get funny ping times on the kernels that
break when they're still up
(64 bytes from 10.10.9.1: icmp_seq=0 ttl=255 time=4294971590968 ms)
next reply other threads:[~2005-09-25 10:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-25 10:58 Pekka Pietikainen [this message]
2005-09-25 13:43 ` rwlock recursion on CPU#0, netfilter related? Harald Welte
2005-09-25 20:19 ` Pekka Pietikainen
2005-09-28 14:58 ` Pekka Pietikainen
2005-09-29 12:05 ` Harald Welte
2005-09-30 6:49 ` Funny timestamps (Was: Re: rwlock recursion on CPU#0, netfilter related?) Pekka Pietikainen
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=20050925105834.GA15243@ee.oulu.fi \
--to=pp@ee.oulu.fi \
--cc=netdev@oss.sgi.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.