That looks like a different problem.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Jun 14 10:36:08 calvin syslogd: kernel boot file is /boot/kernel/kernel
Jun 14 10:36:08 calvin kernel: panic: lock (sleep mutex) inp not locked @
/usr/src/sys/netinet/tcp_subr.c:1069
Thanks for the bug report, Sid. This panic should be addressed by the
following commit:
hsu
An Tue, Jun 11, 2002 at 11:06:44AM -0700, Edwin Culp schreib :
Quoting Steve Ames [EMAIL PROTECTED]:
| On Tue, Jun 11, 2002 at 10:51:25PM +0530, Sid Carter wrote:
| An Tue, Jun 11, 2002 at 04:58:39PM +0200, Thomas Ugland schreib :
I get blown away with network setup with a Fatal trap 12,
An Fri, Jun 14, 2002 at 12:43:51AM +0530, Sid Carter schreib :
An Tue, Jun 11, 2002 at 11:06:44AM -0700, Edwin Culp schreib :
Quoting Steve Ames [EMAIL PROTECTED]:
| On Tue, Jun 11, 2002 at 10:51:25PM +0530, Sid Carter wrote:
| An Tue, Jun 11, 2002 at 04:58:39PM +0200, Thomas Ugland
On 13-Jun-2002 Sid Carter wrote:
An Tue, Jun 11, 2002 at 11:06:44AM -0700, Edwin Culp schreib :
Quoting Steve Ames [EMAIL PROTECTED]:
| On Tue, Jun 11, 2002 at 10:51:25PM +0530, Sid Carter wrote:
| An Tue, Jun 11, 2002 at 04:58:39PM +0200, Thomas Ugland schreib :
I get blown away with
Jun 11 22:34:47 calvin kernel: lock order reversal
Jun 11 22:34:47 calvin kernel: 1st 0xd311c2f8 inp (inp) @
/usr/src/sys/netinet/tcp_usrreq.c:581
Jun 11 22:34:47 calvin kernel: 2nd 0xc04a5340 Giant (Giant) @
/usr/src/sys/kern/subr_trap.c:76
Jun 11 22:34:47 calvin kernel:
Duplicate inp warnings occur whenever 2 inp locks are held, even though they're
on different inps, because all the inp locks are named inp. I've
investigated a couple of these already and they were all places where
we intended to grab two inp locks. So, for the most part, these warning are
On 13-Jun-2002 Jeffrey Hsu wrote:
Duplicate inp warnings occur whenever 2 inp locks are held, even though they're
on different inps, because all the inp locks are named inp. I've
investigated a couple of these already and they were all places where
we intended to grab two inp locks. So,
An Thu, Jun 13, 2002 at 02:19:52PM -0700, Jeffrey Hsu schreib :
Duplicate inp warnings occur whenever 2 inp locks are held, even though they're
on different inps, because all the inp locks are named inp. I've
investigated a couple of these already and they were all places where
we intended
An Fri, Jun 14, 2002 at 10:44:59AM +0530, Sid Carter schreib :
An Thu, Jun 13, 2002 at 02:19:52PM -0700, Jeffrey Hsu schreib :
Duplicate inp warnings occur whenever 2 inp locks are held, even though they're
on different inps, because all the inp locks are named inp. I've
investigated a
System crashed after updating today.
During the start of system services, in specific
at the start of sendmail the system crashes with
the new kernel. :/
uname -a:
-
FreeBSD vampire.lothlorien.no 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Tue
Jun 11 15:41:09 CEST 2002
System crashed after updating today.
During the start of system services, in specific
at the start of sendmail the system crashes with
the new kernel. :/
There are some problems with the inpcb locking:
- attempts to destroy held lock in in_pcbdetach.
- typo in unlocking
An Tue, Jun 11, 2002 at 04:58:39PM +0200, Thomas Ugland schreib :
System crashed after updating today.
During the start of system services, in specific
at the start of sendmail the system crashes with
the new kernel. :/
uname -a:
-
FreeBSD vampire.lothlorien.no 5.0-CURRENT FreeBSD
On Tue, Jun 11, 2002 at 10:51:25PM +0530, Sid Carter wrote:
An Tue, Jun 11, 2002 at 04:58:39PM +0200, Thomas Ugland schreib :
System crashed after updating today.
During the start of system services, in specific
at the start of sendmail the system crashes with
the new kernel. :/
uname
Quoting Steve Ames [EMAIL PROTECTED]:
| On Tue, Jun 11, 2002 at 10:51:25PM +0530, Sid Carter wrote:
| An Tue, Jun 11, 2002 at 04:58:39PM +0200, Thomas Ugland schreib :
| System crashed after updating today.
| During the start of system services, in specific
| at the start of sendmail the
On Tue, Jun 11, 2002 at 12:28:48PM -0500, Steve Ames wrote:
You got way more info than I did. With this mornings -CURRENT (around 9AM EDT):
Jun 11 09:22:10 : Doing initial network setup:
Jun 11 09:22:10 : host.conf
Jun 11 09:22:10 : hostname
Jun 11 09:22:10 : .
Jun 11 09:22:10 :
Jun
typo in unlocking (causing recursive lock instead)
Fixed. Thanks.
lack of inet6 support for inpcb locking, e.g. no
handling of locks in in6_pcbdetach.
attempts to destroy held lock in in_pcbdetach
Gurg, IPv6 isn't locked up yet! These must be the result of inadvertent
17 matches
Mail list logo
