kern/118897: Kernel Panic acquiring IP address from DHCP server on newly enabled netcard

[Kris Kennaway]

The following reply was made to PR kern/118897; it has been noted by GNATS.

From: Kris Kennaway <kris at FreeBSD.org>
To: Manolis Kiagias <sonicy at otenet.gr>
Cc: freebsd-gnats-submit at FreeBSD.org
Subject: Re: kern/118897: Kernel Panic acquiring IP address from DHCP server
 on	newly enabled netcard
Date: Mon, 31 Dec 2007 16:43:36 +0100

 Manolis Kiagias wrote:
 > Kris Kennaway wrote:
 >> Manolis Kiagias wrote:
 >>>> Number:         118897
 >>>> Category:       kern
 >>>> Synopsis:       Kernel Panic acquiring IP address from DHCP server
 >>>> on newly enabled netcard
 >>>> Confidential:   no
 >>>> Severity:       critical
 >>>> Priority:       medium
 >>>> Responsible:    freebsd-bugs
 >>>> State:          open
 >>>> Quarter:        Keywords:       Date-Required:
 >>>> Class:          sw-bug
 >>>> Submitter-Id:   current-users
 >>>> Arrival-Date:   Thu Dec 20 18:10:02 UTC 2007
 >>>> Closed-Date:
 >>>> Last-Modified:
 >>>> Originator:     Manolis Kiagias
 >>>> Release:        6.3-RC1
 >>>> Organization:
 >>>> Environment:
 >>> FreeBSD pegasus.dyndns.org 6.3-RC1-p1 FreeBSD 6.3-RC1-p1 #2: Sun Dec 
 >>> 2 19:48:21 EET 2007    
 >>> root at pegasus.dyndns.org:/usr/obj/usr/src/sys/PEGASUS  i386
 >>>
 >>>> Description:
 >>> Machine has a broadcom network card shown as bfe0.  At boot, the card
 >>> is not enabled (commented out) in rc.conf Driver attaches normally.
 >>> After editing rc.conf to enable the line:
 >>>
 >>> ifconfig_bfe0="DHCP"
 >>>
 >>> and running:
 >>>
 >>> /etc/rc.d/netif restart
 >>>
 >>> there is a kernel panic while getting an address from DHCP server (a
 >>> linksys home router).
 >>>
 >>> panic: page fault
 >>> fault virtual address = 0x104
 >>> fault code = supervisor read, page not present
 >>> instruction pointer = 0x20:0xc052417d
 >>> stack pointer = 0x28:0xe71ffbec
 >>> frame pointer = 0x28:0xe71ffbf8
 >>> code segment = base 0x0 limit 0xfffff type 0x1b
 >>> =DPL 0, pres 1, def32 1, gran 1
 >>> =resume, IOPL=0
 >>> =971 (ifconfig)
 >>> =12
 >>>> How-To-Repeat:
 >>> The symptom is repeatable every time. Use the procedure mentioned
 >>> above. The symptom does not occur if you reboot after enabling the
 >>> card in rc.conf. In this case the card is assigned an IP and
 >>> subsequent runs of netif have no undesirable effects.
 >>>> Fix:
 >>> None that I know. Only workaround is to reboot after enabling the
 >>> rc.conf entry.
 >>>
 >>>> Release-Note:
 >>>> Audit-Trail:
 >>>> Unformatted:
 >>> _______________________________________________
 >>> freebsd-bugs at freebsd.org mailing list
 >>> http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
 >>> To unsubscribe, send any mail to "freebsd-bugs-unsubscribe at freebsd.org"
 >>>
 >>> .
 >>>
 >> Thanks for the report, but you need to do some additional work to
 >> complete the submission.  Please see:
 >>
 >>
 >> http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html
 >>
 >>
 >> and obtain a crashdump and backtrace.
 >>
 >> Kris
 >>
 >>
 > Hi,
 > 
 > Unfortunately I cannot get a kernel dump from the system. I have set
 > dumpdev to my  swap device in rc.conf. I also tried the AUTO setting. I
 > get the message:
 > 
 > Dumping 2046 (2 chunks)
 > 
 > but it never starts writing.
 > 
 > This is an Acer Aspire 5610 Core Duo (not core2 though) machine,
 > googling revealed SMP maybe responsible for not being able to dump.
 > I recompiled the kernel without SMP, however the non-SMP kernel does not
 > crash performing the  procedure mentioned in the PR.
 > 
 > If there are any more steps I could perform at this point, please let me
 > know. This machine is generally available for all sorts of experiments :)
 > 
 > Thanks,
 > Manolis Kiagias
 > 
 > 
 
 Either try enabling minidumps (debug.minidump), maybe try adding a 
 different disk device (e.g. ATA) and dumping on that, or just use DDB to 
 obtain the information, either by serial console, hand transcription or 
 photography.
 
 Kris