Date: Sun, 04 Jul 2010 18:38:39 +0200 From: Gabor Kovesdan <gabor@FreeBSD.org> To: soc-status@freebsd.org Cc: =?UTF-8?B?RWR3YXJkIFRvbWFzeiBOYXBpZXJhxYJh?= <trasz@FreeBSD.org> Subject: Collective resource limits status report #5 Message-ID: <4C30B90F.9040703@FreeBSD.org> In-Reply-To: <4C2761B8.9030800@FreeBSD.org> References: <4C1BCB96.4040608@FreeBSD.org> <AANLkTikwUYWCIvlDQ60L4L8gMcEeDFIV6850csEwuH8E@mail.gmail.com> <4C21CAF0.2040607@FreeBSD.org> <AANLkTikLoskpABjaUlufnBGOBeU-Z62CiuQfH5sDyY1Z@mail.gmail.com> <4C230A0B.3080700@FreeBSD.org> <4C2761B8.9030800@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Since last report, I've resolved the problems that caused kernel panic. The linked list handling now seems to be ok, I've checked it many times but somehow still there's a bug somewhere. I store an entry there but later the job isn't found. I've also added some Robert Watson locking (see rwlock(9), last line :) to check if that helps but it caused another kernel panics, so this is commented out at the moment. Now, I'm working on resolving the locking problem and making the lists actually work. I might try debugging with adding some temporary syscalls to access internal kernel structures or printing out something with a sysctl (this was pgj's idea) so that I can figure out what's going wrong. If you have a better idea or you find something strange in the patch, please let me know. Another issue, I've tried to merge my work into p4 but I got strange problems. I wrote to soc-admins@ and perforce-admin@ regarding this, I hope I can also figure it out soon. For the meantime, I provide a full patch, I think it's still easy to read because the main part of the code resides in sys/kern/kern_jobs.c. http://kovesdan.org/patches/jobs_current.diff Gabor
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4C30B90F.9040703>