Date: Mon, 7 Aug 2017 09:19:29 -0700 From: Matt Joras <mjoras@FreeBSD.org> To: Hans Petter Selasky <hps@selasky.org>, Ben RUBSON <ben.rubson@gmail.com>, FreeBSD Net <freebsd-net@freebsd.org> Subject: Re: mlx4en, timer irq @100%... Message-ID: <896dd782-cb2c-0259-65d1-b00daae452de@FreeBSD.org> In-Reply-To: <9c306f10-7c05-d28d-e551-a930603aaafa@selasky.org> References: <BF3A3E47-A726-49FB-B83F-666EFC5C0FF1@gmail.com> <72b9de84-5572-3737-b274-34d2c5cdf634@selasky.org> <91DCB96E-4C08-44C5-94E7-E7C686DEFE5F@gmail.com> <c3fdf0bb-833d-915f-c246-9459819cd825@selasky.org> <4DF74CB8-23D2-4CCF-B699-5B86DAEA65E5@gmail.com> <40602CEA-D417-4E5B-8C68-916958D49A0B@gmail.com> <9c306f10-7c05-d28d-e551-a930603aaafa@selasky.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 08/07/2017 09:11, Hans Petter Selasky wrote: > Hi, > > Try to enter "kgdb" and run: > > thread apply all bt > > Look for the callout function in question. > > --HPS > If you don't have a way to attach kgdb handy you could also break into ddb(4) and run "alltrace". Though gdb would be more useful for an ongoing session if we need more than the backtrace since you could switch to that thread and investigate it directly.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?896dd782-cb2c-0259-65d1-b00daae452de>