Subject: kern/1280: ifconfig causes panic in i386-current (24/7/95)
To: None <gnats-bugs@gnats.netbsd.org>
From: Acb Barclay <acb@mavericks.bt.co.uk>
List: netbsd-bugs
Date: 07/26/1995 08:57:31
>Number: 1280
>Category: kern
>Synopsis: ifconfig causes panic with AF_ISO and AF_CCITT
>Confidential: no
>Severity: critical
>Priority: medium
>Responsible: kern-bug-people (Kernel Bug People)
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Wed Jul 26 04:05:01 1995
>Last-Modified:
>Originator: Alex Barclay
>Organization:
British Telecommunications plc.
>Release: NetBSD-current (24/7/95)
>Environment:
System: NetBSD portcullis.mavericks.bt.co.uk 1.0A NetBSD 1.0A (PORTCULLIS) #0: Tue Jul 25 12:43:03 1995 root@portcullis.mavericks.bt.co.uk:/amd/clouseau/disks/dk1/NetBSD-current/src/sys/arch/i386/compile/PORTCULLIS i386
>Description:
ifconfig causes panic when used with iso and ns address families
(so far this has happened with _both_ iso and ns on interfaces
ed and lo)
Example command:
ifconfig ed0 ns 1234.1234
Kernel Messages:
vm_fault(f8787a00,0,3,0) -> 1
kernel: page fault trap, code=0
stopped at _ns_control+0x199: movl %ebx, 0(%eax)
Stack Frame
_ns_control
_idp_userreq
_if_ioctl
_soo_ioctl
_ioctl
_syscall
(syscall number 54)
A similar behaviour is exhibited with iso (fault occurs
in _iso_control, I seem to remember)
>How-To-Repeat:
ifconfig with either ns or iso, never fails :-)
>Fix:
Not sure on this. Am currently looking at it. What has been
recently changed in this area?
>Audit-Trail:
>Unformatted: