Processes stuck in *unp_m after recent uipc changes

With the latest uipc locking changes, I experienced a hard lockup on
my -current machine. Many processes got stuck in *unp_m state and
ctrl-alt-delete at the console cannot properly restart the machine and
I had to hard-reset (no coredump available). Is there anyway to
diagnose this?

Jiawei

--
"If it looks like a duck, walks like a duck, and quacks like a duck,
then to the end user it's a duck, and end users have made it pretty
clear they want a duck; whether the duck drinks hot chocolate or
coffee is irrelevant."
_______________________________________________
freebsd-current@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@xxxxxxxxxxx"

Relevant Pages

  • OO for 5yr olds.
    ... I do have Duck from the hornby thomas range and its ideal - slow (otherwise ... good at them) but they whizz round too fast and get stuck across points. ... Is the 0-6-0 Thomas as good as and the same speed as Duck? ...
    (uk.rec.models.rail)
  • Re: unkillable mount_smbfs processes
    ... A situation like this - something stuck in devdrn, ... report. ... "If it looks like a duck, walks like a duck, and quacks like a duck, ...
    (freebsd-current)
  • Re: Processes stuck in *unp_m after recent uipc changes
    ... Many processes got stuck in *unp_m state and ctrl-alt-delete at the console cannot properly restart the machine and I had to hard-reset. ...
    (freebsd-current)