i386/62789: PANIC on PPPoE Server

Meno Abels meno.abels at adviser.com
Fri Feb 13 07:00:39 PST 2004


>Number:         62789
>Category:       i386
>Synopsis:       PANIC on PPPoE Server
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-i386
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Feb 13 07:00:34 PST 2004
>Closed-Date:
>Last-Modified:
>Originator:     Meno Abels
>Release:        5.2.1-RC2
>Organization:
ADVISER  COM
>Environment:
FreeBSD neo.abels.adviser.com 5.2.1-RC2 FreeBSD 5.2.1-RC2 #5: Thu Feb 12 13:25:31 CET 2004     root at neo.abels.adviser.com:/usr/obj/usr/src/sys/GENERIC  i386
    
>Description:
   I tried today to setup an pppoe server on 5.x the first time.
I copied over my working configuration from 4.9 and started the 
mpd. Than a didn't two times an connection attempted from an
winxp an got two the same panic:

Feb 13 15:40:49 neo kernel: 
Feb 13 15:40:49 neo kernel: 
Feb 13 15:40:49 neo kernel: Fatal trap 12: page fault while in kernel mode
Feb 13 15:40:49 neo kernel: cpuid = 0; apic id = 00
Feb 13 15:40:49 neo kernel: fault virtual address	= 0x1c
Feb 13 15:40:49 neo kernel: fault code		= supervisor write, page not present
Feb 13 15:40:49 neo kernel: instruction pointer	= 0x8:0xc061b6d5
Feb 13 15:40:49 neo kernel: stack pointer	        = 0x10:0xd77e77a4
Feb 13 15:40:49 neo kernel: frame pointer	        = 0x10:0xd77e77b4
Feb 13 15:40:49 neo kernel: code segment		= base 0x0, limit 0xfffff, type 0x1b
Feb 13 15:40:49 neo kernel: = DPL 0, pres 1, def32 1, gran 1
Feb 13 15:40:49 neo kernel: processor eflags	= interrupt enabled, resume, IOPL = 0
Feb 13 15:40:49 neo kernel: current process		= 37 (swi1: net)
Feb 13 15:40:49 neo kernel: trap number		= 12
Feb 13 15:40:49 neo kernel: panic: page fault
Feb 13 15:40:49 neo kernel: cpuid = 0; 
Feb 13 15:40:49 neo kernel: 

So I'm very sad about. If you need more help to track down
the problem feel free to contact me.
>How-To-Repeat:
      Reboot the System and make an new connection attempt.
>Fix:
      
>Release-Note:
>Audit-Trail:
>Unformatted:


More information about the freebsd-i386 mailing list