DragonFly bugs List (threaded) for 2004-06
Re: Boot hangs starting postfix
On Sun, Jun 13, 2004 at 12:13:41PM -0700, Matthew Dillon wrote:
> Please try this debugging patch. It doesn't fix anything but it adds
> some debugging printfs that I am hoping will help Joerg, Hiten, and I
> figure out what is going on. I also tsleep() for a few ticks to
> (hopefully) prevent livelock from locking up the whole system.
> What I am guessing you will see is a continuous stream of messages
> on the console from two different PIDs when it gets to the postfix
> startup, but you should still be able to ssh into the box and take
> a snapshot by running 'dmesg'.
> p.s. if there is some sort of race going on the printf() might interfere
> with it and stop the livelock, but if that occurs it should not be
> considered fixed :-).
[joseph, if you happen to have corrupted messages in the queue, please don't
remove it before giving other people a clue to fix this lock up.]
Yes, this at least keeps ssh alive, and the following messages repeated
until I removed corrupted messages (files in /var/spool/postfix/corrupt/)
Jun 14 10:46:55 fred /kernel: lf_setlock: 0xcf8df6d4 pid 0 type 3 flags 00000030
Jun 14 10:46:55 fred /kernel: lf_setlock: 0xcf8df7f4 pid 0 type 3 flags 00000030
I was so stupid that I didn't keep the corrupted messages, and
now older kernel(without your patch) doesn't lock up anymore!
Just creating pair of empty files in the corrupt/ directory doesn't
> Index: kern_lockf.c