Port-xen archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

XEN/NetBSD panic during loop in the network switch

To: port-xen%NetBSD.org@localhost
Subject: XEN/NetBSD panic during loop in the network switch
From: Fredrik Pettai <pettai%nordu.net@localhost>
Date: Fri, 26 Sep 2008 17:42:37 +0200

Hi,

We had a misconfiguration issue on one of our smaller server networks,then our personal manage to make a loop by connecting two switchestogether over several physical connector, without running any loopprotection, like STP or equal.

We discovered some weird behavior on one of our servers running XEN(3.1.2) / NetBSD 4.0 RELEASE.It got panic directly (no other system did that), with a very longconsole output...The only modification made to the running kernel (compared with theXEN3_DOM0) is "options NMBCLUSTERS=65536".

The thing that made it more interesting, is that another serverrunning an older version of XEN (3.0.3) / NetBSD 4_BETA2, located inthe same switch, didn't say a thing. It just kept running, business asusual...

Both systems running on the exact same hardware (Dell 2950, the wherepurchased at the same time, but latter one hasn't been firmwareupdated (BIOS, raid controller etc.)). Except that the NetBSD sourcediffer (quite much, BETA2 is from feb 2008), the kernel running on thelatter system is also a XEN3_DOM0, but slightly stripped conf and with"options NMBCLUSTERS=4096"

Anybody else who has experienced the same thing while make loops onthe network? :-)

Or any hints to why the newer XEN/NetBSD system went unhappy?

Here is the console output:

panic: bnx0: Double mbuf allocation failure!
MBegin traceback...
^Mfatal page fault in supervisor mode
^Mtrap type 6 code 0 eip c04e2f30 cs 9 eflags 10246 cr2 0 ilevel 5
^Mpanic: trap
^MFaulted in mid-traceback; aborting...
^Mdumping to dev 4,1 offset 16274551

^Mdump 245 244 243 242 241 240 (XEN) mm.c:649:d0 Error getting mfncf850 (pfn cb) from L1 entry cf850001 f

or dom0
panic: HYPERVISOR_mmu_update failed
^M
^MFaulted in mid-traceback; aborting...
^Mdumping to dev 4,1 offset 16274551

^Mdump (XEN) mm.c:649:d0 Error getting mfn cf850 (pfn cb) from L1entry cf850001 for dom0

panic: HYPERVISOR_mmu_update failed
^M
^MFaulted in mid-traceback; aborting...
^Mdumping to dev 4,1 offset 16274551

^Mdump (XEN) mm.c:649:d0 Error getting mfn cf850 (pfn cb) from L1entry cf850001 for dom0

panic: HYPERVISOR_mmu_update failed
^M
^MFaulted in mid-traceback; aborting...
^Mdumping to dev 4,1 offset 16274551

^Mdump (XEN) mm.c:649:d0 Error getting mfn cf850 (pfn cb) from L1entry cf850001 for dom0

panic: HYPERVISOR_mmu_update failed
^M
^MFaulted in mid-traceback; aborting...
^Mdumping to dev 4,1 offset 16274551

^Mdump (XEN) mm.c:649:d0 Error getting mfn cf850 (pfn cb) from L1entry cf850001 for dom0

panic: HYPERVISOR_mmu_update failed
^M
^MFaulted in mid-traceback; aborting...
dumping to dev 4,1 offset 16274551

^Mdump (XEN) mm.c:649:d0 Error getting mfn cf850 (pfn cb) from L1entry cf850001 for dom0

panic: HYPERVISOR_mmu_update failed
^M
^MFaulted in mid-traceback; aborting...
^Mdumping to dev 4,1 offset 16274551

^Mdump (XEN) mm.c:649:d0 Error getting mfn cf850 (pfn cb) from L1entry cf850001 for dom0

panic: HYPERVISOR_mmu_update failed
^M
^MFaulted in mid-traceback; aborting...
^Mdumping to dev 4,1 offset 16274551

^Mdump (XEN) mm.c:649:d0 Error getting mfn cf850 (pfn cb) from L1entry cf850001 for dom0

panic: HYPERVISOR_mmu_update failed
^M
^MFaulted in mid-traceback; aborting...
^Mdumping to dev 4,1 offset 16274551

