Date: Mon, 7 Aug 2017 19:19:29 +0200 From: Ben RUBSON <ben.rubson@gmail.com> To: FreeBSD Net <freebsd-net@freebsd.org> Subject: Re: mlx4en, timer irq @100%... Message-ID: <0DB9F6FF-8BC9-48F5-B359-AC1905B9EB06@gmail.com> In-Reply-To: <896dd782-cb2c-0259-65d1-b00daae452de@FreeBSD.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> <896dd782-cb2c-0259-65d1-b00daae452de@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 07 Aug 2017, at 18:19, Matt Joras <mjoras@FreeBSD.org> wrote: >=20 > On 08/07/2017 09:11, Hans Petter Selasky wrote: >> Hi, >>=20 >> Try to enter "kgdb" and run: >>=20 >> thread apply all bt >>=20 >> Look for the callout function in question. >>=20 >> --HPS >>=20 > 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. >=20 Hi Hans & Matt, Thank you for your answers, glad to hear from you :) So here is the full kgdb(thread apply all bt) command log : https://benrubson.github.io/kgdb.log We found the faulty thread : # procstat -ak | grep "swi4.*tcp" 12 100029 intr swi4: clock (0) tcp_tw_2msl_scan = pfslowtimo softclock_call_cc softclock intr_event_execute_handlers = ithread_loop fork_exit fork_trampoline=20 # kgdb (...) Thread 747 (Thread 100029): #0 sched_switch (td=3D0xfffff8000f337500, newtd=3D0xfffff8010e144000, = flags=3D<value optimized out>) at /usr/src/sys/kern/sched_ule.c:1973 #1 0xfffffe1000f92d80 in ?? () #2 0xfffffe0f8f74b6e0 in ?? () #3 0xffffffff810bd274 in handleevents (now=3D<value optimized out>, = fake=3DError accessing memory address 0xffffffffffffffcc: Bad address. ) at /usr/src/sys/kern/kern_clocksource.c:223 Previous frame inner to this frame (corrupt stack?) (...) Of course let me know if you need further info. Thank you again, Ben
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0DB9F6FF-8BC9-48F5-B359-AC1905B9EB06>