Re: [RFC] kern/kern_timeout.c rewrite in progress

From: Hans Petter Selasky <hps_at_selasky.org>
Date: Thu, 01 Jan 2015 02:16:50 +0100
On 01/01/15 02:02, Hans Petter Selasky wrote:
> On 12/31/14 23:56, Ivan Klymenko wrote:
>> В Mon, 29 Dec 2014 21:03:24 +0100
>> Hans Petter Selasky <hps_at_selasky.org> пишет:
>>
>
> Hi,
>
> Is your kernel compiled with Witness? Do you see any lock order reversal
> warnings?
>
> Can you do from kgdb:
>
> thread apply all bt
>
> And send me the result off-list?
>
> I'll have a closer look at this tomorrow.
>
>>
>> panic: spin lock held too long
>> http://paste.org.ru/?acf7io
>>
>
> Thank you!
>

Hi,

This backtrace looks incorrect, because I cannot find where teken code 
calls into callout_xxx().

--HPS

cpuid = 2
KDB: stack backtrace:
#0 0xffffffff80a03680 at kdb_backtrace+0x60
#1 0xffffffff809c19a1 at panic+0x1c1
#2 0xffffffff809a3d57 at _mtx_lock_spin_cookie+0x257
#3 0xffffffff809da367 at callout_lock+0x87
#4 0xffffffff809da3c0 at callout_restart_async+0x20
#5 0xffffffff809da22d at callout_reset_sbt_on+0xfd
#6 0xffffffff809da64e at callout_schedule+0x2e
#7 0xffffffff80c6c179 at teken_subr_do_putchar+0x79
#8 0xffffffff80c6b80e at teken_state_init+0x2ae
#9 0xffffffff80c6d78e at teken_input_char+0x4e
#10 0xffffffff80c6bb18 at teken_input+0x28
#11 0xffffffff80a15821 at termcn_cnputc+0xc1
#12 0xffffffff80961dd0 at cnputc+0x80
#13 0xffffffff809620e8 at cnputs+0xb8
#14 0xffffffff80a09561 at putchar+0x151
#15 0xffffffff80a08186 at kvprintf+0xf6
#16 0xffffffff80a09bad at _vprintf+0x8d
#17 0xffffffff80a09dc3 at printf+0x53
Received on Thu Jan 01 2015 - 00:16:14 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:54 UTC