From owner-freebsd-stable Thu Dec 20 6:28:22 2001 Delivered-To: freebsd-stable@freebsd.org Received: from ns2.robhughes.com (12-237-138-77.client.attbi.com [12.237.138.77]) by hub.freebsd.org (Postfix) with SMTP id 9404737B417 for ; Thu, 20 Dec 2001 06:27:59 -0800 (PST) Received: (qmail 6396 invoked from network); 20 Dec 2001 14:27:58 -0000 Received: from hexch01.robhughes.com (192.168.1.3) by ns2.robhughes.com with SMTP; 20 Dec 2001 14:27:58 -0000 Subject: RE: 4.4-stable kernel panic with dummynet/bridging. Same rules work fine with 4.3-RC MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable Date: Thu, 20 Dec 2001 08:27:58 -0600 Message-ID: X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 X-MS-Has-Attach: Content-Class: urn:content-classes:message X-MS-TNEF-Correlator: Thread-Topic: 4.4-stable kernel panic with dummynet/bridging. Same rules work fine with 4.3-RC Thread-Index: AcGJSAtQ/suwCWlDR+SFGrTvBTGKXwAGe4vw From: "Robert D. Hughes" To: "Yusuf Goolamabbas" , , Cc: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hmmmm.... I thought it was just me, and I hadn't had a chance yet to go digging. I just enabled OPTIONS =3D BRIDGE in the kernel and I was = getting spontaneous reboots, but they pointed to NATD blowing up. Essentially the same error though. Removing OPTIONS =3D BRIDGE seems to have stopped the reboots. This is on the 4.4-STABLE tree and has been going on for at least a couple of weeks. Rob -----Original Message----- From: Yusuf Goolamabbas [mailto:yusufg@outblaze.com] Sent: Thursday, December 20, 2001 5:16 AM To: freebsd-net@freebsd.org; freebsd-stable@freebsd.org Cc: cez@pkl.net Subject: 4.4-stable kernel panic with dummynet/bridging. Same rules work fine with 4.3-RC Hi, Similar to what Ceri describes in this message http://docs.freebsd.org/cgi/getmsg.cgi?fetch=3D508422+0+current/freebsd-s= t able I have observed a 4.4-stable box panicing whenever bridging is turned on. This was cvsup'ed today morning. I have other boxes cvsup'ed at the same time except that they don't have dummynet/bridging configured in them and they work pretty well I replaced the box with an another 4.3-RC box and the same rules enclosed here work just fine ${fwcmd} add 100 pass all from any to any via lo0 ${fwcmd} add 200 deny all from any to 127.0.0.0/8 ${fwcmd} add 300 deny ip from 127.0.0.0/8 to any # If you're using 'options BRIDGE', uncomment the following line to pass ARP ${fwcmd} add 400 pass udp from 0.0.0.0 2054 to 0.0.0.0 ${fwcmd} add 500 pass all from to any in via fxp0 ${fwcmd} add 800 pipe 1 ip from to any in via fxp1 ${fwcmd} pipe 1 config mask src-ip 0x000000ff bw 512Kbit/s queue 50=20 Basically, fxp1 is connected to a switch and every machine on that switch is rate limited to 512Kbit/s individually I had configured the box with DDB but didn't have serial console so I transcribed everything at the db> prompt Fatal trap 12: page fault while in kernel mode fault virtual address =3D 0xa4 fault code =3D superviser read, page not present instruction pointer =3D 0x8:0xc0199164 strack pointer =3D 0x10:0xc9889b5c frame pointer =3D 0x10:0xc9889bac code segment =3D base 0x0, limit 0xfff type 0x1b =3D DPL 0, pres 1, def32 1, gran 1 processor eflags =3D interrupt enabled, resume, IOPL =3D 0 current process =3D 55 (sh) interrupt mask =3D kernel: type 12 trap, code =3D 0 stopped at in_arpinput+0x158; movl 0xa4(%eax,%eax) db> t in_arpinput(c077cb00,0,c989cac,c020d625,c020d5df) at in_arpinput+0x158 arpintr(c020dfdf,0,c02800,0,c7640010,c0e700,0) at arpintr+0x112 swi_net_next(c028c26c,c764f000,3,0,c835c440) at swi_net_next trap_pfault(c9889d20,0,c764f000,0,806c591) at trap_pfault+0xbe trap(10,c9880010,c01d0010,c764f000,80be591_ at trap+0x31f calltrap() at calltrap+0x11 trap 0xc : eip - 0xc02172cf , esp - 0xc9889d60, ebp - 0xc9889d88 copyinstr(c9889e68,0,0,c9889f80,c9889f80) at copyinstr+0x37 exec_elf_imagact(c9889e68,c835c440,3,c9889f80,c9889e68) at exec_elf_imagact+0xba execve(c835c440,c9889f80,80be5d4,0,80be590) at execve+0x26c syscall2(2f,2f,2f,80be590,0) at syscall2+0x1a5 Xinit0x80_syscall() + Xint-x80_syscall+0x25 Hope this helps Regards, Yusuf --=20 Yusuf Goolamabbas yusufg@outblaze.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message