Date: Sat, 27 Oct 2007 16:42:23 +0200 From: Danny Braniss <danny@cs.huji.ac.il> To: hackers@FreeBSD.org Cc: freebsd-current@FreeBSD.org Subject: Re: dump problems Message-ID: <E1Ilmrn-0007Lq-EU@cs1.cs.huji.ac.il> In-Reply-To: <E1IiTeh-0007tt-G6@cs1.cs.huji.ac.il> References: <E1ISdQi-000GkC-4v@cs1.cs.huji.ac.il> <20070904233246.GA2409@epia-2.farid-hajji.net> <E1ISnig-000Nbm-Ep@cs1.cs.huji.ac.il> <043a01c7f202$a7ad0920$f7071b60$@co.uk> <E1IU10R-000MRT-T8@cs1.cs.huji.ac.il> <046801c7f229$a4534510$ecf9cf30$@co.uk> <E1IUcXc-000NdZ-LH@cs1.cs.huji.ac.il> <E1IUePt-000P2R-RM@cs1.cs.huji.ac.il> <E1IiTeh-0007tt-G6@cs1.cs.huji.ac.il>
next in thread | previous in thread | raw e-mail | index | archive | help
to recap: dump will get stuck/deadlock. found the problem, but no solution in sight :-( dump creates 3 processess and syncs with them via kill(2) - don't want to go into the merrits of this - and sometimes: - the signal is received even if it's blocked. - the signal is not received. - it happens mainly on > 2way multicore hosts. all this seems to be a problem in the kernel. need some insight please! thanks, danny PS: sorry for the shortness of the message, anything else will get me to start %$#@! dump, specially tape.c.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E1Ilmrn-0007Lq-EU>