^Mdump (XEN) mm.c:649:d0 Error getting mfn cf850 (pfn cb) from L1entry cf850001 for dom0

panic: HYPERVISOR_mmu_update failed
^M
^MFaulted in mid-traceback; aborting...
^Mdumping to dev 4,1 offset 16274551

^Mdump (XEN) mm.c:649:d0 Error getting mfn cf850 (pfn cb) from L1entry cf850001 for dom0

panic: HYPERVISOR_mmu_update failed
^M
^MFaulted in mid-traceback; aborting...
^Mdumping to dev 4,1 offset 16274551
^Mdump panic: HYPERVISOR_mmu_update failed
^M
^MFaulted in mid-traceback; aborting...
^Mdumping to dev 4,1 offset 16274551
^Mdump panic: HYPERVISOR_mmu_update failed
^M
^MFaulted in mid-traceback; aborting...
^Mdumping to dev 4,1 offset 16274551
^Mdump panic: HYPERVISOR_mmu_update failed
^M
^MFaulted in mid-traceback; aborting...
^Mdumping to dev 4,1 offset 16274551
^Mdump panic: HYPERVISOR_mmu_update failed
^M
^MFaulted in mid-traceback; aborting...
^Mdumping to dev 4,1 offset 16274551
^Mdump panic: HYPERVISOR_mmu_update failed
^M
^MFaulted in mid-traceback; aborting...
^Mdumping to dev 4,1 offset 16274551
^Mdump panic: HYPERVISOR_mmu_update failed
^M
^MFaulted in mid-traceback; aborting...
^Mdumping to dev 4,1 offset 16274551
^Mdump panic: HYPERVISOR_mmu_update failed
^M
^MFaulted in mid-traceback; aborting...
^Mdumping to dev 4,1 offset 16274551
^Mdump panic: HYPERVISOR_mmu_update failed
^M
^MFaulted in mid-traceback; aborting...
^Mdumping to dev 4,1 offset 16274551
^Mdump panic: HYPERVISOR_mmu_update failed
^M
^MFaulted in mid-traceback; aborting...
^Mdumping to dev 4,1 offset 16274551
^Mdump panic: HYPERVISOR_mmu_update failed
^M
^MFaulted in mid-traceback; aborting...
^Mdumping to dev 4,1 offset 16274551
^Mdump panic: HYPERVISOR_mmu_update failed
^M
^MFaulted in mid-traceback; aborting...
^Mdumping to dev 4,1 offset 16274551
^Mdump panic: HYPERVISOR_mmu_update failed
^M
^MFaulted in mid-traceback; aborting...
^Mdumping to dev 4,1 offset 16274551
^Mdump panic: HYPERVISOR_mmu_update failed
^M
^MFaulted in mid-traceback; aborting...
^Mdumping to dev 4,1 offset 16274551
^Mdump panic: HYPERVISOR_mmu_update failed
^M
^MFaulted in mid-traceback; aborting...
^Mdumping to dev 4,1 offset 16274551
^Mdump panic: HYPERVISOR_mmu_update failed
^M
^MFaulted in mid-traceback; aborting...
^Mdumping to dev 4,1 offset 16274551
^Mdump panic: HYPERVISOR_mmu_update failed
^M
^MFaulted in mid-traceback; aborting...
^Mdumping to dev 4,1 offset 16274551
^Mdump panic: HYPERVISOR_mmu_update failed
^M
^MFaulted in mid-traceback; aborting...
^Mdumping to dev 4,1 offset 16274551
^Mdump panic: HYPERVISOR_mmu_update failed
^M
^MFaulted in mid-traceback; aborting...
^Mdumping to dev 4,1 offset 16274551
^Mdump panic: HYPERVISOR_mmu_update failed
^M
^MFaulted in mid-traceback; aborting...
^Mdumping to dev 4,1 offset 16274551
^Mdump panic: HYPERVISOR_mmu_update failed
^M
^MFaulted in mid-traceback; aborting...
^Mdumping to dev 4,1 offset 16274551
^Mdump panic: HYPERVISOR_mmu_update failed
^M
^MFaulted in mid-traceback; aborting...
^Mdumping to dev 4,1 offset 16274551
^Mdump panic: HYPERVISOR_mmu_update failed
^M
^MFaulted in mid-traceback; aborting...
^Mdumping to dev 4,1 offset 16274551
^Mdump (XEN) domain_crash_sync called from entry.S (ff16699e)
(XEN) Domain 0 (vcpu#0) crashed on cpu#1:
(XEN) ----[ Xen-3.1.2  x86_32  debug=n  Not tainted ]----
(XEN) CPU:    1
(XEN) EIP:    0009:[<c0706aa5>]
(XEN) EFLAGS: 00010283   CONTEXT: guest
(XEN) eax: 0000000f   ebx: c0a8603a   ecx: 0000000f   edx: 00000003
(XEN) esi: c0a8604a   edi: 0000021d   ebp: c0a86068   esp: c0a85ff0
(XEN) cr0: 8005003b   cr4: 000006d0   cr3: c1b00000   cr2: c0a85ff8
(XEN) ds: 0011   es: 0011   fs: 0031   gs: 0011   ss: 0011   cs: 0009
(XEN) Guest stack trace from esp=c0a85ff0:

(XEN) 000001e3 004001e3 008001e3 00206063 000f4240 00000000000071a0 c0a86050(XEN) c0a86048 c0a86040 00000000 00000200 00000001 0000000200000000 c051ec2f(XEN) c0988aa0 c0a861ec 00006078 00000000 00000000 0000bc28000f0000 00004240(XEN) 021d0000 71a0eb38 00000000 000f4240 9beda64c 00134642c0a86088 c0705a8c(XEN) eb3871a0 0000021d 000f4240 00000000 00000000 00000200c0a860c8 c04f55d5(XEN) eb3871a0 0000021d 000f4240 00000000 00000000 0000000000000000 00000000(XEN) 00000000 000002c0 3ee5e000 c092a5e0 3ee5e000 000002c0c0a86108 c0259cf4(XEN) 000003e8 00000001 d4bc9e80 c0967520 c15e6700 c1246000c0a86108 c025a353(XEN) c1246000 d4bc9e80 00000000 00000001 0000000c c12570f0c0a86158 c025bff6(XEN) c12570f0 c0967520 010054b6 00000001 00000200 00000000c0a86158 c0705b78(XEN) c1246000 c12570f0 000000b6 00000000 00000000 0000000400000000 c0967520(XEN) 00000000 00000000 c0a861c8 c05099cd c124603c 00000000c0967520 00000000(XEN) 01000000 00000000 c0a86198 01000000 eb3871a0 00000001f0a8ee00 00000001(XEN) 00000000 0008003f c15e7400 00000200 c15e6700 c124603c000f4240 002a0000(XEN) b6540001 00010000 9bebcbdd 00000001 00000001 c0a861ecc0a863f8 c04e6da9(XEN) 00000401 00f85477 00000000 c0a861ec 00000200 c1309400c0509790 ca8f8604(XEN) 000001f8 c0a85000 00000001 00a8f000 00000000 0f57100000000000 00000000(XEN) 00000000 00000000 00000000 00000000 00000000 0000000000000000 00000000(XEN) 00000000 00000000 00000000 00000000 00000000 0000000000000000 00000000(XEN) 00000000 00000000 00000000 00000000 00000000 0000000000000000 00000000

(XEN) Domain 0 crashed: rebooting machine in 5 seconds.

TIA,
Fredrik

Follow-Ups:
- Re: XEN/NetBSD panic during loop in the network switch
  - From: Manuel Bouyer

References:
- Xen 3.3: unknown type console at xenbus0 id0 not configured
  - From: Juan RP
- Xen-3.3 build help
  - From: John Hayward
- Re: Xen-3.3 build help
  - From: Manuel Bouyer
- Re: Xen-3.3 build help
  - From: John Hayward
- Re: Xen-3.3 build help
  - From: Manuel Bouyer
- Re: Xen-3.3 build help
  - From: John Hayward
- Re: Xen-3.3 build help
  - From: Manuel Bouyer

Prev by Date: Re: Xen-3.3 build help
Next by Date: Re: XEN/NetBSD panic during loop in the network switch
Previous by Thread: Re: Xen-3.3 build help
Next by Thread: Re: XEN/NetBSD panic during loop in the network switch
Indexes:

Home | Main Index | Thread Index | Old Index