From nobody@FreeBSD.org  Fri Dec  3 00:02:07 2004
Return-Path: <nobody@FreeBSD.org>
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 6E20B16A4CE
	for <freebsd-gnats-submit@FreeBSD.org>; Fri,  3 Dec 2004 00:02:07 +0000 (GMT)
Received: from www.freebsd.org (www.freebsd.org [216.136.204.117])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 5E1DB43D48
	for <freebsd-gnats-submit@FreeBSD.org>; Fri,  3 Dec 2004 00:02:07 +0000 (GMT)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (localhost [127.0.0.1])
	by www.freebsd.org (8.13.1/8.13.1) with ESMTP id iB3027At027737
	for <freebsd-gnats-submit@FreeBSD.org>; Fri, 3 Dec 2004 00:02:07 GMT
	(envelope-from nobody@www.freebsd.org)
Received: (from nobody@localhost)
	by www.freebsd.org (8.13.1/8.13.1/Submit) id iB3026Jr027736;
	Fri, 3 Dec 2004 00:02:06 GMT
	(envelope-from nobody)
Message-Id: <200412030002.iB3026Jr027736@www.freebsd.org>
Date: Fri, 3 Dec 2004 00:02:06 GMT
From: Jonas Nagel <fireball@zerouptime.ch>
To: freebsd-gnats-submit@FreeBSD.org
Subject: [panic] vlan over fxp driver IP assignment crash
X-Send-Pr-Version: www-2.3

>Number:         74635
>Category:       kern
>Synopsis:       [panic] vlan over fxp driver IP assignment crash
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    yar
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Dec 03 00:10:24 GMT 2004
>Closed-Date:    Sun Jan 29 12:55:15 GMT 2006
>Last-Modified:  Sun Jan 29 12:55:15 GMT 2006
>Originator:     Jonas Nagel
>Release:        5.3-RELEASE-p1 or 5.3-STABLE, Build date: 01.12.2004
>Organization:
-
>Environment:
>Description:
      After creating a vlan0 device and hooking it to the physical 
      device fxp0, assignment of an IP address results into a kernel 
      panic.

      Fatal trap 12: page fault while in kernel mode
      (did not have the chance to write down the entire crash message)

      The problem exists within a GENERIC kernel using the if_vlan.ko 
      kernel loadable module and also after compiling in 'device 
      vlan' into into a custom kernel. 

      I tried both 5.3-RELEASE and 5.3-STABLE kernel sources.

      The Hardware is a IBM ThinkPad R30, fxp0 is the built-in Intel NIC.
>How-To-Repeat:
     ifconfig vlan0 create
     ifconfig vlan0 vlan 1 vlandev fxp0
     ifconfig vlan0 inet 192.168.1.1 netmask 255.255.255.0

     I suspect the problem with the fxp driver because someone else 
     using a different driver on 5.3-RELEASE could not reproduce the 
     bug. Maybe it's even ThinkPad-specific.

     
>Fix:
      Unknown to me.
>Release-Note:
>Audit-Trail:

From: Jonas Nagel <fireball@zerouptime.ch>
To: freebsd-gnats-submit@FreeBSD.org,
	=?ISO-8859-1?Q?Micha=B3?= Listos <mcl@mclhq.com>
