From owner-freebsd-net Sun Aug 19 9: 9: 8 2001 Delivered-To: freebsd-net@freebsd.org Received: from ns.okbmei.msk.su (ns.okbmei.msk.su [194.190.170.19]) by hub.freebsd.org (Postfix) with ESMTP id E843237B408 for ; Sun, 19 Aug 2001 09:09:04 -0700 (PDT) (envelope-from burba@okbmei.msk.su) Received: from okbmei.msk.su (burba.ac.orbita.ru [193.192.144.124]) by ns.okbmei.msk.su (8.11.4/8.11.4) with ESMTP id f7JG8da16144; Sun, 19 Aug 2001 20:08:39 +0400 (MSD) Message-ID: <3B7FE482.FA1F2E8D@okbmei.msk.su> Date: Sun, 19 Aug 2001 20:08:34 +0400 From: "Alex S. Burba" X-Mailer: Mozilla 4.74 [en] (Win95; U) X-Accept-Language: en MIME-Version: 1.0 To: Travis Leuthauser Cc: freebsd-net@freebsd.org Subject: Re: IPSec VPN tunnel question References: Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > What do you mean by "what ping/traceroute keys"? As I can see your SPD says that packets ONLY from 172.16.250.0/24 TO 172.16.69.0/24 should be tunneled and vice versa. But the command 'ping 172.16.250.1' equals to 'ping -S 24.181.119.107 172.16.250.1' and your polices do not permit such packets from 24.181.119.107 to 172.16.250.1 to be tunneled. So you should use command 'ping -S 172.16.69.1 172.16.250.1'. Keep in mind that IPSec just simply DROPS packets which are not permited by the policies or by the SAD. So you can see in tcpdump that something goes over the tunnel, but it can be only dropped packets. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Aug 20 4: 8:20 2001 Delivered-To: freebsd-net@freebsd.org Received: from mgw1.MEIway.com (mgw1.meiway.com [212.73.210.75]) by hub.freebsd.org (Postfix) with ESMTP id 2A38137B401 for ; Mon, 20 Aug 2001 04:08:15 -0700 (PDT) (envelope-from LConrad@Go2France.com) Received: from mail.Go2France.com (ms1.meiway.com [212.73.210.73]) by mgw1.MEIway.com (Postfix Relay Hub) with ESMTP id 6BDFD16B38 for ; Mon, 20 Aug 2001 13:08:13 +0200 (CEST) Received: from IBM-HIRXKN66F0W.Go2France.com [195.115.185.184] by mail.Go2France.com with ESMTP (SMTPD32-6.06) id A204327201DE; Mon, 20 Aug 2001 13:18:28 +0200 Message-Id: <5.1.0.14.0.20010820124519.0404bf48@mail.Go2France.com> X-Sender: LConrad@Go2France.com@mail.Go2France.com X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Mon, 20 Aug 2001 13:08:53 +0200 To: freebsd-net@freebsd.org From: Len Conrad Subject: taking ppp down and up Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1"; format=flowed Content-Transfer-Encoding: 8bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org We´re very happy with PPPoE into our cable modem ´cept the whole link isn´t reliable :)))) ... for at least the reason that France Telecom (French-govt-protected monopoly), God bless 'em, cripples their ADSL service by inserting 3 minute blackouts, at the next hop at end their end of the ADSL, link throughout the day, (ping to next hop dead) to protect their exorbitantly priced leased-line service. Usually after these blackouts, our FreeBSD PPPoE router just waits until FT´s box responds again and all is. We cast yet-another curse on FT, re-start our ssh and pcAnywhere sessions, truck along. The other pb is that sometimes, PPPoE doesn´t come back, and we wonder whether maybe, in these cases, it´s really PPPoE halting, as I´ve seen others report in these lists. It´s the PPP from 4.3-Release .iso. We of course need better reliability in the face of whatever PPP halts, so we´re trying to come up with a script we could run to take down the link (tun0, ppp) and then bring it up, and not having much success. We also run ipf and ipnat, so here´s what our script looks like: ipf -D killall ppp kill `cat /var/run/ipmon.pid` kill `cat /var/run/tun0.pid` /usr/sbin/ppp -quiet -ddial -nat -unit0 meidsl ipf -E ipf -Fa -f /etc/ipf-stats.rules ipnat -CF -f /etc/ipnat.rules /usr/sbin/ipmon -Dna /var/log/ipmon/iplog ~ Running the above with the line up, we see this on the screen: warning: /dev/tun0: Device busy 0 entries flushed from NAT table 0 entries flushed from NAT list Aug 20 12:51:13 gw0 /kernel: IP Filter: v3.4.19 unloaded gw0# Aug 20 12:51:13 gw0 /kernel: IP Filter: v3.4.19 unloaded Aug 20 12:51:13 gw0 /kernel: IP Filter: v3.4.19 initialized. Default = pass all, Logging = enabled Aug 20 12:51:13 gw0 /kernel: IP Filter: v3.4.19 initialized. Default = pass all, Logging = enabled Aug 20 12:51:13 gw0 ppp[1002]: Warning: /dev/tun0: Device busy but the line doesn´t come up, until we run the same ppprest.sh script a second time and get this on the screen: No matching processes were found cat: /var/run/tun0.pid: No such file or directory cat: /var/run/tun0.pid: No such file or directory usage: kill [-s signal_name] pid ... kill -l [exit_status] kill -signal_name pid ... kill -signal_number pid ... Aug 20 12:52:23 gw0 /kernel: IP Filter: v3.4.19 unloaded Aug 20 12:52:23 gw0 /kernel: IP Filter: v3.4.19 unloaded 0 entries flushed from NAT table 0 entries flushed from NAT list gw0# Aug 20 12:52:23 gw0 /kernel: IP Filter: v3.4.19 initialized. Default = pass all, Logging = enabled Aug 20 12:52:23 gw0 /kernel: IP Filter: v3.4.19 initialized. Default = pass all, Logging = enabled and the PPP link comes up again. We´ve tried a lot of different sequences for the script, but nothing works ON THE FIRST SCRIPT RUN, so we think we´re got wrong or missing commands. Any suggestions? Also, anybody have any ideas for a probe that will distinguish between when the FT blackout is the pb (ie, don´t run PPP restart script) vs when PPPoE is hung? Len http://MenAndMice.com/DNS-training http://BIND8NT.MEIway.com : ISC BIND 8.2.4 for NT4 & W2K http://IMGate.MEIway.com : Build free, hi-perf, anti-abuse mail gateways To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Aug 20 4:28: 5 2001 Delivered-To: freebsd-net@freebsd.org Received: from pelissero.org (dyn69-32.sftm-212-159.plus.net [212.159.32.69]) by hub.freebsd.org (Postfix) with ESMTP id 2C02237B409; Mon, 20 Aug 2001 04:27:41 -0700 (PDT) (envelope-from wcp@pelissero.org) Received: (from wcp@localhost) by pelissero.org (8.11.5/8.9.3) id f7KBRPl03252; Mon, 20 Aug 2001 12:27:25 +0100 (BST) (envelope-from wcp) From: "Walter C. Pelissero" Message-ID: <15232.62492.730149.447791@hyde.lpds.sublink.org> Date: Mon, 20 Aug 2001 12:27:24 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: hackers@freebsd.org, net@freebsd.org Subject: 4.4-RC NFS panic X-Mailer: VM 6.90 under 21.1 (patch 13) "Crater Lake" XEmacs Lucid Reply-To: walter@pelissero.org X-Attribution: WP Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org [ it seems my original article didn't get through ] I recently upgraded to 4.4-RC. Now my Vaio panics when I use NFS volumes (as client). The panic is reproducible with a: find /some/NFS/mount/point -type f -exec cat {} \; >/dev/null Sometime I got a "page fault", sometime a "lockmgr: locking against myself" Here is a kgdb session: GNU gdb 4.18 Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-unknown-freebsd". Reading symbols from kernel.debug...done. IdlePTD 3612672 initial pcb at 2bb8a0 panicstr: page fault panic messages: --- Fatal trap 12: page fault while in kernel mode fault virtual address = 0x33693d55 fault code = supervisor read, page not present instruction pointer = 0x8:0xc016dbdd stack pointer = 0x10:0xc7834c58 frame pointer = 0x10:0xc7834c64 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 180 (nfsiod) interrupt mask = net trap number = 12 panic: page fault syncing disks... 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 done Uptime: 3m58s dumping to dev #ad/0x30001, offset 272736 dump ata0: resetting devices .. done 127 126 125 124 123 122 121 120 119 118 117 116 115 114 113 112 111 110 109 108 107 106 105 104 103 102 101 100 99 98 97 96 95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 --- #0 dumpsys () at ../../kern/kern_shutdown.c:472 (kgdb) bt #0 dumpsys () at ../../kern/kern_shutdown.c:472 #1 0xc015250f in boot (howto=256) at ../../kern/kern_shutdown.c:312 #2 0xc01528dc in poweroff_wait (junk=0xc027b66c, howto=-1071140465) at ../../kern/kern_shutdown.c:580 #3 0xc023b4b2 in trap_fatal (frame=0xc7834c18, eva=862534997) at ../../i386/i386/trap.c:956 #4 0xc023b185 in trap_pfault (frame=0xc7834c18, usermode=0, eva=862534997) at ../../i386/i386/trap.c:849 #5 0xc023ad6f in trap (frame={tf_fs = 16, tf_es = 16, tf_ds = 16, tf_edi = 6684672, tf_esi = 862534981, tf_ebp = -947696540, tf_isp = -947696572, tf_ebx = 862534981, tf_edx = 6684672, tf_ecx = -1066162108, tf_eax = 6684672, tf_trapno = 12, tf_err = 0, tf_eip = -1072243747, tf_cs = 8, tf_eflags = 66054, tf_esp = -1066172160, tf_ss = -1066172160}) at ../../i386/i386/trap.c:448 #6 0xc016dbdd in m_freem (m=0x33693d45) at ../../kern/uipc_mbuf.c:618 #7 0xc016dbfc in m_freem (m=0xc0738a00) at ../../kern/uipc_mbuf.c:618 #8 0xc0b59652 in ?? () #9 0xc0b66b92 in ?? () #10 0xc0b3fe37 in ?? () #11 0xc0b606de in ?? () #12 0xc0b5f11b in ?? () #13 0xc023b75d in syscall2 (frame={tf_fs = 47, tf_es = 47, tf_ds = 47, tf_edi = -1077936680, tf_esi = 0, tf_ebp = -1077936776, tf_isp = -947695660, tf_ebx = 2, tf_edx = 1, tf_ecx = 19, tf_eax = 155, tf_trapno = 12, tf_err = 2, tf_eip = 134515664, tf_cs = 31, tf_eflags = 643, tf_esp = -1077936852, tf_ss = 47}) at ../../i386/i386/trap.c:1155 #14 0xc022fae5 in Xint0x80_syscall () #15 0x8048135 in ?? () (kgdb) -- walter pelissero http://www.pelissero.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Aug 20 4:30:30 2001 Delivered-To: freebsd-net@freebsd.org Received: from Awfulhak.org (gw.Awfulhak.org [217.204.245.18]) by hub.freebsd.org (Postfix) with ESMTP id CD95937B416 for ; Mon, 20 Aug 2001 04:30:15 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [fec0::1:12]) by Awfulhak.org (8.11.5/8.11.5) with ESMTP id f7KBU4v10810; Mon, 20 Aug 2001 12:30:04 +0100 (BST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.11.4/8.11.4) with ESMTP id f7KBTuU80473; Mon, 20 Aug 2001 12:29:56 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200108201129.f7KBTuU80473@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: Len Conrad Cc: freebsd-net@FreeBSD.ORG, brian@freebsd-services.com Subject: Re: taking ppp down and up In-Reply-To: Message from Len Conrad of "Mon, 20 Aug 2001 13:08:53 +0200." <5.1.0.14.0.20010820124519.0404bf48@mail.Go2France.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Date: Mon, 20 Aug 2001 12:29:56 +0100 From: Brian Somers Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi, WRT killing ppp, the best way is: killall ppp; killall -2 ppp The first tells ppp to exit cleanly and starts it trying to negotiate = a shutdown with the other end. The second kill tells ppp to just = drop all existing connections. WRT the PPPoE lockup problem, I'd love to get to the bottom of this = (I can't reproduce it here). If anybody can give me an account on a = machine that locks up like this, I'd gladly have a crack at trying to = solve the problem. Cheers. > We=B4re very happy with PPPoE into our cable modem > = > =B4cept the whole link isn=B4t reliable :)))) > = > ... for at least the reason that France Telecom (French-govt-protected = > monopoly), God bless 'em, cripples their ADSL service by inserting 3 mi= nute = > blackouts, at the next hop at end their end of the ADSL, link throughou= t = > the day, (ping to next hop dead) to protect their exorbitantly priced = > leased-line service. > = > Usually after these blackouts, our FreeBSD PPPoE router just waits unti= l = > FT=B4s box responds again and all is. We cast yet-another curse on FT,= = > re-start our ssh and pcAnywhere sessions, truck along. > = > The other pb is that sometimes, PPPoE doesn=B4t come back, and we wonde= r = > whether maybe, in these cases, it=B4s really PPPoE halting, as I=B4ve s= een = > others report in these lists. It=B4s the PPP from 4.3-Release .iso. > = > We of course need better reliability in the face of whatever PPP halts,= so = > we=B4re trying to come up with a script we could run to take down the l= ink = > (tun0, ppp) and then bring it up, and not having much success. We als= o = > run ipf and ipnat, so here=B4s what our script looks like: > = > ipf -D > = > killall ppp > = > kill `cat /var/run/ipmon.pid` > = > kill `cat /var/run/tun0.pid` > = > /usr/sbin/ppp -quiet -ddial -nat -unit0 meidsl > = > ipf -E > ipf -Fa -f /etc/ipf-stats.rules > ipnat -CF -f /etc/ipnat.rules > /usr/sbin/ipmon -Dna /var/log/ipmon/iplog > ~ > Running the above with the line up, we see this on the screen: > = > warning: /dev/tun0: Device busy > 0 entries flushed from NAT table > 0 entries flushed from NAT list > Aug 20 12:51:13 gw0 /kernel: IP Filter: v3.4.19 unloaded > gw0# Aug 20 12:51:13 gw0 /kernel: IP Filter: v3.4.19 unloaded > Aug 20 12:51:13 gw0 /kernel: IP Filter: v3.4.19 initialized. Default =3D= = > pass all, Logging =3D enabled > Aug 20 12:51:13 gw0 /kernel: IP Filter: v3.4.19 initialized. Default =3D= = > pass all, Logging =3D enabled > Aug 20 12:51:13 gw0 ppp[1002]: Warning: /dev/tun0: Device busy > = > but the line doesn=B4t come up, until we run the same ppprest.sh script= a = > second time and get this on the screen: > = > No matching processes were found > cat: /var/run/tun0.pid: No such file or directory > cat: /var/run/tun0.pid: No such file or directory > usage: kill [-s signal_name] pid ... > kill -l [exit_status] > kill -signal_name pid ... > kill -signal_number pid ... > Aug 20 12:52:23 gw0 /kernel: IP Filter: v3.4.19 unloaded > Aug 20 12:52:23 gw0 /kernel: IP Filter: v3.4.19 unloaded > 0 entries flushed from NAT table > 0 entries flushed from NAT list > gw0# Aug 20 12:52:23 gw0 /kernel: IP Filter: v3.4.19 initialized. Defa= ult = > =3D pass all, Logging =3D enabled > Aug 20 12:52:23 gw0 /kernel: IP Filter: v3.4.19 initialized. Default =3D= = > pass all, Logging =3D enabled > = > and the PPP link comes up again. > = > We=B4ve tried a lot of different sequences for the script, but nothing = works = > ON THE FIRST SCRIPT RUN, so we think we=B4re got wrong or missing comma= nds. > = > Any suggestions? > = > Also, anybody have any ideas for a probe that will distinguish between = when = > the FT blackout is the pb (ie, don=B4t run PPP restart script) vs when = PPPoE = > is hung? > = > Len > = > = > http://MenAndMice.com/DNS-training > http://BIND8NT.MEIway.com : ISC BIND 8.2.4 for NT4 & W2K > http://IMGate.MEIway.com : Build free, hi-perf, anti-abuse mail gatewa= ys -- = Brian http://www.freebsd-services.com/ Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Aug 20 4:56:18 2001 Delivered-To: freebsd-net@freebsd.org Received: from mgw1.MEIway.com (mgw1.meiway.com [212.73.210.75]) by hub.freebsd.org (Postfix) with ESMTP id 6B3C637B416 for ; Mon, 20 Aug 2001 04:56:15 -0700 (PDT) (envelope-from LConrad@Go2France.com) Received: from mail.Go2France.com (ms1.meiway.com [212.73.210.73]) by mgw1.MEIway.com (Postfix Relay Hub) with ESMTP id C79BF16B36 for ; Mon, 20 Aug 2001 13:56:11 +0200 (CEST) Received: from IBM-HIRXKN66F0W.Go2France.com [195.115.185.184] by mail.Go2France.com with ESMTP (SMTPD32-6.06) id AD42160901D8; Mon, 20 Aug 2001 14:06:26 +0200 Message-Id: <5.1.0.14.0.20010820135141.03ec8de0@mail.Go2France.com> X-Sender: LConrad@Go2France.com@mail.Go2France.com X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Mon, 20 Aug 2001 13:56:46 +0200 To: freebsd-net@freebsd.org From: Len Conrad Subject: Re: taking ppp down and up In-Reply-To: <200108201129.f7KBTuU80473@hak.lan.Awfulhak.org> References: <5.1.0.14.0.20010820124519.0404bf48@mail.Go2France.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1"; format=flowed Content-Transfer-Encoding: 8bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >WRT killing ppp, the best way is: > > killall ppp; killall -2 ppp and the best .... works! Our script now succeeds in bringing up PPP again. Thanks >WRT the PPPoE lockup problem, I'd love to get to the bottom of this >(I can't reproduce it here). If anybody can give me an account on a >machine that locks up like this, I'd gladly have a crack at trying to >solve the problem. we are not sure we have the ppp lockup, but we certainly have the "FT lockout". We are willing to give you an ssh account, but when we´re down ..... :)) Do you have any ideas WRT, from POV of the PPP machine, how to distinguish between local ppp lockup vs ppp ok but remote nexthop dead? Len http://MenAndMice.com/DNS-training http://BIND8NT.MEIway.com : ISC BIND 8.2.4 for NT4 & W2K http://IMGate.MEIway.com : Build free, hi-perf, anti-abuse mail gateways To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Aug 20 5:15:10 2001 Delivered-To: freebsd-net@freebsd.org Received: from Awfulhak.org (gw.Awfulhak.org [217.204.245.18]) by hub.freebsd.org (Postfix) with ESMTP id C905A37B41B for ; Mon, 20 Aug 2001 05:15:04 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [fec0::1:12]) by Awfulhak.org (8.11.5/8.11.5) with ESMTP id f7KCErv11033; Mon, 20 Aug 2001 13:14:53 +0100 (BST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.11.4/8.11.4) with ESMTP id f7KCEjU81471; Mon, 20 Aug 2001 13:14:45 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200108201214.f7KCEjU81471@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: Len Conrad Cc: freebsd-net@FreeBSD.ORG, brian@freebsd-services.com Subject: Re: taking ppp down and up In-Reply-To: Message from Len Conrad of "Mon, 20 Aug 2001 13:56:46 +0200." <5.1.0.14.0.20010820135141.03ec8de0@mail.Go2France.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Date: Mon, 20 Aug 2001 13:14:45 +0100 From: Brian Somers Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > >WRT the PPPoE lockup problem, I'd love to get to the bottom of this > >(I can't reproduce it here). If anybody can give me an account on a > >machine that locks up like this, I'd gladly have a crack at trying to > >solve the problem. > = > we are not sure we have the ppp lockup, but we certainly have the "FT l= ockout". > = > We are willing to give you an ssh account, but when we=B4re down ..... = :)) > = > Do you have any ideas WRT, from POV of the PPP machine, how to distingu= ish = > between local ppp lockup vs ppp ok but remote nexthop dead? I think monitoring the network for PPPoE traffic should say whether = or not the local end is dead (no traffic =3D=3D local death). ``tcpdump = -i iface -l not ip'' should do it. Assuming there's no traffic, it may be necessary to install a modified = netgraph module - one that logs when it's setting up and triggering = timeouts. I did this some time ago here, but could never get = anything to lock up :( I've been told that ``killall -11 ppp'' or = attaching to ppp with gdb just shows ppp in select() (as expected), = but it may be worth confirming this too. I can only guess that the problem is due to netgraph mis-processing = some rogue data from the other side (data I can't reproduce here 'cos = I'm using netgraph). To this end, it may even be worth running = tcpdump permanently on the link (with -x) so that we can get a look = at the dodgy data. > Len > = > = > http://MenAndMice.com/DNS-training > http://BIND8NT.MEIway.com : ISC BIND 8.2.4 for NT4 & W2K > http://IMGate.MEIway.com : Build free, hi-perf, anti-abuse mail gatewa= ys -- = Brian http://www.freebsd-services.com/ Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Aug 20 5:30:59 2001 Delivered-To: freebsd-net@freebsd.org Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id E561837B407; Mon, 20 Aug 2001 05:30:54 -0700 (PDT) (envelope-from jmz@FreeBSD.org) Received: (from jmz@localhost) by freefall.freebsd.org (8.11.4/8.11.4) id f7KCUBd44155; Mon, 20 Aug 2001 05:30:11 -0700 (PDT) (envelope-from jmz) Date: Mon, 20 Aug 2001 05:30:11 -0700 (PDT) Message-Id: <200108201230.f7KCUBd44155@freefall.freebsd.org> From: Jean-Marc Zucconi To: Len Conrad Cc: freebsd-net@FreeBSD.ORG Subject: Re: taking ppp down and up In-Reply-To: <5.1.0.14.0.20010820124519.0404bf48@mail.Go2France.com> References: <5.1.0.14.0.20010820124519.0404bf48@mail.Go2France.com> X-Mailer: Emacs 21.0.104.2 Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >>>>> Len Conrad writes: > We=B4re very happy with PPPoE into our cable modem > =B4cept the whole link isn=B4t reliable :)))) > ... for at least the reason that France Telecom (French-govt-protected= > monopoly), God bless 'em, cripples their ADSL service by inserting 3 m= inute > blackouts, at the next hop at end their end of the ADSL, link througho= ut > the day, (ping to next hop dead) to protect their exorbitantly priced > leased-line service. There is no 3 minute blackout. The session is just closed. Change lqrperiod if you want a shorter deconnexion. Jean-Marc -- Jean-Marc Zucconi -- PGP Key: finger jmz@FreeBSD.org [KeyID: 400B38E9] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Aug 20 5:42:57 2001 Delivered-To: freebsd-net@freebsd.org Received: from ringworld.nanolink.com (sentinel.office1.bg [217.75.135.254]) by hub.freebsd.org (Postfix) with SMTP id F00A537B62A for ; Mon, 20 Aug 2001 05:42:30 -0700 (PDT) (envelope-from roam@ringlet.net) Received: (qmail 1033 invoked by uid 1000); 20 Aug 2001 12:40:09 -0000 Date: Mon, 20 Aug 2001 15:40:09 +0300 From: Peter Pentchev To: "Walter C. Pelissero" Cc: hackers@freebsd.org, net@freebsd.org Subject: Re: 4.4-RC NFS panic Message-ID: <20010820154009.A991@ringworld.oblivion.bg> Mail-Followup-To: "Walter C. Pelissero" , hackers@freebsd.org, net@freebsd.org References: <15232.62492.730149.447791@hyde.lpds.sublink.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <15232.62492.730149.447791@hyde.lpds.sublink.org>; from walter@pelissero.org on Mon, Aug 20, 2001 at 12:27:24PM +0100 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Mon, Aug 20, 2001 at 12:27:24PM +0100, Walter C. Pelissero wrote: > [ it seems my original article didn't get through ] > > I recently upgraded to 4.4-RC. > Now my Vaio panics when I use NFS volumes (as client). > The panic is reproducible with a: > > find /some/NFS/mount/point -type f -exec cat {} \; >/dev/null > > Sometime I got a "page fault", sometime a "lockmgr: locking against myself" > > Here is a kgdb session: [snip] > #7 0xc016dbfc in m_freem (m=0xc0738a00) at ../../kern/uipc_mbuf.c:618 > #8 0xc0b59652 in ?? () > #9 0xc0b66b92 in ?? () > #10 0xc0b3fe37 in ?? () > #11 0xc0b606de in ?? () > #12 0xc0b5f11b in ?? () > #13 0xc023b75d in syscall2 (frame={tf_fs = 47, tf_es = 47, tf_ds = 47, All those ??'s are the result of kgdb being unable to look inside a kernel module. Are you loading NFS as a module? What other modules are loaded at the time of the panic? Could you try compiling them statically into the kernel, see if the panic still happens, but with more debugging information? G'luck, Peter -- If this sentence didn't exist, somebody would have invented it. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Aug 20 5:52:52 2001 Delivered-To: freebsd-net@freebsd.org Received: from mgw1.MEIway.com (mgw1.meiway.com [212.73.210.75]) by hub.freebsd.org (Postfix) with ESMTP id EB32537B409 for ; Mon, 20 Aug 2001 05:52:49 -0700 (PDT) (envelope-from LConrad@Go2France.com) Received: from mail.Go2France.com (ms1.meiway.com [212.73.210.73]) by mgw1.MEIway.com (Postfix Relay Hub) with ESMTP id 78B6416B30 for ; Mon, 20 Aug 2001 14:52:06 +0200 (CEST) Received: from IBM-HIRXKN66F0W.Go2France.com [195.115.185.184] by mail.Go2France.com with ESMTP (SMTPD32-6.06) id AA5CF4E01EA; Mon, 20 Aug 2001 15:02:20 +0200 Message-Id: <5.1.0.14.0.20010820144540.032e0da0@mail.Go2France.com> X-Sender: LConrad@Go2France.com@mail.Go2France.com X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Mon, 20 Aug 2001 14:52:30 +0200 To: freebsd-net@freebsd.org From: Len Conrad Subject: Re: taking ppp down and up In-Reply-To: <200108201230.f7KCUBd44155@freefall.freebsd.org> References: <5.1.0.14.0.20010820124519.0404bf48@mail.Go2France.com> <5.1.0.14.0.20010820124519.0404bf48@mail.Go2France.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1"; format=flowed Content-Transfer-Encoding: 8bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > > ... for at least the reason that France Telecom (French-govt-protected > > monopoly), God bless 'em, cripples their ADSL service by inserting 3 > minute > > blackouts, at the next hop at end their end of the ADSL, link throughout > > the day, (ping to next hop dead) to protect their exorbitantly priced > > leased-line service. > >There is no 3 minute blackout. The session is just closed. Change >lqrperiod if you want a shorter deconnexion. Merci bcp, so that´s where from the repeatable 6 x 30 seconds comes!! thanks Do you know what causes these sessions to close? Len http://MenAndMice.com/DNS-training http://BIND8NT.MEIway.com : ISC BIND 8.2.4 for NT4 & W2K http://IMGate.MEIway.com : Build free, hi-perf, anti-abuse mail gateways To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Aug 20 6:58:22 2001 Delivered-To: freebsd-net@freebsd.org Received: from mgw1.MEIway.com (mgw1.meiway.com [212.73.210.75]) by hub.freebsd.org (Postfix) with ESMTP id B6D2E37B41E for ; Mon, 20 Aug 2001 06:58:19 -0700 (PDT) (envelope-from LConrad@Go2France.com) Received: from mail.Go2France.com (ms1.meiway.com [212.73.210.73]) by mgw1.MEIway.com (Postfix Relay Hub) with ESMTP id 86B6716B37 for ; Mon, 20 Aug 2001 15:58:16 +0200 (CEST) Received: from IBM-HIRXKN66F0W.Go2France.com [195.115.185.184] by mail.Go2France.com with ESMTP (SMTPD32-6.06) id A9DFF3D01E2; Mon, 20 Aug 2001 16:08:31 +0200 Message-Id: <5.1.0.14.0.20010820155259.03e25e20@mail.Go2France.com> X-Sender: LConrad@Go2France.com@mail.Go2France.com X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Mon, 20 Aug 2001 15:58:55 +0200 To: freebsd-net@freebsd.org From: Len Conrad Subject: Re: taking ppp down and up In-Reply-To: <5.1.0.14.0.20010820144540.032e0da0@mail.Go2France.com> References: <200108201230.f7KCUBd44155@freefall.freebsd.org> <5.1.0.14.0.20010820124519.0404bf48@mail.Go2France.com> <5.1.0.14.0.20010820124519.0404bf48@mail.Go2France.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1"; format=flowed Content-Transfer-Encoding: 8bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >>There is no 3 minute blackout. The session is just closed. Change >>lqrperiod if you want a shorter deconnexion. > >Merci bcp, so that´s where from the repeatable 6 x 30 seconds comes!! thanks but with ppp.conf having: enable lqr set lqr accept set lqrperiod 3 we get: Aug 20 15:51:11 gw0 ppp[1672]: Warning: 0: Invalid lqr period - min 2 Aug 20 15:51:11 gw0 ppp[1672]: Warning: set lqr: Failed 1 what is the syntax for "set lqrperiod" ? man ppp is clear but our syntax is not accepted. Len http://MenAndMice.com/DNS-training http://BIND8NT.MEIway.com : ISC BIND 8.2.4 for NT4 & W2K http://IMGate.MEIway.com : Build free, hi-perf, anti-abuse mail gateways To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Aug 20 7:26:13 2001 Delivered-To: freebsd-net@freebsd.org Received: from Awfulhak.org (gw.Awfulhak.org [217.204.245.18]) by hub.freebsd.org (Postfix) with ESMTP id AC94937B415 for ; Mon, 20 Aug 2001 07:26:04 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [fec0::1:12]) by Awfulhak.org (8.11.5/8.11.5) with ESMTP id f7KEPrv11903; Mon, 20 Aug 2001 15:25:53 +0100 (BST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.11.4/8.11.4) with ESMTP id f7KEPiU84756; Mon, 20 Aug 2001 15:25:44 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200108201425.f7KEPiU84756@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: Len Conrad Cc: freebsd-net@FreeBSD.ORG, brian@freebsd-services.com Subject: Re: taking ppp down and up In-Reply-To: Message from Len Conrad of "Mon, 20 Aug 2001 15:58:55 +0200." <5.1.0.14.0.20010820155259.03e25e20@mail.Go2France.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Date: Mon, 20 Aug 2001 15:25:44 +0100 From: Brian Somers Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > = > >>There is no 3 minute blackout. The session is just closed. Change > >>lqrperiod if you want a shorter deconnexion. > > > >Merci bcp, so that=B4s where from the repeatable 6 x 30 seconds comes!= ! thanks Of course your provider should be sending a PADT... perhaps their = end is crashing or something ? > but > with ppp.conf having: > = > enable lqr > set lqr accept > set lqrperiod 3 > = > we get: > = > Aug 20 15:51:11 gw0 ppp[1672]: Warning: 0: Invalid lqr period - min 2 > Aug 20 15:51:11 gw0 ppp[1672]: Warning: set lqr: Failed 1 > = > what is the syntax for "set lqrperiod" ? man ppp is clear but our syn= tax = > is not accepted. The middle line is the problem -- atoi("accept") =3D=3D 0. > Len > = > = > http://MenAndMice.com/DNS-training > http://BIND8NT.MEIway.com : ISC BIND 8.2.4 for NT4 & W2K > http://IMGate.MEIway.com : Build free, hi-perf, anti-abuse mail gatewa= ys -- = Brian http://www.freebsd-services.com/ Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Aug 20 10:35:21 2001 Delivered-To: freebsd-net@freebsd.org Received: from pelissero.org (dyn209-37.sftm-212-159.plus.net [212.159.37.209]) by hub.freebsd.org (Postfix) with ESMTP id E2A0937B40D; Mon, 20 Aug 2001 10:35:02 -0700 (PDT) (envelope-from wcp@pelissero.org) Received: (from wcp@localhost) by pelissero.org (8.11.5/8.9.3) id f7KHYwe02231; Mon, 20 Aug 2001 18:34:58 +0100 (BST) (envelope-from wcp) From: "Walter C. Pelissero" MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15233.19009.779227.903080@hyde.lpds.sublink.org> Date: Mon, 20 Aug 2001 18:34:57 +0100 To: hackers@freebsd.org, net@freebsd.org Subject: Re: 4.4-RC NFS panic In-Reply-To: <20010820154009.A991@ringworld.oblivion.bg> References: <15232.62492.730149.447791@hyde.lpds.sublink.org> <20010820154009.A991@ringworld.oblivion.bg> X-Mailer: VM 6.90 under 21.1 (patch 13) "Crater Lake" XEmacs Lucid Reply-To: walter@pelissero.org X-Attribution: WP Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org [ third time I retry to post this message on the mailing list ] Peter Pentchev writes: > On Mon, Aug 20, 2001 at 12:27:24PM +0100, Walter C. Pelissero wrote: > All those ??'s are the result of kgdb being unable to look inside > a kernel module. Are you loading NFS as a module? Yep. I recompiled a kernel with almost all modules linked in. I forgot some of them but I guess those don't hurt. Now kldstat says: Id Refs Address Size Name 1 4 0xc0100000 298698 kernel 2 1 0xc0399000 30e0 splash_bmp.ko 3 1 0xc039d000 5458 vesa.ko 4 1 0xc0b63000 19000 usb.ko The panic is still easily reproducible and therefore I've got some more details to show you: GNU gdb 4.18 Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-unknown-freebsd". Reading symbols from kernel.debug...done. IdlePTD 4009984 initial pcb at 311680 panicstr: page fault panic messages: --- Fatal trap 12: page fault while in kernel mode fault virtual address = 0x65746e69 fault code = supervisor read, page not present instruction pointer = 0x8:0xc028782e stack pointer = 0x10:0xc780bccc frame pointer = 0x10:0xc780bd08 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 179 (nfsiod) interrupt mask = none trap number = 12 panic: page fault syncing disks... 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 done Uptime: 3m35s dumping to dev #ad/0x30001, offset 272736 dump ata0: resetting devices .. done 127 126 125 124 123 122 121 120 119 118 117 116 115 114 113 112 111 110 109 108 107 106 105 104 103 102 101 100 99 98 97 96 95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 --- #0 dumpsys () at ../../kern/kern_shutdown.c:472 472 if (dumping++) { (kgdb) bt #0 dumpsys () at ../../kern/kern_shutdown.c:472 #1 0xc0159b17 in boot (howto=256) at ../../kern/kern_shutdown.c:312 #2 0xc0159ee4 in poweroff_wait (junk=0xc02cd40c, howto=-1070805201) at ../../kern/kern_shutdown.c:580 #3 0xc0289002 in trap_fatal (frame=0xc780bc8c, eva=1702129257) at ../../i386/i386/trap.c:956 #4 0xc0288cd5 in trap_pfault (frame=0xc780bc8c, usermode=0, eva=1702129257) at ../../i386/i386/trap.c:849 #5 0xc02888bf in trap (frame={tf_fs = 16, tf_es = -1019805680, tf_ds = -1062076400, tf_edi = -1003117116, tf_esi = 1702129257, tf_ebp = -947864312, tf_isp = -947864392, tf_ebx = 6716, tf_edx = -947864124, tf_ecx = 1679, tf_eax = 1589720923, tf_trapno = 12, tf_err = 0, tf_eip = -1071089618, tf_cs = 8, tf_eflags = 66066, tf_esp = 1397686380, tf_ss = 6716}) at ../../i386/i386/trap.c:448 #6 0xc028782e in generic_bcopy () #7 0xc01f994a in nfs_readrpc (vp=0xc78dc300, uiop=0xc780bdc4, cred=0xc0bc9d80) at ../../nfs/nfs_vnops.c:1118 #8 0xc01d3393 in nfs_doio (bp=0xc3373e60, cr=0xc0bc9d80, p=0x0) at ../../nfs/nfs_bio.c:1410 #9 0xc01f348e in nfssvc_iod (p=0xc77baf20) at ../../nfs/nfs_syscalls.c:970 #10 0xc01f1ed3 in nfssvc (p=0xc77baf20, uap=0xc780bf80) at ../../nfs/nfs_syscalls.c:166 #11 0xc02892ad in syscall2 (frame={tf_fs = 47, tf_es = 47, tf_ds = 47, tf_edi = -1077936680, tf_esi = 0, tf_ebp = -1077936776, tf_isp = -947863596, tf_ebx = 2, tf_edx = 1, tf_ecx = 19, tf_eax = 155, tf_trapno = 12, tf_err = 2, tf_eip = 134515664, tf_cs = 31, tf_eflags = 643, tf_esp = -1077936852, tf_ss = 47}) at ../../i386/i386/trap.c:1155 #12 0xc027d635 in Xint0x80_syscall () #13 0x8048135 in ?? () Side note. I experienced another panic not directly related to NFS. During a high resolution print of a big image (something around 30MB postscript file) on a remote host (the NFS server) I got a panic, which might suggest the problem (if related) is in a deeper level than NFS. The remote printing panic is not so easy to reproduce so I gave up on that front. A nicer remark. The NFS server is up and running with a 4.4-RC (the same as my Vaio) since Friday without a single problem. I'm currently using a 4.3-STABLE and I don't get a panic whatsoever, so I assume the hardware is still all right. -- walter pelissero http://www.pelissero.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Aug 20 11:23:33 2001 Delivered-To: freebsd-net@freebsd.org Received: from mail.wrs.com (unknown-1-11.windriver.com [147.11.1.11]) by hub.freebsd.org (Postfix) with ESMTP id 3A0A037B415; Mon, 20 Aug 2001 11:23:23 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@[147.11.46.201]) by mail.wrs.com (8.9.3/8.9.1) with ESMTP id LAA26908; Mon, 20 Aug 2001 11:23:14 -0700 (PDT) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <15233.19009.779227.903080@hyde.lpds.sublink.org> Date: Mon, 20 Aug 2001 11:23:21 -0700 (PDT) From: John Baldwin To: "Walter C. Pelissero" Subject: Re: 4.4-RC NFS panic Cc: net@FreeBSD.org, hackers@FreeBSD.org Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On 20-Aug-01 Walter C. Pelissero wrote: > [ third time I retry to post this message on the mailing list ] > > Peter Pentchev writes: > > On Mon, Aug 20, 2001 at 12:27:24PM +0100, Walter C. Pelissero wrote: > > All those ??'s are the result of kgdb being unable to look inside > > a kernel module. Are you loading NFS as a module? > > Yep. I recompiled a kernel with almost all modules linked in. I > forgot some of them but I guess those don't hurt. > Now kldstat says: > > Id Refs Address Size Name > 1 4 0xc0100000 298698 kernel > 2 1 0xc0399000 30e0 splash_bmp.ko > 3 1 0xc039d000 5458 vesa.ko > 4 1 0xc0b63000 19000 usb.ko > > The panic is still easily reproducible and therefore I've got some > more details to show you: > > GNU gdb 4.18 > Copyright 1998 Free Software Foundation, Inc. > GDB is free software, covered by the GNU General Public License, and you are > welcome to change it and/or distribute copies of it under certain conditions. > Type "show copying" to see the conditions. > There is absolutely no warranty for GDB. Type "show warranty" for details. > This GDB was configured as "i386-unknown-freebsd". > Reading symbols from kernel.debug...done. > IdlePTD 4009984 > initial pcb at 311680 > panicstr: page fault > panic messages: > --- > Fatal trap 12: page fault while in kernel mode > fault virtual address = 0x65746e69 "etni" Looks like a string has gotten spammed across a data structure or a weird pointer, etc. From the previous panic: > fault virtual address = 0x33693d55 "3i=U" That one looks more suspicious, but could still be part of a string of some sort. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Aug 20 11:46:44 2001 Delivered-To: freebsd-net@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id DDE7A37B409; Mon, 20 Aug 2001 11:46:38 -0700 (PDT) (envelope-from julian@elischer.org) Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id LAA38102; Mon, 20 Aug 2001 11:52:40 -0700 (PDT) Date: Mon, 20 Aug 2001 11:52:39 -0700 (PDT) From: Julian Elischer To: John Baldwin Cc: "Walter C. Pelissero" , net@FreeBSD.org, hackers@FreeBSD.org Subject: Re: 4.4-RC NFS panic In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org remember it's littel endian On Mon, 20 Aug 2001, John Baldwin wrote: > > fault virtual address = 0x65746e69 > "etni" "inet" > > Looks like a string has gotten spammed across a data structure or a weird > pointer, etc. > > From the previous panic: > > > fault virtual address = 0x33693d55 > "3i=U" > "U=i3" (as in U=i386_xxx;" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Aug 20 11:46:50 2001 Delivered-To: freebsd-net@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id 9941E37B40E; Mon, 20 Aug 2001 11:46:42 -0700 (PDT) (envelope-from julian@elischer.org) Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id LAA38108; Mon, 20 Aug 2001 11:53:42 -0700 (PDT) Date: Mon, 20 Aug 2001 11:53:42 -0700 (PDT) From: Julian Elischer To: John Baldwin Cc: "Walter C. Pelissero" , net@FreeBSD.org, hackers@FreeBSD.org Subject: Re: 4.4-RC NFS panic In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > "etni" oops I mean "inte" (as in "integer" > > Looks like a string has gotten spammed across a data structure or a weird > pointer, etc. > > From the previous panic: > > > fault virtual address = 0x33693d55 > "3i=U" > > That one looks more suspicious, but could still be part of a string of some > sort. > > -- > > John Baldwin -- http://www.FreeBSD.org/~jhb/ > PGP Key: http://www.baldwin.cx/~john/pgpkey.asc > "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Aug 20 11:51:35 2001 Delivered-To: freebsd-net@freebsd.org Received: from pelissero.org (dyn192-37.sftm-212-159.plus.net [212.159.37.192]) by hub.freebsd.org (Postfix) with ESMTP id C28F437B41D; Mon, 20 Aug 2001 11:51:25 -0700 (PDT) (envelope-from wcp@pelissero.org) Received: (from wcp@localhost) by pelissero.org (8.11.5/8.9.3) id f7KIpIs15182; Mon, 20 Aug 2001 19:51:18 +0100 (BST) (envelope-from wcp) From: "Walter C. Pelissero" MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15233.23589.587884.764408@hyde.lpds.sublink.org> Date: Mon, 20 Aug 2001 19:51:17 +0100 To: John Baldwin Cc: net@FreeBSD.org, hackers@FreeBSD.org Subject: Re: 4.4-RC NFS panic In-Reply-To: References: <15233.19009.779227.903080@hyde.lpds.sublink.org> X-Mailer: VM 6.90 under 21.1 (patch 13) "Crater Lake" XEmacs Lucid Reply-To: walter@pelissero.org X-Attribution: WP Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org John Baldwin writes: > > fault virtual address = 0x65746e69 > "etni" > > Looks like a string has gotten spammed across a data structure or a > weird pointer, etc. Whatever mess happend, I've got some news for you that should remove the NFS module from the list of possible causes. Currently I'm running an old 4.3-STABLE kernel and kldstat shows: Id Refs Address Size Name 1 6 0xc0000000 40000000 kernel 2 1 0xc0ae0000 d000 msdos.ko 3 1 0xc0b0f000 6000 procfs.ko 4 1 0xc0b18000 4000 kernfs.ko 5 1 0xc0b3b000 4d000 nfs.ko <--- ! 6 1 0xc0bae000 12000 linux.ko That is, since my /modules is new, I've loaded the brand new 4.4-RC's NFS module, and it works without a glitch (at least for now). This enforces my belief that there is something broken in some deeper layer of the network code (see the remote printing issue). The time stamp of the older kernel is -r-xr-xr-x 1 root wheel 2408052 Jul 29 15:19 /kernel.good It's a pretty long period (almost a month) but maybe is possible to track down the mods to the network code till now. -- walter pelissero http://www.pelissero.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Aug 20 11:58:26 2001 Delivered-To: freebsd-net@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 615C637B418; Mon, 20 Aug 2001 11:58:20 -0700 (PDT) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 20 Aug 2001 19:58:19 +0100 (BST) Date: Mon, 20 Aug 2001 19:58:18 +0100 From: David Malone To: "Walter C. Pelissero" Cc: John Baldwin , net@FreeBSD.org, hackers@FreeBSD.org Subject: Re: 4.4-RC NFS panic Message-ID: <20010820195818.A68554@walton.maths.tcd.ie> References: <15233.19009.779227.903080@hyde.lpds.sublink.org> <15233.23589.587884.764408@hyde.lpds.sublink.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <15233.23589.587884.764408@hyde.lpds.sublink.org>; from walter@pelissero.org on Mon, Aug 20, 2001 at 07:51:17PM +0100 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Mon, Aug 20, 2001 at 07:51:17PM +0100, Walter C. Pelissero wrote: > This enforces my belief that there is something broken in some deeper > layer of the network code (see the remote printing issue). Just out of curiosity, what sort of network card is your Vaio using? Someone else is seeing network related panics that might be related to freeing an mbuf that's in use, and it's possible this might be related. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Aug 20 13:22:45 2001 Delivered-To: freebsd-net@freebsd.org Received: from tara.freenix.org (keltia.freenix.org [62.4.20.87]) by hub.freebsd.org (Postfix) with ESMTP id 1597637B41A; Mon, 20 Aug 2001 13:22:40 -0700 (PDT) (envelope-from roberto@tara.freenix.org) Received: by tara.freenix.org (Postfix/TLS, from userid 101) id DE6AF208; Mon, 20 Aug 2001 22:22:38 +0200 (CEST) Date: Mon, 20 Aug 2001 22:22:38 +0200 From: Ollivier Robert To: net@FreeBSD.org, hackers@FreeBSD.org Subject: Re: 4.4-RC NFS panic Message-ID: <20010820222238.A84351@tara.freenix.org> Mail-Followup-To: net@FreeBSD.org, hackers@FreeBSD.org References: <15233.19009.779227.903080@hyde.lpds.sublink.org> <15233.23589.587884.764408@hyde.lpds.sublink.org> <20010820195818.A68554@walton.maths.tcd.ie> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010820195818.A68554@walton.maths.tcd.ie>; from dwmalone@maths.tcd.ie on Mon, Aug 20, 2001 at 07:58:18PM +0100 X-Operating-System: FreeBSD 5.0-CURRENT K6-3D/266 & 2x PPro/200 SMP Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org According to David Malone: > Just out of curiosity, what sort of network card is your Vaio using? > Someone else is seeing network related panics that might be related If this is a VAIO with built-in ethernet, then it is an fxp card. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 5.0-CURRENT #80: Sun Jun 4 22:44:19 CEST 2000 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Aug 20 15:16:23 2001 Delivered-To: freebsd-net@freebsd.org Received: from server.kibernet.net (8-158.ta.cable.kks.net [213.161.8.158]) by hub.freebsd.org (Postfix) with ESMTP id 389A537B401 for ; Mon, 20 Aug 2001 15:16:11 -0700 (PDT) (envelope-from maddave@suxx.eu.org) Received: from spider.suxx.eu.org (unknown [194.249.141.2]) by server.kibernet.net (Postfix) with ESMTP id 6F187243B0 for ; Tue, 21 Aug 2001 00:15:37 +0200 (CEST) Received: by spider.suxx.eu.org (Postfix, from userid 1000) id 7DB9717771; Mon, 20 Aug 2001 23:49:46 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by spider.suxx.eu.org (Postfix) with ESMTP id 1C96D32C67 for ; Mon, 20 Aug 2001 23:49:46 +0200 (CEST) Date: Mon, 20 Aug 2001 23:49:45 +0200 (CEST) From: David Delibasic To: Subject: Box crashing Message-ID: <20010820234411.R46882-100000@spider.suxx.eu.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hellow ... I have upgraded my freebsd machine to 4.4-RC one day ago...and i have a problem with gif interfaces... in kernel config file i have: pseudo-device gif 8 and i can't see any gif interfaces with `ifconfig -a` and `gifconfig -a`. When i try to load module if_gif it loads but when i try to unload it freebsd crashed... Help ! D. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Aug 20 15:46:31 2001 Delivered-To: freebsd-net@freebsd.org Received: from mail.newgold.net (aphex.newgold.net [209.42.222.44]) by hub.freebsd.org (Postfix) with SMTP id BEB9537B409 for ; Mon, 20 Aug 2001 15:46:27 -0700 (PDT) (envelope-from jmallett@mail.newgold.net) Received: (qmail 14064 invoked by uid 1000); 20 Aug 2001 22:46:25 -0000 Date: Mon, 20 Aug 2001 22:46:25 +0000 From: Joseph Mallett To: Julian Elischer Cc: John Baldwin , "Walter C. Pelissero" , net@FreeBSD.org, hackers@FreeBSD.org Subject: Re: 4.4-RC NFS panic Message-ID: <20010820224625.A14002@NewGold.NET> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.19i Organisation: New Gold Technology Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > > "etni" > > "inet" > Your string reversal function is buggy. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Aug 20 16:38:57 2001 Delivered-To: freebsd-net@freebsd.org Received: from pelissero.org (dyn90-32.sftm-212-159.plus.net [212.159.32.90]) by hub.freebsd.org (Postfix) with ESMTP id B469337B403; Mon, 20 Aug 2001 16:38:46 -0700 (PDT) (envelope-from wcp@pelissero.org) Received: (from wcp@localhost) by pelissero.org (8.11.5/8.9.3) id f7KNcWO00667; Tue, 21 Aug 2001 00:38:32 +0100 (BST) (envelope-from wcp) From: "Walter C. Pelissero" MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15233.40823.749512.643101@hyde.lpds.sublink.org> Date: Tue, 21 Aug 2001 00:38:31 +0100 To: David Malone Cc: John Baldwin , net@FreeBSD.org, hackers@FreeBSD.org Subject: Re: 4.4-RC NFS panic In-Reply-To: <20010820195818.A68554@walton.maths.tcd.ie> References: <15233.19009.779227.903080@hyde.lpds.sublink.org> <15233.23589.587884.764408@hyde.lpds.sublink.org> <20010820195818.A68554@walton.maths.tcd.ie> X-Mailer: VM 6.90 under 21.1 (patch 13) "Crater Lake" XEmacs Lucid Reply-To: walter@pelissero.org X-Attribution: WP Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org David Malone writes: > On Mon, Aug 20, 2001 at 07:51:17PM +0100, Walter C. Pelissero wrote: > > This enforces my belief that there is something broken in some deeper > > layer of the network code (see the remote printing issue). > > Just out of curiosity, what sort of network card is your Vaio using? > Someone else is seeing network related panics that might be related > to freeing an mbuf that's in use, and it's possible this might be > related. Mmmm, you might be right. I'm using a 3com 589, therefore I'm using the ep driver. Unfortunately I don't have a different PCMCIA network card at hand, but I can try to reverse the crash test with my server. Yes, the server is running exactly the same version (4.4-RC) but uses the de driver. So I did and, guess what, the find/cat test on my server over an NFS mounted directory from my Vaio ran without a problem. I've just done a further test. I've mounted a directory tree from Vaio to Vaio using localhost (lo driver) and the test has run smoothly. So chances would be good the bug is in the ep driver. Unfortunately... $ ls -l /sys/dev/ep total 70 -rw-r--r-- 1 root wheel 23554 Jul 17 2000 if_ep.c -rw-r--r-- 1 root wheel 6202 Jan 14 2000 if_ep_eisa.c -rw-r--r-- 1 root wheel 10046 Dec 16 2000 if_ep_isa.c -rw-r--r-- 1 root wheel 4584 Oct 27 1999 if_ep_mca.c -rw-r--r-- 1 root wheel 6950 Aug 9 2000 if_ep_pccard.c -rw-r--r-- 1 root wheel 13935 Jan 12 2000 if_epreg.h -rw-r--r-- 1 root wheel 2667 May 24 2000 if_epvar.h none of the modules belonging to the ep driver has been touched for a long time. Side note. Regarding a different problem I've mentioned in freebsd-hackers I've been told 4.4-RC has got problems with the PCCARD code. Whether that can influence the ep driver is beyond my knowledge. -- walter pelissero http://www.pelissero.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Aug 20 17: 3:15 2001 Delivered-To: freebsd-net@freebsd.org Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by hub.freebsd.org (Postfix) with ESMTP id AD6EF37B408 for ; Mon, 20 Aug 2001 17:03:10 -0700 (PDT) (envelope-from brdavis@odin.ac.hmc.edu) Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.11.0/8.11.0) id f7L02wD03420; Mon, 20 Aug 2001 17:02:58 -0700 Date: Mon, 20 Aug 2001 17:02:58 -0700 From: Brooks Davis To: David Delibasic Cc: freebsd-net@FreeBSD.ORG Subject: Re: Box crashing Message-ID: <20010820170258.A29133@Odin.AC.HMC.Edu> References: <20010820234411.R46882-100000@spider.suxx.eu.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="k+w/mQv8wyuph6w0" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010820234411.R46882-100000@spider.suxx.eu.org>; from maddave@suxx.eu.org on Mon, Aug 20, 2001 at 11:49:45PM +0200 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org --k+w/mQv8wyuph6w0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Aug 20, 2001 at 11:49:45PM +0200, David Delibasic wrote: > I have upgraded my freebsd machine to 4.4-RC one day ago...and i have a > problem with gif interfaces... >=20 > in kernel config file i have: > pseudo-device gif 8 >=20 > and i can't see any gif interfaces with `ifconfig -a` and `gifconfig -a`. > When i try to load module if_gif it loads but when i try to unload it > freebsd crashed... With regard to the missing interfaces, you need to read /usr/src/UPDATING or the release notes when you upgrade. You now create gif devices with: ifconfig gif<#> create A number after the psuedo-device entry has no effect for gif. As to crashing, I haven't seen that problem here. I'm updating a system for testing. -- 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 --k+w/mQv8wyuph6w0 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE7gaUxXY6L6fI4GtQRAn45AJ4tCkcwUcjpGXvf0BdH4R8VQpzFhwCff/1l rKMInAvvkLBXq0FP+f3jDhY= =PPY+ -----END PGP SIGNATURE----- --k+w/mQv8wyuph6w0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Aug 20 20: 9:57 2001 Delivered-To: freebsd-net@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 0CD4637B405; Mon, 20 Aug 2001 20:09:53 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.3/8.11.3) with ESMTP id f7L39oq37037; Mon, 20 Aug 2001 21:09:51 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.3/8.11.4) with ESMTP id f7L39oW55481; Mon, 20 Aug 2001 21:09:50 -0600 (MDT) (envelope-from imp@harmony.village.org) Message-Id: <200108210309.f7L39oW55481@harmony.village.org> To: walter@pelissero.org Subject: Re: 4.4-RC NFS panic Cc: David Malone , John Baldwin , net@FreeBSD.ORG, hackers@FreeBSD.ORG In-reply-to: Your message of "Tue, 21 Aug 2001 00:38:31 BST." <15233.40823.749512.643101@hyde.lpds.sublink.org> References: <15233.40823.749512.643101@hyde.lpds.sublink.org> <15233.19009.779227.903080@hyde.lpds.sublink.org> <15233.23589.587884.764408@hyde.lpds.sublink.org> <20010820195818.A68554@walton.maths.tcd.ie> Date: Mon, 20 Aug 2001 21:09:50 -0600 From: Warner Losh Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org In message <15233.40823.749512.643101@hyde.lpds.sublink.org> "Walter C. Pelissero" writes: : Mmmm, you might be right. I'm using a 3com 589, therefore I'm using : the ep driver. The ep driver has been a little flakey under heavy load (like NFS) for a while. : Side note. Regarding a different problem I've mentioned in : freebsd-hackers I've been told 4.4-RC has got problems with the PCCARD : code. Whether that can influence the ep driver is beyond my : knowledge. No. It is a works or doesn't kinda bug. If you are getting to the point of mounting with NFS, the network works. Unless you are seeing 1s ping times. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Aug 21 1:35:44 2001 Delivered-To: freebsd-net@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id A5FB637B40C; Tue, 21 Aug 2001 01:35:38 -0700 (PDT) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 21 Aug 2001 09:35:35 +0100 (BST) To: walter@pelissero.org Cc: John Baldwin , net@FreeBSD.org, hackers@FreeBSD.org, Andre Albsmeier , Warner Losh Subject: Re: 4.4-RC NFS panic In-reply-to: Your message of "Tue, 21 Aug 2001 00:38:31 BST." <15233.40823.749512.643101@hyde.lpds.sublink.org> X-Request-Do: Date: Tue, 21 Aug 2001 09:35:34 +0100 From: David Malone Message-ID: <200108210935.aa87782@salmon.maths.tcd.ie> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > I've just done a further test. I've mounted a directory tree from > Vaio to Vaio using localhost (lo driver) and the test has run > smoothly. So chances would be good the bug is in the ep driver. > Unfortunately... Andre Albsmeier, who's seeing various network problems, is using the xe driver (also PCMCIA I think), but the problems go away if he uses an Etherexpress card on the PCI bus of the same machine. It seems unlikely to be PCMCIA related ('cos it has nothing to do with the networking itself) it may just be triggered in machines with slower networking. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Aug 21 2: 2:49 2001 Delivered-To: freebsd-net@freebsd.org Received: from goliath.siemens.de (goliath.siemens.de [194.138.37.131]) by hub.freebsd.org (Postfix) with ESMTP id 3C5A437B40F; Tue, 21 Aug 2001 02:02:41 -0700 (PDT) (envelope-from andre.albsmeier@mchp.siemens.de) X-Envelope-Sender-Is: andre.albsmeier@mchp.siemens.de (at relayer goliath.siemens.de) Received: from mail1.siemens.de (mail1.siemens.de [139.23.33.14]) by goliath.siemens.de (8.11.1/8.11.1) with ESMTP id f7L924b20344; Tue, 21 Aug 2001 11:02:04 +0200 (MET DST) Received: from curry.mchp.siemens.de (curry.mchp.siemens.de [139.25.42.7]) by mail1.siemens.de (8.11.4/8.11.4) with ESMTP id f7L923708772; Tue, 21 Aug 2001 11:02:04 +0200 (MET DST) Received: (from localhost) by curry.mchp.siemens.de (8.11.3/8.11.3) id f7L923K51581; Date: Tue, 21 Aug 2001 11:02:03 +0200 From: Andre Albsmeier To: David Malone Cc: walter@pelissero.org, John Baldwin , net@FreeBSD.org, hackers@FreeBSD.org, Andre Albsmeier , Warner Losh Subject: Re: 4.4-RC NFS panic Message-ID: <20010821110203.A24141@curry.mchp.siemens.de> References: <15233.40823.749512.643101@hyde.lpds.sublink.org> <200108210935.aa87782@salmon.maths.tcd.ie> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200108210935.aa87782@salmon.maths.tcd.ie>; from dwmalone@maths.tcd.ie on Tue, Aug 21, 2001 at 09:35:34AM +0100 X-Echelon: BND CIA NSA Mossad KGB MI6 IRA detonator nuclear assault strike Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Tue, 21-Aug-2001 at 09:35:34 +0100, David Malone wrote: > > I've just done a further test. I've mounted a directory tree from > > Vaio to Vaio using localhost (lo driver) and the test has run > > smoothly. So chances would be good the bug is in the ep driver. > > Unfortunately... > > Andre Albsmeier, who's seeing various network problems, is using > the xe driver (also PCMCIA I think), but the problems go away if > he uses an Etherexpress card on the PCI bus of the same machine. As I wrote in my PR (#29845), my problems also happen with the 3C589 which uses the ep driver. So we can sum up to: 1.) Intel Etherexpress PRO/100 PCMCIA (xe driver) crashes 2.) 3Com 589D EtherLink III PCMCIA (ep driver) crashes 3.) Intel Etherexpress PRO/100+ PCI Card (fxp driver) works perfectly -Andre > > It seems unlikely to be PCMCIA related ('cos it has nothing to do > with the networking itself) it may just be triggered in machines > with slower networking. > > David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Aug 21 2: 7:40 2001 Delivered-To: freebsd-net@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id A910A37B401; Tue, 21 Aug 2001 02:07:35 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.3/8.11.3) with ESMTP id f7L97Xq38200; Tue, 21 Aug 2001 03:07:34 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.3/8.11.4) with ESMTP id f7L97XW64198; Tue, 21 Aug 2001 03:07:33 -0600 (MDT) (envelope-from imp@harmony.village.org) Message-Id: <200108210907.f7L97XW64198@harmony.village.org> To: Andre Albsmeier Subject: Re: 4.4-RC NFS panic Cc: David Malone , walter@pelissero.org, John Baldwin , net@FreeBSD.org, hackers@FreeBSD.org In-reply-to: Your message of "Tue, 21 Aug 2001 11:02:03 +0200." <20010821110203.A24141@curry.mchp.siemens.de> References: <20010821110203.A24141@curry.mchp.siemens.de> <15233.40823.749512.643101@hyde.lpds.sublink.org> <200108210935.aa87782@salmon.maths.tcd.ie> Date: Tue, 21 Aug 2001 03:07:33 -0600 From: Warner Losh Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org In message <20010821110203.A24141@curry.mchp.siemens.de> Andre Albsmeier writes: : As I wrote in my PR (#29845), my problems also happen with : the 3C589 which uses the ep driver. So we can sum up to: : : 1.) Intel Etherexpress PRO/100 PCMCIA (xe driver) crashes : 2.) 3Com 589D EtherLink III PCMCIA (ep driver) crashes : 3.) Intel Etherexpress PRO/100+ PCI Card (fxp driver) works perfectly Interesting. I'm not sure what to make of this. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Aug 21 2:25:25 2001 Delivered-To: freebsd-net@freebsd.org Received: from goliath.siemens.de (goliath.siemens.de [194.138.37.131]) by hub.freebsd.org (Postfix) with ESMTP id 705D737B412; Tue, 21 Aug 2001 02:25:19 -0700 (PDT) (envelope-from andre.albsmeier@mchp.siemens.de) X-Envelope-Sender-Is: andre.albsmeier@mchp.siemens.de (at relayer goliath.siemens.de) Received: from mail2.siemens.de (mail2.siemens.de [139.25.208.11]) by goliath.siemens.de (8.11.1/8.11.1) with ESMTP id f7L9P5b03494; Tue, 21 Aug 2001 11:25:05 +0200 (MET DST) Received: from curry.mchp.siemens.de (curry.mchp.siemens.de [139.25.42.7]) by mail2.siemens.de (8.11.4/8.11.4) with ESMTP id f7L9P4n10627; Tue, 21 Aug 2001 11:25:05 +0200 (MET DST) Received: (from localhost) by curry.mchp.siemens.de (8.11.3/8.11.3) id f7L9P4K51719; Date: Tue, 21 Aug 2001 11:25:04 +0200 From: Andre Albsmeier To: Warner Losh Cc: Andre Albsmeier , David Malone , walter@pelissero.org, John Baldwin , net@FreeBSD.org, hackers@FreeBSD.org Subject: Re: 4.4-RC NFS panic Message-ID: <20010821112504.A24304@curry.mchp.siemens.de> References: <20010821110203.A24141@curry.mchp.siemens.de> <15233.40823.749512.643101@hyde.lpds.sublink.org> <200108210935.aa87782@salmon.maths.tcd.ie> <20010821110203.A24141@curry.mchp.siemens.de> <200108210907.f7L97XW64198@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200108210907.f7L97XW64198@harmony.village.org>; from imp@harmony.village.org on Tue, Aug 21, 2001 at 03:07:33AM -0600 X-Echelon: BND CIA NSA Mossad KGB MI6 IRA detonator nuclear assault strike Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Tue, 21-Aug-2001 at 03:07:33 -0600, Warner Losh wrote: > In message <20010821110203.A24141@curry.mchp.siemens.de> Andre Albsmeier writes: > : As I wrote in my PR (#29845), my problems also happen with > : the 3C589 which uses the ep driver. So we can sum up to: > : > : 1.) Intel Etherexpress PRO/100 PCMCIA (xe driver) crashes > : 2.) 3Com 589D EtherLink III PCMCIA (ep driver) crashes > : 3.) Intel Etherexpress PRO/100+ PCI Card (fxp driver) works perfectly > > Interesting. I'm not sure what to make of this. So do I. Ian Dowse already sent me a program to inspect the mbufs in the crashdumps. I don't know a lot about mbufs but the output appears really hosed... I will try it again using another PCMICA card I just got... -Andre To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Aug 21 3:24:47 2001 Delivered-To: freebsd-net@freebsd.org Received: from david.siemens.de (david.siemens.de [192.35.17.14]) by hub.freebsd.org (Postfix) with ESMTP id 7CA6037B414; Tue, 21 Aug 2001 03:24:41 -0700 (PDT) (envelope-from andre.albsmeier@mchp.siemens.de) X-Envelope-Sender-Is: andre.albsmeier@mchp.siemens.de (at relayer david.siemens.de) Received: from mail3.siemens.de (mail3.siemens.de [139.25.208.14]) by david.siemens.de (8.11.0/8.11.0) with ESMTP id f7LAOVc19929; Tue, 21 Aug 2001 12:24:31 +0200 (MET DST) Received: from curry.mchp.siemens.de (curry.mchp.siemens.de [139.25.42.7]) by mail3.siemens.de (8.11.6/8.11.6) with ESMTP id f7LAOVw35731842; Tue, 21 Aug 2001 12:24:31 +0200 (MEST) Received: (from localhost) by curry.mchp.siemens.de (8.11.3/8.11.3) id f7LAOUK51987; Date: Tue, 21 Aug 2001 12:24:30 +0200 From: Andre Albsmeier To: Warner Losh Cc: Andre Albsmeier , David Malone , walter@pelissero.org, John Baldwin , net@FreeBSD.org, hackers@FreeBSD.org Subject: Re: 4.4-RC NFS panic Message-ID: <20010821122430.A25855@curry.mchp.siemens.de> References: <20010821110203.A24141@curry.mchp.siemens.de> <15233.40823.749512.643101@hyde.lpds.sublink.org> <200108210935.aa87782@salmon.maths.tcd.ie> <20010821110203.A24141@curry.mchp.siemens.de> <200108210907.f7L97XW64198@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200108210907.f7L97XW64198@harmony.village.org>; from imp@harmony.village.org on Tue, Aug 21, 2001 at 03:07:33AM -0600 X-Echelon: BND CIA NSA Mossad KGB MI6 IRA detonator nuclear assault strike Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Tue, 21-Aug-2001 at 03:07:33 -0600, Warner Losh wrote: > In message <20010821110203.A24141@curry.mchp.siemens.de> Andre Albsmeier writes: > : As I wrote in my PR (#29845), my problems also happen with > : the 3C589 which uses the ep driver. So we can sum up to: > : > : 1.) Intel Etherexpress PRO/100 PCMCIA (xe driver) crashes > : 2.) 3Com 589D EtherLink III PCMCIA (ep driver) crashes > : 3.) Intel Etherexpress PRO/100+ PCI Card (fxp driver) works perfectly > > Interesting. I'm not sure what to make of this. We can now add: 4.) D-Link DFE-650 PCMCIA (ed driver) freezes :-( Warner, I have seen your mails regarding pcic-44rc1.diff.1. My box has a TI PCI-1225 chip... I will try the patch... -Andre To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Aug 21 10:45:32 2001 Delivered-To: freebsd-net@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 9348C37B409; Tue, 21 Aug 2001 10:45:18 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.3/8.11.3) with ESMTP id f7LHjDq39709; Tue, 21 Aug 2001 11:45:13 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.3/8.11.4) with ESMTP id f7LHjCW66969; Tue, 21 Aug 2001 11:45:13 -0600 (MDT) (envelope-from imp@harmony.village.org) Message-Id: <200108211745.f7LHjCW66969@harmony.village.org> To: David Malone Subject: Re: 4.4-RC NFS panic Cc: walter@pelissero.org, John Baldwin , net@FreeBSD.ORG, hackers@FreeBSD.ORG, Andre Albsmeier In-reply-to: Your message of "Tue, 21 Aug 2001 09:35:34 BST." <200108210935.aa87782@salmon.maths.tcd.ie> References: <200108210935.aa87782@salmon.maths.tcd.ie> Date: Tue, 21 Aug 2001 11:45:12 -0600 From: Warner Losh Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org In message <200108210935.aa87782@salmon.maths.tcd.ie> David Malone writes: : Andre Albsmeier, who's seeing various network problems, is using : the xe driver (also PCMCIA I think), but the problems go away if : he uses an Etherexpress card on the PCI bus of the same machine. : : It seems unlikely to be PCMCIA related ('cos it has nothing to do : with the networking itself) it may just be triggered in machines : with slower networking. After talking with Ian Dowse, I think that we've hammered out what may cause this. Basically, the problem is code in net doing splnet() -> pcic_pci_intr -> netcard_intr -> network code. And we've interrupted the critical section, broken all kinds of invariants. Warner P.S. I think that with Ian's other interrupt changes, we can do the following w/o problems. This should fix the network problems, I think. Index: pcic_pci.c =================================================================== RCS file: /cache/ncvs/src/sys/pccard/pcic_pci.c,v retrieving revision 1.54.2.7 diff -u -r1.54.2.7 pcic_pci.c --- pcic_pci.c 2001/08/21 09:06:25 1.54.2.7 +++ pcic_pci.c 2001/08/21 17:18:06 @@ -515,15 +515,6 @@ * in the CD change. */ sp->getb(sp, PCIC_STAT_CHG); - - /* - * If we have a card in the slot with an interrupt handler, then - * call it. Note: This means that each card can have at most one - * interrupt handler for it. Since multifunction cards aren't - * supported, this shouldn't cause a problem in practice. - */ - if (sc->cd_present && sp->intr != NULL) - sp->intr(sp->argp); } /* @@ -784,36 +775,6 @@ return (0); } -static int -pcic_pci_setup_intr(device_t dev, device_t child, struct resource *irq, - int flags, driver_intr_t *intr, void *arg, void **cookiep) -{ - struct pcic_softc *sc = (struct pcic_softc *) device_get_softc(dev); - struct pcic_slot *sp = &sc->slots[0]; - - if (sp->intr) { - device_printf(dev, -"Interrupt already established, possible multiple attach bug.\n"); - return (EINVAL); - } - sp->intr = intr; - sp->argp = arg; - *cookiep = sc; - return (0); -} - -static int -pcic_pci_teardown_intr(device_t dev, device_t child, struct resource *irq, - void *cookie) -{ - struct pcic_softc *sc = (struct pcic_softc *) device_get_softc(dev); - struct pcic_slot *sp = &sc->slots[0]; - - sp->intr = NULL; - sp->argp = NULL; - return (0); -} - static device_method_t pcic_pci_methods[] = { /* Device interface */ DEVMETHOD(device_probe, pcic_pci_probe), @@ -829,8 +790,8 @@ DEVMETHOD(bus_release_resource, bus_generic_release_resource), DEVMETHOD(bus_activate_resource, pcic_activate_resource), DEVMETHOD(bus_deactivate_resource, pcic_deactivate_resource), - DEVMETHOD(bus_setup_intr, pcic_pci_setup_intr), - DEVMETHOD(bus_teardown_intr, pcic_pci_teardown_intr), + DEVMETHOD(bus_setup_intr, bus_generic_setup_intr), + DEVMETHOD(bus_teardown_intr, bus_generic_teardown_intr), /* Card interface */ DEVMETHOD(card_set_res_flags, pcic_set_res_flags), To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Aug 21 11:28:24 2001 Delivered-To: freebsd-net@freebsd.org Received: from thor.oit.pdx.edu (thor.oit.pdx.edu [131.252.120.40]) by hub.freebsd.org (Postfix) with ESMTP id 6515E37B40B; Tue, 21 Aug 2001 11:28:16 -0700 (PDT) (envelope-from singh@pdx.edu) Received: from freke.odin.pdx.edu (freke.odin.pdx.edu [131.252.120.43]) by thor.oit.pdx.edu (8.11.1/8.11.1) with ESMTP id f7LISFe01620; Tue, 21 Aug 2001 11:28:16 -0700 (PDT) Received: from localhost (singh@localhost) by freke.odin.pdx.edu (8.11.1/8.11.1) with ESMTP id f7LISFE13922; Tue, 21 Aug 2001 11:28:15 -0700 (PDT) X-Authentication-Warning: freke.odin.pdx.edu: singh owned process doing -bs Date: Tue, 21 Aug 2001 11:28:15 -0700 (PDT) From: Harkirat Singh X-X-Sender: To: Cc: Subject: SACK is available in FreeBSD Release 4.3 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hello All! In the past there were may queries about SACK and FACK support in FreeBSD, I was one of them who enquired about this in mailing group. We have implemented SACK+FACK in FreeBSD Release 4.3, it is freely available at www.cs.pdx.edu/~singh/software.html. I have tested it in 3-hop ad-hoc network and it is working fine. Please have a look and let us know for any further clarification / information. Regards, Harkirat Singh To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Aug 21 15:25:10 2001 Delivered-To: freebsd-net@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id 26A3337B406; Tue, 21 Aug 2001 15:24:59 -0700 (PDT) (envelope-from julian@elischer.org) Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id PAA44147; Tue, 21 Aug 2001 15:25:07 -0700 (PDT) Date: Tue, 21 Aug 2001 15:25:06 -0700 (PDT) From: Julian Elischer To: Harkirat Singh Cc: questions@FreeBSD.ORG, net@FreeBSD.ORG Subject: Re: SACK is available in FreeBSD Release 4.3 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Before it can be checked in it has to go to -current. If you could make a -currnt version it would greatly increas the chance that it can be integrated.. (it has to go in -current first, and then if people have tried it out, it can go into 4.x) On Tue, 21 Aug 2001, Harkirat Singh wrote: > > Hello All! > > In the past there were may queries about SACK and FACK support in > FreeBSD, I was one of them who enquired about this in mailing group. > > We have implemented SACK+FACK in FreeBSD Release 4.3, it is freely > available at www.cs.pdx.edu/~singh/software.html. > > I have tested it in 3-hop ad-hoc network and it is working fine. Please > have a look and let us know for any further clarification / information. > > > Regards, > > Harkirat Singh > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Aug 21 15:42:12 2001 Delivered-To: freebsd-net@freebsd.org Received: from thor.oit.pdx.edu (thor.oit.pdx.edu [131.252.120.40]) by hub.freebsd.org (Postfix) with ESMTP id AD88B37B405; Tue, 21 Aug 2001 15:42:05 -0700 (PDT) (envelope-from singh@pdx.edu) Received: from gere.odin.pdx.edu (gere.odin.pdx.edu [131.252.120.42]) by thor.oit.pdx.edu (8.11.1/8.11.1) with ESMTP id f7LMg1e11809; Tue, 21 Aug 2001 15:42:01 -0700 (PDT) Received: from localhost (singh@localhost) by gere.odin.pdx.edu (8.11.1/8.11.1) with ESMTP id f7LMg1102620; Tue, 21 Aug 2001 15:42:01 -0700 (PDT) X-Authentication-Warning: gere.odin.pdx.edu: singh owned process doing -bs Date: Tue, 21 Aug 2001 15:42:01 -0700 (PDT) From: Harkirat Singh X-X-Sender: To: Julian Elischer Cc: , Subject: Re: SACK is available in FreeBSD Release 4.3 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hello Julian, As a student while doing my project I surfed a lot for SACK patch in FreeBSd Release4.3. I felt that if someone like me in need of SACK src can use it and can save time in writing the code. That was the only purpose to send the previous mail in the newsgroup. I am not sure what do you mean by -current version. Regards, Harkirat Singh On Tue, 21 Aug 2001, Julian Elischer wrote: > Before it can be checked in it has to go to -current. > > If you could make a -currnt version it would greatly increas the chance > that it can be integrated.. > > (it has to go in -current first, and then if people have tried it out, it > can go into 4.x) > > > > > On Tue, 21 Aug 2001, Harkirat Singh wrote: > > > > > Hello All! > > > > In the past there were may queries about SACK and FACK support in > > FreeBSD, I was one of them who enquired about this in mailing group. > > > > We have implemented SACK+FACK in FreeBSD Release 4.3, it is freely > > available at www.cs.pdx.edu/~singh/software.html. > > > > I have tested it in 3-hop ad-hoc network and it is working fine. Please > > have a look and let us know for any further clarification / information. > > > > > > Regards, > > > > Harkirat Singh > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-net" in the body of the message > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Aug 21 15:50:19 2001 Delivered-To: freebsd-net@freebsd.org Received: from yoda.bmi.net (yoda.bmi.net [204.57.191.163]) by hub.freebsd.org (Postfix) with ESMTP id 7303437B403; Tue, 21 Aug 2001 15:50:04 -0700 (PDT) (envelope-from jmcoopr@webmail.bmi.net) Received: from johncoop.MSHOME (drumheller-router.bmi.net [206.63.201.3] (may be forged)) by yoda.bmi.net (Pro-8.9.3/Pro-8.9.3) with ESMTP id PAA29777; Tue, 21 Aug 2001 15:49:44 -0700 Received: from johncoop.MSHOME (localhost [127.0.0.1]) by johncoop.MSHOME (8.11.6/8.11.6) with ESMTP id f7LMo9u00625; Tue, 21 Aug 2001 15:50:09 -0700 (PDT) (envelope-from jmcoopr@webmail.bmi.net) Date: Tue, 21 Aug 2001 15:50:09 -0700 From: John Merryweather Cooper To: Harkirat Singh Cc: Julian Elischer , questions@FreeBSD.ORG, net@FreeBSD.ORG Subject: Re: SACK is available in FreeBSD Release 4.3 Message-ID: <20010821155009.E523@johncoop> References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit In-Reply-To: ; from singh@pdx.edu on Tue, Aug 21, 2001 at 15:42:01 -0700 X-Mailer: Balsa 1.1.7 Lines: 79 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On 2001.08.21 15:42 Harkirat Singh wrote: > > Hello Julian, > > As a student while doing my project I surfed a lot for SACK > patch > in FreeBSd Release4.3. I felt that if someone like me in need of SACK > src > can use it and can save time in writing the code. That was the only > purpose to send the previous mail in the newsgroup. > > I am not sure what do you mean by -current version. > A verions of your code that will compile/run on FreeBSD 5-CURRENT. It's the bleeding edge developer branch of the FreeBSD code. Someone correct me if I'm wrong, but I think you'll need to build a -CURRENT machine to do this. Then ensure/port the code to (hopefully) compile/run on both 4.3/4.4 and 5. jmc ============================= > Regards, > > Harkirat Singh > > > On Tue, 21 Aug 2001, Julian Elischer wrote: > > > Before it can be checked in it has to go to -current. > > > > If you could make a -currnt version it would greatly increas the > chance > > that it can be integrated.. > > > > (it has to go in -current first, and then if people have tried it > out, it > > can go into 4.x) > > > > > > > > > > On Tue, 21 Aug 2001, Harkirat Singh wrote: > > > > > > > > Hello All! > > > > > > In the past there were may queries about SACK and FACK > support in > > > FreeBSD, I was one of them who enquired about this in mailing > group. > > > > > > We have implemented SACK+FACK in FreeBSD Release 4.3, it is freely > > > available at www.cs.pdx.edu/~singh/software.html. > > > > > > I have tested it in 3-hop ad-hoc network and it is working fine. > Please > > > have a look and let us know for any further clarification / > information. > > > > > > > > > Regards, > > > > > > Harkirat Singh > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > with "unsubscribe freebsd-net" in the body of the message > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-net" in the body of the message > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Aug 21 15:57:39 2001 Delivered-To: freebsd-net@freebsd.org Received: from iguana.aciri.org (iguana.aciri.org [192.150.187.36]) by hub.freebsd.org (Postfix) with ESMTP id 9091C37B403; Tue, 21 Aug 2001 15:57:35 -0700 (PDT) (envelope-from rizzo@iguana.aciri.org) Received: (from rizzo@localhost) by iguana.aciri.org (8.11.3/8.11.1) id f7LMtIY36918; Tue, 21 Aug 2001 15:55:18 -0700 (PDT) (envelope-from rizzo) From: Luigi Rizzo Message-Id: <200108212255.f7LMtIY36918@iguana.aciri.org> Subject: Re: SACK is available in FreeBSD Release 4.3 In-Reply-To: <20010821155009.E523@johncoop> from John Merryweather Cooper at "Aug 21, 2001 3:50: 9 pm" To: jmcoopr@webmail.bmi.net (John Merryweather Cooper) Date: Tue, 21 Aug 2001 15:55:18 -0700 (PDT) Cc: singh@pdx.edu, julian@elischer.org, questions@FreeBSD.ORG, net@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > A verions of your code that will compile/run on FreeBSD 5-CURRENT. It's > the bleeding edge developer branch of the FreeBSD code. Someone correct > me if I'm wrong, but I think you'll need to build a -CURRENT machine to > do this. Then ensure/port the code to (hopefully) compile/run on both in fact, you can use the picobsd build script(*) to cross-build an image using -CURRENT sources on a -STABLE box. (*) i committed that to -current, but forgot to MFC at the time... cheers luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Aug 21 16: 9:11 2001 Delivered-To: freebsd-net@freebsd.org Received: from femail35.sdc1.sfba.home.com (femail35.sdc1.sfba.home.com [24.254.60.25]) by hub.freebsd.org (Postfix) with ESMTP id 05D4537B40B; Tue, 21 Aug 2001 16:08:51 -0700 (PDT) (envelope-from bmah@employees.org) Received: from intruder.bmah.org ([24.176.204.87]) by femail35.sdc1.sfba.home.com (InterMail vM.4.01.03.20 201-229-121-120-20010223) with ESMTP id <20010821230850.PPHY26922.femail35.sdc1.sfba.home.com@intruder.bmah.org>; Tue, 21 Aug 2001 16:08:50 -0700 Received: (from bmah@localhost) by intruder.bmah.org (8.11.5/8.11.3) id f7LN8ob14076; Tue, 21 Aug 2001 16:08:50 -0700 (PDT) (envelope-from bmah) Message-Id: <200108212308.f7LN8ob14076@intruder.bmah.org> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: John Merryweather Cooper Cc: Harkirat Singh , Julian Elischer , questions@FreeBSD.ORG, net@FreeBSD.ORG Subject: Re: SACK is available in FreeBSD Release 4.3 In-Reply-To: <20010821155009.E523@johncoop> References: <20010821155009.E523@johncoop> Comments: In-reply-to John Merryweather Cooper message dated "Tue, 21 Aug 2001 15:50:09 -0700." From: "Bruce A. Mah" Reply-To: bmah@FreeBSD.ORG X-Face: g~c`.{#4q0"(V*b#g[i~rXgm*w;:nMfz%_RZLma)UgGN&=j`5vXoU^@n5v4:OO)c["!w)nD/!!~e4Sj7LiT'6*wZ83454H""lb{CC%T37O!!'S$S&D}sem7I[A 2V%N&+ X-Image-Url: http://www.employees.org/~bmah/Images/bmah-cisco-small.gif X-Url: http://www.employees.org/~bmah/ Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==_Exmh_-940588932P"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Tue, 21 Aug 2001 16:08:50 -0700 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org --==_Exmh_-940588932P Content-Type: text/plain; charset=us-ascii If memory serves me right, John Merryweather Cooper wrote: > On 2001.08.21 15:42 Harkirat Singh wrote: > > > > Hello Julian, > > > > As a student while doing my project I surfed a lot for SACK > > patch > > in FreeBSd Release4.3. I felt that if someone like me in need of SACK > > src > > can use it and can save time in writing the code. That was the only > > purpose to send the previous mail in the newsgroup. > > > > I am not sure what do you mean by -current version. > > > > A verions of your code that will compile/run on FreeBSD 5-CURRENT. It's > the bleeding edge developer branch of the FreeBSD code. Someone correct > me if I'm wrong, but I think you'll need to build a -CURRENT machine to > do this. Then ensure/port the code to (hopefully) compile/run on both > 4.3/4.4 and 5. (...picking a random message to reply to...) A meta-point...Harkirat was nice enough to post these diffs publically. He never said anything about committing these to -CURRENT or 4-STABLE, but just put them up for people to look at if they were interested. I don't know if committing them is even something he wants to deal with, although hopefully that *is* the case. I'm worried that he's going to get scared away by all the things that he "has to do". No one else has said it yet, but thanks Harkirat for letting us know about your code. As you know, a number of people have asked about this functionality in the past. I haven't read the code closely yet, but I think it'd be great if this *is* a version that can go into -CURRENT, and eventually 4-STABLE. Peace, Bruce. --==_Exmh_-940588932P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: Exmh version 2.3.1+ 05/14/2001 iD8DBQE7guoB2MoxcVugUsMRAiYgAJ4wzt5qTH5f8TIWLWvK4IZPf+55ngCfXOYf fVOkuksxplMx10y3wQta3qA= =7W+j -----END PGP SIGNATURE----- --==_Exmh_-940588932P-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Aug 21 16:25:38 2001 Delivered-To: freebsd-net@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id 3B11237B40E; Tue, 21 Aug 2001 16:25:05 -0700 (PDT) (envelope-from julian@elischer.org) Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id QAA44443; Tue, 21 Aug 2001 16:34:03 -0700 (PDT) Date: Tue, 21 Aug 2001 16:34:03 -0700 (PDT) From: Julian Elischer To: "Bruce A. Mah" Cc: John Merryweather Cooper , Harkirat Singh , questions@FreeBSD.ORG, net@FreeBSD.ORG Subject: Re: SACK is available in FreeBSD Release 4.3 In-Reply-To: <200108212308.f7LN8ob14076@intruder.bmah.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org yes, I agree.. It is nice of you to make this available.. I'm sure that soemone will work on getting it into -current. (please don't delete it for a while. others may take some time to get to it, but at least now they have your email in teh archives to say where to get it...) On Tue, 21 Aug 2001, Bruce A. Mah wrote: > If memory serves me right, John Merryweather Cooper wrote: > > On 2001.08.21 15:42 Harkirat Singh wrote: > > > > > > Hello Julian, > > > > > > As a student while doing my project I surfed a lot for SACK > > > patch > > > in FreeBSd Release4.3. I felt that if someone like me in need of SACK > > > src > > > can use it and can save time in writing the code. That was the only > > > purpose to send the previous mail in the newsgroup. > > > > > > I am not sure what do you mean by -current version. > > > > > > > A verions of your code that will compile/run on FreeBSD 5-CURRENT. It's > > the bleeding edge developer branch of the FreeBSD code. Someone correct > > me if I'm wrong, but I think you'll need to build a -CURRENT machine to > > do this. Then ensure/port the code to (hopefully) compile/run on both > > 4.3/4.4 and 5. > > (...picking a random message to reply to...) > > A meta-point...Harkirat was nice enough to post these diffs publically. > He never said anything about committing these to -CURRENT or 4-STABLE, > but just put them up for people to look at if they were interested. I > don't know if committing them is even something he wants to deal with, > although hopefully that *is* the case. I'm worried that he's going to > get scared away by all the things that he "has to do". > > No one else has said it yet, but thanks Harkirat for letting us know > about your code. As you know, a number of people have asked about this > functionality in the past. I haven't read the code closely yet, but I > think it'd be great if this *is* a version that can go into -CURRENT, > and eventually 4-STABLE. > > Peace, > > Bruce. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Aug 21 16:25:39 2001 Delivered-To: freebsd-net@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id D2A9237B407; Tue, 21 Aug 2001 16:25:00 -0700 (PDT) (envelope-from julian@elischer.org) Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id QAA44441; Tue, 21 Aug 2001 16:31:36 -0700 (PDT) Date: Tue, 21 Aug 2001 16:31:35 -0700 (PDT) From: Julian Elischer To: Harkirat Singh Cc: questions@FreeBSD.ORG, net@FreeBSD.ORG Subject: Re: SACK is available in FreeBSD Release 4.3 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org -current freeBSD It is not important, but I just meant that it helps to get things integrated if they are provided as patches against 5.x instead of 4.x, but if it is hard for you, because you have no 5.x then it is not a probelm. someone will get it going.. Did you base it on previous work? On Tue, 21 Aug 2001, Harkirat Singh wrote: > > Hello Julian, > > As a student while doing my project I surfed a lot for SACK patch > in FreeBSd Release4.3. I felt that if someone like me in need of SACK src > can use it and can save time in writing the code. That was the only > purpose to send the previous mail in the newsgroup. > > I am not sure what do you mean by -current version. > > Regards, > > Harkirat Singh > > > On Tue, 21 Aug 2001, Julian Elischer wrote: > > > Before it can be checked in it has to go to -current. > > > > If you could make a -currnt version it would greatly increas the chance > > that it can be integrated.. > > > > (it has to go in -current first, and then if people have tried it out, it > > can go into 4.x) > > > > > > > > > > On Tue, 21 Aug 2001, Harkirat Singh wrote: > > > > > > > > Hello All! > > > > > > In the past there were may queries about SACK and FACK support in > > > FreeBSD, I was one of them who enquired about this in mailing group. > > > > > > We have implemented SACK+FACK in FreeBSD Release 4.3, it is freely > > > available at www.cs.pdx.edu/~singh/software.html. > > > > > > I have tested it in 3-hop ad-hoc network and it is working fine. Please > > > have a look and let us know for any further clarification / information. > > > > > > > > > Regards, > > > > > > Harkirat Singh > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > with "unsubscribe freebsd-net" in the body of the message > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-net" in the body of the message > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Aug 21 16:31:41 2001 Delivered-To: freebsd-net@freebsd.org Received: from technokratis.com (modemcable093.62-201-24.mtl.mc.videotron.ca [24.201.62.93]) by hub.freebsd.org (Postfix) with ESMTP id D0EE137B407; Tue, 21 Aug 2001 16:31:12 -0700 (PDT) (envelope-from bmilekic@technokratis.com) Received: (from bmilekic@localhost) by technokratis.com (8.11.4/8.11.3) id f7LNYD322338; Tue, 21 Aug 2001 19:34:13 -0400 (EDT) (envelope-from bmilekic) Date: Tue, 21 Aug 2001 19:34:13 -0400 From: Bosko Milekic To: alfred@freebsd.org, jlemon@freebsd.org, freebsd-net@freebsd.org Subject: [PATCH] mbtypes stats re-enabled in -CURRENT Message-ID: <20010821193413.A22031@technokratis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi, Several weeks ago, Jiangyi Liu sent me an early patch that re-enabled mbtypes statistics under the mbuf allocator in -CURRENT (I had disabled them temporarily while I worked on the allocator semantics itself). Just a couple of days ago, I cleaned up the patch, fixed it up, and rolled a new diff applying to most recent CURRENT. This patch re-enables mbtypes statistics under CURRENT: http://people.freebsd.org/~bmilekic/code/mb_alloc/mbtypes_stats.diff (17k) To CURRENT users with either SMP or UP : please test, you will need to: 1) cvsup fresh CURRENT sources 2) apply patch found at above URL 3) rebuild and reinstall kernel 4) reboot 5) cp /usr/src/sys/sys/mbuf.h /usr/include/sys/ 6) rebuild and reinstall both /usr/src/usr.bin/netstat and /usr/src/usr.bin/systat 7) go about your business, all network services working as usual 8) Check `netstat -m' and `systat -mbufs' outputs, more specifically look out for "Allocated mbuf types" output in the mbuf section of `netstat -m' output and look for allocated mbuf types to be displayed following a `systat -mbufs' 9) Email me (bmilekic@dsuper.net) and let me know how it went. I'd like to commit this within the next week. To those reviewing the patch, here's how it works: Mbuf "types" (e.g. MT_DATA, etc.) are counted with the help of `long' types. Each per-CPU mbuf statistics data structure (mbpstat) contains an array of longs called mb_mbtypes[]. The size of this array is, of course, MT_NTYPES, defined in sys/mbuf.h specifically for this purpose. The general mbuf statistics structure (called mbstat) contains a `short' m_numtypes member which, during mbuf_init(), is set to MT_NTYPES. The general container's mbpstat struct, like the per-CPU container's mbpstat structs, also contains this mb_mbtypes array. During mbuf allocation, (type) being an argument already passed to m_get() gets passed down to the mb_alloc allocation routine (mb_alloc()). For mbuf clusters, MT_NOTMBUF gets passed down (MT_FREE - no longer used - has been renamed to MT_NOTMBUF). The mb_alloc() code will then increment mb_mbtypes[(type)] if (type) is not MT_NOTMBUF. This manipulation is performed cosistently because it is in the per-CPU container and because it is done while the per-CPU container's (or the general container's) list is already held. During mbuf freeing, mbuf_being_freed->m_type is passed to mb_free() by m_free(). Again, in the case of mbuf clusters, MT_NOTMBUF is passed down instead. So, mb_free() will decrement mb_mbtypes[(type)] if (type) is not MT_NOTMBUF. This manipulation is handled under the given container's lock and is therefore guaranteed to be consistent. The reason this works is because each container has its own mbpstat per-CPU structure and can therefore ensure its consistency via its own container lock. The other reason this works is because mb_mbtypes[] is, in each case, an array of _longs_ and not _unsigned longs_. This allows for the counters to go below 0, as is expected in this situation. Consider, for example, that a thread A runs on CPU 0 and allocates an MT_DATA mbuf, then this happens: mbpstat[cpu_0]->mb_mbtypes[MT_DATA]++; If one considers that mbpstat[cpu_0]->mb_mbtypes[MT_DATA] was 0 prior to this manipulation, then its new value is 1. Now consider that another thread B on CPU 1 frees this same mbuf. Then this happens: mbpstat[cpu_1]->mb_mbtypes[MT_DATA]--; If one considers that mbpstat[cpu_1]->mb_mbtypes[MT_DATA] was 0 prior to this manipulation, then its new value is -1. So to get the "real" mbtypes[(type)] value, we do the following: mbtypes[(type)] = mbpstat[cpu_1]->mb_mbtypes[(type)] + ... + mbpstat[cpu_n]->mb_mbtypes[(type)]; We are guaranteed a number >= 0, because of the fact that all the mb_mbtypes[] are manipulated consistently, under some lock, and because we will never have a certain type _decremented_ before it's once _incremented_. In other words, we will never have something like "mb_mbtypes[(type)]--" occur unless there was already at least one "mb_mbtypes[(type)]++" that occured on at least one of the other containers. MCHTYPE() is implemented to call a function m_chtype() which changes the type accordingly and manipulates the mb_mbtypes[] of the general container after acquiring the general container's lock. This function is rarely used, and it should hopefully stay that way. Regards, -- Bosko Milekic bmilekic@technokratis.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Aug 21 18:10:33 2001 Delivered-To: freebsd-net@freebsd.org Received: from home.certto.com.br (home.certto.com.br [200.250.15.3]) by hub.freebsd.org (Postfix) with ESMTP id A3E2B37B408 for ; Tue, 21 Aug 2001 18:10:19 -0700 (PDT) (envelope-from lfenciso@certto.com.br) Received: from micro7 (micro2.certto.com.br [200.250.15.11]) by home.certto.com.br (8.11.3/8.11.3) with SMTP id f7M1CxM15639 for ; Tue, 21 Aug 2001 22:13:00 -0300 Content-Type: text/plain; charset="iso-8859-1" From: Luis Fernando Enciso To: net@freebsd.org Subject: 3c975 ATM Link works in FreeBSD? Date: Tue, 21 Aug 2001 22:09:15 -0300 X-Mailer: KMail [version 1.2] MIME-Version: 1.0 Message-Id: <01082122091501.00411@micro7> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org 3c975 ATM Link (3Com) works in FreeBSD 4.x? I not found any reference about him in /stand/help/HARDWARE.TXT. He works in FreeBSD or OpenBSD? Where I can find more information about this card? Thanks, Enciso ----------------------------------- Luis Fernando Enciso System Administrator To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Aug 21 22:42:48 2001 Delivered-To: freebsd-net@freebsd.org Received: from david.siemens.de (david.siemens.de [192.35.17.14]) by hub.freebsd.org (Postfix) with ESMTP id 058C337B412; Tue, 21 Aug 2001 22:42:02 -0700 (PDT) (envelope-from andre.albsmeier@mchp.siemens.de) X-Envelope-Sender-Is: andre.albsmeier@mchp.siemens.de (at relayer david.siemens.de) Received: from mail2.siemens.de (mail2.siemens.de [139.25.208.11]) by david.siemens.de (8.11.0/8.11.0) with ESMTP id f7M5flc23520; Wed, 22 Aug 2001 07:41:47 +0200 (MET DST) Received: from curry.mchp.siemens.de (curry.mchp.siemens.de [139.25.42.7]) by mail2.siemens.de (8.11.6/8.11.6) with ESMTP id f7M5flm01187; Wed, 22 Aug 2001 07:41:47 +0200 (MET DST) Received: (from localhost) by curry.mchp.siemens.de (8.11.3/8.11.3) id f7M5fkK57899; Date: Wed, 22 Aug 2001 07:41:46 +0200 From: Andre Albsmeier To: Warner Losh Cc: David Malone , walter@pelissero.org, John Baldwin , net@FreeBSD.ORG, hackers@FreeBSD.ORG, Andre Albsmeier Subject: Re: 4.4-RC NFS panic Message-ID: <20010822074146.A34016@curry.mchp.siemens.de> References: <200108210935.aa87782@salmon.maths.tcd.ie> <200108211745.f7LHjCW66969@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200108211745.f7LHjCW66969@harmony.village.org>; from imp@harmony.village.org on Tue, Aug 21, 2001 at 11:45:12AM -0600 X-Echelon: BND CIA NSA Mossad KGB MI6 IRA detonator nuclear assault strike Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Tue, 21-Aug-2001 at 11:45:12 -0600, Warner Losh wrote: > In message <200108210935.aa87782@salmon.maths.tcd.ie> David Malone writes: > : Andre Albsmeier, who's seeing various network problems, is using > : the xe driver (also PCMCIA I think), but the problems go away if > : he uses an Etherexpress card on the PCI bus of the same machine. > : > : It seems unlikely to be PCMCIA related ('cos it has nothing to do > : with the networking itself) it may just be triggered in machines > : with slower networking. > > After talking with Ian Dowse, I think that we've hammered out what may > cause this. Basically, the problem is > > code in net doing splnet() > > -> pcic_pci_intr -> netcard_intr -> network code. > > And we've interrupted the critical section, broken all kinds of > invariants. > > Warner > > P.S. I think that with Ian's other interrupt changes, we can do the > following w/o problems. This should fix the network problems, I > think. Runs perfectly for about 10 minutes now under full load. It didn't survive 10 seconds before :-) I still have the hangs on a warm reboot but this is a different story... Thanks a lot for the quick help! -Andre > > Index: pcic_pci.c > =================================================================== > RCS file: /cache/ncvs/src/sys/pccard/pcic_pci.c,v > retrieving revision 1.54.2.7 > diff -u -r1.54.2.7 pcic_pci.c > --- pcic_pci.c 2001/08/21 09:06:25 1.54.2.7 > +++ pcic_pci.c 2001/08/21 17:18:06 > @@ -515,15 +515,6 @@ > * in the CD change. > */ > sp->getb(sp, PCIC_STAT_CHG); > - > - /* > - * If we have a card in the slot with an interrupt handler, then > - * call it. Note: This means that each card can have at most one > - * interrupt handler for it. Since multifunction cards aren't > - * supported, this shouldn't cause a problem in practice. > - */ > - if (sc->cd_present && sp->intr != NULL) > - sp->intr(sp->argp); > } > > /* > @@ -784,36 +775,6 @@ > return (0); > } > > -static int > -pcic_pci_setup_intr(device_t dev, device_t child, struct resource *irq, > - int flags, driver_intr_t *intr, void *arg, void **cookiep) > -{ > - struct pcic_softc *sc = (struct pcic_softc *) device_get_softc(dev); > - struct pcic_slot *sp = &sc->slots[0]; > - > - if (sp->intr) { > - device_printf(dev, > -"Interrupt already established, possible multiple attach bug.\n"); > - return (EINVAL); > - } > - sp->intr = intr; > - sp->argp = arg; > - *cookiep = sc; > - return (0); > -} > - > -static int > -pcic_pci_teardown_intr(device_t dev, device_t child, struct resource *irq, > - void *cookie) > -{ > - struct pcic_softc *sc = (struct pcic_softc *) device_get_softc(dev); > - struct pcic_slot *sp = &sc->slots[0]; > - > - sp->intr = NULL; > - sp->argp = NULL; > - return (0); > -} > - > static device_method_t pcic_pci_methods[] = { > /* Device interface */ > DEVMETHOD(device_probe, pcic_pci_probe), > @@ -829,8 +790,8 @@ > DEVMETHOD(bus_release_resource, bus_generic_release_resource), > DEVMETHOD(bus_activate_resource, pcic_activate_resource), > DEVMETHOD(bus_deactivate_resource, pcic_deactivate_resource), > - DEVMETHOD(bus_setup_intr, pcic_pci_setup_intr), > - DEVMETHOD(bus_teardown_intr, pcic_pci_teardown_intr), > + DEVMETHOD(bus_setup_intr, bus_generic_setup_intr), > + DEVMETHOD(bus_teardown_intr, bus_generic_teardown_intr), > > /* Card interface */ > DEVMETHOD(card_set_res_flags, pcic_set_res_flags), -- BSD, from the people who brought you TCP/IP. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Aug 21 22:45: 2 2001 Delivered-To: freebsd-net@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 30F6037B436; Tue, 21 Aug 2001 22:44:44 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.3/8.11.3) with ESMTP id f7M5igq41737; Tue, 21 Aug 2001 23:44:42 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.3/8.11.4) with ESMTP id f7M5ifW72264; Tue, 21 Aug 2001 23:44:41 -0600 (MDT) (envelope-from imp@harmony.village.org) Message-Id: <200108220544.f7M5ifW72264@harmony.village.org> To: Andre Albsmeier Subject: Re: 4.4-RC NFS panic Cc: David Malone , walter@pelissero.org, John Baldwin , net@FreeBSD.ORG, hackers@FreeBSD.ORG In-reply-to: Your message of "Wed, 22 Aug 2001 07:41:46 +0200." <20010822074146.A34016@curry.mchp.siemens.de> References: <20010822074146.A34016@curry.mchp.siemens.de> <200108210935.aa87782@salmon.maths.tcd.ie> <200108211745.f7LHjCW66969@harmony.village.org> Date: Tue, 21 Aug 2001 23:44:40 -0600 From: Warner Losh Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org In message <20010822074146.A34016@curry.mchp.siemens.de> Andre Albsmeier writes: : I still have the hangs on a warm reboot but this is a different : story... Eh? what kind of hangs and when? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Aug 21 23: 1: 1 2001 Delivered-To: freebsd-net@freebsd.org Received: from goliath.siemens.de (goliath.siemens.de [194.138.37.131]) by hub.freebsd.org (Postfix) with ESMTP id 2D4BA37B408; Tue, 21 Aug 2001 22:59:56 -0700 (PDT) (envelope-from andre.albsmeier@mchp.siemens.de) X-Envelope-Sender-Is: andre.albsmeier@mchp.siemens.de (at relayer goliath.siemens.de) Received: from mail1.siemens.de (mail1.siemens.de [139.23.33.14]) by goliath.siemens.de (8.11.1/8.11.1) with ESMTP id f7M5xhb09664; Wed, 22 Aug 2001 07:59:43 +0200 (MET DST) Received: from curry.mchp.siemens.de (curry.mchp.siemens.de [139.25.42.7]) by mail1.siemens.de (8.11.6/8.11.6) with ESMTP id f7M5xhN17718; Wed, 22 Aug 2001 07:59:43 +0200 (MET DST) Received: (from localhost) by curry.mchp.siemens.de (8.11.3/8.11.3) id f7M5xhK57987; Date: Wed, 22 Aug 2001 07:59:42 +0200 From: Andre Albsmeier To: Warner Losh Cc: Andre Albsmeier , David Malone , walter@pelissero.org, John Baldwin , net@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: 4.4-RC NFS panic Message-ID: <20010822075942.A34091@curry.mchp.siemens.de> References: <20010822074146.A34016@curry.mchp.siemens.de> <200108210935.aa87782@salmon.maths.tcd.ie> <200108211745.f7LHjCW66969@harmony.village.org> <20010822074146.A34016@curry.mchp.siemens.de> <200108220544.f7M5ifW72264@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200108220544.f7M5ifW72264@harmony.village.org>; from imp@harmony.village.org on Tue, Aug 21, 2001 at 11:44:40PM -0600 X-Echelon: BND CIA NSA Mossad KGB MI6 IRA detonator nuclear assault strike Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Tue, 21-Aug-2001 at 23:44:40 -0600, Warner Losh wrote: > In message <20010822074146.A34016@curry.mchp.siemens.de> Andre Albsmeier writes: > : I still have the hangs on a warm reboot but this is a different > : story... > > Eh? what kind of hangs and when? Attached below is the dmesg... It hangs only when warm booting; after a power toggle everything is OK... Copyright (c) 1992-2001 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 4.4-RC #23: Wed Aug 22 07:21:34 CEST 2001 root@bali.ofw.tld:/src/obj-4/src/src-4/sys/schlappy Calibrating clock(s) ... TSC clock: 366660160 Hz, i8254 clock: 1193146 Hz Timecounter "i8254" frequency 1193146 Hz CPU: Pentium II/Pentium II Xeon/Celeron (366.66-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x66a Stepping = 10 Features=0x183f9ff real memory = 134152192 (131008K bytes) Physical memory chunk(s): 0x00001000 - 0x0009efff, 647168 bytes (158 pages) 0x00325000 - 0x07febfff, 130838528 bytes (31943 pages) avail memory = 127590400 (124600K bytes) bios32: Found BIOS32 Service Directory header at 0xc00f6230 bios32: Entry = 0xfd790 (c00fd790) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0x225 pnpbios: Found PnP BIOS data at 0xc00f6260 pnpbios: Entry = f0000:a34e Rev = 1.0 pnpbios: Event flag at 4b4 Other BIOS signatures found: ACPI: 000f61f0 Preloaded elf kernel "kernel" at 0xc02ff000. Pentium Pro MTRR support enabled pci_open(1): mode 1 addr port (0x0cf8) is 0x8000384c pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=71908086) Using $PIR table, 7 entries at 0xc00fdf50 apm0: on motherboard apm: found APM BIOS v1.2, connected at v1.2 npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard found-> vendor=0x8086, dev=0x7190, revid=0x03 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[10]: type 1, range 32, base f8000000, size 26 found-> vendor=0x8086, dev=0x7191, revid=0x03 class=06-04-00, hdrtype=0x01, mfdev=0 subordinatebus=1 secondarybus=1 found-> vendor=0x8086, dev=0x7110, revid=0x02 class=06-80-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 found-> vendor=0x8086, dev=0x7111, revid=0x01 class=01-01-80, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[20]: type 1, range 32, base 0000fcd0, size 4 found-> vendor=0x8086, dev=0x7112, revid=0x01 class=0c-03-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=d, irq=9 map[20]: type 1, range 32, base 0000fce0, size 5 found-> vendor=0x8086, dev=0x7113, revid=0x02 class=06-80-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[90]: type 1, range 32, base 00002180, size 4 found-> vendor=0x104c, dev=0xac1c, revid=0x01 class=06-07-00, hdrtype=0x02, mfdev=1 subordinatebus=0 secondarybus=0 intpin=a, irq=10 found-> vendor=0x104c, dev=0xac1c, revid=0x01 class=06-07-00, hdrtype=0x02, mfdev=1 subordinatebus=0 secondarybus=0 intpin=b, irq=11 pci0: on pcib0 pcib1: at device 1.0 on pci0 found-> vendor=0x10c8, dev=0x0005, revid=0x12 class=03-00-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 intpin=a, irq=10 map[10]: type 1, range 32, base f6000000, size 24 map[14]: type 1, range 32, base fe400000, size 22 map[18]: type 1, range 32, base feb00000, size 20 found-> vendor=0x10c8, dev=0x8005, revid=0x12 class=04-01-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 intpin=b, irq=11 map[10]: type 1, range 32, base f7800000, size 22 map[14]: type 1, range 32, base fea00000, size 20 pci1: on pcib1 pci1: (vendor=0x10c8, dev=0x0005) at 0.0 irq 10 chip1: mem 0xfea00000-0xfeafffff,0xf7800000-0xf7bfffff irq 11 at device 0.1 on pci1 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xfcd0-0xfcdf at device 7.1 on pci0 ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0xfcd0 ata0: mask=03 status0=50 status1=50 ata0: mask=03 ostat0=50 ostat2=50 ata0-slave: ATAPI probe a=14 b=eb ata0-master: ATAPI probe a=00 b=00 ata0: mask=03 status0=50 status1=00 ata0-master: ATA probe a=01 b=a5 ata0: devices=09 ata0: at 0x1f0 irq 14 on atapci0 ata1: iobase=0x0170 altiobase=0x0376 bmaddr=0xfcd8 ata1: mask=00 status0=ff status1=ff ata1: probe allocation failed pci0: (vendor=0x8086, dev=0x7112) at 7.2 irq 9 chip2: port 0x2180-0x218f at device 7.3 on pci0 pcic0: irq 10 at device 10.0 on pci0 pcic0: PCI Memory allocated: 0x44000000 pcic0: TI12XX PCI Config Reg: [ring enable][speaker enable][pwr save][CSC serial isa irq] pccard0: on pcic0 pcic1: irq 11 at device 10.1 on pci0 pcic1: PCI Memory allocated: 0x44001000 pcic1: TI12XX PCI Config Reg: [ring enable][speaker enable][pwr save][CSC serial isa irq] pccard1: on pcic1 ata-: ata0 exists, using next available unit number ata-: ata1 exists, using next available unit number pcic-: pcic0 exists, using next available unit number Trying Read_Port at 203 Trying Read_Port at 243 Trying Read_Port at 283 Trying Read_Port at 2c3 Trying Read_Port at 303 Trying Read_Port at 343 Trying Read_Port at 383 Trying Read_Port at 3c3 isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices orm0: