Date: Wed, 19 Feb 2014 14:27:56 +0400 From: Dmitry Sivachenko <trtrmitya@gmail.com> To: Mark Johnston <markj@FreeBSD.org> Cc: stable@freebsd.org Subject: Re: sdt_probe_stub: Why did this get called? Message-ID: <A493B060-F7D6-4A83-B5D7-335EAD820299@gmail.com> In-Reply-To: <CAMw1wOx3rE_rWHueY25MmDYT61tjFEsMt2j9Ph1B2LDPeezW1Q@mail.gmail.com> References: <E8996797-E4D0-4AAA-840A-A3F490B35FA5@gmail.com> <CAMw1wOx3rE_rWHueY25MmDYT61tjFEsMt2j9Ph1B2LDPeezW1Q@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 18 февр. 2014 г., at 20:31, Mark Johnston <markj@FreeBSD.org> wrote: > On Tue, Feb 18, 2014 at 5:34 AM, Dmitry Sivachenko <trtrmitya@gmail.com> wrote: >> Hello! >> >> FreeBSD 10.0-STABLE #0 r262016M >> >> >> During the boot, I see the following line on console: >> sdt_probe_stub: Why did this get called? >> >> What does it mean? > > It means that an SDT probe was somehow enabled without setting the > probe hook (which points to sdt_probe_stub() by default). > > Are you using DTrace on the system? What local modifications have you > made to the code? No modifications to code and I don't use DTrace on that machine (it is just compiled in the kernel). After some digging I found that my ethernet is auto-configured on 100MBit instead of 1000MBit, and after I replaced a patch cord both problems (ethernet speed and the above console message about sdt_probe_stub) disappeared. Sorry for the noise.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?A493B060-F7D6-4A83-B5D7-335EAD820299>