[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: kern/49065: ifconfig tun0 ... sequence locks up system
The following reply was made to PR kern/49065; it has been noted by GNATS.
From: Frank Kardel <kardel%netbsd.org@localhost>
Subject: Re: kern/49065: ifconfig tun0 ... sequence locks up system
Date: Sun, 03 Aug 2014 17:14:32 +0200
Hmmm, LOCKDEBUG gives me:
panic: lockdebug_lookup: uninitialized lock (lock=0xc057e204, from=e8c9e670)
cpu0: Begin traceback...
cpu0: End traceback...
disabling named gets me past that. Strangely on an sysinst upgraded RPI
I cannot reproduce the issue, I thought...
But I bisected through the services running (namely named, mdnsd).
Collected reproduceable facts:
- It turns out that *running mdnsd* will trigger the locking issue.
- named triggers only a LOCKDEBUG (uninitialized lock) panic (see
So it looks like mdnsd's handling of the interfaces will leave a lock on
the socket structure AFAICS.
On 08/03/14 14:55, Nick Hudson wrote:
> The following reply was made to PR kern/49065; it has been noted by GNATS.
> From: Nick Hudson <skrll%netbsd.org@localhost>
> To: gnats-bugs%NetBSD.org@localhost
> Cc: kardel%netbsd.org@localhost, kern-bug-people%netbsd.org@localhost,
> gnats-admin%netbsd.org@localhost, netbsd-bugs%netbsd.org@localhost
> Subject: Re: kern/49065: ifconfig tun0 ... sequence locks up system
> Date: Sun, 03 Aug 2014 12:04:13 +0100
> What's you full kernel config? Have you tried with LOCKDEBUG?
Main Index |
Thread Index |