Date: Thu, 03 Nov 2005 09:34:18 +0300 From: Boris Samorodov <bsam@ipt.ru> To: Victor Snezhko <snezhko@indorsoft.ru> Cc: Max Laier <max@love2party.net>, freebsd-current@freebsd.org Subject: Re: CURRENT + amd64 + user-ppp = panic Message-ID: <05980805@srv.sem.ipt.ru> In-Reply-To: <u1x1ycmqq.fsf@indorsoft.ru> (Victor Snezhko's message of "Thu, 03 Nov 2005 11:40:45 %2B0600") References: <20051027022313.R675@kushnir1.kiev.ua> <200511021035.22990.max@love2party.net> <20051103001509.C85422@kushnir1.kiev.ua> <200511030059.05946.max@love2party.net> <20051103020404.J85422@kushnir1.kiev.ua> <u1x1ycmqq.fsf@indorsoft.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 03 Nov 2005 11:40:45 +0600 Victor Snezhko wrote: > In the meantime, I want to debug this too. I would insert a panic() > call somewhere in the beginning of nd6_llinfo_settimer(), but there is > a problem. nd6_llinfo_settimer() is called not only when I start ppp, > but at bootup too (at bootup - once, I think that this is due to > initializing lo0 interface, which has a default ipv6 address). Could I > somehow make the kernel not panic at boot time and panic later, when I > call ppp? You may use a flag. Touch /var/run/.boot file. If the flag presents, your panic() doesn't occur. After booting remove the flag and start ppp again. > E.g, how can I know uptime from the kernel mode? WBR -- Boris B. Samorodov, Research Engineer InPharmTech Co, http://www.ipt.ru Telephone & Internet Service Provider
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?05980805>