Date: Mon, 16 Dec 2013 19:18:20 -0500 From: Eitan Adler <lists@eitanadler.com> To: Aleksandr Rybalko <ray@dlink.ua> Cc: Alexander Motin <mav@freebsd.org>, freebsd-current Current <freebsd-current@freebsd.org> Subject: Re: r259286 panic Message-ID: <CAF6rxgm064qHPQtwy_xpVo7Ckee9KK56dsaPs%2BVCsv5Ri_R2Qg@mail.gmail.com> In-Reply-To: <CAJ1Oi8HhRSGvuPVb_sQLqzeUAKy=oQFKRa2PO8ggwx6pBKS9Hg@mail.gmail.com> References: <CAF6rxg=toapB1UuoqtmwT7Hwz=mzrVM9Zd7xgzWSM%2B9-WHydCw@mail.gmail.com> <CAF6rxg=eTf-VLDfjA=pA85idy1wFy=dgh2GgqDgFjJ%2B1kr0PoA@mail.gmail.com> <52AEF86B.5080600@FreeBSD.org> <CAJ1Oi8HhRSGvuPVb_sQLqzeUAKy=oQFKRa2PO8ggwx6pBKS9Hg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Dec 16, 2013 at 6:41 PM, Aleksandr Rybalko <ray@dlink.ua> wrote: > > Hi guys! > > I've investigate problem a bit. And can say that callout initialized with > callout_int(), w/o mpsafe flag: > callout_init(&vw->vw_proc_dead_timer, 0); > [sys/dev/vt/vt_core.c:1714] > And callout_init did not set CALLOUT_RETURNUNLOCKED flag, and assign it's > lock object to Giant, but where Giant lost on exit from callout I dunno :) > > seems some bug somewhere much deep. > > Eitan, do this 100% reproducible? If so, can you please try to replace > callout_init(&vw->vw_proc_dead_timer, 0); > with > callout_init(&vw->vw_proc_dead_timer, CALLOUT_MPSAFE); > at [sys/dev/vt/vt_core.c:1714] ? I can not reproduce it, despite trying. >From memory here is what I saw: - X seemed frozen so I VT switched to the terminal - this took a long time - I plugged in a USB mouse - instant panic I have no idea if any of those are related (in particular, was the mouse just a fluke?). -- Eitan Adler
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAF6rxgm064qHPQtwy_xpVo7Ckee9KK56dsaPs%2BVCsv5Ri_R2Qg>