RE: Panic at vlan_input()
On 05-Oct-01 Jun Kuriyama wrote: I got another panic on my yesterday's -current. At this time, I made a kernel with device vlan. db t vlan_input(c0e73800,..) at vlan_input+0x42 ether_demux(c156b000,...) at ether_demux+0x12a ether_input(c156b000,...) at ether_input+0x5a wi_rxeof(c156000,...) at wi_rxeof+0x1b7 wi_intr(c156b000,...) at wi_intr+0xd6 pcic_pci_func_intr(c14fc200) at pcic_pci_func_intr+0x36 ithread_loop(c0ce0580,...) at ithread_loop+0x12a fork_exit(c01b6bac,...) at fork_exit+0x58 fork_trampoline() at fork_trampoline+0x8 Erm, what is the panic message? :) -- John Baldwin [EMAIL PROTECTED] -- 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 [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Panic at vlan_input()
I think this is a bug in the loadable VLAN code; there's a != which should be an ==, which results in packets with known tags being discarded and would result in packets with unknown tags causing a null pointer dereference. I'll commit a fix soon as soon as I've tested it more. Bill To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Panic at vlan_input()
At Fri, 5 Oct 2001 16:27:50 + (UTC), John Baldwin wrote: Erm, what is the panic message? :) Oops, sorry. Fatal trap 12: page fault while in kernel mode fault virtual address = 0x2a fault code = supervisor read, page not present instruction pointer = 0x8:0xc0207652 stack pointer = 0x10:0xca1fcc00 frame pointer = 0x10:0xca1fcc08 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 18 (irq9: pcic0 rl0 wi*) kernel: type 12 trap, code=0 Stopped at vlan_input+0x42:testb $0x1,0x2a(%edx) -- Jun Kuriyama [EMAIL PROTECTED] // IMG SRC, Inc. [EMAIL PROTECTED] // FreeBSD Project To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Panic at vlan_input()
At Sat, 6 Oct 2001 03:48:55 + (UTC), Bill Fenner wrote: I think this is a bug in the loadable VLAN code; there's a != which should be an ==, which results in packets with known tags being discarded and would result in packets with unknown tags causing a null pointer dereference. I'll commit a fix soon as soon as I've tested it more. Your commit to if_vlan.c seems to solve my problem. Thanks! -- Jun Kuriyama [EMAIL PROTECTED] // IMG SRC, Inc. [EMAIL PROTECTED] // FreeBSD Project To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Panic at vlan_input()
I got another panic on my yesterday's -current. At this time, I made a kernel with device vlan. db t vlan_input(c0e73800,..) at vlan_input+0x42 ether_demux(c156b000,...) at ether_demux+0x12a ether_input(c156b000,...) at ether_input+0x5a wi_rxeof(c156000,...) at wi_rxeof+0x1b7 wi_intr(c156b000,...) at wi_intr+0xd6 pcic_pci_func_intr(c14fc200) at pcic_pci_func_intr+0x36 ithread_loop(c0ce0580,...) at ithread_loop+0x12a fork_exit(c01b6bac,...) at fork_exit+0x58 fork_trampoline() at fork_trampoline+0x8 -- Jun Kuriyama [EMAIL PROTECTED] // IMG SRC, Inc. [EMAIL PROTECTED] // FreeBSD Project To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
