Date: Mon, 31 Aug 2015 12:58:01 +0200 From: Oliver Pinter <oliver.pinter@hardenedbsd.org> To: =?UTF-8?B?SmVhbi1Tw6liYXN0aWVuIFDDqWRyb24=?= <dumbbell@freebsd.org> Cc: freebsd-current@freebsd.org Subject: Re: panic: Stray timeout Message-ID: <CAPQ4fftscg9qLHO54s3zO9gTdUe4n36Und22WSc7Hbtozcv_uQ@mail.gmail.com> In-Reply-To: <55E41522.7070409@FreeBSD.org> References: <55E2DA91.6080206@FreeBSD.org> <CAPQ4ffs9FJpkExmtzVePO71=ezBKp6ZR-fPB-PjEO2ko32RHcw@mail.gmail.com> <55E353E1.6050605@FreeBSD.org> <55E41522.7070409@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 8/31/15, Jean-S=C3=A9bastien P=C3=A9dron <dumbbell@freebsd.org> wrote: > On 30.08.2015 21:05, Andriy Gapon wrote: >> On 30/08/2015 21:37, Oliver Pinter wrote: >>> You have a running Xorg with radeonkms driver, and this issue >>> occurrence under high load (for example parallel buildworld)? >> >> I use radonkms indeed and judging from ta_func =3D ttm_bo_delayed_workqu= eue >> it was >> involved. But there was no steady system load before the crash, perhaps >> there >> was a spike though. > > I get this panic several times a week since around February this year. > It appeared without any commit to TTM or the Radeon driver. It happens > no matter the load for me. I got this panic, and I have somewhere a kernel and a coredump on my other machine. I got this panic only when I put my machine under heavy load and use X with randonkms driver. When I didn't use X and start the build under vt, I newer got this panic. > > So far, I never found the cause, even though I spent a lot of time > reading TTM, subr_taskqueue.c and kern_timeout.c. > > So, this is a simple "me too" :-/ > > -- > Jean-S=C3=A9bastien P=C3=A9dron > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPQ4fftscg9qLHO54s3zO9gTdUe4n36Und22WSc7Hbtozcv_uQ>