From owner-freebsd-stable@FreeBSD.ORG Sun Jul 2 01:47:25 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F029E16A52D for ; Sun, 2 Jul 2006 01:47:24 +0000 (UTC) (envelope-from lists@stringsutils.com) Received: from zoraida.natserv.net (p65-147.acedsl.com [66.114.65.147]) by mx1.FreeBSD.org (Postfix) with ESMTP id CFDE544FF7 for ; Sun, 2 Jul 2006 01:25:19 +0000 (GMT) (envelope-from lists@stringsutils.com) Received: from zoraida.natserv.net (localhost.natserv.net [127.0.0.1]) by zoraida.natserv.net (Postfix) with ESMTP id F0F62B825 for ; Sat, 1 Jul 2006 21:25:18 -0400 (EDT) Received: from zoraida.natserv.net (zoraida.natserv.net [66.114.65.147]) by zoraida.natserv.net (Postfix) with ESMTP id C7208B81F for ; Sat, 1 Jul 2006 21:25:18 -0400 (EDT) Message-ID: X-Mailer: http://www.courier-mta.org/cone/ From: Francisco Reyes To: FreeBSD Stable List Date: Sat, 01 Jul 2006 21:25:18 -0400 Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset="US-ASCII" Content-Disposition: inline Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Subject: High vmstat, filesystem unresponsive then hang 6.1 Stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Jul 2006 01:47:25 -0000 I believe this may be related to the NFS issues mentioned recent, but hopefully I may have captured enough info to help others troubleshoot.. I got the header of some ps commands.. and when was about to do full listing of the same ps commands to files.. the machine hung up. The machine is 6.1 Stable around 6-25 ( plus or minus 1 day). iostat 5 (not much of a load) tty da0 cpu tin tout KB/t tps MB/s us ni sy in id 0 31 17.71 125 2.17 20 0 5 1 74 0 26 8.57 23 0.19 0 0 1 0 99 0 9 33.73 10 0.34 0 0 0 0 99 0 21 8.42 18 0.15 0 0 1 1 99 0 9 15.92 58 0.90 0 0 0 0 99 0 9 15.18 7 0.10 0 0 0 0 99 0 53 12.93 9 0.11 0 0 1 0 99 0 31 5.17 58 0.29 0 0 1 1 99 vmstat 5 (very high 'b' column) procs memory page disk faults cpu r b w avm fre flt re pi po fr sr da0 in sy cs us sy id 0 248 2 1410436 110728 1519 2 0 0 1644 264 0 4481 8862 9168 20 6 74 0 248 0 1410436 110796 0 0 0 0 13 0 4 700 40 1426 0 1 99 0 248 0 1410436 110764 1 0 0 0 39 0 14 1253 722 2615 0 1 99 0 248 0 1410436 110720 1 0 0 0 10 0 5 407 396 899 0 1 99 0 248 0 1410436 110704 1 0 0 0 60 0 21 2822 360 5695 0 2 98 0 248 0 1410436 110684 1 0 0 0 10 0 7 538 434 1166 0 1 99 0 248 0 1410436 110668 0 0 0 0 75 0 51 576 163 1026 0 0 99 0 248 0 1410436 110696 0 0 0 0 23 0 31 1171 190 2271 0 1 99 vmstat 5 procs memory page disk faults cpu r b w avm fre flt re pi po fr sr da0 in sy cs us sy id 0 250 1 1399688 152000 1517 2 0 0 1643 264 0 4479 8853 9163 20 6 74 0 250 0 1399688 151968 2 0 0 0 25 0 28 1395 966 2852 0 2 98 0 250 0 1399692 151892 1 0 0 0 12 0 6 446 540 986 0 0 99 0 250 2 1399692 151604 1 0 0 0 50 0 37 803 675 1611 0 1 99 Don't recall which ps.. 411 1 0 ufs ?? Ds 0:04.81 /usr/sbin/mountd -r 37675 650 0 ufs ?? D 0:00.46 /usr/bin/perl /data/backaway/mailarchive/client/bin/smtpproxy 127.0.0.1:10026 127.0.0.1:10025 (perl5.8.7) 37919 650 0 ufs ?? D 0:00.46 /usr/bin/perl /data/backaway/mailarchive/client/bin/smtpproxy 127.0.0.1:10026 127.0.0.1:10025 (perl5.8.7) 39306 650 0 ufs ?? D 0:00.39 /usr/bin/perl /data/backaway/mailarchive/client/bin/smtpproxy 127.0.0.1:10026 127.0.0.1:10025 (perl5.8.7) 40214 38649 4100 ufs ?? Ds 0:00.00 /usr/local/bin/maildrop -d nbilous@dialonewolfedale.com 40220 32943 4100 ufs ?? Ds 0:00.00 /usr/local/bin/maildrop -d jrowe@zoofriends.org 40223 33257 4100 ufs ?? Ds 0:00.00 /usr/local/bin/maildrop -d logmonitoring@ewarna.com 40226 32942 4100 ufs ?? Ds 0:00.00 /usr/local/bin/maildrop -d nbilous@dialonewolfedale.com 40228 33199 4100 ufs ?? Ds 0:00.00 /usr/local/bin/maildrop -d enquiries@markaw.com 40231 38599 4100 ufs ?? Ds 0:00.00 /usr/local/bin/maildrop -d snewman@starlo.com 40233 32896 4100 ufs ?? Ds 0:00.00 /usr/local/bin/maildrop -d pciuzio@microimage.cc 40236 33224 4100 ufs ?? Ds 0:00.00 /usr/local/bin/maildrop -d twilkerson@briorealty.com 40238 32876 4100 ufs ?? Ds 0:00.00 /usr/local/bin/maildrop -d ginnycash@reidrealestate.com 40240 32976 4100 ufs ?? Ds 0:00.00 /usr/local/bin/maildrop -d classic@classicrealtyinc.com 40242 35580 4100 ufs ?? Ds 0:00.00 /usr/local/bin/maildrop -d patrick.green@cifo.org 40246 35593 4100 ufs ?? Ds 0:00.00 /usr/local/bin/maildrop -d frizzelle@thestranger.com 40248 32923 4100 ufs ?? Ds 0:00.00 /usr/local/bin/maildrop -d earias@gkgcpa.com 40252 35596 4100 ufs ?? Ds 0:00.01 /usr/local/bin/maildrop -d seemckays@reidrealestate.com 40253 29833 4100 ufs ?? Ds 0:00.01 /usr/local/bin/maildrop -d seemckays@reidrealestate.com ps ax -O ppid,flags,mwchan | awk '$6 ~ /^D/ || $6 == "STAT"' PID PPID F MWCHAN TT STAT TIME COMMAND 2 0 204 - ?? DL 0:17.68 [g_event] 3 0 204 - ?? DL 9:14.85 [g_up] 4 0 204 - ?? DL 10:50.81 [g_down] 5 0 204 - ?? DL 0:02.93 [thread taskq] 6 0 204 - ?? DL 0:00.00 [acpi_task0] 7 0 204 - ?? DL 0:00.00 [acpi_task1] 8 0 204 - ?? DL 0:00.00 [acpi_task2] 9 0 204 - ?? DL 0:00.00 [kqueue taskq] 15 0 204 - ?? DL 8:47.55 [yarrow] 27 0 204 - ?? DL 0:01.72 [fdc0] 28 0 204 psleep ?? DL 0:43.74 [pagedaemon] 29 0 204 psleep ?? DL 0:00.00 [vmdaemon] 30 0 20c pgzero ?? DL 7:35.27 [pagezero] 31 0 204 psleep ?? DL 0:57.11 [bufdaemon] 32 0 204 syncer ?? DL 8:46.07 [syncer] 33 0 204 vlruwt ?? DL 0:28.29 [vnlru] 34 0 204 sdflus ?? DL 2:35.54 [softdepflush] 35 0 204 - ?? DL 1:01.20 [schedcpu] 411 1 0 ufs ?? Ds 0:04.81 /usr/sbin/mountd -r 39306 650 0 ufs ?? D 0:00.39 /usr/bin/perl /data/backaway/mailarchive/client/bin/smtpproxy 127.0.0.1:10026 127.0.0.1:10025 (perl5.8.7) 40214 38649 4100 ufs ?? Ds 0:00.00 /usr/local/bin/maildrop -d nbilous@dialonewolfedale.com 40220 32943 4100 ufs ?? Ds 0:00.00 /usr/local/bin/maildrop -d jrowe@zoofriends.org 40223 33257 4100 ufs ?? Ds 0:00.00 /usr/local/bin/maildrop -d logmonitoring@ewarna.com 40226 32942 4100 ufs ?? Ds 0:00.00 /usr/local/bin/maildrop -d nbilous@dialonewolfedale.com 40228 33199 4100 ufs ?? Ds 0:00.00 /usr/local/bin/maildrop -d enquiries@markaw.com 40231 38599 4100 ufs ?? Ds 0:00.00 /usr/local/bin/maildrop -d snewman@starlo.com 40233 32896 4100 ufs ?? Ds 0:00.00 /usr/local/bin/maildrop -d pciuzio@microimage.cc 40236 33224 4100 ufs ?? Ds 0:00.00 /usr/local/bin/maildrop -d twilkerson@briorealty.com 40238 32876 4100 ufs ?? Ds 0:00.00 /usr/local/bin/maildrop -d ginnycash@reidrealestate.com 40240 32976 4100 ufs ?? Ds 0:00.00 /usr/local/bin/maildrop -d classic@classicrealtyinc.com 40242 35580 4100 ufs ?? Ds 0:00.00 /usr/local/bin/maildrop -d patrick.green@cifo.org 40246 35593 4100 ufs ?? Ds 0:00.00 /usr/local/bin/maildrop -d frizzelle@thestranger.com 40248 32923 4100 ufs ?? Ds 0:00.00 /usr/local/bin/maildrop -d earias@gkgcpa.com ps axlww UID PID PPID CPU PRI NI VSZ RSS MWCHAN STAT TT TIME COMMAND 0 0 0 0 12 0 0 0 - WLs ?? 0:00.00 [swapper] 0 1 0 0 8 0 744 268 wait ILs ?? 0:00.01 /sbin/init -- 0 2 0 0 -8 0 0 8 - DL ?? 0:17.68 [g_event] 0 3 0 0 -8 0 0 8 - DL ?? 9:14.93 [g_up] 0 4 0 0 -8 0 0 8 - DL ?? 10:50.90 [g_down] 0 5 0 0 8 0 0 8 - DL ?? 0:02.93 [thread taskq] 0 6 0 0 8 0 0 8 - DL ?? 0:00.00 [acpi_task0] 0 7 0 0 8 0 0 8 - DL ?? 0:00.00 [acpi_task1] 0 8 0 0 8 0 0 8 - DL ?? 0:00.00 [acpi_task2] 0 9 0 0 8 0 0 8 - DL ?? 0:00.00 [kqueue taskq] 0 10 0 153 171 0 0 8 - RL ?? 3939:36.70 [idle: cpu1] 0 11 0 148 171 0 0 8 - RL ?? 4416:30.08 [idle: cpu0] 0 12 0 2 -44 0 0 8 - WL ?? 50:41.76 [swi1: net] 0 13 0 0 -32 0 0 8 - WL ?? 8:56.20 [swi4: clock sio] 0 14 0 0 -36 0 0 8 - WL ?? 0:00.00 [swi3: vm] 0 15 0 0 96 0 0 8 - DL ?? 8:47.68 [yarrow] UID PID PPID CPU PRI NI VSZ RSS MWCHAN STAT TT TIME COMMAND 0 0 0 0 12 0 0 0 - WLs ?? 0:00.00 [swapper] 0 1 0 0 8 0 744 268 wait ILs ?? 0:00.01 /sbin/init -- 0 2 0 0 -8 0 0 8 - DL ?? 0:17.68 [g_event] 0 3 0 0 -8 0 0 8 - DL ?? 9:14.93 [g_up] 0 4 0 0 -8 0 0 8 - DL ?? 10:50.90 [g_down] 0 5 0 0 8 0 0 8 - DL ?? 0:02.93 [thread taskq] 0 6 0 0 8 0 0 8 - DL ?? 0:00.00 [acpi_task0] 0 7 0 0 8 0 0 8 - DL ?? 0:00.00 [acpi_task1] 0 8 0 0 8 0 0 8 - DL ?? 0:00.00 [acpi_task2] 0 9 0 0 8 0 0 8 - DL ?? 0:00.00 [kqueue taskq] 0 10 0 153 171 0 0 8 - RL ?? 3939:36.70 [idle: cpu1] 0 11 0 148 171 0 0 8 - RL ?? 4416:30.08 [idle: cpu0] 0 12 0 2 -44 0 0 8 - WL ?? 50:41.76 [swi1: net] 0 13 0 0 -32 0 0 8 - WL ?? 8:56.20 [swi4: clock sio] 0 14 0 0 -36 0 0 8 - WL ?? 0:00.00 [swi3: vm] 0 15 0 0 96 0 0 8 - DL ?? 8:47.68 [yarrow] 0 16 0 0 -24 0 0 8 - WL ?? 0:00.01 [swi6: task queue] 0 17 0 0 -24 0 0 8 - WL ?? 0:00.00 [swi6: +] 0 18 0 0 -28 0 0 8 - WL ?? 6:34.50 [swi5: +] 0 19 0 0 -40 0 0 8 - WL ?? 6:42.62 [swi2: cambio] 0 20 0 0 -52 0 0 8 - WL ?? 0:00.00 [irq9: acpi0] 0 21 0 0 -64 0 0 8 - WL ?? 0:00.00 [irq14: ata0] 0 22 0 0 -64 0 0 8 - WL ?? 0:00.00 [irq15: ata1] 0 23 0 0 -68 0 0 8 - WL ?? 8:13.27 [irq26: bge0] 0 24 0 0 -68 0 0 8 - WL ?? 50:29.26 [irq27: bge1] 0 25 0 0 -60 0 0 8 - WL ?? 0:00.01 [irq1: atkbd0] 0 26 0 0 -48 0 0 8 - WL ?? 0:00.00 [swi0: sio] 0 27 0 0 -8 0 0 8 - DL ?? 0:01.72 [fdc0] 0 28 0 0 -16 0 0 8 psleep DL ?? 0:43.74 [pagedaemon] 0 29 0 0 20 0 0 8 psleep DL ?? 0:00.00 [vmdaemon] 0 30 0 0 171 0 0 8 pgzero DL ?? 7:35.27 [pagezero] 0 31 0 0 -16 0 0 8 psleep DL ?? 0:57.11 [bufdaemon] 0 32 0 0 20 0 0 8 syncer DL ?? 8:46.35 [syncer] 0 33 0 0 -4 0 0 8 vlruwt DL ?? 0:28.29 [vnlru] 0 34 0 0 -16 0 0 8 sdflus DL ?? 2:35.54 [softdepflush] 0 35 0 0 -40 0 0 8 - DL ?? 1:01.29 [schedcpu] 0 116 1 255 20 0 1220 648 pause Is ?? 0:00.00 adjkerntz -i 0 295 1 0 4 0 516 276 select Is ?? 0:05.71 /sbin/devd 0 337 1 0 96 0 1344 908 select Ss ?? 5:54.01 /usr/sbin/syslogd -s 0 354 1 0 96 0 1412 1032 select Ss ?? 0:07.06 /usr/sbin/rpcbind 0 411 1 0 -4 0 1536 1128 ufs Ds ?? 0:04.81 /usr/sbin/mountd -r 0 413 1 0 4 0 1364 956 accept Is ?? 0:00.02 nfsd: master (nfsd) 0 414 413 4 4 0 1240 716 - S ?? 101:39.74 nfsd: server (nfsd) 0 415 413 0 4 0 1240 716 - S ?? 24:34.31 nfsd: server (nfsd) 0 416 413 0 4 0 1240 716 - S ?? 9:23.71 nfsd: server (nfsd) 0 417 413 0 4 0 1240 716 - S ?? 4:21.56 nfsd: server (nfsd) 0 419 413 0 4 0 1240 716 - I ?? 2:24.04 nfsd: server (nfsd) 0 420 413 0 4 0 1240 716 - I ?? 0:01.46 nfsd: server (nfsd) Any insights would be greatly appreciated. We are likely to try and downgrade to 5.5 stable.. 6.X has been nothing but problems to us with regards to NFS.. both on the client and server. From owner-freebsd-stable@FreeBSD.ORG Sun Jul 2 01:57:25 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9A54216A567 for ; Sun, 2 Jul 2006 01:57:25 +0000 (UTC) (envelope-from lists@stringsutils.com) Received: from zoraida.natserv.net (p65-147.acedsl.com [66.114.65.147]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9399E44C9D for ; Sun, 2 Jul 2006 01:13:27 +0000 (GMT) (envelope-from lists@stringsutils.com) Received: from zoraida.natserv.net (localhost.natserv.net [127.0.0.1]) by zoraida.natserv.net (Postfix) with ESMTP id 8434DB822; Sat, 1 Jul 2006 21:13:26 -0400 (EDT) Received: from zoraida.natserv.net (zoraida.natserv.net [66.114.65.147]) by zoraida.natserv.net (Postfix) with ESMTP id 52A57B81F; Sat, 1 Jul 2006 21:13:26 -0400 (EDT) References: <20060629230309.GA12773@lpthe.jussieu.fr> <20060630041733.GA4941@zibbi.meraka.csir.co.za> Message-ID: X-Mailer: http://www.courier-mta.org/cone/ From: Francisco Reyes To: John Hay Date: Sat, 01 Jul 2006 21:13:26 -0400 Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset="US-ASCII" Content-Disposition: inline Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Cc: freebsd-stable@freebsd.org, Michel Talon Subject: Re: NFS Locking Issue X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Jul 2006 01:57:25 -0000 John Hay writes: > I only started to see the lockd problems when upgrading the server side > to FreeBSD 6.x and later. I had various FreeBSD clients, between 4.x > and 7-current and the lockd problem only showed up when upgrading the > server from 5.x to 6.x. It confirms the same we are experiencing.. constant freezing/locking issues. I guess no more 6.X for us.. for the foreseable future.. From owner-freebsd-stable@FreeBSD.ORG Sun Jul 2 06:39:51 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9665516A407 for ; Sun, 2 Jul 2006 06:39:51 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from cs1.cs.huji.ac.il (cs1.cs.huji.ac.il [132.65.16.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0B36243D48 for ; Sun, 2 Jul 2006 06:39:50 +0000 (GMT) (envelope-from danny@cs.huji.ac.il) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by cs1.cs.huji.ac.il with esmtp id 1FwvcP-0009Td-Ls; Sun, 02 Jul 2006 09:39:45 +0300 X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.2 To: Francisco Reyes In-reply-to: References: <20060629230309.GA12773@lpthe.jussieu.fr> <20060630041733.GA4941@zibbi.meraka.csir.co.za> Comments: In-reply-to Francisco Reyes message dated "Sat, 01 Jul 2006 21:13:26 -0400." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 02 Jul 2006 09:39:45 +0300 From: Danny Braniss Message-ID: Cc: freebsd-stable@freebsd.org, Michel Talon Subject: Re: NFS Locking Issue X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Jul 2006 06:39:51 -0000 > John Hay writes: > > > I only started to see the lockd problems when upgrading the server side > > to FreeBSD 6.x and later. I had various FreeBSD clients, between 4.x > > and 7-current and the lockd problem only showed up when upgrading the > > server from 5.x to 6.x. > > It confirms the same we are experiencing.. constant freezing/locking issues. > I guess no more 6.X for us.. for the foreseable future.. just to add some more 'ingredients' to the problems: 1- we are suffering from the lockd syndrome 2- am-utils sometimes failes - specially /net (type:=host) [there seems to be a race condition] both problems are new since 6.1 and now, on a 'mostly idle' machine, after failing to compile openoffice-2.0 the lockd is 'spinning' with no real work, at least so it seems: last pid: 69935; load averages: 0.16, 0.10, 0.08 up 1+16:37:25 09:37:09 44 processes: 1 running, 43 sleeping CPU states: 2.6% user, 0.0% nice, 0.4% system, 0.4% interrupt, 96.6% idle Mem: 129M Active, 2796M Inact, 157M Wired, 106M Cache, 214M Buf, 132M Free Swap: 4096M Total, 4096M Free PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND 513 root 1 96 0 48628K 45304K select 1 67:39 5.13% rpc.lockd 498 root 1 4 0 2420K 868K - 1 23:38 0.83% nfsd 419 root 1 96 0 5408K 2088K select 1 98:13 0.00% amd-6.1.5 danny From owner-freebsd-stable@FreeBSD.ORG Sun Jul 2 08:06:59 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C3D7E16A40F for ; Sun, 2 Jul 2006 08:06:59 +0000 (UTC) (envelope-from fblist@gmail.com) Received: from wx-out-0102.google.com (wx-out-0102.google.com [66.249.82.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5009A43D45 for ; Sun, 2 Jul 2006 08:06:59 +0000 (GMT) (envelope-from fblist@gmail.com) Received: by wx-out-0102.google.com with SMTP id h30so403392wxd for ; Sun, 02 Jul 2006 01:06:58 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=qCxdYRS3s9YWWa7wqTMZmzOE3FL2r/eNOkvAv+t60O7/+O26oZnqbRzPpwSlHNplL9r3u90226V5fTu1vKuL0dKkeOhSxLYzj3TEDPEQbTo+tdZLxcQb/s2k+I0DqS/mRiPRA+xzopdhih+imjhnaxLB2p6MprNhX/aik2LjXHU= Received: by 10.70.20.18 with SMTP id 18mr3617505wxt; Sun, 02 Jul 2006 01:06:58 -0700 (PDT) Received: by 10.70.129.9 with HTTP; Sun, 2 Jul 2006 01:06:58 -0700 (PDT) Message-ID: <910c4cb0607020106teec096ah1b123753acef6f9c@mail.gmail.com> Date: Sun, 2 Jul 2006 16:06:58 +0800 From: "Ren Zhen" To: freebsd-stable MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: T23 lock up after enter KDB either on 6-STABLE or 7-CURRENT X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Jul 2006 08:06:59 -0000 After I login, press Ctrl+Alt+ESC, kernel says: KDB: enter: manual escape to debugger [thread pid 16 tid 100014 ] Stopped at kdb_enter+0x2b: nop db> Then, my T23 lock up. I can only switch off the computer. But, I use "boot -d" at booting kdb will work fine. I press c it continue. When "login:" displayed on the screen, I enter the KDB, it lock up again. Both 6-STABLE and 7-CURRENT have this problem. My T23's model is 2647-4NC. Piii 1.13 256M*2 SDR. I have uninstalled one DIMM, but it seems to have no help to this problem. My kernel configuration file is GENERIC with following debug options: options KDB options DDB options GDB options INVARIANTS options INVARIANT_SUPPORT options WITNESS options WITNESS_SKIPSPIN From owner-freebsd-stable@FreeBSD.ORG Sun Jul 2 10:54:25 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 81A6D16A403 for ; Sun, 2 Jul 2006 10:54:25 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3422343D45 for ; Sun, 2 Jul 2006 10:54:25 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id BCD7D46BEA; Sun, 2 Jul 2006 06:54:24 -0400 (EDT) Date: Sun, 2 Jul 2006 11:54:24 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Ren Zhen In-Reply-To: <910c4cb0607020106teec096ah1b123753acef6f9c@mail.gmail.com> Message-ID: <20060702115326.K67344@fledge.watson.org> References: <910c4cb0607020106teec096ah1b123753acef6f9c@mail.gmail.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable Subject: Re: T23 lock up after enter KDB either on 6-STABLE or 7-CURRENT X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Jul 2006 10:54:25 -0000 On Sun, 2 Jul 2006, Ren Zhen wrote: > After I login, press Ctrl+Alt+ESC, kernel says: > KDB: enter: manual escape to debugger > [thread pid 16 tid 100014 ] > Stopped at kdb_enter+0x2b: nop > db> > > Then, my T23 lock up. I can only switch off the computer. > > But, I use "boot -d" at booting kdb will work fine. I press c it continue. > When "login:" displayed on the screen, I enter the KDB, it lock up again. > > Both 6-STABLE and 7-CURRENT have this problem. > > My T23's model is 2647-4NC. Piii 1.13 256M*2 SDR. I have uninstalled one > DIMM, but it seems to have no help to this problem. Try compiling out device kbdmux and see if that fixes things? There are reported problems regarding kbdmux's interaction with the debugger. Robert N M Watson Computer Laboratory University of Cambridge > > My kernel configuration file is GENERIC with following debug options: > options KDB > options DDB > options GDB > options INVARIANTS > options INVARIANT_SUPPORT > options WITNESS > options WITNESS_SKIPSPIN > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > From owner-freebsd-stable@FreeBSD.ORG Sun Jul 2 11:47:15 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D5F8A16A56F for ; Sun, 2 Jul 2006 11:47:15 +0000 (UTC) (envelope-from dzalewski@open-craft.com) Received: from zeus.lunarpages.com (zeus.lunarpages.com [216.193.211.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8B27F43D6E for ; Sun, 2 Jul 2006 11:14:40 +0000 (GMT) (envelope-from dzalewski@open-craft.com) Received: from [196.218.200.205] (helo=[10.0.0.189]) by zeus.lunarpages.com with esmtpa (Exim 4.52) id 1FwzvF-0001j8-QN for freebsd-stable@freebsd.org; Sun, 02 Jul 2006 04:15:30 -0700 From: Dominik Zalewski Organization: OpenCraft To: freebsd-stable@freebsd.org Date: Sun, 2 Jul 2006 14:08:33 +0300 User-Agent: KMail/1.9.3 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200607021408.33744.dzalewski@open-craft.com> X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - zeus.lunarpages.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - open-craft.com X-Source: X-Source-Args: X-Source-Dir: Subject: Portupgrade failed - /var/db/pkg/pkgdb.db: unexpected file type or format X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Jul 2006 11:47:15 -0000 I'm using FreeBSD 6.1-stable . Today I updated my ports tree using cvsup and then I ran as usually portupgrade -a . It upgraded my portupgrade to version portupgrade-2.1.3.2,2. After that portupgrade stopped working. Here is an error message: [root@silicon /]# portupgrade -a [Updating the pkgdb in /var/db/pkg ... /var/db/pkg/pkgdb.db: unexpected file type or format -- Invalid argument; rebuild needed] [Rebuilding the pkgdb in /var/db/pkg ... [Updating the pkgdb in /var/db/pkg ... /var/db/pkg/pkgdb.db: unexpected file type or format -- Invalid argument; rebuild needed] [Rebuilding the pkgdb in /var/db/pkg ... /var/db/pkg/pkgdb.db: unexpected file type or format -- Invalid argument: Cannot update the pkgdb!]: Cannot update the pkgdb!] Command failed [exit code 1]: /usr/local/sbin/pkgdb -aFQ Any ideas? Thank you in advance, Dominik Zalewski From owner-freebsd-stable@FreeBSD.ORG Sun Jul 2 13:34:12 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 01CFE16A415 for ; Sun, 2 Jul 2006 13:34:12 +0000 (UTC) (envelope-from volker@vwsoft.com) Received: from frontmail.ipactive.de (frontmail.ipactive.de [85.214.39.229]) by mx1.FreeBSD.org (Postfix) with ESMTP id 688F843D48 for ; Sun, 2 Jul 2006 13:34:11 +0000 (GMT) (envelope-from volker@vwsoft.com) Received: from mail.vtec.ipme.de (gprs-pool-1-008.eplus-online.de [212.23.126.8]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by frontmail.ipactive.de (Postfix) with ESMTP id E04F933D0F for ; Sun, 2 Jul 2006 15:34:05 +0200 (CEST) Received: from [192.168.201.3] (unknown [192.168.201.3]) by mail.vtec.ipme.de (Postfix) with ESMTP id 9EA4E2E518; Sun, 2 Jul 2006 15:34:01 +0200 (CEST) Message-ID: <44A7CB60.4010102@vwsoft.com> Date: Sun, 02 Jul 2006 15:34:24 +0200 From: Volker User-Agent: Thunderbird 1.5.0.4 (X11/20060610) MIME-Version: 1.0 To: Dominik Zalewski References: <200607021408.33744.dzalewski@open-craft.com> In-Reply-To: <200607021408.33744.dzalewski@open-craft.com> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-VWSoft-MailScanner: Found to be clean X-MailScanner-From: volker@vwsoft.com X-ipactive-MailScanner-Information: Please contact the ISP for more information X-ipactive-MailScanner: Found to be clean X-ipactive-MailScanner-From: volker@vwsoft.com Cc: freebsd-stable@freebsd.org Subject: Re: Portupgrade failed - /var/db/pkg/pkgdb.db: unexpected file type or format X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Jul 2006 13:34:12 -0000 On 12/23/-58 20:59, Dominik Zalewski wrote: > I'm using FreeBSD 6.1-stable . Today I updated my ports tree using cvsup and > then I ran as usually portupgrade -a . It upgraded my portupgrade to version > portupgrade-2.1.3.2,2. After that portupgrade stopped working. > > in /var/db/pkg ... /var/db/pkg/pkgdb.db: unexpected file type or format -- Dominik, I've had the same today and thought it has been my mistake (doing a pkg_version in parallel). Just delete /var/db/pkg/pkgdb.db and run `pkgdb -F' and all should be fine. At least on my system I was able to rebuild pkgdb.db that way and all is working again. Greetings, Volker From owner-freebsd-stable@FreeBSD.ORG Sun Jul 2 13:35:59 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 03C9516A412 for ; Sun, 2 Jul 2006 13:35:59 +0000 (UTC) (envelope-from vladgalu@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.186]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4803E43D60 for ; Sun, 2 Jul 2006 13:35:57 +0000 (GMT) (envelope-from vladgalu@gmail.com) Received: by nf-out-0910.google.com with SMTP id c29so592273nfb for ; Sun, 02 Jul 2006 06:35:56 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=DpyyJsXEtizA9e1fKQRlt4+rAQbmErfs801jWgPLQbcurta1bTBTUh3+omb0EjmhWnV87w9vPR8sr3DADOwHHs+9se54ouOMaNbAG6UvCvSida7xHik1r/DB5UiuQEFaOUFz3dKcjqy6j2I276UtYh3hElg3XEjw3ON45Hnk3V8= Received: by 10.49.21.14 with SMTP id y14mr1637106nfi; Sun, 02 Jul 2006 06:35:56 -0700 (PDT) Received: by 10.48.250.2 with HTTP; Sun, 2 Jul 2006 06:35:55 -0700 (PDT) Message-ID: <79722fad0607020635i53ffc6clca3e9cf7b50fe101@mail.gmail.com> Date: Sun, 2 Jul 2006 16:35:55 +0300 From: "Vlad GALU" To: freebsd-stable@freebsd.org In-Reply-To: <200607021408.33744.dzalewski@open-craft.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <200607021408.33744.dzalewski@open-craft.com> Subject: Re: Portupgrade failed - /var/db/pkg/pkgdb.db: unexpected file type or format X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Jul 2006 13:35:59 -0000 On 7/2/06, Dominik Zalewski wrote: > I'm using FreeBSD 6.1-stable . Today I updated my ports tree using cvsup and > then I ran as usually portupgrade -a . It upgraded my portupgrade to version > portupgrade-2.1.3.2,2. After that portupgrade stopped working. > > Here is an error message: > > [root@silicon /]# portupgrade -a > [Updating the pkgdb > in /var/db/pkg ... /var/db/pkg/pkgdb.db: unexpected file type or format -- > Invalid argument; rebuild needed] [Rebuilding the pkgdb > in /var/db/pkg ... [Updating the pkgdb > in /var/db/pkg ... /var/db/pkg/pkgdb.db: unexpected file type or format -- > Invalid argument; rebuild needed] [Rebuilding the pkgdb > in /var/db/pkg ... /var/db/pkg/pkgdb.db: unexpected file type or format -- > Invalid argument: Cannot update the pkgdb!]: Cannot update the pkgdb!] > Command failed [exit code 1]: /usr/local/sbin/pkgdb -aFQ Removing pkgdb.db and INDEX-6.db and then rebuilding them with pkgdb and portsdb did the trick for me. > > Any ideas? > > Thank you in advance, > > Dominik Zalewski > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > -- If it's there, and you can see it, it's real. If it's not there, and you can see it, it's virtual. If it's there, and you can't see it, it's transparent. If it's not there, and you can't see it, you erased it. From owner-freebsd-stable@FreeBSD.ORG Sun Jul 2 13:39:38 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 41FEF16A415 for ; Sun, 2 Jul 2006 13:39:38 +0000 (UTC) (envelope-from dzalewski@open-craft.com) Received: from zeus.lunarpages.com (zeus.lunarpages.com [216.193.211.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id C26C544010 for ; Sun, 2 Jul 2006 13:39:25 +0000 (GMT) (envelope-from dzalewski@open-craft.com) Received: from [196.218.200.205] (helo=[10.0.0.189]) by zeus.lunarpages.com with esmtpa (Exim 4.52) id 1Fx2BF-0004P9-Pg; Sun, 02 Jul 2006 06:40:10 -0700 From: Dominik Zalewski Organization: OpenCraft To: Volker Date: Sun, 2 Jul 2006 16:33:17 +0300 User-Agent: KMail/1.9.3 References: <200607021408.33744.dzalewski@open-craft.com> <44A7CB60.4010102@vwsoft.com> In-Reply-To: <44A7CB60.4010102@vwsoft.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200607021633.17906.dzalewski@open-craft.com> X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - zeus.lunarpages.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - open-craft.com X-Source: X-Source-Args: X-Source-Dir: Cc: freebsd-stable@freebsd.org Subject: Re: Portupgrade failed - /var/db/pkg/pkgdb.db: unexpected file type or format X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Jul 2006 13:39:38 -0000 On Sunday 02 July 2006 16:34, you wrote: > On 12/23/-58 20:59, Dominik Zalewski wrote: > > I'm using FreeBSD 6.1-stable . Today I updated my ports tree using cvsup > > and then I ran as usually portupgrade -a . It upgraded my portupgrade to > > version portupgrade-2.1.3.2,2. After that portupgrade stopped working. > > > > in /var/db/pkg ... /var/db/pkg/pkgdb.db: unexpected file type or format > > -- > > Dominik, > > I've had the same today and thought it has been my mistake (doing a > pkg_version in parallel). > > Just delete /var/db/pkg/pkgdb.db and run `pkgdb -F' and all should > be fine. At least on my system I was able to rebuild pkgdb.db that > way and all is working again. > > Greetings, > > Volker Thanks. I rebuild my pkgdb.db and it looks everything is fine. Thank you, Dominik Zalewski From owner-freebsd-stable@FreeBSD.ORG Sun Jul 2 13:43:42 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3C33516A403 for ; Sun, 2 Jul 2006 13:43:42 +0000 (UTC) (envelope-from dzalewski@open-craft.com) Received: from zeus.lunarpages.com (zeus.lunarpages.com [216.193.211.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id AE6C34400B for ; Sun, 2 Jul 2006 13:43:41 +0000 (GMT) (envelope-from dzalewski@open-craft.com) Received: from [196.218.200.205] (helo=[10.0.0.189]) by zeus.lunarpages.com with esmtpa (Exim 4.52) id 1Fx2FR-00057G-9X for freebsd-stable@freebsd.org; Sun, 02 Jul 2006 06:44:29 -0700 From: Dominik Zalewski Organization: OpenCraft To: freebsd-stable@freebsd.org Date: Sun, 2 Jul 2006 16:37:37 +0300 User-Agent: KMail/1.9.3 References: <200607021408.33744.dzalewski@open-craft.com> <79722fad0607020635i53ffc6clca3e9cf7b50fe101@mail.gmail.com> In-Reply-To: <79722fad0607020635i53ffc6clca3e9cf7b50fe101@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200607021637.37741.dzalewski@open-craft.com> X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - zeus.lunarpages.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - open-craft.com X-Source: X-Source-Args: X-Source-Dir: Subject: Re: Portupgrade failed - /var/db/pkg/pkgdb.db: unexpected file type or format X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Jul 2006 13:43:42 -0000 On Sunday 02 July 2006 16:35, Vlad GALU wrote: > On 7/2/06, Dominik Zalewski wrote: > > I'm using FreeBSD 6.1-stable . Today I updated my ports tree using cvsup > > and then I ran as usually portupgrade -a . It upgraded my portupgrade to > > version portupgrade-2.1.3.2,2. After that portupgrade stopped working. > > > > Here is an error message: > > > > [root@silicon /]# portupgrade -a > > [Updating the pkgdb > > in /var/db/pkg ... /var/db/pkg/pkgdb.db: unexpected file type or format > > -- Invalid argument; rebuild needed] [Rebuilding the pkgdb > > in /var/db/pkg ... [Updating the pkgdb > > > > in /var/db/pkg ... /var/db/pkg/pkgdb.db: unexpected file type or format > > -- Invalid argument; rebuild needed] [Rebuilding the pkgdb > > in /var/db/pkg ... /var/db/pkg/pkgdb.db: unexpected > > file type or format -- Invalid argument: Cannot update the pkgdb!]: > > Cannot update the pkgdb!] Command failed [exit code 1]: > > /usr/local/sbin/pkgdb -aFQ > > Removing pkgdb.db and INDEX-6.db and then rebuilding them with > pkgdb and portsdb did the trick for me. > > > Any ideas? > > > > Thank you in advance, > > > > Dominik Zalewski > > _______________________________________________ > > freebsd-stable@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" Thanks man, alreadt fixed :) Regards, Dominik Zalewski From owner-freebsd-stable@FreeBSD.ORG Sun Jul 2 14:34:00 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EAFB416A558 for ; Sun, 2 Jul 2006 14:33:59 +0000 (UTC) (envelope-from fblist@gmail.com) Received: from wx-out-0102.google.com (wx-out-0102.google.com [66.249.82.200]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5E0794439A for ; Sun, 2 Jul 2006 14:16:34 +0000 (GMT) (envelope-from fblist@gmail.com) Received: by wx-out-0102.google.com with SMTP id h30so421241wxd for ; Sun, 02 Jul 2006 07:16:33 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=mPFuNC3FRRzi65lMikaLAnaV1AhDu8m3qMbonnwpO5w4nmMDRSGFFGUyPzc61j02/rxoPCoE1J/2epePFWejRMmOHOtqrQB9yXuwR+wx5EpDUYiONgTjN+9D/DrE+51BMfDyBlqehYRJZo+aze5QXz6Oa5IX7rO8F/82iYdcKG0= Received: by 10.70.26.16 with SMTP id 16mr4030675wxz; Sun, 02 Jul 2006 07:16:33 -0700 (PDT) Received: by 10.70.129.9 with HTTP; Sun, 2 Jul 2006 07:16:33 -0700 (PDT) Message-ID: <910c4cb0607020716l7088b7ffg524604de055f5930@mail.gmail.com> Date: Sun, 2 Jul 2006 22:16:33 +0800 From: "Ren Zhen" To: "Robert Watson" In-Reply-To: <20060702115326.K67344@fledge.watson.org> MIME-Version: 1.0 References: <910c4cb0607020106teec096ah1b123753acef6f9c@mail.gmail.com> <20060702115326.K67344@fledge.watson.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-stable Subject: Re: T23 lock up after enter KDB either on 6-STABLE or 7-CURRENT X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Jul 2006 14:34:00 -0000 Thanks a lot. After I remove the kdbmux, it works fine. :) On 7/2/06, Robert Watson wrote: > > > On Sun, 2 Jul 2006, Ren Zhen wrote: > > > After I login, press Ctrl+Alt+ESC, kernel says: > > KDB: enter: manual escape to debugger > > [thread pid 16 tid 100014 ] > > Stopped at kdb_enter+0x2b: nop > > db> > > > > Then, my T23 lock up. I can only switch off the computer. > > > > But, I use "boot -d" at booting kdb will work fine. I press c it > continue. > > When "login:" displayed on the screen, I enter the KDB, it lock up > again. > > > > Both 6-STABLE and 7-CURRENT have this problem. > > > > My T23's model is 2647-4NC. Piii 1.13 256M*2 SDR. I have uninstalled one > > DIMM, but it seems to have no help to this problem. > > Try compiling out device kbdmux and see if that fixes things? There are > reported problems regarding kbdmux's interaction with the debugger. > > Robert N M Watson > Computer Laboratory > University of Cambridge > > > > > My kernel configuration file is GENERIC with following debug options: > > options KDB > > options DDB > > options GDB > > options INVARIANTS > > options INVARIANT_SUPPORT > > options WITNESS > > options WITNESS_SKIPSPIN > > _______________________________________________ > > freebsd-stable@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org > " > > > From owner-freebsd-stable@FreeBSD.ORG Sun Jul 2 15:57:20 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DAAD816A56F for ; Sun, 2 Jul 2006 15:57:20 +0000 (UTC) (envelope-from freebsd-listen@fabiankeil.de) Received: from smtprelay01.ispgateway.de (smtprelay01.ispgateway.de [80.67.18.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3615E44284 for ; Sun, 2 Jul 2006 15:33:52 +0000 (GMT) (envelope-from freebsd-listen@fabiankeil.de) Received: (qmail 31139 invoked from network); 2 Jul 2006 15:33:51 -0000 Received: from unknown (HELO localhost) (775067@[217.50.151.147]) (envelope-sender ) by smtprelay01.ispgateway.de (qmail-ldap-1.03) with SMTP for ; 2 Jul 2006 15:33:51 -0000 Date: Sun, 2 Jul 2006 17:33:38 +0200 From: Fabian Keil To: Robert Watson Message-ID: <20060702173338.00a5ed44@localhost> In-Reply-To: <20060628101729.J50845@fledge.watson.org> References: <20060627175853.765a590e@localhost> <20060628101729.J50845@fledge.watson.org> X-Mailer: Sylpheed-Claws 2.2.3 (GTK+ 2.8.19; i386-portbld-freebsd6.1) X-PGP-KEY-URL: http://www.fabiankeil.de/gpg-keys/freebsd-listen-2006-08-19.asc User-Agent: 321 test Mime-Version: 1.0 Content-Type: multipart/signed; boundary="Sig_wzkp/wo_80Zh=okBSNrSOZJ"; protocol="application/pgp-signature"; micalg=PGP-SHA1 Cc: Peter Thoenen , freebsd-stable@freebsd.org Subject: Re: FreeBSD 6.1 Tor issues (Once More, with Feeling) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Jul 2006 15:57:21 -0000 --Sig_wzkp/wo_80Zh=okBSNrSOZJ Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Robert Watson wrote: > On Tue, 27 Jun 2006, Fabian Keil wrote: >=20 > > There was a "request" for Tor related problem reports a while ago, > > I couldn't find the message again, but I believe it was posted here. >=20 > I'm very interested in tracking down this problem, but have had a lot > of trouble getting reliable reports of problems -- i.e., ones where I > could get any debugging information. I had a similar conversation on > these lines yeterday with Roger (Tor author) here at the WEIS > conference. If this is easily reproduceable, I would like you to do > the following: > - Does the hang occur? If so, use a serial break to get into DDB, > see the above. I previously had the serial console misconfigured and I'm still not sure if the settings are correct now. So far I put "BOOT_COMCONSOLE_SPEED=3D57600" in /etc/make.conf, "options CONSPEED=3D57600" in the kernel and "console=3Dcomconsole" in /boot/loader.conf. Kernel and bootblock were recompiled and reinstalled. /boot.config contains the line: "-D -h -S57600" (speed setting through make.conf didn't work). The boot process now starts with: PXELINUX 3.11 2005-09-02 Copyright (C) 1994-2005 H. Peter Anvin Booting from local disk... 1 Linux 2 FreeBSD 3 FreeBSD Default: 2=20 /boot.config: -DConsoles: internal video/keyboard serial port =20 BIOS drive C: is disk0 BIOS 639kB/523200kB available memory FreeBSD/i386 bootstrap loader, Revision 1.1 [...] After manually triggering a test panic through debug.kdb.enter I could enter ddb and everything seemed to be working. However today I got another hang and couldn't enter the debugger by sending BREAK. It is the same BREAK ssh sends with ~B, right? Even after rebooting, sending break didn't trigger a panic, so either I'm sending the wrong BREAK, or my console settings are still messed up. Any ideas? Fabian --=20 http://www.fabiankeil.de/ --Sig_wzkp/wo_80Zh=okBSNrSOZJ Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEp+dbjV8GA4rMKUQRAkYlAKCyHy/njIji95D/ykRI1C/yps0b9gCeIP/W IDstMpVovLqA6WkSiBXotQk= =oBO1 -----END PGP SIGNATURE----- --Sig_wzkp/wo_80Zh=okBSNrSOZJ-- From owner-freebsd-stable@FreeBSD.ORG Sun Jul 2 16:10:15 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9359616A407 for ; Sun, 2 Jul 2006 16:10:15 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id EA1A643D46 for ; Sun, 2 Jul 2006 16:10:14 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id F26D046BB7; Sun, 2 Jul 2006 12:10:13 -0400 (EDT) Date: Sun, 2 Jul 2006 17:10:13 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Fabian Keil In-Reply-To: <20060702173338.00a5ed44@localhost> Message-ID: <20060702170843.C67344@fledge.watson.org> References: <20060627175853.765a590e@localhost> <20060628101729.J50845@fledge.watson.org> <20060702173338.00a5ed44@localhost> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Peter Thoenen , freebsd-stable@freebsd.org Subject: Re: FreeBSD 6.1 Tor issues (Once More, with Feeling) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Jul 2006 16:10:15 -0000 On Sun, 2 Jul 2006, Fabian Keil wrote: >> I'm very interested in tracking down this problem, but have had a lot of >> trouble getting reliable reports of problems -- i.e., ones where I could >> get any debugging information. I had a similar conversation on these lines >> yeterday with Roger (Tor author) here at the WEIS conference. If this is >> easily reproduceable, I would like you to do the following: > >> - Does the hang occur? If so, use a serial break to get into DDB, see the >> above. > > I previously had the serial console misconfigured and I'm still not sure if > the settings are correct now. > > So far I put "BOOT_COMCONSOLE_SPEED=57600" in /etc/make.conf, "options > CONSPEED=57600" in the kernel and "console=comconsole" in /boot/loader.conf. > Kernel and bootblock were recompiled and reinstalled. /boot.config contains > the line: "-D -h -S57600" (speed setting through make.conf didn't work). I don't use alternative console speeds, so can't comment on the specifics of the above, but the output below looks right. > The boot process now starts with: > > PXELINUX 3.11 2005-09-02 Copyright (C) 1994-2005 H. Peter Anvin > Booting from local disk... > > 1 Linux > 2 FreeBSD > 3 FreeBSD > > Default: 2 > > /boot.config: -DConsoles: internal video/keyboard serial port > BIOS drive C: is disk0 > BIOS 639kB/523200kB available memory > > FreeBSD/i386 bootstrap loader, Revision 1.1 > [...] > > After manually triggering a test panic through debug.kdb.enter I could enter > ddb and everything seemed to be working. > > However today I got another hang and couldn't enter the debugger by sending > BREAK. It is the same BREAK ssh sends with ~B, right? > > Even after rebooting, sending break didn't trigger a panic, so either I'm > sending the wrong BREAK, or my console settings are still messed up. Any > ideas? What serial software are you using to reach the console? Do you have options BREAK_TO_DEBUGGER compiled into your kernel? The delivery mechanism for the break will depend on the software you're using... Robert N M Watson Computer Laboratory University of Cambridge From owner-freebsd-stable@FreeBSD.ORG Sun Jul 2 16:18:32 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3B57416A407 for ; Sun, 2 Jul 2006 16:18:32 +0000 (UTC) (envelope-from donaldjoneill@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.181]) by mx1.FreeBSD.org (Postfix) with ESMTP id A454D43D45 for ; Sun, 2 Jul 2006 16:18:31 +0000 (GMT) (envelope-from donaldjoneill@gmail.com) Received: by py-out-1112.google.com with SMTP id c63so840106pyc for ; Sun, 02 Jul 2006 09:18:30 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:to:subject:date:user-agent:cc:references:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:message-id:from; b=M67XJolkvRkobAZ6viOJPi2tLr1J6LM4+WQUPS9iD1jppaODqcnyV9qEC9XAQd0sGI7VYFjxMhj2PpT92o/+uOe/pMxH9v7Qx3JE2+5GuZRprpmFSbkPC2tsLmLJE4980Jjx9BP/h/q9kRqvfB+kc6UR4Y29LLQ4mAPSj8fD8Mo= Received: by 10.35.27.1 with SMTP id e1mr254978pyj; Sun, 02 Jul 2006 09:18:30 -0700 (PDT) Received: from pres1750.airedalians.com ( [75.7.74.134]) by mx.gmail.com with ESMTP id t70sm1454829pyg.2006.07.02.09.18.29; Sun, 02 Jul 2006 09:18:29 -0700 (PDT) To: freebsd-stable@freebsd.org Date: Sun, 2 Jul 2006 11:16:52 -0500 User-Agent: KMail/1.9.3 References: <200607021408.33744.dzalewski@open-craft.com> <79722fad0607020635i53ffc6clca3e9cf7b50fe101@mail.gmail.com> <200607021637.37741.dzalewski@open-craft.com> In-Reply-To: <200607021637.37741.dzalewski@open-craft.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200607021116.53432.duncan.fbsd@gmail.com> From: "Donald J. O'Neill" Cc: Volker , Dominik Zalewski , Vlad GALU Subject: Re: Portupgrade failed - /var/db/pkg/pkgdb.db: unexpected file type or format X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Jul 2006 16:18:32 -0000 On Sunday 02 July 2006 08:37, Dominik Zalewski wrote: > On Sunday 02 July 2006 16:35, Vlad GALU wrote: > > On 7/2/06, Dominik Zalewski wrote: > > > I'm using FreeBSD 6.1-stable . Today I updated my ports tree using > > > cvsup and then I ran as usually portupgrade -a . It upgraded my > > > portupgrade to version portupgrade-2.1.3.2,2. After that portupgrade > > > stopped working. > > > > > > Here is an error message: > > > > > > [root@silicon /]# portupgrade -a > > > [Updating the pkgdb > > > in /var/db/pkg ... /var/db/pkg/pkgdb.db: unexpected file type or format > > > -- Invalid argument; rebuild needed] [Rebuilding the pkgdb > > > in /var/db/pkg ... [Updating the pkgdb > > > > > > in /var/db/pkg ... /var/db/pkg/pkgdb.db: unexpected file type or format > > > -- Invalid argument; rebuild needed] [Rebuilding the pkgdb > > > in /var/db/pkg ... /var/db/pkg/pkgdb.db: unexpected > > > file type or format -- Invalid argument: Cannot update the pkgdb!]: > > > Cannot update the pkgdb!] Command failed [exit code 1]: > > > /usr/local/sbin/pkgdb -aFQ > > > > Removing pkgdb.db and INDEX-6.db and then rebuilding them with > > pkgdb and portsdb did the trick for me. > > > > > Any ideas? > > > > > > Thank you in advance, > > > > > > Dominik Zalewski > > > _______________________________________________ > > Thanks man, alreadt fixed :) > > Regards, > > Dominik Zalewski > Pretty good answers, but it may involve a little more work than that. This is what I did: mv /usr/ports/INDEX-6.db --> INDEX-6.db.org mv /var/db/pkg/pkgdb.db --> pkgdb.db.org pkg_delete portupgrade-2.1.3.1,2 pkg_delete ruby18-bdb-0.5.9 pkg_delete ruby18-bdb1-0.2.2 pkg_delete db4-4.0.14_1,1 pkg_delete db41-4.1.25_3 pkg_delete db42-4.2.52_4 I left db43-4.3.29, It would be needed later and reomoving it would cause too many other things to have to be rebuilt (or I get a bite in the ass if I don't). cd /usr/ports/sysutils/portupgrade make conf ----- select bdb4, it'll use db43 as that's what's installed make package-recursive pkgdb -F fix the dependencies portversion -v |grep needs rebuilds portsdb (and rechecks pkgdb.db) and I find out what ports need upgrading. By the way, I don't use cvsup to upgrade the ports tree. I use portsnap. It's way faster than cvsup. When I used cvsup it could take up to 1/2 hr (depending on the computer speed) to get to the point of upgrading ports. Using portsnap, it only takes a couple of minutes to get to it. Don From owner-freebsd-stable@FreeBSD.ORG Sun Jul 2 16:22:47 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0294716A403 for ; Sun, 2 Jul 2006 16:22:47 +0000 (UTC) (envelope-from freebsd@hub.org) Received: from hub.org (hub.org [200.46.204.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9CFB543FF4 for ; Sun, 2 Jul 2006 16:22:37 +0000 (GMT) (envelope-from freebsd@hub.org) Received: from localhost (wm.hub.org [200.46.204.128]) by hub.org (Postfix) with ESMTP id 5776A2919EF; Sun, 2 Jul 2006 13:22:36 -0300 (ADT) Received: from hub.org ([200.46.204.220]) by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024) with ESMTP id 10301-01; Sun, 2 Jul 2006 16:22:37 +0000 (UTC) Received: from ganymede.hub.org (blk-7-151-244.eastlink.ca [71.7.151.244]) by hub.org (Postfix) with ESMTP id D5AB5290C6D; Sun, 2 Jul 2006 13:22:34 -0300 (ADT) Received: by ganymede.hub.org (Postfix, from userid 1027) id C139645DAA; Sun, 2 Jul 2006 13:22:34 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id BAB2C45B66; Sun, 2 Jul 2006 13:22:34 -0300 (ADT) Date: Sun, 2 Jul 2006 13:22:34 -0300 (ADT) From: User Freebsd To: Francisco Reyes In-Reply-To: Message-ID: <20060702132053.D1103@ganymede.hub.org> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: FreeBSD Stable List Subject: Re: High vmstat, filesystem unresponsive then hang 6.1 Stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Jul 2006 16:22:47 -0000 This is the same issue that I've been hitting, and that requires the serial console / DDB stuff described in the debugging deadlocks web page that I pointed you at ... So far *knock on wood* since adding all of the debugging to one of my server, none of mine have done it ... but the more ppl experiencing this, and getting the debugging in place to provide proper kernel traces, the better ... On Sat, 1 Jul 2006, Francisco Reyes wrote: > I believe this may be related to the NFS issues mentioned recent, but > hopefully I may have captured enough info to help others troubleshoot.. > I got the header of some ps commands.. and when was about to do full listing > of the same ps commands to files.. the machine hung up. > > The machine is 6.1 Stable around 6-25 ( plus or minus 1 day). > > > iostat 5 (not much of a load) > tty da0 cpu > tin tout KB/t tps MB/s us ni sy in id > 0 31 17.71 125 2.17 20 0 5 1 74 > 0 26 8.57 23 0.19 0 0 1 0 99 > 0 9 33.73 10 0.34 0 0 0 0 99 > 0 21 8.42 18 0.15 0 0 1 1 99 > 0 9 15.92 58 0.90 0 0 0 0 99 > 0 9 15.18 7 0.10 0 0 0 0 99 > 0 53 12.93 9 0.11 0 0 1 0 99 > 0 31 5.17 58 0.29 0 0 1 1 99 > > vmstat 5 (very high 'b' column) > procs memory page disk faults cpu > r b w avm fre flt re pi po fr sr da0 in sy cs us sy id > 0 248 2 1410436 110728 1519 2 0 0 1644 264 0 4481 8862 9168 20 6 74 > 0 248 0 1410436 110796 0 0 0 0 13 0 4 700 40 1426 0 1 99 > 0 248 0 1410436 110764 1 0 0 0 39 0 14 1253 722 2615 0 1 99 > 0 248 0 1410436 110720 1 0 0 0 10 0 5 407 396 899 0 1 99 > 0 248 0 1410436 110704 1 0 0 0 60 0 21 2822 360 5695 0 2 98 > 0 248 0 1410436 110684 1 0 0 0 10 0 7 538 434 1166 0 1 99 > 0 248 0 1410436 110668 0 0 0 0 75 0 51 576 163 1026 0 0 99 > 0 248 0 1410436 110696 0 0 0 0 23 0 31 1171 190 2271 0 1 99 > > vmstat 5 > procs memory page disk faults cpu > r b w avm fre flt re pi po fr sr da0 in sy cs us sy id > 0 250 1 1399688 152000 1517 2 0 0 1643 264 0 4479 8853 9163 20 6 74 > 0 250 0 1399688 151968 2 0 0 0 25 0 28 1395 966 2852 0 2 98 > 0 250 0 1399692 151892 1 0 0 0 12 0 6 446 540 986 0 0 99 > 0 250 2 1399692 151604 1 0 0 0 50 0 37 803 675 1611 0 1 99 > > > Don't recall which ps.. > 411 1 0 ufs ?? Ds 0:04.81 /usr/sbin/mountd -r > 37675 650 0 ufs ?? D 0:00.46 /usr/bin/perl > /data/backaway/mailarchive/client/bin/smtpproxy 127.0.0.1:10026 > 127.0.0.1:10025 (perl5.8.7) > 37919 650 0 ufs ?? D 0:00.46 /usr/bin/perl > /data/backaway/mailarchive/client/bin/smtpproxy 127.0.0.1:10026 > 127.0.0.1:10025 (perl5.8.7) > 39306 650 0 ufs ?? D 0:00.39 /usr/bin/perl > /data/backaway/mailarchive/client/bin/smtpproxy 127.0.0.1:10026 > 127.0.0.1:10025 (perl5.8.7) > 40214 38649 4100 ufs ?? Ds 0:00.00 /usr/local/bin/maildrop -d > nbilous@dialonewolfedale.com > 40220 32943 4100 ufs ?? Ds 0:00.00 /usr/local/bin/maildrop -d > jrowe@zoofriends.org > 40223 33257 4100 ufs ?? Ds 0:00.00 /usr/local/bin/maildrop -d > logmonitoring@ewarna.com > 40226 32942 4100 ufs ?? Ds 0:00.00 /usr/local/bin/maildrop -d > nbilous@dialonewolfedale.com > 40228 33199 4100 ufs ?? Ds 0:00.00 /usr/local/bin/maildrop -d > enquiries@markaw.com > 40231 38599 4100 ufs ?? Ds 0:00.00 /usr/local/bin/maildrop -d > snewman@starlo.com > 40233 32896 4100 ufs ?? Ds 0:00.00 /usr/local/bin/maildrop -d > pciuzio@microimage.cc > 40236 33224 4100 ufs ?? Ds 0:00.00 /usr/local/bin/maildrop -d > twilkerson@briorealty.com > 40238 32876 4100 ufs ?? Ds 0:00.00 /usr/local/bin/maildrop -d > ginnycash@reidrealestate.com > 40240 32976 4100 ufs ?? Ds 0:00.00 /usr/local/bin/maildrop -d > classic@classicrealtyinc.com > 40242 35580 4100 ufs ?? Ds 0:00.00 /usr/local/bin/maildrop -d > patrick.green@cifo.org > 40246 35593 4100 ufs ?? Ds 0:00.00 /usr/local/bin/maildrop -d > frizzelle@thestranger.com > 40248 32923 4100 ufs ?? Ds 0:00.00 /usr/local/bin/maildrop -d > earias@gkgcpa.com > 40252 35596 4100 ufs ?? Ds 0:00.01 /usr/local/bin/maildrop -d > seemckays@reidrealestate.com > 40253 29833 4100 ufs ?? Ds 0:00.01 /usr/local/bin/maildrop -d > seemckays@reidrealestate.com > > > > ps ax -O ppid,flags,mwchan | awk '$6 ~ /^D/ || $6 == "STAT"' > PID PPID F MWCHAN TT STAT TIME COMMAND > 2 0 204 - ?? DL 0:17.68 [g_event] > 3 0 204 - ?? DL 9:14.85 [g_up] > 4 0 204 - ?? DL 10:50.81 [g_down] > 5 0 204 - ?? DL 0:02.93 [thread taskq] > 6 0 204 - ?? DL 0:00.00 [acpi_task0] > 7 0 204 - ?? DL 0:00.00 [acpi_task1] > 8 0 204 - ?? DL 0:00.00 [acpi_task2] > 9 0 204 - ?? DL 0:00.00 [kqueue taskq] > 15 0 204 - ?? DL 8:47.55 [yarrow] > 27 0 204 - ?? DL 0:01.72 [fdc0] > 28 0 204 psleep ?? DL 0:43.74 [pagedaemon] > 29 0 204 psleep ?? DL 0:00.00 [vmdaemon] > 30 0 20c pgzero ?? DL 7:35.27 [pagezero] > 31 0 204 psleep ?? DL 0:57.11 [bufdaemon] > 32 0 204 syncer ?? DL 8:46.07 [syncer] > 33 0 204 vlruwt ?? DL 0:28.29 [vnlru] > 34 0 204 sdflus ?? DL 2:35.54 [softdepflush] > 35 0 204 - ?? DL 1:01.20 [schedcpu] > 411 1 0 ufs ?? Ds 0:04.81 /usr/sbin/mountd -r > 39306 650 0 ufs ?? D 0:00.39 /usr/bin/perl > /data/backaway/mailarchive/client/bin/smtpproxy 127.0.0.1:10026 > 127.0.0.1:10025 (perl5.8.7) > 40214 38649 4100 ufs ?? Ds 0:00.00 /usr/local/bin/maildrop -d > nbilous@dialonewolfedale.com > 40220 32943 4100 ufs ?? Ds 0:00.00 /usr/local/bin/maildrop -d > jrowe@zoofriends.org > 40223 33257 4100 ufs ?? Ds 0:00.00 /usr/local/bin/maildrop -d > logmonitoring@ewarna.com > 40226 32942 4100 ufs ?? Ds 0:00.00 /usr/local/bin/maildrop -d > nbilous@dialonewolfedale.com > 40228 33199 4100 ufs ?? Ds 0:00.00 /usr/local/bin/maildrop -d > enquiries@markaw.com > 40231 38599 4100 ufs ?? Ds 0:00.00 /usr/local/bin/maildrop -d > snewman@starlo.com > 40233 32896 4100 ufs ?? Ds 0:00.00 /usr/local/bin/maildrop -d > pciuzio@microimage.cc > 40236 33224 4100 ufs ?? Ds 0:00.00 /usr/local/bin/maildrop -d > twilkerson@briorealty.com > 40238 32876 4100 ufs ?? Ds 0:00.00 /usr/local/bin/maildrop -d > ginnycash@reidrealestate.com > 40240 32976 4100 ufs ?? Ds 0:00.00 /usr/local/bin/maildrop -d > classic@classicrealtyinc.com > 40242 35580 4100 ufs ?? Ds 0:00.00 /usr/local/bin/maildrop -d > patrick.green@cifo.org > 40246 35593 4100 ufs ?? Ds 0:00.00 /usr/local/bin/maildrop -d > frizzelle@thestranger.com > 40248 32923 4100 ufs ?? Ds 0:00.00 /usr/local/bin/maildrop -d > earias@gkgcpa.com > > > ps axlww > UID PID PPID CPU PRI NI VSZ RSS MWCHAN STAT TT TIME COMMAND > 0 0 0 0 12 0 0 0 - WLs ?? 0:00.00 [swapper] > 0 1 0 0 8 0 744 268 wait ILs ?? 0:00.01 /sbin/init > -- > 0 2 0 0 -8 0 0 8 - DL ?? 0:17.68 [g_event] > 0 3 0 0 -8 0 0 8 - DL ?? 9:14.93 [g_up] > 0 4 0 0 -8 0 0 8 - DL ?? 10:50.90 [g_down] > 0 5 0 0 8 0 0 8 - DL ?? 0:02.93 [thread > taskq] > 0 6 0 0 8 0 0 8 - DL ?? 0:00.00 > [acpi_task0] > 0 7 0 0 8 0 0 8 - DL ?? 0:00.00 > [acpi_task1] > 0 8 0 0 8 0 0 8 - DL ?? 0:00.00 > [acpi_task2] > 0 9 0 0 8 0 0 8 - DL ?? 0:00.00 [kqueue > taskq] > 0 10 0 153 171 0 0 8 - RL ?? 3939:36.70 [idle: > cpu1] > 0 11 0 148 171 0 0 8 - RL ?? 4416:30.08 [idle: > cpu0] > 0 12 0 2 -44 0 0 8 - WL ?? 50:41.76 [swi1: > net] > 0 13 0 0 -32 0 0 8 - WL ?? 8:56.20 [swi4: > clock sio] > 0 14 0 0 -36 0 0 8 - WL ?? 0:00.00 [swi3: vm] > 0 15 0 0 96 0 0 8 - DL ?? 8:47.68 [yarrow] > UID PID PPID CPU PRI NI VSZ RSS MWCHAN STAT TT TIME COMMAND > 0 0 0 0 12 0 0 0 - WLs ?? 0:00.00 [swapper] > 0 1 0 0 8 0 744 268 wait ILs ?? 0:00.01 /sbin/init > -- > 0 2 0 0 -8 0 0 8 - DL ?? 0:17.68 [g_event] > 0 3 0 0 -8 0 0 8 - DL ?? 9:14.93 [g_up] > 0 4 0 0 -8 0 0 8 - DL ?? 10:50.90 [g_down] > 0 5 0 0 8 0 0 8 - DL ?? 0:02.93 [thread > taskq] > 0 6 0 0 8 0 0 8 - DL ?? 0:00.00 > [acpi_task0] > 0 7 0 0 8 0 0 8 - DL ?? 0:00.00 > [acpi_task1] > 0 8 0 0 8 0 0 8 - DL ?? 0:00.00 > [acpi_task2] > 0 9 0 0 8 0 0 8 - DL ?? 0:00.00 [kqueue > taskq] > 0 10 0 153 171 0 0 8 - RL ?? 3939:36.70 [idle: > cpu1] > 0 11 0 148 171 0 0 8 - RL ?? 4416:30.08 [idle: > cpu0] > 0 12 0 2 -44 0 0 8 - WL ?? 50:41.76 [swi1: > net] > 0 13 0 0 -32 0 0 8 - WL ?? 8:56.20 [swi4: > clock sio] > 0 14 0 0 -36 0 0 8 - WL ?? 0:00.00 [swi3: vm] > 0 15 0 0 96 0 0 8 - DL ?? 8:47.68 [yarrow] > 0 16 0 0 -24 0 0 8 - WL ?? 0:00.01 [swi6: > task queue] > 0 17 0 0 -24 0 0 8 - WL ?? 0:00.00 [swi6: +] > 0 18 0 0 -28 0 0 8 - WL ?? 6:34.50 [swi5: +] > 0 19 0 0 -40 0 0 8 - WL ?? 6:42.62 [swi2: > cambio] > 0 20 0 0 -52 0 0 8 - WL ?? 0:00.00 [irq9: > acpi0] > 0 21 0 0 -64 0 0 8 - WL ?? 0:00.00 [irq14: > ata0] > 0 22 0 0 -64 0 0 8 - WL ?? 0:00.00 [irq15: > ata1] > 0 23 0 0 -68 0 0 8 - WL ?? 8:13.27 [irq26: > bge0] > 0 24 0 0 -68 0 0 8 - WL ?? 50:29.26 [irq27: > bge1] > 0 25 0 0 -60 0 0 8 - WL ?? 0:00.01 [irq1: > atkbd0] > 0 26 0 0 -48 0 0 8 - WL ?? 0:00.00 [swi0: > sio] > 0 27 0 0 -8 0 0 8 - DL ?? 0:01.72 [fdc0] > 0 28 0 0 -16 0 0 8 psleep DL ?? 0:43.74 > [pagedaemon] > 0 29 0 0 20 0 0 8 psleep DL ?? 0:00.00 [vmdaemon] > 0 30 0 0 171 0 0 8 pgzero DL ?? 7:35.27 [pagezero] > 0 31 0 0 -16 0 0 8 psleep DL ?? 0:57.11 > [bufdaemon] > 0 32 0 0 20 0 0 8 syncer DL ?? 8:46.35 [syncer] > 0 33 0 0 -4 0 0 8 vlruwt DL ?? 0:28.29 [vnlru] > 0 34 0 0 -16 0 0 8 sdflus DL ?? 2:35.54 > [softdepflush] > 0 35 0 0 -40 0 0 8 - DL ?? 1:01.29 [schedcpu] > 0 116 1 255 20 0 1220 648 pause Is ?? 0:00.00 adjkerntz > -i > 0 295 1 0 4 0 516 276 select Is ?? 0:05.71 /sbin/devd > 0 337 1 0 96 0 1344 908 select Ss ?? 5:54.01 > /usr/sbin/syslogd -s > 0 354 1 0 96 0 1412 1032 select Ss ?? 0:07.06 > /usr/sbin/rpcbind > 0 411 1 0 -4 0 1536 1128 ufs Ds ?? 0:04.81 > /usr/sbin/mountd -r > 0 413 1 0 4 0 1364 956 accept Is ?? 0:00.02 nfsd: > master (nfsd) > 0 414 413 4 4 0 1240 716 - S ?? 101:39.74 nfsd: > server (nfsd) > 0 415 413 0 4 0 1240 716 - S ?? 24:34.31 nfsd: > server (nfsd) > 0 416 413 0 4 0 1240 716 - S ?? 9:23.71 nfsd: > server (nfsd) > 0 417 413 0 4 0 1240 716 - S ?? 4:21.56 nfsd: > server (nfsd) > 0 419 413 0 4 0 1240 716 - I ?? 2:24.04 nfsd: > server (nfsd) > 0 420 413 0 4 0 1240 716 - I ?? 0:01.46 nfsd: > server (nfsd) > > Any insights would be greatly appreciated. > We are likely to try and downgrade to 5.5 stable.. 6.X has been nothing but > problems to us with regards to NFS.. both on the client and server. > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . scrappy@hub.org MSN . scrappy@hub.org Yahoo . yscrappy Skype: hub.org ICQ . 7615664 From owner-freebsd-stable@FreeBSD.ORG Sun Jul 2 17:05:32 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9C04616A403 for ; Sun, 2 Jul 2006 17:05:32 +0000 (UTC) (envelope-from freebsd-listen@fabiankeil.de) Received: from smtprelay01.ispgateway.de (smtprelay01.ispgateway.de [80.67.18.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6FAC444555 for ; Sun, 2 Jul 2006 17:05:31 +0000 (GMT) (envelope-from freebsd-listen@fabiankeil.de) Received: (qmail 19200 invoked from network); 2 Jul 2006 17:05:29 -0000 Received: from unknown (HELO localhost) (775067@[217.50.151.147]) (envelope-sender ) by smtprelay01.ispgateway.de (qmail-ldap-1.03) with SMTP for ; 2 Jul 2006 17:05:29 -0000 Date: Sun, 2 Jul 2006 19:05:20 +0200 From: Fabian Keil To: Robert Watson Message-ID: <20060702190520.3b344c83@localhost> In-Reply-To: <20060702170843.C67344@fledge.watson.org> References: <20060627175853.765a590e@localhost> <20060628101729.J50845@fledge.watson.org> <20060702173338.00a5ed44@localhost> <20060702170843.C67344@fledge.watson.org> X-Mailer: Sylpheed-Claws 2.2.3 (GTK+ 2.8.19; i386-portbld-freebsd6.1) X-PGP-KEY-URL: http://www.fabiankeil.de/gpg-keys/freebsd-listen-2006-08-19.asc User-Agent: 321 test Mime-Version: 1.0 Content-Type: multipart/signed; boundary="Sig_8.6DL+reQjOqcr=ZPMylzXF"; protocol="application/pgp-signature"; micalg=PGP-SHA1 Cc: Peter Thoenen , freebsd-stable@freebsd.org Subject: Re: FreeBSD 6.1 Tor issues (Once More, with Feeling) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Jul 2006 17:05:32 -0000 --Sig_8.6DL+reQjOqcr=ZPMylzXF Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Robert Watson wrote: > On Sun, 2 Jul 2006, Fabian Keil wrote: > > After manually triggering a test panic through debug.kdb.enter I > > could enter ddb and everything seemed to be working. > > > > However today I got another hang and couldn't enter the debugger by > > sending BREAK. It is the same BREAK ssh sends with ~B, right? > > > > Even after rebooting, sending break didn't trigger a panic, so > > either I'm sending the wrong BREAK, or my console settings are > > still messed up. Any ideas? >=20 > What serial software are you using to reach the console? I use ssh to log in to a console server, hit enter and am connected to the console. I have no idea what kind of software is used between console server and console. > Do you have options BREAK_TO_DEBUGGER compiled into your kernel? Yes, together with the other options you suggested: makeoptions DEBUG=3D-g options DDB #options KDB_UNATTENDED options KDB options BREAK_TO_DEBUGGER options WITNESS options WITNESS_SKIPSPIN options INVARIANTS options INVARIANT_SUPPORT > The delivery mechanism for the break will depend on the software > you're using... The ssh man page offers: |~B Send a BREAK to the remote system (only useful for SSH protocol | version 2 and if the peer supports it). I am using ssh 2, but the only reaction I get is a new line. |FreeBSD/i386 (tor.fabiankeil.de) (ttyd0) | |login: ~B | Maybe machdep.enable_panic_key would be another solution? The description says "Enable panic via keypress specified in kbdmap(5)", I'm just not sure if console input qualifies as "keypress". Fabian --=20 http://www.fabiankeil.de/ --Sig_8.6DL+reQjOqcr=ZPMylzXF Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEp/zWjV8GA4rMKUQRAj1aAKDpYy4TQaaNZKqbyU7czMvH60btmACg4RvR N0xpH+pDPZhKI48eL7uNHW4= =dA7g -----END PGP SIGNATURE----- --Sig_8.6DL+reQjOqcr=ZPMylzXF-- From owner-freebsd-stable@FreeBSD.ORG Sun Jul 2 17:24:48 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 92B9A16A40F for ; Sun, 2 Jul 2006 17:24:48 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 37A1443D45 for ; Sun, 2 Jul 2006 17:24:48 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id E2F9E46BA4; Sun, 2 Jul 2006 13:24:47 -0400 (EDT) Date: Sun, 2 Jul 2006 18:24:47 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Fabian Keil In-Reply-To: <20060702190520.3b344c83@localhost> Message-ID: <20060702182302.H80381@fledge.watson.org> References: <20060627175853.765a590e@localhost> <20060628101729.J50845@fledge.watson.org> <20060702173338.00a5ed44@localhost> <20060702170843.C67344@fledge.watson.org> <20060702190520.3b344c83@localhost> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Peter Thoenen , freebsd-stable@freebsd.org Subject: Re: FreeBSD 6.1 Tor issues (Once More, with Feeling) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Jul 2006 17:24:48 -0000 On Sun, 2 Jul 2006, Fabian Keil wrote: > Robert Watson wrote: > >> On Sun, 2 Jul 2006, Fabian Keil wrote: > >>> After manually triggering a test panic through debug.kdb.enter I >>> could enter ddb and everything seemed to be working. >>> >>> However today I got another hang and couldn't enter the debugger by >>> sending BREAK. It is the same BREAK ssh sends with ~B, right? >>> >>> Even after rebooting, sending break didn't trigger a panic, so >>> either I'm sending the wrong BREAK, or my console settings are >>> still messed up. Any ideas? >> >> What serial software are you using to reach the console? > > I use ssh to log in to a console server, hit enter and am connected to the > console. I have no idea what kind of software is used between console server > and console. You probably need to find out in order to find out what break sequence to send. Alternatively, you can use ALT_BREAK_TO_DEBUGGER, which defines an alternative break sequence without relying on a serial break (which is an out-of-band break signal). >> The delivery mechanism for the break will depend on the software you're >> using... > > The ssh man page offers: > > |~B Send a BREAK to the remote system (only useful for SSH protocol > | version 2 and if the peer supports it). > > I am using ssh 2, but the only reaction I get is a new line. > > |FreeBSD/i386 (tor.fabiankeil.de) (ttyd0) > | > |login: ~B > | It sounds like your serial console server may not know how to map SSH break signals into remote serial break signals. Try ALT_BREAK_TO_DEBUGGER. Here's the description from NOTES: # Solaris implements a new BREAK which is initiated by a character # sequence CR ~ ^b which is similar to a familiar pattern used on # Sun servers by the Remote Console. options ALT_BREAK_TO_DEBUGGER Robert N M Watson Computer Laboratory University of Cambridge From owner-freebsd-stable@FreeBSD.ORG Sun Jul 2 19:23:50 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 698E316A417 for ; Sun, 2 Jul 2006 19:23:50 +0000 (UTC) (envelope-from freebsd-listen@fabiankeil.de) Received: from smtprelay01.ispgateway.de (smtprelay01.ispgateway.de [80.67.18.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id 146A543D58 for ; Sun, 2 Jul 2006 19:23:48 +0000 (GMT) (envelope-from freebsd-listen@fabiankeil.de) Received: (qmail 27167 invoked from network); 2 Jul 2006 19:23:47 -0000 Received: from unknown (HELO localhost) (775067@[217.50.151.147]) (envelope-sender ) by smtprelay01.ispgateway.de (qmail-ldap-1.03) with SMTP for ; 2 Jul 2006 19:23:47 -0000 Date: Sun, 2 Jul 2006 21:23:35 +0200 From: Fabian Keil To: Robert Watson Message-ID: <20060702212335.0bf121be@localhost> In-Reply-To: <20060702182302.H80381@fledge.watson.org> References: <20060627175853.765a590e@localhost> <20060628101729.J50845@fledge.watson.org> <20060702173338.00a5ed44@localhost> <20060702170843.C67344@fledge.watson.org> <20060702190520.3b344c83@localhost> <20060702182302.H80381@fledge.watson.org> X-Mailer: Sylpheed-Claws 2.2.3 (GTK+ 2.8.19; i386-portbld-freebsd6.1) X-PGP-KEY-URL: http://www.fabiankeil.de/gpg-keys/freebsd-listen-2006-08-19.asc User-Agent: 321 test Mime-Version: 1.0 Content-Type: multipart/signed; boundary="Sig_=X5.3dpWhQoZs7E3vnqvSQr"; protocol="application/pgp-signature"; micalg=PGP-SHA1 Cc: Peter Thoenen , freebsd-stable@freebsd.org Subject: Re: FreeBSD 6.1 Tor issues (Once More, with Feeling) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Jul 2006 19:23:50 -0000 --Sig_=X5.3dpWhQoZs7E3vnqvSQr Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Robert Watson wrote: > On Sun, 2 Jul 2006, Fabian Keil wrote: > > I am using ssh 2, but the only reaction I get is a new line. > > > > |FreeBSD/i386 (tor.fabiankeil.de) (ttyd0) > > | > > |login: ~B > > | >=20 > It sounds like your serial console server may not know how to map SSH > break signals into remote serial break signals. Try > ALT_BREAK_TO_DEBUGGER. Here's the description from NOTES: >=20 > # Solaris implements a new BREAK which is initiated by a character > # sequence CR ~ ^b which is similar to a familiar pattern used on > # Sun servers by the Remote Console. > options ALT_BREAK_TO_DEBUGGER It took me several attempts to get the character sequence right, but yes, this one works. Thanks. Fabian --=20 http://www.fabiankeil.de/ --Sig_=X5.3dpWhQoZs7E3vnqvSQr Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEqB1AjV8GA4rMKUQRApj6AJ4+exbwTqrTo+Kd+1z1ePnugHYuuACeMYzG BjG0u3Sj8DFYaO+FyP3uT8Y= =kHX/ -----END PGP SIGNATURE----- --Sig_=X5.3dpWhQoZs7E3vnqvSQr-- From owner-freebsd-stable@FreeBSD.ORG Sun Jul 2 19:32:36 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6FEB316A403; Sun, 2 Jul 2006 19:32:36 +0000 (UTC) (envelope-from dan@dan.emsphone.com) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 10D0C43D45; Sun, 2 Jul 2006 19:32:35 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.13.1/8.13.4) id k62JWOOQ024337; Sun, 2 Jul 2006 14:32:24 -0500 (CDT) (envelope-from dan) Date: Sun, 2 Jul 2006 14:32:24 -0500 From: Dan Nelson To: Robert Watson Message-ID: <20060702193224.GD4915@dan.emsphone.com> References: <20060627175853.765a590e@localhost> <20060628101729.J50845@fledge.watson.org> <20060702173338.00a5ed44@localhost> <20060702170843.C67344@fledge.watson.org> <20060702190520.3b344c83@localhost> <20060702182302.H80381@fledge.watson.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060702182302.H80381@fledge.watson.org> X-OS: FreeBSD 5.5-PRERELEASE X-message-flag: Outlook Error User-Agent: Mutt/1.5.11 Cc: Peter Thoenen , freebsd-stable@freebsd.org Subject: Re: FreeBSD 6.1 Tor issues (Once More, with Feeling) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Jul 2006 19:32:36 -0000 In the last episode (Jul 02), Robert Watson said: > On Sun, 2 Jul 2006, Fabian Keil wrote: > >The ssh man page offers: > > > >|~B Send a BREAK to the remote system (only useful for SSH > >| protocol version 2 and if the peer supports it). > > > >I am using ssh 2, but the only reaction I get is a new line. > > > >|FreeBSD/i386 (tor.fabiankeil.de) (ttyd0) > >| > >|login: ~B If you enter ~B and actually see a ~B printed to the screen, then ssh didn't process it because you didn't hit first. So ~B will tell ssh to send a break. > It sounds like your serial console server may not know how to map SSH > break signals into remote serial break signals. Try > ALT_BREAK_TO_DEBUGGER. Here's the description from NOTES: > > # Solaris implements a new BREAK which is initiated by a character > # sequence CR ~ ^b which is similar to a familiar pattern used on > # Sun servers by the Remote Console. > options ALT_BREAK_TO_DEBUGGER ... and if you're sshing to your terminal server, remember that ssh will eat that tilde (because you sent ~ ), so you need to send ~~^B to pass the right characters to FreeBSD. Or change ssh's escape character with the -e flag. -- Dan Nelson dnelson@allantgroup.com From owner-freebsd-stable@FreeBSD.ORG Sun Jul 2 20:07:13 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2DD8416A47C for ; Sun, 2 Jul 2006 20:07:13 +0000 (UTC) (envelope-from freebsd@hub.org) Received: from hub.org (hub.org [200.46.204.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id B17DF43DA8 for ; Sun, 2 Jul 2006 19:34:10 +0000 (GMT) (envelope-from freebsd@hub.org) Received: from localhost (wm.hub.org [200.46.204.128]) by hub.org (Postfix) with ESMTP id 25CE32919EF; Sun, 2 Jul 2006 16:34:07 -0300 (ADT) Received: from hub.org ([200.46.204.220]) by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024) with ESMTP id 10301-07; Sun, 2 Jul 2006 19:34:10 +0000 (UTC) Received: from ganymede.hub.org (blk-7-151-244.eastlink.ca [71.7.151.244]) by hub.org (Postfix) with ESMTP id 0BE6E290C6D; Sun, 2 Jul 2006 16:34:06 -0300 (ADT) Received: by ganymede.hub.org (Postfix, from userid 1027) id 0CA404853F; Sun, 2 Jul 2006 16:34:10 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id 05B5233DF1; Sun, 2 Jul 2006 16:34:10 -0300 (ADT) Date: Sun, 2 Jul 2006 16:34:09 -0300 (ADT) From: User Freebsd To: Francisco Reyes In-Reply-To: Message-ID: <20060702162942.D1103@ganymede.hub.org> References: <20060629230309.GA12773@lpthe.jussieu.fr> <20060630041733.GA4941@zibbi.meraka.csir.co.za> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org, Michel Talon Subject: Re: NFS Locking Issue X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Jul 2006 20:07:13 -0000 On Sat, 1 Jul 2006, Francisco Reyes wrote: > John Hay writes: > >> I only started to see the lockd problems when upgrading the server side >> to FreeBSD 6.x and later. I had various FreeBSD clients, between 4.x >> and 7-current and the lockd problem only showed up when upgrading the >> server from 5.x to 6.x. > > It confirms the same we are experiencing.. constant freezing/locking issues. > I guess no more 6.X for us.. for the foreseable future.. Since there are several of us experiencing what looks to be the same sort of deadlock issue, I beseech you not to give up ... right now, all we've been able to get to the developers is virtually useless information (vmstat and such shows the problem, but it doesn't allow developers to identify the problem) ... Is this a problem that you can easily recreate, even on a non-production machine? In my case, I have one machine fully configured for debugging, but, of course, since re-configuring it, it hasn't exhibited the problem ... if most of us get our machines configured properly to give useful information to the developers to debug this, the faster it will get fixed ... My experience with most of the developers is that if you can get into DDB and give them 'internal traces' of the code, bugs tend to get fixed very quickly ... vmstat/ps give "external views", more summaries then anything ... its the details "under the hood" that they need ... its not much different then your auto-mechanic ... try telling him there is a 'knocking under the hood, please tell me how to fix it, but you can't have my car', and he'll brush you off ... give him 30 minutes under the hood, and not only will he have identified it, but he'll probably fix it too ... ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . scrappy@hub.org MSN . scrappy@hub.org Yahoo . yscrappy Skype: hub.org ICQ . 7615664 From owner-freebsd-stable@FreeBSD.ORG Sun Jul 2 21:41:03 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 58CE716A47B; Sun, 2 Jul 2006 21:41:03 +0000 (UTC) (envelope-from ohartman@mail.uni-mainz.de) Received: from mailgate1.zdv.Uni-Mainz.DE (mailgate1.zdv.Uni-Mainz.DE [134.93.178.129]) by mx1.FreeBSD.org (Postfix) with ESMTP id 02FAA43E2C; Sun, 2 Jul 2006 21:41:02 +0000 (GMT) (envelope-from ohartman@mail.uni-mainz.de) Received: from [192.168.1.128] (e178003000.adsl.alicedsl.de [85.178.3.0]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailgate1.zdv.Uni-Mainz.DE (Postfix) with ESMTP id C76C33011B22; Sun, 2 Jul 2006 23:41:01 +0200 (CEST) Message-ID: <44A83D69.7010006@mail.uni-mainz.de> Date: Sun, 02 Jul 2006 23:40:57 +0200 From: "O. Hartmann" User-Agent: Thunderbird 1.5.0.4 (X11/20060612) MIME-Version: 1.0 To: freebsd-amd64@freebsd.org, freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at uni-mainz.de Cc: Subject: dd on USB 2.0 device (OHCI) horrible slow X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Jul 2006 21:41:03 -0000 Hello. Tried today to delete and prepare a fresh installed external USB 2.0 drive as GELI provider, here is the result of an aborted dd: sotokan# dd if=/dev/random of=/dev/da0a.eli bs=16k ^C8388825+0 records in 8388824+0 records out 137442492416 bytes transferred in 33883.288406 secs (4056350 bytes/sec) system is a FreeBSD 6.1-STABEL/amd64 box, hardware ASUS A8N32-SLI Deluxe with AMD64 3500+ From owner-freebsd-stable@FreeBSD.ORG Sun Jul 2 21:41:51 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 02C3816A494 for ; Sun, 2 Jul 2006 21:41:51 +0000 (UTC) (envelope-from torfinn.ingolfsen@broadpark.no) Received: from osl1smout1.broadpark.no (osl1smout1.broadpark.no [80.202.4.58]) by mx1.FreeBSD.org (Postfix) with ESMTP id F046F43E01 for ; Sun, 2 Jul 2006 21:41:40 +0000 (GMT) (envelope-from torfinn.ingolfsen@broadpark.no) Received: from osl1sminn1.broadpark.no ([80.202.4.59]) by osl1smout1.broadpark.no (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with ESMTP id <0J1S00CBGPLFU180@osl1smout1.broadpark.no> for freebsd-stable@freebsd.org; Sun, 02 Jul 2006 23:41:39 +0200 (CEST) Received: from kg-work.kg4.no ([80.203.92.117]) by osl1sminn1.broadpark.no (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with SMTP id <0J1S00CC7PLFPKO0@osl1sminn1.broadpark.no> for freebsd-stable@freebsd.org; Sun, 02 Jul 2006 23:41:39 +0200 (CEST) Date: Sun, 02 Jul 2006 23:41:39 +0200 From: Torfinn Ingolfsen X-Face: "t9w2,-X@O^I`jVW\sonI3.,36KBLZE*AL[y9lL[PyFD*r_S:dIL9c[8Y>V42R0"!"yb_zN,f#%.[PYYNq; m"_0v; ~rUM2Yy!zmkh)3&U|u!=T(zyv,MHJv"nDH>OJ`t(@mil461d_B'Uo|'nMwlKe0Mv=kvV?Nh@>Hb<3s_z2jYgZhPb@?Wi^x1a~Hplz1.zH In-reply-to: <44A7CB60.4010102@vwsoft.com> To: freebsd-stable@freebsd.org Message-id: <20060702234139.28a4d3b5.torfinn.ingolfsen@broadpark.no> MIME-version: 1.0 X-Mailer: Sylpheed version 2.2.5 (GTK+ 2.8.19; i386-portbld-freebsd5.5) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT References: <200607021408.33744.dzalewski@open-craft.com> <44A7CB60.4010102@vwsoft.com> Subject: Re: Portupgrade failed - /var/db/pkg/pkgdb.db: unexpected file type or format X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Jul 2006 21:41:51 -0000 On Sun, 02 Jul 2006 15:34:24 +0200 Volker wrote: > I've had the same today and thought it has been my mistake (doing a > pkg_version in parallel). Ther seems to ne a problem with the latest version of portupgrade, this happened for me on two 6-stable systems (one i386, the other amd64) today. Anyway, the mentioned methods fixes the problem. -- Regards, Torfinn Ingolfsen, Norway From owner-freebsd-stable@FreeBSD.ORG Sun Jul 2 21:49:45 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8195C16A407 for ; Sun, 2 Jul 2006 21:49:45 +0000 (UTC) (envelope-from lists@stringsutils.com) Received: from zoraida.natserv.net (p65-147.acedsl.com [66.114.65.147]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1FA7F43FDA for ; Sun, 2 Jul 2006 21:49:44 +0000 (GMT) (envelope-from lists@stringsutils.com) Received: from zoraida.natserv.net (localhost.natserv.net [127.0.0.1]) by zoraida.natserv.net (Postfix) with ESMTP id 5506AB822; Sun, 2 Jul 2006 17:49:44 -0400 (EDT) Received: from zoraida.natserv.net (zoraida.natserv.net [66.114.65.147]) by zoraida.natserv.net (Postfix) with ESMTP id 20C9BB81F; Sun, 2 Jul 2006 17:49:44 -0400 (EDT) References: <20060629230309.GA12773@lpthe.jussieu.fr> <20060630041733.GA4941@zibbi.meraka.csir.co.za> <20060702162942.D1103@ganymede.hub.org> Message-ID: X-Mailer: http://www.courier-mta.org/cone/ From: Francisco Reyes To: User Freebsd Date: Sun, 02 Jul 2006 17:49:44 -0400 Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset="US-ASCII" Content-Disposition: inline Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Cc: freebsd-stable@freebsd.org, Michel Talon Subject: Re: NFS Locking Issue X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Jul 2006 21:49:45 -0000 User Freebsd writes: > Since there are several of us experiencing what looks to be the same sort > of deadlock issue, I beseech you not to give up I will try to setup the environment, but to be honest no more 6.X for us until 6.2 or 6.3.. We have lost clients already. > Is this a problem that you can easily recreate There is one thing I can easily recreate that would very helpfull to solve. The 6.X NFS clients freeze if the NFS server goes away. I have been able to reproduce that every single time.. both in test and production. > machine? In my case, I have one machine fully configured for debugging, Although solving both, server and client, would be great for us if we could at least solve the client.. it would be very helpfull.. until our next server comes.. in which we are going to install 5.5 > information to the developers to debug this, the faster it will get fixed Agree.. but with 4+ crashes in less than a week it has reached the point where we have moved workload away from the most problematic machine.. to try to aliviate the problem.. but still was not enough.. to prevent at least one big customer of ours to go.. We don't keep tight track of the smaller ones. :-) > different then your auto-mechanic ... try telling him there is a 'knocking > under the hood, please tell me how to fix it, but you can't have my car', > and he'll brush you off ... give him 30 minutes under the hood, and not > only will he have identified it, but he'll probably fix it too ... The problem is when you are a taxi driver... and it cost you money to have the car off the streets.. and you don't know when the 'knocking' will occur... :-) Will setup my laptop with the debug settings and will then work on trying to debug the client problem... depending on how that goes will then possibly try the server that is giving us problems. From owner-freebsd-stable@FreeBSD.ORG Sun Jul 2 22:48:46 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4265216A415 for ; Sun, 2 Jul 2006 22:48:46 +0000 (UTC) (envelope-from pieter@degoeje.nl) Received: from smtp.utwente.nl (smtp2.utsp.utwente.nl [130.89.2.9]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6B1E744520 for ; Sun, 2 Jul 2006 22:48:44 +0000 (GMT) (envelope-from pieter@degoeje.nl) Received: from nox.student.utwente.nl (nox.student.utwente.nl [130.89.165.91]) by smtp.utwente.nl (8.12.10/SuSE Linux 0.7) with ESMTP id k62Mme8l029296; Mon, 3 Jul 2006 00:48:40 +0200 From: Pieter de Goeje To: ASTESIN Date: Mon, 3 Jul 2006 00:48:39 +0200 User-Agent: KMail/1.9.3 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200607030048.39920.pieter@degoeje.nl> X-UTwente-MailScanner-Information: Scanned by MailScanner. Contact helpdesk@ITBE.utwente.nl for more information. X-UTwente-MailScanner: Found to be clean X-UTwente-MailScanner-From: pieter@degoeje.nl X-Spam-Status: No Cc: freebsd-stable@freebsd.org Subject: Re: 6-STABLE on 6 Gb RAM 2 x Xeon 3.0 HTT & GDT RAID5 - how? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Jul 2006 22:48:46 -0000 On Saturday 01 July 2006 21:24, ASTESIN wrote: > Purpose: just Apache + mod_perl + MySQL 5.x application server. > Install went fine, system boots, I'm going to try PAE kernel on it. But > somathing makes me doubt that things are going on well... > > I.e. I worry about strange messages in dmesg output with regard to ACPI, I'm not sure if they're harmful. > see below; will iir0 work with PAE? See PAE(4). According to /usr/src/sys/i386/conf/PAE device iir should work. Regards, Pieter From owner-freebsd-stable@FreeBSD.ORG Sun Jul 2 22:54:17 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EB9C916A52D; Sun, 2 Jul 2006 22:54:17 +0000 (UTC) (envelope-from tbyte@otel.net) Received: from mail.otel.net (gw3.OTEL.net [212.36.8.151]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6C0DA43E87; Sun, 2 Jul 2006 22:22:15 +0000 (GMT) (envelope-from tbyte@otel.net) Received: from warhead.otel.net ([212.36.8.210]) by mail.otel.net with esmtp (Exim 4.62 (FreeBSD)) (envelope-from ) id 1FxAKT-0006AS-1N; Mon, 03 Jul 2006 01:22:13 +0300 MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit X-send-pr-version: gtk-send-pr 0.4.7 X-GNATS-Notify: Date: Mon, 3 Jul 2006 01:22:12 +0300 From: "Iasen Kostoff" Message-Id: <1151878932.16831@WarHeaD.OTEL.net> To: "FreeBSD gnats submit" Cc: freebsd-stable@freebsd.org Subject: Bug in ata (ata-all.c) driver X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Jul 2006 22:54:18 -0000 >Submitter-Id: stable-users >Originator: Iasen Kostoff >Organization: OTEL.net >Confidential: no >Synopsis: Bug in ata (ata-all.c) driver >Severity: serious >Priority: medium >Category: kern >Class: sw-bug >Release: FreeBSD 6.1-STABLE i386 >Environment: System: FreeBSD 6.1-STABLE #2: Sat Jul 1 13:01:14 EEST 2006 root@WarHeaD.OTEL.net:/usr/src6/sys/i386/compile/WARHEAD >Description: I found a little bug (probably) in sys/dev/ata-all.c which somehow corrupts device parameters structure. When I first did "atacontrol list" device info about ad0 looked like this: Master: ad0 ATA/ATAPI revision 7 after I ran "atacontrol cap ad0" it printed somewhat messy output like having enabled SMART but not supported... then I did "atacontrol list" again and saw that the line about ad0 have changed to something like this: Master: ad0 ATA/ATAPI revision 0 or similar. After some digging and comparing the way "IOCATADEVICES" and "IOCATAGPARM" work I saw (probably) bogus ata_getparam() call. After removing this call to ata_getparam() everything work as expected (atleast that's what it looks like for ~30 min run). "atacontrol cap ad0" shows right results and doesn't screw the device parameters. I just hope that this doesn't break something else but I doubt it coz it just gets info and doesn't set anything. >How-To-Repeat: In description. >Fix: --- ata-all.c.old Sat Jul 1 04:10:30 2006 +++ ata-all.c Sat Jul 1 04:40:26 2006 @@ -505,7 +505,6 @@ return error; case IOCATAGPARM: - ata_getparam(atadev, 0); bcopy(&atadev->param, params, sizeof(struct ata_params)); return 0; From owner-freebsd-stable@FreeBSD.ORG Mon Jul 3 04:20:19 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0371F16A403 for ; Mon, 3 Jul 2006 04:20:18 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from fw.zoral.com.ua (ll-227.216.82.212.sovam.net.ua [212.82.216.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2A73C43D45 for ; Mon, 3 Jul 2006 04:20:17 +0000 (GMT) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by fw.zoral.com.ua (8.13.4/8.13.4) with ESMTP id k634KCOw030611 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 3 Jul 2006 07:20:12 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.13.6/8.13.6) with ESMTP id k634KBD1041490; Mon, 3 Jul 2006 07:20:11 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.13.6/8.13.6/Submit) id k634KAOJ041489; Mon, 3 Jul 2006 07:20:10 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Mon, 3 Jul 2006 07:20:10 +0300 From: Kostik Belousov To: Francisco Reyes Message-ID: <20060703042010.GG37822@deviant.kiev.zoral.com.ua> References: <20060629230309.GA12773@lpthe.jussieu.fr> <20060630041733.GA4941@zibbi.meraka.csir.co.za> <20060702162942.D1103@ganymede.hub.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="vKFfOv5t3oGVpiF+" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i X-Virus-Scanned: ClamAV version 0.88.2, clamav-milter version 0.88.2 on fw.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=0.4 required=5.0 tests=ALL_TRUSTED, DNS_FROM_RFC_ABUSE,SPF_NEUTRAL autolearn=no version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on fw.zoral.com.ua Cc: freebsd-stable@freebsd.org, Michel Talon , User Freebsd Subject: Re: NFS Locking Issue X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Jul 2006 04:20:19 -0000 --vKFfOv5t3oGVpiF+ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Jul 02, 2006 at 05:49:44PM -0400, Francisco Reyes wrote: > User Freebsd writes: >=20 > >Since there are several of us experiencing what looks to be the same sor= t=20 > >of deadlock issue, I beseech you not to give up >=20 > I will try to setup the environment, but to be honest no more 6.X for us= =20 > until 6.2 or 6.3.. We have lost clients already. I think that then 6.2 and 6.3 is not for you either. Problems cannot be fixed until enough information is given. Since nobody except you experience that problems (at least, only you notified about the problem existence), no bug reports with sufficient information is given. >=20 > >Is this a problem that you can easily recreate >=20 > There is one thing I can easily recreate that would very helpfull to solv= e. > The 6.X NFS clients freeze if the NFS server goes away. >=20 > I have been able to reproduce that every single time.. both in test and= =20 > production. Is this for intr mounts ? I posted some time ago the patches that improved handling of signals in nfs client. If you could test it, that would be useful. ? sys/nfsclient/.arch-ids Index: sys/nfsclient/nfs_socket.c =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /usr/local/arch/ncvs/src/sys/nfsclient/nfs_socket.c,v retrieving revision 1.141 diff -u -r1.141 nfs_socket.c --- sys/nfsclient/nfs_socket.c 23 May 2006 18:33:58 -0000 1.141 +++ sys/nfsclient/nfs_socket.c 3 Jul 2006 04:19:23 -0000 @@ -1701,11 +1701,13 @@ p =3D td->td_proc; PROC_LOCK(p); tmpset =3D p->p_siglist; + SIGSETOR(tmpset, td->td_siglist); SIGSETNAND(tmpset, td->td_sigmask); mtx_lock(&p->p_sigacts->ps_mtx); SIGSETNAND(tmpset, p->p_sigacts->ps_sigignore); mtx_unlock(&p->p_sigacts->ps_mtx); - if (SIGNOTEMPTY(p->p_siglist) && nfs_sig_pending(tmpset)) { + if ((SIGNOTEMPTY(p->p_siglist) || SIGNOTEMPTY(td->td_siglist)) + && nfs_sig_pending(tmpset)) { PROC_UNLOCK(p); return (EINTR); } Index: sys/nfsclient/nfs_vnops.c =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /usr/local/arch/ncvs/src/sys/nfsclient/nfs_vnops.c,v retrieving revision 1.266 diff -u -r1.266 nfs_vnops.c --- sys/nfsclient/nfs_vnops.c 19 May 2006 00:04:24 -0000 1.266 +++ sys/nfsclient/nfs_vnops.c 3 Jul 2006 04:19:24 -0000 @@ -2716,7 +2716,7 @@ * otherwise just do it ourselves. */ if ((bp->b_flags & B_ASYNC) =3D=3D 0 || - nfs_asyncio(VFSTONFS(ap->a_vp->v_mount), bp, NOCRED, td)) + nfs_asyncio(VFSTONFS(ap->a_vp->v_mount), bp, NOCRED, curthread)) (void)nfs_doio(ap->a_vp, bp, cr, td); return (0); } --vKFfOv5t3oGVpiF+ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) iD8DBQFEqJr6C3+MBN1Mb4gRAs0QAJ9PPTCtdFjWFJC3osU7OsoneGqNWwCfcOqF mC49Qg5T6AICokwWe863s5E= =0oBr -----END PGP SIGNATURE----- --vKFfOv5t3oGVpiF+-- From owner-freebsd-stable@FreeBSD.ORG Mon Jul 3 04:23:54 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E3F9C16A403 for ; Mon, 3 Jul 2006 04:23:54 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 42BF843D46 for ; Mon, 3 Jul 2006 04:23:53 +0000 (GMT) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (inchoate.gsoft.com.au [203.31.81.44]) (authenticated bits=0) by cain.gsoft.com.au (8.13.5/8.13.4) with ESMTP id k634NlXm035949 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 3 Jul 2006 13:53:47 +0930 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: freebsd-stable@freebsd.org Date: Mon, 3 Jul 2006 13:53:40 +0930 User-Agent: KMail/1.9.3 References: <200606301021.35529.doconnor@gsoft.com.au> In-Reply-To: <200606301021.35529.doconnor@gsoft.com.au> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1254761.lNOFAKeg5I"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200607031353.42158.doconnor@gsoft.com.au> X-Spam-Score: -1.36 () ALL_TRUSTED X-Scanned-By: MIMEDefang 2.56 on 203.31.81.10 Subject: Re: 6.1-STABLE panic X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Jul 2006 04:23:55 -0000 --nextPart1254761.lNOFAKeg5I Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Friday 30 June 2006 10:21, Daniel O'Connor wrote: > I have an odd problem with 6.1 where it panics, and then when it reboots > the system hangs solid just after printing how much memory is in the > system, the only way out is the reset switch. > Fatal trap 12: page fault while in kernel mode > fault virtual address =3D 0xb6 > fault code =3D supervisor read, page not present > instruction pointer =3D 0x20:0xc0512564 > stack pointer =3D 0x28:0xdea06b1c > frame pointer =3D 0x28:0xdea06b4c I got another one in 'rtorrent' (BitTorrent client) with exactly the same stack & frame pointer and stack trace. #7 0xc0512564 in soo_poll (fp=3D0x54, events=3D-557274220, active_cred=3D0= xdec8ab84, td=3D0x122) at /data/src/sys/kern/sys_socket.c:232 232 { Current language: auto; currently c (kgdb) list 227 soo_poll(fp, events, active_cred, td) 228 struct file *fp; 229 int events; 230 struct ucred *active_cred; 231 struct thread *td; 232 { 233 struct socket *so =3D fp->f_data; 234 int error; 235 236 NET_LOCK_GIANT(); (kgdb) print so $1 =3D (struct socket *) 0xc48f8300 (kgdb) print fp $2 =3D (struct file *) 0x54 (kgdb) print fp->f_data Cannot access memory at address 0x60 (kgdb) up #8 0xc050cff1 in kern_select (td=3D0xc48f8300, nd=3D290, fd_in=3D0x8122000, fd_ou=3D0x8122400, fd_ex=3D0x8122800, tvp=3D0xdec8acd0) at /data/src/sys/kern/sys_generic.c:763 763 error =3D selscan(td, ibits, obits, nd); (kgdb) print td $3 =3D (struct thread *) 0xc48f8300 (kgdb) print ibits $4 =3D {0xdec8ac1c, 0xdec8ac44, 0xdec8ac6c} (kgdb) print obits $5 =3D {0xdec8aba4, 0xdec8abcc, 0xdec8abf4} (kgdb) print nd $6 =3D 290 =2E.. I don't know where the stack frame for selscan went.. Does anyone else see this? It is fairly frequent and is getting a bit frustrating :) =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart1254761.lNOFAKeg5I Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQBEqJvO5ZPcIHs/zowRAnXxAKCHEQt/497YZJ3doewaIVeltt3JhQCfavQo pHWiWByeLoGCo35ZlRR88bI= =4E9/ -----END PGP SIGNATURE----- --nextPart1254761.lNOFAKeg5I-- From owner-freebsd-stable@FreeBSD.ORG Mon Jul 3 04:50:13 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BD4D716A416 for ; Mon, 3 Jul 2006 04:50:13 +0000 (UTC) (envelope-from lists@stringsutils.com) Received: from zoraida.natserv.net (p65-147.acedsl.com [66.114.65.147]) by mx1.FreeBSD.org (Postfix) with ESMTP id 35E65440E7 for ; Mon, 3 Jul 2006 04:50:13 +0000 (GMT) (envelope-from lists@stringsutils.com) Received: from zoraida.natserv.net (localhost.natserv.net [127.0.0.1]) by zoraida.natserv.net (Postfix) with ESMTP id 08768B822; Mon, 3 Jul 2006 00:50:12 -0400 (EDT) Received: from zoraida.natserv.net (zoraida.natserv.net [66.114.65.147]) by zoraida.natserv.net (Postfix) with ESMTP id BEFDFB81F; Mon, 3 Jul 2006 00:50:11 -0400 (EDT) References: <20060629230309.GA12773@lpthe.jussieu.fr> <20060630041733.GA4941@zibbi.meraka.csir.co.za> <20060702162942.D1103@ganymede.hub.org> <20060703042010.GG37822@deviant.kiev.zoral.com.ua> Message-ID: X-Mailer: http://www.courier-mta.org/cone/ From: Francisco Reyes To: Kostik Belousov Date: Mon, 03 Jul 2006 00:50:11 -0400 Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset="US-ASCII" Content-Disposition: inline Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Cc: freebsd-stable@freebsd.org, User Freebsd Subject: Re: NFS Locking Issue X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Jul 2006 04:50:13 -0000 Kostik Belousov writes: > I think that then 6.2 and 6.3 is not for you either. Problems > cannot be fixed until enough information is given. I am trying.. but so far only other users who are having the same problem are commenting on this and other simmilar threads. We just need some guidance.. Mark gave me a URL to turn on debugging and volunteered ot give me some pointers.. I will try, but I will likely try on my own time, on my own machines.. I can not tell the owner of the company I work for to let me "try".. or "play around" in production machines.. as we loose customers because of current problems with the 6.X line. > Since nobody except you experience that problems (at least, only you notified > about the problem existence) Did you miss the part of: > User Freebsd writes: >>Since there are several of us experiencing what looks to be the same sort >>of deadlock issue, I beseech you not to give up I am not the only one reporting or having the issue. > Is this for intr mounts? "intr" ? > improved handling of signals in nfs client. If you could test it, that > would be useful. Does it matter if the OS is i386 or am64? Have an amd64 machine I can more easily play with... with no risk to production. From owner-freebsd-stable@FreeBSD.ORG Mon Jul 3 04:59:02 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E0B6516A417 for ; Mon, 3 Jul 2006 04:59:02 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from fw.zoral.com.ua (ll-227.216.82.212.sovam.net.ua [212.82.216.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id E00D7440E7 for ; Mon, 3 Jul 2006 04:59:00 +0000 (GMT) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by fw.zoral.com.ua (8.13.4/8.13.4) with ESMTP id k634wtCI031466 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 3 Jul 2006 07:58:56 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.13.6/8.13.6) with ESMTP id k634wtsV087397; Mon, 3 Jul 2006 07:58:55 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.13.6/8.13.6/Submit) id k634wsX1087396; Mon, 3 Jul 2006 07:58:54 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Mon, 3 Jul 2006 07:58:54 +0300 From: Kostik Belousov To: Francisco Reyes Message-ID: <20060703045854.GH37822@deviant.kiev.zoral.com.ua> References: <20060629230309.GA12773@lpthe.jussieu.fr> <20060630041733.GA4941@zibbi.meraka.csir.co.za> <20060702162942.D1103@ganymede.hub.org> <20060703042010.GG37822@deviant.kiev.zoral.com.ua> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="PyMzGVE0NRonI6bs" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i X-Virus-Scanned: ClamAV version 0.88.2, clamav-milter version 0.88.2 on fw.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=0.4 required=5.0 tests=ALL_TRUSTED, DNS_FROM_RFC_ABUSE,SPF_NEUTRAL autolearn=no version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on fw.zoral.com.ua Cc: freebsd-stable@freebsd.org, User Freebsd Subject: Re: NFS Locking Issue X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Jul 2006 04:59:03 -0000 --PyMzGVE0NRonI6bs Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jul 03, 2006 at 12:50:11AM -0400, Francisco Reyes wrote: > Kostik Belousov writes: > >Since nobody except you experience that problems (at least, only you=20 > >notified > >about the problem existence) >=20 > Did you miss the part of: >=20 > >User Freebsd writes: > >>Since there are several of us experiencing what looks to be the same so= rt > >>of deadlock issue, I beseech you not to give up >=20 > I am not the only one reporting or having the issue. I think you have different issues. >=20 > >Is this for intr mounts? >=20 > "intr" ? Mount option that allows to interrupt nfs operation by signal. See mount_nfs(8). BTW, I had the impression that this feature not working was one of your problem. >=20 >=20 > >improved handling of signals in nfs client. If you could test it, that > >would be useful. >=20 > Does it matter if the OS is i386 or am64? > Have an amd64 machine I can more easily play with... with no risk to=20 > production.=20 No, this shall be applicable to any arch. Except that the patches are sever= al month old, and were developed against CURRENT. But I think that it is applicable to STABLE. --PyMzGVE0NRonI6bs Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) iD8DBQFEqKQOC3+MBN1Mb4gRAgUsAKC7Beb/cDcHREvTCKjxWCOxoQH10gCghB2+ K8NvD2dD4XTpC4zS359qvIo= =ju7V -----END PGP SIGNATURE----- --PyMzGVE0NRonI6bs-- From owner-freebsd-stable@FreeBSD.ORG Mon Jul 3 05:00:45 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 83B4816A517 for ; Mon, 3 Jul 2006 05:00:45 +0000 (UTC) (envelope-from fbsd@1command.com) Received: from mail.1command.com (mail.1command.com [216.177.243.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6A79D43EEC for ; Mon, 3 Jul 2006 04:30:58 +0000 (GMT) (envelope-from fbsd@1command.com) Received: from mail.1command.com (localhost.1command.com [127.0.0.1]) by mail.1command.com (8.13.3/8.13.3) with ESMTP id k634Ut0o046496 for ; Sun, 2 Jul 2006 21:30:56 -0700 (PDT) (envelope-from fbsd@1command.com) Received: (from www@localhost) by mail.1command.com (8.13.3/8.13.3/Submit) id k634Ut73046495 for freebsd-stable@freebsd.org; Sun, 2 Jul 2006 21:30:55 -0700 (PDT) (envelope-from fbsd@1command.com) Received: from ns1.1command.com (ns1.1command.com [216.177.243.34]) by webmail.1command.com (H.R. Communications Messaging System) with HTTP; Sun, 02 Jul 2006 21:30:55 -0700 Message-ID: <20060702213055.lc4jhdhe8c8sk48o@webmail.1command.com> X-Priority: 3 (Normal) Date: Sun, 02 Jul 2006 21:30:55 -0700 From: "Chris H." To: freebsd-stable@freebsd.org References: <20060629230309.GA12773@lpthe.jussieu.fr> In-Reply-To: <20060629230309.GA12773@lpthe.jussieu.fr> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=_65y7s2he6k0s"; protocol="application/pgp-signature"; micalg="pgp-sha1" Content-Transfer-Encoding: 7bit User-Agent: H.R. Communications Internet Messaging System (HCIMS) 4.1 Professional (not for redistribution) / FreeBSD-5.5 Subject: Re: NFS Locking Issue X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Jul 2006 05:00:45 -0000 This message is in MIME format and has been PGP signed. --=_65y7s2he6k0s Content-Type: text/plain; charset=ISO-8859-1; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit Quoting Michel Talon : >> I guess I'm still just a bit stunned that a bug this obvious not only >> found it's way into the STABLE branch, but is still there. Maybe it's >> not as obvious as I think, or not many folks are using it? All I know >> for sure here is that if I had upgraded to 6.1 my network would have >> been crippled. > > Strange, since i upgraded to FreeBSD-6.1 and the NFS server to Fedora Core 5, > my machine, NFS client is happy, and lockd works. It is first time since > years i have no problem. It certainly did not work with FreeBSD-5 and i still > have a machine with FreeBSD-6.0 which does not work properly > (frequently loses > the NFS mount, but it gets remounted some times later by amd). Anyways i have > exactly 0 problem with the 6.1 machine. I could extend that to say that > everything works very well on that machine, nothing is slow, including disk > access. This has not always been the case. Stability wise, i have not > seen any > panic, hang or whatever since i have compiled a kernel adapted to my > hardware. > I got a panic with the generic kernel soon after installation, but now > machine is totally stable. So it would appear that you cured the NFS problems inherent with FBSD-6 by replacing FBSD with Fedora Linux. Nice to know that NFSd works in Linux. But won't help those on the FBSD list fix their FBSD-6 boxen. :/ > > > > -- > > Michel TALON > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > -- panic: kernel trap (ignored) ----------------------------------------------------------------- FreeBSD 5.4-RELEASE-p12 (SMP - 900x2) Tue Mar 7 19:37:23 PST 2006 ///////////////////////////////////////////////////////////////// --=_65y7s2he6k0s Content-Type: application/pgp-signature Content-Description: PGP Digital Signature Content-Disposition: inline Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQBEqJ1/XxK1cRs0zxkRArHTAKChOI8e6XF17ywpmVuK57M97NwQkQCdGduc OUzwSxtedzTbeRKwFTSCdYY= =9IFl -----END PGP SIGNATURE----- --=_65y7s2he6k0s-- From owner-freebsd-stable@FreeBSD.ORG Mon Jul 3 09:06:59 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B471D16A40F for ; Mon, 3 Jul 2006 09:06:59 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 42052443A5 for ; Mon, 3 Jul 2006 09:06:59 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 1545846BCD; Mon, 3 Jul 2006 05:06:52 -0400 (EDT) Date: Mon, 3 Jul 2006 10:06:52 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Kostik Belousov In-Reply-To: <20060703045854.GH37822@deviant.kiev.zoral.com.ua> Message-ID: <20060703100038.I26325@fledge.watson.org> References: <20060629230309.GA12773@lpthe.jussieu.fr> <20060630041733.GA4941@zibbi.meraka.csir.co.za> <20060702162942.D1103@ganymede.hub.org> <20060703042010.GG37822@deviant.kiev.zoral.com.ua> <20060703045854.GH37822@deviant.kiev.zoral.com.ua> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: User Freebsd , freebsd-stable@freebsd.org, Francisco Reyes Subject: Re: NFS Locking Issue X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Jul 2006 09:06:59 -0000 On Mon, 3 Jul 2006, Kostik Belousov wrote: > On Mon, Jul 03, 2006 at 12:50:11AM -0400, Francisco Reyes wrote: >> Kostik Belousov writes: >>> Since nobody except you experience that problems (at least, only you >>> notified >>> about the problem existence) >> >> Did you miss the part of: >> >>> User Freebsd writes: >>>> Since there are several of us experiencing what looks to be the same sort >>>> of deadlock issue, I beseech you not to give up >> >> I am not the only one reporting or having the issue. > I think you have different issues. I agree. It looks like we have several issues floating around. There are some known issues with rpc.lockd (and probably some unknown ones) that will require a concerted effort to resolve. There appear to be a number of reports relating to this/these problems. It sounds like there is also an NFS client race condition or other bug of some sort. I think it would be really useful to isolate the two during debugging. Specifically, to make sure that the second client bug is reproduceable without rpc.lockd running on the client (and related mount flags). Once we have some more information, such as vnode locking information, client thread stack traces, etc, we should probably get Mohan in the loop if things seem sticky. I believe he was on vacation last week; he may be back this week sometime. With the July 4 weekend afoot, a lot of .us developers are offline. Robert N M Watson Computer Laboratory University of Cambridge From owner-freebsd-stable@FreeBSD.ORG Mon Jul 3 09:10:47 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A8D0D16A92B for ; Mon, 3 Jul 2006 09:10:47 +0000 (UTC) (envelope-from freebsd-listen@fabiankeil.de) Received: from smtprelay01.ispgateway.de (smtprelay01.ispgateway.de [80.67.18.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7EBDE43D4C for ; Mon, 3 Jul 2006 09:10:41 +0000 (GMT) (envelope-from freebsd-listen@fabiankeil.de) Received: (qmail 30427 invoked from network); 3 Jul 2006 09:10:39 -0000 Received: from unknown (HELO localhost) (775067@[217.50.146.49]) (envelope-sender ) by smtprelay01.ispgateway.de (qmail-ldap-1.03) with SMTP for ; 3 Jul 2006 09:10:39 -0000 Date: Mon, 3 Jul 2006 11:10:31 +0200 From: Fabian Keil To: Dan Nelson Message-ID: <20060703111031.48b21924@localhost> In-Reply-To: <20060702193224.GD4915@dan.emsphone.com> References: <20060627175853.765a590e@localhost> <20060628101729.J50845@fledge.watson.org> <20060702173338.00a5ed44@localhost> <20060702170843.C67344@fledge.watson.org> <20060702190520.3b344c83@localhost> <20060702182302.H80381@fledge.watson.org> <20060702193224.GD4915@dan.emsphone.com> X-Mailer: Sylpheed-Claws 2.2.3 (GTK+ 2.8.19; i386-portbld-freebsd6.1) X-PGP-KEY-URL: http://www.fabiankeil.de/gpg-keys/freebsd-listen-2006-08-19.asc User-Agent: 321 test Mime-Version: 1.0 Content-Type: multipart/signed; boundary=Sig_EK.83B7w7ta0Jv7+KoX.13y; protocol="application/pgp-signature"; micalg=PGP-SHA1 Cc: Peter Thoenen , Robert Watson , freebsd-stable@freebsd.org Subject: Re: FreeBSD 6.1 Tor issues (Once More, with Feeling) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Jul 2006 09:10:47 -0000 --Sig_EK.83B7w7ta0Jv7+KoX.13y Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Dan Nelson wrote: > In the last episode (Jul 02), Robert Watson said: > > On Sun, 2 Jul 2006, Fabian Keil wrote: > > >The ssh man page offers: > > > > > >|~B Send a BREAK to the remote system (only useful for SSH > > >| protocol version 2 and if the peer supports it). > > > > > >I am using ssh 2, but the only reaction I get is a new line. > > > > > >|FreeBSD/i386 (tor.fabiankeil.de) (ttyd0) > > >| > > >|login: ~B >=20 > If you enter ~B and actually see a ~B printed to the screen, then ssh > didn't process it because you didn't hit first. So ~B will > tell ssh to send a break. I am actually using ~B and I don't see just "~B", but "~B ". The tilde is printed after I release B, therefore I guess it is working. =20 > > It sounds like your serial console server may not know how to map > > SSH break signals into remote serial break signals. Try > > ALT_BREAK_TO_DEBUGGER. Here's the description from NOTES: > >=20 > > # Solaris implements a new BREAK which is initiated by a character > > # sequence CR ~ ^b which is similar to a familiar pattern used on > > # Sun servers by the Remote Console. > > options ALT_BREAK_TO_DEBUGGER >=20 > ... and if you're sshing to your terminal server, remember that ssh > will eat that tilde (because you sent ~ ), so you need to send > ~~^B to pass the right characters to FreeBSD. Or change ssh's > escape character with the -e flag. ~^b works for me, without touching any ssh settings. As ~. is still causing a disconnect, it doesn't look like the escape character was changed either. Fabian --=20 http://www.fabiankeil.de/ --Sig_EK.83B7w7ta0Jv7+KoX.13y Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEqN8NjV8GA4rMKUQRAmeDAKCef8RxDFj/FW1xoPboO5FJao9NoQCfQ5eM N5eg9Fnx2goMUGfXTbx2JMo= =FlmO -----END PGP SIGNATURE----- --Sig_EK.83B7w7ta0Jv7+KoX.13y-- From owner-freebsd-stable@FreeBSD.ORG Mon Jul 3 09:27:30 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F0C5F16A40F for ; Mon, 3 Jul 2006 09:27:30 +0000 (UTC) (envelope-from freebsd-listen@fabiankeil.de) Received: from smtprelay03.ispgateway.de (smtprelay03.ispgateway.de [80.67.18.15]) by mx1.FreeBSD.org (Postfix) with ESMTP id 00D3D43E33 for ; Mon, 3 Jul 2006 09:27:19 +0000 (GMT) (envelope-from freebsd-listen@fabiankeil.de) Received: (qmail 1140 invoked from network); 3 Jul 2006 09:27:18 -0000 Received: from unknown (HELO localhost) (775067@[217.50.146.49]) (envelope-sender ) by smtprelay03.ispgateway.de (qmail-ldap-1.03) with SMTP for ; 3 Jul 2006 09:27:18 -0000 Date: Mon, 3 Jul 2006 11:27:05 +0200 From: Fabian Keil To: Robert Watson Message-ID: <20060703112705.0da6a071@localhost> In-Reply-To: <20060702212335.0bf121be@localhost> References: <20060627175853.765a590e@localhost> <20060628101729.J50845@fledge.watson.org> <20060702173338.00a5ed44@localhost> <20060702170843.C67344@fledge.watson.org> <20060702190520.3b344c83@localhost> <20060702182302.H80381@fledge.watson.org> <20060702212335.0bf121be@localhost> X-Mailer: Sylpheed-Claws 2.2.3 (GTK+ 2.8.19; i386-portbld-freebsd6.1) X-PGP-KEY-URL: http://www.fabiankeil.de/gpg-keys/freebsd-listen-2006-08-19.asc User-Agent: 321 test Mime-Version: 1.0 Content-Type: multipart/signed; boundary=Sig_hi48nKb.YbrU0C4nSqr+2vI; protocol="application/pgp-signature"; micalg=PGP-SHA1 Cc: Peter Thoenen , freebsd-stable@freebsd.org Subject: Re: FreeBSD 6.1 Tor issues (Once More, with Feeling) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Jul 2006 09:27:31 -0000 --Sig_hi48nKb.YbrU0C4nSqr+2vI Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Fabian Keil wrote: > Robert Watson wrote: > > It sounds like your serial console server may not know how to map > > SSH break signals into remote serial break signals. Try > > ALT_BREAK_TO_DEBUGGER. Here's the description from NOTES: > >=20 > > # Solaris implements a new BREAK which is initiated by a character > > # sequence CR ~ ^b which is similar to a familiar pattern used on > > # Sun servers by the Remote Console. > > options ALT_BREAK_TO_DEBUGGER >=20 > It took me several attempts to get the character sequence right, > but yes, this one works. Thanks. Unfortunately it didn't work while the system was hanging this morning. I wasn't logged in at the console before the hang occurred, so it maybe that the terminal server checked the console for life signs, found none and did neither connect nor print a warning (wild guess I have no idea if it does that). It could also mean that I'm seeing the mysterious "power off" part described in: but I have no way to tell the difference. I will stay connected to the console until the system hangs again to see if it changes anything. Fabian --=20 http://www.fabiankeil.de/ --Sig_hi48nKb.YbrU0C4nSqr+2vI Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEqOLzjV8GA4rMKUQRAlTBAKCaX03m6suEx3OFJBeYVfXRr6kJ2gCaAnxf zTdNM+Cdw480a4P4RpB02Ag= =AXl+ -----END PGP SIGNATURE----- --Sig_hi48nKb.YbrU0C4nSqr+2vI-- From owner-freebsd-stable@FreeBSD.ORG Mon Jul 3 09:48:45 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 085B716A617; Mon, 3 Jul 2006 09:48:45 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from fw.zoral.com.ua (ll-227.216.82.212.sovam.net.ua [212.82.216.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1B04343E61; Mon, 3 Jul 2006 09:47:32 +0000 (GMT) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by fw.zoral.com.ua (8.13.4/8.13.4) with ESMTP id k639lPpT039283 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 3 Jul 2006 12:47:25 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.13.6/8.13.6) with ESMTP id k639lPxW091426; Mon, 3 Jul 2006 12:47:25 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.13.6/8.13.6/Submit) id k639lNmq091425; Mon, 3 Jul 2006 12:47:23 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Mon, 3 Jul 2006 12:47:23 +0300 From: Kostik Belousov To: Robert Watson Message-ID: <20060703094723.GI37822@deviant.kiev.zoral.com.ua> References: <20060629230309.GA12773@lpthe.jussieu.fr> <20060630041733.GA4941@zibbi.meraka.csir.co.za> <20060702162942.D1103@ganymede.hub.org> <20060703042010.GG37822@deviant.kiev.zoral.com.ua> <20060703045854.GH37822@deviant.kiev.zoral.com.ua> <20060703100038.I26325@fledge.watson.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="xQmOcGOVkeO43v2v" Content-Disposition: inline In-Reply-To: <20060703100038.I26325@fledge.watson.org> User-Agent: Mutt/1.4.2.1i X-Virus-Scanned: ClamAV version 0.88.2, clamav-milter version 0.88.2 on fw.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=0.4 required=5.0 tests=ALL_TRUSTED, DNS_FROM_RFC_ABUSE,SPF_NEUTRAL autolearn=no version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on fw.zoral.com.ua Cc: User Freebsd , freebsd-stable@freebsd.org, Francisco Reyes Subject: Re: NFS Locking Issue X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Jul 2006 09:48:45 -0000 --xQmOcGOVkeO43v2v Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jul 03, 2006 at 10:06:52AM +0100, Robert Watson wrote: >=20 > On Mon, 3 Jul 2006, Kostik Belousov wrote: >=20 > >On Mon, Jul 03, 2006 at 12:50:11AM -0400, Francisco Reyes wrote: > >>Kostik Belousov writes: > >>>Since nobody except you experience that problems (at least, only you > >>>notified > >>>about the problem existence) > >> > >>Did you miss the part of: > >> > >>>User Freebsd writes: > >>>>Since there are several of us experiencing what looks to be the same= =20 > >>>>sort > >>>>of deadlock issue, I beseech you not to give up > >> > >>I am not the only one reporting or having the issue. > >I think you have different issues. >=20 > I agree. It looks like we have several issues floating around. There ar= e=20 > some known issues with rpc.lockd (and probably some unknown ones) that wi= ll=20 > require a concerted effort to resolve. There appear to be a number of=20 > reports relating to this/these problems. >=20 > It sounds like there is also an NFS client race condition or other bug of= =20 > some sort. >=20 > I think it would be really useful to isolate the two during debugging.=20 > Specifically, to make sure that the second client bug is reproduceable=20 > without rpc.lockd running on the client (and related mount flags). Once = we=20 > have some more information, such as vnode locking information, client=20 > thread stack traces, etc, we should probably get Mohan in the loop if=20 > things seem sticky. I believe he was on vacation last week; he may be bac= k=20 > this week sometime. With the July 4 weekend afoot, a lot of .us developer= s=20 > are offline. I too did noted some time ago that unresposible nfs server takes nfs client down. I then looked at the issue, and have the impression that this is again the case of runningbufspace depletion. I got a lot of processes in wdrain and flswai states. After nfs server repaired, active write requests were executed, number of dirty buffers decreased, and system returned to normal operation. This seems to be an architectural issue. I tried to bring discussion up several month ago, but got no response. And, there is the small problem about SIGINT being ignored when mounted with intr flag. Patch to fix this is attached in my previous mail. --xQmOcGOVkeO43v2v Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) iD8DBQFEqOerC3+MBN1Mb4gRAlDPAKDod9GxQbGxgRhagOtC7YNgbPcHoQCcDsMc OoIDZvs6NJ1YGN+lBFvHBDs= =8YUX -----END PGP SIGNATURE----- --xQmOcGOVkeO43v2v-- From owner-freebsd-stable@FreeBSD.ORG Mon Jul 3 10:50:09 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1B84816A40F for ; Mon, 3 Jul 2006 10:50:09 +0000 (UTC) (envelope-from andrew@areilly.bpa.nu) Received: from omta04sl.mx.bigpond.com (omta04sl.mx.bigpond.com [144.140.93.156]) by mx1.FreeBSD.org (Postfix) with ESMTP id F406A43D45 for ; Mon, 3 Jul 2006 10:50:07 +0000 (GMT) (envelope-from andrew@areilly.bpa.nu) Received: from areilly.bpa.nu ([141.168.7.22]) by omta04sl.mx.bigpond.com with ESMTP id <20060703105005.FNHS7229.omta04sl.mx.bigpond.com@areilly.bpa.nu> for ; Mon, 3 Jul 2006 10:50:05 +0000 Received: (qmail 89780 invoked by uid 501); 3 Jul 2006 10:50:09 -0000 Date: Mon, 3 Jul 2006 20:50:09 +1000 From: Andrew Reilly To: Robert Watson Message-ID: <20060703105009.GA89088@duncan.reilly.home> References: <20060629230309.GA12773@lpthe.jussieu.fr> <20060630041733.GA4941@zibbi.meraka.csir.co.za> <20060702162942.D1103@ganymede.hub.org> <20060703042010.GG37822@deviant.kiev.zoral.com.ua> <20060703045854.GH37822@deviant.kiev.zoral.com.ua> <20060703100038.I26325@fledge.watson.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060703100038.I26325@fledge.watson.org> User-Agent: Mutt/1.4.2.1i Cc: Kostik Belousov , Francisco Reyes , freebsd-stable@freebsd.org, User Freebsd Subject: Re: NFS Locking Issue X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Jul 2006 10:50:09 -0000 On Mon, Jul 03, 2006 at 10:06:52AM +0100, Robert Watson wrote: > It sounds like there is also an NFS client race condition or other bug of > some sort. It may not be related, directly, but one thing that I noticed, while trying to sort out my own recently commissioned NFS setup, is that the -r1024 mount flag is *crucial* when the network is 100BaseT and the server is a new, fast amd64 box, and the client is an old P3-500 with a RealTek ethernet card. It works fine, now, but tcpdump showed that it was retrying forever without. Even NFS over TCP seemed to suffer a bunch of error-related retries which amounted to stalls in the client. Is there any way for this sort of thing to be adjusted automatically? Cheers, -- Andrew From owner-freebsd-stable@FreeBSD.ORG Mon Jul 3 12:22:20 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7E76416A412 for ; Mon, 3 Jul 2006 12:22:20 +0000 (UTC) (envelope-from michel@lpthe.jussieu.fr) Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by mx1.FreeBSD.org (Postfix) with ESMTP id EB0A943D66 for ; Mon, 3 Jul 2006 12:22:13 +0000 (GMT) (envelope-from michel@lpthe.jussieu.fr) Received: from parthe.lpthe.jussieu.fr (parthe.lpthe.jussieu.fr [134.157.10.1]) by shiva.jussieu.fr (8.13.6/jtpda-5.4) with ESMTP id k63CMCJJ010427 for ; Mon, 3 Jul 2006 14:22:12 +0200 (CEST) X-Ids: 166 Received: from niobe.lpthe.jussieu.fr (niobe.lpthe.jussieu.fr [134.157.10.41]) by parthe.lpthe.jussieu.fr (Postfix) with ESMTP id 8F4E59FB19 for ; Mon, 3 Jul 2006 14:22:11 +0200 (CEST) Received: by niobe.lpthe.jussieu.fr (Postfix, from userid 2005) id DB83235; Mon, 3 Jul 2006 14:22:10 +0200 (CEST) Date: Mon, 3 Jul 2006 14:22:10 +0200 From: Michel Talon To: freebsd-stable@freebsd.org Message-ID: <20060703122210.GA46625@lpthe.jussieu.fr> Mail-Followup-To: Michel Talon , freebsd-stable@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0.2 (shiva.jussieu.fr [134.157.0.166]); Mon, 03 Jul 2006 14:22:12 +0200 (CEST) X-Virus-Scanned: ClamAV 0.88.2/1579/Sat Jul 1 12:20:41 2006 on shiva.jussieu.fr X-Virus-Status: Clean X-Miltered: at shiva.jussieu.fr with ID 44A90BF4.001 by Joe's j-chkmail (http://j-chkmail.ensmp.fr)! Subject: Re: NFS Locking Issue X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Jul 2006 12:22:20 -0000 > So it would appear that you cured the NFS problems inherent with FBSD-6 > by replacing FBSD with Fedora Linux. Nice to know that NFSd works in Linux. > But won't help those on the FBSD list fix their FBSD-6 boxen. :/ > First NFS is designed to make machines of different OSs interact properly. If a FreeBSD server interacts properly with a FreeBSD client, but not other clients, you cannot say that the situation is fine. Second i am not the one to chose the NFS server, there are people working in social groups, in the real world. And third, the most important, the OP message seemed to imply that the FreeBSD-6 NFS client was at fault, i pointed out that in my experience my FreeBSD-6.1 client works OK, while the 6.0 doesn't, when interacting with a FC5 server. This is in itself a relevant piece of information for the problem at hand. It may be that the server side is at fault, or some complex interaction between client and server. Anyways some people claimed here that they had no problem with FreeBSD-5 clients and servers. My experience is that i had constant problems between FreeBSD-5 clients and Fedora Core 3 servers. I cannot provide any other data point. I am not particularly sure of the quality of the FC3 or FC5 NFS server implementation, except that the ~ 100 workstations running the similar Fedora distribution work like a charm with their homes NFS mounted on the server. On the other hand a Debian client machine also has severe NFS problems. My only conclusion is that these NFS stories are very tricky. The only moment everything worked fine was when we were running Solaris on the server. -- Michel TALON From owner-freebsd-stable@FreeBSD.ORG Mon Jul 3 12:34:37 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AE1C716A47E for ; Mon, 3 Jul 2006 12:34:37 +0000 (UTC) (envelope-from freebsd@hub.org) Received: from hub.org (hub.org [200.46.204.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1040343D48 for ; Mon, 3 Jul 2006 12:34:37 +0000 (GMT) (envelope-from freebsd@hub.org) Received: from localhost (wm.hub.org [200.46.204.128]) by hub.org (Postfix) with ESMTP id 54235290C2B; Mon, 3 Jul 2006 09:34:31 -0300 (ADT) Received: from hub.org ([200.46.204.220]) by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024) with ESMTP id 95263-08; Mon, 3 Jul 2006 12:34:36 +0000 (UTC) Received: from ganymede.hub.org (blk-7-151-244.eastlink.ca [71.7.151.244]) by hub.org (Postfix) with ESMTP id CFF2C290C1F; Mon, 3 Jul 2006 09:34:30 -0300 (ADT) Received: by ganymede.hub.org (Postfix, from userid 1027) id 333FF3769F; Mon, 3 Jul 2006 09:34:40 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id 15CDC33DF1; Mon, 3 Jul 2006 09:34:40 -0300 (ADT) Date: Mon, 3 Jul 2006 09:34:39 -0300 (ADT) From: User Freebsd To: Francisco Reyes In-Reply-To: Message-ID: <20060703093332.D1103@ganymede.hub.org> References: <20060629230309.GA12773@lpthe.jussieu.fr> <20060630041733.GA4941@zibbi.meraka.csir.co.za> <20060702162942.D1103@ganymede.hub.org> <20060703042010.GG37822@deviant.kiev.zoral.com.ua> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Kostik Belousov , freebsd-stable@freebsd.org Subject: Re: NFS Locking Issue X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Jul 2006 12:34:37 -0000 On Mon, 3 Jul 2006, Francisco Reyes wrote: > Kostik Belousov writes: > >> I think that then 6.2 and 6.3 is not for you either. Problems >> cannot be fixed until enough information is given. > > I am trying.. but so far only other users who are having the same problem are > commenting on this and other simmilar threads. > > We just need some guidance.. > > Mark gave me a URL to turn on debugging and volunteered ot give me some > pointers.. I will try, but I will likely try on my own time, on my own > machines.. I can not tell the owner of the company I work for to let me > "try".. or "play around" in production machines.. as we loose customers > because of current problems with the 6.X line. >> Since nobody except you experience that problems (at least, only you >> notified >> about the problem existence) > > Did you miss the part of: > >> User Freebsd writes: >>> Since there are several of us experiencing what looks to be the same sort >>> of deadlock issue, I beseech you not to give up > > I am not the only one reporting or having the issue. Careful here, I think this is where things are getting confused ... the above is related to the deadlock (high vmstat blockd issue), not the NFS issue ... we're getting two different issues confused :) >> improved handling of signals in nfs client. If you could test it, that >> would be useful. > > Does it matter if the OS is i386 or am64? > Have an amd64 machine I can more easily play with... with no risk to > production. Does the amd64 machine exhibit the same problem? ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . scrappy@hub.org MSN . scrappy@hub.org Yahoo . yscrappy Skype: hub.org ICQ . 7615664 From owner-freebsd-stable@FreeBSD.ORG Mon Jul 3 13:20:42 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 305A216A4D1 for ; Mon, 3 Jul 2006 13:20:42 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from pi.codefab.com (pi.codefab.com [199.103.21.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8A92C43EBF for ; Mon, 3 Jul 2006 12:50:36 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from localhost (localhost [127.0.0.1]) by pi.codefab.com (Postfix) with ESMTP id E9C7E5D79; Mon, 3 Jul 2006 08:50:35 -0400 (EDT) X-Virus-Scanned: amavisd-new at codefab.com Received: from pi.codefab.com ([127.0.0.1]) by localhost (pi.codefab.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p0wl+81zdE-5; Mon, 3 Jul 2006 08:50:34 -0400 (EDT) Received: from [192.168.1.251] (pool-68-160-201-170.ny325.east.verizon.net [68.160.201.170]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by pi.codefab.com (Postfix) with ESMTP id 94C1D5C31; Mon, 3 Jul 2006 08:50:34 -0400 (EDT) Message-ID: <44A91294.3080701@mac.com> Date: Mon, 03 Jul 2006 08:50:28 -0400 From: Chuck Swiger User-Agent: Thunderbird 1.5.0.4 (Windows/20060516) MIME-Version: 1.0 To: Michel Talon , freebsd-stable@freebsd.org References: <20060703122210.GA46625@lpthe.jussieu.fr> In-Reply-To: <20060703122210.GA46625@lpthe.jussieu.fr> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: NFS Locking Issue X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Jul 2006 13:20:42 -0000 Michel Talon wrote: [ ...a long email snipped... ] > My only conclusion is that these NFS stories are very > tricky. The only moment everything worked fine was when we were running > Solaris on the server. I can't speak to the earlier part about NFS with Linux, but at least I very much agree with your conclusion: Solaris makes one of the best NFS servers available, over a broad range of use cases. However, I also wish to note that if you want to use NFS and you need remote locking to work, your best hope is when the software you use is willing to use explicit lockfiles rather than depending on rpc.lockd to provide remote flock()/lockf()-style locking. There are plenty of software out there which includes locking tests (sendmail does, UWash IMAP does, Perl does, etc), and my observation has been that actually using NFS-based remote locking under anything beyond trivial load tends to make rpc.lockd terminate within seconds (maybe with a core dump, if you get lucky), or end up with processes getting stuck forever waiting on locks that don't ever return because they've been lost somewhere in limbo. YMMV. :-) -- -Chuck From owner-freebsd-stable@FreeBSD.ORG Mon Jul 3 14:05:44 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 05CCD16A407 for ; Mon, 3 Jul 2006 14:05:44 +0000 (UTC) (envelope-from vivek@khera.org) Received: from yertle.kcilink.com (yertle.kcilink.com [65.205.34.180]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9A9A943D49 for ; Mon, 3 Jul 2006 14:05:43 +0000 (GMT) (envelope-from vivek@khera.org) Received: from [192.168.1.3] (unknown [192.168.1.3]) by yertle.kcilink.com (Postfix) with ESMTP id 5A0C4B827 for ; Mon, 3 Jul 2006 10:05:42 -0400 (EDT) Mime-Version: 1.0 (Apple Message framework v752.2) In-Reply-To: <281C4418-D0A0-4AAF-8C06-F6A4D5AC5571@syz.com> References: <281C4418-D0A0-4AAF-8C06-F6A4D5AC5571@syz.com> Content-Type: multipart/signed; micalg=sha1; boundary=Apple-Mail-18--317834673; protocol="application/pkcs7-signature" Message-Id: <325AF3FC-8B6B-4215-AF16-9026CD1ECF5D@khera.org> From: Vivek Khera Date: Mon, 3 Jul 2006 10:05:40 -0400 To: freebsd-stable X-Mailer: Apple Mail (2.752.2) X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: Which FreeBSD is the most stable for Dell PowerEdge 2850 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Jul 2006 14:05:44 -0000 --Apple-Mail-18--317834673 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed On Jun 30, 2006, at 8:08 PM, Dan Charrois wrote: > In any case, the server is used heavily all year except July, so > this is my time of year to take things apart, update software, > etc. And so I'm wondering - what is the recommended version of > FreeBSD I should be running if stability is of the utmost > importance? Should I migrate to the 6.x stream? Is it relatively > solid? Or should I stay with 5.4 for now? I've seen some messages > posted periodically from various people running into problems, I don't have any 2850's but the 1850 I have has been running 6.0 since the BETA1, and last night just upgraded it to 6.1. No issues. The PERC 4e/Si card is phenominally fast on this system (running 2 disk RAID1). I'd recommend you to run 6.1 as it is stable on all of my Dell systems that run it (and I'm migrating the older FreeBSD boxes to 6.1 as time permits). If you already have > 1 CPU, you might as well leave hyperthreading off. There are cases where it degenerates performance rather than enhance it. As for mysql version, "no comment" :-) --Apple-Mail-18--317834673-- From owner-freebsd-stable@FreeBSD.ORG Mon Jul 3 20:00:35 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6078216A403 for ; Mon, 3 Jul 2006 20:00:35 +0000 (UTC) (envelope-from drosih@rpi.edu) Received: from smtp6.server.rpi.edu (smtp6.server.rpi.edu [128.113.2.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4C4664415C for ; Mon, 3 Jul 2006 19:29:28 +0000 (GMT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by smtp6.server.rpi.edu (8.13.1/8.13.1) with ESMTP id k63JTIru012362; Mon, 3 Jul 2006 15:29:21 -0400 Mime-Version: 1.0 Message-Id: In-Reply-To: References: <20060629230309.GA12773@lpthe.jussieu.fr> <20060630041733.GA4941@zibbi.meraka.csir.co.za> Date: Mon, 3 Jul 2006 15:29:18 -0400 To: Francisco Reyes , John Hay From: Garance A Drosihn Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-CanItPRO-Stream: default X-RPI-SA-Score: undef - spam-scanning disabled X-Scanned-By: CanIt (www . canit . ca) Cc: freebsd-stable@freebsd.org, Michel Talon Subject: Re: NFS Locking Issue X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Jul 2006 20:00:35 -0000 At 9:13 PM -0400 7/1/06, Francisco Reyes wrote: >John Hay writes: > >>I only started to see the lockd problems when upgrading >>the server side to FreeBSD 6.x and later. I had various >>FreeBSD clients, between 4.x and 7-current and the lockd >>problem only showed up when upgrading the server from >>5.x to 6.x. > >It confirms the same we are experiencing.. constant >freezing/locking issues. I guess no more 6.X for us.. for >the foreseable future.. I don't know if this will be of any help to anyone, but... I recently moved a network-based service from a 4.x machine to a 6.x machine. Despite some testing in advance of the switch, many people had problems with the service. I booted to a somewhat out-of-date snapshot of 5.x on the same box. I still had problems, but it didn't seem as bad, so I stuck with the 5.x system. Some problems turned out to be bugs in the service itself, and were eventually found and fixed. However, one set of problems on that out-of-date snapshot of 5.x were solved by adding: net.inet.tcp.rfc1323=0 to /etc/sysctl.conf. The guy who suggested that said it avoided a bug which was fixed in later versions of either 5.x or 6.x, I forget which. Of interest is that the bug was such that some people connecting to the service were never bothered by the bug, while other people could not use the service at all until I turned off tcp.rfc1323 . I have a test version of the same service running on a different FreeBSD/i386 box, and that box is now updated to freebsd-stable as of June 10th. Lo and behold, someone connecting to that test box reported some problems. So I typed in 'sysctl net.inet.tcp.rfc1323=0', and his problem immediately disappeared. So, it might be that there is still some problem with the rfc1323 processing, or that the bug which had been fixed has somehow been re-introduced. In any case, people who are experiencing problems with NFS might want to try that, and see if it makes any difference. It does strike me as odd that some people are having a *lot* of trouble with NFS under 6.x, while others seem to be okay with it. Perhaps the difference is the network topology between the NFS server and the NFS clients. Obviously, this is nothing but a guess on my part. I am not a networking guru! -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu From owner-freebsd-stable@FreeBSD.ORG Mon Jul 3 21:33:01 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5F33216A403 for ; Mon, 3 Jul 2006 21:33:01 +0000 (UTC) (envelope-from Michael.Collette@TestEquity.com) Received: from smtp.testequity.com (gateway.testequity.com [205.147.14.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0A23743D4C for ; Mon, 3 Jul 2006 21:33:00 +0000 (GMT) (envelope-from Michael.Collette@TestEquity.com) Received: from smtp.priv.testequity.com (unknown [192.168.3.27]) by smtp.testequity.com (Postfix) with ESMTP id B826F13C41A; Mon, 3 Jul 2006 14:33:00 -0700 (PDT) Received: from [192.168.3.172] (mach172.priv.testequity.com [192.168.3.172]) by smtp.priv.testequity.com (Postfix) with ESMTP id C86FCC775; Mon, 3 Jul 2006 14:33:00 -0700 (PDT) Message-ID: <44A98D41.2020200@TestEquity.com> Date: Mon, 03 Jul 2006 14:33:53 -0700 From: Michael Collette Organization: TestEquity LLC User-Agent: Thunderbird 1.5.0.4 (X11/20060607) MIME-Version: 1.0 To: Garance A Drosihn References: <20060629230309.GA12773@lpthe.jussieu.fr> <20060630041733.GA4941@zibbi.meraka.csir.co.za> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: NFS Locking Issue X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Jul 2006 21:33:01 -0000 Garance A Drosihn wrote: > At 9:13 PM -0400 7/1/06, Francisco Reyes wrote: >> John Hay writes: >> >>> I only started to see the lockd problems when upgrading >>> the server side to FreeBSD 6.x and later. I had various >>> FreeBSD clients, between 4.x and 7-current and the lockd >>> problem only showed up when upgrading the server from >>> 5.x to 6.x. >> >> It confirms the same we are experiencing.. constant >> freezing/locking issues. I guess no more 6.X for us.. for >> the foreseable future.. > > I don't know if this will be of any help to anyone, > but... > > I recently moved a network-based service from a 4.x machine > to a 6.x machine. Despite some testing in advance of the > switch, many people had problems with the service. I booted > to a somewhat out-of-date snapshot of 5.x on the same box. > I still had problems, but it didn't seem as bad, so I stuck > with the 5.x system. Some problems turned out to be bugs > in the service itself, and were eventually found and fixed. > > However, one set of problems on that out-of-date snapshot > of 5.x were solved by adding: > > net.inet.tcp.rfc1323=0 > > to /etc/sysctl.conf. The guy who suggested that said it > avoided a bug which was fixed in later versions of either > 5.x or 6.x, I forget which. Of interest is that the bug > was such that some people connecting to the service were > never bothered by the bug, while other people could not use > the service at all until I turned off tcp.rfc1323 . > > I have a test version of the same service running on a > different FreeBSD/i386 box, and that box is now updated > to freebsd-stable as of June 10th. Lo and behold, someone > connecting to that test box reported some problems. So I > typed in 'sysctl net.inet.tcp.rfc1323=0', and his problem > immediately disappeared. So, it might be that there is > still some problem with the rfc1323 processing, or that the > bug which had been fixed has somehow been re-introduced. > > In any case, people who are experiencing problems with NFS > might want to try that, and see if it makes any difference. > It does strike me as odd that some people are having a *lot* > of trouble with NFS under 6.x, while others seem to be okay > with it. Perhaps the difference is the network topology > between the NFS server and the NFS clients. > > Obviously, this is nothing but a guess on my part. I am > not a networking guru! > Thanks for the try Garance, but in my setup it didn't make any difference. I'll get into a bit more detail about my setup in another post. Later on, -- Michael Collette IT Manager TestEquity Inc Michael.Collette@TestEquity.com From owner-freebsd-stable@FreeBSD.ORG Mon Jul 3 22:19:57 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9FFC816A4DD for ; Mon, 3 Jul 2006 22:19:57 +0000 (UTC) (envelope-from sthalik@tehran.lain.pl) Received: from mail.in5.pl (rollercoaster.insane.pl [213.251.173.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8C06E43DDD for ; Mon, 3 Jul 2006 22:19:36 +0000 (GMT) (envelope-from sthalik@tehran.lain.pl) Received: from tehran.lain.pl ([85.221.230.102] helo=tehran.local ident=mailnull) from mailnull by mail.in5.pl with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (envelope-from ) id 1FxWlT-0000Wh-TO for freebsd-stable@freebsd.org; Tue, 04 Jul 2006 00:19:36 +0200 Received: from sthalik by tehran.local with local (Exim 4.62 (FreeBSD)) (envelope-from ) id 1FxWlS-000FVS-8S for freebsd-stable@freebsd.org; Tue, 04 Jul 2006 00:19:34 +0200 Date: Tue, 4 Jul 2006 00:19:34 +0200 From: Stanislaw Halik To: freebsd-stable@freebsd.org Message-ID: <20060703221934.GA59568@tehran.lain.pl> Mail-Followup-To: freebsd-stable@freebsd.org References: <20060627045310.GA6324@tehran.lain.pl> <20060627140946.J273@fledge.watson.org> <20060627134134.GA23337@tehran.lain.pl> <20060628101405.I50845@fledge.watson.org> <20060630120812.GA2380@tehran.lain.pl> <20060630145851.S23703@fledge.watson.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="opJtzjQTFsWo+cga" Content-Disposition: inline In-Reply-To: <20060630145851.S23703@fledge.watson.org> X-PGP-Key: http://tehran.lain.pl/public.key User-Agent: Mutt/1.5.11 Subject: Re: trap 12: supervisor write, page not present on 6.1-STABLE Tue May 16 2006 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Jul 2006 22:19:57 -0000 --opJtzjQTFsWo+cga Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jun 30, 2006, Robert Watson wrote: > Thanks for testing the patch -- it looks like there's a more pressing=20 > logical problem in this code! Could you try the following simpler patch: > http://www.watson.org/~robert/freebsd/netperf/ip_ctloutput.diff > The IP option code seems not to know that (in RELENG_6 and before) the pc= b=20 > is discarded on disconnect, and the application is querying the TTL after= a=20 > disconnect. In FreeBSD 7.x, the pcb is preserved after disconnect so thi= s=20 > succeeds. I'm running with the patch applied for 3 days straight and the machine didn't crash once. Please, consider merging it to RELENG_6. --opJtzjQTFsWo+cga Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) iD8DBQFEqZf1adU+vjT62TERAie0AJ9/+cUuI+67DrLRozLq8J3ObszbAACeK5MG /yMhWgoQVFRorVbKEnfsDIM= =AjRh -----END PGP SIGNATURE----- --opJtzjQTFsWo+cga-- From owner-freebsd-stable@FreeBSD.ORG Mon Jul 3 22:39:09 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DE81B16A4E5 for ; Mon, 3 Jul 2006 22:39:09 +0000 (UTC) (envelope-from Michael.Collette@TestEquity.com) Received: from smtp.testequity.com (gateway.testequity.com [205.147.14.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7B32243D45 for ; Mon, 3 Jul 2006 22:39:09 +0000 (GMT) (envelope-from Michael.Collette@TestEquity.com) Received: from smtp.priv.testequity.com (unknown [192.168.3.27]) by smtp.testequity.com (Postfix) with ESMTP id 34FBE13C447; Mon, 3 Jul 2006 15:39:09 -0700 (PDT) Received: from [192.168.3.172] (mach172.priv.testequity.com [192.168.3.172]) by smtp.priv.testequity.com (Postfix) with ESMTP id 3079CC29F; Mon, 3 Jul 2006 15:39:09 -0700 (PDT) Message-ID: <44A99CC1.7070501@TestEquity.com> Date: Mon, 03 Jul 2006 15:40:01 -0700 From: Michael Collette Organization: TestEquity LLC User-Agent: Thunderbird 1.5.0.4 (X11/20060607) MIME-Version: 1.0 To: User Freebsd References: <20060629230309.GA12773@lpthe.jussieu.fr> <20060630041733.GA4941@zibbi.meraka.csir.co.za> <20060702162942.D1103@ganymede.hub.org> In-Reply-To: <20060702162942.D1103@ganymede.hub.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: NFS Locking Issue X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Jul 2006 22:39:10 -0000 User Freebsd wrote: > On Sat, 1 Jul 2006, Francisco Reyes wrote: > >> John Hay writes: >> >>> I only started to see the lockd problems when upgrading the server side >>> to FreeBSD 6.x and later. I had various FreeBSD clients, between 4.x >>> and 7-current and the lockd problem only showed up when upgrading the >>> server from 5.x to 6.x. >> >> It confirms the same we are experiencing.. constant freezing/locking >> issues. >> I guess no more 6.X for us.. for the foreseable future.. > > Since there are several of us experiencing what looks to be the same > sort of deadlock issue, I beseech you not to give up Honestly trying not to. To tell ya the truth, I've been giving a real hard look at Ubuntu for my serving needs. This NFS thing has got me seriously questioning FreeBSD right at the moment. >... right now, all > we've been able to get to the developers is virtually useless > information (vmstat and such shows the problem, but it doesn't allow > developers to identify the problem) ... > > Is this a problem that you can easily recreate, even on a non-production > machine? Oh yeah. I've got a couple of ways I'm able to get this to fail. Method #1: --------------------------------------------------------------------- Let's start with the simplest. The scenario here involves 2 machines, mach01 and mach02. Both are running 6-STABLE, and both are running rpcbind, rpc.statd, and rpc.lockd. mach01 has exported /documents and mach02 is mounting that export under /mnt. Simple enough? The /documents directory has multiple subdirectories and files of various sizes. The actual amount of data doesn't really matter to produce a failure. All you need to do at this point is to try to copy files from that mount point to somewhere else on the hard drive. cp -Rp /mnt/* /tmp/documents/ You may, or not, see that a couple of subdirectories were created, but no files actually moved over. The cp command is now locked up, and no traffic moves. This usually takes a second or two to show up as a problem. I can repeat this with multiple 6-STABLE boxes. Turn off rpc.lockd on either the server or client before the cp command, and things work. Method #2: --------------------------------------------------------------------- Booting to a diskless work station. The server (mach01) has exported /usr, /usr/local, /usr/X11R6 and enough other stuff to get a diskless workstation up and running. Not going to get into all the details here other than to say that I have a fully functioning setup like this on 5.4 boxes now. I've knocked the boot up of the diskless client (mach02) down to console only. Once at the console I startx with a regular user, taking me in to twm. From there I try to launch a KDE application, which in my test case is kwrite. The same situation is true with launching a GTK app, such as Gimp. X and twm start up. I've got all the rest of the system reasonably functional. When I try to run kwrite, none of the KDE subsystems start up. kwrite just sits there in a lockd state. Same is true of Gimp. If I shutdown rpc.lockd on either machine I'm able to bring up a full KDE desktop, with all applications able to run. Other Testing: --------------------------------------------------------------------- At one point we had in our test network a 6.1 NFS server providing files to 5.4 diskless clients without any problems. We first got to noticing the bulk of the glitches when I moved the diskless setup to use a 6.1 kernel. As I said, I've been looking at Linux alternatives. Especially after reading about Michel Talon's experiences with Fedora. I initially tried CentOS, but wasn't able to get NFS working properly on that thing. I had an Ubuntu CD handy, so I installed it on a test box. Wow, does that NFS server boogie! Using Ubuntu as the server I connected a FreeBSD 5.4 and 6-stable box as clients on a 100Mb/s network. The time trial used a dummy 100Meg file transfered from the server to the client. We measured 90Mb/s transfer, which was FAR faster than I had ever been able to get 2 FreeBSD boxes to perform doing similar tests. I then used Ubuntu to connect to a 5.4 server we have in production. I don't recall the exact stats, but it was close to 10x slower. No lockups here though. After the 4th of July I intend to test Ubuntu as a client to a FreeBSD 6-STABLE server on a gigabit lan to run similar time trials. I'm looking to confirm what I can only suspect at this point, which is that the NFS server on FreeBSD is mucked up, but the client is okay. As time allows I hope to run similar tests between two Ubuntu boxes, then run it all again with Fedora. Seriously debating whether to move some or all of our infrastructure to Linux after all this. A 3-4 month old known bug like this gives me a great deal of concern about FreeBSD. That, and Ubuntu's NFS server speed just about knocked me over! > In my case, I have one machine fully configured for debugging, > but, of course, since re-configuring it, it hasn't exhibited the problem > ... if most of us get our machines configured properly to give useful > information to the developers to debug this, the faster it will get > fixed ... > > My experience with most of the developers is that if you can get into > DDB and give them 'internal traces' of the code, bugs tend to get fixed > very quickly ... vmstat/ps give "external views", more summaries then > anything ... its the details "under the hood" that they need ... its not > much different then your auto-mechanic ... try telling him there is a > 'knocking under the hood, please tell me how to fix it, but you can't > have my car', and he'll brush you off ... give him 30 minutes under the > hood, and not only will he have identified it, but he'll probably fix it > too ... Marc, the car is starting but won't move at all. I don't know if this is the transmission, the steering wheel, or the radio. I am feeling pretty certain that this car should never have left the lot in this condition though. Again, these are problems that have been around for a while... http://www.freebsd.org/cgi/query-pr.cgi?pr=84953 http://www.freebsd.org/cgi/query-pr.cgi?pr=80389 Later on, -- Michael Collette IT Manager TestEquity Inc Michael.Collette@TestEquity.com From owner-freebsd-stable@FreeBSD.ORG Mon Jul 3 23:15:36 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5630A16A4DE for ; Mon, 3 Jul 2006 23:15:36 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 15D3F43D53 for ; Mon, 3 Jul 2006 23:15:34 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 8C6EE46BEE; Mon, 3 Jul 2006 19:15:33 -0400 (EDT) Date: Tue, 4 Jul 2006 00:15:33 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Stanislaw Halik In-Reply-To: <20060703221934.GA59568@tehran.lain.pl> Message-ID: <20060704001437.W54173@fledge.watson.org> References: <20060627045310.GA6324@tehran.lain.pl> <20060627140946.J273@fledge.watson.org> <20060627134134.GA23337@tehran.lain.pl> <20060628101405.I50845@fledge.watson.org> <20060630120812.GA2380@tehran.lain.pl> <20060630145851.S23703@fledge.watson.org> <20060703221934.GA59568@tehran.lain.pl> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org Subject: Re: trap 12: supervisor write, page not present on 6.1-STABLE Tue May 16 2006 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Jul 2006 23:15:36 -0000 On Tue, 4 Jul 2006, Stanislaw Halik wrote: > On Fri, Jun 30, 2006, Robert Watson wrote: >> Thanks for testing the patch -- it looks like there's a more pressing >> logical problem in this code! Could you try the following simpler patch: > >> http://www.watson.org/~robert/freebsd/netperf/ip_ctloutput.diff > >> The IP option code seems not to know that (in RELENG_6 and before) the pcb >> is discarded on disconnect, and the application is querying the TTL after a >> disconnect. In FreeBSD 7.x, the pcb is preserved after disconnect so this >> succeeds. > > I'm running with the patch applied for 3 days straight and the machine > didn't crash once. Please, consider merging it to RELENG_6. I have committed this as ip_output.c:1.242.2.9 in the RELENG_6 branch, and will also merge to RELENG_5 in a few days. Assuming this settles well, I'll talk to the RE team about doing an errata patch for this in the RELENG_6_1 branch. Thanks! Robert N M Watson Computer Laboratory University of Cambridge From owner-freebsd-stable@FreeBSD.ORG Mon Jul 3 23:48:27 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D096A16A55A for ; Mon, 3 Jul 2006 23:48:27 +0000 (UTC) (envelope-from apache@km20932-01.keymachine.de) Received: from km20932-01.keymachine.de (ns.km20932-01.keymachine.de [84.19.184.119]) by mx1.FreeBSD.org (Postfix) with ESMTP id E78F843D46 for ; Mon, 3 Jul 2006 23:48:26 +0000 (GMT) (envelope-from apache@km20932-01.keymachine.de) Received: from km20932-01.keymachine.de (localhost [127.0.0.1]) by km20932-01.keymachine.de (8.12.11/8.12.11) with ESMTP id k640nDgT005363 for ; Tue, 4 Jul 2006 02:49:13 +0200 Received: (from apache@localhost) by km20932-01.keymachine.de (8.12.11/8.12.11/Submit) id k640nDpj005362; Tue, 4 Jul 2006 02:49:13 +0200 Date: Tue, 4 Jul 2006 02:49:13 +0200 Message-Id: <200607040049.k640nDpj005362@km20932-01.keymachine.de> From: Chase Bank To: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Chase Online. Banking Account registration information X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Jul 2006 23:48:28 -0000 [chaseNew.gif] Chase Bank Online. Department Notice You have received this email because you or someone had used your account from different locations. For security purpose, we are required to open an investigation into this matter. In order to safeguard your account, we require that you confirm your banking details. To help speed up this process, please access the following link so we can complete the verification of your Chase Online. Banking Account registration information : To get started, please click the link below: [1]https://www.chase.com Please Note: If we do no receive the appropriate account verification within 48 hours, then we will assume this Chase Bank account is fraudulent and will be suspended. The purpose of this verification is to ensure that your bank account has not been fraudulently used and to combat the fraud from our community. Regards, Chase Bank - Chase Online. Banking Department _________________________________________________________________ Securities (including mutual funds and variable life insurance), annuities and insurance products are not bank deposits and are not insured by the FDIC or any other agency of the United States, nor are they obligations of, nor insured or guaranteed by, JPMorgan Chase Bank, N.A., CISC, CIA, CMIA or their affiliates. Securities (including mutual funds and variable life insurance) and annuities involve investment risks, including the possible loss of value. References 1. http://cms.ucall.com/ From owner-freebsd-stable@FreeBSD.ORG Tue Jul 4 09:24:20 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9348D16A4E7 for ; Tue, 4 Jul 2006 09:24:20 +0000 (UTC) (envelope-from michel@lpthe.jussieu.fr) Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by mx1.FreeBSD.org (Postfix) with ESMTP id 99D8943D45 for ; Tue, 4 Jul 2006 09:24:19 +0000 (GMT) (envelope-from michel@lpthe.jussieu.fr) Received: from parthe.lpthe.jussieu.fr (parthe.lpthe.jussieu.fr [134.157.10.1]) by shiva.jussieu.fr (8.13.6/jtpda-5.4) with ESMTP id k649LSJY084950 for ; Tue, 4 Jul 2006 11:21:54 +0200 (CEST) X-Ids: 166 Received: from niobe.lpthe.jussieu.fr (niobe.lpthe.jussieu.fr [134.157.10.41]) by parthe.lpthe.jussieu.fr (Postfix) with ESMTP id 11FAE9FB92 for ; Tue, 4 Jul 2006 11:21:28 +0200 (CEST) Received: by niobe.lpthe.jussieu.fr (Postfix, from userid 2005) id 5420335; Tue, 4 Jul 2006 11:21:27 +0200 (CEST) Date: Tue, 4 Jul 2006 11:21:27 +0200 From: Michel Talon To: freebsd-stable@freebsd.org Message-ID: <20060704092127.GA55167@lpthe.jussieu.fr> Mail-Followup-To: Michel Talon , freebsd-stable@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0.2 (shiva.jussieu.fr [134.157.0.166]); Tue, 04 Jul 2006 11:21:54 +0200 (CEST) X-Virus-Scanned: ClamAV 0.88.2/1582/Mon Jul 3 23:23:18 2006 on shiva.jussieu.fr X-Virus-Status: Clean X-j-bayes: Bayes filter score (experimental) : 0.273 XXXXX X-Miltered: at shiva.jussieu.fr with ID 44AA3318.001 by Joe's j-chkmail (http://j-chkmail.ensmp.fr)! Subject: Re: NFS Locking Issue X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Jul 2006 09:24:20 -0000 > Using Ubuntu as the server I connected a FreeBSD 5.4 and 6-stable box as > clients on a 100Mb/s network. The time trial used a dummy 100Meg file > transfered from the server to the client. > I have similar experiences here. With FreeBSD-6.1 as client (using an Intel etherexpress card at 100 Mb/s) and FC5 server i see full wire speed for file transfers via NFS. > After the 4th of July I intend to test Ubuntu as a client to a FreeBSD > 6-STABLE server on a gigabit lan to run similar time trials. I'm > looking to confirm what I can only suspect at this point, which is that > the NFS server on FreeBSD is mucked up, but the client is okay. I have the same impression. The 6.1-RELEASE client seems to work well. Yesterday i have upgraded my 6.0 (*) box to 6.1 and i have not seen a single NFS problem after that. Moreover i am using rpc.statd, and rpc.lockd and they work OK and are really functional. I have the following sysctl which may have an effect on the problem: vfs.nfs.access_cache_timeout=5 So it may well be that it is the FreeBSD NFS server code which has problems. (*) 6.0-RELEASE client definitively does not work OK for me. -- Michel TALON From owner-freebsd-stable@FreeBSD.ORG Tue Jul 4 10:23:32 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 502BA16A4E7 for ; Tue, 4 Jul 2006 10:23:32 +0000 (UTC) (envelope-from dmitry@atlantis.dp.ua) Received: from postman.atlantis.dp.ua (postman.atlantis.dp.ua [193.108.47.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id CD6E943D55 for ; Tue, 4 Jul 2006 10:23:30 +0000 (GMT) (envelope-from dmitry@atlantis.dp.ua) Received: from smtp.atlantis.dp.ua (smtp.atlantis.dp.ua [193.108.46.231]) by postman.atlantis.dp.ua (8.13.1/8.13.1) with ESMTP id k64ANMNV054248 for ; Tue, 4 Jul 2006 13:23:22 +0300 (EEST) (envelope-from dmitry@atlantis.dp.ua) Date: Tue, 4 Jul 2006 13:23:22 +0300 (EEST) From: Dmitry Pryanishnikov To: freebsd-stable@freebsd.org Message-ID: <20060704130402.X31561@atlantis.atlantis.dp.ua> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: Misleading "fdisk: Geom not found" in 6.1-RELEASE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Jul 2006 10:23:32 -0000 Hello! I've noticed that using fdisk against ad2 drive gives misleading diagnostics at the end of execution (there are no mounted partitions at the drive, OS boot device is ad0): root@test# uname -r 6.1-RELEASE root@test# mount|grep ad2 root@test# fdisk -a ad2 ******* Working on device /dev/ad2 ******* ... Partition 2 is marked active Do you want to change the active partition? [n] y Supply a decimal value for "active partition" [2] 1 Are you happy with this choice [n] y ... Should we write new partition table? [n] y fdisk: Geom not found root@test# One can think that it's an error message, however new partition table actually gets written to the disk, next fdisk run (and 'hd /dev/ad2', to be sure) confirms so. What's the reason of this message? fdisk(8) doesn't reply to this question. The strangest thing is that this message doesn't show during modification of partition table on system disk (ad0). Modification succeeds in both cases. Sincerely, Dmitry -- Atlantis ISP, System Administrator e-mail: dmitry@atlantis.dp.ua nic-hdl: LYNX-RIPE From owner-freebsd-stable@FreeBSD.ORG Tue Jul 4 10:30:51 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2521416A4DA for ; Tue, 4 Jul 2006 10:30:51 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id CA01B43D49 for ; Tue, 4 Jul 2006 10:30:50 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 513A246C68; Tue, 4 Jul 2006 06:30:50 -0400 (EDT) Date: Tue, 4 Jul 2006 11:30:50 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Michael Collette In-Reply-To: <44A99CC1.7070501@TestEquity.com> Message-ID: <20060704112906.G54173@fledge.watson.org> References: <20060629230309.GA12773@lpthe.jussieu.fr> <20060630041733.GA4941@zibbi.meraka.csir.co.za> <20060702162942.D1103@ganymede.hub.org> <44A99CC1.7070501@TestEquity.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org, User Freebsd Subject: Re: NFS Locking Issue X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Jul 2006 10:30:51 -0000 On Mon, 3 Jul 2006, Michael Collette wrote: > http://www.freebsd.org/cgi/query-pr.cgi?pr=80389 If you locally back out the referenced change lock_proc.c:1.18 in rpc.lockd on the server, do things improve? Robert N M Watson Computer Laboratory University of Cambridge From owner-freebsd-stable@FreeBSD.ORG Tue Jul 4 13:40:35 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C014E16A4EC for ; Tue, 4 Jul 2006 13:40:35 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from fw.zoral.com.ua (ll-227.216.82.212.sovam.net.ua [212.82.216.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id B397043D49 for ; Tue, 4 Jul 2006 13:40:34 +0000 (GMT) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by fw.zoral.com.ua (8.13.4/8.13.4) with ESMTP id k64DeSim082508 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 4 Jul 2006 16:40:28 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.13.6/8.13.6) with ESMTP id k64DeSlf009659; Tue, 4 Jul 2006 16:40:28 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.13.6/8.13.6/Submit) id k64DeRxk009658; Tue, 4 Jul 2006 16:40:27 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Tue, 4 Jul 2006 16:40:27 +0300 From: Kostik Belousov To: Michael Collette Message-ID: <20060704134027.GK37822@deviant.kiev.zoral.com.ua> References: <20060629230309.GA12773@lpthe.jussieu.fr> <20060630041733.GA4941@zibbi.meraka.csir.co.za> <20060702162942.D1103@ganymede.hub.org> <44A99CC1.7070501@TestEquity.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="2fjX3cMESU3XgGmZ" Content-Disposition: inline In-Reply-To: <44A99CC1.7070501@TestEquity.com> User-Agent: Mutt/1.4.2.1i X-Virus-Scanned: ClamAV version 0.88.2, clamav-milter version 0.88.2 on fw.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=0.4 required=5.0 tests=ALL_TRUSTED, DNS_FROM_RFC_ABUSE,SPF_NEUTRAL autolearn=no version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on fw.zoral.com.ua Cc: freebsd-stable@freebsd.org, User Freebsd Subject: Re: NFS Locking Issue X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Jul 2006 13:40:35 -0000 --2fjX3cMESU3XgGmZ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jul 03, 2006 at 03:40:01PM -0700, Michael Collette wrote: > User Freebsd wrote: > >On Sat, 1 Jul 2006, Francisco Reyes wrote: > > > >>John Hay writes: > >> > >>>I only started to see the lockd problems when upgrading the server side > >>>to FreeBSD 6.x and later. I had various FreeBSD clients, between 4.x > >>>and 7-current and the lockd problem only showed up when upgrading the > >>>server from 5.x to 6.x. > >> > >>It confirms the same we are experiencing.. constant freezing/locking=20 > >>issues. > >>I guess no more 6.X for us.. for the foreseable future.. > > > >Since there are several of us experiencing what looks to be the same=20 > >sort of deadlock issue, I beseech you not to give up >=20 > Honestly trying not to. To tell ya the truth, I've been giving a real=20 > hard look at Ubuntu for my serving needs. This NFS thing has got me=20 > seriously questioning FreeBSD right at the moment. >=20 > >... right now, all=20 > >we've been able to get to the developers is virtually useless=20 > >information (vmstat and such shows the problem, but it doesn't allow=20 > >developers to identify the problem) ... > > > >Is this a problem that you can easily recreate, even on a non-production= =20 > >machine? >=20 > Oh yeah. I've got a couple of ways I'm able to get this to fail. >=20 > Method #1: > --------------------------------------------------------------------- > Let's start with the simplest. The scenario here involves 2 machines,=20 > mach01 and mach02. Both are running 6-STABLE, and both are running=20 > rpcbind, rpc.statd, and rpc.lockd. mach01 has exported /documents and=20 > mach02 is mounting that export under /mnt. Simple enough? >=20 > The /documents directory has multiple subdirectories and files of=20 > various sizes. The actual amount of data doesn't really matter to=20 > produce a failure. All you need to do at this point is to try to copy=20 > files from that mount point to somewhere else on the hard drive. >=20 > cp -Rp /mnt/* /tmp/documents/ >=20 > You may, or not, see that a couple of subdirectories were created, but=20 > no files actually moved over. The cp command is now locked up, and no=20 > traffic moves. This usually takes a second or two to show up as a=20 > problem. I can repeat this with multiple 6-STABLE boxes. >=20 > Turn off rpc.lockd on either the server or client before the cp command,= =20 > and things work. Either way you specified is too vague to reproduce the problem. As was said, you shall supply tcpdump of the failed nfs session. Personally, I tried to do what you described as method 1, and got no hangs, everything copied as it should be. I did it between amd64 6.1-STABLE as of yesterday (client) and same STABLE i386 as server. Monitoring lockd interaction by ethereal also did not reveal anythi= ng. So, what you need to provide to help debug the issue: 1. as detailed information on problem machines configuration as possible 2. exact version of the software you using 3. tcpdump of nfs sessions (for me, it is preferable to get raw tcpdump that could be load into ethereal) 4. log of rpc.lockd both on client and server (see the -d option in man page). Issue seems to be highly specific for some configuration details. And, for instance, me is unable to reproduce it on debug testbench. Without help of the user experiencing trouble, it could take forever to kill that bug. --2fjX3cMESU3XgGmZ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) iD8DBQFEqm/KC3+MBN1Mb4gRApT5AJ0dZjLDl1ljo2wV82EPCioVZcSiyACgx6Ye cLKq2cY3h6obxoG24SBfhE8= =1oCt -----END PGP SIGNATURE----- --2fjX3cMESU3XgGmZ-- From owner-freebsd-stable@FreeBSD.ORG Tue Jul 4 15:04:20 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5EDC516A4DA for ; Tue, 4 Jul 2006 15:04:20 +0000 (UTC) (envelope-from owensr@comcast.net) Received: from sccrmhc14.comcast.net (sccrmhc14.comcast.net [63.240.77.84]) by mx1.FreeBSD.org (Postfix) with ESMTP id E3E1343D46 for ; Tue, 4 Jul 2006 15:04:19 +0000 (GMT) (envelope-from owensr@comcast.net) Received: from lappy2 (c-69-243-17-124.hsd1.va.comcast.net[69.243.17.124]) by comcast.net (sccrmhc14) with SMTP id <20060704150419014004k05re>; Tue, 4 Jul 2006 15:04:19 +0000 Message-ID: <001701c69f7b$1e6b2550$0301a8c0@LAPPY2> From: "Raymond Owens" To: Date: Tue, 4 Jul 2006 11:04:16 -0400 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1807 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1807 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: if_bridge.c question X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Jul 2006 15:04:20 -0000 I am running 6.1 release on some systems. I have a question about the = bridging changes in if_bridge.c which were made in the stable branch. I = am having a problem bonding two heavily loaded network interfaces for = IDS purposes. There is greatly increased packets droppage when using = 'ifconfig bridge0 monitor' to merge the two sniff interfaces under 6.1 = release. (I am trying to get around using two concurrent Snort = processeses) Is it expected that the new bridge monitor function introduced in the = stable branch will have much less packet droppage in identical = situations when bonding busy interfaces? If so is there a way to get = this without upgrading whole system to 6.1 stable? Will binary upgrade = using 6.1 stable ISO provide this functionality also? Also I had tried netgraph (and one2many) to bond the interfaces and it = worked fine but at traffic peaks during day it would eventually stop = seeing any packets at all on the virtual interface. Thanks From owner-freebsd-stable@FreeBSD.ORG Tue Jul 4 19:06:12 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8225616A4DE for ; Tue, 4 Jul 2006 19:06:12 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id CB2C743D72 for ; Tue, 4 Jul 2006 19:06:03 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.14] (imini.samsco.home [192.168.254.14]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id k64J5tYD007453; Tue, 4 Jul 2006 13:06:01 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <44AABBD9.4000603@samsco.org> Date: Tue, 04 Jul 2006 13:04:57 -0600 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.7) Gecko/20050416 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Michel Talon References: <20060704092127.GA55167@lpthe.jussieu.fr> In-Reply-To: <20060704092127.GA55167@lpthe.jussieu.fr> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on pooker.samsco.org Cc: freebsd-stable@freebsd.org Subject: Re: NFS Locking Issue X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Jul 2006 19:06:12 -0000 Michel Talon wrote: >>Using Ubuntu as the server I connected a FreeBSD 5.4 and 6-stable box as >>clients on a 100Mb/s network. The time trial used a dummy 100Meg file >>transfered from the server to the client. >> > > > I have similar experiences here. With FreeBSD-6.1 as client (using an Intel > etherexpress card at 100 Mb/s) and FC5 server i see full wire speed for file > transfers via NFS. > > >>After the 4th of July I intend to test Ubuntu as a client to a FreeBSD >>6-STABLE server on a gigabit lan to run similar time trials. I'm >>looking to confirm what I can only suspect at this point, which is that >>the NFS server on FreeBSD is mucked up, but the client is okay. > > > I have the same impression. The 6.1-RELEASE client seems to work well. > Yesterday i have upgraded my 6.0 (*) box to 6.1 and i have not seen a single > NFS problem after that. Moreover i am using rpc.statd, and rpc.lockd > and they work OK and are really functional. > I have the following sysctl which may have an effect on the problem: > vfs.nfs.access_cache_timeout=5 > > So it may well be that it is the FreeBSD NFS server code which has problems. > > (*) 6.0-RELEASE client definitively does not work OK for me. > > For what it's worth, I recently spent a lot of time putting FreeBSD 6.1 to the test as both an NFS client and server in a mixed OS environment. By far and away, the biggest problems that I encountered with it were due to linux NFS bugs. CentOS, FC, and SuSE all created huge problems under load, and it was impossible to get stable results until I started using 2.6.12 and higher kernels. I have a variety of theories that I wish I had had time to test. I've seen hints of problems with READDIRPLUS, with FreeBSD's habit of mapping GETATTR to ACCESS, and with handle sizes. But in any case, it's been no secret that Linux has had very severe NFS problems in the past, and that the NetApp folks have worked very hard over the last year to fix them in the most recent Linux kernel releases. The only real fault I give FreeBSD is rpc.lockd. It's pretty much useless in all but trivial circumstances. Beyond that, make sure you're using a linux kernel that is relatively recent. Scott From owner-freebsd-stable@FreeBSD.ORG Tue Jul 4 20:47:23 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AACA816A4DF for ; Tue, 4 Jul 2006 20:47:23 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 246F843D45 for ; Tue, 4 Jul 2006 20:47:23 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id C53F146BA9; Tue, 4 Jul 2006 16:47:21 -0400 (EDT) Date: Tue, 4 Jul 2006 21:47:21 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Scott Long In-Reply-To: <44AABBD9.4000603@samsco.org> Message-ID: <20060704214326.L64340@fledge.watson.org> References: <20060704092127.GA55167@lpthe.jussieu.fr> <44AABBD9.4000603@samsco.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org, Michel Talon Subject: Re: NFS Locking Issue X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Jul 2006 20:47:23 -0000 On Tue, 4 Jul 2006, Scott Long wrote: > For what it's worth, I recently spent a lot of time putting FreeBSD 6.1 to > the test as both an NFS client and server in a mixed OS environment. By far > and away, the biggest problems that I encountered with it were due to linux > NFS bugs. CentOS, FC, and SuSE all created huge problems under load, and it > was impossible to get stable results until I started using 2.6.12 and higher > kernels. > > I have a variety of theories that I wish I had had time to test. I've seen > hints of problems with READDIRPLUS, with FreeBSD's habit of mapping GETATTR > to ACCESS, and with handle sizes. But in any case, it's been no secret that > Linux has had very severe NFS problems in the past, and that the NetApp > folks have worked very hard over the last year to fix them in the most > recent Linux kernel releases. The only real fault I give FreeBSD is > rpc.lockd. It's pretty much useless in all but trivial circumstances. > Beyond that, make sure you're using a linux kernel that is relatively > recent. BTW, I noticed yesterday that that IPv6 support committ to rpc.lockd was never backed out. An immediate question for people experiencing new rpc.lockd problems with 6.x should be whether or not backing out that change helps. I set up a simple local testbed for rpc.lockd this morning and have started running some basic tests. I wasn't able to trivially reproduce rpc.lockd problems reported for cp -r, although I did bump into another bump in the memory mapping of zero-length files following creation in the NFS client, which I've passed on to Mohan. I think what's needed is a wire-level regression suite, though, in order to avoid mixing up our rpc.lockd client code with the tests for rpc.lockd's server. This is something I may be able to start looking at this week, although it's the usual time trade-off: work on getting audit ready for MFC, network stack locking and protocol cleanup/bug fixing, or throw rpc.lockd into the mix as well? If we can demonstrate that backing out the IPv6 change clearly helps, we need to figure out why it's causing the problem. A casual read of the change doesn't suggest anything obvious, unfortunately, suggesting something non-obvious :-(. Robert N M Watson Computer Laboratory University of Cambridge From owner-freebsd-stable@FreeBSD.ORG Tue Jul 4 21:24:36 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7BEF316A4E7 for ; Tue, 4 Jul 2006 21:24:36 +0000 (UTC) (envelope-from michel@lpthe.jussieu.fr) Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8258743D46 for ; Tue, 4 Jul 2006 21:24:34 +0000 (GMT) (envelope-from michel@lpthe.jussieu.fr) Received: from parthe.lpthe.jussieu.fr (parthe.lpthe.jussieu.fr [134.157.10.1]) by shiva.jussieu.fr (8.13.7/jtpda-5.4) with ESMTP id k64LOXjx018918 for ; Tue, 4 Jul 2006 23:24:33 +0200 (CEST) X-Ids: 164 Received: from niobe.lpthe.jussieu.fr (niobe.lpthe.jussieu.fr [134.157.10.41]) by parthe.lpthe.jussieu.fr (Postfix) with ESMTP id 481F99FB92 for ; Tue, 4 Jul 2006 23:24:33 +0200 (CEST) Received: by niobe.lpthe.jussieu.fr (Postfix, from userid 2005) id 7793F35; Tue, 4 Jul 2006 23:24:32 +0200 (CEST) Date: Tue, 4 Jul 2006 23:24:32 +0200 From: Michel Talon To: freebsd-stable@freebsd.org Message-ID: <20060704212432.GA57426@lpthe.jussieu.fr> Mail-Followup-To: Michel Talon , freebsd-stable@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0.2 (shiva.jussieu.fr [134.157.0.164]); Tue, 04 Jul 2006 23:24:33 +0200 (CEST) X-Virus-Scanned: ClamAV 0.88.2/1585/Tue Jul 4 22:39:34 2006 on shiva.jussieu.fr X-Virus-Status: Clean X-j-bayes: Bayes filter score (experimental) : 0.222 XXXX X-Miltered: at shiva.jussieu.fr with ID 44AADC91.001 by Joe's j-chkmail (http://j-chkmail.ensmp.fr)! Subject: Re: NFS Locking Issue X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Jul 2006 21:24:36 -0000 > BTW, I noticed yesterday that that IPv6 support committ to rpc.lockd was never > backed out. An immediate question for people experiencing new rpc.lockd > problems with 6.x should be whether or not backing out that change helps. So it may be relevant to say that i have kernels without IPV6 support. Recall that i have absolutely no problem with the client in FreeBSD-6.1. Tomorrow i will test one of the 6.1 machines as a NFS server and the other as a client, and will make you know if i see something. As to the problems you mention about NFS Linux, yes i have seen a lot since years. But to my surprise FC5 seems to work well. By the way it is kernel 2.6.16 so sufficiently recent for the problems to have been ironed out, presumably. -- Michel TALON From owner-freebsd-stable@FreeBSD.ORG Tue Jul 4 22:21:57 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2745216A4E7 for ; Tue, 4 Jul 2006 22:21:57 +0000 (UTC) (envelope-from thompsa@freebsd.org) Received: from grunt7.ihug.co.nz (grunt7.ihug.co.nz [203.109.254.47]) by mx1.FreeBSD.org (Postfix) with ESMTP id BC37043D49 for ; Tue, 4 Jul 2006 22:21:56 +0000 (GMT) (envelope-from thompsa@freebsd.org) Received: from 203-109-251-39.static.bliink.ihug.co.nz (heff.fud.org.nz) [203.109.251.39] by grunt7.ihug.co.nz with esmtp (Exim 3.35 #1 (Debian)) id 1FxtHH-0006HU-00; Wed, 05 Jul 2006 10:21:55 +1200 Received: by heff.fud.org.nz (Postfix, from userid 1001) id A07C21CC1F; Wed, 5 Jul 2006 10:21:54 +1200 (NZST) Date: Wed, 5 Jul 2006 10:21:54 +1200 From: Andrew Thompson To: Raymond Owens Message-ID: <20060704222154.GA1954@heff.fud.org.nz> References: <001701c69f7b$1e6b2550$0301a8c0@LAPPY2> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <001701c69f7b$1e6b2550$0301a8c0@LAPPY2> User-Agent: Mutt/1.5.11 Cc: freebsd-stable@freebsd.org Subject: Re: if_bridge.c question X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Jul 2006 22:21:57 -0000 On Tue, Jul 04, 2006 at 11:04:16AM -0400, Raymond Owens wrote: > I am running 6.1 release on some systems. I have a question about the > bridging changes in if_bridge.c which were made in the stable branch. > I am having a problem bonding two heavily loaded network interfaces > for IDS purposes. There is greatly increased packets droppage when > using 'ifconfig bridge0 monitor' to merge the two sniff interfaces > under 6.1 release. (I am trying to get around using two concurrent > Snort processeses) > > Is it expected that the new bridge monitor function introduced in the > stable branch will have much less packet droppage in identical > situations when bonding busy interfaces? If so is there a way to get > this without upgrading whole system to 6.1 stable? Will binary upgrade > using 6.1 stable ISO provide this functionality also? You can just grab src/sys/net/if_bridge.c from the stable branch and build it on 6.1. You can either rebuild the kernel or if you are using modules then make && make install in src/sys/modules/if_bridge. Let me know if you get stuck. cheers, Andrew From owner-freebsd-stable@FreeBSD.ORG Wed Jul 5 00:50:34 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8351016A4E1 for ; Wed, 5 Jul 2006 00:50:34 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 942D343D58 for ; Wed, 5 Jul 2006 00:50:30 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.14] (imini.samsco.home [192.168.254.14]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id k650oOpg008838; Tue, 4 Jul 2006 18:50:29 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <44AB0C96.3090400@samsco.org> Date: Tue, 04 Jul 2006 18:49:26 -0600 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.7) Gecko/20050416 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Michel Talon References: <20060704212432.GA57426@lpthe.jussieu.fr> In-Reply-To: <20060704212432.GA57426@lpthe.jussieu.fr> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on pooker.samsco.org Cc: freebsd-stable@freebsd.org Subject: Re: NFS Locking Issue X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Jul 2006 00:50:34 -0000 Michel Talon wrote: >>BTW, I noticed yesterday that that IPv6 support committ to rpc.lockd was never >>backed out. An immediate question for people experiencing new rpc.lockd >>problems with 6.x should be whether or not backing out that change helps. > > > So it may be relevant to say that i have kernels without IPV6 support. > Recall that i have absolutely no problem with the client in FreeBSD-6.1. > Tomorrow i will test one of the 6.1 machines as a NFS server and the other as > a client, and will make you know if i see something. > > As to the problems you mention about NFS Linux, yes i have seen a lot since > years. But to my surprise FC5 seems to work well. By the way it is kernel > 2.6.16 so sufficiently recent for the problems to have been ironed out, > presumably. > > > 2.6.16 should be OK. I've heard of problems with cookie and handle sizes with it, but only under highly unusual circumstances. Scott From owner-freebsd-stable@FreeBSD.ORG Wed Jul 5 05:00:02 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 95F9116A4DE for ; Wed, 5 Jul 2006 05:00:02 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from cs1.cs.huji.ac.il (cs1.cs.huji.ac.il [132.65.16.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 11F5A43D45 for ; Wed, 5 Jul 2006 05:00:02 +0000 (GMT) (envelope-from danny@cs.huji.ac.il) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by cs1.cs.huji.ac.il with esmtp id 1FxzUU-000MMw-5m; Wed, 05 Jul 2006 07:59:58 +0300 X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.2 To: Scott Long In-reply-to: Your message of Tue, 04 Jul 2006 13:04:57 -0600 . Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 05 Jul 2006 07:59:58 +0300 From: Danny Braniss Message-ID: Cc: freebsd-stable@freebsd.org, Michel Talon Subject: Re: NFS Locking Issue X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Jul 2006 05:00:02 -0000 > Michel Talon wrote: > > >>Using Ubuntu as the server I connected a FreeBSD 5.4 and 6-stable box as > >>clients on a 100Mb/s network. The time trial used a dummy 100Meg file > >>transfered from the server to the client. > >> > > > > > > I have similar experiences here. With FreeBSD-6.1 as client (using an Intel > > etherexpress card at 100 Mb/s) and FC5 server i see full wire speed for file > > transfers via NFS. > > > > > >>After the 4th of July I intend to test Ubuntu as a client to a FreeBSD > >>6-STABLE server on a gigabit lan to run similar time trials. I'm > >>looking to confirm what I can only suspect at this point, which is that > >>the NFS server on FreeBSD is mucked up, but the client is okay. > > > > > > I have the same impression. The 6.1-RELEASE client seems to work well. > > Yesterday i have upgraded my 6.0 (*) box to 6.1 and i have not seen a single > > NFS problem after that. Moreover i am using rpc.statd, and rpc.lockd > > and they work OK and are really functional. > > I have the following sysctl which may have an effect on the problem: > > vfs.nfs.access_cache_timeout=5 > > > > So it may well be that it is the FreeBSD NFS server code which has problems. > > > > (*) 6.0-RELEASE client definitively does not work OK for me. > > > > > > For what it's worth, I recently spent a lot of time putting FreeBSD 6.1 > to the test as both an NFS client and server in a mixed OS environment. > By far and away, the biggest problems that I encountered with it were > due to linux NFS bugs. CentOS, FC, and SuSE all created huge problems > under load, and it was impossible to get stable results until I started > using 2.6.12 and higher kernels. > > I have a variety of theories that I wish I had had time to test. I've > seen hints of problems with READDIRPLUS, with FreeBSD's habit of mapping > GETATTR to ACCESS, and with handle sizes. But in any case, it's been no > secret that Linux has had very severe NFS problems in the past, and that > the NetApp folks have worked very hard over the last year to fix them in > the most recent Linux kernel releases. The only real fault I give > FreeBSD is rpc.lockd. It's pretty much useless in all but trivial > circumstances. Beyond that, make sure you're using a linux kernel that > is relatively recent. > In my case our main servers are NetApp, and the problems are more related to am-utils running into some race condition (need more time to debug this :-) the other problem is related to throughput, freebsd is slower than linux, and while freebsd/nfs/tcp is faster on Freebsd than udp, on linux it's the same. So it seems some tunning is needed. our main problem now is samba/rpc.lockd, we are stuck with a server running FreeBSD 5.4 which crashes, and we can't upgrade to 6.1 because lockd doesn't work. So, if someone is willing to look into the lockd issue, we would like to help. danny > Scott > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > From owner-freebsd-stable@FreeBSD.ORG Wed Jul 5 07:02:09 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B1DDE16A4DA for ; Wed, 5 Jul 2006 07:02:09 +0000 (UTC) (envelope-from m.ehinger@ltur.de) Received: from postx.gateway-inter.net (postx.gateway-inter.net [213.144.19.80]) by mx1.FreeBSD.org (Postfix) with ESMTP id 63DA643D55 for ; Wed, 5 Jul 2006 07:02:09 +0000 (GMT) (envelope-from m.ehinger@ltur.de) To: freebsd-stable@freebsd.org From: m.ehinger@ltur.de MIME-Version: 1.0 Message-ID: Date: Wed, 5 Jul 2006 09:03:29 +0200 Content-type: text/plain; charset=US-ASCII Subject: novell mount losing state X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Jul 2006 07:02:09 -0000 Hello, i'am using FreeBSD 6.1 Stable and tried to mount an Novell volume (mount_nwfs). Mounting the volume works without problems but after some time of inactivity on that mount i have to remount the volume to get access again. Syslog message: Jul 5 08:51:08 pcmcb3-104 kernel: ncprq: Restoring connection, flags = 101 Output of "ncplist c" working mount (yesterday evening) Active NCP connections: refid server:user(connid), owner:group(mode), refs, 7 SERVER:USER(483), root:wheel(755), 1, Output of "ncplist c" non working mount (today morning) Active NCP connections: refid server:user(connid), owner:group(mode), refs, 7 SERVER:USER(397), root:wheel(755), 1, <> If i use a cronjob to access the mount periodically there is no such problem! Any hints? If this is the wrong list please let me know If you need more info you're welcome Thanks in advance Maik From owner-freebsd-stable@FreeBSD.ORG Wed Jul 5 07:37:40 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A5F0016A4DA for ; Wed, 5 Jul 2006 07:37:40 +0000 (UTC) (envelope-from ob@gruft.de) Received: from obh.snafu.de (obh.snafu.de [213.73.92.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2E28B43D46 for ; Wed, 5 Jul 2006 07:37:39 +0000 (GMT) (envelope-from ob@gruft.de) Received: from ob by obh.snafu.de with local (Exim 4.62 (FreeBSD)) (envelope-from ) id 1Fy1x4-000HFC-1K for freebsd-stable@freebsd.org; Wed, 05 Jul 2006 09:37:38 +0200 Date: Wed, 5 Jul 2006 09:37:38 +0200 From: Oliver Brandmueller To: freebsd-stable@freebsd.org Message-ID: <20060705073737.GK90128@e-Gitt.NET> Mail-Followup-To: freebsd-stable@freebsd.org References: <20060704092127.GA55167@lpthe.jussieu.fr> <44AABBD9.4000603@samsco.org> <20060704214326.L64340@fledge.watson.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="uxuisgdDHaNETlh8" Content-Disposition: inline In-Reply-To: <20060704214326.L64340@fledge.watson.org> User-Agent: Mutt/1.5.11 Sender: Oliver Brandmueller Subject: Re: NFS Locking Issue X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Jul 2006 07:37:40 -0000 --uxuisgdDHaNETlh8 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Mornin' On Tue, Jul 04, 2006 at 09:47:21PM +0100, Robert Watson wrote: > BTW, I noticed yesterday that that IPv6 support committ to rpc.lockd was= =20 > never backed out. An immediate question for people experiencing new=20 > rpc.lockd problems with 6.x should be whether or not backing out that=20 > change helps. That could be a good pointer. I also started experiencing some problems=20 at home (I did not investigate further though, but started using local=20 locking and all was fine), while in our prod setup, where lots of=20 machines are running, and many of them use 6-STABLE of not too long ago,=20 I never experienced any problems with NFS. The main difference between=20 both these networks is, that at home I have an IPv6 environment, while=20 at work it's IPv4 only. I barely find time before the weekend to do tests, but if I don't read=20 any postings telling, that this made a difference, I will then start=20 testing at home. Thanx, Oliver --=20 | Oliver Brandmueller | Offenbacher Str. 1 | Germany D-14197 Berlin | | Fon +49-172-3130856 | Fax +49-172-3145027 | WWW: http://the.addict.de/ | | Ich bin das Internet. Sowahr ich Gott helfe. | | Eine gewerbliche Nutzung aller enthaltenen Adressen ist nicht gestattet! | --uxuisgdDHaNETlh8 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) iD8DBQFEq2xBiqtMdzjafykRApTRAJ0RkEUnbXgyQRuAFXUWolHNeCf9dgCgmA5N yMEORiK7q4DZNBSHXJym1pM= =mh4v -----END PGP SIGNATURE----- --uxuisgdDHaNETlh8-- From owner-freebsd-stable@FreeBSD.ORG Wed Jul 5 09:09:27 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 78D2516A4E1 for ; Wed, 5 Jul 2006 09:09:27 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id C15A943D49 for ; Wed, 5 Jul 2006 09:09:25 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 36AAB46CC7; Wed, 5 Jul 2006 05:09:25 -0400 (EDT) Date: Wed, 5 Jul 2006 10:09:24 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Danny Braniss In-Reply-To: Message-ID: <20060705100403.Y80381@fledge.watson.org> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org, Michel Talon Subject: Re: NFS Locking Issue X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Jul 2006 09:09:27 -0000 On Wed, 5 Jul 2006, Danny Braniss wrote: > In my case our main servers are NetApp, and the problems are more related to > am-utils running into some race condition (need more time to debug this :-) > the other problem is related to throughput, freebsd is slower than linux, > and while freebsd/nfs/tcp is faster on Freebsd than udp, on linux it's the > same. So it seems some tunning is needed. > > our main problem now is samba/rpc.lockd, we are stuck with a server running > FreeBSD 5.4 which crashes, and we can't upgrade to 6.1 because lockd doesn't > work. > > So, if someone is willing to look into the lockd issue, we would like to > help. The most significant problem working with rpc.lockd is creating easy to reproduce test cases. Not least because they can potentially involve multiple clients. If you can help to produce simple test cases to reproduce the bugs you're seeing, that would be invaluable. I'm aware of two general classes of problems with rpc.lockd. First, architectural issues, some derived from architectural problems in the NLM protocol: for example, assumptions that there can be a clean mapping of process lock owners to locks, which fall down as locks are properties of file descriptors that can be inheritted. Second, implementation bugs/misfeatures, such as the kernel not knowing how to cancel lock requests, so being unable to implement interruptible waits on locks in the distributed case. Reducing complex failure modes to easily reproduced test cases is tricky also, though. It requires careful analysis, often with ktrace and tcpdump/ethereal to work out what's going on, and not a little luck to perform the reduction of a large trace down to a simple test scenario. The first step is to try and figure out what, if any, specific workload results in a problem. For example, can you trigger it using work on just one client against a server, without client<->client interactions? This makes tracking and reproduction a lot easier, as multi-client test cases are really tricky! Once you've established whether it can be reproduced with a single client, you have to track down the behavior that triggers it -- normally, this is done by attempting to narrow down the specific program or sequence of events that causes the bug to trigger, removing things one at a time to see what causes the problem to disappear. This is made more difficult as lock managers are sensitive to timing, so removing a high load item from the list, even if it isn't the source of the problem, might cause it to trigger less frequently. Robert N M Watson Computer Laboratory University of Cambridge From owner-freebsd-stable@FreeBSD.ORG Wed Jul 5 09:50:43 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A84E916A4DF for ; Wed, 5 Jul 2006 09:50:43 +0000 (UTC) (envelope-from fbsd@1command.com) Received: from mail.1command.com (mail.1command.com [216.177.243.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0D82943D45 for ; Wed, 5 Jul 2006 09:50:42 +0000 (GMT) (envelope-from fbsd@1command.com) Received: from mail.1command.com (localhost.1command.com [127.0.0.1]) by mail.1command.com (8.13.3/8.13.3) with ESMTP id k659oeA0071921 for ; Wed, 5 Jul 2006 02:50:40 -0700 (PDT) (envelope-from fbsd@1command.com) Received: (from www@localhost) by mail.1command.com (8.13.3/8.13.3/Submit) id k659oe5c071920 for freebsd-stable@freebsd.org; Wed, 5 Jul 2006 02:50:40 -0700 (PDT) (envelope-from fbsd@1command.com) Received: from ns1.1command.com (ns1.1command.com [216.177.243.34]) by webmail.1command.com (H.R. Communications Messaging System) with HTTP; Wed, 05 Jul 2006 02:50:39 -0700 Message-ID: <20060705025039.q1ftty7o0csw84ko@webmail.1command.com> X-Priority: 3 (Normal) Date: Wed, 05 Jul 2006 02:50:39 -0700 From: "Chris H." To: freebsd-stable@freebsd.org References: <20060703122210.GA46625@lpthe.jussieu.fr> In-Reply-To: <20060703122210.GA46625@lpthe.jussieu.fr> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=_7c81nw2yt8o4"; protocol="application/pgp-signature"; micalg="pgp-sha1" Content-Transfer-Encoding: 7bit User-Agent: H.R. Communications Internet Messaging System (HCIMS) 4.1 Professional (not for redistribution) / FreeBSD-5.5 Subject: Re: NFS Locking Issue X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Jul 2006 09:50:43 -0000 This message is in MIME format and has been PGP signed. --=_7c81nw2yt8o4 Content-Type: text/plain; charset=ISO-8859-1; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit Quoting Michel Talon : >> So it would appear that you cured the NFS problems inherent with FBSD-6 >> by replacing FBSD with Fedora Linux. Nice to know that NFSd works in Linux. >> But won't help those on the FBSD list fix their FBSD-6 boxen. :/ >> > > First NFS is designed to make machines of different OSs interact properly. Yes, this is it's purpose. > If a FreeBSD server interacts properly with a FreeBSD client, but not other > clients, you cannot say that the situation is fine. Indeed. > Second i am not the one to chose the NFS server, there are people working > in social groups, in the real world. > > And third, the most important, the OP message seemed to imply that the > FreeBSD-6 NFS client was at fault, i pointed out that in my experience my > FreeBSD-6.1 client works OK, while the 6.0 doesn't, when interacting with a > FC5 server. This is in itself a relevant piece of information for the problem > at hand. It may be that the server side is at fault, or some complex > interaction between client and server. Of course. I quite agree. Horrible oversight on my part. > > Anyways some people claimed here that they had no problem with FreeBSD-5 > clients and servers. My experience is that i had constant problems > between FreeBSD-5 clients and Fedora Core 3 servers. I cannot provide any > other data point. I am not particularly sure of the quality of the FC3 or > FC5 NFS server implementation, except that the ~ 100 workstations > running the similar Fedora distribution work like a charm with their homes > NFS mounted on the server. On the other hand a Debian client machine > also has > severe NFS problems. My only conclusion is that these NFS stories are very > tricky. The only moment everything worked fine was when we were running > Solaris on the server. Useful knowledge, to be sure. Sorry for my oversight. I should probably refrain from responding when I have too many other things purculating in my mind while at work. This has gotten me in trouble once before on this _same_ list. :) Thank you for your thoughtful response. > > > -- > > Michel TALON > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > -- panic: kernel trap (ignored) ----------------------------------------------------------------- FreeBSD 5.4-RELEASE-p12 (SMP - 900x2) Tue Mar 7 19:37:23 PST 2006 ///////////////////////////////////////////////////////////////// --=_7c81nw2yt8o4 Content-Type: application/pgp-signature Content-Description: PGP Digital Signature Content-Disposition: inline Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQBEq4tvXxK1cRs0zxkRAhblAJ98+XCLdZHwgWWrVLe4BoR9Jm/14gCfQvI2 zGlmyxeoHwmvAMQsY+jd8fc= =IXpM -----END PGP SIGNATURE----- --=_7c81nw2yt8o4-- From owner-freebsd-stable@FreeBSD.ORG Wed Jul 5 10:46:45 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ED9D116A4DA for ; Wed, 5 Jul 2006 10:46:45 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from cs1.cs.huji.ac.il (cs1.cs.huji.ac.il [132.65.16.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8C45A43D46 for ; Wed, 5 Jul 2006 10:46:45 +0000 (GMT) (envelope-from danny@cs.huji.ac.il) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by cs1.cs.huji.ac.il with esmtp id 1Fy4u4-000A88-3q for freebsd-stable@freebsd.org; Wed, 05 Jul 2006 13:46:44 +0300 X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.2 To: freebsd-stable@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 05 Jul 2006 13:46:44 +0300 From: Danny Braniss Message-ID: Subject: mountd changed? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Jul 2006 10:46:46 -0000 something has changed wrt nmount(2)/mountd(8)/exports(5): > cat /etc/exports /h -alldirs -network 132.65.0.0 -mask 255.255.0.0 > cat /etc/fstab /dev/da1s1d /h ufs rw 1 1 and all is fine, the filesystem is exported and accesible. # /etc/rc.d/mountd reload Reloading mountd config files. but /var/log/messages: mountd[473]: can't change attributes for /h mountd[473]: bad exports list line /h -alldirs -network 132.65.0.0 -mask 255.255.0.0 btw, nothing has changed in the /etc/exports file. 2nd, the root (/) is nfs readonly. and now any attempt to mount is denied. just in case: kern.securelevel: -1 danny From owner-freebsd-stable@FreeBSD.ORG Wed Jul 5 11:38:48 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 74CE916A4DF; Wed, 5 Jul 2006 11:38:48 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from fw.zoral.com.ua (ll-227.216.82.212.sovam.net.ua [212.82.216.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4CF8543D55; Wed, 5 Jul 2006 11:38:46 +0000 (GMT) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by fw.zoral.com.ua (8.13.4/8.13.4) with ESMTP id k65BcOYw017483 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 5 Jul 2006 14:38:24 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.13.6/8.13.6) with ESMTP id k65BcOFe049139; Wed, 5 Jul 2006 14:38:24 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.13.6/8.13.6/Submit) id k65BcMJJ049138; Wed, 5 Jul 2006 14:38:22 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Wed, 5 Jul 2006 14:38:22 +0300 From: Kostik Belousov To: Robert Watson Message-ID: <20060705113822.GM37822@deviant.kiev.zoral.com.ua> References: <20060705100403.Y80381@fledge.watson.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="yaPAUYI/0vT2YKpA" Content-Disposition: inline In-Reply-To: <20060705100403.Y80381@fledge.watson.org> User-Agent: Mutt/1.4.2.1i X-Virus-Scanned: ClamAV version 0.88.2, clamav-milter version 0.88.2 on fw.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=0.4 required=5.0 tests=ALL_TRUSTED, DNS_FROM_RFC_ABUSE,SPF_NEUTRAL autolearn=no version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on fw.zoral.com.ua Cc: freebsd-stable@freebsd.org, Michel Talon Subject: Re: NFS Locking Issue X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Jul 2006 11:38:48 -0000 --yaPAUYI/0vT2YKpA Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jul 05, 2006 at 10:09:24AM +0100, Robert Watson wrote: > The most significant problem working with rpc.lockd is creating easy to= =20 > reproduce test cases. Not least because they can potentially involve=20 > multiple clients. If you can help to produce simple test cases to=20 > reproduce the bugs you're seeing, that would be invaluable. >=20 =2E....... >=20 > Reducing complex failure modes to easily reproduced test cases is tricky= =20 > also, though. It requires careful analysis, often with ktrace and=20 > tcpdump/ethereal to work out what's going on, and not a little luck to=20 > perform the reduction of a large trace down to a simple test scenario. T= he=20 > first step is to try and figure out what, if any, specific workload resul= ts=20 > in a problem. For example, can you trigger it using work on just one=20 > client against a server, without client<->client interactions? This make= s=20 > tracking and reproduction a lot easier, as multi-client test cases are=20 > really tricky! Once you've established whether it can be reproduced with= a=20 > single client, you have to track down the behavior that triggers it --=20 > normally, this is done by attempting to narrow down the specific program = or=20 > sequence of events that causes the bug to trigger, removing things one at= a=20 > time to see what causes the problem to disappear. This is made more=20 > difficult as lock managers are sensitive to timing, so removing a high lo= ad=20 > item from the list, even if it isn't the source of the problem, might cau= se=20 > it to trigger less frequently. I made the patch for rpc.lockd that could somewhat ease obtaining debug information. Patch is available at http://people.freebsd.org/~kib/rpc.lockd-debug.patch No functional changes. Patch only adds dumping of currently held locks (as perceived by lockd) on receiving of SIGUSR1. You need to specify debug level 2 or 3 to obtain the dump. Also, the both lockd processes now put identification information in the proctitle (srv and kern). SIGUSR1 shall be sent to srv process. --yaPAUYI/0vT2YKpA Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) iD8DBQFEq6SuC3+MBN1Mb4gRApCoAKCtMr8xxjm6SRZo/v19JLCc6AYa/ACffhrk DwT7qAM1B0b73pWvr4m7GxU= =4Dzc -----END PGP SIGNATURE----- --yaPAUYI/0vT2YKpA-- From owner-freebsd-stable@FreeBSD.ORG Wed Jul 5 12:21:21 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1482D16A4DA; Wed, 5 Jul 2006 12:21:21 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from fw.zoral.com.ua (ll-227.216.82.212.sovam.net.ua [212.82.216.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id CF56043D6B; Wed, 5 Jul 2006 12:21:06 +0000 (GMT) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by fw.zoral.com.ua (8.13.4/8.13.4) with ESMTP id k65CKf5g018961 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 5 Jul 2006 15:20:41 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.13.6/8.13.6) with ESMTP id k65CKfku049987; Wed, 5 Jul 2006 15:20:41 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.13.6/8.13.6/Submit) id k65CKeUd049986; Wed, 5 Jul 2006 15:20:40 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Wed, 5 Jul 2006 15:20:40 +0300 From: Kostik Belousov To: Robert Watson Message-ID: <20060705122040.GN37822@deviant.kiev.zoral.com.ua> References: <20060705100403.Y80381@fledge.watson.org> <20060705113822.GM37822@deviant.kiev.zoral.com.ua> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="hnsKUeImFCk/igEn" Content-Disposition: inline In-Reply-To: <20060705113822.GM37822@deviant.kiev.zoral.com.ua> User-Agent: Mutt/1.4.2.1i X-Virus-Scanned: ClamAV version 0.88.2, clamav-milter version 0.88.2 on fw.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=0.4 required=5.0 tests=ALL_TRUSTED, DNS_FROM_RFC_ABUSE,SPF_NEUTRAL autolearn=no version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on fw.zoral.com.ua Cc: freebsd-stable@freebsd.org, Michel Talon Subject: Re: NFS Locking Issue X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Jul 2006 12:21:21 -0000 --hnsKUeImFCk/igEn Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jul 05, 2006 at 02:38:22PM +0300, Kostik Belousov wrote: > On Wed, Jul 05, 2006 at 10:09:24AM +0100, Robert Watson wrote: > > The most significant problem working with rpc.lockd is creating easy to= =20 > > reproduce test cases. Not least because they can potentially involve= =20 > > multiple clients. If you can help to produce simple test cases to=20 > > reproduce the bugs you're seeing, that would be invaluable. > >=20 > ........ > >=20 > > Reducing complex failure modes to easily reproduced test cases is trick= y=20 > > also, though. It requires careful analysis, often with ktrace and=20 > > tcpdump/ethereal to work out what's going on, and not a little luck to= =20 > > perform the reduction of a large trace down to a simple test scenario. = The=20 > > first step is to try and figure out what, if any, specific workload res= ults=20 > > in a problem. For example, can you trigger it using work on just one= =20 > > client against a server, without client<->client interactions? This ma= kes=20 > > tracking and reproduction a lot easier, as multi-client test cases are= =20 > > really tricky! Once you've established whether it can be reproduced wi= th a=20 > > single client, you have to track down the behavior that triggers it --= =20 > > normally, this is done by attempting to narrow down the specific progra= m or=20 > > sequence of events that causes the bug to trigger, removing things one = at a=20 > > time to see what causes the problem to disappear. This is made more=20 > > difficult as lock managers are sensitive to timing, so removing a high = load=20 > > item from the list, even if it isn't the source of the problem, might c= ause=20 > > it to trigger less frequently. >=20 > I made the patch for rpc.lockd that could somewhat ease obtaining > debug information. Patch is available at > http://people.freebsd.org/~kib/rpc.lockd-debug.patch >=20 > No functional changes. Patch only adds dumping of currently held locks > (as perceived by lockd) on receiving of SIGUSR1. You need to specify > debug level 2 or 3 to obtain the dump. >=20 > Also, the both lockd processes now put identification information > in the proctitle (srv and kern). SIGUSR1 shall be sent to srv process. Hmm, after looking at the dump there and some code reading, I have noted the following: 1. NLM lock request contains the field caller_name. It is filled by (let call it) kernel rpc.lockd by the results of hostname(3). 2. This caller_name is used by server rpc.lockd to send request for host monitoring to rpc.statd (see send_granted). Request is made by clnt_call, that is blocking rpc call. 3. rpc.statd does getaddrinfo on caller_name to determine address of the host to monitor. If the getaddrinfo in step 3 waits for resolver, then your client machine will get locking process in"lockd" state. Could people experiencing rpc.lockd mistery at least report whether _server_ machine successfully resolve hostname of clients as reported by hostname? And, if yes, to what family of IP protocols ? --hnsKUeImFCk/igEn Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) iD8DBQFEq66XC3+MBN1Mb4gRAihxAJ0SnlK6dgxW2Avpgk0XQmnRbLJn2ACeKu4e IBHKWUU0NroCooOkXQe5TNc= =ixeW -----END PGP SIGNATURE----- --hnsKUeImFCk/igEn-- From owner-freebsd-stable@FreeBSD.ORG Wed Jul 5 13:05:01 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0DE7216A4DA for ; Wed, 5 Jul 2006 13:05:00 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 72EA343D53 for ; Wed, 5 Jul 2006 13:05:00 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id CBECE46CD3; Wed, 5 Jul 2006 09:04:59 -0400 (EDT) Date: Wed, 5 Jul 2006 14:04:59 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Kostik Belousov In-Reply-To: <20060705122040.GN37822@deviant.kiev.zoral.com.ua> Message-ID: <20060705140225.X18236@fledge.watson.org> References: <20060705100403.Y80381@fledge.watson.org> <20060705113822.GM37822@deviant.kiev.zoral.com.ua> <20060705122040.GN37822@deviant.kiev.zoral.com.ua> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org, Michel Talon Subject: Re: NFS Locking Issue X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Jul 2006 13:05:01 -0000 On Wed, 5 Jul 2006, Kostik Belousov wrote: >> Also, the both lockd processes now put identification information in the >> proctitle (srv and kern). SIGUSR1 shall be sent to srv process. > > Hmm, after looking at the dump there and some code reading, I have noted the > following: > > 1. NLM lock request contains the field caller_name. It is filled by (let > call it) kernel rpc.lockd by the results of hostname(3). > > 2. This caller_name is used by server rpc.lockd to send request for host > monitoring to rpc.statd (see send_granted). Request is made by clnt_call, > that is blocking rpc call. > > 3. rpc.statd does getaddrinfo on caller_name to determine address of the > host to monitor. > > If the getaddrinfo in step 3 waits for resolver, then your client machine > will get locking process in"lockd" state. > > Could people experiencing rpc.lockd mistery at least report whether _server_ > machine successfully resolve hostname of clients as reported by hostname? > And, if yes, to what family of IP protocols ? It's not impossible. It would be interesting to see if ps axl reports that rpc.lockd is in the kqread state, which would suggest it was blocked in the resolver. We probably ought to review rpc.statd and make sure it's generally sensible. I've noticed that its notification process on start is a bit poorly structured in terms of how it notifies hosts of its state change -- if one host is down, it may take a very long time to notify other hosts. There are a number of other dubious things about the NLM protocol design (at least, from my reading last night). I've also noticed that our rpc.lockd is particularly sensitive, on the client side, to locks being released by a different process than the process that acquired the lock, which is triggered excessively by our new libpidfile in RELENG_6. Robert N M Watson Computer Laboratory University of Cambridge From owner-freebsd-stable@FreeBSD.ORG Wed Jul 5 13:20:17 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B31EB16A4DE; Wed, 5 Jul 2006 13:20:17 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from fw.zoral.com.ua (ll-227.216.82.212.sovam.net.ua [212.82.216.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id F2C1543D46; Wed, 5 Jul 2006 13:20:16 +0000 (GMT) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by fw.zoral.com.ua (8.13.4/8.13.4) with ESMTP id k65DK6WL020704 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 5 Jul 2006 16:20:06 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.13.6/8.13.6) with ESMTP id k65DK5of060910; Wed, 5 Jul 2006 16:20:05 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.13.6/8.13.6/Submit) id k65DK59Z060909; Wed, 5 Jul 2006 16:20:05 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Wed, 5 Jul 2006 16:20:05 +0300 From: Kostik Belousov To: Robert Watson Message-ID: <20060705132005.GP37822@deviant.kiev.zoral.com.ua> References: <20060705100403.Y80381@fledge.watson.org> <20060705113822.GM37822@deviant.kiev.zoral.com.ua> <20060705122040.GN37822@deviant.kiev.zoral.com.ua> <20060705140225.X18236@fledge.watson.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="B3NBd8mrXZtPJEYR" Content-Disposition: inline In-Reply-To: <20060705140225.X18236@fledge.watson.org> User-Agent: Mutt/1.4.2.1i X-Virus-Scanned: ClamAV version 0.88.2, clamav-milter version 0.88.2 on fw.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=0.4 required=5.0 tests=ALL_TRUSTED, DNS_FROM_RFC_ABUSE,SPF_NEUTRAL autolearn=no version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on fw.zoral.com.ua Cc: freebsd-stable@freebsd.org, Michel Talon Subject: Re: NFS Locking Issue X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Jul 2006 13:20:17 -0000 --B3NBd8mrXZtPJEYR Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jul 05, 2006 at 02:04:59PM +0100, Robert Watson wrote: >=20 > On Wed, 5 Jul 2006, Kostik Belousov wrote: >=20 > >>Also, the both lockd processes now put identification information in th= e=20 > >>proctitle (srv and kern). SIGUSR1 shall be sent to srv process. > > > >Hmm, after looking at the dump there and some code reading, I have noted= =20 > >the following: > > > >1. NLM lock request contains the field caller_name. It is filled by (let= =20 > >call it) kernel rpc.lockd by the results of hostname(3). > > > >2. This caller_name is used by server rpc.lockd to send request for host= =20 > >monitoring to rpc.statd (see send_granted). Request is made by clnt_call= ,=20 > >that is blocking rpc call. > > > >3. rpc.statd does getaddrinfo on caller_name to determine address of the= =20 > >host to monitor. > > > >If the getaddrinfo in step 3 waits for resolver, then your client machin= e=20 > >will get locking process in"lockd" state. > > > >Could people experiencing rpc.lockd mistery at least report whether=20 > >_server_ machine successfully resolve hostname of clients as reported by= =20 > >hostname? And, if yes, to what family of IP protocols ? >=20 > It's not impossible. It would be interesting to see if ps axl reports th= at=20 > rpc.lockd is in the kqread state, which would suggest it was blocked in t= he=20 ^^^^^^^^^^^^ rpc.statd :). > resolver. We probably ought to review rpc.statd and make sure it's=20 > generally sensible. I've noticed that its notification process on start = is=20 > a bit poorly structured in terms of how it notifies hosts of its state=20 > change -- if one host is down, it may take a very long time to notify oth= er=20 > hosts. --B3NBd8mrXZtPJEYR Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) iD8DBQFEq7yEC3+MBN1Mb4gRAl6hAJkBxQS3CgwTXHTUpUYSK/z7SedtrwCfXksU qepdFQmKwhGll47wICxaJDg= =anyo -----END PGP SIGNATURE----- --B3NBd8mrXZtPJEYR-- From owner-freebsd-stable@FreeBSD.ORG Wed Jul 5 13:33:36 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5038816A4E5 for ; Wed, 5 Jul 2006 13:33:36 +0000 (UTC) (envelope-from michel@lpthe.jussieu.fr) Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by mx1.FreeBSD.org (Postfix) with ESMTP id 50ED243D5A for ; Wed, 5 Jul 2006 13:33:32 +0000 (GMT) (envelope-from michel@lpthe.jussieu.fr) Received: from parthe.lpthe.jussieu.fr (parthe.lpthe.jussieu.fr [134.157.10.1]) by shiva.jussieu.fr (8.13.6/jtpda-5.4) with ESMTP id k65DXUYD041804 for ; Wed, 5 Jul 2006 15:33:31 +0200 (CEST) X-Ids: 165 Received: from niobe.lpthe.jussieu.fr (niobe.lpthe.jussieu.fr [134.157.10.41]) by parthe.lpthe.jussieu.fr (Postfix) with ESMTP id 73EA89FB19 for ; Wed, 5 Jul 2006 15:33:30 +0200 (CEST) Received: by niobe.lpthe.jussieu.fr (Postfix, from userid 2005) id 9161235; Wed, 5 Jul 2006 15:33:29 +0200 (CEST) Date: Wed, 5 Jul 2006 15:33:29 +0200 From: Michel Talon To: freebsd-stable@freebsd.org Message-ID: <20060705133329.GA65123@lpthe.jussieu.fr> Mail-Followup-To: Michel Talon , freebsd-stable@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0.2 (shiva.jussieu.fr [134.157.0.165]); Wed, 05 Jul 2006 15:33:31 +0200 (CEST) X-Virus-Scanned: ClamAV 0.88.2/1585/Tue Jul 4 22:39:34 2006 on shiva.jussieu.fr X-Virus-Status: Clean X-j-bayes: Bayes filter score (experimental) : 0.312 XXXXXX X-Miltered: at shiva.jussieu.fr with ID 44ABBFAA.002 by Joe's j-chkmail (http://j-chkmail.ensmp.fr)! Subject: Re: NFS Locking Issue X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Jul 2006 13:33:36 -0000 > So it may be relevant to say that i have kernels without IPV6 support. > Recall that i have absolutely no problem with the client in FreeBSD-6.1. > Tomorrow i will test one of the 6.1 machines as a NFS server and the other as > a client, and will make you know if i see something. Well, i have checked between 2 FreeBSD-6.1-RELEASE machines on the network, both have fxp ethernet driver running at 100 Mb/s, one is NFS server other NFS client. Both run lockd and statd. I have absolutely no problem exchanging files, for example if i begin to copy /usr/src through NFS from one machine to the other, which makes a lot of transactions of all sorts, i get: niobe# mount asmodee:/usr/src /mnt cp -R /mnt/src . ... after some time i interrupt the transfer niobe% du -sh . 131M . and during this time i observe the following type of statistics asmodee% netstat -w 1 -I fxp0 input (fxp0) output packets errs bytes packets errs bytes colls 542 0 84116 1330 0 1219388 0 515 0 72806 1290 0 1196330 0 501 0 95722 1081 0 741048 0 539 0 90704 1090 0 1228052 0 645 0 67888 902 0 1451098 0 405 0 81264 1609 0 604278 0 503 0 74218 709 0 924422 0 500 0 98904 973 0 619350 0 550 0 100122 855 0 836328 0 615 0 79336 1081 0 862772 0 577 0 82862 901 0 1005024 0 which looks decent to me. Doing the same with just one big file no problem either, and i get a transfer speed of 6.60 MB/s which is perhaps a little less than with linux, but nothing catastrophic. I get 8.20 MB/s for FreeBSD client interacting with the Linux server. Now netstat gives packets errs bytes packets errs bytes colls 785 0 123266 4716 0 6825600 0 759 0 139898 4530 0 7747276 0 852 0 124652 5106 0 6902566 0 863 0 128040 5170 0 7081738 0 811 0 123760 4862 0 6851498 0 789 0 123540 4720 0 6834310 0 840 0 115378 5024 0 6382114 0 So up to what i can see NFS works OK for me on FreeBSD-6.1. So the main difference with other people cases may be that i have removed IPV6 support from kernel. -- Michel TALON From owner-freebsd-stable@FreeBSD.ORG Wed Jul 5 14:51:46 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 946F616A4DA; Wed, 5 Jul 2006 14:51:46 +0000 (UTC) (envelope-from freebsd@hub.org) Received: from hub.org (hub.org [200.46.204.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1D50743D49; Wed, 5 Jul 2006 14:51:45 +0000 (GMT) (envelope-from freebsd@hub.org) Received: from localhost (wm.hub.org [200.46.204.128]) by hub.org (Postfix) with ESMTP id BF842290C1E; Wed, 5 Jul 2006 11:51:38 -0300 (ADT) Received: from hub.org ([200.46.204.220]) by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024) with ESMTP id 76859-02; Wed, 5 Jul 2006 14:51:44 +0000 (UTC) Received: from ganymede.hub.org (blk-7-151-244.eastlink.ca [71.7.151.244]) by hub.org (Postfix) with ESMTP id 9FFA4290C20; Wed, 5 Jul 2006 11:51:37 -0300 (ADT) Received: by ganymede.hub.org (Postfix, from userid 1027) id 7938849A13; Wed, 5 Jul 2006 11:51:49 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id 77BCB4825E; Wed, 5 Jul 2006 11:51:49 -0300 (ADT) Date: Wed, 5 Jul 2006 11:51:49 -0300 (ADT) From: User Freebsd To: Robert Watson In-Reply-To: <20060705100403.Y80381@fledge.watson.org> Message-ID: <20060705114848.F1103@ganymede.hub.org> References: <20060705100403.Y80381@fledge.watson.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org, Michel Talon Subject: Re: NFS Locking Issue X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Jul 2006 14:51:46 -0000 On Wed, 5 Jul 2006, Robert Watson wrote: > On Wed, 5 Jul 2006, Danny Braniss wrote: > >> In my case our main servers are NetApp, and the problems are more related >> to am-utils running into some race condition (need more time to debug this >> :-) the other problem is related to throughput, freebsd is slower than >> linux, and while freebsd/nfs/tcp is faster on Freebsd than udp, on linux >> it's the same. So it seems some tunning is needed. >> >> our main problem now is samba/rpc.lockd, we are stuck with a server running >> FreeBSD 5.4 which crashes, and we can't upgrade to 6.1 because lockd >> doesn't work. >> >> So, if someone is willing to look into the lockd issue, we would like to >> help. > > The most significant problem working with rpc.lockd is creating easy to > reproduce test cases. Not least because they can potentially involve > multiple clients. If you can help to produce simple test cases to reproduce > the bugs you're seeing, that would be invaluable. > > I'm aware of two general classes of problems with rpc.lockd. First, > architectural issues, some derived from architectural problems in the NLM > protocol: for example, assumptions that there can be a clean mapping of > process lock owners to locks, which fall down as locks are properties of file > descriptors that can be inheritted. Second, implementation bugs/misfeatures, > such as the kernel not knowing how to cancel lock requests, so being unable > to implement interruptible waits on locks in the distributed case. > > Reducing complex failure modes to easily reproduced test cases is tricky > also, though. It requires careful analysis, often with ktrace and > tcpdump/ethereal to work out what's going on, and not a little luck to > perform the reduction of a large trace down to a simple test scenario. The > first step is to try and figure out what, if any, specific workload results > in a problem. For example, can you trigger it using work on just one client > against a server, without client<->client interactions? This makes tracking > and reproduction a lot easier, as multi-client test cases are really tricky! > Once you've established whether it can be reproduced with a single client, > you have to track down the behavior that triggers it -- normally, this is > done by attempting to narrow down the specific program or sequence of events > that causes the bug to trigger, removing things one at a time to see what > causes the problem to disappear. This is made more difficult as lock > managers are sensitive to timing, so removing a high load item from the list, > even if it isn't the source of the problem, might cause it to trigger less > frequently. I'm not sure if this is an option for anyone, either developer or user, but in the past, on particularly tricky bugs where I seemed to be the only one to be able to produce it, I've given access to a 'trusted developer' to the machine itself, to minimize the time lag that emails create ... but, also, to let the developer at a machine that has the load required to easily reproduce it ... Not sure if there is anyone out there, on either side of the proverbial fence, that feels comfortable doing this, but figured I'd throw the idea out ... I believe, in Francisco's case, they are willing to pay someone to fix the NFS issues they are having, which, i'd assume, means easy access to the problematic server(s) to do proper testing in a "real life scenario" ... ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . scrappy@hub.org MSN . scrappy@hub.org Yahoo . yscrappy Skype: hub.org ICQ . 7615664 From owner-freebsd-stable@FreeBSD.ORG Wed Jul 5 15:18:11 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5384416A56D for ; Wed, 5 Jul 2006 15:18:11 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 00D0543D4C for ; Wed, 5 Jul 2006 15:18:08 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 49EB946C84; Wed, 5 Jul 2006 11:18:08 -0400 (EDT) Date: Wed, 5 Jul 2006 16:18:08 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Michael Collette In-Reply-To: <44A99CC1.7070501@TestEquity.com> Message-ID: <20060705161559.W18236@fledge.watson.org> References: <20060629230309.GA12773@lpthe.jussieu.fr> <20060630041733.GA4941@zibbi.meraka.csir.co.za> <20060702162942.D1103@ganymede.hub.org> <44A99CC1.7070501@TestEquity.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org, User Freebsd Subject: Re: NFS Locking Issue X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Jul 2006 15:18:11 -0000 On Mon, 3 Jul 2006, Michael Collette wrote: > --------------------------------------------------------------------- > Let's start with the simplest. The scenario here involves 2 machines, mach01 > and mach02. Both are running 6-STABLE, and both are running rpcbind, > rpc.statd, and rpc.lockd. mach01 has exported /documents and mach02 is > mounting that export under /mnt. Simple enough? > > The /documents directory has multiple subdirectories and files of various > sizes. The actual amount of data doesn't really matter to produce a failure. > All you need to do at this point is to try to copy files from that mount > point to somewhere else on the hard drive. > > cp -Rp /mnt/* /tmp/documents/ > > You may, or not, see that a couple of subdirectories were created, but no > files actually moved over. The cp command is now locked up, and no traffic > moves. This usually takes a second or two to show up as a problem. I can > repeat this with multiple 6-STABLE boxes. > > Turn off rpc.lockd on either the server or client before the cp command, and > things work. I've tried several times to reproduce this, and have not succeeded in doing so. In princple, cp should not be using advisory locks. Could you try running cp under ktrace, and saving the ktrace file somewhere outside of NFS? Something like the following: ktrace -f /usr/tmp/localfile cp -Rp /mnt/* /tmp/documents/ If you are able to reproduce the problem with tracing turned on, a copy of the tracefile would be very helpful. Also, when it locks up, are you able to kill cp using Ctrl-C, and if you hit Ctrl-T while it appears locked, what output do you get? Thanks, Robert N M Watson Computer Laboratory University of Cambridge From owner-freebsd-stable@FreeBSD.ORG Wed Jul 5 16:41:55 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B53E116A4DF for ; Wed, 5 Jul 2006 16:41:55 +0000 (UTC) (envelope-from lists@niamodnikufesin.de) Received: from mx.does.not-exist.de (mx.does.not-exist.de [62.159.88.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id B3F6343D69 for ; Wed, 5 Jul 2006 16:41:49 +0000 (GMT) (envelope-from lists@niamodnikufesin.de) Received: from rw.does.not-exist.de ([10.42.23.2]) by mx.does.not-exist.de with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.52 (FreeBSD)) id 1FyAQq-000AsB-MJ; Wed, 05 Jul 2006 18:40:57 +0200 Received: from hank by rw.does.not-exist.de with local (Exim 4.52 (FreeBSD)) id 1FyAQs-0001N1-ET; Wed, 05 Jul 2006 18:40:58 +0200 Date: Wed, 5 Jul 2006 18:40:58 +0200 From: Hank Hampel To: freebsd-stable@freebsd.org Message-ID: <20060705164058.GA5194@warning.this.domain.does.not-exist.de> Mail-Followup-To: freebsd-stable@freebsd.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="jI8keyz6grp/JLjh" Content-Disposition: inline User-Agent: Mutt/1.4.2.1i X-fcc-folder: freebsd-stable-list Subject: 5.5-stable network interface rl0 stops working X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Jul 2006 16:41:55 -0000 --jI8keyz6grp/JLjh Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hello everybody, I have a very disturbing problem with one of our FreeBSD 5.5-stable machines. It is a box on which ~10 jail systems run, each with small to moderate network traffic. Now from time to time - sometimes after a few days, sometimes after a couple of weeks - the network interface rl0 (which is the main interface on the maschine, rl1 is for backups/internal use only) stops working. Each jailed system has its own firewall ruleset, permitting only traffic for the services in that specific jail. The packet filter used is ipfw. Some of the rules are stateful (keep-state). When rl0 stops working ipfw loggs lots of denied packets so that it seems that the dynamic (keep-state) rules don't work any longer. We checked and increased the buffers for the dynamic rules to no avail - I doubt they are part of the problem. I'm not even sure ipfw is part of the problem. After the stop on the interface occurs there is no other way to get the interface up and running again than rebooting the whole machine. Restarting /etc/rc.d/netif, the jails or ipfw doesn't help anything. The bad thing is I haven't found any way to trigger this problem so that I can only check and change things and wait if the situation improves or not. For example I've already set debug.mpsafenet="0" but this doesn't help, in contrast it seems to worsen the problem a little bit. Find attached the dmesg output of the machine. If any other information is needed to hunt down the cause of this problem please let me know. I checked various list archives but haven't found a clue yet. -------------------------[ dmesg ]------------------------- Copyright (c) 1992-2006 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.5-STABLE #5: Tue May 30 13:51:55 CEST 2006 root@shawshank.nr-city.net:/usr/obj/usr/src/sys/SHAWSHANK WARNING: MPSAFE network stack disabled, expect reduced performance. Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) 4 CPU 2.40GHz (2411.60-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf34 Stepping = 4 Features=0xbfebfbff real memory = 2147418112 (2047 MB) avail memory = 2096037888 (1998 MB) ACPI APIC Table: ioapic0 irqs 0-23 on motherboard npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 cpu0: on acpi0 acpi_button0: on acpi0 pcib0: port 0x1000-0x10bf,0xcf8-0xcff on acpi0 pci0: on pcib0 agp0: mem 0xe8000000-0xefffffff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pcib2: at device 30.0 on pci0 pci2: on pcib2 pci2: at device 0.0 (no driver attached) rl0: port 0x9000-0x90ff mem 0xf5000000-0xf50000ff irq 21 at device 1.0 on pci2 miibus0: on rl0 rlphy0: on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto rl0: Ethernet address: 00:02:2a:d5:39:74 rl1: port 0x9400-0x94ff mem 0xf5001000-0xf50010ff irq 22 at device 2.0 on pci2 miibus1: on rl1 rlphy1: on miibus1 rlphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto rl1: Ethernet address: 00:02:2a:d5:39:53 isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0xf000-0xf00f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 31.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 pci0: at device 31.3 (no driver attached) acpi_tz0: on acpi0 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A, console sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A pmtimer0 on isa0 orm0: at iomem 0xc0000-0xc7fff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x100> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 atkbdc0: at port 0x64,0x60 on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 ppc0: parallel port not found. Timecounter "TSC" frequency 2411601876 Hz quality 800 Timecounters tick every 10.000 msec ipfw2 initialized, divert disabled, rule-based forwarding disabled, default to deny, logging disabled ad0: 114497MB [232629/16/63] at ata0-master UDMA100 acd0: DVDROM at ata1-master PIO4 Mounting root from ufs:/dev/ad0s1a -------------------------[ dmesg ]------------------------- Best regards, Hank --jI8keyz6grp/JLjh Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQFEq+uaXSKk5/a79toRAj8sAJ94aRlBwuxaWHIadN52uhULfom3EQCgmzYJ S1lUdr6+ZSyF2pBJe50bSio= =iZKr -----END PGP SIGNATURE----- --jI8keyz6grp/JLjh-- From owner-freebsd-stable@FreeBSD.ORG Wed Jul 5 17:42:52 2006 Return-Path: X-Original-To: stable@FreeBSD.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9BC4016A4DE for ; Wed, 5 Jul 2006 17:42:52 +0000 (UTC) (envelope-from gibbs@scsiguy.com) Received: from ns1.scsiguy.com (ns1.scsiguy.com [70.89.174.89]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3EC1043D49 for ; Wed, 5 Jul 2006 17:42:52 +0000 (GMT) (envelope-from gibbs@scsiguy.com) Received: from [10.0.0.90] (63-138-13-146.customer.static.ip.paetec.net [63.138.13.146] (may be forged)) (authenticated bits=0) by ns1.scsiguy.com (8.13.6/8.13.6) with ESMTP id k65HgnA6009867 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 5 Jul 2006 11:42:50 -0600 (MDT) (envelope-from gibbs@scsiguy.com) Date: Wed, 05 Jul 2006 11:42:44 -0600 From: "Justin T. Gibbs" To: stable@FreeBSD.org Message-ID: <86C10E7655AA8C2D8C433AAC@[10.0.0.90]> X-Mailer: Mulberry/3.1.6 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline Cc: Subject: fetch hangs on AMD64 RELENG_6 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Jul 2006 17:42:52 -0000 Hi, I'm seeing fetch hang under AMD64/RELENG_6 when fetching data from several different sites. An i386 machinem sitting next to it running current from a few weeks back is not showing this problem when fetching the same files. The failing machine is a Dell 2850 with an em0 device. We have a T-1 here, so transfer speeds are usually well over 100KBps. fetch is stuck in sbwait. Restarting fetch a few times will eventually allow the transfer to complete. Anyone else seen this? Any hints on how I might help debug the problem? Thanks, Justin From owner-freebsd-stable@FreeBSD.ORG Wed Jul 5 17:48:19 2006 Return-Path: X-Original-To: stable@FreeBSD.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4594116A4E0 for ; Wed, 5 Jul 2006 17:48:19 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from pi.codefab.com (pi.codefab.com [199.103.21.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4137843D6B for ; Wed, 5 Jul 2006 17:48:11 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from localhost (localhost [127.0.0.1]) by pi.codefab.com (Postfix) with ESMTP id C2E9C5FCC; Wed, 5 Jul 2006 13:48:10 -0400 (EDT) X-Virus-Scanned: amavisd-new at codefab.com Received: from pi.codefab.com ([127.0.0.1]) by localhost (pi.codefab.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0YINCiM3DGwb; Wed, 5 Jul 2006 13:48:10 -0400 (EDT) Received: from [199.103.21.238] (pan.codefab.com [199.103.21.238]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by pi.codefab.com (Postfix) with ESMTP id 1025D5C2E; Wed, 5 Jul 2006 13:48:10 -0400 (EDT) In-Reply-To: <86C10E7655AA8C2D8C433AAC@[10.0.0.90]> References: <86C10E7655AA8C2D8C433AAC@[10.0.0.90]> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Charles Swiger Date: Wed, 5 Jul 2006 13:48:07 -0400 To: Justin T. Gibbs X-Mailer: Apple Mail (2.752.2) Cc: stable@FreeBSD.org Subject: Re: fetch hangs on AMD64 RELENG_6 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Jul 2006 17:48:19 -0000 On Jul 5, 2006, at 1:42 PM, Justin T. Gibbs wrote: > I'm seeing fetch hang under AMD64/RELENG_6 when fetching data > from several different sites. An i386 machine sitting next to it > running current from a few weeks back is not showing this problem > when fetching the same files. [ ... ] > Any hints on how I might help debug the problem? Using tcpdump to look at the traffic would be a useful starting point. :-) -- -Chuck From owner-freebsd-stable@FreeBSD.ORG Wed Jul 5 17:48:59 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4951E16A4E6 for ; Wed, 5 Jul 2006 17:48:59 +0000 (UTC) (envelope-from freebsd@hub.org) Received: from hub.org (hub.org [200.46.204.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1B6E643D53 for ; Wed, 5 Jul 2006 17:48:58 +0000 (GMT) (envelope-from freebsd@hub.org) Received: from localhost (wm.hub.org [200.46.204.128]) by hub.org (Postfix) with ESMTP id F3A5E290C20; Wed, 5 Jul 2006 14:48:55 -0300 (ADT) Received: from hub.org ([200.46.204.220]) by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024) with ESMTP id 40807-10; Wed, 5 Jul 2006 17:48:57 +0000 (UTC) Received: from ganymede.hub.org (blk-7-151-244.eastlink.ca [71.7.151.244]) by hub.org (Postfix) with ESMTP id 285C1290C1E; Wed, 5 Jul 2006 14:48:55 -0300 (ADT) Received: by ganymede.hub.org (Postfix, from userid 1027) id 3F4474825E; Wed, 5 Jul 2006 14:48:53 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id 39B4837EC9; Wed, 5 Jul 2006 14:48:53 -0300 (ADT) Date: Wed, 5 Jul 2006 14:48:53 -0300 (ADT) From: User Freebsd To: Michel Talon In-Reply-To: <20060705133329.GA65123@lpthe.jussieu.fr> Message-ID: <20060705144809.F1171@ganymede.hub.org> References: <20060705133329.GA65123@lpthe.jussieu.fr> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org Subject: Re: NFS Locking Issue X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Jul 2006 17:48:59 -0000 On Wed, 5 Jul 2006, Michel Talon wrote: >> So it may be relevant to say that i have kernels without IPV6 support. >> Recall that i have absolutely no problem with the client in FreeBSD-6.1. >> Tomorrow i will test one of the 6.1 machines as a NFS server and the other as >> a client, and will make you know if i see something. > > Well, i have checked between 2 FreeBSD-6.1-RELEASE machines on the network, > both have fxp ethernet driver running at 100 Mb/s, one is NFS server other NFS > client. Both run lockd and statd. I have absolutely no problem exchanging > files, for example if i begin to copy /usr/src through NFS from one machine to > the other, which makes a lot of transactions of all sorts, i get: > niobe# mount asmodee:/usr/src /mnt > cp -R /mnt/src . > ... > after some time i interrupt the transfer > niobe% du -sh . > 131M . > and during this time i observe the following type of statistics > asmodee% netstat -w 1 -I fxp0 > input (fxp0) output > packets errs bytes packets errs bytes colls > 542 0 84116 1330 0 1219388 0 > 515 0 72806 1290 0 1196330 0 > 501 0 95722 1081 0 741048 0 > 539 0 90704 1090 0 1228052 0 > 645 0 67888 902 0 1451098 0 > 405 0 81264 1609 0 604278 0 > 503 0 74218 709 0 924422 0 > 500 0 98904 973 0 619350 0 > 550 0 100122 855 0 836328 0 > 615 0 79336 1081 0 862772 0 > 577 0 82862 901 0 1005024 0 > > which looks decent to me. > > Doing the same with just one big file no problem either, and i get a transfer > speed of 6.60 MB/s which is perhaps a little less than with linux, but nothing > catastrophic. I get 8.20 MB/s for FreeBSD client interacting with the Linux > server. > > Now netstat gives > packets errs bytes packets errs bytes colls > 785 0 123266 4716 0 6825600 0 > 759 0 139898 4530 0 7747276 0 > 852 0 124652 5106 0 6902566 0 > 863 0 128040 5170 0 7081738 0 > 811 0 123760 4862 0 6851498 0 > 789 0 123540 4720 0 6834310 0 > 840 0 115378 5024 0 6382114 0 > > So up to what i can see NFS works OK for me on FreeBSD-6.1. > > So the main difference with other people cases may be that i have removed IPV6 > support from kernel. What are others using for ethernet? In your case, you say you are running between fxp cards ... I've heard some report, in another thread, problems with the bge driver ... could we be possibly talking internet vs nfs issues? ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . scrappy@hub.org MSN . scrappy@hub.org Yahoo . yscrappy Skype: hub.org ICQ . 7615664 From owner-freebsd-stable@FreeBSD.ORG Wed Jul 5 17:49:03 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BD61016A537 for ; Wed, 5 Jul 2006 17:49:03 +0000 (UTC) (envelope-from rsmith@xs4all.nl) Received: from smtp-vbr16.xs4all.nl (smtp-vbr16.xs4all.nl [194.109.24.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8BCE743D46 for ; Wed, 5 Jul 2006 17:49:02 +0000 (GMT) (envelope-from rsmith@xs4all.nl) Received: from slackbox.xs4all.nl (slackbox.xs4all.nl [213.84.242.160]) by smtp-vbr16.xs4all.nl (8.13.6/8.13.6) with ESMTP id k65Hn0Zu023222 for ; Wed, 5 Jul 2006 19:49:01 +0200 (CEST) (envelope-from rsmith@xs4all.nl) Received: by slackbox.xs4all.nl (Postfix, from userid 1001) id 9C9B4B89D; Wed, 5 Jul 2006 19:49:00 +0200 (CEST) Date: Wed, 5 Jul 2006 19:49:00 +0200 From: Roland Smith To: freebsd-stable@freebsd.org Message-ID: <20060705174900.GA36025@slackbox.xs4all.nl> Mail-Followup-To: freebsd-stable@freebsd.org References: <20060705164058.GA5194@warning.this.domain.does.not-exist.de> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="uAKRQypu60I7Lcqm" Content-Disposition: inline In-Reply-To: <20060705164058.GA5194@warning.this.domain.does.not-exist.de> X-GPG-Fingerprint: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 X-GPG-Key: http://www.xs4all.nl/~rsmith/pubkey.txt X-GPG-Notice: If this message is not signed, don't assume I sent it! User-Agent: Mutt/1.5.11 X-Virus-Scanned: by XS4ALL Virus Scanner Subject: Re: 5.5-stable network interface rl0 stops working X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Jul 2006 17:49:03 -0000 --uAKRQypu60I7Lcqm Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jul 05, 2006 at 06:40:58PM +0200, Hank Hampel wrote: > Hello everybody, >=20 > I have a very disturbing problem with one of our FreeBSD 5.5-stable > machines. It is a box on which ~10 jail systems run, each with > small to moderate network traffic. >=20 > Now from time to time - sometimes after a few days, sometimes after a > couple of weeks - the network interface rl0 (which is the main > interface on the maschine, rl1 is for backups/internal use only) stops > working. Are they physically on the motherboard? Or on PCI cards? In the latter case try reseating the card in the slot. Try switching rl0 and rl1, and see if te problem persists. Also, swapping out the ethernet cable is worth trying. Another thing to check is if rl0 is sharing an interrupt with another device. That can cause problems. > Each jailed system has its own firewall ruleset, permitting only > traffic for the services in that specific jail. The packet filter used > is ipfw. Some of the rules are stateful (keep-state). >=20 > When rl0 stops working ipfw loggs lots of denied packets so that it > seems that the dynamic (keep-state) rules don't work any longer. We > checked and increased the buffers for the dynamic rules to no avail - > I doubt they are part of the problem. I'm not even sure ipfw is part > of the problem. Does the problem persist without ipfw? I've got an rl0 card on my workstation (6.1-STABLE, amd64, using PF without problems) > After the stop on the interface occurs there is no other way to get > the interface up and running again than rebooting the whole machine. > Restarting /etc/rc.d/netif, the jails or ipfw doesn't help anything. What does ifconfig say after the interface stops working? =20 > The bad thing is I haven't found any way to trigger this problem so > that I can only check and change things and wait if the situation > improves or not. For example I've already set debug.mpsafenet=3D"0" but > this doesn't help, in contrast it seems to worsen the problem a little > bit. > Find attached the dmesg output of the machine. If any other > information is needed to hunt down the cause of this problem please > let me know. I checked various list archives but haven't found a clue > yet. Anything in the logs, except the denied packets? Roland --=20 R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) --uAKRQypu60I7Lcqm Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) iD8DBQFEq/uMEnfvsMMhpyURAtNcAJ94jGl9dy5fEX/JW+LZMHW0giDY/wCfWrfZ knAr80PjaFHf4KT2ecc9SpI= =LMPX -----END PGP SIGNATURE----- --uAKRQypu60I7Lcqm-- From owner-freebsd-stable@FreeBSD.ORG Wed Jul 5 17:52:48 2006 Return-Path: X-Original-To: stable@FreeBSD.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E11DB16A4E5 for ; Wed, 5 Jul 2006 17:52:48 +0000 (UTC) (envelope-from mike@jellydonut.org) Received: from mail.secureworks.net (mail.secureworks.net [65.114.32.155]) by mx1.FreeBSD.org (Postfix) with SMTP id 38C0143D45 for ; Wed, 5 Jul 2006 17:52:46 +0000 (GMT) (envelope-from mike@jellydonut.org) Received: (qmail 57392 invoked from network); 5 Jul 2006 17:52:45 -0000 Received: from unknown (HELO ?192.168.14.135?) (63.239.86.253) by 0 with SMTP; 5 Jul 2006 17:52:45 -0000 Message-ID: <44ABFC6C.4070203@jellydonut.org> Date: Wed, 05 Jul 2006 13:52:44 -0400 From: Michael Proto User-Agent: Thunderbird 1.5.0.4 (X11/20060627) MIME-Version: 1.0 References: <86C10E7655AA8C2D8C433AAC@[10.0.0.90]> In-Reply-To: <86C10E7655AA8C2D8C433AAC@[10.0.0.90]> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: stable@FreeBSD.org Subject: Re: fetch hangs on AMD64 RELENG_6 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Jul 2006 17:52:49 -0000 Justin T. Gibbs wrote: > Hi, > > I'm seeing fetch hang under AMD64/RELENG_6 when fetching data > from several different sites. An i386 machinem sitting next to it > running current from a few weeks back is not showing this problem > when fetching the same files. The failing machine is a Dell 2850 > with an em0 device. We have a T-1 here, so transfer speeds are > usually well over 100KBps. fetch is stuck in sbwait. Restarting > fetch a few times will eventually allow the transfer to complete. > Anyone else seen this? Any hints on how I might help debug the > problem? > Are these fetches for ports installs, and if so are they from the gnu.org site(s)? I noticed a similar issue myself last night when doing some installs from ports, and they were all related to gnu.org FTP sites. Otherwise fetch was working just as expected. -Proto From owner-freebsd-stable@FreeBSD.ORG Wed Jul 5 17:54:06 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B7E7316A4E2 for ; Wed, 5 Jul 2006 17:54:06 +0000 (UTC) (envelope-from mihir.sanghavi@gmail.com) Received: from wx-out-0102.google.com (wx-out-0102.google.com [66.249.82.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id 804A143D7B for ; Wed, 5 Jul 2006 17:54:05 +0000 (GMT) (envelope-from mihir.sanghavi@gmail.com) Received: by wx-out-0102.google.com with SMTP id h30so835116wxd for ; Wed, 05 Jul 2006 10:54:04 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=MA/p+PKJyxRUqHlKx01O9nBM/pXCjLg1Iu6BpDzXDJfaKkXOx50r+M+PRFNKGn4UAgP7FzP3liwYXmgqTNAW9BnQdkz5jJuVpIs1eaEXoTfKB2BfORt5ETRbVYASfpe+NKdagdhhgathv1CFQx9qNqybjvatiyoud42oqm/Eqgo= Received: by 10.70.99.7 with SMTP id w7mr4538098wxb; Wed, 05 Jul 2006 10:54:04 -0700 (PDT) Received: by 10.70.48.16 with HTTP; Wed, 5 Jul 2006 10:54:04 -0700 (PDT) Message-ID: <11419abd0607051054r7d8f5c81r7d6331208bd9ec82@mail.gmail.com> Date: Wed, 5 Jul 2006 10:54:04 -0700 From: "Mihir Sanghavi" To: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Network Card X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Jul 2006 17:54:06 -0000 Hi, Can someone please tell me how do i activate the network card in FreeBSD 5.5. Thanks. -- What we see depends mainly on what we look for. -MIHIR From owner-freebsd-stable@FreeBSD.ORG Wed Jul 5 18:21:11 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 35F0916A4E2 for ; Wed, 5 Jul 2006 18:21:11 +0000 (UTC) (envelope-from cianlists@cian.ws) Received: from mail.cian.ws (cian.ws [87.192.36.98]) by mx1.FreeBSD.org (Postfix) with ESMTP id 876DF43D7E for ; Wed, 5 Jul 2006 18:21:03 +0000 (GMT) (envelope-from cianlists@cian.ws) Received: from localhost (localhost [127.0.0.1]) by mail.cian.ws (Postfix) with ESMTP id A83AF33C66; Wed, 5 Jul 2006 19:21:01 +0100 (IST) X-Virus-Scanned: amavisd-new at cian.ws Received: from mail.cian.ws ([127.0.0.1]) by localhost (oppy.cian.ws [127.0.0.1]) (amavisd-new, port 10024) with LMTP id QRZBBv-anWHq; Wed, 5 Jul 2006 19:20:58 +0100 (IST) Received: from [10.0.1.5] (g5.cian.ws [10.0.1.5]) by mail.cian.ws (Postfix) with ESMTP id F161A33C60; Wed, 5 Jul 2006 19:20:57 +0100 (IST) In-Reply-To: <11419abd0607051054r7d8f5c81r7d6331208bd9ec82@mail.gmail.com> References: <11419abd0607051054r7d8f5c81r7d6331208bd9ec82@mail.gmail.com> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="Apple-Mail-18--129719156" Message-Id: Content-Transfer-Encoding: 7bit From: Cian Hughes Date: Wed, 5 Jul 2006 19:20:56 +0100 To: Mihir Sanghavi X-Pgp-Agent: GPGMail 1.1.2 (Tiger) X-Mailer: Apple Mail (2.752.2) Cc: freebsd-stable@freebsd.org Subject: Re: Network Card X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Jul 2006 18:21:11 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --Apple-Mail-18--129719156 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/config- network-setup.html might help you Regards, cian On 5 Jul 2006, at 18:54, Mihir Sanghavi wrote: > Hi, > Can someone please tell me how do i activate the network card in > FreeBSD 5.5. > Thanks. > -- > What we see depends mainly on what we look for. > -MIHIR > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable- > unsubscribe@freebsd.org" --Apple-Mail-18--129719156 content-type: application/pgp-signature; x-mac-type=70674453; name=PGP.sig content-description: This is a digitally signed message part content-disposition: inline; filename=PGP.sig content-transfer-encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (Darwin) iD8DBQFErAMIaVVfOlCF0TQRAvcWAJ0VTGHB02zmc6NuNIINIrcGIr2tPgCgkEBV vp1GB0q/Mtes3DpKNt1D3OI= =9CQD -----END PGP SIGNATURE----- --Apple-Mail-18--129719156-- From owner-freebsd-stable@FreeBSD.ORG Wed Jul 5 20:08:52 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 14CB416A4DD for ; Wed, 5 Jul 2006 20:08:52 +0000 (UTC) (envelope-from michel@lpthe.jussieu.fr) Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by mx1.FreeBSD.org (Postfix) with ESMTP id 097C743D49 for ; Wed, 5 Jul 2006 20:08:50 +0000 (GMT) (envelope-from michel@lpthe.jussieu.fr) Received: from parthe.lpthe.jussieu.fr (parthe.lpthe.jussieu.fr [134.157.10.1]) by shiva.jussieu.fr (8.13.6/jtpda-5.4) with ESMTP id k65K8nRb020912 for ; Wed, 5 Jul 2006 22:08:49 +0200 (CEST) X-Ids: 165 Received: from niobe.lpthe.jussieu.fr (niobe.lpthe.jussieu.fr [134.157.10.41]) by parthe.lpthe.jussieu.fr (Postfix) with ESMTP id 5A2A69FBD1 for ; Wed, 5 Jul 2006 22:08:49 +0200 (CEST) Received: by niobe.lpthe.jussieu.fr (Postfix, from userid 2005) id 971F835; Wed, 5 Jul 2006 22:08:48 +0200 (CEST) Date: Wed, 5 Jul 2006 22:08:48 +0200 From: Michel Talon To: freebsd-stable@freebsd.org Message-ID: <20060705200848.GA66671@lpthe.jussieu.fr> Mail-Followup-To: Michel Talon , freebsd-stable@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0.2 (shiva.jussieu.fr [134.157.0.165]); Wed, 05 Jul 2006 22:08:49 +0200 (CEST) X-Virus-Scanned: ClamAV 0.88.2/1586/Wed Jul 5 21:22:07 2006 on shiva.jussieu.fr X-Virus-Status: Clean X-j-bayes: Bayes filter score (experimental) : 0.384 XXXXXXX X-Miltered: at shiva.jussieu.fr with ID 44AC1C51.003 by Joe's j-chkmail (http://j-chkmail.ensmp.fr)! Subject: Re: NFS Locking Issue X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Jul 2006 20:08:52 -0000 > with the bge driver ... could we be possibly talking internet vs nfs > issues? Pursuing invetigations, i have discovered that for people having workstations whose home directories are on a NFS server, and who run Gnome or KDE, there is a program which has horrible NFS behavior, it is gam_server from gamin, which detects alterations on your .kde for example. On my machine running nfsstat -c -w 1 i see 4000 requests/s due to that. If i displace it (*) and kill it, this drops to 80 requests/s and KDE works exactly as well, including discovering new files. I think it is not necessary to comment on the performance penalty if a number of stations send 4000r/s to a server, it will soon be killed. (*) it restarts itself automatically so it is necessary to displace or rename it before killing. -- Michel TALON From owner-freebsd-stable@FreeBSD.ORG Wed Jul 5 20:22:52 2006 Return-Path: X-Original-To: stable@FreeBSD.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D175016A4DE for ; Wed, 5 Jul 2006 20:22:52 +0000 (UTC) (envelope-from gibbs@scsiguy.com) Received: from ns1.scsiguy.com (ns1.scsiguy.com [70.89.174.89]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6FA9543D5E for ; Wed, 5 Jul 2006 20:22:50 +0000 (GMT) (envelope-from gibbs@scsiguy.com) Received: from [10.0.0.90] (63-138-13-146.customer.static.ip.paetec.net [63.138.13.146] (may be forged)) (authenticated bits=0) by ns1.scsiguy.com (8.13.6/8.13.6) with ESMTP id k65KMm7Z010545 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 5 Jul 2006 14:22:49 -0600 (MDT) (envelope-from gibbs@scsiguy.com) Date: Wed, 05 Jul 2006 14:22:42 -0600 From: "Justin T. Gibbs" To: Charles Swiger Message-ID: In-Reply-To: References: <86C10E7655AA8C2D8C433AAC@[10.0.0.90]> X-Mailer: Mulberry/3.1.6 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline Cc: stable@FreeBSD.org Subject: Re: fetch hangs on AMD64 RELENG_6 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Jul 2006 20:22:52 -0000 Hmm. Seems we close the window unexpectedly and the remote side doesn't retransmit when we open it. FreeBSD's acks stop once the window is fully open... aren't the acks supposed to retried longer? If not, shouldn't fetch eventually see a socket close event instead of hanging forever? A similar failure occurs with SACK disabled. -- Justin 13:31:44.695211 IP manna.mozilla.org.http > databus.avidyne.com.64531: . 9018128:9019496(1368) ack 179 win 1716 13:31:44.695229 IP databus.avidyne.com.64531 > manna.mozilla.org.http: . ack 8957936 win 32832 13:31:44.702704 IP manna.mozilla.org.http > databus.avidyne.com.64531: . 9019496:9020864(1368) ack 179 win 1716 13:31:44.702719 IP databus.avidyne.com.64531 > manna.mozilla.org.http: . ack 8957936 win 32832 13:31:44.710200 IP manna.mozilla.org.http > databus.avidyne.com.64531: . 9020864:9022232(1368) ack 179 win 1716 13:31:44.710215 IP databus.avidyne.com.64531 > manna.mozilla.org.http: . ack 8957936 win 32832 13:31:44.719444 IP manna.mozilla.org.http > databus.avidyne.com.64531: . 9022232:9023600(1368) ack 179 win 1716 13:31:44.719462 IP databus.avidyne.com.64531 > manna.mozilla.org.http: . ack 8957936 win 32832 13:31:44.727065 IP manna.mozilla.org.http > databus.avidyne.com.64531: . 8957936:8959304(1368) ack 179 win 1716 13:31:44.727089 IP databus.avidyne.com.64531 > manna.mozilla.org.http: . ack 9023600 win 0 13:31:44.727146 IP databus.avidyne.com.64531 > manna.mozilla.org.http: . ack 9023600 win 1680 13:31:44.727181 IP databus.avidyne.com.64531 > manna.mozilla.org.http: . ack 9023600 win 3216 13:31:44.727275 IP databus.avidyne.com.64531 > manna.mozilla.org.http: . ack 9023600 win 4752 13:31:44.727295 IP databus.avidyne.com.64531 > manna.mozilla.org.http: . ack 9023600 win 6288 13:31:44.727342 IP databus.avidyne.com.64531 > manna.mozilla.org.http: . ack 9023600 win 7824 13:31:44.727375 IP databus.avidyne.com.64531 > manna.mozilla.org.http: . ack 9023600 win 9360 13:31:44.727492 IP databus.avidyne.com.64531 > manna.mozilla.org.http: . ack 9023600 win 10896 13:31:44.727513 IP databus.avidyne.com.64531 > manna.mozilla.org.http: . ack 9023600 win 12432 13:31:44.727565 IP databus.avidyne.com.64531 > manna.mozilla.org.http: . ack 9023600 win 15504 13:31:44.727632 IP databus.avidyne.com.64531 > manna.mozilla.org.http: . ack 9023600 win 17040 13:31:44.727653 IP databus.avidyne.com.64531 > manna.mozilla.org.http: . ack 9023600 win 18576 13:31:44.727701 IP databus.avidyne.com.64531 > manna.mozilla.org.http: . ack 9023600 win 20112 13:31:44.727780 IP databus.avidyne.com.64531 > manna.mozilla.org.http: . ack 9023600 win 21648 13:31:44.727870 IP databus.avidyne.com.64531 > manna.mozilla.org.http: . ack 9023600 win 23184 13:31:44.727889 IP databus.avidyne.com.64531 > manna.mozilla.org.http: . ack 9023600 win 24720 13:31:44.727920 IP databus.avidyne.com.64531 > manna.mozilla.org.http: . ack 9023600 win 26256 13:31:44.727982 IP databus.avidyne.com.64531 > manna.mozilla.org.http: . ack 9023600 win 27792 13:31:44.728034 IP databus.avidyne.com.64531 > manna.mozilla.org.http: . ack 9023600 win 29328 13:31:44.728053 IP databus.avidyne.com.64531 > manna.mozilla.org.http: . ack 9023600 win 30864 13:31:44.728217 IP databus.avidyne.com.64531 > manna.mozilla.org.http: . ack 9023600 win 32400 From owner-freebsd-stable@FreeBSD.ORG Wed Jul 5 20:56:12 2006 Return-Path: X-Original-To: stable@FreeBSD.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2D0CD16A4DA for ; Wed, 5 Jul 2006 20:56:12 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from pi.codefab.com (pi.codefab.com [199.103.21.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id BAA3843D49 for ; Wed, 5 Jul 2006 20:56:11 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from localhost (localhost [127.0.0.1]) by pi.codefab.com (Postfix) with ESMTP id 2ED9C5DB3; Wed, 5 Jul 2006 16:56:11 -0400 (EDT) X-Virus-Scanned: amavisd-new at codefab.com Received: from pi.codefab.com ([127.0.0.1]) by localhost (pi.codefab.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Lq-IUT7k+Gdr; Wed, 5 Jul 2006 16:56:10 -0400 (EDT) Received: from [199.103.21.238] (pan.codefab.com [199.103.21.238]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by pi.codefab.com (Postfix) with ESMTP id 1D7465C31; Wed, 5 Jul 2006 16:56:10 -0400 (EDT) In-Reply-To: References: <86C10E7655AA8C2D8C433AAC@[10.0.0.90]> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Charles Swiger Date: Wed, 5 Jul 2006 16:56:09 -0400 To: Justin T. Gibbs X-Mailer: Apple Mail (2.752.2) Cc: stable@FreeBSD.org Subject: Re: fetch hangs on AMD64 RELENG_6 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Jul 2006 20:56:12 -0000 On Jul 5, 2006, at 4:22 PM, Justin T. Gibbs wrote: > Hmm. Seems we close the window unexpectedly and the remote side > doesn't > retransmit when we open it. Yes, interesting that. :-) Normally the stack only sets the window size to 0 in the event of severe congestion, it's used to tell the other side to stop sending traffic for an interval, although the other side should retry with zero-data-length ACK-only packets after a delay, or once your side sends a packet opening the window. > FreeBSD's acks stop once the window is fully > open... aren't the acks supposed to retried longer? If not, shouldn't > fetch eventually see a socket close event instead of hanging forever? RFC-793 says: "The sending TCP must be prepared to accept from the user and send at least one octet of new data even if the send window is zero. The sending TCP must regularly retransmit to the receiving TCP even when the window is zero. Two minutes is recommended for the retransmission interval when the window is zero. This retransmission is essential to guarantee that when either TCP has a zero window the re-opening of the window will be reliably reported to the other. When the receiving TCP has a zero window and a segment arrives it must still send an acknowledgment showing its next expected sequence number and current window (zero)." The fact that you aren't seeing any ACK's back from this remote server suggests that perhaps a stateful firewall is involved which is getting confused and/or dropping the state entry once it sees the zero-window-size packet from your machine. There may be something wrong on the FreeBSD side as well, of course-- the fact that it grows the window by sending nearly twenty or more ACK packets in the span of about one millisecond without waiting for any ACKs from the other side is pretty wacky in it's own right. -- -Chuck From owner-freebsd-stable@FreeBSD.ORG Wed Jul 5 21:45:40 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0587D16A4DD for ; Wed, 5 Jul 2006 21:45:40 +0000 (UTC) (envelope-from lists@stringsutils.com) Received: from zoraida.natserv.net (p65-147.acedsl.com [66.114.65.147]) by mx1.FreeBSD.org (Postfix) with ESMTP id 92AD943D45 for ; Wed, 5 Jul 2006 21:45:38 +0000 (GMT) (envelope-from lists@stringsutils.com) Received: from zoraida.natserv.net (localhost.natserv.net [127.0.0.1]) by zoraida.natserv.net (Postfix) with ESMTP id 51C03B833; Wed, 5 Jul 2006 17:45:36 -0400 (EDT) X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on zoraida.natserv.net X-Spam-Level: X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=failed version=3.1.3 Received: from zoraida.natserv.net (zoraida.natserv.net [66.114.65.147]) by zoraida.natserv.net (Postfix) with ESMTP id 0D6FBB822; Wed, 5 Jul 2006 17:45:36 -0400 (EDT) References: <20060704092127.GA55167@lpthe.jussieu.fr> <44AABBD9.4000603@samsco.org> Message-ID: X-Mailer: http://www.courier-mta.org/cone/ From: Francisco Reyes To: Scott Long Date: Wed, 05 Jul 2006 17:45:35 -0400 Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset="US-ASCII" Content-Disposition: inline Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Cc: freebsd-stable@freebsd.org, Michel Talon Subject: Re: NFS Locking Issue X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Jul 2006 21:45:40 -0000 Scott Long writes: > For what it's worth, I recently spent a lot of time putting FreeBSD 6.1 > to the test as both an NFS client and server in a mixed OS environment. I have a few debugging settings/suggestions that have been sent my way and I plan to try them tonight, but this is just another report.. FreeBSD only environment. Today after hours going crazy with horrible performance I brought down nfsd and brought it back up.. that simple process got vmstat 'b' column down and everything was back to normal. Again this will not help anyone troubleshoot, but just to mention that it happens even with a FreeBSD only environment. From owner-freebsd-stable@FreeBSD.ORG Wed Jul 5 21:53:51 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0D86516A4DF; Wed, 5 Jul 2006 21:53:51 +0000 (UTC) (envelope-from lists@stringsutils.com) Received: from zoraida.natserv.net (p65-147.acedsl.com [66.114.65.147]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4D29343D69; Wed, 5 Jul 2006 21:53:42 +0000 (GMT) (envelope-from lists@stringsutils.com) Received: from zoraida.natserv.net (localhost.natserv.net [127.0.0.1]) by zoraida.natserv.net (Postfix) with ESMTP id 78925B833; Wed, 5 Jul 2006 17:53:40 -0400 (EDT) X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on zoraida.natserv.net X-Spam-Level: X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=failed version=3.1.3 Received: from zoraida.natserv.net (zoraida.natserv.net [66.114.65.147]) by zoraida.natserv.net (Postfix) with ESMTP id 25A51B822; Wed, 5 Jul 2006 17:53:40 -0400 (EDT) References: <20060705100403.Y80381@fledge.watson.org> Message-ID: X-Mailer: http://www.courier-mta.org/cone/ From: Francisco Reyes To: Robert Watson Date: Wed, 05 Jul 2006 17:53:39 -0400 Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset="US-ASCII" Content-Disposition: inline Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Cc: freebsd-stable@freebsd.org, Michel Talon Subject: Re: NFS Locking Issue X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Jul 2006 21:53:51 -0000 Robert Watson writes: > can you trigger it using work on just one client against a server, without > client<->client interactions? This makes tracking and reproduction a lot > easier Personally I am experiencing two problems. 1- NFS clients freeze/hang if the server goes away. We have clients with several mounts so if one of the servers dies then the entire operation of the client is put in jeopardy. This I can reproduce every single time with a 6.X client.. with both a 5.X and a 6.X server. "umount -f" hangs too. > as multi-client test cases are really tricky! The second case only happens under heavy load and restarting nfsd makes it go away. Basically 'b' column in vmstat goes high and the performnance of the machine falls to the floor. Going to try http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneld ebug-deadlocks.html And reading up on how to debug with DDB. Have another user who volunteered to give me some pointers.. so will try that.. so I am able to actually produce more helpfull info. From owner-freebsd-stable@FreeBSD.ORG Wed Jul 5 22:02:39 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C677A16A4E7; Wed, 5 Jul 2006 22:02:39 +0000 (UTC) (envelope-from lists@stringsutils.com) Received: from zoraida.natserv.net (p65-147.acedsl.com [66.114.65.147]) by mx1.FreeBSD.org (Postfix) with ESMTP id 59EFF43D45; Wed, 5 Jul 2006 22:02:39 +0000 (GMT) (envelope-from lists@stringsutils.com) Received: from zoraida.natserv.net (localhost.natserv.net [127.0.0.1]) by zoraida.natserv.net (Postfix) with ESMTP id BDD2DB838; Wed, 5 Jul 2006 18:02:36 -0400 (EDT) X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on zoraida.natserv.net X-Spam-Level: X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=failed version=3.1.3 Received: from zoraida.natserv.net (zoraida.natserv.net [66.114.65.147]) by zoraida.natserv.net (Postfix) with ESMTP id 8103CB822; Wed, 5 Jul 2006 18:02:36 -0400 (EDT) References: <20060705100403.Y80381@fledge.watson.org> <20060705113822.GM37822@deviant.kiev.zoral.com.ua> <20060705122040.GN37822@deviant.kiev.zoral.com.ua> <20060705140225.X18236@fledge.watson.org> Message-ID: X-Mailer: http://www.courier-mta.org/cone/ From: Francisco Reyes To: Robert Watson Date: Wed, 05 Jul 2006 18:02:36 -0400 Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset="US-ASCII" Content-Disposition: inline Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Cc: Kostik Belousov , freebsd-stable@freebsd.org Subject: Re: NFS Locking Issue X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Jul 2006 22:02:39 -0000 Robert Watson writes: > It's not impossible. It would be interesting to see if ps axl reports that > rpc.lockd is in the kqread state, which would suggest it was blocked in the > resolver. Just tried "ps axl | grep rpc" in the machine giving us the most grief.. Only got one line back: root 367 0.0 0.0 1368 960 ?? Ss 25Jun06 0:05.52 /usr/sbin/rpcbin 0 1 0 4 0 select Is that what one of the lines I should keep an eye, next time the machine is locked up? From owner-freebsd-stable@FreeBSD.ORG Wed Jul 5 22:10:23 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3870B16A504; Wed, 5 Jul 2006 22:10:23 +0000 (UTC) (envelope-from lists@stringsutils.com) Received: from zoraida.natserv.net (p65-147.acedsl.com [66.114.65.147]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9BE6543D8C; Wed, 5 Jul 2006 22:10:15 +0000 (GMT) (envelope-from lists@stringsutils.com) Received: from zoraida.natserv.net (localhost.natserv.net [127.0.0.1]) by zoraida.natserv.net (Postfix) with ESMTP id 5B175B833; Wed, 5 Jul 2006 18:10:05 -0400 (EDT) X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on zoraida.natserv.net X-Spam-Level: X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=failed version=3.1.3 Received: from zoraida.natserv.net (zoraida.natserv.net [66.114.65.147]) by zoraida.natserv.net (Postfix) with ESMTP id 0DF50B822; Wed, 5 Jul 2006 18:10:05 -0400 (EDT) References: <20060705100403.Y80381@fledge.watson.org> <20060705113822.GM37822@deviant.kiev.zoral.com.ua> <20060705122040.GN37822@deviant.kiev.zoral.com.ua> <20060705140225.X18236@fledge.watson.org> Message-ID: X-Mailer: http://www.courier-mta.org/cone/ From: Francisco Reyes To: Robert Watson Date: Wed, 05 Jul 2006 18:10:04 -0400 Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset="US-ASCII" Content-Disposition: inline Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Cc: Kostik Belousov , freebsd-stable@freebsd.org, Michel Talon Subject: Re: NFS Locking Issue X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Jul 2006 22:10:23 -0000 Robert Watson writes: > It's not impossible. It would be interesting to see if ps axl reports that > rpc.lockd is in the kqread state Found my post in another thread. 0 354 1 0 96 0 1412 1032 select Ss ?? 0:07.06 /usr/sbin/rpcbind It was not in kqread state.. and that was from a point where the machine was totally locked up.. had to do a physical reset.. could not even kill nfsd that time. I had also more output from several different ps. You need to do "view more" to see them all. http://tinyurl.com/kpejr From owner-freebsd-stable@FreeBSD.ORG Wed Jul 5 22:33:38 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C08A116A4E1; Wed, 5 Jul 2006 22:33:38 +0000 (UTC) (envelope-from lists@stringsutils.com) Received: from zoraida.natserv.net (p65-147.acedsl.com [66.114.65.147]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2576243D5F; Wed, 5 Jul 2006 22:33:36 +0000 (GMT) (envelope-from lists@stringsutils.com) Received: from zoraida.natserv.net (localhost.natserv.net [127.0.0.1]) by zoraida.natserv.net (Postfix) with ESMTP id CF595B833; Wed, 5 Jul 2006 18:33:32 -0400 (EDT) X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on zoraida.natserv.net X-Spam-Level: X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=failed version=3.1.3 Received: from zoraida.natserv.net (zoraida.natserv.net [66.114.65.147]) by zoraida.natserv.net (Postfix) with ESMTP id 7EF8CB822; Wed, 5 Jul 2006 18:33:32 -0400 (EDT) References: <20060705100403.Y80381@fledge.watson.org> <20060705114848.F1103@ganymede.hub.org> Message-ID: X-Mailer: http://www.courier-mta.org/cone/ From: Francisco Reyes To: User Freebsd Date: Wed, 05 Jul 2006 18:33:32 -0400 Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset="US-ASCII" Content-Disposition: inline Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Cc: freebsd-stable@freebsd.org, Robert Watson , Michel Talon Subject: Re: NFS Locking Issue X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Jul 2006 22:33:38 -0000 User Freebsd writes: > I believe, in Francisco's case, they are willing to pay someone to fix the > NFS issues they are having, which, i'd assume, means easy access to the > problematic server(s) to do proper testing in a "real life scenario" ... Correct. As long as the person is someone "trusted in the community" we could do that. And yes we are willing to come to some agreement for compensation for the help. Needless to say our introduction of new machines will go through a more rigourous test in the future.. specially when jumping to a new Release number in FreeBSD. We lost 1 big customer and after today we likely will loose 2 or 3 more.. of the big ones.. when it's all said and done we are likely to loose several thousand dollars/month due to this 6.X incidents. We are fairly new to NFS and that's why we were hoping to get someone to help us.. or at least point us in the right direction. I plan to go over the link you sent me and try to prepare at least one machine. As for paying someone, yes we have been actively looking for someone to help us since we are relatively new to NFS.. and much more newer to troubleshooting this type of prolbems From owner-freebsd-stable@FreeBSD.ORG Wed Jul 5 22:49:14 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 80D3E16A4DA for ; Wed, 5 Jul 2006 22:49:14 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 23E7843D45 for ; Wed, 5 Jul 2006 22:49:14 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id C700646C52; Wed, 5 Jul 2006 18:49:13 -0400 (EDT) Date: Wed, 5 Jul 2006 23:49:13 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Francisco Reyes In-Reply-To: Message-ID: <20060705234514.I70011@fledge.watson.org> References: <20060705100403.Y80381@fledge.watson.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org, Michel Talon Subject: Re: NFS Locking Issue X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Jul 2006 22:49:14 -0000 On Wed, 5 Jul 2006, Francisco Reyes wrote: >> can you trigger it using work on just one client against a server, without >> client<->client interactions? This makes tracking and reproduction a lot >> easier > > Personally I am experiencing two problems. > 1- NFS clients freeze/hang if the server goes away. > We have clients with several mounts so if one of the servers dies then the > entire operation of the client is put in jeopardy. > > This I can reproduce every single time with a 6.X client.. with both a 5.X > and a 6.X server. > > "umount -f" hangs too. The problems you are experiencing are almost certainly not related to rpc.lockd, rather, bugs in the NFS client. Let's just look at the normal use hang for now, and revisit umount -f after that. >> as multi-client test cases are really tricky! > > The second case only happens under heavy load and restarting nfsd makes it > go away. Basically 'b' column in vmstat goes high and the performnance of > the machine falls to the floor. > > Going to try > http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneld > ebug-deadlocks.html > > And reading up on how to debug with DDB. Have another user who volunteered > to give me some pointers.. so will try that.. so I am able to actually > produce more helpfull info. If you can get into DDB when the hang has occurred, output via serial console for the following commands would be very helpful: show pcpu show allpcpu ps trace traceall show locks show alllocks show uma show malloc show lockedvnods Note that the last two will only work if you compile WITNESS in -- WITNESS significantly changes kernel timing, so you may find it closes whatever race you're running into. If you can reproduce the problem with WITNESS and INVARIANTS, that would be very useful. The above output will hopefully tell us the basic state of the system with respect to processes, threads, locking, and so on, and may help us track things down. For the above, you definitely want a serial console as it will be quite a bit of output. Also, can you send the output of the 'mount' command from the un-hung state? I notice a lot of threads stuck in 'ufs'. Finally, during the above, if you could disable background file system checking by placing the following in /etc/rc.conf: background_fsck="NO" And boot to single user mode, doing a full fsck -p before booting up, in order to make sure the file system is in a good state before beginning. Robert N M Watson Computer Laboratory University of Cambridge From owner-freebsd-stable@FreeBSD.ORG Wed Jul 5 22:50:20 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E178016A4F5 for ; Wed, 5 Jul 2006 22:50:20 +0000 (UTC) (envelope-from lists@stringsutils.com) Received: from zoraida.natserv.net (p65-147.acedsl.com [66.114.65.147]) by mx1.FreeBSD.org (Postfix) with ESMTP id 20B6443D92 for ; Wed, 5 Jul 2006 22:50:06 +0000 (GMT) (envelope-from lists@stringsutils.com) Received: from zoraida.natserv.net (localhost.natserv.net [127.0.0.1]) by zoraida.natserv.net (Postfix) with ESMTP id 0576AB833; Wed, 5 Jul 2006 18:50:01 -0400 (EDT) X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on zoraida.natserv.net X-Spam-Level: X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=failed version=3.1.3 Received: from zoraida.natserv.net (zoraida.natserv.net [66.114.65.147]) by zoraida.natserv.net (Postfix) with ESMTP id D6B1AB822; Wed, 5 Jul 2006 18:50:00 -0400 (EDT) References: <20060705133329.GA65123@lpthe.jussieu.fr> <20060705144809.F1171@ganymede.hub.org> Message-ID: X-Mailer: http://www.courier-mta.org/cone/ From: Francisco Reyes To: User Freebsd Date: Wed, 05 Jul 2006 18:50:00 -0400 Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset="US-ASCII" Content-Disposition: inline Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Cc: freebsd-stable@freebsd.org, Michel Talon Subject: Re: NFS Locking Issue X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Jul 2006 22:50:21 -0000 User Freebsd writes: > What are others using for ethernet? Of our two machines having the problem 1 has BGE and the other one has EM (Intel). Doesn't seem to make much of a difference. Except for the network cards, these two machines are identical. Same motherboard, same RAID controller, same amount of RAM, same RAID configuration... From owner-freebsd-stable@FreeBSD.ORG Thu Jul 6 00:02:10 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0364616A4DA for ; Thu, 6 Jul 2006 00:02:10 +0000 (UTC) (envelope-from vyeperman@gmail.com) Received: from wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.235]) by mx1.FreeBSD.org (Postfix) with ESMTP id 221A043D49 for ; Thu, 6 Jul 2006 00:02:08 +0000 (GMT) (envelope-from vyeperman@gmail.com) Received: by wr-out-0506.google.com with SMTP id 58so1224342wri for ; Wed, 05 Jul 2006 17:02:08 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=eS9V2/YwUxe5F/WOEE5gNSwAm/w+qaH56IKX2sTArW2ckLqz0HOc2/CbmaDi/Z2Z6JNMEWA0+84UCIe+/xnOoTmIlo6yECZIulY1FcmtrZPXyz12zIEAaz50xo48lSYreI4lbd6u3uH4cFC5hUwC/rO339njWUOZCbliXIuyNm4= Received: by 10.64.83.17 with SMTP id g17mr25278qbb; Wed, 05 Jul 2006 17:02:08 -0700 (PDT) Received: by 10.65.181.16 with HTTP; Wed, 5 Jul 2006 17:02:08 -0700 (PDT) Message-ID: <6c3c36d00607051702l178c1cb1he58749c03725c1ac@mail.gmail.com> Date: Wed, 5 Jul 2006 17:02:08 -0700 From: "Vye Wilson" To: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: 0.0% user, 0.0% nice, 0.0% system, 53.8% interrupt, 46.2% idle - Unusual interrupt use? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Jul 2006 00:02:10 -0000 Recently I've had an unusually high amount of 'interrupt' cpu usage. I stopped all my jails so the box is for the most part idle. Here is my uname: FreeBSD Natsume.wow.com 6.1-STABLE FreeBSD 6.1-STABLE #3: Tue Jul 4 22:14:02 UTC 2006 vye@Natsume.wow.com:/usr/obj/usr/src/sys/NATSUME i386 Here is my top output: last pid: 674; load averages: 0.00, 0.00, 0.00 up 0+00:32:49 16:51:02 19 processes: 1 running, 18 sleeping CPU states: 0.0% user, 0.0% nice, 0.0% system, 53.8% interrupt, 46.2%idle Mem: 5332K Active, 3984K Inact, 20M Wired, 9056K Buf, 967M Free Swap: 2022M Total, 2022M Free PID USERNAME THR PRI NICE SIZE RES STATE TIME WCPU COMMAND 666 root 1 4 0 6116K 3096K sbwait 0:00 0.00% sshd 674 root 1 -64 0 2288K 1560K RUN 0:00 0.00% top 670 vye 1 8 0 3188K 1992K wait 0:00 0.00% bash 672 vye 1 8 0 1684K 1332K wait 0:00 0.00% su 312 root 1 96 0 1344K 988K select 0:00 0.00% syslogd 673 root 1 8 0 3184K 2068K wait 0:00 0.00% bash 669 vye 1 96 0 6100K 3128K select 0:00 0.00% sshd 463 root 1 8 0 1356K 1116K nanslp 0:00 0.00% cron 594 root 1 5 0 1312K 944K ttyin 0:00 0.00% getty 599 root 1 5 0 1312K 944K ttyin 0:00 0.00% getty 593 root 1 5 0 1312K 944K ttyin 0:00 0.00% getty 597 root 1 5 0 1312K 944K ttyin 0:00 0.00% getty 592 root 1 5 0 1312K 944K ttyin 0:00 0.00% getty 595 root 1 5 0 1312K 944K ttyin 0:00 0.00% getty 596 root 1 5 0 1312K 944K ttyin 0:00 0.00% getty 598 root 1 5 0 1312K 944K ttyin 0:00 0.00% getty 450 root 1 96 0 3400K 2556K select 0:00 0.00% sshd 390 root 1 96 0 1256K 832K select 0:00 0.00% usbd 283 root 1 108 0 516K 376K select 0:00 0.00% devd After taking a look at dmesg I'm not sure if I just now noticed this or if it has recently started doing this: unknown: can't assign resources (memory) unknown: can't assign resources (port) unknown: can't assign resources (port) unknown: can't assign resources (port) unknown: can't assign resources (port) unknown: can't assign resources (port) unknown: can't assign resources (irq) Full dmesg output: Copyright (c) 1992-2006 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 6.1-STABLE #3: Tue Jul 4 22:14:02 UTC 2006 vye@Natsume.wow.com:/usr/obj/usr/src/sys/NATSUME Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) 4 CPU 2.40GHz (2392.05-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf27 Stepping = 7 Features=0xbfebfbff Features2=0x400 real memory = 1073479680 (1023 MB) avail memory = 1041547264 (993 MB) MPTable: ioapic0: Assuming intbase of 0 ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 cpu0 on motherboard pcib0: pcibus 0 on motherboard pci0: on pcib0 pcib0: unable to route slot 31 INTC agp0: mem 0xf8000000-0xfbffffff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pcib2: at device 30.0 on pci0 pci2: on pcib2 3ware device driver for 9000 series storage controllers, version: 3.60.02.012 twa0: <3ware 9000 series Storage Controller> port 0xd400-0xd4ff mem 0xfeaffc00-0xfeaffcff,0xf3800000-0xf3ffffff irq 21 at device 9.0 on pci2 twa0: [GIANT-LOCKED] twa0: INFO: (0x15: 0x1300): Controller details:: Model 9500S-12, 12 ports, Firmware FE9X 2.06.00.009, BIOS BE9X 2.03.01.051 pcib3: at device 11.0 on pci2 pci3: on pcib3 pci3: at device 8.0 (no driver attached) fwohci0: mem 0xfc8fe000-0xfc8fefff irq 17 at device 9.0on pci3 fwohci0: OHCI version 1.0 (ROM=1) fwohci0: No. of Isochronous channels is 8. fwohci0: EUI64 00:08:d3:f0:00:00:01:09 fwohci0: Phy 1394a available S400, 3 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: on fwohci0 fwe0: on firewire0 if_fwe0: Fake Ethernet address: 02:08:d3:00:01:09 fwe0: Ethernet address: 02:08:d3:00:01:09 fwe0: if_start running deferred for Giant sbp0: on firewire0 fwohci0: Initiate bus reset fwohci0: node_id=0xc800ffc0, gen=1, CYCLEMASTER mode firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me) firewire0: bus manager 0 (me) fxp0: port 0xdf00-0xdf3f mem 0xfeacf000-0xfeacffff,0xfea80000-0xfea9ffff irq 18 at device 12.0 on pci2 miibus0: on fxp0 inphy0: on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp0: Ethernet address: 00:07:e9:d4:a4:f8 fxp1: port 0xde80-0xdebf mem 0xfeace000-0xfeacefff,0xfea40000-0xfea5ffff irq 19 at device 13.0 on pci2 miibus1: on fxp1 inphy1: on miibus1 inphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp1: Ethernet address: 00:07:e9:d4:a4:fa pci2: at device 15.0 (no driver attached) isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at device 31.1 on pci0 ata0: on atapci0 ata1: on atapci0 uhci0: port 0xef40-0xef5f irq 19 at device 31.2 on pci0 uhci0: [GIANT-LOCKED] usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered pci0: at device 31.3 (no driver attached) uhci1: port 0xef80-0xef9f irq 10 at device 31.4 on pci0 uhci1: [GIANT-LOCKED] usb1: on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered pmtimer0 on isa0 orm0: at iomem 0xc0000-0xc7fff,0xc8000-0xc8fff,0xc9000-0xca7ff,0xca800-0xcb7ff,0xcb800-0xcc7ff on isa0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model IntelliMouse, device ID 3 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode ppbus0: on ppc0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 unknown: can't assign resources (memory) unknown: can't assign resources (port) unknown: can't assign resources (port) unknown: can't assign resources (port) unknown: can't assign resources (port) unknown: can't assign resources (port) unknown: can't assign resources (irq) Timecounter "TSC" frequency 2392047584 Hz quality 800 Timecounters tick every 1.000 msec ad2: 76319MB at ata1-master UDMA100 ad3: 114473MB at ata1-slave UDMA100 da0 at twa0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-3 device da0: 100.000MB/s transfers da0: 858276MB (1757749248 512 byte sectors: 255H 63S/T 109414C) Trying to mount root from ufs:/dev/ad2s1a I'm really not sure how to go about troubleshooting this issue. Can someone point me in the right direction? Thanks in advance. -- --Vye From owner-freebsd-stable@FreeBSD.ORG Thu Jul 6 00:08:29 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A825E16A4E0 for ; Thu, 6 Jul 2006 00:08:29 +0000 (UTC) (envelope-from max@love2party.net) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.187]) by mx1.FreeBSD.org (Postfix) with ESMTP id 02E2543D46 for ; Thu, 6 Jul 2006 00:08:28 +0000 (GMT) (envelope-from max@love2party.net) Received: from [88.64.180.221] (helo=amd64.laiers.local) by mrelayeu.kundenserver.de (node=mrelayeu6) with ESMTP (Nemesis), id 0ML29c-1FyHPv3js8-0003G5; Thu, 06 Jul 2006 02:08:28 +0200 From: Max Laier Organization: FreeBSD To: "Vye Wilson" Date: Thu, 6 Jul 2006 02:08:20 +0200 User-Agent: KMail/1.9.1 References: <6c3c36d00607051702l178c1cb1he58749c03725c1ac@mail.gmail.com> In-Reply-To: <6c3c36d00607051702l178c1cb1he58749c03725c1ac@mail.gmail.com> X-Face: ,,8R(x[kmU]tKN@>gtH1yQE4aslGdu+2]; R]*pL,U>^H?)gW@49@wdJ`H<=?utf-8?q?=25=7D*=5FBD=0A=09U=5For=3D=5CmOZf764=26nYj=3DJYbR1PW0ud?=>|!~,,CPC.1-D$FG@0h3#'5"k{V]a~.<=?utf-8?q?mZ=7D44=23Se=7Em=0A=09Fe=7E=5C=5DX5B=5D=5Fxj?=(ykz9QKMw_l0C2AQ]}Ym8)fU MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart2214946.HOJPf43YFo"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200607060208.26315.max@love2party.net> X-Provags-ID: kundenserver.de abuse@kundenserver.de login:61c499deaeeba3ba5be80f48ecc83056 Cc: freebsd-stable@freebsd.org Subject: Re: 0.0% user, 0.0% nice, 0.0% system, 53.8% interrupt, 46.2% idle - Unusual interrupt use? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Jul 2006 00:08:29 -0000 --nextPart2214946.HOJPf43YFo Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Thursday 06 July 2006 02:02, Vye Wilson wrote: > I'm really not sure how to go about troubleshooting this issue. Can someo= ne > point me in the right direction? "vmstat -i" should give a good idea what is causing the interrupt load. =2D-=20 /"\ Best regards, | mlaier@freebsd.org \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | mlaier@EFnet / \ ASCII Ribbon Campaign | Against HTML Mail and News --nextPart2214946.HOJPf43YFo Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQBErFR6XyyEoT62BG0RAiBoAJ9iJ2fjG7ongL6Ss4N1o2hOioajKwCeIJD4 wAnaVvap6XwS05aLu8bOubk= =+mdO -----END PGP SIGNATURE----- --nextPart2214946.HOJPf43YFo-- From owner-freebsd-stable@FreeBSD.ORG Thu Jul 6 00:08:31 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 440CC16A4DA for ; Thu, 6 Jul 2006 00:08:31 +0000 (UTC) (envelope-from killing@multiplay.co.uk) Received: from multiplay.co.uk (core6.multiplay.co.uk [85.236.96.23]) by mx1.FreeBSD.org (Postfix) with ESMTP id A318D43D46 for ; Thu, 6 Jul 2006 00:08:30 +0000 (GMT) (envelope-from killing@multiplay.co.uk) Received: from vader ([212.135.219.179]) by multiplay.co.uk (multiplay.co.uk [85.236.96.23]) (MDaemon PRO v9.0.1) with ESMTP id md50002732675.msg for ; Thu, 06 Jul 2006 01:08:28 +0100 Message-ID: <11d501c6a090$3bedc1d0$b3db87d4@multiplay.co.uk> From: "Steven Hartland" To: "Vye Wilson" , References: <6c3c36d00607051702l178c1cb1he58749c03725c1ac@mail.gmail.com> Date: Thu, 6 Jul 2006 01:07:50 +0100 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2869 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869 X-Spam-Processed: multiplay.co.uk, Thu, 06 Jul 2006 01:08:28 +0100 (not processed: message from valid local sender) X-MDRemoteIP: 212.135.219.179 X-Return-Path: killing@multiplay.co.uk X-MDaemon-Deliver-To: freebsd-stable@freebsd.org X-MDAV-Processed: multiplay.co.uk, Thu, 06 Jul 2006 01:08:30 +0100 Cc: Subject: Re: 0.0% user, 0.0% nice, 0.0% system, 53.8% interrupt, 46.2% idle - Unusual interrupt use? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Jul 2006 00:08:31 -0000 "vmstat -i" and "systat" will be useful at identifying what is causing the interupts. Vye Wilson wrote: > Recently I've had an unusually high amount of 'interrupt' cpu usage. I > stopped all my jails so the box is for the most part idle. Steve ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmaster@multiplay.co.uk. From owner-freebsd-stable@FreeBSD.ORG Thu Jul 6 00:17:04 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DD28116A4DA for ; Thu, 6 Jul 2006 00:17:04 +0000 (UTC) (envelope-from vyeperman@gmail.com) Received: from wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.239]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4E02D43D45 for ; Thu, 6 Jul 2006 00:17:04 +0000 (GMT) (envelope-from vyeperman@gmail.com) Received: by wr-out-0506.google.com with SMTP id 58so1226157wri for ; Wed, 05 Jul 2006 17:17:03 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=VyYTHkwJXWDsCe4t6KOEppgZQZgoEZvsU9QCoYFZQyINlok5c1P456plkvtuE65XFCrK7Y4MWfCCsAR7Pc/PbcJ60FNT7Gv0pw/PVibAfTS+Jn4+BHbUZt8tlVN6xgEmqHB2iL3smxLoxHm0eyKbbWYE2Xl/EAamT2oeGd4espw= Received: by 10.65.114.19 with SMTP id r19mr31324qbm; Wed, 05 Jul 2006 17:17:03 -0700 (PDT) Received: by 10.65.181.16 with HTTP; Wed, 5 Jul 2006 17:17:03 -0700 (PDT) Message-ID: <6c3c36d00607051717t5aa6ed1dl3595c11b3b769561@mail.gmail.com> Date: Wed, 5 Jul 2006 17:17:03 -0700 From: "Vye Wilson" To: freebsd-stable@freebsd.org In-Reply-To: <200607060208.26315.max@love2party.net> MIME-Version: 1.0 References: <6c3c36d00607051702l178c1cb1he58749c03725c1ac@mail.gmail.com> <200607060208.26315.max@love2party.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: 0.0% user, 0.0% nice, 0.0% system, 53.8% interrupt, 46.2% idle - Unusual interrupt use? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Jul 2006 00:17:04 -0000 # vmstat -i interrupt total rate irq1: atkbd0 5 0 irq6: fdc0 3 0 irq10: uhci1 915633230 262810 irq15: ata1 1306 0 irq17: fwohci0 1 0 irq18: fxp0 2876 0 irq21: twa0 153 0 cpu0: timer 6964974 1999 Total 922602548 264811 # systat /0 /1 /2 /3 /4 /5 /6 /7 /8 /9 /10 Load Average /0 /10 /20 /30 /40 /50 /60 /70 /80 /90 /100 root irq10: uhc XXXXXXXXXXXXXXXXX root idle XXXXXXXXXXXXXXXXX XXXXXXXXXXXXXXXX So would irq10 be the culprit? If so where do I go from here? On 7/5/06, Max Laier wrote: > > On Thursday 06 July 2006 02:02, Vye Wilson wrote: > > I'm really not sure how to go about troubleshooting this issue. Can > someone > > point me in the right direction? > > "vmstat -i" should give a good idea what is causing the interrupt load. > > -- > /"\ Best regards, | mlaier@freebsd.org > \ / Max Laier | ICQ #67774661 > X http://pf4freebsd.love2party.net/ | mlaier@EFnet > / \ ASCII Ribbon Campaign | Against HTML Mail and News > > > -- --Vye From owner-freebsd-stable@FreeBSD.ORG Thu Jul 6 00:33:43 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4D02416A4DF for ; Thu, 6 Jul 2006 00:33:43 +0000 (UTC) (envelope-from freebsd@hub.org) Received: from hub.org (hub.org [200.46.204.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id C4D6E43D45 for ; Thu, 6 Jul 2006 00:33:42 +0000 (GMT) (envelope-from freebsd@hub.org) Received: from localhost (wm.hub.org [200.46.204.128]) by hub.org (Postfix) with ESMTP id 2AA1E290C2C; Wed, 5 Jul 2006 21:33:35 -0300 (ADT) Received: from hub.org ([200.46.204.220]) by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024) with ESMTP id 89094-01; Thu, 6 Jul 2006 00:33:40 +0000 (UTC) Received: from ganymede.hub.org (blk-7-151-244.eastlink.ca [71.7.151.244]) by hub.org (Postfix) with ESMTP id 9D646290C29; Wed, 5 Jul 2006 21:33:34 -0300 (ADT) Received: by ganymede.hub.org (Postfix, from userid 1027) id 0013D37EC9; Wed, 5 Jul 2006 21:33:40 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id EE36C3769F; Wed, 5 Jul 2006 21:33:40 -0300 (ADT) Date: Wed, 5 Jul 2006 21:33:40 -0300 (ADT) From: User Freebsd To: Francisco Reyes In-Reply-To: Message-ID: <20060705213223.U1171@ganymede.hub.org> References: <20060704092127.GA55167@lpthe.jussieu.fr> <44AABBD9.4000603@samsco.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org, Michel Talon Subject: Re: NFS Locking Issue X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Jul 2006 00:33:43 -0000 On Wed, 5 Jul 2006, Francisco Reyes wrote: > Scott Long writes: > >> For what it's worth, I recently spent a lot of time putting FreeBSD 6.1 >> to the test as both an NFS client and server in a mixed OS environment. > > I have a few debugging settings/suggestions that have been sent my way and I > plan to try them tonight, but this is just another report.. > > FreeBSD only environment. > Today after hours going crazy with horrible performance I brought down nfsd > and brought it back up.. that simple process got vmstat 'b' column down and > everything was back to normal. > > Again this will not help anyone troubleshoot, but just to mention that it > happens even with a FreeBSD only environment. 'k, to those out there that know what is useful, and what isn't ... If Francisco had DDB enabled, did a CTL-ALT-ESC when the above happens, and does a 'panic' to crash the server and dump a core ... can anything useful be gleamed from that core dump? ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . scrappy@hub.org MSN . scrappy@hub.org Yahoo . yscrappy Skype: hub.org ICQ . 7615664 From owner-freebsd-stable@FreeBSD.ORG Thu Jul 6 00:40:02 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0D60B16A4E0 for ; Thu, 6 Jul 2006 00:40:02 +0000 (UTC) (envelope-from killing@multiplay.co.uk) Received: from multiplay.co.uk (core6.multiplay.co.uk [85.236.96.23]) by mx1.FreeBSD.org (Postfix) with ESMTP id 22BE243D72 for ; Thu, 6 Jul 2006 00:39:54 +0000 (GMT) (envelope-from killing@multiplay.co.uk) Received: from vader ([212.135.219.179]) by multiplay.co.uk (multiplay.co.uk [85.236.96.23]) (MDaemon PRO v9.0.1) with ESMTP id md50002732799.msg for ; Thu, 06 Jul 2006 01:39:15 +0100 Message-ID: <126d01c6a094$8b03e4d0$b3db87d4@multiplay.co.uk> From: "Steven Hartland" To: "Vye Wilson" , References: <6c3c36d00607051702l178c1cb1he58749c03725c1ac@mail.gmail.com><200607060208.26315.max@love2party.net> <6c3c36d00607051717t5aa6ed1dl3595c11b3b769561@mail.gmail.com> Date: Thu, 6 Jul 2006 01:38:40 +0100 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2869 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869 X-Spam-Processed: multiplay.co.uk, Thu, 06 Jul 2006 01:39:15 +0100 (not processed: message from valid local sender) X-MDRemoteIP: 212.135.219.179 X-Return-Path: killing@multiplay.co.uk X-MDaemon-Deliver-To: freebsd-stable@freebsd.org X-MDAV-Processed: multiplay.co.uk, Thu, 06 Jul 2006 01:39:16 +0100 Cc: Subject: Re: 0.0% user, 0.0% nice, 0.0% system, 53.8% interrupt, 46.2% idle - Unusual interrupt use? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Jul 2006 00:40:02 -0000 Anything plugged into USB if so try removing it as uhci1 is clearly your issue. Vye Wilson wrote: > # vmstat -i > interrupt total rate > irq1: atkbd0 5 0 > irq6: fdc0 3 0 > irq10: uhci1 915633230 262810 > irq15: ata1 1306 0 > irq17: fwohci0 1 0 > irq18: fxp0 2876 0 > irq21: twa0 153 0 > cpu0: timer 6964974 1999 ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmaster@multiplay.co.uk. From owner-freebsd-stable@FreeBSD.ORG Thu Jul 6 00:40:05 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0C5F516A4E0 for ; Thu, 6 Jul 2006 00:40:04 +0000 (UTC) (envelope-from max@love2party.net) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.187]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4D45F43D46 for ; Thu, 6 Jul 2006 00:40:02 +0000 (GMT) (envelope-from max@love2party.net) Received: from [88.64.180.221] (helo=amd64.laiers.local) by mrelayeu.kundenserver.de (node=mrelayeu2) with ESMTP (Nemesis), id 0MKwtQ-1FyHuT1OGr-0001La; Thu, 06 Jul 2006 02:40:01 +0200 From: Max Laier Organization: FreeBSD To: freebsd-stable@freebsd.org Date: Thu, 6 Jul 2006 02:39:53 +0200 User-Agent: KMail/1.9.1 References: <6c3c36d00607051702l178c1cb1he58749c03725c1ac@mail.gmail.com> <200607060208.26315.max@love2party.net> <6c3c36d00607051717t5aa6ed1dl3595c11b3b769561@mail.gmail.com> In-Reply-To: <6c3c36d00607051717t5aa6ed1dl3595c11b3b769561@mail.gmail.com> X-Face: ,,8R(x[kmU]tKN@>gtH1yQE4aslGdu+2]; R]*pL,U>^H?)gW@49@wdJ`H<=?utf-8?q?=25=7D*=5FBD=0A=09U=5For=3D=5CmOZf764=26nYj=3DJYbR1PW0ud?=>|!~,,CPC.1-D$FG@0h3#'5"k{V]a~.<=?utf-8?q?mZ=7D44=23Se=7Em=0A=09Fe=7E=5C=5DX5B=5D=5Fxj?=(ykz9QKMw_l0C2AQ]}Ym8)fU MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart3424914.X2IQr1ie2G"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200607060240.00346.max@love2party.net> X-Provags-ID: kundenserver.de abuse@kundenserver.de login:61c499deaeeba3ba5be80f48ecc83056 Cc: Vye Wilson Subject: Re: 0.0% user, 0.0% nice, 0.0% system, 53.8% interrupt, 46.2% idle - Unusual interrupt use? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Jul 2006 00:40:05 -0000 --nextPart3424914.X2IQr1ie2G Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Thursday 06 July 2006 02:17, Vye Wilson wrote: > # vmstat -i > interrupt total rate > irq1: atkbd0 5 0 > irq6: fdc0 3 0 > irq10: uhci1 915633230 262810 > irq15: ata1 1306 0 > irq17: fwohci0 1 0 > irq18: fxp0 2876 0 > irq21: twa0 153 0 > cpu0: timer 6964974 1999 > Total 922602548 264811 Are you using usb on that box? If not, get rid of device uhci in your kern= el=20 config to see if that fixes it. If you are using usb - I have no idea. A= =20 BIOS upgrade might help. =2D-=20 /"\ Best regards, | mlaier@freebsd.org \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | mlaier@EFnet / \ ASCII Ribbon Campaign | Against HTML Mail and News --nextPart3424914.X2IQr1ie2G Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQBErFvgXyyEoT62BG0RAsJcAJ9tgcpqVDj3W9XDxiuz7wwgflUV6ACeMGhd zr7bwm7cNpGDG2aTy7mNCas= =sPLw -----END PGP SIGNATURE----- --nextPart3424914.X2IQr1ie2G-- From owner-freebsd-stable@FreeBSD.ORG Thu Jul 6 00:46:09 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 972CC16A4E0 for ; Thu, 6 Jul 2006 00:46:09 +0000 (UTC) (envelope-from LoN_Kamikaze@gmx.de) Received: from mail.gmx.net (mail.gmx.de [213.165.64.21]) by mx1.FreeBSD.org (Postfix) with SMTP id AC40143D4C for ; Thu, 6 Jul 2006 00:46:08 +0000 (GMT) (envelope-from LoN_Kamikaze@gmx.de) Received: (qmail invoked by alias); 06 Jul 2006 00:46:07 -0000 Received: from p54A7DBFD.dip.t-dialin.net (EHLO [192.168.0.12]) [84.167.219.253] by mail.gmx.net (mp029) with SMTP; 06 Jul 2006 02:46:07 +0200 X-Authenticated: #5465401 Message-ID: <44AC5D39.4010502@gmx.de> Date: Thu, 06 Jul 2006 02:45:45 +0200 From: "[LoN]Kamikaze" Organization: Lords of Nightmare User-Agent: Thunderbird 1.5.0.4 (X11/20060605) MIME-Version: 1.0 To: freebsd-stable@freebsd.org, freebsd-ports@freebsd.org X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 Cc: Subject: pkg_version confused by architecutre in package name X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Jul 2006 00:46:09 -0000 I normally run the command # pkg_version -Iv | grep \< before running 'portupgrade -a', to see what's going to happen. This time I got the following output: diablo-jdk-freebsd6.i386.1.5.0.07.00 < needs updating (index has 1.5.0.07.00) It seems that the tool is confused by the i386 in the package name. From owner-freebsd-stable@FreeBSD.ORG Thu Jul 6 01:10:16 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7986716A4E9; Thu, 6 Jul 2006 01:10:16 +0000 (UTC) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 058C943D53; Thu, 6 Jul 2006 01:10:15 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.13.0/8.13.0) with ESMTP id k661AFGi010667; Wed, 5 Jul 2006 18:10:15 -0700 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id k661AFip010666; Wed, 5 Jul 2006 18:10:15 -0700 Date: Wed, 5 Jul 2006 18:10:15 -0700 From: Brooks Davis To: "[LoN]Kamikaze" Message-ID: <20060706011015.GA6677@odin.ac.hmc.edu> References: <44AC5D39.4010502@gmx.de> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ZGiS0Q5IWpPtfppv" Content-Disposition: inline In-Reply-To: <44AC5D39.4010502@gmx.de> User-Agent: Mutt/1.4.1i X-Virus-Scanned: by amavisd-new Cc: freebsd-stable@freebsd.org, freebsd-ports@freebsd.org Subject: Re: pkg_version confused by architecutre in package name X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Jul 2006 01:10:16 -0000 --ZGiS0Q5IWpPtfppv Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jul 06, 2006 at 02:45:45AM +0200, [LoN]Kamikaze wrote: > I normally run the command > # pkg_version -Iv | grep \< > before running 'portupgrade -a', to see what's going to happen. This time= I got the following output: >=20 > diablo-jdk-freebsd6.i386.1.5.0.07.00 < needs updating (index has 1.5.0= .07.00) >=20 > It seems that the tool is confused by the i386 in the package name. Actually I think it's confused by the fact that the package name is "diablo-jdk" and the version is "freebsd6.i386.1.5.0.07.00". That's just plain bogus. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --ZGiS0Q5IWpPtfppv Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFErGL2XY6L6fI4GtQRAs57AJ4+DLFXnAO6dIHBRiOQal91mELcDACgnxc7 dAer88nkBxvF8O7Uns7X1Gc= =qioC -----END PGP SIGNATURE----- --ZGiS0Q5IWpPtfppv-- From owner-freebsd-stable@FreeBSD.ORG Thu Jul 6 01:24:09 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E480316A4F3 for ; Thu, 6 Jul 2006 01:24:09 +0000 (UTC) (envelope-from atanas@asd.aplus.net) Received: from pro20.abac.com (pro20.abac.com [66.226.64.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7FDA343D49 for ; Thu, 6 Jul 2006 01:24:09 +0000 (GMT) (envelope-from atanas@asd.aplus.net) Received: from [216.55.129.5] (asd2.aplus.net [216.55.129.5]) (authenticated bits=0) by pro20.abac.com (8.13.6/8.13.6) with ESMTP id k661O3UB032613 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 5 Jul 2006 18:24:03 -0700 (PDT) (envelope-from atanas@asd.aplus.net) Message-ID: <44AC6793.2070608@asd.aplus.net> Date: Wed, 05 Jul 2006 18:29:55 -0700 From: Atanas User-Agent: Thunderbird 1.5.0.4 (Macintosh/20060516) MIME-Version: 1.0 To: pyunyh@gmail.com References: <20060628185426.M43909@ganymede.hub.org> <20060628225239.GA93265@dan.emsphone.com> <44A3394C.4090209@asd.aplus.net> <44A3817F.4030105@thebeastie.org> <20060629092154.GE742@turion.vk2pj.dyndns.org> <20060629083130.X1229@ganymede.hub.org> <44A4A02A.9060802@thebeastie.org> <20060630012615.Q1103@ganymede.hub.org> <44A57B71.6020201@asd.aplus.net> <20060701035416.GC54876@cdnetworks.co.kr> In-Reply-To: <20060701035416.GC54876@cdnetworks.co.kr> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 1.47 (SPF_SOFTFAIL) Cc: Peter Jeremy , freebsd-stable@freebsd.org, Michael Vince , User Freebsd Subject: Re: em device hangs on ifconfig alias ... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Jul 2006 01:24:10 -0000 Pyun YongHyeon said the following on 6/30/06 8:54 PM: > On Fri, Jun 30, 2006 at 12:28:49PM -0700, Atanas wrote: > > User Freebsd said the following on 6/29/06 9:29 PM: > > > > > >The other funny thing about the current em driver is that if you move an > > >IP to it from a different server, the appropriate ARP packets aren't > > >sent out to redirect the IP traffic .. recently, someone pointed me to > > >arping, which has solved my problem *external* to the driver ... > > > > > That's the second reason why I (still) avoid em in mass-aliased systems. > > > > I have a single pool of IP addresses shared by many servers with > > multiple aliases each. When someone leaves and frees an IP, it gets > > reused and brought up on a different server. In case it was previously > > handled by em, the traffic doesn't get redirected to the new server. > > > > Similar thing happens even with machines with single static IPs. For > > instance when retiring an old production system, I usually request a new > > box to be brought up on a different IP, make a fresh install on > > everything and test, swap IP addresses and reboot. In case of em, after > > a soft reboot both systems are inaccessible. > > > > A workaround is to power both of the systems down and then power them > > up. This however cannot be done remotely and in case there were IP > > aliases, they still don't get any traffic. > > > > I haven't fully tested it but what about attached patch? > It may fix your ARP issue. The patch also fixes other issues > related with ioctls. > Now em(4) will send a ARP packet when its IP address is changed even > if there is no active link. Since em(4) is not mii-aware driver I > can't sure this behaviour is correct. > The patch is against if_em.c,v 1.116 2006/06/06, which is 7-CURRENT. I tried "merging" the relevant em driver files into a 6-STABLE installation by simply copying sys/dev/em/* and sys/modules/em/Makefile, but it seems that the new revision depends on other -CURRENT things and the module build fails: # pwd /usr/src/sys/modules/em # make clean; make ... /usr/src/sys/modules/em/../../dev/em/if_em.c: In function `em_setup_interface': /usr/src/sys/modules/em/../../dev/em/if_em.c:2143: error: `IFCAP_VLAN_HWCSUM' undeclared (first use in this function) ... I don't have a 7-CURRENT based box around. It seems too bleeding edge for me anyway. I was hoping to play with different if_em kernel modules on a semi-production (spare) box and eventually test the proposed em patch, but apparently it's not so easy. Please let me know if I'm missing something obvious. Thanks, Atanas > > > ------------------------------------------------------------------------ > > Index: if_em.c > =================================================================== > RCS file: /pool/ncvs/src/sys/dev/em/if_em.c,v > retrieving revision 1.116 > diff -u -r1.116 if_em.c > --- if_em.c 6 Jun 2006 08:03:49 -0000 1.116 > +++ if_em.c 1 Jul 2006 03:51:41 -0000 > @@ -692,7 +692,8 @@ > > EM_LOCK_ASSERT(sc); > > - if (!sc->link_active) > + if ((ifp->if_drv_flags & (IFF_DRV_RUNNING|IFF_DRV_OACTIVE)) != > + IFF_DRV_RUNNING) > return; > > while (!IFQ_DRV_IS_EMPTY(&ifp->if_snd)) { > @@ -751,11 +752,6 @@ > return (error); > > switch (command) { > - case SIOCSIFADDR: > - case SIOCGIFADDR: > - IOCTL_DEBUGOUT("ioctl rcv'd: SIOCxIFADDR (Get/Set Interface Addr)"); > - ether_ioctl(ifp, command, data); > - break; > case SIOCSIFMTU: > { > int max_frame_size; > @@ -802,17 +798,19 @@ > IOCTL_DEBUGOUT("ioctl rcv'd: SIOCSIFFLAGS (Set Interface Flags)"); > EM_LOCK(sc); > if (ifp->if_flags & IFF_UP) { > - if (!(ifp->if_drv_flags & IFF_DRV_RUNNING)) { > + if ((ifp->if_drv_flags & IFF_DRV_RUNNING)) { > + if ((ifp->if_flags ^ sc->if_flags) & > + IFF_PROMISC) { > + em_disable_promisc(sc); > + em_set_promisc(sc); > + } > + } else > em_init_locked(sc); > - } > - > - em_disable_promisc(sc); > - em_set_promisc(sc); > } else { > - if (ifp->if_drv_flags & IFF_DRV_RUNNING) { > + if (ifp->if_drv_flags & IFF_DRV_RUNNING) > em_stop(sc); > - } > } > + sc->if_flags = ifp->if_flags; > EM_UNLOCK(sc); > break; > case SIOCADDMULTI: > @@ -878,8 +876,8 @@ > break; > } > default: > - IOCTL_DEBUGOUT1("ioctl received: UNKNOWN (0x%x)", (int)command); > - error = EINVAL; > + error = ether_ioctl(ifp, command, data); > + break; > } > > return (error); > Index: if_em.h > =================================================================== > RCS file: /pool/ncvs/src/sys/dev/em/if_em.h,v > retrieving revision 1.44 > diff -u -r1.44 if_em.h > --- if_em.h 15 Feb 2006 08:39:50 -0000 1.44 > +++ if_em.h 1 Jul 2006 03:51:41 -0000 > @@ -259,6 +259,7 @@ > struct callout timer; > struct callout tx_fifo_timer; > int io_rid; > + int if_flags; > struct mtx mtx; > int em_insert_vlan_header; > struct task link_task; > > > ------------------------------------------------------------------------ > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-stable@FreeBSD.ORG Thu Jul 6 02:11:19 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A4EEA16A4DA for ; Thu, 6 Jul 2006 02:11:19 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from nz-out-0102.google.com (nz-out-0102.google.com [64.233.162.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7B6CD43D45 for ; Thu, 6 Jul 2006 02:11:18 +0000 (GMT) (envelope-from pyunyh@gmail.com) Received: by nz-out-0102.google.com with SMTP id r28so1008125nza for ; Wed, 05 Jul 2006 19:11:18 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=t6xhqT637CqiwKf/mTfDbXtwM0wZDvsSdsmKB/LNgTMTkihUxpMUwn7vggwctQI4j22Evb1suhTdZs3embY/b/xva8lRR5H7Rx7AnMySvh5xYPjrM5yXFWfuWMOgoykAA9FiwiJiO4PLfS5dghQNSKrW++bwJosBmqhhHRDnL8Y= Received: by 10.36.74.20 with SMTP id w20mr119310nza; Wed, 05 Jul 2006 19:11:18 -0700 (PDT) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.gmail.com with ESMTP id 15sm2248276nzn.2006.07.05.19.11.14; Wed, 05 Jul 2006 19:11:17 -0700 (PDT) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.13.5/8.13.5) with ESMTP id k662EobY077537 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 6 Jul 2006 11:14:50 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id k662EiRP077536; Thu, 6 Jul 2006 11:14:44 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Thu, 6 Jul 2006 11:14:44 +0900 From: Pyun YongHyeon To: Atanas Message-ID: <20060706021444.GA76865@cdnetworks.co.kr> References: <20060628225239.GA93265@dan.emsphone.com> <44A3394C.4090209@asd.aplus.net> <44A3817F.4030105@thebeastie.org> <20060629092154.GE742@turion.vk2pj.dyndns.org> <20060629083130.X1229@ganymede.hub.org> <44A4A02A.9060802@thebeastie.org> <20060630012615.Q1103@ganymede.hub.org> <44A57B71.6020201@asd.aplus.net> <20060701035416.GC54876@cdnetworks.co.kr> <44AC6793.2070608@asd.aplus.net> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="1yeeQ81UyVL57Vl7" Content-Disposition: inline In-Reply-To: <44AC6793.2070608@asd.aplus.net> User-Agent: Mutt/1.4.2.1i Cc: Peter Jeremy , freebsd-stable@freebsd.org, Michael Vince , User Freebsd Subject: Re: em device hangs on ifconfig alias ... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Jul 2006 02:11:19 -0000 --1yeeQ81UyVL57Vl7 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Wed, Jul 05, 2006 at 06:29:55PM -0700, Atanas wrote: > Pyun YongHyeon said the following on 6/30/06 8:54 PM: > >On Fri, Jun 30, 2006 at 12:28:49PM -0700, Atanas wrote: > > > User Freebsd said the following on 6/29/06 9:29 PM: > > > > > > > >The other funny thing about the current em driver is that if you move > > an > >IP to it from a different server, the appropriate ARP packets > > aren't > >sent out to redirect the IP traffic .. recently, someone > > pointed me to > >arping, which has solved my problem *external* to the > > driver ... > > > > > > > That's the second reason why I (still) avoid em in mass-aliased systems. > > > > > > I have a single pool of IP addresses shared by many servers with > > > multiple aliases each. When someone leaves and frees an IP, it gets > > > reused and brought up on a different server. In case it was previously > > > handled by em, the traffic doesn't get redirected to the new server. > > > > > > Similar thing happens even with machines with single static IPs. For > > > instance when retiring an old production system, I usually request a > > new > box to be brought up on a different IP, make a fresh install on > > > everything and test, swap IP addresses and reboot. In case of em, after > > > a soft reboot both systems are inaccessible. > > > > > > A workaround is to power both of the systems down and then power them > > > up. This however cannot be done remotely and in case there were IP > > > aliases, they still don't get any traffic. > > > > > > >I haven't fully tested it but what about attached patch? > >It may fix your ARP issue. The patch also fixes other issues > >related with ioctls. > >Now em(4) will send a ARP packet when its IP address is changed even > >if there is no active link. Since em(4) is not mii-aware driver I > >can't sure this behaviour is correct. > > > The patch is against if_em.c,v 1.116 2006/06/06, which is 7-CURRENT. I > tried "merging" the relevant em driver files into a 6-STABLE > installation by simply copying sys/dev/em/* and sys/modules/em/Makefile, > but it seems that the new revision depends on other -CURRENT things and > the module build fails: > > # pwd > /usr/src/sys/modules/em > # make clean; make > ... > /usr/src/sys/modules/em/../../dev/em/if_em.c: In function > `em_setup_interface': > /usr/src/sys/modules/em/../../dev/em/if_em.c:2143: error: > `IFCAP_VLAN_HWCSUM' undeclared (first use in this function) > ... > > I don't have a 7-CURRENT based box around. It seems too bleeding edge > for me anyway. I was hoping to play with different if_em kernel modules > on a semi-production (spare) box and eventually test the proposed em > patch, but apparently it's not so easy. > > Please let me know if I'm missing something obvious. > My bad. Here is patch generated against RELENG_6. -- Regards, Pyun YongHyeon --1yeeQ81UyVL57Vl7 Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="em.arp.REL_6.patch" --- if_em.c.orig Fri May 19 09:19:57 2006 +++ if_em.c Thu Jul 6 11:10:56 2006 @@ -657,8 +657,9 @@ mtx_assert(&adapter->mtx, MA_OWNED); - if (!adapter->link_active) - return; + if ((ifp->if_drv_flags & (IFF_DRV_RUNNING|IFF_DRV_OACTIVE)) != + IFF_DRV_RUNNING) + return; while (!IFQ_DRV_IS_EMPTY(&ifp->if_snd)) { @@ -719,11 +720,6 @@ if (adapter->in_detach) return(error); switch (command) { - case SIOCSIFADDR: - case SIOCGIFADDR: - IOCTL_DEBUGOUT("ioctl rcv'd: SIOCxIFADDR (Get/Set Interface Addr)"); - ether_ioctl(ifp, command, data); - break; case SIOCSIFMTU: { int max_frame_size; @@ -760,16 +756,17 @@ IOCTL_DEBUGOUT("ioctl rcv'd: SIOCSIFFLAGS (Set Interface Flags)"); EM_LOCK(adapter); if (ifp->if_flags & IFF_UP) { - if (!(ifp->if_drv_flags & IFF_DRV_RUNNING)) { + if ((ifp->if_drv_flags & IFF_DRV_RUNNING)) { + if ((ifp->if_flags ^ adapter->if_flags) & + IFF_PROMISC) { + em_disable_promisc(adapter); + em_set_promisc(adapter); + } + } else em_init_locked(adapter); - } - - em_disable_promisc(adapter); - em_set_promisc(adapter); } else { - if (ifp->if_drv_flags & IFF_DRV_RUNNING) { + if (ifp->if_drv_flags & IFF_DRV_RUNNING) em_stop(adapter); - } } EM_UNLOCK(adapter); break; @@ -835,8 +832,8 @@ break; } default: - IOCTL_DEBUGOUT1("ioctl received: UNKNOWN (0x%x)", (int)command); - error = EINVAL; + error = ether_ioctl(ifp, command, data); + break; } return(error); --- if_em.h.orig Thu Jul 6 11:06:17 2006 +++ if_em.h Thu Jul 6 11:06:41 2006 @@ -331,6 +331,7 @@ struct callout timer; struct callout tx_fifo_timer; int io_rid; + int if_flags; u_int8_t unit; struct mtx mtx; int em_insert_vlan_header; --1yeeQ81UyVL57Vl7-- From owner-freebsd-stable@FreeBSD.ORG Thu Jul 6 02:19:07 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ACDEE16A4E2 for ; Thu, 6 Jul 2006 02:19:07 +0000 (UTC) (envelope-from vyeperman@gmail.com) Received: from wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.238]) by mx1.FreeBSD.org (Postfix) with ESMTP id 80D4143D49 for ; Thu, 6 Jul 2006 02:19:05 +0000 (GMT) (envelope-from vyeperman@gmail.com) Received: by wr-out-0506.google.com with SMTP id 58so1239449wri for ; Wed, 05 Jul 2006 19:19:05 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=OW44GkSzFZieCZRuA1dBv+xHZDUugRcx/3206bQwyzyqZvRGdklIik2Zedcgr99tbNx92S3y7p7su4AXfqGWwysVe4ItqeymAJ2AbJSyPFuzLgvHEZXCZaa3zgTfd7yqqWAyqBVwpAm3fdLs9sf9KPapIc3cg73cZLe0Zei5lhA= Received: by 10.65.213.14 with SMTP id p14mr95487qbq; Wed, 05 Jul 2006 19:19:04 -0700 (PDT) Received: by 10.65.181.16 with HTTP; Wed, 5 Jul 2006 19:19:04 -0700 (PDT) Message-ID: <6c3c36d00607051919ra101804pede53c4f2ae3bb9f@mail.gmail.com> Date: Wed, 5 Jul 2006 19:19:04 -0700 From: "Vye Wilson" To: freebsd-stable@freebsd.org In-Reply-To: <200607060240.00346.max@love2party.net> MIME-Version: 1.0 References: <6c3c36d00607051702l178c1cb1he58749c03725c1ac@mail.gmail.com> <200607060208.26315.max@love2party.net> <6c3c36d00607051717t5aa6ed1dl3595c11b3b769561@mail.gmail.com> <200607060240.00346.max@love2party.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: 0.0% user, 0.0% nice, 0.0% system, 53.8% interrupt, 46.2% idle - Unusual interrupt use? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Jul 2006 02:19:07 -0000 I do not use usb at all on this paticular server. The only ones on it are the 2-4 onboard ones. Removing uhci from my kernel fixed this issue. Thank you. On 7/5/06, Max Laier wrote: > > On Thursday 06 July 2006 02:17, Vye Wilson wrote: > > # vmstat -i > > interrupt total rate > > irq1: atkbd0 5 0 > > irq6: fdc0 3 0 > > irq10: uhci1 915633230 262810 > > irq15: ata1 1306 0 > > irq17: fwohci0 1 0 > > irq18: fxp0 2876 0 > > irq21: twa0 153 0 > > cpu0: timer 6964974 1999 > > Total 922602548 264811 > > Are you using usb on that box? If not, get rid of device uhci in your > kernel > config to see if that fixes it. If you are using usb - I have no idea. A > BIOS upgrade might help. > > -- > /"\ Best regards, | mlaier@freebsd.org > \ / Max Laier | ICQ #67774661 > X http://pf4freebsd.love2party.net/ | mlaier@EFnet > / \ ASCII Ribbon Campaign | Against HTML Mail and News > > > -- --Vye From owner-freebsd-stable@FreeBSD.ORG Thu Jul 6 04:14:00 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C2AE116A4DE for ; Thu, 6 Jul 2006 04:14:00 +0000 (UTC) (envelope-from dan@syz.com) Received: from mail2.syz.com (static-139-142-196-33.gtcust.grouptelecom.net [139.142.196.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id 722F143D49 for ; Thu, 6 Jul 2006 04:14:00 +0000 (GMT) (envelope-from dan@syz.com) Received: from [127.0.0.1] (localhost [127.0.0.1]) by mail2.syz.com (Postfix) with ESMTP id 94281257B3E; Wed, 5 Jul 2006 22:13:59 -0600 (MDT) Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <10C47031-8CC8-4C62-BE5B-F95579EF1DD3@syz.com> Content-Transfer-Encoding: 7bit From: Dan Charrois Date: Wed, 5 Jul 2006 22:13:59 -0600 To: vivek@khera.org X-Mailer: Apple Mail (2.752.2) Cc: freebsd-stable@freebsd.org Subject: Re: Which FreeBSD is the most stable for Dell PowerEdge 2850 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Jul 2006 04:14:00 -0000 > I don't have any 2850's but the 1850 I have has been running 6.0 > since the BETA1, and last night just upgraded it to 6.1. No issues. > The PERC 4e/Si card is phenominally fast on this system (running 2 > disk RAID1). I'd recommend you to run 6.1 as it is stable on all of > my Dell systems that run it (and I'm migrating the older FreeBSD > boxes to 6.1 as time permits). > > If you already have > 1 CPU, you might as well leave hyperthreading > off. There are cases where it degenerates performance rather than > enhance it. > > As for mysql version, "no comment" :-) Thanks for the reply! I'm in the process of upgrading the 2850 to 6.1 now, and it seems to have gone well so far. Time will tell in the long term whether the stability is what I'm hoping for, but at least it does seem to be up and running okay so far. As for hyperthreading, I did some benchmarking back with FreeBSD 5.4 using the actual SQL databases I'm serving on the machine and loading the server with lots of simultaneous queries from remote machines similar to those which will be used in production. Back then, there was about a 10% increase in performance. I'll run the same tests again before putting the machine in production again to see if anything changed. 10% isn't much, but every bit helps, if hyperthreading doesn't cause the machine to become unstable otherwise. Thanks again! Dan -- Syzygy Research & Technology Box 83, Legal, AB T0G 1L0 Canada Phone: 780-961-2213 From owner-freebsd-stable@FreeBSD.ORG Thu Jul 6 08:27:52 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D701E16A4E2 for ; Thu, 6 Jul 2006 08:27:52 +0000 (UTC) (envelope-from hdemir@metu.edu.tr) Received: from tenedos.general.services.metu.edu.tr (tenedos.general.services.metu.edu.tr [144.122.144.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id DDDD043D55 for ; Thu, 6 Jul 2006 08:27:51 +0000 (GMT) (envelope-from hdemir@metu.edu.tr) Received: from simena.user.services.metu.edu.tr (simena.user.services.metu.edu.tr [144.122.144.15]) by tenedos.general.services.metu.edu.tr (8.13.7/8.13.7) with ESMTP id k668Rnon017133 for ; Thu, 6 Jul 2006 11:27:49 +0300 Received: (from hdemir@localhost) by simena.user.services.metu.edu.tr (8.13.7/8.13.7/Submit) id k668Rnd4516302 for freebsd-stable@freebsd.org; Thu, 6 Jul 2006 11:27:49 +0300 Date: Thu, 6 Jul 2006 11:27:49 +0300 From: husnu demir To: freebsd-stable@freebsd.org Message-ID: <20060706082748.GA921748@metu.edu.tr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.11 X-Virus-Scanned: ClamAV 0.88.2/1586/Wed Jul 5 22:22:07 2006 on tenedos.general.services.metu.edu.tr X-Virus-Status: Clean Subject: cannot listen fatm0 with tcpdump X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Jul 2006 08:27:52 -0000 Hi, I need to listen up the fatm0 interface but could not do that. Is there any reason for that? Thanks in advance. Husnu Demir. ------------------------------------------------------- Error Message: # tcpdump -i fatm0 tcpdump: BIOCSETIF: fatm0: Device not configured And settings; # ATM settings device atm options NATM # uname -a FreeBSD nrouter 6.1-PRERELEASE FreeBSD 6.1-PRERELEASE #0: Mon Mar 13 14:56:09 EET 2006 root@nrouter:/usr/obj/usr/src/sys/NOTDEFAULT i386 # ifconfig fatm0 xx.yy.zz.130 netmask 255.255.255.252 up # atmconfig natm add xx.yy.zz.129 fatm0 0 148 llc/snap ubr And syslog message for the card; Jul 6 09:57:58 nrouter fatm0: mem 0xf7000000-0xf71fffff irq 21 at device 0.0 on pci5 Jul 6 09:57:58 nrouter fatm0: [GIANT-LOCKED] Jul 6 09:57:58 nrouter fatm0: ESI=00:20:48:04:f8:83 serial=63619 hw=0x20001 sw=0x4010c From owner-freebsd-stable@FreeBSD.ORG Thu Jul 6 08:54:44 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 53D9816A4DE for ; Thu, 6 Jul 2006 08:54:44 +0000 (UTC) (envelope-from lists@niamodnikufesin.de) Received: from mx.does.not-exist.de (mx.does.not-exist.de [62.159.88.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id C9B4943D46 for ; Thu, 6 Jul 2006 08:54:42 +0000 (GMT) (envelope-from lists@niamodnikufesin.de) Received: from rw.does.not-exist.de ([10.42.23.2]) by mx.does.not-exist.de with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.52 (FreeBSD)) id 1FyPd8-000HnE-DA; Thu, 06 Jul 2006 10:54:38 +0200 Received: from hank by rw.does.not-exist.de with local (Exim 4.52 (FreeBSD)) id 1FyPdA-0000SI-Ll; Thu, 06 Jul 2006 10:54:40 +0200 Date: Thu, 6 Jul 2006 10:54:40 +0200 From: Hank Hampel To: freebsd-stable@freebsd.org Message-ID: <20060706085440.GA1654@warning.this.domain.does.not-exist.de> Mail-Followup-To: freebsd-stable@freebsd.org References: <20060705164058.GA5194@warning.this.domain.does.not-exist.de> <20060705174900.GA36025@slackbox.xs4all.nl> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="VS++wcV0S1rZb1Fb" Content-Disposition: inline In-Reply-To: <20060705174900.GA36025@slackbox.xs4all.nl> User-Agent: Mutt/1.4.2.1i X-fcc-folder: freebsd-stable-list Subject: Re: 5.5-stable network interface rl0 stops working X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Jul 2006 08:54:44 -0000 --VS++wcV0S1rZb1Fb Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi Roland, On (060705), Roland Smith wrote: > > couple of weeks - the network interface rl0 (which is the main > > interface on the maschine, rl1 is for backups/internal use only) stops > Are they physically on the motherboard? Or on PCI cards? In the latter > case try reseating the card in the slot. fortunately they are PCI cards, so I'll check the seating. > Try switching rl0 and rl1, and see if te problem persists. Also, > swapping out the ethernet cable is worth trying. Switching/exchanging the cards was an option we haven't tried yet although it came to my mind earlier - for sure the strangest problems are hardware related so I'll give this a try and report back. Swapping out the ethernet cable was one of the first things I checked but to no avail. But I'm not really sure if the switch isn't part of the problem (although all other ports function correctly) so I'll change the switch port to. > Another thing to check is if rl0 is sharing an interrupt with another > device. That can cause problems. No there is no interupt sharing for this device but thanks for this hint, I hadn't checked it yet. > > When rl0 stops working ipfw loggs lots of denied packets so that it > > seems that the dynamic (keep-state) rules don't work any longer. We > Does the problem persist without ipfw? I've got an rl0 card on my > workstation (6.1-STABLE, amd64, using PF without problems) Unfortunately I can't check this because we use ipfw to generate traffic statistics for the jails. But when the interface stops working it has no impact to disable the firewall, short of that no log messages are generated any longer. > > After the stop on the interface occurs there is no other way to get > > the interface up and running again than rebooting the whole machine. > > Restarting /etc/rc.d/netif, the jails or ipfw doesn't help anything. > What does ifconfig say after the interface stops working? When the interface stops working ifconfig seems "to think" everything is still ok. There is no hint in the output of ifconfig that the interface is not working and ifconfig down/up doesn't help any. > Anything in the logs, except the denied packets? No strange enough there is no other hint in the logs that the system is not working. At first I thought it was kind of an ipfw problem because packets seem to arrive on the host but the responses get blocked by ipfw. I'll check with tcpdump the next time it happens if it's true that packets still arrive on the system. On the other hand if ipfw is part of the problem (especially the dynamic rules) then flushing ipfw should help I think - but it doesn't. So maybe it's an hardware issue, I'll definitly check this and report back. Thanks for the hints and tips! Best regards, Hank --VS++wcV0S1rZb1Fb Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQFErM/QXSKk5/a79toRApBjAJ9CDNx/UPT8E7dN4RrOD89qZB1TJACfagDw aA/FI44BG1DKxmiB+Vhj33k= =GvFW -----END PGP SIGNATURE----- --VS++wcV0S1rZb1Fb-- From owner-freebsd-stable@FreeBSD.ORG Thu Jul 6 09:02:09 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4F35F16A4DE for ; Thu, 6 Jul 2006 09:02:09 +0000 (UTC) (envelope-from LoN_Kamikaze@gmx.de) Received: from mail.gmx.net (mail.gmx.de [213.165.64.21]) by mx1.FreeBSD.org (Postfix) with SMTP id 0BF9A43D4C for ; Thu, 6 Jul 2006 09:02:07 +0000 (GMT) (envelope-from LoN_Kamikaze@gmx.de) Received: (qmail invoked by alias); 06 Jul 2006 09:02:06 -0000 Received: from p54A7E1FC.dip.t-dialin.net (EHLO [192.168.0.12]) [84.167.225.252] by mail.gmx.net (mp031) with SMTP; 06 Jul 2006 11:02:07 +0200 X-Authenticated: #5465401 Message-ID: <44ACD177.1000204@gmx.de> Date: Thu, 06 Jul 2006 11:01:43 +0200 From: "[LoN]Kamikaze" Organization: Lords of Nightmare User-Agent: Thunderbird 1.5.0.4 (X11/20060605) MIME-Version: 1.0 To: Brooks Davis References: <44AC5D39.4010502@gmx.de> <20060706011015.GA6677@odin.ac.hmc.edu> In-Reply-To: <20060706011015.GA6677@odin.ac.hmc.edu> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 Cc: freebsd-stable@freebsd.org, freebsd-ports@freebsd.org Subject: Re: pkg_version confused by architecutre in package name X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Jul 2006 09:02:09 -0000 Brooks Davis wrote: > On Thu, Jul 06, 2006 at 02:45:45AM +0200, [LoN]Kamikaze wrote: >> I normally run the command >> # pkg_version -Iv | grep \< >> before running 'portupgrade -a', to see what's going to happen. This time I got the following output: >> >> diablo-jdk-freebsd6.i386.1.5.0.07.00 < needs updating (index has 1.5.0.07.00) >> >> It seems that the tool is confused by the i386 in the package name. > > Actually I think it's confused by the fact that the package name is > "diablo-jdk" and the version is "freebsd6.i386.1.5.0.07.00". That's > just plain bogus. > > -- Brooks > So who is at fault? The ports infrastructure or the FreeBSD foundation? From owner-freebsd-stable@FreeBSD.ORG Thu Jul 6 13:06:01 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0CD8416A4DF for ; Thu, 6 Jul 2006 13:06:01 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id C0DB443D6D for ; Thu, 6 Jul 2006 13:05:55 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 5B5E646D11; Thu, 6 Jul 2006 09:05:55 -0400 (EDT) Date: Thu, 6 Jul 2006 14:05:55 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Max Laier In-Reply-To: <200607060208.26315.max@love2party.net> Message-ID: <20060706140527.H92823@fledge.watson.org> References: <6c3c36d00607051702l178c1cb1he58749c03725c1ac@mail.gmail.com> <200607060208.26315.max@love2party.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Vye Wilson , freebsd-stable@freebsd.org Subject: Re: 0.0% user, 0.0% nice, 0.0% system, 53.8% interrupt, 46.2% idle - Unusual interrupt use? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Jul 2006 13:06:01 -0000 On Thu, 6 Jul 2006, Max Laier wrote: > On Thursday 06 July 2006 02:02, Vye Wilson wrote: >> I'm really not sure how to go about troubleshooting this issue. Can someone >> point me in the right direction? > > "vmstat -i" should give a good idea what is causing the interrupt load. I also highly recommend "top -S", which causes top to show system threads, such as interrupt threads and network threads, as a way to look at CPU use. Robert N M Watson Computer Laboratory University of Cambridge From owner-freebsd-stable@FreeBSD.ORG Thu Jul 6 15:24:05 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3C80816A4DE; Thu, 6 Jul 2006 15:24:05 +0000 (UTC) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id C717643D46; Thu, 6 Jul 2006 15:24:04 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.13.0/8.13.0) with ESMTP id k66FO4tt018552; Thu, 6 Jul 2006 08:24:04 -0700 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id k66FO459018551; Thu, 6 Jul 2006 08:24:04 -0700 Date: Thu, 6 Jul 2006 08:24:04 -0700 From: Brooks Davis To: "[LoN]Kamikaze" Message-ID: <20060706152403.GA13815@odin.ac.hmc.edu> References: <44AC5D39.4010502@gmx.de> <20060706011015.GA6677@odin.ac.hmc.edu> <44ACD177.1000204@gmx.de> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="a8Wt8u1KmwUX3Y2C" Content-Disposition: inline In-Reply-To: <44ACD177.1000204@gmx.de> User-Agent: Mutt/1.4.1i X-Virus-Scanned: by amavisd-new Cc: freebsd-stable@freebsd.org, freebsd-ports@freebsd.org Subject: Re: pkg_version confused by architecutre in package name X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Jul 2006 15:24:05 -0000 --a8Wt8u1KmwUX3Y2C Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jul 06, 2006 at 11:01:43AM +0200, [LoN]Kamikaze wrote: > Brooks Davis wrote: > > On Thu, Jul 06, 2006 at 02:45:45AM +0200, [LoN]Kamikaze wrote: > >> I normally run the command > >> # pkg_version -Iv | grep \< > >> before running 'portupgrade -a', to see what's going to happen. This t= ime I got the following output: > >> > >> diablo-jdk-freebsd6.i386.1.5.0.07.00 < needs updating (index has 1.= 5.0.07.00) > >> > >> It seems that the tool is confused by the i386 in the package name. > >=20 > > Actually I think it's confused by the fact that the package name is > > "diablo-jdk" and the version is "freebsd6.i386.1.5.0.07.00". That's > > just plain bogus. > >=20 > So who is at fault? The ports infrastructure or the FreeBSD foundation? I don't know. How did you install it? -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --a8Wt8u1KmwUX3Y2C Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFErSsTXY6L6fI4GtQRAjqrAJ9Fy7KFDfHIviGDm2BH2xTXXpVIhwCguQP9 6xG6DYtBi1jx28cYQbr2rG4= =jS/v -----END PGP SIGNATURE----- --a8Wt8u1KmwUX3Y2C-- From owner-freebsd-stable@FreeBSD.ORG Thu Jul 6 16:05:12 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 43ADF16A4E7 for ; Thu, 6 Jul 2006 16:05:12 +0000 (UTC) (envelope-from LoN_Kamikaze@gmx.de) Received: from mail.gmx.net (mail.gmx.de [213.165.64.21]) by mx1.FreeBSD.org (Postfix) with SMTP id 305DC43D5D for ; Thu, 6 Jul 2006 16:05:09 +0000 (GMT) (envelope-from LoN_Kamikaze@gmx.de) Received: (qmail invoked by alias); 06 Jul 2006 16:05:08 -0000 Received: from p54A7E1FC.dip.t-dialin.net (EHLO [192.168.0.12]) [84.167.225.252] by mail.gmx.net (mp001) with SMTP; 06 Jul 2006 18:05:08 +0200 X-Authenticated: #5465401 Message-ID: <44AD3495.9090603@gmx.de> Date: Thu, 06 Jul 2006 18:04:37 +0200 From: "[LoN]Kamikaze" Organization: Lords of Nightmare User-Agent: Thunderbird 1.5.0.4 (X11/20060605) MIME-Version: 1.0 To: Brooks Davis References: <44AC5D39.4010502@gmx.de> <20060706011015.GA6677@odin.ac.hmc.edu> <44ACD177.1000204@gmx.de> <20060706152403.GA13815@odin.ac.hmc.edu> In-Reply-To: <20060706152403.GA13815@odin.ac.hmc.edu> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 Cc: freebsd-stable@freebsd.org, freebsd-ports@freebsd.org Subject: Re: pkg_version confused by architecutre in package name X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Jul 2006 16:05:12 -0000 Brooks Davis wrote: > On Thu, Jul 06, 2006 at 11:01:43AM +0200, [LoN]Kamikaze wrote: >> Brooks Davis wrote: >>> On Thu, Jul 06, 2006 at 02:45:45AM +0200, [LoN]Kamikaze wrote: >>>> I normally run the command >>>> # pkg_version -Iv | grep \< >>>> before running 'portupgrade -a', to see what's going to happen. This time I got the following output: >>>> >>>> diablo-jdk-freebsd6.i386.1.5.0.07.00 < needs updating (index has 1.5.0.07.00) >>>> >>>> It seems that the tool is confused by the i386 in the package name. >>> Actually I think it's confused by the fact that the package name is >>> "diablo-jdk" and the version is "freebsd6.i386.1.5.0.07.00". That's >>> just plain bogus. >>> >> So who is at fault? The ports infrastructure or the FreeBSD foundation? > > I don't know. How did you install it? > # pkg_add diablo-jdk-freebsd6.i386.1.5.0.07.00.tbz From owner-freebsd-stable@FreeBSD.ORG Thu Jul 6 16:37:07 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F227C16A4DE for ; Thu, 6 Jul 2006 16:37:06 +0000 (UTC) (envelope-from goran.lowkrantz@ismobile.com) Received: from mail.ismobile.com (tandgrisner.ismobile.com [213.88.244.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6CF1643D49 for ; Thu, 6 Jul 2006 16:37:05 +0000 (GMT) (envelope-from goran.lowkrantz@ismobile.com) Received: from [10.255.253.2] (thor.glz.hidden-powers.com [10.255.253.2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.ismobile.com (Postfix) with ESMTP id BFFEA2280B for ; Thu, 6 Jul 2006 18:37:01 +0200 (CEST) Date: Thu, 06 Jul 2006 18:37:00 +0200 From: Goran Lowkrantz To: freebsd-stable@freebsd.org Message-ID: <24C282E4D260624D50275B43@[10.255.253.2]> X-Mailer: Mulberry/4.0.4 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Subject: Problem restarting gvinum raid-5 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Jul 2006 16:37:07 -0000 Hi, We have a gvinum raid-5 volume that that we had to replace a disk on and=20 after that we cant get the new subdisk starting. Here are the things we did: 1: Replace disk and boot singleuser to fdisk and lable new disk: gvinum -> list 5 drives: D disk4 State: up /dev/da5s1a A: 0/17492 MB (0%) D disk3 State: up /dev/da4s1a A: 0/17492 MB (0%) D disk2 State: up /dev/da3s1a A: 0/17492 MB (0%) D disk1 State: up /dev/da2s1a A: 0/17492 MB (0%) 1 volume: V imap State: up Plexes: 1 Size: 68 GB 1 plex: P imap.p0 R5 State: up Subdisks: 5 Size: 68 GB 5 subdisks: S imap.p0.s0 State: up D: disk1 Size: 17 GB S imap.p0.s1 State: up D: disk2 Size: 17 GB S imap.p0.s2 State: up D: disk3 Size: 17 GB S imap.p0.s3 State: up D: disk4 Size: 17 GB S imap.p0.s4 State: up D: disk5 Size: 17 GB After fixing the new disk partition we did a saveconfig and reboot: gvinum -> list 5 drives: D disk5 State: up /dev/da6s1a A: 0/17492 MB (0%) D disk4 State: up /dev/da5s1a A: 0/17492 MB (0%) D disk3 State: up /dev/da4s1a A: 0/17492 MB (0%) D disk2 State: up /dev/da3s1a A: 0/17492 MB (0%) D disk1 State: up /dev/da2s1a A: 0/17492 MB (0%) 1 volume: V imap State: up Plexes: 1 Size: 68 GB 1 plex: P imap.p0 R5 State: up Subdisks: 5 Size: 68 GB 5 subdisks: S imap.p0.s4 State: stale D: disk5 Size: 17 GB S imap.p0.s3 State: up D: disk4 Size: 17 GB S imap.p0.s2 State: up D: disk3 Size: 17 GB S imap.p0.s1 State: up D: disk2 Size: 17 GB S imap.p0.s0 State: up D: disk1 Size: 17 GB Tried start on plex and subdisk, nnot working. Finally, to get plex into=20 degraded mode we did a setstate down imap.p0.s4. gvinum -> list 5 drives: D disk5 State: up /dev/da6s1a A: 0/17492 MB (0%) D disk4 State: up /dev/da5s1a A: 0/17492 MB (0%) D disk3 State: up /dev/da4s1a A: 0/17492 MB (0%) D disk2 State: up /dev/da3s1a A: 0/17492 MB (0%) D disk1 State: up /dev/da2s1a A: 0/17492 MB (0%) 1 volume: V imap State: up Plexes: 1 Size: 68 GB 1 plex: P imap.p0 R5 State: degraded Subdisks: 5 Size: 68 GB 5 subdisks: S imap.p0.s4 State: down D: disk5 Size: 17 GB S imap.p0.s3 State: up D: disk4 Size: 17 GB S imap.p0.s2 State: up D: disk3 Size: 17 GB S imap.p0.s1 State: up D: disk2 Size: 17 GB S imap.p0.s0 State: up D: disk1 Size: 17 GB and here we are. Start on volume or plex give errno 16, start on subdisk=20 gives can't start: cannot start 'imap.p0.s4' - not yet supported. Can't find any descriptions of the proper way to do disk replacement, so if = this is wrong, I'd love to get updated. And how do we get the current=20 situation upa nd running? Regards, G=C3=B6ran ................................................... the future isMobile Goran Lowkrantz System Architect, isMobile, Aurorum 2, S-977 75 Lule=C3=A5, Sweden Phone: +46(0)920-75559 Mobile: +46(0)70-587 87 82 Fax: +46(0)70-615 87 82 http://www.ismobile.com ............................................... From owner-freebsd-stable@FreeBSD.ORG Thu Jul 6 16:52:03 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AB58816A4E0 for ; Thu, 6 Jul 2006 16:52:03 +0000 (UTC) (envelope-from brad-fbsd-stable@duttonbros.com) Received: from uno.mnl.com (uno.mnl.com [63.97.246.49]) by mx1.FreeBSD.org (Postfix) with SMTP id 4BF1243D46 for ; Thu, 6 Jul 2006 16:52:03 +0000 (GMT) (envelope-from brad-fbsd-stable@duttonbros.com) Received: (qmail 47271 invoked by uid 85); 6 Jul 2006 16:52:01 -0000 Received: from 127.0.0.1 by uno (envelope-from , uid 89) with qmail-scanner-1.25 (spamassassin: 2.55. Clear:RC:1(127.0.0.1):. Processed in 0.07268 secs); 06 Jul 2006 16:52:01 -0000 Received: from unknown (HELO uno.mnl.com) (127.0.0.1) by localhost with SMTP; 6 Jul 2006 16:52:00 -0000 Received: from 192.168.0.13 (SquirrelMail authenticated user bdutton) by uno.mnl.com with HTTP; Thu, 6 Jul 2006 09:52:00 -0700 (PDT) Message-ID: <1250.192.168.0.13.1152204720.squirrel@uno.mnl.com> Date: Thu, 6 Jul 2006 09:52:00 -0700 (PDT) From: "Bradley W. Dutton" To: freebsd-stable@freebsd.org User-Agent: SquirrelMail/1.4.6 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Subject: graid3 rebuild panic: mb_dtor_pack: ext_size != MCLBYTES X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: brad-fbsd-stable@duttonbros.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Jul 2006 16:52:03 -0000 Hi, I get the below panic when rebuilding a graid3 array. Is this indicative of a hardware or software problem? Or is some of the data on my array corrupt and I should just rebuild the array? I searched on google and didn't find much. panic: mb_dtor_pack: ext_size != MCLBYTES Thanks for your time, Brad From owner-freebsd-stable@FreeBSD.ORG Thu Jul 6 17:56:39 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7733016A4DF for ; Thu, 6 Jul 2006 17:56:39 +0000 (UTC) (envelope-from ronald-freebsd8@klop.yi.org) Received: from smtp-out3.tiscali.nl (smtp-out3.tiscali.nl [195.241.79.178]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0CD0243D6B for ; Thu, 6 Jul 2006 17:56:36 +0000 (GMT) (envelope-from ronald-freebsd8@klop.yi.org) Received: from [82.171.39.195] (helo=guido.klop.ws) by smtp-out3.tiscali.nl with smtp (Tiscali http://www.tiscali.nl) id 1FyY5c-00067a-Aq for ; Thu, 06 Jul 2006 19:56:36 +0200 Received: (qmail 73194 invoked from network); 6 Jul 2006 17:56:34 -0000 Received: from localhost.thuis.klop.ws (HELO localhost) (127.0.0.1) by localhost.thuis.klop.ws with SMTP; 6 Jul 2006 17:56:34 -0000 Date: Thu, 06 Jul 2006 19:56:34 +0200 To: freebsd-stable@freebsd.org From: "Ronald Klop" Content-Type: text/plain; format=flowed; delsp=yes; charset=us-ascii MIME-Version: 1.0 References: <20060704212432.GA57426@lpthe.jussieu.fr> <44AB0C96.3090400@samsco.org> Content-Transfer-Encoding: 7bit Message-ID: In-Reply-To: <44AB0C96.3090400@samsco.org> User-Agent: Opera Mail/9.00 (FreeBSD) Subject: Re: NFS Locking Issue X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Jul 2006 17:56:39 -0000 On Wed, 05 Jul 2006 02:49:26 +0200, Scott Long wrote: > Michel Talon wrote: > >>> BTW, I noticed yesterday that that IPv6 support committ to rpc.lockd >>> was never backed out. An immediate question for people experiencing >>> new rpc.lockd problems with 6.x should be whether or not backing out >>> that change helps. >> So it may be relevant to say that i have kernels without IPV6 support. >> Recall that i have absolutely no problem with the client in FreeBSD-6.1. >> Tomorrow i will test one of the 6.1 machines as a NFS server and the >> other as >> a client, and will make you know if i see something. >> As to the problems you mention about NFS Linux, yes i have seen a lot >> since >> years. But to my surprise FC5 seems to work well. By the way it is >> kernel >> 2.6.16 so sufficiently recent for the problems to have been ironed out, >> presumably. >> > > 2.6.16 should be OK. I've heard of problems with cookie and handle > sizes with it, but only under highly unusual circumstances. > > Scott Just for the record. I'm running a 6.1-STABLE client with a Debian 3.1 server with kernel 2.6.12 and that works ok with nfs locking. Locking didn't work in the past (6.0-STABLE). Ronald. -- Ronald Klop Amsterdam, The Netherlands From owner-freebsd-stable@FreeBSD.ORG Thu Jul 6 18:32:59 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A567716A4DA for ; Thu, 6 Jul 2006 18:32:59 +0000 (UTC) (envelope-from abcjr@abcjr.net) Received: from abc3.abcjr.net (abc3.abcjr.net [65.241.104.86]) by mx1.FreeBSD.org (Postfix) with ESMTP id 420FD43D53 for ; Thu, 6 Jul 2006 18:32:58 +0000 (GMT) (envelope-from abcjr@abcjr.net) Received: from abcjr.abcjr.net (ip68-102-33-105.ks.ok.cox.net [68.102.33.105]) by abc3.abcjr.net (Postfix) with ESMTP id 29D6D6313 for ; Thu, 6 Jul 2006 13:32:57 -0500 (CDT) Received: from abcjr.abcjr.net (localhost [127.0.0.1]) by abcjr.abcjr.net (8.13.6/8.13.6) with ESMTP id k66IWr0g068024 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 6 Jul 2006 13:32:54 -0500 (CDT) (envelope-from abcjr@abcjr.abcjr.net) Received: (from abcjr@localhost) by abcjr.abcjr.net (8.13.6/8.13.6/Submit) id k66IWrej068023 for freebsd-stable@freebsd.org; Thu, 6 Jul 2006 13:32:53 -0500 (CDT) (envelope-from abcjr) Date: Thu, 6 Jul 2006 13:32:53 -0500 From: "Arnold Cavazos Jr." To: freebsd-stable@freebsd.org Message-ID: <20060706183253.GC61190@abcjr.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.11 X-Virus-Scanned: ClamAV 0.88.2/1586/Wed Jul 5 14:22:07 2006 on abcjr.abcjr.net X-Virus-Status: Clean X-Spam-Status: No, score=-1.4 required=5.0 tests=ALL_TRUSTED,AWL, SPF_HELO_PASS autolearn=disabled version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on abcjr.abcjr.net Subject: Dell PowerEdge 750 & 850 environtmental monitoring X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Jul 2006 18:32:59 -0000 Does anybody have temperature and fan monitoring working on Dell PowerEdge 750's & 850's? I have done my share of googling without much luck. -- Arnold Cavazos, Jr. abcjr at abcjr . net From owner-freebsd-stable@FreeBSD.ORG Thu Jul 6 19:46:25 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 90A5D16A4DE for ; Thu, 6 Jul 2006 19:46:25 +0000 (UTC) (envelope-from anton@nikiforov.ru) Received: from vika.newlines.ru (anna.newlines.ru [195.246.218.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0243443D73 for ; Thu, 6 Jul 2006 19:46:23 +0000 (GMT) (envelope-from anton@nikiforov.ru) Received: from localhost (unknown [127.0.0.1]) by vika.newlines.ru (Postfix) with ESMTP id 3FBAB114CA for ; Thu, 6 Jul 2006 23:46:22 +0400 (MSD) Received: from vika.newlines.ru ([127.0.0.1]) by localhost (anna.newlines.ru [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 68250-06 for ; Thu, 6 Jul 2006 23:46:17 +0400 (MSD) Received: from [192.168.80.107] (strijev.office.sportlottery.ru [192.168.80.107]) by vika.newlines.ru (Postfix) with ESMTP for ; Thu, 6 Jul 2006 23:46:17 +0400 (MSD) Message-ID: <44AD688A.6050408@nikiforov.ru> Date: Thu, 06 Jul 2006 23:46:18 +0400 From: Anton Nikiforov User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915 X-Accept-Language: ru, en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: By amavis at office-gw.newlines.ru Subject: carp+pfsync+freevrrpd+jail X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Jul 2006 19:46:25 -0000 Dear all. I have the following trouble: Using carp and pfsync i have made the redundand firewall (OS is 6.1p2 and everything is done like in mans, even ifconfig options) The only thing that is different that i have 2 ethernet interface (one for crosover link and the other is the paren interface for vlans) host1 ifconfig_vlan101="inet X.Y.Z.1 netmask 255.255.255.0 broadcast X.Y.Z.255 vlan 101 vlandev em0" ifconfig_carp0="vhid 1 pass abc X.Y.Z.3" ifconfig_vlan100="inet A.B.C.1 netmask 255.255.255.0 broadcast A.B.C.255 vlan 100 vlandev em0" ifconfig_carp1="vhid 1 pass abc A.B.C.3" ifconfig_pfsync0="up syncif em1" host2 ifconfig_vlan101="inet X.Y.Z.2 netmask 255.255.255.0 broadcast X.Y.Z.255 vlan 101 vlandev em0" ifconfig_carp0="vhid 1 advskew 100 pass abc X.Y.Z.3" ifconfig_vlan100="inet A.B.C.2 netmask 255.255.255.0 broadcast A.B.C.255 vlan 100 vlandev em0" ifconfig_carp0="vhid 1 advskew 100 pass abc A.B.C.3" ifconfig_pfsync0="up syncif em1" What i have is that when i'm pinging carp0 (inet) or carp1(lan) interface's ip address of my firewall - i'm receivind DUP responses. And when host2 is ths slave and i'm starting to ping carp0 address - no traffic appears on master host - that means that the local carp interface responding to my packets.. That means that in case some service (provided by jail managed by freevrrpd) will be accessed from outside - i cannot be sure what host will answer the request. I have done some tests. When i'm sshing to virtual IP - sometimes i'm getting ssh prompt and can login, and sometimes it says that host auth info is bad (yes, because second server answering me at this time) and sometimes i'm loosing ssh connection while session is active. net.inet.carp.preempt = 1 net.inet.carp.log=2 net.inet.carp.arpbalance=0 No ballance needed. I want to have some service run in main OS, some services run in jail and i want to be sure which host will answer the request when bouth hosts are up and running. Could please someone direct me what to do or where to read? Best regards, Anton Nikiforov From owner-freebsd-stable@FreeBSD.ORG Thu Jul 6 20:23:16 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0C63A16A4DD for ; Thu, 6 Jul 2006 20:23:16 +0000 (UTC) (envelope-from atanas@asd.aplus.net) Received: from pro20.abac.com (pro20.abac.com [66.226.64.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id A333543D49 for ; Thu, 6 Jul 2006 20:23:15 +0000 (GMT) (envelope-from atanas@asd.aplus.net) Received: from [216.55.129.5] (asd2.aplus.net [216.55.129.5]) (authenticated bits=0) by pro20.abac.com (8.13.6/8.13.6) with ESMTP id k66KNC4P061285 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 6 Jul 2006 13:23:12 -0700 (PDT) (envelope-from atanas@asd.aplus.net) Message-ID: <44AD7297.7080605@asd.aplus.net> Date: Thu, 06 Jul 2006 13:29:11 -0700 From: Atanas User-Agent: Thunderbird 1.5.0.4 (Macintosh/20060516) MIME-Version: 1.0 To: pyunyh@gmail.com References: <20060628225239.GA93265@dan.emsphone.com> <44A3394C.4090209@asd.aplus.net> <44A3817F.4030105@thebeastie.org> <20060629092154.GE742@turion.vk2pj.dyndns.org> <20060629083130.X1229@ganymede.hub.org> <44A4A02A.9060802@thebeastie.org> <20060630012615.Q1103@ganymede.hub.org> <44A57B71.6020201@asd.aplus.net> <20060701035416.GC54876@cdnetworks.co.kr> <44AC6793.2070608@asd.aplus.net> <20060706021444.GA76865@cdnetworks.co.kr> In-Reply-To: <20060706021444.GA76865@cdnetworks.co.kr> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 1.47 (SPF_SOFTFAIL) Cc: Peter Jeremy , freebsd-stable@freebsd.org, Michael Vince , User Freebsd Subject: Re: em device hangs on ifconfig alias ... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Jul 2006 20:23:16 -0000 Pyun YongHyeon said the following on 7/5/06 7:14 PM: > > Here is patch generated against RELENG_6. > OK, I just tested that, but it doesn't seem to make any difference. Here's what I did: I commented out the em device from my kernel (a 6-STABLE one from yesterday) and compiled three if_em kernel modules: - one taken from 6.1 release - the unpatched 6-STABLE one - the latter with the above patch applied So I was able to load and test each of these modules independently and without actually restarting the machine. I changed also the driver version string in if_em.c, just to ensure that I'm really loading the right em module by checking dmesg: em1: port 0xdc80-0xdcbf mem 0xfcfe0000-0xfcffffff irq 55 at device 4.1 on pci3 em1: Ethernet address: 00:04:23:b5:1b:ff em1: link state changed to UP I used 2 machines - one running 6.1-RELEASE and using fxp (I'll call it "FXP"), and the test one running 6-STABLE with em (I'll call it "EM"), and tried exchanging/moving an IP alias between them. FXP# ifconfig fxp0: flags=8843 mtu 1500 options=b inet 10.10.64.30 netmask 0xffffff00 broadcast 10.10.64.255 ether 00:e0:81:31:f4:1e media: Ethernet autoselect (100baseTX ) status: active EM# ifconfig em1: flags=8843 mtu 1500 options=b inet 10.10.64.63 netmask 0xffffff00 broadcast 10.10.64.255 ether 00:04:23:b5:1b:ff media: Ethernet autoselect (100baseTX ) status: active First I brought up an IP alias on the FXP machine: FXP# ifconfig fxp0 inet alias 10.10.64.40 netmask 255.255.255.255 and checked whether it's accessible from anywhere - yes. Then I moved that to EM: FXP# ifconfig fxp0 inet -alias 10.10.64.40 EM# ifconfig em1 inet alias 10.10.64.40 netmask 255.255.255.255 and checked again - no. It was accessible only from its own subnet (10.10.64.x), but not from anywhere else. Moving that back to FXP works, but moving it back to EM doesn't. The only way I found to make it accessible was to arping something from the aliased IP address: EM# arping -S10.10.64.40 -c1 somehost So it seems that when an IP alias has been recently used on some other machine (on FXP in my case), the em driver is unable to initialize that IP alias properly. It might be that the fxp driver is not sending something when releasing an alias, who knows. But fact is that fxp always initializes its aliases properly - I use it extensively and it always worked. I tried setting another IP alias that never has been used on these machines. I brought that up first on EM and it worked. The moved it to FXP and it also worked! But moving it back to EM made it inaccessible. It looks like there's something fishy with the alias initialization. Another related problem is that the card gets re-initialized (reset?) on each alias you add (takes between 0.3 and 1 seconds, depending how fast the hardware is), which for mass aliased systems could be a serious hurdle after a crash or reboot. Regards, Atanas > > > ------------------------------------------------------------------------ > > --- if_em.c.orig Fri May 19 09:19:57 2006 > +++ if_em.c Thu Jul 6 11:10:56 2006 > @@ -657,8 +657,9 @@ > > mtx_assert(&adapter->mtx, MA_OWNED); > > - if (!adapter->link_active) > - return; > + if ((ifp->if_drv_flags & (IFF_DRV_RUNNING|IFF_DRV_OACTIVE)) != > + IFF_DRV_RUNNING) > + return; > > while (!IFQ_DRV_IS_EMPTY(&ifp->if_snd)) { > > @@ -719,11 +720,6 @@ > if (adapter->in_detach) return(error); > > switch (command) { > - case SIOCSIFADDR: > - case SIOCGIFADDR: > - IOCTL_DEBUGOUT("ioctl rcv'd: SIOCxIFADDR (Get/Set Interface Addr)"); > - ether_ioctl(ifp, command, data); > - break; > case SIOCSIFMTU: > { > int max_frame_size; > @@ -760,16 +756,17 @@ > IOCTL_DEBUGOUT("ioctl rcv'd: SIOCSIFFLAGS (Set Interface Flags)"); > EM_LOCK(adapter); > if (ifp->if_flags & IFF_UP) { > - if (!(ifp->if_drv_flags & IFF_DRV_RUNNING)) { > + if ((ifp->if_drv_flags & IFF_DRV_RUNNING)) { > + if ((ifp->if_flags ^ adapter->if_flags) & > + IFF_PROMISC) { > + em_disable_promisc(adapter); > + em_set_promisc(adapter); > + } > + } else > em_init_locked(adapter); > - } > - > - em_disable_promisc(adapter); > - em_set_promisc(adapter); > } else { > - if (ifp->if_drv_flags & IFF_DRV_RUNNING) { > + if (ifp->if_drv_flags & IFF_DRV_RUNNING) > em_stop(adapter); > - } > } > EM_UNLOCK(adapter); > break; > @@ -835,8 +832,8 @@ > break; > } > default: > - IOCTL_DEBUGOUT1("ioctl received: UNKNOWN (0x%x)", (int)command); > - error = EINVAL; > + error = ether_ioctl(ifp, command, data); > + break; > } > > return(error); > --- if_em.h.orig Thu Jul 6 11:06:17 2006 > +++ if_em.h Thu Jul 6 11:06:41 2006 > @@ -331,6 +331,7 @@ > struct callout timer; > struct callout tx_fifo_timer; > int io_rid; > + int if_flags; > u_int8_t unit; > struct mtx mtx; > int em_insert_vlan_header; From owner-freebsd-stable@FreeBSD.ORG Thu Jul 6 20:27:39 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0A17916A4DE for ; Thu, 6 Jul 2006 20:27:39 +0000 (UTC) (envelope-from imb@protected-networks.net) Received: from aaron.protected-networks.net (aaron.protected-networks.net [202.12.127.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 792BB43D49 for ; Thu, 6 Jul 2006 20:27:38 +0000 (GMT) (envelope-from imb@protected-networks.net) Received: from localhost (localhost [127.0.0.1]) by aaron.protected-networks.net (Postfix) with ESMTP id BED4CC451; Thu, 6 Jul 2006 16:27:36 -0400 (EDT) Received: from aaron.protected-networks.net (localhost [127.0.0.1]) by aaron.protected-networks.net (Postfix) with ESMTP id 3F6DEC441; Thu, 6 Jul 2006 16:27:33 -0400 (EDT) Authentication-Results: aaron.protected-networks.net from=imb@protected-networks.net; domainkey=pass Received: from aaron.protected-networks.net (localhost [127.0.0.1]) by aaron.protected-networks.net (Postfix) with ESMTP id C90C0C43F; Thu, 6 Jul 2006 16:27:32 -0400 (EDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=200509; d=protected-networks.net; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:X-Enigmail-Version:OpenPGP:Content-Type:Content-Transfer-Encoding; b=CzNf+7/83clp9MEe6jIgjQYdv5DFG/Pajkx8Pnzq3ytlL8mUwADMN4E1v+9CuyQSsLLKcQ5vxMsrsJnuLiDpeo1mA4zwUZr8StHnJUrgCh0WFtVGK5677djd9vUW5cIG; Received: from [192.168.1.10] (c-24-218-147-31.hsd1.ma.comcast.net [24.218.147.31]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "Iain Michael Butler", Issuer "Protected Networks Certificate Authority" (verified OK)) by aaron.protected-networks.net (Postfix) with ESMTP id 6B7CDC3DB; Thu, 6 Jul 2006 16:27:32 -0400 (EDT) Message-ID: <44AD7230.6020605@protected-networks.net> Date: Thu, 06 Jul 2006 16:27:28 -0400 From: Michael Butler User-Agent: Thunderbird 1.5.0.4 (Windows/20060516) MIME-Version: 1.0 To: "Arnold Cavazos Jr." References: <20060706183253.GC61190@abcjr.net> In-Reply-To: <20060706183253.GC61190@abcjr.net> X-Enigmail-Version: 0.94.0.0 OpenPGP: id=BFCB1D4E Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: Dell PowerEdge 750 & 850 environtmental monitoring X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Jul 2006 20:27:39 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Arnold Cavazos Jr. wrote: | Does anybody have temperature and fan monitoring working on Dell | PowerEdge 750's & 850's? I have done my share of googling without much | luck. | Which monitoring tools have you tried, sysutils/mbmon? What sort of monitor hardware is it? - -- Michael Butler, CISSP Information Security Architect, Protected Networks http://www.protected-networks.net PGP Key ID: BFCB1D4E Key fingerprint: 8E29 5BD0 06F4 4ABB E819 67D3 45A0 6F77 BFCB 1D4E -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (MingW32) iD8DBQFErXIwRaBvd7/LHU4RAjkTAJ9kFUO1SLfsX3XAL+/8TxlKwLShsgCdHwi2 VDyjK2cWSLRhAgzYi81Av/w= =nFul -----END PGP SIGNATURE----- From owner-freebsd-stable@FreeBSD.ORG Thu Jul 6 22:24:46 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 39F8F16A4DE for ; Thu, 6 Jul 2006 22:24:46 +0000 (UTC) (envelope-from terry@tmk.com) Received: from server.tmk.com (server.tmk.com [204.141.35.63]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0725543D53 for ; Thu, 6 Jul 2006 22:24:45 +0000 (GMT) (envelope-from terry@tmk.com) Received: from tmk.com by tmk.com (PMDF V6.3 #37010) id <01M4H8CJWGIO0008EJ@tmk.com> for freebsd-stable@freebsd.org; Thu, 06 Jul 2006 18:24:44 -0400 (EDT) Date: Thu, 06 Jul 2006 18:21:38 -0400 (EDT) From: Terry Kennedy To: freebsd-stable@freebsd.org Message-id: <01M4H8H0UJ5G0008EJ@tmk.com> MIME-version: 1.0 Content-type: TEXT/PLAIN; CHARSET=us-ascii Subject: Re: Dell PowerEdge 750 & 850 environtmental monitoring X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Jul 2006 22:24:46 -0000 > Does anybody have temperature and fan monitoring working on Dell > PowerEdge 750's & 850's? I have done my share of googling without > much luck. With the DRAC III/XT card installed, I am monitoring PE750's using the IPMI device ("device ipmi" in the kernel config of 6.1-STABLE) and the ipmitool port. You can view the results at: http://www.tmk.com/cgi-bin/ipmi.cgi Terry Kennedy http://www.tmk.com terry@tmk.com New York, NY USA From owner-freebsd-stable@FreeBSD.ORG Fri Jul 7 00:59:59 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 96F4816A4DD for ; Fri, 7 Jul 2006 00:59:59 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from nz-out-0102.google.com (nz-out-0102.google.com [64.233.162.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id CF2C143D46 for ; Fri, 7 Jul 2006 00:59:58 +0000 (GMT) (envelope-from pyunyh@gmail.com) Received: by nz-out-0102.google.com with SMTP id i11so1123464nzi for ; Thu, 06 Jul 2006 17:59:58 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=VaDth/DLhXjBuS7wsBqgE8jXWCcAnhEE4Eck/LLXG5QSQ+c7sR06NhjEAz2yXQRc90yNCG1pDEh17xRnZqSMKl8O3b3O0MX0NfT/nRXeyH/QnkWDoRI35/Eq/WX2WxiCa0VRWnEZPMjMSmSgILX3Fo+B7adNJnQw79ZKNBUmflk= Received: by 10.36.127.4 with SMTP id z4mr1771532nzc; Thu, 06 Jul 2006 17:59:58 -0700 (PDT) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.gmail.com with ESMTP id 19sm16845359nzp.2006.07.06.17.59.55; Thu, 06 Jul 2006 17:59:57 -0700 (PDT) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.13.5/8.13.5) with ESMTP id k6713hO6083809 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 7 Jul 2006 10:03:43 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id k6713fsK083808; Fri, 7 Jul 2006 10:03:41 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Fri, 7 Jul 2006 10:03:41 +0900 From: Pyun YongHyeon To: Atanas Message-ID: <20060707010341.GD82406@cdnetworks.co.kr> References: <44A3817F.4030105@thebeastie.org> <20060629092154.GE742@turion.vk2pj.dyndns.org> <20060629083130.X1229@ganymede.hub.org> <44A4A02A.9060802@thebeastie.org> <20060630012615.Q1103@ganymede.hub.org> <44A57B71.6020201@asd.aplus.net> <20060701035416.GC54876@cdnetworks.co.kr> <44AC6793.2070608@asd.aplus.net> <20060706021444.GA76865@cdnetworks.co.kr> <44AD7297.7080605@asd.aplus.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <44AD7297.7080605@asd.aplus.net> User-Agent: Mutt/1.4.2.1i Cc: Peter Jeremy , freebsd-stable@freebsd.org, Michael Vince , User Freebsd Subject: Re: em device hangs on ifconfig alias ... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Jul 2006 00:59:59 -0000 On Thu, Jul 06, 2006 at 01:29:11PM -0700, Atanas wrote: > Pyun YongHyeon said the following on 7/5/06 7:14 PM: > > > >Here is patch generated against RELENG_6. > > > OK, I just tested that, but it doesn't seem to make any difference. > > Here's what I did: > > I commented out the em device from my kernel (a 6-STABLE one from > yesterday) and compiled three if_em kernel modules: > - one taken from 6.1 release > - the unpatched 6-STABLE one > - the latter with the above patch applied > > So I was able to load and test each of these modules independently and > without actually restarting the machine. I changed also the driver > version string in if_em.c, just to ensure that I'm really loading the > right em module by checking dmesg: > > em1: > port 0xdc80-0xdcbf mem 0xfcfe0000-0xfcffffff irq 55 at device 4.1 on pci3 > em1: Ethernet address: 00:04:23:b5:1b:ff > em1: link state changed to UP > > I used 2 machines - one running 6.1-RELEASE and using fxp (I'll call it > "FXP"), and the test one running 6-STABLE with em (I'll call it "EM"), > and tried exchanging/moving an IP alias between them. > > FXP# ifconfig > fxp0: flags=8843 mtu 1500 > options=b > inet 10.10.64.30 netmask 0xffffff00 broadcast 10.10.64.255 > ether 00:e0:81:31:f4:1e > media: Ethernet autoselect (100baseTX ) > status: active > > EM# ifconfig > em1: flags=8843 mtu 1500 > options=b > inet 10.10.64.63 netmask 0xffffff00 broadcast 10.10.64.255 > ether 00:04:23:b5:1b:ff > media: Ethernet autoselect (100baseTX ) > status: active > > First I brought up an IP alias on the FXP machine: > > FXP# ifconfig fxp0 inet alias 10.10.64.40 netmask 255.255.255.255 > > and checked whether it's accessible from anywhere - yes. Then I moved > that to EM: > > FXP# ifconfig fxp0 inet -alias 10.10.64.40 > EM# ifconfig em1 inet alias 10.10.64.40 netmask 255.255.255.255 > > and checked again - no. It was accessible only from its own subnet > (10.10.64.x), but not from anywhere else. > > Moving that back to FXP works, but moving it back to EM doesn't. The > only way I found to make it accessible was to arping something from the > aliased IP address: > > EM# arping -S10.10.64.40 -c1 somehost > > So it seems that when an IP alias has been recently used on some other > machine (on FXP in my case), the em driver is unable to initialize that > IP alias properly. > > It might be that the fxp driver is not sending something when releasing > an alias, who knows. But fact is that fxp always initializes its aliases > properly - I use it extensively and it always worked. > > I tried setting another IP alias that never has been used on these > machines. I brought that up first on EM and it worked. The moved it to > FXP and it also worked! But moving it back to EM made it inaccessible. > Hmm, that's strange. I've double checked that stock em(4) didn't generate ARP packets when its addresses were changed. So I made em(4) generate ARP. Could you see a gratuitous ARP with tcpdump when you change its address? > It looks like there's something fishy with the alias initialization. > > Another related problem is that the card gets re-initialized (reset?) on > each alias you add (takes between 0.3 and 1 seconds, depending how fast > the hardware is), which for mass aliased systems could be a serious > hurdle after a crash or reboot. > This is other issue. em(4) performs two time-consuming operations in its initialization routine. One is DMA tag/map creation and the other is checksumming EEPROM contents in init routine. I have an experimental patch for it but let's fix one at a time. -- Regards, Pyun YongHyeon From owner-freebsd-stable@FreeBSD.ORG Fri Jul 7 01:48:47 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D44FB16A4DF; Fri, 7 Jul 2006 01:48:47 +0000 (UTC) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 83F9F43D45; Fri, 7 Jul 2006 01:48:47 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.13.0/8.13.0) with ESMTP id k671mkiI001738; Thu, 6 Jul 2006 18:48:46 -0700 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id k671mkhi001737; Thu, 6 Jul 2006 18:48:46 -0700 Date: Thu, 6 Jul 2006 18:48:46 -0700 From: Brooks Davis To: "[LoN]Kamikaze" Message-ID: <20060707014846.GB500@odin.ac.hmc.edu> References: <44AC5D39.4010502@gmx.de> <20060706011015.GA6677@odin.ac.hmc.edu> <44ACD177.1000204@gmx.de> <20060706152403.GA13815@odin.ac.hmc.edu> <44AD3495.9090603@gmx.de> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="gatW/ieO32f1wygP" Content-Disposition: inline In-Reply-To: <44AD3495.9090603@gmx.de> User-Agent: Mutt/1.4.1i X-Virus-Scanned: by amavisd-new Cc: freebsd-stable@freebsd.org, freebsd-ports@freebsd.org Subject: Re: pkg_version confused by architecutre in package name X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Jul 2006 01:48:47 -0000 --gatW/ieO32f1wygP Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jul 06, 2006 at 06:04:37PM +0200, [LoN]Kamikaze wrote: >=20 > Brooks Davis wrote: > > On Thu, Jul 06, 2006 at 11:01:43AM +0200, [LoN]Kamikaze wrote: > >> Brooks Davis wrote: > >>> On Thu, Jul 06, 2006 at 02:45:45AM +0200, [LoN]Kamikaze wrote: > >>>> I normally run the command > >>>> # pkg_version -Iv | grep \< > >>>> before running 'portupgrade -a', to see what's going to happen. This= time I got the following output: > >>>> > >>>> diablo-jdk-freebsd6.i386.1.5.0.07.00 < needs updating (index has = 1.5.0.07.00) > >>>> > >>>> It seems that the tool is confused by the i386 in the package name. > >>> Actually I think it's confused by the fact that the package name is > >>> "diablo-jdk" and the version is "freebsd6.i386.1.5.0.07.00". That's > >>> just plain bogus. > >>> > >> So who is at fault? The ports infrastructure or the FreeBSD foundation? > >=20 > > I don't know. How did you install it? >=20 > # pkg_add diablo-jdk-freebsd6.i386.1.5.0.07.00.tbz It definitly installs correctly if you use the port instead of the package. It looks like the package is incorrect. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --gatW/ieO32f1wygP Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFErb1+XY6L6fI4GtQRAqieAJ9Awy0DmSKJ3+u3lzTvdpxVktV/aQCbBchf Hos4btNETdKzkff/BB6IfP4= =FhUT -----END PGP SIGNATURE----- --gatW/ieO32f1wygP-- From owner-freebsd-stable@FreeBSD.ORG Fri Jul 7 02:01:30 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4A94F16A4DA; Fri, 7 Jul 2006 02:01:30 +0000 (UTC) (envelope-from mikej@rogers.com) Received: from H43.C18.B96.tor.eicat.ca (H43.C18.B96.tor.eicat.ca [66.96.18.43]) by mx1.FreeBSD.org (Postfix) with ESMTP id DCBC443D4C; Fri, 7 Jul 2006 02:01:29 +0000 (GMT) (envelope-from mikej@rogers.com) Received: from [127.0.0.1] (desktop.home.local [172.16.0.200]) by H43.C18.B96.tor.eicat.ca (Postfix) with ESMTP id 24BB7114F3; Thu, 6 Jul 2006 22:00:53 -0400 (EDT) Message-ID: <44ADC08B.8000408@rogers.com> Date: Thu, 06 Jul 2006 22:01:47 -0400 From: Mike Jakubik User-Agent: Thunderbird 1.5.0.4 (Windows/20060516) MIME-Version: 1.0 To: obrien@freebsd.org References: <20060629193346.GA2548@dragon.NUXI.org> <44AD6756.4070008@rogers.com> In-Reply-To: <44AD6756.4070008@rogers.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SpamToaster-Information: This messages has been scanned by SpamToaster http://www.digitalprogression.ca X-SpamToaster: Found to be clean X-SpamToaster-SpamCheck: not spam, SpamAssassin (not cached, score=-2.49, required 3.5, ALL_TRUSTED -1.80, AWL 0.00, BAYES_00 -2.60, DK_POLICY_SIGNSOME 0.00, DNS_FROM_RFC_ABUSE 0.20, DNS_FROM_RFC_POST 1.71) X-SpamToaster-From: mikej@rogers.com X-Spam-Status: No Cc: stable@freebsd.org, freebsd-current@freebsd.org Subject: Re: Still getting 'calcru: runtime went backwards' X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Jul 2006 02:01:30 -0000 I'm getting a ton of them now, and i found a way to reproduce them. Basically i run a compile session in one terminal, say make buildkernel, and run top in another. As soon as i run top, the messages appear, and they seem to be synchronized with the refresh rate of top, 2 messages per refresh. This is on a 6.1-STABLE as of today. --- calcru: negative runtime of -261273 usec for pid 12 (swi4: clock) calcru: negative runtime of -261273 usec for pid 12 (swi4: clock) calcru: negative runtime of -259691 usec for pid 12 (swi4: clock) ... From owner-freebsd-stable@FreeBSD.ORG Fri Jul 7 02:06:08 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0E7CB16A4DA for ; Fri, 7 Jul 2006 02:06:08 +0000 (UTC) (envelope-from atanas@asd.aplus.net) Received: from pro20.abac.com (pro20.abac.com [66.226.64.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id BB68143D76 for ; Fri, 7 Jul 2006 02:06:01 +0000 (GMT) (envelope-from atanas@asd.aplus.net) Received: from [216.55.129.5] (asd2.aplus.net [216.55.129.5]) (authenticated bits=0) by pro20.abac.com (8.13.6/8.13.6) with ESMTP id k6725uCj015043 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 6 Jul 2006 19:05:56 -0700 (PDT) (envelope-from atanas@asd.aplus.net) Message-ID: <44ADC2ED.4070904@asd.aplus.net> Date: Thu, 06 Jul 2006 19:11:57 -0700 From: Atanas User-Agent: Thunderbird 1.5.0.4 (Macintosh/20060516) MIME-Version: 1.0 To: pyunyh@gmail.com References: <44A3817F.4030105@thebeastie.org> <20060629092154.GE742@turion.vk2pj.dyndns.org> <20060629083130.X1229@ganymede.hub.org> <44A4A02A.9060802@thebeastie.org> <20060630012615.Q1103@ganymede.hub.org> <44A57B71.6020201@asd.aplus.net> <20060701035416.GC54876@cdnetworks.co.kr> <44AC6793.2070608@asd.aplus.net> <20060706021444.GA76865@cdnetworks.co.kr> <44AD7297.7080605@asd.aplus.net> <20060707010341.GD82406@cdnetworks.co.kr> In-Reply-To: <20060707010341.GD82406@cdnetworks.co.kr> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 1.47 (SPF_SOFTFAIL) Cc: Peter Jeremy , freebsd-stable@freebsd.org, Michael Vince , User Freebsd Subject: Re: em device hangs on ifconfig alias ... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Jul 2006 02:06:08 -0000 Pyun YongHyeon said the following on 7/6/06 6:03 PM: > > Hmm, that's strange. I've double checked that stock em(4) didn't > generate ARP packets when its addresses were changed. So I made > em(4) generate ARP. Could you see a gratuitous ARP with tcpdump > when you change its address? > I just left a "tcpdump -n arp host 10.10.64.40" on a third machine sniffing around and tested all em module versions I had (the stock 6.1, 6-STABLE and 6-STABLE with your patch), but got silence on all three: EM# ifconfig em1 inet alias 10.10.64.40 EM# ifconfig em1 inet -alias 10.10.64.40 The fxp driver appears to send something on startup and nothing on shutdown: FXP# ifconfig fxp0 inet alias 10.10.64.40 18:41:54.584059 arp who-has 10.10.64.40 tell 10.10.64.40 FXP# ifconfig fxp0 inet -alias 10.10.64.40 When I manually arping the em alias after startup (i.e. simulate what fxp does), everything works as expected: EM# ifconfig em1 inet alias 10.10.64.40 EM# arping -c1 -S10.10.64.40 10.10.64.40 18:46:07.808701 arp who-has 10.10.64.40 tell 10.10.64.40 EM# ifconfig em1 inet -alias 10.10.64.40 It appears that this is what the em driver is supposed to do, or at least fxp does it in this way. > This is other issue. em(4) performs two time-consuming operations > in its initialization routine. One is DMA tag/map creation and the > other is checksumming EEPROM contents in init routine. > I have an experimental patch for it but let's fix one at a time. > OK, let's put that aside for now. Regards, Atanas From owner-freebsd-stable@FreeBSD.ORG Fri Jul 7 04:05:02 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5038716A4DA for ; Fri, 7 Jul 2006 04:05:02 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from nz-out-0102.google.com (nz-out-0102.google.com [64.233.162.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id 92E4C43D49 for ; Fri, 7 Jul 2006 04:05:01 +0000 (GMT) (envelope-from pyunyh@gmail.com) Received: by nz-out-0102.google.com with SMTP id i11so1140120nzi for ; Thu, 06 Jul 2006 21:05:01 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=tFmjRYp0NcW4P2WKThJINLbyM3vCtN5VWFqbGijKZx+MC7tu7VPFJXA+hQKHVrOsXnBPFMH3z0H/4+F2/6Nx3Lun7zMS/Qc6EENb7GL9KAWLKgHEnUHBNnNLC6u1rzjDfDPs1UfTbhOX/6yngpeFdhL3e3gN+pOaZn1sKp1s1+8= Received: by 10.36.105.17 with SMTP id d17mr1920527nzc; Thu, 06 Jul 2006 21:05:00 -0700 (PDT) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.gmail.com with ESMTP id 20sm10867752nzp.2006.07.06.21.04.58; Thu, 06 Jul 2006 21:05:00 -0700 (PDT) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.13.5/8.13.5) with ESMTP id k6748iCF084317 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 7 Jul 2006 13:08:44 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id k6748dLv084316; Fri, 7 Jul 2006 13:08:39 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Fri, 7 Jul 2006 13:08:38 +0900 From: Pyun YongHyeon To: Atanas Message-ID: <20060707040838.GE82406@cdnetworks.co.kr> References: <20060629083130.X1229@ganymede.hub.org> <44A4A02A.9060802@thebeastie.org> <20060630012615.Q1103@ganymede.hub.org> <44A57B71.6020201@asd.aplus.net> <20060701035416.GC54876@cdnetworks.co.kr> <44AC6793.2070608@asd.aplus.net> <20060706021444.GA76865@cdnetworks.co.kr> <44AD7297.7080605@asd.aplus.net> <20060707010341.GD82406@cdnetworks.co.kr> <44ADC2ED.4070904@asd.aplus.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <44ADC2ED.4070904@asd.aplus.net> User-Agent: Mutt/1.4.2.1i Cc: Peter Jeremy , freebsd-stable@freebsd.org, Michael Vince , User Freebsd Subject: Re: em device hangs on ifconfig alias ... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Jul 2006 04:05:02 -0000 On Thu, Jul 06, 2006 at 07:11:57PM -0700, Atanas wrote: > Pyun YongHyeon said the following on 7/6/06 6:03 PM: > > > >Hmm, that's strange. I've double checked that stock em(4) didn't > >generate ARP packets when its addresses were changed. So I made > >em(4) generate ARP. Could you see a gratuitous ARP with tcpdump > >when you change its address? > > > I just left a "tcpdump -n arp host 10.10.64.40" on a third machine > sniffing around and tested all em module versions I had (the stock 6.1, > 6-STABLE and 6-STABLE with your patch), but got silence on all three: > That's odd. I've tested it on CURRENT and I could see the ARP packet. Are you sure you patched correctly? If so I have to build a RELENG_6 machine and give it try. > EM# ifconfig em1 inet alias 10.10.64.40 > > EM# ifconfig em1 inet -alias 10.10.64.40 > > It's normal. > The fxp driver appears to send something on startup and nothing on > shutdown: > > FXP# ifconfig fxp0 inet alias 10.10.64.40 > 18:41:54.584059 arp who-has 10.10.64.40 tell 10.10.64.40 > FXP# ifconfig fxp0 inet -alias 10.10.64.40 > > > When I manually arping the em alias after startup (i.e. simulate what > fxp does), everything works as expected: > > EM# ifconfig em1 inet alias 10.10.64.40 > > EM# arping -c1 -S10.10.64.40 10.10.64.40 > 18:46:07.808701 arp who-has 10.10.64.40 tell 10.10.64.40 Because arping requested it em(4) generated it. > EM# ifconfig em1 inet -alias 10.10.64.40 > > > It appears that this is what the em driver is supposed to do, or at > least fxp does it in this way. > No, it's an em(4) driver bug. fxp(4)'s behavior is correct. > >This is other issue. em(4) performs two time-consuming operations > >in its initialization routine. One is DMA tag/map creation and the > >other is checksumming EEPROM contents in init routine. > >I have an experimental patch for it but let's fix one at a time. > > > OK, let's put that aside for now. > > Regards, > Atanas > -- Regards, Pyun YongHyeon From owner-freebsd-stable@FreeBSD.ORG Fri Jul 7 07:17:19 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4E30E16A4DE for ; Fri, 7 Jul 2006 07:17:19 +0000 (UTC) (envelope-from nvass@teledomenet.gr) Received: from matrix.teledomenet.gr (dns1.teledomenet.gr [213.142.128.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9099543D53 for ; Fri, 7 Jul 2006 07:17:17 +0000 (GMT) (envelope-from nvass@teledomenet.gr) Received: from iris ([192.168.1.71]) by matrix.teledomenet.gr (8.12.10/8.12.10) with ESMTP id k677HGEY004782; Fri, 7 Jul 2006 10:17:16 +0300 From: Nikos Vassiliadis To: freebsd-stable@freebsd.org Date: Fri, 7 Jul 2006 10:14:29 +0300 User-Agent: KMail/1.9.1 References: <44AD688A.6050408@nikiforov.ru> In-Reply-To: <44AD688A.6050408@nikiforov.ru> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200607071014.29700.nvass@teledomenet.gr> Cc: Anton Nikiforov Subject: Re: carp+pfsync+freevrrpd+jail X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Jul 2006 07:17:19 -0000 On Thursday 06 July 2006 22:46, Anton Nikiforov wrote: > Dear all. [snip] > > That means that in case some service (provided by jail managed by > freevrrpd) will be accessed from outside - i cannot be sure what host > will answer the request. > You have vrrp on jails and carp on the host system? That's probably not a good idea, they both use the same ether-type. Who is gonna get the incoming packet? carp or freevrrpd? both? I guess both. Who is gonna reply? Do you know if a vrrp packet confuses carp or conversely? nik:0:~$ grep carp /etc/protocols carp 112 CARP vrrp # Common Address Redundancy Protocol From owner-freebsd-stable@FreeBSD.ORG Fri Jul 7 07:17:26 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B30A616A508 for ; Fri, 7 Jul 2006 07:17:26 +0000 (UTC) (envelope-from LoN_Kamikaze@gmx.de) Received: from mail.gmx.net (mail.gmx.net [213.165.64.21]) by mx1.FreeBSD.org (Postfix) with SMTP id 43C7B43D5C for ; Fri, 7 Jul 2006 07:17:25 +0000 (GMT) (envelope-from LoN_Kamikaze@gmx.de) Received: (qmail invoked by alias); 07 Jul 2006 07:17:23 -0000 Received: from p54A7D531.dip.t-dialin.net (EHLO [192.168.0.12]) [84.167.213.49] by mail.gmx.net (mp037) with SMTP; 07 Jul 2006 09:17:23 +0200 X-Authenticated: #5465401 Message-ID: <44AE0A69.20101@gmx.de> Date: Fri, 07 Jul 2006 09:16:57 +0200 From: "[LoN]Kamikaze" Organization: Lords of Nightmare User-Agent: Thunderbird 1.5.0.4 (X11/20060605) MIME-Version: 1.0 To: Brooks Davis References: <44AC5D39.4010502@gmx.de> <20060706011015.GA6677@odin.ac.hmc.edu> <44ACD177.1000204@gmx.de> <20060706152403.GA13815@odin.ac.hmc.edu> <44AD3495.9090603@gmx.de> <20060707014846.GB500@odin.ac.hmc.edu> In-Reply-To: <20060707014846.GB500@odin.ac.hmc.edu> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 Cc: freebsd-stable@freebsd.org, freebsd-ports@freebsd.org Subject: Re: pkg_version confused by architecutre in package name X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Jul 2006 07:17:26 -0000 Brooks Davis wrote: > On Thu, Jul 06, 2006 at 06:04:37PM +0200, [LoN]Kamikaze wrote: >> Brooks Davis wrote: >>> On Thu, Jul 06, 2006 at 11:01:43AM +0200, [LoN]Kamikaze wrote: >>>> Brooks Davis wrote: >>>>> On Thu, Jul 06, 2006 at 02:45:45AM +0200, [LoN]Kamikaze wrote: >>>>>> I normally run the command >>>>>> # pkg_version -Iv | grep \< >>>>>> before running 'portupgrade -a', to see what's going to happen. This time I got the following output: >>>>>> >>>>>> diablo-jdk-freebsd6.i386.1.5.0.07.00 < needs updating (index has 1.5.0.07.00) >>>>>> >>>>>> It seems that the tool is confused by the i386 in the package name. >>>>> Actually I think it's confused by the fact that the package name is >>>>> "diablo-jdk" and the version is "freebsd6.i386.1.5.0.07.00". That's >>>>> just plain bogus. >>>>> >>>> So who is at fault? The ports infrastructure or the FreeBSD foundation? >>> I don't know. How did you install it? >> # pkg_add diablo-jdk-freebsd6.i386.1.5.0.07.00.tbz > > It definitly installs correctly if you use the port instead of the > package. It looks like the package is incorrect. > Yes, that fixed it. So I guess the FreeBSD foundation is at fault. From owner-freebsd-stable@FreeBSD.ORG Fri Jul 7 08:27:27 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EF4A216A4DA for ; Fri, 7 Jul 2006 08:27:27 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from cs1.cs.huji.ac.il (cs1.cs.huji.ac.il [132.65.16.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 795E643D45 for ; Fri, 7 Jul 2006 08:27:27 +0000 (GMT) (envelope-from danny@cs.huji.ac.il) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by cs1.cs.huji.ac.il with esmtp id 1FylgM-000BTi-I7 for freebsd-stable@freebsd.org; Fri, 07 Jul 2006 11:27:26 +0300 X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.2 To: freebsd-stable@freebsd.org In-reply-to: References: Comments: In-reply-to Danny Braniss message dated "Wed, 05 Jul 2006 13:46:44 +0300." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 07 Jul 2006 11:27:26 +0300 From: Danny Braniss Message-ID: Subject: Re: mountd changed? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Jul 2006 08:27:28 -0000 > something has changed wrt nmount(2)/mountd(8)/exports(5): > > > cat /etc/exports > /h -alldirs -network 132.65.0.0 -mask 255.255.0.0 > > cat /etc/fstab > /dev/da1s1d /h ufs rw 1 1 > > and all is fine, the filesystem is exported and accesible. > > # /etc/rc.d/mountd reload > Reloading mountd config files. > > but /var/log/messages: > mountd[473]: can't change attributes for /h > mountd[473]: bad exports list line /h -alldirs -network 132.65.0.0 -mask > 255.255.0.0 > > btw, nothing has changed in the /etc/exports file. > 2nd, the root (/) is nfs readonly. > and now any attempt to mount is denied. > just in case: kern.securelevel: -1 > the problem is solved. see http://www.freebsd.org/cgi/query-pr.cgi?pr=99873 danny From owner-freebsd-stable@FreeBSD.ORG Fri Jul 7 09:17:48 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C4CF016A4DA for ; Fri, 7 Jul 2006 09:17:48 +0000 (UTC) (envelope-from dkirhlarov@oilspace.com) Received: from office.oilspace.com (ns2.oilspace.com [194.129.65.230]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1741E43D45 for ; Fri, 7 Jul 2006 09:17:47 +0000 (GMT) (envelope-from dkirhlarov@oilspace.com) Received: from dimma.mow.oilspace.com (hq.oilspace.com [81.222.156.185]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by office.oilspace.com (Postfix) with ESMTP id D5C7D136CDB for ; Fri, 7 Jul 2006 10:17:36 +0100 (BST) Received: from dimma.mow.oilspace.com (localhost [127.0.0.1]) by dimma.mow.oilspace.com (8.13.4/8.13.3) with ESMTP id k679Ha03040354 for ; Fri, 7 Jul 2006 13:17:36 +0400 (MSD) (envelope-from dkirhlarov@localhost.oilspace.com) Received: (from dkirhlarov@localhost) by dimma.mow.oilspace.com (8.13.4/8.13.3/Submit) id k679HZOk040353 for freebsd-stable@freebsd.org; Fri, 7 Jul 2006 13:17:35 +0400 (MSD) (envelope-from dkirhlarov) Date: Fri, 7 Jul 2006 13:17:35 +0400 From: Dmitriy Kirhlarov To: freebsd-stable@freebsd.org Message-ID: <20060707091734.GA38936@dimma.mow.oilspace.com> Mail-Followup-To: freebsd-stable@freebsd.org References: <44AD688A.6050408@nikiforov.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <44AD688A.6050408@nikiforov.ru> X-Mailer: Mutt-ng devel (2005-03-13) based on Mutt 1.5.9 X-Operating-System: FreeBSD 5.4-STABLE User-Agent: mutt-ng/devel-r581 (FreeBSD) Subject: Re: carp+pfsync+freevrrpd+jail X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Jul 2006 09:17:49 -0000 Hi! First of all. If you're using carp, you need ports/net/ifstated, not freevrrpd. On Thu, Jul 06, 2006 at 11:46:18PM +0400, Anton Nikiforov wrote: > What i have is that when i'm pinging carp0 (inet) or carp1(lan) > interface's ip address of my firewall - i'm receivind DUP responses. One from carp and other from freevrrpd. > And when host2 is ths slave and i'm starting to ping carp0 address - > no traffic appears on master host - that means that the local carp > interface responding to my packets.. Yep. Full standby mode (backup don't have shared IP) is not implemented now. > That means that in case some service (provided by jail managed by > freevrrpd) will be accessed from outside - i cannot be sure what > host will answer the request. I don't understand your idea. Do you want to start-stop jail, when master node is down-up? > I have done some tests. When i'm sshing to virtual IP - sometimes > i'm getting ssh prompt and can login, and sometimes it says that > host auth info is bad (yes, because second server answering me at > this time) and sometimes i'm loosing ssh connection while session is > active. Use 'advbase' and 'advskew' params on both hosts for hard managing status of nodes. > No ballance needed. I want to have some service run in main OS, some > services run in jail and i want to be sure which host will answer > the request when bouth hosts are up and running. Be careful, if you want to use carp IP inside jail. Only master node can get data from external world. I tried to make this schema: ldap1 / \ ldapn1 ldapn2 | | | | | | clients clients Where ldap1 -- master ldap server. ldapn1, ldapn2 -- jail on different hosts on carp shared IP. They connect to ldap1 and get fresh data from master ldap server. I found, that only master node can start successfully. Jail on backup node can't start, because ldap server can't start. It can't start, because, it can't successfully connect to ldap1. ldapn2 sends SYN, ldap1 returns SYN+ACK, and switch delivers this packet to ldapn1 -- active master node. In order to have this schema working, both nodes must have personal IP and shared IP, but it's impossible within current jail implementation. WBR -- Dmitriy Kirhlarov OILspace, 26 Leninskaya sloboda, bld. 2, 2nd floor, 115280 Moscow, Russia P:+7 495 105 7247 ext.203 F:+7 495 105 7246 E:DmitriyKirhlarov@oilspace.com OILspace - The resource enriched - www.oilspace.com From owner-freebsd-stable@FreeBSD.ORG Fri Jul 7 12:34:55 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5AA4A16A4E9 for ; Fri, 7 Jul 2006 12:34:55 +0000 (UTC) (envelope-from freebsd-listen@fabiankeil.de) Received: from smtprelay01.ispgateway.de (smtprelay01.ispgateway.de [80.67.18.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id D03CD43DA4 for ; Fri, 7 Jul 2006 12:34:47 +0000 (GMT) (envelope-from freebsd-listen@fabiankeil.de) Received: (qmail 13889 invoked from network); 7 Jul 2006 12:34:45 -0000 Received: from unknown (HELO localhost) (775067@[217.50.128.20]) (envelope-sender ) by smtprelay01.ispgateway.de (qmail-ldap-1.03) with SMTP for ; 7 Jul 2006 12:34:45 -0000 Date: Fri, 7 Jul 2006 14:34:36 +0200 From: Fabian Keil To: freebsd-stable@freebsd.org Message-ID: <20060707143436.3716f63c@localhost> In-Reply-To: <20060703112705.0da6a071@localhost> References: <20060627175853.765a590e@localhost> <20060628101729.J50845@fledge.watson.org> <20060702173338.00a5ed44@localhost> <20060702170843.C67344@fledge.watson.org> <20060702190520.3b344c83@localhost> <20060702182302.H80381@fledge.watson.org> <20060702212335.0bf121be@localhost> <20060703112705.0da6a071@localhost> X-Mailer: Sylpheed-Claws 2.3.1 (GTK+ 2.8.19; i386-portbld-freebsd6.1) X-PGP-KEY-URL: http://www.fabiankeil.de/gpg-keys/freebsd-listen-2006-08-19.asc Mime-Version: 1.0 Content-Type: multipart/signed; boundary="Sig_rOmSZeS.=Tok48PT5q5OvEt"; protocol="application/pgp-signature"; micalg=PGP-SHA1 Cc: Peter Thoenen , Robert Watson Subject: Re: FreeBSD 6.1 Tor issues (Once More, with Feeling) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Jul 2006 12:34:55 -0000 --Sig_rOmSZeS.=Tok48PT5q5OvEt Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Fabian Keil wrote: > Fabian Keil wrote: >=20 > > Robert Watson wrote: >=20 > > > It sounds like your serial console server may not know how to map > > > SSH break signals into remote serial break signals. Try > > > ALT_BREAK_TO_DEBUGGER. Here's the description from NOTES: > > >=20 > > > # Solaris implements a new BREAK which is initiated by a character > > > # sequence CR ~ ^b which is similar to a familiar pattern used on > > > # Sun servers by the Remote Console. > > > options ALT_BREAK_TO_DEBUGGER > >=20 > > It took me several attempts to get the character sequence right, > > but yes, this one works. Thanks. >=20 > Unfortunately it didn't work while the system was hanging > this morning. Since then I got one or two hangs a day and entering the debugger never worked out, even if my console connection was opened a few minutes before the hang. I no longer think it has anything to do with the terminal server, but assume the hang takes the console with it. sio0 is running on acpi0, so I tried to disable acpi to see if it changes anything, but the only change I got was that fxp0 stopped working (it is up but only produces timeout warnings). I tried to partly disable acpi subsystems like described in acpi(4), but either I got the syntax wrong, or it just isn't working. Can someone on this list confirm or deny if something like debug.acpi.disabled=3Disa in /boot/loader.conf makes sense? That's how I understand the man page, but I don't see any reaction. I also tried /etc/sysctl.conf (which probably is parsed too late anyway) but I just got a message that the sysctl does not exists. sysctl debug.acpi indeed only shows: debug.acpi.do_powerstate: 1 debug.acpi.acpi_ca_version: 0x20041119 debug.acpi.semaphore_debug: 0 so maybe I need some special acpi options or it just doesn't work if acpi is loaded as a module, but as least the man page has no such hints. Fabian --=20 http://www.fabiankeil.de/ --Sig_rOmSZeS.=Tok48PT5q5OvEt Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) iD8DBQFErlTjjV8GA4rMKUQRApNNAJsH09z9tikl6IUiGrRinlnBq7MsBgCcDTVB zGUFzqf/s1gt2Laewkkc1cc= =n6nj -----END PGP SIGNATURE----- --Sig_rOmSZeS.=Tok48PT5q5OvEt-- From owner-freebsd-stable@FreeBSD.ORG Fri Jul 7 13:33:31 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 31BE116A4DA for ; Fri, 7 Jul 2006 13:33:31 +0000 (UTC) (envelope-from ob@gruft.de) Received: from obh.snafu.de (obh.snafu.de [213.73.92.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id AEA0643D53 for ; Fri, 7 Jul 2006 13:33:30 +0000 (GMT) (envelope-from ob@gruft.de) Received: from ob by obh.snafu.de with local (Exim 4.62 (FreeBSD)) (envelope-from ) id 1FyqSX-000Fwl-KX for freebsd-stable@freebsd.org; Fri, 07 Jul 2006 15:33:29 +0200 Date: Fri, 7 Jul 2006 15:33:29 +0200 From: Oliver Brandmueller To: freebsd-stable@freebsd.org Message-ID: <20060707133329.GE32936@e-Gitt.NET> Mail-Followup-To: freebsd-stable@freebsd.org References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="f0KYrhQ4vYSV2aJu" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.11 Sender: Oliver Brandmueller Subject: Re: mountd changed? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Jul 2006 13:33:31 -0000 --f0KYrhQ4vYSV2aJu Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi. On Fri, Jul 07, 2006 at 11:27:26AM +0300, Danny Braniss wrote: > the problem is solved. see=20 > http://www.freebsd.org/cgi/query-pr.cgi?pr=3D99873 I had the same problem. patch applied and all is fine! Thanx! - Oliver --=20 | Oliver Brandmueller | Offenbacher Str. 1 | Germany D-14197 Berlin | | Fon +49-172-3130856 | Fax +49-172-3145027 | WWW: http://the.addict.de/ | | Ich bin das Internet. Sowahr ich Gott helfe. | | Eine gewerbliche Nutzung aller enthaltenen Adressen ist nicht gestattet! | --f0KYrhQ4vYSV2aJu Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) iD8DBQFErmKpiqtMdzjafykRAharAKDEvUZTHT0hbgCHx3WYiz5SYBnrsgCgv7Dx JP45WQ8syHBb4t5HWnoz9B8= =I4/6 -----END PGP SIGNATURE----- --f0KYrhQ4vYSV2aJu-- From owner-freebsd-stable@FreeBSD.ORG Fri Jul 7 13:40:55 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 71D4116A4DA for ; Fri, 7 Jul 2006 13:40:55 +0000 (UTC) (envelope-from quetzal@zone3000.net) Received: from mx1.sitevalley.com (sitevalley.com [209.67.60.43]) by mx1.FreeBSD.org (Postfix) with SMTP id F405043D46 for ; Fri, 7 Jul 2006 13:40:54 +0000 (GMT) (envelope-from quetzal@zone3000.net) Received: from zone3000.kharkov.ua (HELO localhost) (217.144.68.98) by 209.67.61.254 with SMTP; 7 Jul 2006 13:40:53 -0000 Date: Fri, 7 Jul 2006 16:40:26 +0300 From: Nikolay Pavlov To: freebsd-stable@freebsd.org Message-ID: <20060707134026.GA1750@zone3000.net> Mail-Followup-To: Nikolay Pavlov , freebsd-stable@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 6.1-RELEASE Subject: Processes in block state in vmstat. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Jul 2006 13:40:55 -0000 Hi, folks. I want to add some additional information about problem related processes in block state. I see it on my server Dual CPU: Intel(R) Xeon(TM) CPU 2.40GHz (2399.33-MHz 686-class CPU) with amrd device. FreeBSD 6.1-RELEASE-p1 I see some httpd daemons in D state: procs memory page disk faults cpu r b w avm fre flt re pi po fr sr am0 in sy cs us sy id 0 527 0 2173832 94028 49 0 0 0 2722 2658 0 9219 4140 17350 1 7 92 0 528 0 2172836 93636 66 0 0 0 218 0 6 504 512 1221 0 2 98 0 523 0 2171828 93360 56 0 0 0 188 0 6 551 298 1286 0 2 98 0 523 0 2171972 92612 29 0 0 0 189 0 6 520 395 1250 0 2 98 30 494 0 2170976 91836 92 0 0 0 333 0 11 448 250 970 0 2 98 0 518 0 2171156 90580 43 1 0 0 314 0 10 640 758 1676 0 3 97 0 510 0 2170244 89452 61 0 0 0 402 0 14 615 644 1667 0 3 97 1 512 0 2170420 89292 1 0 0 0 0 0 0 493 307 1133 0 2 98 0 517 0 2169560 86868 110 0 0 0 735 0 27 623 852 1584 0 3 96 0 514 0 2168552 87176 53 0 0 0 198 0 0 487 200 1078 0 1 99 0 517 0 2178752 84040 1523 0 0 0 1261 0 0 512 2660 1320 2 3 96 vmstat -s 3129790854 cpu context switches 1663101011 device interrupts 5504551 software interrupts 9321603 traps 746764672 system calls 54 kernel threads created 66887 fork() calls 9669 vfork() calls 0 rfork() calls 4784 swap pager pageins 5635 swap pager pages paged in 1902 swap pager pageouts 3590 swap pager pages paged out 24668 vnode pager pageins 64050 vnode pager pages paged in 0 vnode pager pageouts 0 vnode pager pages paged out 28140 page daemon wakeups 479450699 pages examined by the page daemon 75270 pages reactivated 2461680 copy-on-write faults 3805 copy-on-write optimized faults 4531914 zero fill pages zeroed 2732630 zero fill pages prezeroed 18095 intransit blocking page faults 8922821 total VM faults taken 0 pages affected by kernel thread creation 8018826 pages affected by fork() 1107169 pages affected by vfork() 0 pages affected by rfork() 491039188 pages freed 393 pages freed by daemon 5744590 pages freed by exiting processes 201969 pages active 184930 pages inactive 17190 pages in VM cache 107624 pages wired down 750 pages free 4096 bytes per page 30979017 total name lookups cache hits (82% pos + 1% neg) system 1% per-directory deletions 0%, falsehits 0%, toolong 0% vmstat -z ITEM SIZE LIMIT USED FREE REQUESTS UMA Kegs: 140, 0, 83, 13, 83 UMA Zones: 480, 0, 83, 5, 83 UMA Slabs: 64, 0, 2537, 177, 225611 UMA RCntSlabs: 104, 0, 32769, 13, 2949442 UMA Hash: 128, 0, 3, 27, 6 16 Bucket: 76, 0, 27, 23, 73 32 Bucket: 140, 0, 23, 33, 64 64 Bucket: 268, 0, 17, 39, 100 128 Bucket: 524, 0, 223, 71, 1036 VM OBJECT: 132, 0, 30655, 2318, 1833813 MAP: 192, 0, 7, 33, 7 KMAP ENTRY: 68, 65520, 285, 11251, 78210624 MAP ENTRY: 68, 0, 215821, 8011, 3882740 PV ENTRY: 24, 2155135, 1391603, 119877, 42095182 DP fakepg: 72, 0, 0, 53, 6 mt_zone: 1024, 0, 174, 126, 174 16: 16, 0, 2158, 684, 578060 32: 32, 0, 3343, 386, 87211 64: 64, 0, 7323, 819, 1449967 128: 128, 0, 3507, 333, 519528 256: 256, 0, 6226, 509, 181376 512: 512, 0, 64, 96, 77544 1024: 1024, 0, 55, 73, 38283 2048: 2048, 0, 141, 27, 25379 4096: 4096, 0, 1990, 135, 84846 Files: 72, 0, 2924, 1475, 1665330 PROC: 524, 0, 1936, 220, 76612 THREAD: 372, 0, 2156, 14, 2156 KSEGRP: 88, 0, 2156, 84, 2156 UPCALL: 44, 0, 0, 0, 0 VMSPACE: 300, 0, 1886, 337, 76512 mbuf_packet: 256, 0, 66135, 0, 1979970489 mbuf: 256, 0, 7, 1253, 3511131461 mbuf_cluster: 2048, 65536, 65538, 0, 1966671403 mbuf_jumbo_pagesize: 4096, 0, 0, 0, 0 mbuf_jumbo_9k: 9216, 0, 0, 0, 0 mbuf_jumbo_16k: 16384, 0, 0, 0, 0 ACL UMA zone: 388, 0, 0, 0, 0 g_bio: 132, 0, 0, 87, 79264695 ata_request: 204, 0, 0, 0, 0 ata_composite: 196, 0, 0, 0, 0 VNODE: 272, 0, 27508, 7072, 4868108 VNODEPOLL: 76, 0, 1, 49, 1 S VFS Cache: 68, 0, 27595, 2869, 4582987 L VFS Cache: 291, 0, 1708, 203, 314868 NAMEI: 1024, 0, 3, 129, 12912949 DIRHASH: 1024, 0, 495, 41, 4186 NFSMOUNT: 480, 0, 2, 14, 3 NFSNODE: 460, 0, 13, 27, 1525 PIPE: 408, 0, 28, 35, 31594 KNOTE: 68, 0, 0, 168, 5762 socket: 356, 16434, 2327, 1699, 277319 unpcb: 140, 65548, 42, 70, 12935 ipq: 32, 2147, 0, 0, 2235 udpcb: 180, 16434, 5, 127, 5531 inpcb: 180, 16434, 2259, 1393, 258840 tcpcb: 464, 16424, 2258, 1454, 258840 tcptw: 48, 3354, 1, 389, 38232 syncache: 100, 15366, 17, 334, 322283 hostcache: 76, 15400, 246, 304, 6938 tcpreass: 20, 4225, 1, 168, 4936 sackhole: 20, 0, 8, 499, 23975962 ripcb: 180, 16434, 0, 44, 11 rtentry: 132, 0, 5, 53, 54 pfsrctrpl: 100, 0, 0, 0, 0 pfrulepl: 604, 0, 0, 0, 0 pfstatepl: 260, 10005, 0, 0, 0 pfaltqpl: 128, 0, 0, 0, 0 pfpooladdrpl: 68, 0, 0, 0, 0 pfrktable: 1240, 0, 0, 0, 0 pfrkentry: 156, 0, 0, 0, 0 pfrkentry2: 156, 0, 0, 0, 0 pffrent: 16, 5075, 0, 0, 0 pffrag: 48, 0, 0, 0, 0 pffrcache: 48, 10062, 0, 0, 0 pffrcent: 12, 50141, 0, 0, 0 pfstatescrub: 28, 0, 0, 0, 0 pfiaddrpl: 92, 0, 0, 0, 0 pfospfen: 108, 0, 0, 0, 0 pfosfp: 28, 0, 0, 0, 0 IPFW dynamic rule zone: 108, 0, 0, 0, 0 SWAPMETA: 276, 121576, 36, 20, 1613 FFS inode: 132, 0, 27459, 1280, 4866112 FFS1 dinode: 128, 0, 0, 0, 0 FFS2 dinode: 256, 0, 27459, 1206, 4866112 Intresting thing that everytime i use "vmstat 1" problem gone and i save my uptime. Server is still under load and i see only one process in D state 85815 ?? D 0:00.00 /usr/local/sbin/megarc -ldInfo -LAll -a0 Also i have found that it's much easy to trigger this state for httpd when i use low (default) value for MaxSpareServers (I have about 300 ~ 500 connections all the time) -- ========================================================================= = Best regards, Nikolay Pavlov. <<<------------------------------------ = ========================================================================= From owner-freebsd-stable@FreeBSD.ORG Fri Jul 7 14:16:00 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9A48F16A4E5; Fri, 7 Jul 2006 14:16:00 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2E38443D53; Fri, 7 Jul 2006 14:16:00 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 2603646D54; Fri, 7 Jul 2006 10:15:58 -0400 (EDT) Date: Fri, 7 Jul 2006 15:15:58 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: "Bradley W. Dutton" In-Reply-To: <1250.192.168.0.13.1152204720.squirrel@uno.mnl.com> Message-ID: <20060707151333.C51390@fledge.watson.org> References: <1250.192.168.0.13.1152204720.squirrel@uno.mnl.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: pjd@FreeBSD.org, freebsd-stable@freebsd.org Subject: Re: graid3 rebuild panic: mb_dtor_pack: ext_size != MCLBYTES X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Jul 2006 14:16:00 -0000 On Thu, 6 Jul 2006, Bradley W. Dutton wrote: > I get the below panic when rebuilding a graid3 array. Is this indicative of > a hardware or software problem? Or is some of the data on my array corrupt > and I should just rebuild the array? I searched on google and didn't find > much. > > panic: mb_dtor_pack: ext_size != MCLBYTES As I can't ever remember seeing that panic before, which is compatible with google's conclusion, it's likely this is a sign of kernel memory corruption. Whether that is a result of a hardware problem, I can't say. Is this reproduceable? If so, it could be a graid3 memory corruption problem. I've CC'd Pawel, the author of graid3. Robert N M Watson Computer Laboratory University of Cambridge From owner-freebsd-stable@FreeBSD.ORG Fri Jul 7 14:17:57 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0728816A4E0 for ; Fri, 7 Jul 2006 14:17:57 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id CAA5743D6E for ; Fri, 7 Jul 2006 14:17:52 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 59FC646D4E; Fri, 7 Jul 2006 10:17:52 -0400 (EDT) Date: Fri, 7 Jul 2006 15:17:52 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Pyun YongHyeon In-Reply-To: <20060707040838.GE82406@cdnetworks.co.kr> Message-ID: <20060707151640.D51390@fledge.watson.org> References: <20060629083130.X1229@ganymede.hub.org> <44A4A02A.9060802@thebeastie.org> <20060630012615.Q1103@ganymede.hub.org> <44A57B71.6020201@asd.aplus.net> <20060701035416.GC54876@cdnetworks.co.kr> <44AC6793.2070608@asd.aplus.net> <20060706021444.GA76865@cdnetworks.co.kr> <44AD7297.7080605@asd.aplus.net> <20060707010341.GD82406@cdnetworks.co.kr> <44ADC2ED.4070904@asd.aplus.net> <20060707040838.GE82406@cdnetworks.co.kr> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Peter Jeremy , Atanas , freebsd-stable@freebsd.org, Michael Vince , User Freebsd Subject: Re: em device hangs on ifconfig alias ... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Jul 2006 14:17:57 -0000 On Fri, 7 Jul 2006, Pyun YongHyeon wrote: > > I just left a "tcpdump -n arp host 10.10.64.40" on a third machine > > sniffing around and tested all em module versions I had (the stock 6.1, > > 6-STABLE and 6-STABLE with your patch), but got silence on all three: > > That's odd. I've tested it on CURRENT and I could see the ARP packet. Are > you sure you patched correctly? If so I have to build a RELENG_6 machine and > give it try. Is it possible you're seeing an interaction between the reset generated as part of IP address changing, and the time it takes to negotiate link? It's possible that the arp packets are being eaten during the link negotiation, so for systems negotiating quickly (or not at all) then the arp packet is seen on other hosts, and otherwise not... Robert N M Watson Computer Laboratory University of Cambridge > > > EM# ifconfig em1 inet alias 10.10.64.40 > > > > EM# ifconfig em1 inet -alias 10.10.64.40 > > > > > > It's normal. > > > The fxp driver appears to send something on startup and nothing on > > shutdown: > > > > FXP# ifconfig fxp0 inet alias 10.10.64.40 > > 18:41:54.584059 arp who-has 10.10.64.40 tell 10.10.64.40 > > FXP# ifconfig fxp0 inet -alias 10.10.64.40 > > > > > > When I manually arping the em alias after startup (i.e. simulate what > > fxp does), everything works as expected: > > > > EM# ifconfig em1 inet alias 10.10.64.40 > > > > EM# arping -c1 -S10.10.64.40 10.10.64.40 > > 18:46:07.808701 arp who-has 10.10.64.40 tell 10.10.64.40 > > Because arping requested it em(4) generated it. > > > EM# ifconfig em1 inet -alias 10.10.64.40 > > > > > > It appears that this is what the em driver is supposed to do, or at > > least fxp does it in this way. > > > > No, it's an em(4) driver bug. fxp(4)'s behavior is correct. > > > >This is other issue. em(4) performs two time-consuming operations > > >in its initialization routine. One is DMA tag/map creation and the > > >other is checksumming EEPROM contents in init routine. > > >I have an experimental patch for it but let's fix one at a time. > > > > > OK, let's put that aside for now. > > > > Regards, > > Atanas > > > > -- > Regards, > Pyun YongHyeon > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > From owner-freebsd-stable@FreeBSD.ORG Fri Jul 7 14:25:31 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E117516A4DA for ; Fri, 7 Jul 2006 14:25:31 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (arm132.internetdsl.tpnet.pl [83.17.198.132]) by mx1.FreeBSD.org (Postfix) with ESMTP id E889C43D46 for ; Fri, 7 Jul 2006 14:25:28 +0000 (GMT) (envelope-from pjd@garage.freebsd.pl) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id 52AF451395; Fri, 7 Jul 2006 16:25:26 +0200 (CEST) Received: from localhost (unknown [195.117.102.14]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id 456C451393; Fri, 7 Jul 2006 16:25:21 +0200 (CEST) Date: Fri, 7 Jul 2006 16:22:19 +0200 From: Pawel Jakub Dawidek To: "Bradley W. Dutton" Message-ID: <20060707142219.GF12401@garage.freebsd.pl> References: <1250.192.168.0.13.1152204720.squirrel@uno.mnl.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="6v9BRtpmy+umdQlo" Content-Disposition: inline In-Reply-To: <1250.192.168.0.13.1152204720.squirrel@uno.mnl.com> X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 7.0-CURRENT i386 User-Agent: mutt-ng/devel-r804 (FreeBSD) X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-2.6 required=3.0 tests=BAYES_00 autolearn=ham version=3.0.4 Cc: freebsd-stable@freebsd.org Subject: Re: graid3 rebuild panic: mb_dtor_pack: ext_size != MCLBYTES X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Jul 2006 14:25:32 -0000 --6v9BRtpmy+umdQlo Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jul 06, 2006 at 09:52:00AM -0700, Bradley W. Dutton wrote: > Hi, >=20 > I get the below panic when rebuilding a graid3 array. Is this indicative > of a hardware or software problem? Or is some of the data on my array > corrupt and I should just rebuild the array? I searched on google and > didn't find much. >=20 > panic: mb_dtor_pack: ext_size !=3D MCLBYTES Could you tell me which FreeBSD version do you use? Can I reproduce it somehow? --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --6v9BRtpmy+umdQlo Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFErm4bForvXbEpPzQRAmXnAKD1R2uUgbl9dyY8CczlTiUb4LxxswCeNLnz qUqEsAqutUz/F881WiEme44= =C8IP -----END PGP SIGNATURE----- --6v9BRtpmy+umdQlo-- From owner-freebsd-stable@FreeBSD.ORG Fri Jul 7 14:33:02 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A0B9F16A4DF for ; Fri, 7 Jul 2006 14:33:02 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (arm132.internetdsl.tpnet.pl [83.17.198.132]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4BD6143D66 for ; Fri, 7 Jul 2006 14:32:59 +0000 (GMT) (envelope-from pjd@garage.freebsd.pl) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id 1FBFD51393; Fri, 7 Jul 2006 16:32:58 +0200 (CEST) Received: from localhost (unknown [195.117.102.14]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id 4FCD750E96; Fri, 7 Jul 2006 16:32:54 +0200 (CEST) Date: Fri, 7 Jul 2006 16:29:55 +0200 From: Pawel Jakub Dawidek To: "Bradley W. Dutton" Message-ID: <20060707142955.GG12401@garage.freebsd.pl> References: <20060630220256.GB8447@turion.vk2pj.dyndns.org> <20060701074310.GA10220@turion.vk2pj.dyndns.org> <56779.71.202.65.184.1151774173.squirrel@uno.mnl.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="64j1qyTOoGvYcHb1" Content-Disposition: inline In-Reply-To: <56779.71.202.65.184.1151774173.squirrel@uno.mnl.com> X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 7.0-CURRENT i386 User-Agent: mutt-ng/devel-r804 (FreeBSD) X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-2.6 required=3.0 tests=BAYES_00 autolearn=ham version=3.0.4 Cc: freebsd-stable@freebsd.org Subject: Re: graid3 configure on 6 stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Jul 2006 14:33:02 -0000 --64j1qyTOoGvYcHb1 Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Jul 01, 2006 at 10:16:13AM -0700, Bradley W. Dutton wrote: > Hi, >=20 > I just tried 'graid3 configure -a' on a degraded array and received the > following: > panic: lock geom topology not exclusively locked @ > /usr/src/sys/geom/raid3/g_raid3_ctl.c:105 Ouh... Thanks for the report, I fixed it in HEAD and I'm going to MFC the fix in three days. --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --64j1qyTOoGvYcHb1 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFErm/jForvXbEpPzQRAgGUAJwPKuDTtgHy938ZZYr5/Ber2/LRdQCgq+vL PQ95f7C/qm3lyo9UUqKTc5c= =1RrU -----END PGP SIGNATURE----- --64j1qyTOoGvYcHb1-- From owner-freebsd-stable@FreeBSD.ORG Fri Jul 7 14:35:55 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BC9B716A4DF; Fri, 7 Jul 2006 14:35:55 +0000 (UTC) (envelope-from goran.lowkrantz@ismobile.com) Received: from mail.ismobile.com (tandgrisner.ismobile.com [213.88.244.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 157D643D46; Fri, 7 Jul 2006 14:35:54 +0000 (GMT) (envelope-from goran.lowkrantz@ismobile.com) Received: from [172.16.2.106] (viglaf.hq.ismobile.com [172.16.2.106]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.ismobile.com (Postfix) with ESMTP id E47C92280B; Fri, 7 Jul 2006 16:35:53 +0200 (CEST) Message-ID: <44AE7149.6080102@ismobile.com> Date: Fri, 07 Jul 2006 16:35:53 +0200 From: glz Organization: isMobile AB User-Agent: Thunderbird 1.5.0.4 (X11/20060605) MIME-Version: 1.0 To: le@FreeBSD.org References: <24C282E4D260624D50275B43@[10.255.253.2]> In-Reply-To: <24C282E4D260624D50275B43@[10.255.253.2]> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Cc: freebsd-stable@freebsd.org Subject: Re: Problem restarting gvinum raid-5 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Jul 2006 14:35:55 -0000 First, missed some info: > uname -a FreeBSD byleist.hq.ismobile.com 6.1-STABLE FreeBSD 6.1-STABLE #1: Mon Jun 26 20:37:45 CEST 2006 root@byleist.hq.ismobile.com:/usr/obj/usr/src/sys/BYLEISTSMP i386 So I continued to dig into this and it seems that the plex is not rebuilding because the geom is open, i.e. this routine: /* Check if any consumer of the given geom is open. */ int gv_is_open(struct g_geom *gp) { struct g_consumer *cp; if (gp == NULL) return (0); LIST_FOREACH(cp, &gp->consumer, consumer) { if (cp->acr || cp->acw || cp->ace) return (1); } return (0); } What does this mean? How do I make sure the geom is not opened until I can start the plex? I have tested single user and not mounted file system but it does not help. From the code I have read, this state should be the proper for allowing a rebuild of the plex: 5 drives: D disk5 State: up /dev/da6s1a A: 0/17492 MB (0%) D disk4 State: up /dev/da5s1a A: 0/17492 MB (0%) D disk3 State: up /dev/da4s1a A: 0/17492 MB (0%) D disk2 State: up /dev/da3s1a A: 0/17492 MB (0%) D disk1 State: up /dev/da2s1a A: 0/17492 MB (0%) 1 volume: V imap State: up Plexes: 1 Size: 68 GB 1 plex: P imap.p0 R5 State: degraded Subdisks: 5 Size: 68 GB 5 subdisks: S imap.p0.s0 State: up D: disk1 Size: 17 GB S imap.p0.s1 State: up D: disk2 Size: 17 GB S imap.p0.s2 State: up D: disk3 Size: 17 GB S imap.p0.s3 State: up D: disk4 Size: 17 GB S imap.p0.s4 State: stale D: disk5 Size: 17 GB /glz Goran Lowkrantz wrote: > Hi, > > We have a gvinum raid-5 volume that that we had to replace a disk on and > after that we cant get the new subdisk starting. > > Here are the things we did: > 1: Replace disk and boot singleuser to fdisk and lable new disk: > gvinum -> list > 5 drives: > D disk4 State: up /dev/da5s1a A: 0/17492 MB (0%) > D disk3 State: up /dev/da4s1a A: 0/17492 MB (0%) > D disk2 State: up /dev/da3s1a A: 0/17492 MB (0%) > D disk1 State: up /dev/da2s1a A: 0/17492 MB (0%) > > 1 volume: > V imap State: up Plexes: 1 Size: 68 GB > > 1 plex: > P imap.p0 R5 State: up Subdisks: 5 Size: 68 GB > > 5 subdisks: > S imap.p0.s0 State: up D: disk1 Size: 17 GB > S imap.p0.s1 State: up D: disk2 Size: 17 GB > S imap.p0.s2 State: up D: disk3 Size: 17 GB > S imap.p0.s3 State: up D: disk4 Size: 17 GB > S imap.p0.s4 State: up D: disk5 Size: 17 GB > > After fixing the new disk partition we did a saveconfig and reboot: > gvinum -> list > 5 drives: > D disk5 State: up /dev/da6s1a A: 0/17492 MB (0%) > D disk4 State: up /dev/da5s1a A: 0/17492 MB (0%) > D disk3 State: up /dev/da4s1a A: 0/17492 MB (0%) > D disk2 State: up /dev/da3s1a A: 0/17492 MB (0%) > D disk1 State: up /dev/da2s1a A: 0/17492 MB (0%) > > 1 volume: > V imap State: up Plexes: 1 Size: 68 GB > > 1 plex: > P imap.p0 R5 State: up Subdisks: 5 Size: 68 GB > > 5 subdisks: > S imap.p0.s4 State: stale D: disk5 Size: 17 GB > S imap.p0.s3 State: up D: disk4 Size: 17 GB > S imap.p0.s2 State: up D: disk3 Size: 17 GB > S imap.p0.s1 State: up D: disk2 Size: 17 GB > S imap.p0.s0 State: up D: disk1 Size: 17 GB > > Tried start on plex and subdisk, nnot working. Finally, to get plex into > degraded mode we did a setstate down imap.p0.s4. > gvinum -> list > 5 drives: > D disk5 State: up /dev/da6s1a A: 0/17492 MB (0%) > D disk4 State: up /dev/da5s1a A: 0/17492 MB (0%) > D disk3 State: up /dev/da4s1a A: 0/17492 MB (0%) > D disk2 State: up /dev/da3s1a A: 0/17492 MB (0%) > D disk1 State: up /dev/da2s1a A: 0/17492 MB (0%) > > 1 volume: > V imap State: up Plexes: 1 Size: 68 GB > > 1 plex: > P imap.p0 R5 State: degraded Subdisks: 5 Size: 68 GB > > 5 subdisks: > S imap.p0.s4 State: down D: disk5 Size: 17 GB > S imap.p0.s3 State: up D: disk4 Size: 17 GB > S imap.p0.s2 State: up D: disk3 Size: 17 GB > S imap.p0.s1 State: up D: disk2 Size: 17 GB > S imap.p0.s0 State: up D: disk1 Size: 17 GB > > and here we are. Start on volume or plex give errno 16, start on subdisk > gives can't start: cannot start 'imap.p0.s4' - not yet supported. > > Can't find any descriptions of the proper way to do disk replacement, so > if this is wrong, I'd love to get updated. And how do we get the current > situation upa nd running? > > Regards, > Göran > > > > ................................................... the future isMobile > > Goran Lowkrantz > System Architect, isMobile, Aurorum 2, S-977 75 Luleå, Sweden > Phone: +46(0)920-75559 > Mobile: +46(0)70-587 87 82 Fax: +46(0)70-615 87 82 > > http://www.ismobile.com ............................................... > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" -- ................................................... the future isMobile Goran Lowkrantz System Architect, isMobile, Aurorum 2, S-977 75 Luleå, Sweden Phone: +46(0)920-75559 Mobile: +46(0)70-587 87 82 Fax: +46(0)70-615 87 82 http://www.ismobile.com ............................................... From owner-freebsd-stable@FreeBSD.ORG Fri Jul 7 14:49:21 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 38B6616A4DA for ; Fri, 7 Jul 2006 14:49:21 +0000 (UTC) (envelope-from veldy@veldy.net) Received: from sccrmhc12.comcast.net (sccrmhc12.comcast.net [204.127.200.82]) by mx1.FreeBSD.org (Postfix) with ESMTP id 984DB43D62 for ; Fri, 7 Jul 2006 14:49:20 +0000 (GMT) (envelope-from veldy@veldy.net) Received: from fuggle.veldy.net (c-69-180-171-46.hsd1.mn.comcast.net[69.180.171.46]) by comcast.net (sccrmhc12) with ESMTP id <2006070714491901200d1ck3e>; Fri, 7 Jul 2006 14:49:19 +0000 Received: from [127.0.0.1] (localhost.veldy.net [127.0.0.1]) by fuggle.veldy.net (Postfix) with ESMTP id 28F621701A for ; Fri, 7 Jul 2006 09:49:19 -0500 (CDT) Message-ID: <44AE746E.60208@veldy.net> Date: Fri, 07 Jul 2006 09:49:18 -0500 From: "Thomas T. Veldhouse" User-Agent: Thunderbird 1.5.0.4 (Windows/20060516) MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: conftest dies with signal 12 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Jul 2006 14:49:21 -0000 I have seen messages like this on every FreeBSD machine that I have ever built. Can anybody indicate to me what this means? pid 60038 (conftest), uid 0: exited on signal 12 (core dumped) This issue is ALWAYS with "conftest". Tom Veldhouse From owner-freebsd-stable@FreeBSD.ORG Fri Jul 7 15:10:34 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 81AB116A4DD for ; Fri, 7 Jul 2006 15:10:34 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from pi.codefab.com (pi.codefab.com [199.103.21.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7157043D5D for ; Fri, 7 Jul 2006 15:10:30 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from localhost (localhost [127.0.0.1]) by pi.codefab.com (Postfix) with ESMTP id A33205EE3; Fri, 7 Jul 2006 11:10:29 -0400 (EDT) X-Virus-Scanned: amavisd-new at codefab.com Received: from pi.codefab.com ([127.0.0.1]) by localhost (pi.codefab.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KDx0vvKjq9rU; Fri, 7 Jul 2006 11:10:28 -0400 (EDT) Received: from [192.168.1.251] (pool-68-161-117-245.ny325.east.verizon.net [68.161.117.245]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by pi.codefab.com (Postfix) with ESMTP id 5AF345C35; Fri, 7 Jul 2006 11:10:28 -0400 (EDT) Message-ID: <44AE7961.5070802@mac.com> Date: Fri, 07 Jul 2006 11:10:25 -0400 From: Chuck Swiger User-Agent: Thunderbird 1.5.0.4 (Windows/20060516) MIME-Version: 1.0 To: "Thomas T. Veldhouse" References: <44AE746E.60208@veldy.net> In-Reply-To: <44AE746E.60208@veldy.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: conftest dies with signal 12 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Jul 2006 15:10:34 -0000 Thomas T. Veldhouse wrote: > I have seen messages like this on every FreeBSD machine that I have ever > built. Can anybody indicate to me what this means? > > pid 60038 (conftest), uid 0: exited on signal 12 (core dumped) While building software which uses GNU autoconf, ./configure tries to build and run a bunch of tiny test programs to see whether various system calls are available and how they work, figure out sizes of variable types, look for compilers for languages not being used by your software, and so forth. SIG 12 means: No Name Default action Description [ ... ] 12 SIGSYS create core image non-existent system call invoked -- -Chuck From owner-freebsd-stable@FreeBSD.ORG Fri Jul 7 15:13:37 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CA31416A4E0 for ; Fri, 7 Jul 2006 15:13:37 +0000 (UTC) (envelope-from veldy@veldy.net) Received: from sccrmhc12.comcast.net (sccrmhc12.comcast.net [63.240.77.82]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6695343D70 for ; Fri, 7 Jul 2006 15:13:37 +0000 (GMT) (envelope-from veldy@veldy.net) Received: from fuggle.veldy.net (c-69-180-171-46.hsd1.mn.comcast.net[69.180.171.46]) by comcast.net (sccrmhc12) with ESMTP id <2006070715133601200d50vme>; Fri, 7 Jul 2006 15:13:36 +0000 Received: from [127.0.0.1] (localhost.veldy.net [127.0.0.1]) by fuggle.veldy.net (Postfix) with ESMTP id CE0831701A; Fri, 7 Jul 2006 10:13:35 -0500 (CDT) Message-ID: <44AE7A1E.20500@veldy.net> Date: Fri, 07 Jul 2006 10:13:34 -0500 From: "Thomas T. Veldhouse" User-Agent: Thunderbird 1.5.0.4 (Windows/20060516) MIME-Version: 1.0 To: Chuck Swiger References: <44AE746E.60208@veldy.net> <44AE7961.5070802@mac.com> In-Reply-To: <44AE7961.5070802@mac.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: conftest dies with signal 12 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Jul 2006 15:13:37 -0000 Chuck Swiger wrote: > While building software which uses GNU autoconf, ./configure tries to > build and run a bunch of tiny test programs to see whether various > system calls are available and how they work, figure out sizes of > variable types, look for compilers for languages not being used by > your software, and so forth. > > SIG 12 means: > > No Name Default action Description > [ ... ] > 12 SIGSYS create core image non-existent system call > invoked > Ah ... thanks. I should have attempted to lookup what that meant myself before posting to the list. Thank you. Tom Veldhouse From owner-freebsd-stable@FreeBSD.ORG Fri Jul 7 16:18:07 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3788416A516 for ; Fri, 7 Jul 2006 16:18:07 +0000 (UTC) (envelope-from dkirhlarov@oilspace.com) Received: from office.oilspace.com (ns2.oilspace.com [194.129.65.230]) by mx1.FreeBSD.org (Postfix) with ESMTP id B528343D5C for ; Fri, 7 Jul 2006 16:18:06 +0000 (GMT) (envelope-from dkirhlarov@oilspace.com) Received: from dimma.mow.oilspace.com (hq.oilspace.com [81.222.156.185]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by office.oilspace.com (Postfix) with ESMTP id 7446A136CDB for ; Fri, 7 Jul 2006 17:18:05 +0100 (BST) Received: from dimma.mow.oilspace.com (localhost [127.0.0.1]) by dimma.mow.oilspace.com (8.13.4/8.13.3) with ESMTP id k67GI4eH043867 for ; Fri, 7 Jul 2006 20:18:04 +0400 (MSD) (envelope-from dkirhlarov@localhost.oilspace.com) Received: (from dkirhlarov@localhost) by dimma.mow.oilspace.com (8.13.4/8.13.3/Submit) id k67GI4KY043866 for stable@freebsd.org; Fri, 7 Jul 2006 20:18:04 +0400 (MSD) (envelope-from dkirhlarov) Date: Fri, 7 Jul 2006 20:18:04 +0400 From: Dmitriy Kirhlarov To: stable@freebsd.org Message-ID: <20060707161801.GB42118@dimma.mow.oilspace.com> Mail-Followup-To: stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Mailer: Mutt-ng devel (2005-03-13) based on Mutt 1.5.9 X-Operating-System: FreeBSD 5.4-STABLE User-Agent: mutt-ng/devel-r581 (FreeBSD) Cc: Subject: nsswitch.conf problem with group status code X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Jul 2006 16:18:07 -0000 Hi, list. I use mixed (master.passwd + ldap) authorization. I have a problem -- when network unreacheble, local users can't login to system. After investigation, I find reason -- timeouts, when resolver try return ldap server IP. I add to /etc/nsswitch.conf: group: files [success=return notfound=continue unavail=continue tryagain=continue] ldap passwd: files [success=return notfound=continue unavail=continue tryagain=continue] ldap and add in /usr/local/etc/ldap.conf debug 257 After that, I run id root I find, what success=return don't work for group -- we trying connecting to ldap server and get extended grouplist. Why my status code setup ignoring? WBR -- Dmitriy Kirhlarov OILspace, 26 Leninskaya sloboda, bld. 2, 2nd floor, 115280 Moscow, Russia P:+7 495 105 7247 ext.203 F:+7 495 105 7246 E:DmitriyKirhlarov@oilspace.com OILspace - The resource enriched - www.oilspace.com From owner-freebsd-stable@FreeBSD.ORG Fri Jul 7 17:24:22 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B26EA16A4DE for ; Fri, 7 Jul 2006 17:24:22 +0000 (UTC) (envelope-from norbert@augenstein.net) Received: from www33.your-server.de (www33.your-server.de [213.133.104.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id BE25243D66 for ; Fri, 7 Jul 2006 17:24:21 +0000 (GMT) (envelope-from norbert@augenstein.net) Received: from [84.153.7.79] (helo=surfer.augenstein.ten) by www33.your-server.de with esmtpa (Exim 4.52) id 1Fyu3v-0003cF-E5 for freebsd-stable@freebsd.org; Fri, 07 Jul 2006 19:24:20 +0200 Received: from seth.augenstein.ten (seth.augenstein.ten [192.168.0.2]) by surfer.augenstein.ten (Postfix) with ESMTP id 7B6893ED2 for ; Fri, 7 Jul 2006 19:24:15 +0200 (CEST) Received: by seth.augenstein.ten (Postfix, from userid 666) id 22262C7; Fri, 7 Jul 2006 19:24:15 +0200 (CEST) Date: Fri, 7 Jul 2006 19:24:15 +0200 From: Norbert Augenstein To: freebsd-stable@freebsd.org Message-ID: <20060707172414.GA786@seth.augenstein.ten> Mail-Followup-To: freebsd-stable@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 6.1-RELEASE X-Copyright: (c) auge -> Norbert Augenstein, Munich, Germany X-Authenticated-Sender: norbert@augenstein.net X-Virus-Scanned: Clear (ClamAV 0.88.2/1589/Fri Jul 7 16:37:51 2006) Subject: gnutls X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Jul 2006 17:24:22 -0000 Hi all, i have updated gnutls and see libgnutls-extra.so.13 libgnutls-extra.so.13 libgnutls.so.13 before i update all ports denpend on it, shouldn't that read *.so.16 ?? From owner-freebsd-stable@FreeBSD.ORG Fri Jul 7 18:29:25 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4D37316A4E7; Fri, 7 Jul 2006 18:29:25 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id B649943D7F; Fri, 7 Jul 2006 18:29:17 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from localhost.corp.yahoo.com (john@localhost [127.0.0.1]) (authenticated bits=0) by server.baldwin.cx (8.13.4/8.13.4) with ESMTP id k67ITD6k019594; Fri, 7 Jul 2006 14:29:14 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-current@freebsd.org Date: Fri, 7 Jul 2006 13:43:12 -0400 User-Agent: KMail/1.9.1 References: <20060629193346.GA2548@dragon.NUXI.org> <44AD6756.4070008@rogers.com> <44ADC08B.8000408@rogers.com> In-Reply-To: <44ADC08B.8000408@rogers.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200607071343.14205.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [127.0.0.1]); Fri, 07 Jul 2006 14:29:14 -0400 (EDT) X-Virus-Scanned: ClamAV 0.87.1/1589/Fri Jul 7 10:37:51 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx Cc: Mike Jakubik , stable@freebsd.org, obrien@freebsd.org Subject: Re: Still getting 'calcru: runtime went backwards' X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Jul 2006 18:29:25 -0000 On Thursday 06 July 2006 22:01, Mike Jakubik wrote: > I'm getting a ton of them now, and i found a way to reproduce them. > Basically i run a compile session in one terminal, say make buildkernel, > and run top in another. As soon as i run top, the messages appear, and > they seem to be synchronized with the refresh rate of top, 2 messages > per refresh. This is on a 6.1-STABLE as of today. That is partly because when you run top it queries the resource usage of the various processes via fill_kinfo_proc(). When you don't run top, no one is asking for the resource usage numbers, so the kernel doesn't waste time calculating them. > --- > calcru: negative runtime of -261273 usec for pid 12 (swi4: clock) > calcru: negative runtime of -261273 usec for pid 12 (swi4: clock) > calcru: negative runtime of -259691 usec for pid 12 (swi4: clock) > ... In both cases your errors are for a long-running kernel process that's been up since boot. What's the uptime on your box? -- John Baldwin From owner-freebsd-stable@FreeBSD.ORG Fri Jul 7 18:43:28 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1C0E516A51A; Fri, 7 Jul 2006 18:43:28 +0000 (UTC) (envelope-from mikej@rogers.com) Received: from H43.C18.B96.tor.eicat.ca (H43.C18.B96.tor.eicat.ca [66.96.18.43]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1D13343D58; Fri, 7 Jul 2006 18:43:26 +0000 (GMT) (envelope-from mikej@rogers.com) Received: from [127.0.0.1] (desktop.home.local [172.16.0.200]) by H43.C18.B96.tor.eicat.ca (Postfix) with ESMTP id 1807411446; Fri, 7 Jul 2006 14:42:47 -0400 (EDT) Message-ID: <44AEAB61.6000104@rogers.com> Date: Fri, 07 Jul 2006 14:43:45 -0400 From: Mike Jakubik User-Agent: Thunderbird 1.5.0.4 (Windows/20060516) MIME-Version: 1.0 To: John Baldwin References: <20060629193346.GA2548@dragon.NUXI.org> <44AD6756.4070008@rogers.com> <44ADC08B.8000408@rogers.com> <200607071343.14205.jhb@freebsd.org> In-Reply-To: <200607071343.14205.jhb@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SpamToaster-Information: This messages has been scanned by SpamToaster http://www.digitalprogression.ca X-SpamToaster: Found to be clean X-SpamToaster-SpamCheck: not spam, SpamAssassin (not cached, score=-2.49, required 3.5, ALL_TRUSTED -1.80, BAYES_00 -2.60, DK_POLICY_SIGNSOME 0.00, DNS_FROM_RFC_ABUSE 0.20, DNS_FROM_RFC_POST 1.71) X-SpamToaster-From: mikej@rogers.com X-Spam-Status: No Cc: stable@freebsd.org, freebsd-current@freebsd.org, obrien@freebsd.org Subject: Re: Still getting 'calcru: runtime went backwards' X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Jul 2006 18:43:28 -0000 John Baldwin wrote: > That is partly because when you run top it queries the resource usage of the > various processes via fill_kinfo_proc(). When you don't run top, no one is > asking for the resource usage numbers, so the kernel doesn't waste time > calculating them. > > Right, also running ps has the same effect. But why do these messages occur? > In both cases your errors are for a long-running kernel process that's been up > since boot. What's the uptime on your box? > > Not sure what the uptime was, this box is not in production yet so i shut it off regularly. I would guess under an hour. From owner-freebsd-stable@FreeBSD.ORG Fri Jul 7 18:50:11 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0279D16A4F4 for ; Fri, 7 Jul 2006 18:50:10 +0000 (UTC) (envelope-from anton@nikiforov.ru) Received: from vika.newlines.ru (anna.newlines.ru [195.246.218.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 21CC243D46 for ; Fri, 7 Jul 2006 18:50:09 +0000 (GMT) (envelope-from anton@nikiforov.ru) Received: from localhost (unknown [127.0.0.1]) by vika.newlines.ru (Postfix) with ESMTP id B2BEF11C19; Fri, 7 Jul 2006 22:50:07 +0400 (MSD) Received: from vika.newlines.ru ([127.0.0.1]) by localhost (anna.newlines.ru [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 11864-05; Fri, 7 Jul 2006 22:50:02 +0400 (MSD) Received: from [192.168.80.107] (strijev.office.sportlottery.ru [192.168.80.107]) by vika.newlines.ru (Postfix) with ESMTP; Fri, 7 Jul 2006 22:50:02 +0400 (MSD) Message-ID: <44AEACD9.4070103@nikiforov.ru> Date: Fri, 07 Jul 2006 22:50:01 +0400 From: Anton Nikiforov User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915 X-Accept-Language: ru, en-us, en MIME-Version: 1.0 To: Dmitriy Kirhlarov References: <44AD688A.6050408@nikiforov.ru> <20060707091734.GA38936@dimma.mow.oilspace.com> In-Reply-To: <20060707091734.GA38936@dimma.mow.oilspace.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: By amavis at office-gw.newlines.ru Cc: freebsd-stable@freebsd.org Subject: Re: carp+pfsync+freevrrpd+jail X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Jul 2006 18:50:11 -0000 Hello Dmitriy and thanks for your replay. Dmitriy Kirhlarov wrote: >>What i have is that when i'm pinging carp0 (inet) or carp1(lan) >>interface's ip address of my firewall - i'm receivind DUP responses. >> >> > >One from carp and other from freevrrpd. > > While this tests i have freevrrpd down. First of all i want to get fresh firewall with no bugs to continue to test ifstated/freevrrpd. >>And when host2 is ths slave and i'm starting to ping carp0 address - >>no traffic appears on master host - that means that the local carp >>interface responding to my packets.. >> >> > >Yep. Full standby mode (backup don't have shared IP) is not >implemented now. > > Hm... any alternative to carp in this case? (my idea below) >>That means that in case some service (provided by jail managed by >>freevrrpd) will be accessed from outside - i cannot be sure what >>host will answer the request. >> >> > >I don't understand your idea. Do you want to start-stop jail, when >master node is down-up? > > Here we are. We have two servers with shared disk subsystem (geom and/or external SCSI raid) inet ----- em0-vlan101-carp0------------------carp3-vlan100-em0------lan1 carp1 | carp2 |----carp4-vlan200-em0------lan2 ......................many vlans inet ----- em0-vlan101-carp0-----------------carp3-vlan100-em0------lan1 carp1 | carp2 |----carp4-vlan200-em0------lan2 ......................many vlans carp0 - used for routing of traffice that passing from inet to vlans and from vlans to inet Routing is one single task, so, maybe i do not need dedicated carp. But it will make ballance tuning mutch easy, by just changing carp interface parameters to change places for master and slave than to reconfigure services. carp1 - used for routing to services that should (in normal state) work on host1 carp2 - used for routing to services that should (in normal state) work on host2 We have services: SMPT (postfix), cashe (squid+squidguard), ldap....... everything in jails, with unique single IP address connected to loX interface each. When one host become down it's IPs (and services) moving to another by freevrrpd/ifstated. Routing of each single service IP made to the corresponding firewall carp(carp1 or carp2) interface. In other words incoming packet from any interface should go to carp-master. In case service IP is local it just dealing with jail. But if it is remote it meets routing table and packet being forwarded to another host (where corresponding carp is the master and corresponding jail run) Here what i have now carp0 - 192.168.0.1/24 (host1 master) carp1 - 192.168.1.1/24 (host1 master) carp2 - 192.168.2.1/24 (host2 master) carp3 - 192.168.3.1/24 (host1 master) carp4 - 192.168.4.1/24 (host1 master) jail1: ip: 192.168.10.1/32 (SMTP normaly run on host1) jail2: ip: 192.168.10.2/32 (SQUID normaly run on host2) on host2: route add host 192.168.10.1 192.168.1.1 on host1: route add host 192.168.10.2 192.168.2.1 Corresponding jail have to be on the host where corresponding carp is master. If only master carp answering packets then packet, coming from internal vlan200 (where hosts have carp's address set as default router) comes to host: if local jail is running it's being directed to jail itself. if no local jail - it meets routing table to be forwarded to corresponding carp1(2) IP. there it can find local jail IP and being forwarded there. But problems arised when bouth, master and slave answerring to incoming packets. First of all it is not clear why slave answering packets at all. N.B. This is the IDEA. But i would like to make it reality :) >>I have done some tests. When i'm sshing to virtual IP - sometimes >>i'm getting ssh prompt and can login, and sometimes it says that >>host auth info is bad (yes, because second server answering me at >>this time) and sometimes i'm loosing ssh connection while session is >>active. >> >> > >Use 'advbase' and 'advskew' params on both hosts for hard managing >status of nodes. > > > >>No ballance needed. I want to have some service run in main OS, some >>services run in jail and i want to be sure which host will answer >>the request when bouth hosts are up and running. >> >> > >Be careful, if you want to use carp IP inside jail. Only master node can >get data from external world. >I tried to make this schema: > ldap1 > / \ > ldapn1 ldapn2 > | | | | | | > clients clients > >Where ldap1 -- master ldap server. >ldapn1, ldapn2 -- jail on different hosts on carp shared IP. They >connect to ldap1 and get fresh data from master ldap server. > >I found, that only master node can start successfully. Jail on backup >node can't start, because ldap server can't start. It can't start, >because, it can't successfully connect to ldap1. >ldapn2 sends SYN, ldap1 returns SYN+ACK, and switch delivers this >packet to ldapn1 -- active master node. >In order to have this schema working, both nodes must have personal IP >and shared IP, but it's impossible within current jail implementation. > >WBR > > Best regards, Anton From owner-freebsd-stable@FreeBSD.ORG Fri Jul 7 19:00:59 2006 Return-Path: X-Original-To: freebsd-stable@FreeBSD.org Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8842B16A4DF; Fri, 7 Jul 2006 19:00:59 +0000 (UTC) (envelope-from atanas@asd.aplus.net) Received: from pro20.abac.com (pro20.abac.com [66.226.64.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2E47143D5F; Fri, 7 Jul 2006 19:00:48 +0000 (GMT) (envelope-from atanas@asd.aplus.net) Received: from [216.55.129.5] (asd2.aplus.net [216.55.129.5]) (authenticated bits=0) by pro20.abac.com (8.13.6/8.13.6) with ESMTP id k67J0hZR055075 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 7 Jul 2006 12:00:44 -0700 (PDT) (envelope-from atanas@asd.aplus.net) Message-ID: <44AEB0CB.5060102@asd.aplus.net> Date: Fri, 07 Jul 2006 12:06:51 -0700 From: Atanas User-Agent: Thunderbird 1.5.0.4 (Macintosh/20060516) MIME-Version: 1.0 To: Robert Watson References: <20060629083130.X1229@ganymede.hub.org> <44A4A02A.9060802@thebeastie.org> <20060630012615.Q1103@ganymede.hub.org> <44A57B71.6020201@asd.aplus.net> <20060701035416.GC54876@cdnetworks.co.kr> <44AC6793.2070608@asd.aplus.net> <20060706021444.GA76865@cdnetworks.co.kr> <44AD7297.7080605@asd.aplus.net> <20060707010341.GD82406@cdnetworks.co.kr> <44ADC2ED.4070904@asd.aplus.net> <20060707040838.GE82406@cdnetworks.co.kr> <20060707151640.D51390@fledge.watson.org> In-Reply-To: <20060707151640.D51390@fledge.watson.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 1.47 (SPF_SOFTFAIL) Cc: Pyun YongHyeon , Peter Jeremy , freebsd-stable@FreeBSD.org, Michael Vince , User Freebsd Subject: Re: em device hangs on ifconfig alias ... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Jul 2006 19:00:59 -0000 Robert Watson said the following on 7/7/06 7:17 AM: >> > I just left a "tcpdump -n arp host 10.10.64.40" on a third machine > >> sniffing around and tested all em module versions I had (the stock >> 6.1, > 6-STABLE and 6-STABLE with your patch), but got silence on all >> three: >> >> That's odd. I've tested it on CURRENT and I could see the ARP packet. >> Are you sure you patched correctly? If so I have to build a RELENG_6 >> machine and give it try. > > Is it possible you're seeing an interaction between the reset generated > as part of IP address changing, and the time it takes to negotiate > link? It's possible that the arp packets are being eaten during the > link negotiation, so for systems negotiating quickly (or not at all) > then the arp packet is seen on other hosts, and otherwise not... > Looks like this is exactly what happens. I was able to see it by running two tcpdump instances - one on the EM machine running in background and another running elsewhere on the same subnet. So on the EM machine the arp packet actually gets generated by em(4) and caught by the tcpdump running there: EM# tcpdump -n arp and ether src 00:04:23:b5:1b:ff & EM# EM# ifconfig em1 inet alias 10.10.64.40 EM# 11:28:37.178946 arp who-has 10.10.64.40 tell 10.10.64.40 EM# But it doesn't reach the other tcpdump instance running on another host. It seems that the arp packet gets killed before leaving the EM machine, due to the card initialization or something else. I tried sending it manually with arping, just to make sure both tcpdumps operate properly and yes, the packet got delivered to both. I think that I have patched, built and loaded the em(4) kernel module correctly. After applying the patch there were no rejects, before building the module I intentionally appended " (patched)" to its version string in if_em.c, and could see that in dmesg every time I loaded the module: em1: Regards, Atanas From owner-freebsd-stable@FreeBSD.ORG Fri Jul 7 19:33:51 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2197616A4DA; Fri, 7 Jul 2006 19:33:51 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8A9CB43D46; Fri, 7 Jul 2006 19:33:50 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from localhost.corp.yahoo.com (john@localhost [127.0.0.1]) (authenticated bits=0) by server.baldwin.cx (8.13.4/8.13.4) with ESMTP id k67JXmsQ020399; Fri, 7 Jul 2006 15:33:49 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: Mike Jakubik Date: Fri, 7 Jul 2006 15:26:47 -0400 User-Agent: KMail/1.9.1 References: <20060629193346.GA2548@dragon.NUXI.org> <200607071343.14205.jhb@freebsd.org> <44AEAB61.6000104@rogers.com> In-Reply-To: <44AEAB61.6000104@rogers.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200607071526.47758.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [127.0.0.1]); Fri, 07 Jul 2006 15:33:49 -0400 (EDT) X-Virus-Scanned: ClamAV 0.87.1/1589/Fri Jul 7 10:37:51 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx Cc: stable@freebsd.org, freebsd-current@freebsd.org, obrien@freebsd.org Subject: Re: Still getting 'calcru: runtime went backwards' X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Jul 2006 19:33:51 -0000 On Friday 07 July 2006 14:43, Mike Jakubik wrote: > John Baldwin wrote: > > That is partly because when you run top it queries the resource usage of > > the various processes via fill_kinfo_proc(). When you don't run top, no > > one is asking for the resource usage numbers, so the kernel doesn't waste > > time calculating them. > > Right, also running ps has the same effect. But why do these messages occur? Not sure. My guess would be an overflow of some sort but given the short uptime that likely is not the case. -- John Baldwin From owner-freebsd-stable@FreeBSD.ORG Fri Jul 7 20:44:13 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 07A5216A4DF; Fri, 7 Jul 2006 20:44:13 +0000 (UTC) (envelope-from stephen@math.missouri.edu) Received: from sccmmhc91.asp.att.net (sccmmhc91.asp.att.net [204.127.203.211]) by mx1.FreeBSD.org (Postfix) with ESMTP id DAA9643D5C; Fri, 7 Jul 2006 20:44:09 +0000 (GMT) (envelope-from stephen@math.missouri.edu) Received: from [10.0.0.4] (12-216-255-142.client.mchsi.com[12.216.255.142]) by sccmmhc91.asp.att.net (sccmmhc91) with ESMTP id <20060707204405m9100860lde>; Fri, 7 Jul 2006 20:44:08 +0000 Message-ID: <44AEC793.6000406@math.missouri.edu> Date: Fri, 07 Jul 2006 15:44:03 -0500 From: Stephen Montgomery-Smith User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.13) Gecko/20060617 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Mike Jakubik References: <20060629193346.GA2548@dragon.NUXI.org> <44AD6756.4070008@rogers.com> <44ADC08B.8000408@rogers.com> <200607071343.14205.jhb@freebsd.org> <44AEAB61.6000104@rogers.com> In-Reply-To: <44AEAB61.6000104@rogers.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: stable@freebsd.org, freebsd-current@freebsd.org, obrien@freebsd.org, John Baldwin Subject: Re: Still getting 'calcru: runtime went backwards' X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Jul 2006 20:44:13 -0000 Mike Jakubik wrote: > John Baldwin wrote: > >> That is partly because when you run top it queries the resource usage >> of the various processes via fill_kinfo_proc(). When you don't run >> top, no one is asking for the resource usage numbers, so the kernel >> doesn't waste time calculating them. >> >> > > > Right, also running ps has the same effect. But why do these messages > occur? > >> In both cases your errors are for a long-running kernel process that's >> been up since boot. What's the uptime on your box? >> >> > > > Not sure what the uptime was, this box is not in production yet so i > shut it off regularly. I would guess under an hour. I used to be able to get these predictably on FreeBSD 5, except then it could actually cause a panic. If you run "top -s 0" (as root) you can get these errors arriving at a spectacular rate. From owner-freebsd-stable@FreeBSD.ORG Fri Jul 7 21:18:46 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 46CC716A4DE; Fri, 7 Jul 2006 21:18:46 +0000 (UTC) (envelope-from freebsd@hub.org) Received: from hub.org (hub.org [200.46.204.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id AD07543D45; Fri, 7 Jul 2006 21:18:45 +0000 (GMT) (envelope-from freebsd@hub.org) Received: from localhost (wm.hub.org [200.46.204.128]) by hub.org (Postfix) with ESMTP id AC7F1290C3A; Fri, 7 Jul 2006 18:18:41 -0300 (ADT) Received: from hub.org ([200.46.204.220]) by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024) with ESMTP id 75087-07; Fri, 7 Jul 2006 21:18:44 +0000 (UTC) Received: from ganymede.hub.org (blk-222-80-186.eastlink.ca [24.222.80.186]) by hub.org (Postfix) with ESMTP id 0B484290C29; Fri, 7 Jul 2006 18:18:41 -0300 (ADT) Received: by ganymede.hub.org (Postfix, from userid 1027) id 7FCA64825E; Fri, 7 Jul 2006 18:18:46 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id 7AD6847D6D; Fri, 7 Jul 2006 18:18:46 -0300 (ADT) Date: Fri, 7 Jul 2006 18:18:46 -0300 (ADT) From: User Freebsd To: Atanas In-Reply-To: <44AEB0CB.5060102@asd.aplus.net> Message-ID: <20060707181750.O1171@ganymede.hub.org> References: <20060629083130.X1229@ganymede.hub.org> <44A4A02A.9060802@thebeastie.org> <20060630012615.Q1103@ganymede.hub.org> <44A57B71.6020201@asd.aplus.net> <20060701035416.GC54876@cdnetworks.co.kr> <44AC6793.2070608@asd.aplus.net> <20060706021444.GA76865@cdnetworks.co.kr> <44AD7297.7080605@asd.aplus.net> <20060707010341.GD82406@cdnetworks.co.kr> <44ADC2ED.4070904@asd.aplus.net> <20060707040838.GE82406@cdnetworks.co.kr> <20060707151640.D51390@fledge.watson.org> <44AEB0CB.5060102@asd.aplus.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Pyun YongHyeon , Peter Jeremy , Robert Watson , Michael Vince , freebsd-stable@FreeBSD.org Subject: Re: em device hangs on ifconfig alias ... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Jul 2006 21:18:46 -0000 On Fri, 7 Jul 2006, Atanas wrote: > Robert Watson said the following on 7/7/06 7:17 AM: >>> > I just left a "tcpdump -n arp host 10.10.64.40" on a third machine > >>> sniffing around and tested all em module versions I had (the stock 6.1, > >>> 6-STABLE and 6-STABLE with your patch), but got silence on all three: >>> >>> That's odd. I've tested it on CURRENT and I could see the ARP packet. Are >>> you sure you patched correctly? If so I have to build a RELENG_6 machine >>> and give it try. >> >> Is it possible you're seeing an interaction between the reset generated as >> part of IP address changing, and the time it takes to negotiate link? It's >> possible that the arp packets are being eaten during the link negotiation, >> so for systems negotiating quickly (or not at all) then the arp packet is >> seen on other hosts, and otherwise not... >> > Looks like this is exactly what happens. > > I was able to see it by running two tcpdump instances - one on the EM machine > running in background and another running elsewhere on the same subnet. > > So on the EM machine the arp packet actually gets generated by em(4) and > caught by the tcpdump running there: > > EM# tcpdump -n arp and ether src 00:04:23:b5:1b:ff & > EM# > EM# ifconfig em1 inet alias 10.10.64.40 > EM# 11:28:37.178946 arp who-has 10.10.64.40 tell 10.10.64.40 > EM# > > But it doesn't reach the other tcpdump instance running on another host. It > seems that the arp packet gets killed before leaving the EM machine, due to > the card initialization or something else. > > I tried sending it manually with arping, just to make sure both tcpdumps > operate properly and yes, the packet got delivered to both. > > I think that I have patched, built and loaded the em(4) kernel module > correctly. After applying the patch there were no rejects, before building > the module I intentionally appended " (patched)" to its version string in > if_em.c, and could see that in dmesg every time I loaded the module: > em1: Is it possible that we're going at this issue backwards? It isn't the lack of ARP packet going out that is causing the problems with moving IPs, but that delay that we're seeing when aliasing a new IP on the stack? The ARP packet *is* being attempted, but is timing out before the re-init is completing? ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . scrappy@hub.org MSN . scrappy@hub.org Yahoo . yscrappy Skype: hub.org ICQ . 7615664 From owner-freebsd-stable@FreeBSD.ORG Fri Jul 7 21:38:02 2006 Return-Path: X-Original-To: freebsd-stable@FreeBSD.org Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 569C016A4DA for ; Fri, 7 Jul 2006 21:38:02 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id E333543D45 for ; Fri, 7 Jul 2006 21:38:01 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 0E45146BB4; Fri, 7 Jul 2006 17:38:01 -0400 (EDT) Date: Fri, 7 Jul 2006 22:38:01 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: User Freebsd In-Reply-To: <20060707181750.O1171@ganymede.hub.org> Message-ID: <20060707223609.N60542@fledge.watson.org> References: <20060629083130.X1229@ganymede.hub.org> <44A4A02A.9060802@thebeastie.org> <20060630012615.Q1103@ganymede.hub.org> <44A57B71.6020201@asd.aplus.net> <20060701035416.GC54876@cdnetworks.co.kr> <44AC6793.2070608@asd.aplus.net> <20060706021444.GA76865@cdnetworks.co.kr> <44AD7297.7080605@asd.aplus.net> <20060707010341.GD82406@cdnetworks.co.kr> <44ADC2ED.4070904@asd.aplus.net> <20060707040838.GE82406@cdnetworks.co.kr> <20060707151640.D51390@fledge.watson.org> <44AEB0CB.5060102@asd.aplus.net> <20060707181750.O1171@ganymede.hub.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Pyun YongHyeon , Peter Jeremy , Atanas , freebsd-stable@FreeBSD.org, Michael Vince Subject: Re: em device hangs on ifconfig alias ... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Jul 2006 21:38:02 -0000 On Fri, 7 Jul 2006, User Freebsd wrote: >> I think that I have patched, built and loaded the em(4) kernel module >> correctly. After applying the patch there were no rejects, before building >> the module I intentionally appended " (patched)" to its version string in >> if_em.c, and could see that in dmesg every time I loaded the module: em1: >> > > Is it possible that we're going at this issue backwards? It isn't the lack > of ARP packet going out that is causing the problems with moving IPs, but > that delay that we're seeing when aliasing a new IP on the stack? The ARP > packet *is* being attempted, but is timing out before the re-init is > completing? Yes -- basically, there are two problems: (1) A little problem, in which an arp announcement is sent before the link has settled after reset. (2) A big problem, in which the interface is gratuitously recent requiring long settling times. I'd really like to see a fix to the second of these problems (not resetting when an IP is added or removed, resulting in link renegotiation); the first one I'm less concerned about, although it would make some amount of sense to do an arp announcement when the link goes up. Robert N M Watson Computer Laboratory University of Cambridge From owner-freebsd-stable@FreeBSD.ORG Sat Jul 8 02:56:50 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 92F2116A4DE for ; Sat, 8 Jul 2006 02:56:50 +0000 (UTC) (envelope-from spork@bway.net) Received: from mail.bway.net (xena.bway.net [216.220.96.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id 95E1243D58 for ; Sat, 8 Jul 2006 02:56:49 +0000 (GMT) (envelope-from spork@bway.net) Received: (qmail 49028 invoked by uid 0); 8 Jul 2006 02:56:48 -0000 Received: from unknown (HELO white.nat.fasttrackmonkey.com) (spork@bway.net@216.220.116.154) by smtp.bway.net with (DHE-RSA-AES256-SHA encrypted) SMTP; 8 Jul 2006 02:56:48 -0000 Date: Fri, 7 Jul 2006 22:56:47 -0400 (EDT) From: Charles Sprickman X-X-Sender: spork@white.nat.fasttrackmonkey.com To: freebsd-stable@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: 6.1 quota issues X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Jul 2006 02:56:50 -0000 Hello all, I'm in the process of rolling out a new shell server and for numerous reasons have decided 6.x is the best fit (jail improvements, SMP improvements, 3Ware driver, pf). The shell server is within a jail, and the uids there are unique so that quotas remain sane. There are about 5000 active accounts using about 40GB of a 210GB partition. The quota.user file is about 4GB. I just started work on getting quotas setup for everyone after rsyncing all the homedirs from the old server over. At first, all seemed well, then I ran into a few issues on subsequent rsyncs. I had people with large (1GB+) homedirs and quotas in the 1GB-4GB range and as rsync was chowning the files to the users it was throwing errors about "quota exceeded". Here's a brief example that illustrates what I was seeing: ot@beta[/home/staff/micro/tmp]# quota micro Disk quotas for user micro (uid 5315): Filesystem usage quota limit grace files quota limit grace / 1630026 3000000 3100000 13393 0 0 root@beta[/home/staff/micro/tmp]# chown micro index.html chown: index.html: Disc quota exceeded root@beta[/home/staff/micro/tmp]# I know in the past when I've seen inconsistencies indicating that I needed a manual run of quotacheck, they would show up in the output of the quota command; ie: the "quota" command would show the user had more usage than "du" would indicate. The above example is a bit odd - "quota" shows that he's well within his limits, but the kernel thinks otherwise. Thinking it would be a good idea to stop the jails, turn off quotas, umount the partition, fsck it, mount it and then run quotacheck, I found more problems. My first run of quotacheck ran for a few minutes, reported many inconsistencies and then sat there for quite some time before spitting this out: quotacheck: /jails/quota.user: seek failed: Invalid argument Trying again, it reported the same inconsistencies then sat there for more than an hour taking up all the available CPU on the box until I killed it. The mtime on quota.user had not changed during the run. Running it yet again now gives me this: /jails: fixed: inodes 27 -> 0 blocks 156 -> 0 quotacheck: /jails/quota.user: seek failed: Invalid argument THE FOLLOWING FILE SYSTEM HAD AN UNEXPECTED INCONSISTENCY: /dev/twed0s1g (/jails) For now I can live without quotas, but if there's anything I can test from -stable that might address this I'd like to try it. I'd say this thing is still a good month from going live since we have lots of dependancy mess on the old box to clean up before cutting over. Any ideas what's going on here? Is this related to the large number of users and the size of the partition? I've seen some of the discussions about snapshots + quotas, but that seems like an entirely different issue. For the time being I've killed "background_fsck" and "check_quotas" in rc.conf, and I'll avoid dumping that fs with the snapshot flag. What other information can I provide to help better define where this bug lives? Thanks, Charles From owner-freebsd-stable@FreeBSD.ORG Sat Jul 8 03:29:05 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 830A516A4DD for ; Sat, 8 Jul 2006 03:29:05 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from nz-out-0102.google.com (nz-out-0102.google.com [64.233.162.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0C4E643D53 for ; Sat, 8 Jul 2006 03:29:03 +0000 (GMT) (envelope-from pyunyh@gmail.com) Received: by nz-out-0102.google.com with SMTP id 12so221916nzp for ; Fri, 07 Jul 2006 20:29:03 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=fCYEBmqBsVrDfrN9v3osRYA8KPNsrA1RIJCyEfCgQUX4fxEyTk0unt28dqA+ZM948nReEM/a+RpqpV4CQj1H16iONZbbY5fAJuY3byYHAistMCVb6uuZrOK06AlbBIvcJ7GchjILbdXggwh3RJYTEh7Po98SQb0xW2qCPDrGnaI= Received: by 10.36.19.19 with SMTP id 19mr3237197nzs; Fri, 07 Jul 2006 20:29:03 -0700 (PDT) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.gmail.com with ESMTP id 18sm287391nzo.2006.07.07.20.28.59; Fri, 07 Jul 2006 20:29:02 -0700 (PDT) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.13.5/8.13.5) with ESMTP id k683X04N089041 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 8 Jul 2006 12:33:00 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id k683Wtbh089027; Sat, 8 Jul 2006 12:32:55 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Sat, 8 Jul 2006 12:32:55 +0900 From: Pyun YongHyeon To: Robert Watson Message-ID: <20060708033254.GB87930@cdnetworks.co.kr> References: <44AC6793.2070608@asd.aplus.net> <20060706021444.GA76865@cdnetworks.co.kr> <44AD7297.7080605@asd.aplus.net> <20060707010341.GD82406@cdnetworks.co.kr> <44ADC2ED.4070904@asd.aplus.net> <20060707040838.GE82406@cdnetworks.co.kr> <20060707151640.D51390@fledge.watson.org> <44AEB0CB.5060102@asd.aplus.net> <20060707181750.O1171@ganymede.hub.org> <20060707223609.N60542@fledge.watson.org> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="k1lZvvs/B4yU6o8G" Content-Disposition: inline In-Reply-To: <20060707223609.N60542@fledge.watson.org> User-Agent: Mutt/1.4.2.1i Cc: Peter Jeremy , Atanas , freebsd-stable@FreeBSD.org, Michael Vince , User Freebsd Subject: Re: em device hangs on ifconfig alias ... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Jul 2006 03:29:05 -0000 --k1lZvvs/B4yU6o8G Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Fri, Jul 07, 2006 at 10:38:01PM +0100, Robert Watson wrote: > > On Fri, 7 Jul 2006, User Freebsd wrote: > > >>I think that I have patched, built and loaded the em(4) kernel module > >>correctly. After applying the patch there were no rejects, before > >>building the module I intentionally appended " (patched)" to its version > >>string in if_em.c, and could see that in dmesg every time I loaded the > >>module: em1: >>(patched)> > > > >Is it possible that we're going at this issue backwards? It isn't the > >lack of ARP packet going out that is causing the problems with moving IPs, > >but that delay that we're seeing when aliasing a new IP on the stack? The > >ARP packet *is* being attempted, but is timing out before the re-init is > >completing? > > Yes -- basically, there are two problems: > > (1) A little problem, in which an arp announcement is sent before the link > has > settled after reset. > > (2) A big problem, in which the interface is gratuitously recent requiring > long settling times. > > I'd really like to see a fix to the second of these problems (not resetting > when an IP is added or removed, resulting in link renegotiation); the first > one I'm less concerned about, although it would make some amount of sense > to do an arp announcement when the link goes up. > Ah, I see. Thanks for the insight. How about the attached patch? -- Regards, Pyun YongHyeon --k1lZvvs/B4yU6o8G Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="em.arp.HEAD.patch2" Index: if_em.c =================================================================== RCS file: /pool/ncvs/src/sys/dev/em/if_em.c,v retrieving revision 1.116 diff -u -r1.116 if_em.c --- if_em.c 6 Jun 2006 08:03:49 -0000 1.116 +++ if_em.c 8 Jul 2006 03:30:36 -0000 @@ -67,6 +67,7 @@ #include #include +#include #include #include #include @@ -692,6 +693,9 @@ EM_LOCK_ASSERT(sc); + if ((ifp->if_drv_flags & (IFF_DRV_RUNNING|IFF_DRV_OACTIVE)) != + IFF_DRV_RUNNING) + return; if (!sc->link_active) return; @@ -745,6 +749,7 @@ { struct em_softc *sc = ifp->if_softc; struct ifreq *ifr = (struct ifreq *)data; + struct ifaddr *ifa = (struct ifaddr *)data; int error = 0; if (sc->in_detach) @@ -752,9 +757,22 @@ switch (command) { case SIOCSIFADDR: - case SIOCGIFADDR: - IOCTL_DEBUGOUT("ioctl rcv'd: SIOCxIFADDR (Get/Set Interface Addr)"); - ether_ioctl(ifp, command, data); + if (ifa->ifa_addr->sa_family == AF_INET) { + /* + * XXX + * Since resetting hardware takes a very long time + * we only initialize the hardware only when it is + * absolutely required. + */ + ifp->if_flags |= IFF_UP; + if (!(ifp->if_drv_flags & IFF_DRV_RUNNING)) { + EM_LOCK(sc); + em_init_locked(sc); + EM_UNLOCK(sc); + } + arp_ifinit(ifp, ifa); + } else + error = ether_ioctl(ifp, command, data); break; case SIOCSIFMTU: { @@ -802,17 +820,19 @@ IOCTL_DEBUGOUT("ioctl rcv'd: SIOCSIFFLAGS (Set Interface Flags)"); EM_LOCK(sc); if (ifp->if_flags & IFF_UP) { - if (!(ifp->if_drv_flags & IFF_DRV_RUNNING)) { + if ((ifp->if_drv_flags & IFF_DRV_RUNNING)) { + if ((ifp->if_flags ^ sc->if_flags) & + IFF_PROMISC) { + em_disable_promisc(sc); + em_set_promisc(sc); + } + } else em_init_locked(sc); - } - - em_disable_promisc(sc); - em_set_promisc(sc); } else { - if (ifp->if_drv_flags & IFF_DRV_RUNNING) { + if (ifp->if_drv_flags & IFF_DRV_RUNNING) em_stop(sc); - } } + sc->if_flags = ifp->if_flags; EM_UNLOCK(sc); break; case SIOCADDMULTI: @@ -878,8 +898,8 @@ break; } default: - IOCTL_DEBUGOUT1("ioctl received: UNKNOWN (0x%x)", (int)command); - error = EINVAL; + error = ether_ioctl(ifp, command, data); + break; } return (error); Index: if_em.h =================================================================== RCS file: /pool/ncvs/src/sys/dev/em/if_em.h,v retrieving revision 1.44 diff -u -r1.44 if_em.h --- if_em.h 15 Feb 2006 08:39:50 -0000 1.44 +++ if_em.h 8 Jul 2006 03:30:43 -0000 @@ -259,6 +259,7 @@ struct callout timer; struct callout tx_fifo_timer; int io_rid; + int if_flags; struct mtx mtx; int em_insert_vlan_header; struct task link_task; --k1lZvvs/B4yU6o8G Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="em.arp.REL_6.patch2" Index: if_em.c =================================================================== RCS file: /pool/ncvs/src/sys/dev/em/if_em.c,v retrieving revision 1.65.2.16 diff -u -r1.65.2.16 if_em.c --- if_em.c 19 May 2006 00:19:57 -0000 1.65.2.16 +++ if_em.c 8 Jul 2006 03:29:16 -0000 @@ -657,8 +657,9 @@ mtx_assert(&adapter->mtx, MA_OWNED); - if (!adapter->link_active) - return; + if ((ifp->if_drv_flags & (IFF_DRV_RUNNING|IFF_DRV_OACTIVE)) != + IFF_DRV_RUNNING) + return; while (!IFQ_DRV_IS_EMPTY(&ifp->if_snd)) { @@ -714,15 +715,29 @@ { struct ifreq *ifr = (struct ifreq *) data; struct adapter * adapter = ifp->if_softc; + struct ifaddr *ifa = (struct ifaddr *)data; int error = 0; if (adapter->in_detach) return(error); switch (command) { case SIOCSIFADDR: - case SIOCGIFADDR: - IOCTL_DEBUGOUT("ioctl rcv'd: SIOCxIFADDR (Get/Set Interface Addr)"); - ether_ioctl(ifp, command, data); + if (ifa->ifa_addr->sa_family == AF_INET) { + /* + * XXX + * Since resetting hardware takes a very long time + * we only initialize the hardware only when it is + * absolutely required. + */ + ifp->if_flags |= IFF_UP; + if (!(ifp->if_drv_flags & IFF_DRV_RUNNING)) { + EM_LOCK(adapter); + em_init_locked(adapter); + EM_UNLOCK(adapter); + } + arp_ifinit(ifp, ifa); + } else + error = ether_ioctl(ifp, command, data); break; case SIOCSIFMTU: { @@ -760,12 +775,14 @@ IOCTL_DEBUGOUT("ioctl rcv'd: SIOCSIFFLAGS (Set Interface Flags)"); EM_LOCK(adapter); if (ifp->if_flags & IFF_UP) { - if (!(ifp->if_drv_flags & IFF_DRV_RUNNING)) { + if ((ifp->if_drv_flags & IFF_DRV_RUNNING)) { + if ((ifp->if_flags ^ adapter->if_flags) & + IFF_PROMISC) { + em_disable_promisc(adapter); + em_set_promisc(adapter); + } + } else em_init_locked(adapter); - } - - em_disable_promisc(adapter); - em_set_promisc(adapter); } else { if (ifp->if_drv_flags & IFF_DRV_RUNNING) { em_stop(adapter); @@ -835,8 +852,8 @@ break; } default: - IOCTL_DEBUGOUT1("ioctl received: UNKNOWN (0x%x)", (int)command); - error = EINVAL; + error = ether_ioctl(ifp, command, data); + break; } return(error); Index: if_em.h =================================================================== RCS file: /pool/ncvs/src/sys/dev/em/if_em.h,v retrieving revision 1.32.2.2 diff -u -r1.32.2.2 if_em.h --- if_em.h 25 Nov 2005 14:11:59 -0000 1.32.2.2 +++ if_em.h 8 Jul 2006 03:29:25 -0000 @@ -65,6 +65,7 @@ #include #include +#include #include #include #include @@ -331,6 +332,7 @@ struct callout timer; struct callout tx_fifo_timer; int io_rid; + int if_flags; u_int8_t unit; struct mtx mtx; int em_insert_vlan_header; --k1lZvvs/B4yU6o8G-- From owner-freebsd-stable@FreeBSD.ORG Sat Jul 8 07:18:16 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 44DF516A4DA; Sat, 8 Jul 2006 07:18:16 +0000 (UTC) (envelope-from freebsd@bitparts.org) Received: from mail.bitparts.org (63-253-101-190.ip.mcleodusa.net [63.253.101.190]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8451243D5A; Sat, 8 Jul 2006 07:18:11 +0000 (GMT) (envelope-from freebsd@bitparts.org) Received: from [127.0.0.1] (71-11-157-24.dhcp.stls.mo.charter.com [71.11.157.24]) (authenticated bits=0) by mail.bitparts.org (8.13.6/8.13.6) with ESMTP id k687I8vH085176; Sat, 8 Jul 2006 02:18:10 -0500 (CDT) (envelope-from freebsd@bitparts.org) Message-ID: <44AF5C34.8000801@bitparts.org> Date: Sat, 08 Jul 2006 02:18:12 -0500 From: "J. Buck Caldwell" User-Agent: Thunderbird 1.5.0.4 (Windows/20060516) MIME-Version: 1.0 To: freebsd-pf@freebsd.org, freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Received-SPF: pass (mail.bitparts.org: authenticated connection) receiver=mail.bitparts.org; client-ip=71.11.157.24; helo=[127.0.0.1]; envelope-from=freebsd@bitparts.org; x-software=spfmilter 0.93 http://www.acme.com/software/spfmilter/; Cc: Subject: SNMP access to pf ALTQ data? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Jul 2006 07:18:16 -0000 Forgive the cross-posting, but I think I need a wider audience. Is it possible to track pf ALTQ usage with MRTG? I notice that FreeBSD's built-in bsnmpd has a module and mibs to support pf, but I know too little about SNMP to figure out how to access the queue stats. Specifically, I'm looking to make a series of MRTG graphs that show the total bytes that pass through each queue. I figure if worst comes to worst, I can work out a separate program that parses the output of 'pfctl -vsq' and returns that as MRTG-readable input, but it would be much smoother to get it via SNMP, if it can be done. Any help would be appreciated. I'm sure others would be interested in this as well. From owner-freebsd-stable@FreeBSD.ORG Sat Jul 8 07:29:13 2006 Return-Path: X-Original-To: freebsd-stable@FreeBSD.org Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4C5D516A4DE; Sat, 8 Jul 2006 07:29:13 +0000 (UTC) (envelope-from mv@thebeastie.org) Received: from p4.roq.com (ns1.ecoms.com [207.44.130.137]) by mx1.FreeBSD.org (Postfix) with ESMTP id C4C6343D45; Sat, 8 Jul 2006 07:29:10 +0000 (GMT) (envelope-from mv@thebeastie.org) Received: from p4.roq.com (localhost.roq.com [127.0.0.1]) by p4.roq.com (Postfix) with ESMTP id 5A5184CD72; Sat, 8 Jul 2006 07:29:32 +0000 (GMT) Received: from vaulte.jumbuck.com (ppp166-27.static.internode.on.net [150.101.166.27]) by p4.roq.com (Postfix) with ESMTP id A7EA24CD63; Sat, 8 Jul 2006 07:29:31 +0000 (GMT) Received: from vaulte.jumbuck.com (localhost [127.0.0.1]) by vaulte.jumbuck.com (Postfix) with ESMTP id 5AD578A061; Sat, 8 Jul 2006 17:29:00 +1000 (EST) Received: from [192.168.0.6] (ppp157-158.static.internode.on.net [150.101.157.158]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by vaulte.jumbuck.com (Postfix) with ESMTP id 81FA68A01F; Sat, 8 Jul 2006 17:28:54 +1000 (EST) Message-ID: <44AF5EB2.2040701@thebeastie.org> Date: Sat, 08 Jul 2006 17:28:50 +1000 From: Michael Vince User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.13) Gecko/20060526 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Robert Watson References: <20060629083130.X1229@ganymede.hub.org> <44A4A02A.9060802@thebeastie.org> <20060630012615.Q1103@ganymede.hub.org> <44A57B71.6020201@asd.aplus.net> <20060701035416.GC54876@cdnetworks.co.kr> <44AC6793.2070608@asd.aplus.net> <20060706021444.GA76865@cdnetworks.co.kr> <44AD7297.7080605@asd.aplus.net> <20060707010341.GD82406@cdnetworks.co.kr> <44ADC2ED.4070904@asd.aplus.net> <20060707040838.GE82406@cdnetworks.co.kr> <20060707151640.D51390@fledge.watson.org> <44AEB0CB.5060102@asd.aplus.net> <20060707181750.O1171@ganymede.hub.org> <20060707223609.N60542@fledge.watson.org> In-Reply-To: <20060707223609.N60542@fledge.watson.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP X-Virus-Scanned: ClamAV using ClamSMTP Cc: Pyun YongHyeon , Peter Jeremy , Atanas , freebsd-stable@FreeBSD.org, User Freebsd Subject: Re: em device hangs on ifconfig alias ... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Jul 2006 07:29:13 -0000 Robert Watson wrote: > > On Fri, 7 Jul 2006, User Freebsd wrote: > >>> I think that I have patched, built and loaded the em(4) kernel >>> module correctly. After applying the patch there were no rejects, >>> before building the module I intentionally appended " (patched)" to >>> its version string in if_em.c, and could see that in dmesg every >>> time I loaded the module: em1: >> Version - 3.2.18 (patched)> >> >> >> Is it possible that we're going at this issue backwards? It isn't >> the lack of ARP packet going out that is causing the problems with >> moving IPs, but that delay that we're seeing when aliasing a new IP >> on the stack? The ARP packet *is* being attempted, but is timing out >> before the re-init is completing? > > > Yes -- basically, there are two problems: > > (1) A little problem, in which an arp announcement is sent before the > link has > settled after reset. > > (2) A big problem, in which the interface is gratuitously recent > requiring > long settling times. I thought I remember a developer working on the em driver saying just before 6.1 was released that this reset was needed and couldn't be avoided to ensure performance of the device to work at its best, I can't remember his explanation, but this topic has come up before, of course anything is possible to fix. Mike From owner-freebsd-stable@FreeBSD.ORG Sat Jul 8 08:51:36 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EF2AD16A4DE for ; Sat, 8 Jul 2006 08:51:36 +0000 (UTC) (envelope-from fullermd@over-yonder.net) Received: from mail.localelinks.com (web.localelinks.com [64.39.75.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3169A43D46 for ; Sat, 8 Jul 2006 08:51:33 +0000 (GMT) (envelope-from fullermd@over-yonder.net) Received: from draco.over-yonder.net (adsl-072-148-013-213.sip.jan.bellsouth.net [72.148.13.213]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.localelinks.com (Postfix) with ESMTP id 3A58A382; Sat, 8 Jul 2006 03:51:33 -0500 (CDT) Received: by draco.over-yonder.net (Postfix, from userid 100) id 7A5A561C2B; Sat, 8 Jul 2006 03:51:32 -0500 (CDT) Date: Sat, 8 Jul 2006 03:51:32 -0500 From: "Matthew D. Fuller" To: Charles Sprickman Message-ID: <20060708085132.GD98476@over-yonder.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Editor: vi X-OS: FreeBSD User-Agent: Mutt/1.5.11-fullermd.3 Cc: freebsd-stable@freebsd.org Subject: Re: 6.1 quota issues X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Jul 2006 08:51:37 -0000 On Fri, Jul 07, 2006 at 10:56:47PM -0400 I heard the voice of Charles Sprickman, and lo! it spake thus: > > Trying again, it reported the same inconsistencies then sat there > for more than an hour taking up all the available CPU on the box > until I killed it. The mtime on quota.user had not changed during > the run. FWIW, I saw this on a box I setup running a late November -CURRENT last year; I could never get the quotas setup and running right because the check always just looped itself up. The partition they're on has about 3 gig used out of ~45, with maybe a dozen users. I never spent much time on it, since it's just a personal box, and the quotas are mostly just to provide a handy measure of who's using what (no limits set). I just gave it up and decided to worry about it later. -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream. From owner-freebsd-stable@FreeBSD.ORG Sat Jul 8 09:21:49 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ACF2216A4DA for ; Sat, 8 Jul 2006 09:21:49 +0000 (UTC) (envelope-from johan@stromnet.org) Received: from pne-smtpout2-sn2.hy.skanova.net (pne-smtpout2-sn2.hy.skanova.net [81.228.8.164]) by mx1.FreeBSD.org (Postfix) with ESMTP id 311F243D49 for ; Sat, 8 Jul 2006 09:21:48 +0000 (GMT) (envelope-from johan@stromnet.org) Received: from elfi.stromnet.org (213.67.205.103) by pne-smtpout2-sn2.hy.skanova.net (7.2.075) id 44A2F19F001FBFB4; Sat, 8 Jul 2006 11:21:46 +0200 Received: from localhost (localhost [127.0.0.1]) by elfi.stromnet.org (Postfix) with ESMTP id 9729561D62; Sat, 8 Jul 2006 11:21:44 +0200 (CEST) X-Virus-Scanned: amavisd-new at stromnet.org Received: from elfi.stromnet.org ([127.0.0.1]) by localhost (elfi.stromnet.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XjwcxaNQM20v; Sat, 8 Jul 2006 11:21:42 +0200 (CEST) Received: from [192.168.36.100] (81-232-42-209-no37.tbcn.telia.com [81.232.42.209]) by elfi.stromnet.org (Postfix) with ESMTP id 05F1F61D4D; Sat, 8 Jul 2006 11:21:41 +0200 (CEST) In-Reply-To: <44AF5C34.8000801@bitparts.org> References: <44AF5C34.8000801@bitparts.org> Mime-Version: 1.0 (Apple Message framework v750) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: =?ISO-8859-1?Q?Johan_Str=F6m?= Date: Sat, 8 Jul 2006 11:21:50 +0200 To: J. Buck Caldwell X-Mailer: Apple Mail (2.750) Cc: freebsd-stable@freebsd.org Subject: Re: SNMP access to pf ALTQ data? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Jul 2006 09:21:49 -0000 On 8 jul 2006, at 09.18, J. Buck Caldwell wrote: > Forgive the cross-posting, but I think I need a wider audience. > > Is it possible to track pf ALTQ usage with MRTG? I notice that > FreeBSD's built-in bsnmpd has a module and mibs to support pf, but > I know too little about SNMP to figure out how to access the queue > stats. > > Specifically, I'm looking to make a series of MRTG graphs that show > the total bytes that pass through each queue. I figure if worst > comes to worst, I can work out a separate program that parses the > output of 'pfctl -vsq' and returns that as MRTG-readable input, but > it would be much smoother to get it via SNMP, if it can be done. I got one of those, a small python script which feeds the data into a rrd file: https://svn.stromnet.org/repos/misc/trunk/rrd/pfque-rrd.py Works fine, the only problem I have is when i reload my rules (that is, reset the counters).. The graph goes mad ;) Altough, if there is some way to do this via SNMP instead, I would also like to know... The above scripts uses tftp to move the rrdfiles to my graphing host. I call it from crontab every minute. For the graphing I use this: https://svn.stromnet.org/repos/misc/trunk/rrd/pfque-graph.py And the result looks like this: http://stats.stromnet.org/router/details.php?file=pfqueue_out If you look at the last month/year graphs, you see the problem with resetting the counters.. > > Any help would be appreciated. I'm sure others would be interested > in this as well. > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable- > unsubscribe@freebsd.org" From owner-freebsd-stable@FreeBSD.ORG Sat Jul 8 12:30:29 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9B9C416A4DF for ; Sat, 8 Jul 2006 12:30:29 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from home.quip.cz (grimm.quip.cz [213.220.192.218]) by mx1.FreeBSD.org (Postfix) with ESMTP id CC76143D45 for ; Sat, 8 Jul 2006 12:30:27 +0000 (GMT) (envelope-from 000.fbsd@quip.cz) Received: from [192.168.1.2] (qwork.quip.test [192.168.1.2]) by home.quip.cz (Postfix) with ESMTP id CA02B18EC for ; Sat, 8 Jul 2006 14:30:25 +0200 (CEST) Message-ID: <44AFA561.4020104@quip.cz> Date: Sat, 08 Jul 2006 14:30:25 +0200 From: Miroslav Lachman <000.fbsd@quip.cz> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.12) Gecko/20050915 X-Accept-Language: cs, cz, en, en-us MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: portupgrade-2.1.3.2,2 doesn't work with db42 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Jul 2006 12:30:29 -0000 I am upgrading some machines today and those with db42 installed failed after portupgrade from portupgrade-2.1.3,1 to portupgrade-2.1.3.2,2. Every command from portupgrade package ends with: /libexec/ld-elf.so.1: /usr/local/lib/ruby/site_ruby/1.8/i386-freebsd6/bdb.so: Undefined symbol "db_version_4002" I have this problem on FreeBSD 4.11, 5.4 and 6.0. On these boxes I have more then 1 version of BDB: pkg_info -R db4\* Information for db4-4.0.14_1,1: Information for db42-4.2.52_4: Required by: postfix-2.2.10_1,1 ruby18-bdb-0.5.9 portupgrade-2.1.3.2,2 Information for db43-4.3.29: Required by: php5-dba-5.1.4 php5-extensions-1.0 On other machines with 6.1 and only db41-4.1.25_3 installed portupgrade works fine. On machine with 6.0 and db4-4.0.14_1,1 db43-4.3.29 installed works fine too. (portupgrade depends on db43-4.3.29) Only on those machines with BDB 4.2 portupgrade stop working. This is the end of `portupgrade portupgrade` command: ===> Registering installation for portupgrade-2.1.3.2,2 ===> Building package for portupgrade-2.1.3.2,2 Creating package /usr/ports/packages/All/portupgrade-2.1.3.2,2.tbz Registering depends: ruby18-bdb-0.5.9 ldconfig_compat-1.0_8 perl-5.8.8 ruby-1.8.4_8,1 db42-4.2.52_4. Registering conflicts: portupgrade-devel-*. Creating bzip'd tar ball in '/usr/ports/packages/All/portupgrade-2.1.3.2,2.tbz' ===> Cleaning for ruby-1.8.4_8,1 ===> Cleaning for ruby18-bdb-0.5.9 ===> Cleaning for ldconfig_compat-1.0_8 ===> Cleaning for perl-5.8.8 ===> Cleaning for db42-4.2.52_4 ===> Cleaning for libtool-1.5.22_2 ===> Cleaning for portupgrade-2.1.3.2,2 ---> Cleaning out obsolete shared libraries /libexec/ld-elf.so.1: /usr/local/lib/ruby/site_ruby/1.8/i386-freebsd5/bdb.so: Undefined symbol "db_version_4002" ---> Upgrade tasks: 1 ---> Summary: 1 done, 0 ignored, 0 skipped and 0 failed /libexec/ld-elf.so.1: /usr/local/lib/ruby/site_ruby/1.8/i386-freebsd5/bdb.so: Undefined symbol "db_version_4002" /usr/local/lib/ruby/site_ruby/1.8/pkgtools.rb:450:in `__system': Command failed [exit code 1]: /usr/local/sbin/pkgdb -aFQ (CommandFailedError) from /usr/local/lib/ruby/site_ruby/1.8/pkgtools.rb:473:in `__sudo' from /usr/local/lib/ruby/site_ruby/1.8/pkgtools.rb:479:in `xsystem!' from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:961:in `autofix!' from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:957:in `autofix' from /usr/local/sbin/portupgrade:475:in `main' from /usr/local/sbin/portupgrade:718:in `main' from /usr/local/lib/ruby/1.8/optparse.rb:815:in `initialize' from /usr/local/sbin/portupgrade:209:in `main' from /usr/local/sbin/portupgrade:1978 On FreeBSD 4.11 with db4, db41, db42 and db43 installed: Creating gzip'd tar ball in '/usr/ports/packages/All/portupgrade-2.1.3.2,2.tgz' ===> Cleaning for ruby-1.8.4_8,1 ===> Cleaning for ruby18-bdb-0.5.9 ===> Cleaning for ldconfig_compat-1.0_8 ===> Cleaning for openssl-0.9.8b_1 ===> Cleaning for db41-4.1.25_3 ===> Cleaning for rc_subr-1.31_1 ===> Cleaning for portupgrade-2.1.3.2,2 ---> Cleaning out obsolete shared libraries /usr/local/lib/ruby/site_ruby/1.8/i386-freebsd4/bdb.so: (NotImplementedError) BDB needs compatible versions of libdb & db.h you have db.h version 4.1.25 and libdb version 4.3.29 from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:152:in `set_db_driver' from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:81:in `setup' from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:76:in `initialize' from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:5:in `new' from /usr/local/lib/ruby/1.8/singleton.rb:95:in `instance' from /usr/local/lib/ruby/site_ruby/1.8/pkgtools.rb:206:in `init_pkgtools_global' from /usr/local/lib/ruby/site_ruby/1.8/pkgtools.rb:1155 from /usr/local/sbin/portsclean:35 ---> Upgrade tasks: 1 ---> Summary: 1 done, 0 ignored, 0 skipped and 0 failed /usr/local/lib/ruby/site_ruby/1.8/i386-freebsd4/bdb.so: (NotImplementedError) BDB needs compatible versions of libdb & db.h you have db.h version 4.1.25 and libdb version 4.3.29 from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:152:in `set_db_driver' from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:81:in `setup' from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:76:in `initialize' from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:5:in `new' from /usr/local/lib/ruby/1.8/singleton.rb:95:in `instance' from /usr/local/lib/ruby/site_ruby/1.8/pkgtools.rb:206:in `init_pkgtools_global' from /usr/local/lib/ruby/site_ruby/1.8/pkgtools.rb:1155 from /usr/local/sbin/pkgdb:36 /usr/local/lib/ruby/site_ruby/1.8/pkgtools.rb:450:in `__system': Command failed [exit code 1]: /usr/local/sbin/pkgdb -aFQ (CommandFailedError) from /usr/local/lib/ruby/site_ruby/1.8/pkgtools.rb:473:in `__sudo' from /usr/local/lib/ruby/site_ruby/1.8/pkgtools.rb:479:in `xsystem!' from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:961:in `autofix!' from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:957:in `autofix' from /usr/local/sbin/portupgrade:475:in `main' from /usr/local/sbin/portupgrade:718:in `main' from /usr/local/lib/ruby/1.8/optparse.rb:815:in `initialize' from /usr/local/sbin/portupgrade:209:in `main' from /usr/local/sbin/portupgrade:1978 Anybody sees this problem? (and no, this is not the problem with pkgdb.db format as was previously discussed in this list - I read /usr/ports/UPDATING carefully) Miroslav Lachman From owner-freebsd-stable@FreeBSD.ORG Sat Jul 8 14:28:10 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C16E616A4DF; Sat, 8 Jul 2006 14:28:10 +0000 (UTC) (envelope-from martin@gneto.com) Received: from mxfep02.bredband.com (mxfep02.bredband.com [195.54.107.73]) by mx1.FreeBSD.org (Postfix) with ESMTP id B185743D46; Sat, 8 Jul 2006 14:28:07 +0000 (GMT) (envelope-from martin@gneto.com) Received: from ua-83-227-181-30.cust.bredbandsbolaget.se ([83.227.181.30] [83.227.181.30]) by mxfep02.bredband.com with ESMTP id <20060708142806.INMR13023.mxfep02.bredband.com@ua-83-227-181-30.cust.bredbandsbolaget.se>; Sat, 8 Jul 2006 16:28:06 +0200 Received: from [192.168.10.11] (euklides.gneto.com [192.168.10.11]) by ua-83-227-181-30.cust.bredbandsbolaget.se (Postfix) with ESMTP id 5F12067922; Sat, 8 Jul 2006 16:28:05 +0200 (CEST) Message-ID: <44AFC0F5.5010204@gneto.com> Date: Sat, 08 Jul 2006 16:28:05 +0200 From: Martin Nilsson User-Agent: Thunderbird 1.5.0.4 (X11/20060606) MIME-Version: 1.0 To: John Baldwin References: <20060629193346.GA2548@dragon.NUXI.org> <44AD6756.4070008@rogers.com> <44ADC08B.8000408@rogers.com> <200607071343.14205.jhb@freebsd.org> In-Reply-To: <200607071343.14205.jhb@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Mike Jakubik , stable@freebsd.org, freebsd-current@freebsd.org Subject: Re: Still getting 'calcru: runtime went backwards' X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Jul 2006 14:28:11 -0000 John Baldwin wrote: > On Thursday 06 July 2006 22:01, Mike Jakubik wrote: >> I'm getting a ton of them now, and i found a way to reproduce them. >> Basically i run a compile session in one terminal, say make buildkernel, >> and run top in another. As soon as i run top, the messages appear, and >> they seem to be synchronized with the refresh rate of top, 2 messages >> per refresh. This is on a 6.1-STABLE as of today. My PDSMi board is rev 1.01 and BIOS is latest 1.1a I'm using a Pentium D 930 CPU. The below is a cut-n-paste from a fresh boot, note the strange runtime for the swi4 and yarrow processes. em0: flags=8843 mtu 1500 options=b inet6 fe80::230:48ff:fe59:9336%em0 prefixlen 64 scopeid 0x1 inet 192.168.10.123 netmask 0xffffff00 broadcast 192.168.10.255 ether 00:30:48:59:93:36 media: Ethernet autoselect status: no carrier Additional routing options:. calcru: negative runtime of -1357866 usec for pid 13 (swi4: clock sio) calcru: negative runtime of -1357866 usec for pid 13 (swi4: clock sio) Starting devd. Starting ums0 moused:. hw.acpi.cpu.cx_lowest: C1 -> C1 calcru: negative runtime of -1344389 usec for pid 13 (swi4: clock sio) calcru: negative runtime of -1344389 usec for pid 13 (swi4: clock sio) Mounting NFS file systems:. ELF ldconfig path: /lib /usr/lib /usr/lib/compat /usr/X11R6/lib /usr/local/lib 32-bit compatibility ldconfig path: /usr/lib32 calcru: negative runtime of -1329710 usec for pid 13 (swi4: clock sio) calcru: negative runtime of -1329702 usec for pid 13 (swi4: clock sio) Creating and/or trimming log files:. Starting syslogd. Initial amd64 initialization:. Additional ABI support:. Additional ABI support:. NFS access cache time=2 calcru: negative runtime of -1313861 usec for pid 13 (swi4: clock sio) calcru: negative runtime of -1313861 usec for pid 13 (swi4: clock sio) Starting usbd. Starting local daemons:. Updating motd. Configuring syscons: keymap blanktime. Starting sshd. Starting cron. Local package initialization:. Additional TCP options:. Starting background file system checks in 60 seconds. Sat Jul 8 16:11:41 CEST 2006 FreeBSD/amd64 (t127.gneto.com) (ttyv0) login: root Password: FreeBSD 6.1-STABLE (SMP) #0: Fri Jul 7 09:23:24 CEST 2006 Welcome to FreeBSD! t127# ps -ax |more calcru: negative runtime of -663686 usec for pid 16 (yarrow) calcru: negative runtime of -25532 usec for pid 13 (swi4: clock sio) calcru: negative runtime of -663686 usec for pid 16 (yarrow) calcru: negative runtime of -25532 usec for pid 13 (swi4: clock sio) PID TT STAT TIME COMMAND 0 ?? WLs 0:00.00 [swapper] 11 ?? RL 5:41.36 [idle: cpu1] 12 ?? RL 5:42.47 [idle: cpu0] 13 ?? WL 307445734561:49.53 [swi4: clock sio] 14 ?? WL 0:00.00 [swi3: vm] 15 ?? WL 0:00.00 [swi1: net] 16 ?? DL 307445734561:48.89 [yarrow] 17 ?? WL 0:00.00 [swi2: cambio] From owner-freebsd-stable@FreeBSD.ORG Sat Jul 8 14:34:21 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C404116A4DA for ; Sat, 8 Jul 2006 14:34:21 +0000 (UTC) (envelope-from barney@databus.com) Received: from pit.databus.com (p72-0-224-2.acedsl.com [72.0.224.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 61FA143D46 for ; Sat, 8 Jul 2006 14:34:20 +0000 (GMT) (envelope-from barney@databus.com) Received: from pit.databus.com (localhost [127.0.0.1]) by pit.databus.com (8.13.6/8.13.6) with ESMTP id k68EYJxi049424; Sat, 8 Jul 2006 10:34:19 -0400 (EDT) (envelope-from barney@pit.databus.com) Received: (from barney@localhost) by pit.databus.com (8.13.6/8.13.6/Submit) id k68EYJbn049423; Sat, 8 Jul 2006 10:34:19 -0400 (EDT) (envelope-from barney) Date: Sat, 8 Jul 2006 10:34:19 -0400 From: Barney Wolff To: Miroslav Lachman <000.fbsd@quip.cz> Message-ID: <20060708143419.GB47731@pit.databus.com> References: <44AFA561.4020104@quip.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <44AFA561.4020104@quip.cz> User-Agent: Mutt/1.5.11 X-Scanned-By: MIMEDefang 2.56 on 66.114.72.185 Cc: freebsd-stable@freebsd.org Subject: Re: portupgrade-2.1.3.2,2 doesn't work with db42 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Jul 2006 14:34:21 -0000 On Sat, Jul 08, 2006 at 02:30:25PM +0200, Miroslav Lachman wrote: > I am upgrading some machines today and those with db42 installed failed > after portupgrade from portupgrade-2.1.3,1 to portupgrade-2.1.3.2,2. > Every command from portupgrade package ends with: > /libexec/ld-elf.so.1: > /usr/local/lib/ruby/site_ruby/1.8/i386-freebsd6/bdb.so: Undefined symbol > "db_version_4002" > > I have this problem on FreeBSD 4.11, 5.4 and 6.0. On these boxes I have > more then 1 version of BDB: I had the same problem. Fixed it by deleting db41 and rebuilding db42, ruby-bdb and portupgrade. -- Barney Wolff I never met a computer I didn't like. From owner-freebsd-stable@FreeBSD.ORG Sat Jul 8 14:42:28 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 28A7916A4E1 for ; Sat, 8 Jul 2006 14:42:28 +0000 (UTC) (envelope-from mhjacks@swbell.net) Received: from smtp113.sbc.mail.mud.yahoo.com (smtp113.sbc.mail.mud.yahoo.com [68.142.198.212]) by mx1.FreeBSD.org (Postfix) with SMTP id 9198743D45 for ; Sat, 8 Jul 2006 14:42:27 +0000 (GMT) (envelope-from mhjacks@swbell.net) Received: (qmail 93177 invoked from network); 8 Jul 2006 14:42:26 -0000 Received: from unknown (HELO anduril.minas.tirith) (mhjacks@swbell.net@65.67.72.193 with login) by smtp113.sbc.mail.mud.yahoo.com with SMTP; 8 Jul 2006 14:42:26 -0000 Received: from localhost (localhost [127.0.0.1]) by anduril.minas.tirith (Postfix) with ESMTP id 9C6C32E028; Sat, 8 Jul 2006 09:42:25 -0500 (CDT) X-Virus-Scanned: amavisd-new at minas.tirith Received: from anduril.minas.tirith ([127.0.0.1]) by localhost (anduril.minas.tirith [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id crhA4q9btZRk; Sat, 8 Jul 2006 09:42:24 -0500 (CDT) Received: from [192.168.2.102] (arwen.minas.tirith [192.168.2.102]) by anduril.minas.tirith (Postfix) with ESMTP id 2D2942E027; Sat, 8 Jul 2006 09:42:24 -0500 (CDT) Message-ID: <44AFC449.70608@swbell.net> Date: Sat, 08 Jul 2006 09:42:17 -0500 From: Martin Jackson User-Agent: Thunderbird 1.5.0.4 (Windows/20060516) MIME-Version: 1.0 To: Barney Wolff References: <44AFA561.4020104@quip.cz> <20060708143419.GB47731@pit.databus.com> In-Reply-To: <20060708143419.GB47731@pit.databus.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, Miroslav Lachman <000.fbsd@quip.cz> Subject: Re: portupgrade-2.1.3.2,2 doesn't work with db42 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Jul 2006 14:42:28 -0000 > I had the same problem. Fixed it by deleting db41 and rebuilding db42, > ruby-bdb and portupgrade. > I had the same problem - but I fixed mine by removing ruby-bdb (since I only used it for portupgrade) and rebuilding portupgrade to use ruby-bdb1. I love portupgrade, but it seems a little...delicate...when it's upgraded. :) Thanks, Marty From owner-freebsd-stable@FreeBSD.ORG Sat Jul 8 15:06:05 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F16CD16A4DD; Sat, 8 Jul 2006 15:06:05 +0000 (UTC) (envelope-from freebsd@hub.org) Received: from hub.org (hub.org [200.46.204.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6697B43D45; Sat, 8 Jul 2006 15:06:05 +0000 (GMT) (envelope-from freebsd@hub.org) Received: from localhost (wm.hub.org [200.46.204.128]) by hub.org (Postfix) with ESMTP id 3F6BC290C6C; Sat, 8 Jul 2006 12:06:00 -0300 (ADT) Received: from hub.org ([200.46.204.220]) by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024) with ESMTP id 37990-03; Sat, 8 Jul 2006 15:05:59 +0000 (UTC) Received: from ganymede.hub.org (blk-224-179-167.eastlink.ca [24.224.179.167]) by hub.org (Postfix) with ESMTP id A52CC290C6A; Sat, 8 Jul 2006 12:05:59 -0300 (ADT) Received: by ganymede.hub.org (Postfix, from userid 1027) id 103AB47BC1; Sat, 8 Jul 2006 12:05:58 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id 0F0464714C; Sat, 8 Jul 2006 12:05:58 -0300 (ADT) Date: Sat, 8 Jul 2006 12:05:58 -0300 (ADT) From: User Freebsd To: Michael Vince In-Reply-To: <44AF5EB2.2040701@thebeastie.org> Message-ID: <20060708120252.K1799@ganymede.hub.org> References: <20060629083130.X1229@ganymede.hub.org> <44A4A02A.9060802@thebeastie.org> <20060630012615.Q1103@ganymede.hub.org> <44A57B71.6020201@asd.aplus.net> <20060701035416.GC54876@cdnetworks.co.kr> <44AC6793.2070608@asd.aplus.net> <20060706021444.GA76865@cdnetworks.co.kr> <44AD7297.7080605@asd.aplus.net> <20060707010341.GD82406@cdnetworks.co.kr> <44ADC2ED.4070904@asd.aplus.net> <20060707040838.GE82406@cdnetworks.co.kr> <20060707151640.D51390@fledge.watson.org> <44AEB0CB.5060102@asd.aplus.net> <20060707181750.O1171@ganymede.hub.org> <20060707223609.N60542@fledge.watson.org> <44AF5EB2.2040701@thebeastie.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Pyun YongHyeon , Peter Jeremy , Atanas , Robert Watson , freebsd-stable@FreeBSD.org Subject: Re: em device hangs on ifconfig alias ... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Jul 2006 15:06:06 -0000 On Sat, 8 Jul 2006, Michael Vince wrote: > I thought I remember a developer working on the em driver saying just > before 6.1 was released that this reset was needed and couldn't be > avoided to ensure performance of the device to work at its best, I can't > remember his explanation, but this topic has come up before, of course > anything is possible to fix. The thing is, and I may be mis-understanding the explanations so far, the 'reset' is to renegotiate the connection ... if that is the case, and both the switch and the interface are already locked at a speed (in my case, both are hard coded to "100baseTX full duplex", then what is there to re-negotiate? And, why does it appear that *only* the em driver/interface requires this? I run bge and fxp interfaces on this same network, against the same switch, all locked at the same speed, and only the em driver exhibits this problem ... in fact, its only the *newer* em driver that does, as I have one server on the network, using an em interface, that is running an older FreeBSD 4.x kernel, that performs the same as the bge/fxp (ie. perfectly) ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . scrappy@hub.org MSN . scrappy@hub.org Yahoo . yscrappy Skype: hub.org ICQ . 7615664 From owner-freebsd-stable@FreeBSD.ORG Sat Jul 8 17:19:33 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A1A7916A4DA; Sat, 8 Jul 2006 17:19:33 +0000 (UTC) (envelope-from ru@ip.net.ua) Received: from cielago.ip.net.ua (cielago.ip.net.ua [82.193.96.15]) by mx1.FreeBSD.org (Postfix) with ESMTP id ACDBC43D46; Sat, 8 Jul 2006 17:19:32 +0000 (GMT) (envelope-from ru@ip.net.ua) Received: from heffalump.ip.net.ua (heffalump.ip.net.ua [82.193.96.213]) by cielago.ip.net.ua (8.13.6/8.13.6) with ESMTP id k68HIjp9041187 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 8 Jul 2006 20:18:45 +0300 (EEST) (envelope-from ru@ip.net.ua) Received: (from ru@localhost) by heffalump.ip.net.ua (8.13.6/8.13.6) id k68HK2P3078400; Sat, 8 Jul 2006 20:20:02 +0300 (EEST) (envelope-from ru) Date: Sat, 8 Jul 2006 20:20:01 +0300 From: Ruslan Ermilov To: Pyun YongHyeon Message-ID: <20060708172001.GB77281@ip.net.ua> References: <20060706021444.GA76865@cdnetworks.co.kr> <44AD7297.7080605@asd.aplus.net> <20060707010341.GD82406@cdnetworks.co.kr> <44ADC2ED.4070904@asd.aplus.net> <20060707040838.GE82406@cdnetworks.co.kr> <20060707151640.D51390@fledge.watson.org> <44AEB0CB.5060102@asd.aplus.net> <20060707181750.O1171@ganymede.hub.org> <20060707223609.N60542@fledge.watson.org> <20060708033254.GB87930@cdnetworks.co.kr> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="0vzXIDBeUiKkjNJl" Content-Disposition: inline In-Reply-To: <20060708033254.GB87930@cdnetworks.co.kr> User-Agent: Mutt/1.5.11 X-Virus-Scanned: by amavisd-new Cc: freebsd-stable@freebsd.org, Peter Jeremy , Atanas , User Freebsd , Robert Watson , Michael Vince Subject: Re: em device hangs on ifconfig alias ... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Jul 2006 17:19:33 -0000 --0vzXIDBeUiKkjNJl Content-Type: multipart/mixed; boundary="cvVnyQ+4j833TQvp" Content-Disposition: inline --cvVnyQ+4j833TQvp Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Jul 08, 2006 at 12:32:55PM +0900, Pyun YongHyeon wrote: > On Fri, Jul 07, 2006 at 10:38:01PM +0100, Robert Watson wrote: > >=20 > > On Fri, 7 Jul 2006, User Freebsd wrote: > >=20 > > >>I think that I have patched, built and loaded the em(4) kernel modul= e=20 > > >>correctly. After applying the patch there were no rejects, before=20 > > >>building the module I intentionally appended " (patched)" to its ver= sion=20 > > >>string in if_em.c, and could see that in dmesg every time I loaded t= he=20 > > >>module: em1: > >>(patched)> > > > > > >Is it possible that we're going at this issue backwards? It isn't th= e=20 > > >lack of ARP packet going out that is causing the problems with moving= IPs,=20 > > >but that delay that we're seeing when aliasing a new IP on the stack?= The=20 > > >ARP packet *is* being attempted, but is timing out before the re-init= is=20 > > >completing? > >=20 > > Yes -- basically, there are two problems: > >=20 > > (1) A little problem, in which an arp announcement is sent before the = link=20 > > has > > settled after reset. > >=20 > > (2) A big problem, in which the interface is gratuitously recent requi= ring > > long settling times. > >=20 > > I'd really like to see a fix to the second of these problems (not rese= tting=20 > > when an IP is added or removed, resulting in link renegotiation); the = first=20 > > one I'm less concerned about, although it would make some amount of se= nse=20 > > to do an arp announcement when the link goes up. > >=20 >=20 > Ah, I see. Thanks for the insight. > How about the attached patch? >=20 I've been working on this problem for Mike Tancsa about a year ago, and my fix was naive. I ended up not committing it because I found that it broke something else, but I don't remember what exactly now. Ahh, I seem to remember now -- setting a different MAC address was not programmed into a hardware with my patch applied. Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --cvVnyQ+4j833TQvp Content-Type: message/rfc822 Content-Disposition: inline Date: Thu, 31 Mar 2005 10:59:40 +0300 From: Ruslan Ermilov To: Mike Tancsa Subject: Re: em(4) + bridging Message-ID: <20050331075940.GA75268@ip.net.ua> References: <424AB340.1060207@puffy.nu> <20050330151027.GA28805@ip.net.ua> <20050331070152.GA75009@ip.net.ua> <20050331072025.GB75009@ip.net.ua> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="KsGdsel6WgEHnImy" Content-Disposition: inline In-Reply-To: <20050331072025.GB75009@ip.net.ua> User-Agent: Mutt/1.5.9i --KsGdsel6WgEHnImy Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Mar 31, 2005 at 10:20:25AM +0300, Ruslan Ermilov wrote: > On Thu, Mar 31, 2005 at 10:01:52AM +0300, Ruslan Ermilov wrote: > > Hi Mike, > >=20 > > On Wed, Mar 30, 2005 at 08:03:21PM -0500, Mike Tancsa wrote: > > [...] > > > If you could somehow fix the problem with em bouncing its interface > > > when you add or remove an alias from it (RELENG_5), I would gladly > > > send you two nics! ;-) > > >=20 > > > eg ifconfig em0 192.168.13.9 netmask 255.255.255.252 alias > > >=20 > > > will down and up the interface. If the switch port it is in has STP, > > > the port will go into blocking for 30 seconds, which is really > > > troublesome :( > > >=20 > > Is this also a problem in HEAD, or only in RELENG_5? > >=20 > OK, I can easily reproduce the problem here, hold on. >=20 I'm not fully sure this is a right fix, but it works for me. Here's what happens: on SIOCSIFADDR, em_ioctl() is called, then ether_ioctl() which calls em_init() which calls em_hardware_init() (for some odd reason I don't understand). em_hardware_init() is correctly called on attach, so I don't understand why it's also needed in em_init(). Anyway, the hack is as easy as this: %%% Index: if_em.c =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /home/ncvs/src/sys/dev/em/if_em.c,v retrieving revision 1.62 diff -u -p -r1.62 if_em.c --- if_em.c 5 Mar 2005 18:30:10 -0000 1.62 +++ if_em.c 31 Mar 2005 07:41:47 -0000 @@ -832,12 +832,14 @@ em_init_locked(struct adapter * adapter) bcopy(adapter->interface_data.ac_enaddr, adapter->hw.mac_addr, ETHER_ADDR_LEN); =20 +#if 0 /* Initialize the hardware */ if (em_hardware_init(adapter)) { printf("em%d: Unable to initialize the hardware\n",=20 adapter->unit); return; } +#endif =20 if (ifp->if_capenable & IFCAP_VLAN_HWTAGGING) em_enable_vlans(adapter); %%% Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --KsGdsel6WgEHnImy Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFCS63sqRfpzJluFF4RAnZHAKCBea2pVCJ30D/DMmhd/agISU9y+QCfbwMI tklANWUVCgjgYYAsxGW1+rM= =beCd -----END PGP SIGNATURE----- --KsGdsel6WgEHnImy-- --cvVnyQ+4j833TQvp-- --0vzXIDBeUiKkjNJl Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEr+lBqRfpzJluFF4RAiffAKCIt9H003toOJhYlHOfk4yz8y33GACfV0LE LEmvFXwPDwIGdLCaIXisR8E= =nECB -----END PGP SIGNATURE----- --0vzXIDBeUiKkjNJl-- From owner-freebsd-stable@FreeBSD.ORG Sat Jul 8 18:47:42 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 24CD916A4E1 for ; Sat, 8 Jul 2006 18:47:42 +0000 (UTC) (envelope-from wash@wananchi.com) Received: from ns2.wananchi.com (ns2.wananchi.com [62.8.64.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id F32B143D4C for ; Sat, 8 Jul 2006 18:47:40 +0000 (GMT) (envelope-from wash@wananchi.com) Received: from wash by ns2.wananchi.com with local (Exim 4.62 #0 (FreeBSD 4.11-STABLE)) id 1FzHq0-000Kv7-Vc by authid ; Sat, 08 Jul 2006 21:47:32 +0300 Date: Sat, 8 Jul 2006 21:47:32 +0300 From: Odhiambo Washington To: 000.fbsd@quip.cz Message-ID: <20060708184732.GJ18199@wananchi.com> Mail-Followup-To: Odhiambo Washington , 000.fbsd@quip.cz, freebsd-stable@freebsd.org References: <44AFA561.4020104@quip.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <44AFA561.4020104@quip.cz> X-Disclaimer: Any views expressed in this message, where not explicitly attributed otherwise, are mine alone!. User-Agent: mutt-ng/devel-r804 (FreeBSD) Cc: freebsd-stable@freebsd.org Subject: Re: portupgrade-2.1.3.2,2 doesn't work with db42 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Jul 2006 18:47:42 -0000 * On 08/07/06 14:30 +0200, Miroslav Lachman wrote: | I am upgrading some machines today and those with db42 installed failed after portupgrade from portupgrade-2.1.3,1 | to portupgrade-2.1.3.2,2. | Every command from portupgrade package ends with: | /libexec/ld-elf.so.1: /usr/local/lib/ruby/site_ruby/1.8/i386-freebsd6/bdb.so: Undefined symbol "db_version_4002" rm /usr/local/lib/ruby/site_ruby/1.8/i386-freebsd6/bdb.so then tell me what happens if you run portupgrade again! I've gone through this today, so it's still fresh in my mind! -Wash http://www.netmeister.org/news/learn2quote.html DISCLAIMER: See http://www.wananchi.com/bms/terms.php -- +======================================================================+ |\ _,,,---,,_ | Odhiambo Washington Zzz /,`.-'`' -. ;-;;,_ | Wananchi Online Ltd. www.wananchi.com |,4- ) )-,_. ,\ ( `'-'| Tel: +254 20 313985-9 +254 20 313922 '---''(_/--' `-'\_) | GSM: +254 722 743223 +254 733 744121 +======================================================================+ When all other means of communication fail, try words. From owner-freebsd-stable@FreeBSD.ORG Sat Jul 8 19:29:26 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9985D16A4DD for ; Sat, 8 Jul 2006 19:29:26 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from home.quip.cz (grimm.quip.cz [213.220.192.218]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2BB9B43D45 for ; Sat, 8 Jul 2006 19:29:25 +0000 (GMT) (envelope-from 000.fbsd@quip.cz) Received: from [192.168.1.2] (qwork.quip.test [192.168.1.2]) by home.quip.cz (Postfix) with ESMTP id A825E4762; Sat, 8 Jul 2006 21:29:23 +0200 (CEST) Message-ID: <44B00793.2080302@quip.cz> Date: Sat, 08 Jul 2006 21:29:23 +0200 From: Miroslav Lachman <000.fbsd@quip.cz> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.12) Gecko/20050915 X-Accept-Language: cs, cz, en, en-us MIME-Version: 1.0 To: Odhiambo Washington References: <44AFA561.4020104@quip.cz> <20060708184732.GJ18199@wananchi.com> In-Reply-To: <20060708184732.GJ18199@wananchi.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: portupgrade-2.1.3.2,2 doesn't work with db42 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Jul 2006 19:29:26 -0000 Odhiambo Washington wrote: > rm /usr/local/lib/ruby/site_ruby/1.8/i386-freebsd6/bdb.so > > then tell me what happens if you run portupgrade again! > > I've gone through this today, so it's still fresh in my mind! After removing bdb.so portupgrade is working again. Thank you! Just for my knowledge - from where goes this error? What should be fixed? Ruby-bdb or portupgrade? Miroslav Lachman From owner-freebsd-stable@FreeBSD.ORG Sat Jul 8 20:52:28 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AE93916A4DA for ; Sat, 8 Jul 2006 20:52:28 +0000 (UTC) (envelope-from w8hdkim@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.174]) by mx1.FreeBSD.org (Postfix) with ESMTP id 195FE43D46 for ; Sat, 8 Jul 2006 20:52:27 +0000 (GMT) (envelope-from w8hdkim@gmail.com) Received: by ug-out-1314.google.com with SMTP id m3so1161916uge for ; Sat, 08 Jul 2006 13:52:26 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=VhRCDOpkS/QxrcALiJAzy0Wn+XEka4KFkGCLxYoDTXkZOxKenCsw4s06rqWfzWg7883CoIYB8U7mjRUPEOc1eBMSC2s7Bnj0MLP0/cZDE087OA1961V4kMVtfld016Irebc57WRu/qkIZ7/jOtgVJlLMrazZptV9ye8kpHu1+K8= Received: by 10.78.185.7 with SMTP id i7mr1194587huf; Sat, 08 Jul 2006 13:52:26 -0700 (PDT) Received: by 10.78.49.6 with HTTP; Sat, 8 Jul 2006 13:52:26 -0700 (PDT) Message-ID: <89dbfdc30607081352g2c9eca00n738ee4e77dd3335d@mail.gmail.com> Date: Sat, 8 Jul 2006 16:52:26 -0400 From: "Kim Culhan" To: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: gmake: virtual memory exhausted X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Jul 2006 20:52:28 -0000 Greetings- Compiling Asterisk on 6.1-STABLE: gmake -C db1-ast libdb1.a gmake[1]: Entering directory `/usr/local/src/asterisk/asterisk/db1-ast' gmake[1]: *** virtual memory exhausted. Stop. Any suggestion of a tuning parameter to work around this is greatly appreciated. regards -kim -- w8hdkim@gmail.com From owner-freebsd-stable@FreeBSD.ORG Sat Jul 8 22:12:58 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E2FBA16A4DA; Sat, 8 Jul 2006 22:12:58 +0000 (UTC) (envelope-from mikej@rogers.com) Received: from H43.C18.B96.tor.eicat.ca (H43.C18.B96.tor.eicat.ca [66.96.18.43]) by mx1.FreeBSD.org (Postfix) with ESMTP id 78D3243D45; Sat, 8 Jul 2006 22:12:58 +0000 (GMT) (envelope-from mikej@rogers.com) Received: from [127.0.0.1] (desktop.home.local [172.16.0.200]) by H43.C18.B96.tor.eicat.ca (Postfix) with ESMTP id 03FC31140B; Sat, 8 Jul 2006 18:13:28 -0400 (EDT) Message-ID: <44B02DEC.7000300@rogers.com> Date: Sat, 08 Jul 2006 18:13:00 -0400 From: Mike Jakubik User-Agent: Thunderbird 1.5.0.4 (Windows/20060516) MIME-Version: 1.0 To: Martin Nilsson References: <20060629193346.GA2548@dragon.NUXI.org> <44AD6756.4070008@rogers.com> <44ADC08B.8000408@rogers.com> <200607071343.14205.jhb@freebsd.org> <44AFC0F5.5010204@gneto.com> In-Reply-To: <44AFC0F5.5010204@gneto.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SpamToaster-Information: This messages has been scanned by SpamToaster http://www.digitalprogression.ca X-SpamToaster: Found to be clean X-SpamToaster-SpamCheck: not spam, SpamAssassin (not cached, score=-2.49, required 3.5, ALL_TRUSTED -1.80, BAYES_00 -2.60, DK_POLICY_SIGNSOME 0.00, DNS_FROM_RFC_ABUSE 0.20, DNS_FROM_RFC_POST 1.71) X-SpamToaster-From: mikej@rogers.com X-Spam-Status: No Cc: stable@freebsd.org, John Baldwin Subject: Re: Still getting 'calcru: runtime went backwards' X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Jul 2006 22:12:59 -0000 Martin Nilsson wrote: > John Baldwin wrote: >> On Thursday 06 July 2006 22:01, Mike Jakubik wrote: >>> I'm getting a ton of them now, and i found a way to reproduce them. >>> Basically i run a compile session in one terminal, say make >>> buildkernel, and run top in another. As soon as i run top, the >>> messages appear, and they seem to be synchronized with the refresh >>> rate of top, 2 messages per refresh. This is on a 6.1-STABLE as of >>> today. > > My PDSMi board is rev 1.01 and BIOS is latest 1.1a I'm using a Pentium > D 930 CPU. That is identical to my system, same goes for the strange swi4 and yarrow calcru messages. So this problem looks to be directly related to this hardware and bios revision. My older board (i suspect the bios is 1.1, without the a), which is running in amd64 mode and a 2.8GHz cpu does not exhibit this problem.