Date: Wed, 11 Aug 2010 10:19:11 +0200 From: Victor Ophof <mr4hughz@hotmail.com> To: <freebsd-net@freebsd.org> Subject: RE: "RX ring hdr initialization error" Message-ID: <SNT142-w26F3B9913076E4D0D0C8F28C960@phx.gbl> In-Reply-To: <20100810213754.GH6960@michelle.cdnetworks.com> References: <SNT142-w4884CF1F51C4F993E7D6C8C950@phx.gbl>, <20100810213754.GH6960@michelle.cdnetworks.com>
next in thread | previous in thread | raw e-mail | index | archive | help
=20 From: pyunyh@gmail.com Date: Tue=2C 10 Aug 2010 14:37:54 -0700 To: mr4hughz@hotmail.com CC: jfv@freebsd.org=3B freebsd-net@freebsd.org Subject: Re: "RX ring hdr initialization error" On Tue=2C Aug 10=2C 2010 at 12:52:56PM +0200=2C Victor Ophof wrote: >=20 >=20 >=20 >=20 > Hi=20 >=20 > I've bought a asus M4a78-EM Motherboard. to build a NAS on=2C=20 > thinking the onboard Realtek would be sufficant speed=20 > unfortunatly the onboard fives 16/31 mbs at best=20 >=20 > ps later It improved with enabeling "polling" in the kernel (duh)=20 >=20 > so I had a PCI intel GT nic around=2C what gave intermittent tcp/ip conne= ctions in a other machine (ESXi)=20 > unfortunatly this was the same with Freebsd (card issue?) The card is sti= ll in the machine > even with the Intel supplied BSD driver=20 >=20 > now I bought a PCIe intel CT nic=2C put it in and the kernel panic with=20 > "RX ring hdr initialization error" > so replaced the intel with the freebsd one by doing=20 > intel overwrites the freebsd one /boot/kernel/if_em.ko=20 > # cd /usr/src/sys/modules/em/ && make obj depend all install > (was already in the kernel)=20 > =20 >=20 > still panic=20 > anybody got some idea's howto fix ?=20 >=20 --- reaction pyunyh --- I have been using the attached patch for em(4)/igb(4) controllers. These drivers explicitly calls panic(9) when memory allocation failure happens. I don't think it's good idea to panic the box under resource shortage condition as it's common to see this situation on heavily loaded servers. =20 The patch does not solve the one issue yet. The panic caused by RX buffer allocation failure condition which in turn means you're allocating a lot of buffers. Reduce number of descriptors if you=20 increased that too high and see whether the issue could be gone. ---/reaction pyunyh ---What buffers /descriptors I need to reduce? I have 2= gb ram and set the following in /boot/loader.conf vm.kmem_size_max=3D"1024m= " vm.kmem_size=3D"1024m" #vfs.zfs.prefetch_disable=3D1 vm.kmem_size=3D"2048M" vfs.zfs.arc_min=3D"1024M" vfs.zfs.arc_max=3D"1536M" vfs.zfs.vdev.min_pending=3D2 vfs.zfs.vdev.max_pending=3D8 vfs.zfs.txg.timeout=3D5 aio_load=3D"YES" ahci_load=3D"YES" =20 _______________________________________________ freebsd-net@freebsd.org mai= ling list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscr= ibe=2C send any mail to "freebsd-net-unsubscribe@freebsd.org" =
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?SNT142-w26F3B9913076E4D0D0C8F28C960>