On 31/08/2015 22:10, Hans Petter Selasky wrote:
> Hi Andriy,
>
> On 08/31/15 18:46, Andriy Gapon wrote:
>> On 30/08/2015 22:09, Andriy Gapon wrote:
>>> On 30/08/2015 19:16, Konstantin Belousov wrote:
This is strange, I do not think that could be a right explanation of this
issue. The ta
On 03.09.2015 20:24, Andriy Gapon wrote:
> On 30/08/2015 22: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 judgin
On 30/08/2015 22: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 = ttm_bo_delayed_workqueue it
>
Hi Andriy,
On 08/31/15 18:46, Andriy Gapon wrote:
On 30/08/2015 22:09, Andriy Gapon wrote:
On 30/08/2015 19:16, Konstantin Belousov wrote:
This is strange, I do not think that could be a right explanation of this
issue. The taskqueue callout is initialized with the mutex, which means
that the
On 30/08/2015 22:09, Andriy Gapon wrote:
> On 30/08/2015 19:16, Konstantin Belousov wrote:
>> This is strange, I do not think that could be a right explanation of this
>> issue. The taskqueue callout is initialized with the mutex, which means
>> that the callout_stop() caller
>> - must own the mut
On 31.08.2015 12:58, Oliver Pinter wrote:
> 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 pani
On 8/31/15, Jean-Sébastien Pédron 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 judgi
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 = ttm_bo_delayed_workqueue it
>
On 30/08/2015 19:16, Konstantin Belousov wrote:
> This is strange, I do not think that could be a right explanation of this
> issue. The taskqueue callout is initialized with the mutex, which means
> that the callout_stop() caller
> - must own the mutex;
> - is synchronous with the callout.
> In o
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 = ttm_bo_delayed_workqueue it was
involved. But there was no steady system load
problem be already fixed by more
> recent changes?
>
> r286985
>
> panic: Stray timeout
>
> (kgdb) bt
> #0 doadump (textdump=1) at /usr/src/sys/kern/kern_shutdown.c:260
> #1 0x8063236f in kern_reboot (howto=260) at
> /usr/src/sys/kern/kern_shutdown.c:328
>
I've got the following kernel panic seemingly at random.
I have been using the kernel for about a week without any issues and I wasn't
doing anything special when the panic occurred.
Does this panic ring any bells? Could the problem be already fixed by more
recent changes?
r286985
pa
12 matches
Mail list logo