Cc:  
Subject: Re: kern/74635: [panic] vlan over fxp driver IP assignment crash
Date: Sat, 04 Dec 2004 18:15:46 +0100

 Micha=B3 Listos mcl <at> mclhq.com wrote:
 > I don't want to pollute freebsd-bugs, and have no time to read about=20
 > proper way to answer there,
 > so I mail you directly.
 
 Well if you decide to follow up, you could simply click on the bottom
 link in the web pr (http://www.freebsd.org/cgi/query-pr.cgi?pr=3D74635).=20
 
 OR you can simply reply to the bug either to freebsd-gnats-submit but
 then make sure you keep the subject the way it is (plus a Re: or
 whatever in front). When replying make sure you only quote the
 absolutely necessary and don't do jeopary quoting. Reply between the
 lines you refer to (like I do now).
 
 > Make sure you did "ifconfig fxp0 up" before issuing the above commands,=
 =20
 > it worked for me
 > some time ago on stationary pc.
 
 I noticed that doing
 # ifconfig vlan0 create
 # ifconfig vlan0 vlan 1 vlandev fxp0
 and
 # ifconfig vlan0 up
 panics the kernel as well. That means its not the assigning of the IP
 but its the 'bringing up the interface', which is the problem.
 
 Actually I had to do
 # ifconfig fxp0 up
 AFTER configuring the vlan0 interface and BEFORE assigning an IP (thus
 bringing the vlan0 interface up). Then it worked for me without crash!
 
 Thanks to you, Micha, since this is a workaround, I replied directly to
 gnats as well.
 
 But the crash should still be fixed. Since we tracked down the issue to
 a very specific action I think this shouldn't be too hard anymore.
 
 
 Regards,
 --=20
 Jonas Nagel <fireball@zerouptime.ch>
 

From: Jonas Nagel <fireball@zerouptime.ch>
To: FreeBSD-gnats-submit@FreeBSD.org, freebsd-bugs@FreeBSD.org
Cc: =?ISO-8859-1?Q?Micha=B3?= Listos <mcl@mclhq.com>
Subject: Re: kern/74635: [panic] vlan over fxp driver IP assignment crash
Date: Sat, 04 Dec 2004 18:20:32 +0100

 Actually, just when I wrote and sent off my previous e-mail on this box,
 the lappy paniced again, while just sitting there, stating:
 
 panic: softdep_setup_inomapdep: found inode
 
 So it seems that the workaround is only of short nature...
 :/
 
 --=20
 Jonas Nagel <fireball@zerouptime.ch>
 

From: Jonas Nagel <fireball@zerouptime.ch>
To: FreeBSD-gnats-submit@FreeBSD.org, freebsd-bugs@FreeBSD.org
Cc:  
Subject: Re: kern/74635: [panic] vlan over fxp driver IP assignment crash
Date: Sun, 05 Dec 2004 04:51:08 +0100

 Maybe the second panic is related to this pr:
 http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/62824
 
 Though it doesn't sound like there were networking components involved.
 In the worst case this second panic got nothing to do with the original
 problem.
 -- 
 Jonas Nagel <fireball@zerouptime.ch>
 

From: Jonas Nagel <fireball@zerouptime.ch>
To: FreeBSD-gnats-submit@FreeBSD.org, freebsd-bugs@FreeBSD.org
Cc:  
Subject: Re: kern/74635: [panic] vlan over fxp driver IP assignment crash
Date: Thu, 09 Dec 2004 20:52:07 +0100

 Alright, as I thought, no relations of the bug
 http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/62824
 with this case; the lappy just 'sat' there, and crashed (frightening and
 saddening at the same time, somehow). Unlucky coincidence.
 
 The workaround to this crash, as described earlier, does work (at least).
 -- 
 Jonas Nagel <fireball@zerouptime.ch>
 

From: Gleb Smirnoff <glebius@cell.sick.ru>
To: Jonas Nagel <fireball@zerouptime.ch>
Cc: freebsd-gnats-submit@freebsd.org
Subject: kern/74635: [panic] vlan over fxp driver IP assignment crash
Date: Sun, 12 Dec 2004 00:38:31 +0300

   Jonas,
 
   this problem can be specific to hardware. I can't reproduce it
 on Thinkpad T20 running CURRENT and this card:
 
 fxp0: <Intel 82559ER Pro/100 Ethernet> port 0x1800-0x183f mem 0xe8100000-0xe811f
 fff,0xe8120000-0xe8120fff irq 11 at device 3.0 on pci0
 
 How does you card look in dmesg?
 
 Can you describe 'panic recipe' as much precisely as possible? And pls
 show output of 'ifconfig fxp0' before starting the recipe.
 
 -- 
 Totus tuus, Glebius.
 GLEBIUS-RIPN GLEB-RIPE

From: Fireball <fireball@zerouptime.ch>
To: Gleb Smirnoff <glebius@cell.sick.ru>,
	FreeBSD-gnats-submit@FreeBSD.org
Cc: freebsd-bugs@FreeBSD.org
Subject: Re: kern/74635: [panic] vlan over fxp driver IP assignment crash
Date: Mon, 13 Dec 2004 16:53:10 +0100

 >   this problem can be specific to hardware. I can't reproduce it
 > on Thinkpad T20 running CURRENT and this card:
 
 Well, I noticed that it requires having IPV6 support compiled in, to
 reproduce the bug. If I take a GENERIC kernel and comment 'options INET6',
 then the panic is no longer reproducable.
  
 > fxp0: <Intel 82559ER Pro/100 Ethernet> port 0x1800-0x183f mem 0xe8100000-0xe811f
 > fff,0xe8120000-0xe8120fff irq 11 at device 3.0 on pci0
 > 
 > How does you card look in dmesg?
 
 fxp0: <Intel 82801DB (ICH4) Pro/100 VE Ethernet> port 0x8000-0x803f mem
 0xd0204000-0xd0204fff irq 11 at device 8.0 on pci2 miibus0: <MII bus> on
 fxp0
 
 > Can you describe 'panic recipe' as much precisely as possible? And pls
 > show output of 'ifconfig fxp0' before starting the recipe.
 
 Lemme type down the panic message/stack trace (I can provide stack
 addresses etc. if needed):
 
 Stopped at 0xc0519017 = fxp_mc_setup+0x47: movw $0,0(%eax)
 db> trace
 fxp_mc_setup(c1ba4000) at 0xc0519017 = fxp_mc_setup+0x47
 fxp_ioctl(c1ba4000,80206932,0) at 0xc0518de6 = fxp_ioctl+0x12e
 if_delmulti(...) at  ...
 vlan_setmulti(...) at ...
 vlan_ioctl(...) at ...
 vlan_ifaddmulti(...) at ...
 if_addmulti(...) at ...
 in6_addmulti(...) at ...
 in6_update_ifa(...) at ...
 in6_ifattach_linklocal(...) at ...
 in6_ifattach(...)
 in6_if_up(...)
 if_route(...)
 if_up(...)
 ifhwioctl(...)
 ifioctl(...)
 soo_ioctl(...)
 iotctl(...)
 syscall(2f,2f,2f,3,1) at ... = ...
 Xint0x80_syscall() at 0xc07af1cf = ...
 --- syscall (54, FreeBSD ELF32, ioctl), eip = 0x280cc0b7, esp =
 0xbfbfebac, ebp = 0xbfbfebf8 ---
 
 -- 
 Jonas Nagel <fireball@zerouptime.ch>
 

From: Fireball <fireball@zerouptime.ch>
To: Gleb Smirnoff <glebius@cell.sick.ru>
Cc: freebsd-gnats-submit@freebsd.org
Subject: Re: kern/74635: [panic] vlan over fxp driver IP assignment crash
Date: Mon, 13 Dec 2004 16:58:41 +0100

 > And pls show output of 'ifconfig fxp0' before starting the recipe.
 
 root@hirtnb04:~# ifconfig vlan0 create
 root@hirtnb04:~# ifconfig vlan0 vlan 1 vlandev fxp0
 root@hirtnb04:~# ifconfig fxp0
 fxp0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
         options=8<VLAN_MTU>
         inet6 fe80::206:1bff:fec0:d9f4%fxp0 prefixlen 64 scopeid 0x2 
         inet 10.0.0.114 netmask 0xffffff00 broadcast 10.0.0.255
         ether 00:06:1b:c0:d9:f4
         media: Ethernet autoselect (100baseTX <full-duplex>)
         status: active
 
 But it's the same effect with no IP assigned and/or no cable attached.
 
 -- 
 Jonas Nagel <fireball@zerouptime.ch>
 

From: Jonas Nagel <fireball@zerouptime.ch>
To: FreeBSD-gnats-submit@FreeBSD.org, freebsd-bugs@FreeBSD.org
Cc: =?ISO-8859-1?Q?Micha=B3?= Listos <mcl@mclhq.com>
Subject: Re: kern/74635: [panic] vlan over fxp driver IP assignment crash
Date: Sat, 04 Dec 2004 18:20:32 +0100

 Actually, just when I wrote and sent off my previous e-mail on this box,
 the lappy paniced again, while just sitting there, stating:
 
 panic: softdep_setup_inomapdep: found inode
 
 So it seems that the workaround is only of short nature...
 :/
 
 --=20
 Jonas Nagel <fireball@zerouptime.ch>
 
 _______________________________________________
 freebsd-bugs@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
 To unsubscribe, send any mail to "freebsd-bugs-unsubscribe@freebsd.org"
 
State-Changed-From-To: open->feedback 
State-Changed-By: yar 
State-Changed-When: Mon Oct 3 10:27:25 GMT 2005 
State-Changed-Why:  
Can you still reproduce the problem in 6.0-BETAs?  Thanks! 


Responsible-Changed-From-To: freebsd-bugs->yar 
Responsible-Changed-By: yar 
Responsible-Changed-When: Mon Oct 3 10:27:25 GMT 2005 
Responsible-Changed-Why:  
So I can see feedback. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=74635 

From: Gavin Atkinson <gavin.atkinson@ury.york.ac.uk>
To: bug-followup@freebsd.org
Cc: fireball@zerouptime.ch
Subject: Re: kern/74635: [panic] vlan over fxp driver IP assignment crash
Date: Sat, 28 Jan 2006 20:38:04 +0000 (GMT)

 This PR can be closed.
 
 It is a duplicate of kern/78112, and was fixed with sys/dev/fxp/if_fxp.c
 1.225 (HEAD/RELENG_6) and 1.217.2.7 (RELENG_5).
 
 Gavin
State-Changed-From-To: feedback->closed 
State-Changed-By: yar 
State-Changed-When: Sun Jan 29 12:54:05 UTC 2006 
State-Changed-Why:  
>Unformatted:
 >From: Gavin Atkinson <gavin.atkinson@ury.york.ac.uk> 
 >Subject: Re: kern/74635: [panic] vlan over fxp driver IP assignment crash 
 >Date: Sat, 28 Jan 2006 20:38:04 +0000 (GMT) 
 > 
 > This PR can be closed. 
 > 
 > It is a duplicate of kern/78112, and was fixed with sys/dev/fxp/if_fxp.c 
 > 1.225 (HEAD/RELENG_6) and 1.217.2.7 (RELENG_5). 
 > 
 > Gavin 
 
 http://www.freebsd.org/cgi/query-pr.cgi?pr=74635 
