Re: Networking panic on 12 - found the cause
Thanks guys! That was fast On 12/02/2019 20:13, Kristof Provost wrote: On 2019-02-12 13:54:21 (-0600), Eric van Gyzen wrote: > I see the same behavior on head (and stable/12). > > (kgdb) f > #16 0x80ce5331 in ether_output_frame (ifp=0xf80003672800, > m=0xf8000c88b100) at /usr/src/sys/net/if_ethersubr.c:468 > 468 switch (pfil_run_hooks(V_link_pfil_head, , ifp, PFIL_OUT, > > 0x80ce5321 <+81>: mov %gs:0x0,%rax > 0x80ce532a <+90>: mov 0x500(%rax),%rax > => 0x80ce5331 <+97>: mov 0x28(%rax),%rax > > I think this is part of the V_link_pfil_head. I'm not very familiar > with vnet. Does this need a CURVNET_SET(), maybe in garp_rexmit()? > Yes. I posted a proposed patch in https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235699 Basically we get called through a timer, so there's no vnet context. It needs to be set, and then we can safely use any V_ variables. Regards, Kristof ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Networking panic on 12 - found the cause
On 2019-02-12 13:54:21 (-0600), Eric van Gyzen wrote: > I see the same behavior on head (and stable/12). > > (kgdb) f > #16 0x80ce5331 in ether_output_frame (ifp=0xf80003672800, > m=0xf8000c88b100) at /usr/src/sys/net/if_ethersubr.c:468 > 468 switch (pfil_run_hooks(V_link_pfil_head, , ifp, > PFIL_OUT, > >0x80ce5321 <+81>: mov%gs:0x0,%rax >0x80ce532a <+90>: mov0x500(%rax),%rax > => 0x80ce5331 <+97>: mov0x28(%rax),%rax > > I think this is part of the V_link_pfil_head. I'm not very familiar > with vnet. Does this need a CURVNET_SET(), maybe in garp_rexmit()? > Yes. I posted a proposed patch in https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235699 Basically we get called through a timer, so there's no vnet context. It needs to be set, and then we can safely use any V_ variables. Regards, Kristof ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Networking panic on 12 - found the cause
On 2/12/19 8:53 AM, Pete French wrote: > I found my panic. If I take everything out of rc.conf and loader.conf > and sysctl.conf and boot the system it works fine when I add an IP > address. If I add this one line to sysctl.conf > > net.link.ether.inet.garp_rexmit_count=2 > > Then I get a panic when I configure the interface: > > root@serpentine-passive:~ # ifconfig igb0 inet 10.32.10.4/16 up > > > Fatal trap 12: page fault while in kernel mode > cpuid = 0; apic id = 00 > fault virtual address = 0x28 > fault code = supervisor read data, page not present > instruction pointer = 0x20:0x80c987f1 > stack pointer = 0x28:0xfe4d5730 > frame pointer = 0x28:0xfe4d5750 > code segment = base 0x0, limit 0xf, type 0x1b > = DPL 0, pres 1, long 1, def32 0, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = 12 (swi4: clock (0)) > trap number = 12 > panic: page fault > cpuid = 0 > time = 1549981620 > KDB: stack backtrace: > #0 0x80bdfdc7 at kdb_backtrace+0x67 > #1 0x80b93fa3 at vpanic+0x1a3 > #2 0x80b93df3 at panic+0x43 > #3 0x8106a7bf at trap_fatal+0x35f > #4 0x8106a819 at trap_pfault+0x49 > #5 0x81069e3e at trap+0x29e > #6 0x810450c5 at calltrap+0x8 > #7 0x80c986f6 at ether_output+0x6b6 > #8 0x80d03354 at arprequest+0x4c4 > #9 0x80d0515c at garp_rexmit+0xbc > #10 0x80bade19 at softclock_call_cc+0x129 > #11 0x80bae2f9 at softclock+0x79 > #12 0x80b57c57 at ithread_loop+0x1a7 > #13 0x80b54da2 at fork_exit+0x82 > #14 0x810460be at fork_trampoline+0xe I see the same behavior on head (and stable/12). (kgdb) f #16 0x80ce5331 in ether_output_frame (ifp=0xf80003672800, m=0xf8000c88b100) at /usr/src/sys/net/if_ethersubr.c:468 468 switch (pfil_run_hooks(V_link_pfil_head, , ifp, PFIL_OUT, 0x80ce5321 <+81>:mov%gs:0x0,%rax 0x80ce532a <+90>:mov0x500(%rax),%rax => 0x80ce5331 <+97>:mov0x28(%rax),%rax I think this is part of the V_link_pfil_head. I'm not very familiar with vnet. Does this need a CURVNET_SET(), maybe in garp_rexmit()? Eric ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
RE: Networking
I can't run the -CURRENT kernel of the last several days and get any networking performance at all-but this is a desktop machine with a dc. Something's seriously wrong. Michael D. Harnois 2L, University of St. Thomas School of Law Minneapolis, Minnesota -Original Message- From: [EMAIL PROTECTED] [mailto:owner-freebsd-current;FreeBSD.ORG]On Behalf Of M. Warner Losh Sent: Monday, October 28, 2002 10:07 To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: Networking In message: [EMAIL PROTECTED] Niklas Johannes Saers [EMAIL PROTECTED] writes: : Hi all, : I'm wondering a bit on the state of the network-drivers in -CURRENT. : On my laptop running a fairly recent -CURRENT whenever I do a : ifconfig an0 inet 192.168.1.2 netmask 255.255.255.0 : my laptop will freeze until I unplug the card. My fxp0 works great on the : same computer. On another box I'm running, the 3Com 509B card that worked : great with -STABLE gets pings of about 9-10 seconds to a computer it's : hooked directly against. My an0 is a Cisco Aironet 350 card. : : These are probably known problems, but since they've been ongoing for : quite a while now, I thought I'd mention it. If they are not known : problems, I'd be happy to provide additional data. Hmmm, sounds like you have interrupt problems on the laptop. I'm sending this mail with an 'an' card right now and it works w/o a hitch. I can dhclient an address, or set one manually. It does take it about a second to configure the network in either case. I've used both the 340 and the 350 cards with this laptop in recent memory. As for your 509B card, I have no clue. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Networking
According to Niklas Johannes Saers: my laptop will freeze until I unplug the card. My fxp0 works great on the same computer. On another box I'm running, the 3Com 509B card that worked great with -STABLE gets pings of about 9-10 seconds to a computer it's hooked directly against. My an0 is a Cisco Aironet 350 card. Using NEWCARD or OLDCARD (aka pccardd) ? -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- [EMAIL PROTECTED] FreeBSD keltia.freenix.fr 5.0-CURRENT #80: Sun Jun 4 22:44:19 CEST 2000 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Networking
In message: [EMAIL PROTECTED] Niklas Johannes Saers [EMAIL PROTECTED] writes: : Hi all, : I'm wondering a bit on the state of the network-drivers in -CURRENT. : On my laptop running a fairly recent -CURRENT whenever I do a : ifconfig an0 inet 192.168.1.2 netmask 255.255.255.0 : my laptop will freeze until I unplug the card. My fxp0 works great on the : same computer. On another box I'm running, the 3Com 509B card that worked : great with -STABLE gets pings of about 9-10 seconds to a computer it's : hooked directly against. My an0 is a Cisco Aironet 350 card. : : These are probably known problems, but since they've been ongoing for : quite a while now, I thought I'd mention it. If they are not known : problems, I'd be happy to provide additional data. Hmmm, sounds like you have interrupt problems on the laptop. I'm sending this mail with an 'an' card right now and it works w/o a hitch. I can dhclient an address, or set one manually. It does take it about a second to configure the network in either case. I've used both the 340 and the 350 cards with this laptop in recent memory. As for your 509B card, I have no clue. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
