Vladimir Kushnir <vkushnir_at_i.kiev.ua> writes: > On Thu, 3 Nov 2005, Max Laier wrote: > >>> >>> Here it is: right before panic it prints >>> >>> For 0xffffff0017531100 -1 ticks >>> For 0xffffff0017531100 -1 ticks >> >> This results in two consecutive callout_stop() calls, but shouldn't hurt as >> callout_stop is protected against that. >> >> Do you get a dump for this? Can you compare this pointer to the global >> llinfo_nd6 and see if "c" from the softclock() frame is related (or >> maybe the previous item in the list TAILQ). > Sorry I'm not very goot at debugging. Would you please give me some > instructions (lamer's level, preferably :-)). And anyway I'll be able > to do it tomorrow only. 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? E.g, how can I know uptime from the kernel mode? -- WBR, Victor V. Snezhko EMail: snezhko_at_indorsoft.ruReceived on Thu Nov 03 2005 - 04:40:57 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:47 UTC