On Mon, Jan 29, 2018 at 10:42:20AM +0100, Martin Pieuchot wrote:
> Hello Artturi,
>
> On 28/01/18(Sun) 09:08, Artturi Alm wrote:
> > >Synopsis: stuck in netlock
> > >Category: amd64
> > >Environment:
> > System : OpenBSD 6.2
> > Details : OpenBSD 6.2-current (GENERIC.MP) #333: Sun Jan 7
> > 09:13:00 MST 2018
> >
> > [email protected]:/usr/src/sys/arch/amd64/compile/GENERIC.MP
> >
> > Architecture: OpenBSD.amd64
> > Machine : amd64
> > >Description:
> > processes getting stuck w/STATE=netlock, kill has no effect.
> > >How-To-Repeat:
> > using the desktop normally, until trying to restart chrome ends
> > up failing.
>
> What do you mean with "using the desktop normally"? Which applications
> are you using? Which browser plugins? Can you find out the minimum
> setup to reproduce this deadlock?
>
I had mupdf, gvim, weechat and chromium running out of packages, not much
else even installed, and no browser plugins.
if i had only one machine to use, this would be it, so kind of hard to
minimize the setup as i had +24hrs of use(or atleast uptime) before this
got triggered.
> > I've had this happen to me atleast twice in the last few of weeks.
>
> Do you know how to reproduce it easily?
>
No i don't, but i will try to stay alert for this to notice it before i go
killing stuff randomly in despair.
> > At first time i noticed how trying to launch chrome did lock up
> > all the other processes in netlock, and "pkill chrome" did allow
> > the system to recover, i was unable to figure out what was wrong
> > and rebooting did make everything work again, while ie.
> > removing ~/.cache & ~/.config did not.
>
> So the deadlock is related to your chrome usage?
>
Possibly, i've an issue with crome, where it will eventually stop playing
videos.
as an example let's say i've got +50 tabs open in a single "main"window,
and then open a second one with "chromium --incognito" and make it play
some playlist from youtube, once the playback ceases(at the beginning
of a new vid). i have to restart all chrome processes to have it continue.
i was guessing it's not related, as i've had this playback issues like
before 6.2 iirc., and even when playback is not working, it does keep
downloading/buffering the video and everything else does work w/o issues
in the other chrome window.
> > long before running the "ps cl" below, i had already killed all
> > the xterm-windows those processes were in. cwm(1) was unable to
> > kill some of those, but xkill did not.
>
> Well killing process waiting for the 'netlock' won't help. What has to
> be find is which process is holding it. For that we need the full ps
> output, including kernel and userland threads.
Ok, i'll get those if/when i run into this again.
> >
> > after exiting X w/ctrl+alt+backspace(iirc?) i didn't get back to
> > $-prompt, and ^T did show xauth stuck in netlock..
> > i guess it's obvious where it was heading; so i got pics of
> > "# reboot -nq" failing because stuck in the fckng netlock -_-
> >
> > i do have ddb.{panic,console,log}=1, but
> > "# sysctl ddb.trigger=1" ==
> > "sysctl: ddb.trigger: Operation not supported by device"
>
> Not having DDB access will limit the debugging experience. Are you sure
> you tried to enter it on your console?
>
Yes, i had already exited X, or do you mean above would only work from
what i get into with ctrl+alt+f1? and not ie. ctrl+alt+f2?
using the first VT(or whatever those are) was impossible as there
was the xauth locked up giving me no prompt..
> > ?? so i had no option but "virsh reset <domain>"...
>
> Did you try top(1)? What were the kernel processes doing?
Yes, but i didn't pay attention to anything but how weechat
went waiting on netlock if i launched chrome.
on first time i ran into it, i think launching chrome froze systat too.
