tmpfs deadlock on stable/9
Dear colleagues, I have ports tinderbox runnign on stable/9-amd64, with working directories on tmpfs. I have two consecutive tmpfs deadlocks like root@beaver:/usr/local/tb/scripts# ps t2 PID TT STATTIME COMMAND 2337 2 Is 0:00.04 /bin/tcsh 3079 2 I0:00.01 sudo -sE 3260 2 I0:00.02 /bin/tcsh 20309 2 I+ 0:00.06 /bin/sh ./tc tinderbuild -nullfs -norebuild -b 9-i386-RiNet 27035 2 S+ 0:00.13 make PACKAGES=/usr/local/tb/packages/9-i386-RiNet -k -j1 all 46470 2 I+ 0:00.00 sh -ev 46471 2 I+ 0:00.01 /bin/sh /usr/local/tb/scripts/lib/portbuild 9-i386-RiNet 9-i386 RiNet -nullfs gsm-1.0.13.tbz /usr/ports/audio/gsm 46677 2 I+ 0:00.00 /bin/sh /buildscript /usr/ports/audio/gsm 2 46766 2 I+ 0:00.00 /pnohang 7200 /tmp/make.log4 gsm-1.0.13 make build 46767 2 I+ 0:00.02 make build 46768 2 I+ 0:00.00 /pnohang 7200 /tmp/make.log4 gsm-1.0.13 make build 46789 2 I+ 0:00.00 [sh] 46790 2 D+ 0:00.01 make -f Makefile -j4 all 46918 2 I+ 0:00.00 sh -ev 46926 2 I+ 0:00.00 sh -ev 46928 2 Z+ 0:00.09 defunct 46938 2 D+ 0:00.00 mv gsm_create.o ./src/gsm_create.o 46940 2 D+ 0:00.00 mv gsm_print.o ./src/gsm_print.o (this is parallel build, last 2 rm's are deadlocked on tmpfs) what kind of additional info should I send? I have debugging turned on in kernel, if it's needed. Thanks! -- Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] [ FreeBSD committer: ma...@freebsd.org ] *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- ma...@rinet.ru *** ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: tmpfs deadlock on stable/9
On Wed, Dec 07, 2011 at 01:57:08PM +0400, Dmitry Morozovsky wrote: Dear colleagues, I have ports tinderbox runnign on stable/9-amd64, with working directories on tmpfs. I have two consecutive tmpfs deadlocks like root@beaver:/usr/local/tb/scripts# ps t2 PID TT STATTIME COMMAND 2337 2 Is 0:00.04 /bin/tcsh 3079 2 I0:00.01 sudo -sE 3260 2 I0:00.02 /bin/tcsh 20309 2 I+ 0:00.06 /bin/sh ./tc tinderbuild -nullfs -norebuild -b 9-i386-RiNet 27035 2 S+ 0:00.13 make PACKAGES=/usr/local/tb/packages/9-i386-RiNet -k -j1 all 46470 2 I+ 0:00.00 sh -ev 46471 2 I+ 0:00.01 /bin/sh /usr/local/tb/scripts/lib/portbuild 9-i386-RiNet 9-i386 RiNet -nullfs gsm-1.0.13.tbz /usr/ports/audio/gsm 46677 2 I+ 0:00.00 /bin/sh /buildscript /usr/ports/audio/gsm 2 46766 2 I+ 0:00.00 /pnohang 7200 /tmp/make.log4 gsm-1.0.13 make build 46767 2 I+ 0:00.02 make build 46768 2 I+ 0:00.00 /pnohang 7200 /tmp/make.log4 gsm-1.0.13 make build 46789 2 I+ 0:00.00 [sh] 46790 2 D+ 0:00.01 make -f Makefile -j4 all 46918 2 I+ 0:00.00 sh -ev 46926 2 I+ 0:00.00 sh -ev 46928 2 Z+ 0:00.09 defunct 46938 2 D+ 0:00.00 mv gsm_create.o ./src/gsm_create.o 46940 2 D+ 0:00.00 mv gsm_print.o ./src/gsm_print.o (this is parallel build, last 2 rm's are deadlocked on tmpfs) what kind of additional info should I send? I have debugging turned on in kernel, if it's needed. http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug-deadlocks.html No, I do not promise to look into it. pgpQrBHe06ciC.pgp Description: PGP signature
Re: tmpfs deadlock on stable/9
On Wed, 7 Dec 2011, Kostik Belousov wrote: I have ports tinderbox runnign on stable/9-amd64, with working directories on tmpfs. I have two consecutive tmpfs deadlocks like root@beaver:/usr/local/tb/scripts# ps t2 PID TT STATTIME COMMAND 2337 2 Is 0:00.04 /bin/tcsh 3079 2 I0:00.01 sudo -sE 3260 2 I0:00.02 /bin/tcsh 20309 2 I+ 0:00.06 /bin/sh ./tc tinderbuild -nullfs -norebuild -b 9-i386-RiNet 27035 2 S+ 0:00.13 make PACKAGES=/usr/local/tb/packages/9-i386-RiNet -k -j1 all 46470 2 I+ 0:00.00 sh -ev 46471 2 I+ 0:00.01 /bin/sh /usr/local/tb/scripts/lib/portbuild 9-i386-RiNet 9-i386 RiNet -nullfs gsm-1.0.13.tbz /usr/ports/audio/gsm 46677 2 I+ 0:00.00 /bin/sh /buildscript /usr/ports/audio/gsm 2 46766 2 I+ 0:00.00 /pnohang 7200 /tmp/make.log4 gsm-1.0.13 make build 46767 2 I+ 0:00.02 make build 46768 2 I+ 0:00.00 /pnohang 7200 /tmp/make.log4 gsm-1.0.13 make build 46789 2 I+ 0:00.00 [sh] 46790 2 D+ 0:00.01 make -f Makefile -j4 all 46918 2 I+ 0:00.00 sh -ev 46926 2 I+ 0:00.00 sh -ev 46928 2 Z+ 0:00.09 defunct 46938 2 D+ 0:00.00 mv gsm_create.o ./src/gsm_create.o 46940 2 D+ 0:00.00 mv gsm_print.o ./src/gsm_print.o (this is parallel build, last 2 rm's are deadlocked on tmpfs) what kind of additional info should I send? I have debugging turned on in kernel, if it's needed. http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug-deadlocks.html No, I do not promise to look into it. It is available at http://bsd.woozle.net/tmpfs-lock-20111207.txt (~260k) BTW, at least some of the debugger commands referenced (show locks, show alllocks) are no longer exist Thank you! -- Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] [ FreeBSD committer: ma...@freebsd.org ] *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- ma...@rinet.ru *** ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: tmpfs deadlock on stable/9
On Wed, Dec 07, 2011 at 09:59:32PM +0400, Dmitry Morozovsky wrote: On Wed, 7 Dec 2011, Kostik Belousov wrote: I have ports tinderbox runnign on stable/9-amd64, with working directories on tmpfs. I have two consecutive tmpfs deadlocks like root@beaver:/usr/local/tb/scripts# ps t2 PID TT STATTIME COMMAND 2337 2 Is 0:00.04 /bin/tcsh 3079 2 I0:00.01 sudo -sE 3260 2 I0:00.02 /bin/tcsh 20309 2 I+ 0:00.06 /bin/sh ./tc tinderbuild -nullfs -norebuild -b 9-i386-RiNet 27035 2 S+ 0:00.13 make PACKAGES=/usr/local/tb/packages/9-i386-RiNet -k -j1 all 46470 2 I+ 0:00.00 sh -ev 46471 2 I+ 0:00.01 /bin/sh /usr/local/tb/scripts/lib/portbuild 9-i386-RiNet 9-i386 RiNet -nullfs gsm-1.0.13.tbz /usr/ports/audio/gsm 46677 2 I+ 0:00.00 /bin/sh /buildscript /usr/ports/audio/gsm 2 46766 2 I+ 0:00.00 /pnohang 7200 /tmp/make.log4 gsm-1.0.13 make build 46767 2 I+ 0:00.02 make build 46768 2 I+ 0:00.00 /pnohang 7200 /tmp/make.log4 gsm-1.0.13 make build 46789 2 I+ 0:00.00 [sh] 46790 2 D+ 0:00.01 make -f Makefile -j4 all 46918 2 I+ 0:00.00 sh -ev 46926 2 I+ 0:00.00 sh -ev 46928 2 Z+ 0:00.09 defunct 46938 2 D+ 0:00.00 mv gsm_create.o ./src/gsm_create.o 46940 2 D+ 0:00.00 mv gsm_print.o ./src/gsm_print.o (this is parallel build, last 2 rm's are deadlocked on tmpfs) what kind of additional info should I send? I have debugging turned on in kernel, if it's needed. http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug-deadlocks.html No, I do not promise to look into it. It is available at http://bsd.woozle.net/tmpfs-lock-20111207.txt (~260k) BTW, at least some of the debugger commands referenced (show locks, show alllocks) are no longer exist This means that you do not have witness in your kernel. Look at the reference I pointed you once more. pgpcWVtYWuC4L.pgp Description: PGP signature
Re: tmpfs deadlock on stable/9
On Wed, 7 Dec 2011, Kostik Belousov wrote: It is available at http://bsd.woozle.net/tmpfs-lock-20111207.txt (~260k) BTW, at least some of the debugger commands referenced (show locks, show alllocks) are no longer exist This means that you do not have witness in your kernel. Look at the reference I pointed you once more. Ah I see, my bad. I'll test this with WITNESS-enabled kernel tomorrow and return with updated results. -- Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] [ FreeBSD committer: ma...@freebsd.org ] *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- ma...@rinet.ru *** ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Sporadic 9.0-RC2 boot-time panic
On 12/5/11 9:39 PM, Mike Andrews wrote: On 12/1/2011 6:03 PM, Mike Andrews wrote: On 11/28/11 5:48 PM, Ronald Klop wrote: On Mon, 28 Nov 2011 23:37:27 +0100, Mike Andrews mandr...@bit0.com wrote: *Sometimes* when booting 9.0-RC2 on *some* of my machines, I'll get one of the following two panics during multiuser startup, usually while running the /usr/local/etc/rc.d scripts. (The instruction pointer is always exactly one of these two, and they look fairly related.) If after two or three reboots it manages to not panic, the system will run perfectly stable. FYI this is still happening on 9.0-RC3 -- r228247 to be precise. It only seems to be happening on one particular model of motherboard (Supermicro X8STi-F) but it is happening on several identical machines with them -- running on several other (mostly Supermicro) boards is just fine, including at least one with the exact same 82574L NICs. Whoever's wanting to work on this, contact me off-list to get some more up to date console logs and the kernel config. ...or just look at the newly opened kern/163117 PR. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org