disadvantages of running 8.3 kernel on freebsd 8.2 system
I know for UPDATING, it s not correct way, but i tried and 8.2 system works with 8.3 kernel (copied 8.3 /boot/kernel directory to freebsd 8.2 /boot/kernel) and it s not good solution but i want to know; - What are specific disadvantages that i can see clearly, running 8.3 kernel on freebsd 8.2? - What are user land tools those not match with 8.3 kernel on freebsd 8.2 system...? best regards, -- http://www.siyahsapka.org ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: disadvantages of running 8.3 kernel on freebsd 8.2 system
On Thu, Jan 17, 2013 at 02:06:35PM +0200, Ali Okan YÜKSEL wrote: I know for UPDATING, it s not correct way, but i tried and 8.2 system works with 8.3 kernel (copied 8.3 /boot/kernel directory to freebsd 8.2 /boot/kernel) and it s not good solution but i want to know; - What are specific disadvantages that i can see clearly, running 8.3 kernel on freebsd 8.2? - What are user land tools those not match with 8.3 kernel on freebsd 8.2 system...? Because of ... things I'd really rather not even think about, let alone consider discussing ... there are ceratin machines at $work that are thus configured. (Yes, I'm working on repairing this self-inflicted wound.) The only issue of which I'm aware is that if one wishes to use mfiutil(8), it better be one that was built from 8.3 source; an 8.2 mfiutil run on an 8.3 kernel will panic the box consistently. Peace, david -- David H. Wolfskill da...@catwhisker.org Taliban: Evil men with guns afraid of truth from a 14-year old girl. See http://www.catwhisker.org/~david/publickey.gpg for my public key. pgp5XwLJxt2NR.pgp Description: PGP signature
Re: disadvantages of running 8.3 kernel on freebsd 8.2 system
- What are specific disadvantages that i can see clearly, running 8.3 kernel on freebsd 8.2? no idea. just get latest -8 sources, compile world and kernel and install. all newest and in sync. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: disadvantages of running 8.3 kernel on freebsd 8.2 system
On 17 Jan 2013 12:43, Wojciech Puchar woj...@wojtek.tensor.gdynia.pl wrote: - What are specific disadvantages that i can see clearly, running 8.3 kernel on freebsd 8.2? no idea. just get latest -8 sources, compile world and kernel and install. all newest and in sync. I agree; very weird problems sometimes happen with out of sync kernel/world; normally with new world old kernel, but the opposite is possible. Are you simply apprehensive over the time of buildworld? Chris ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: disadvantages of running 8.3 kernel on freebsd 8.2 system
On Jan 17, 2013, at 4:06 AM, Ali Okan YÜKSEL wrote: I know for UPDATING, it s not correct way, but i tried and 8.2 system works with 8.3 kernel (copied 8.3 /boot/kernel directory to freebsd 8.2 /boot/kernel) and it s not good solution but i want to know; - What are specific disadvantages that i can see clearly, running 8.3 kernel on freebsd 8.2? A couple user land tools might barf on you (listed below). Other than that, it's generally considered very safe. The quintessential test-case is running an 8.2 jail under an 8.3 host. We do this all the time with various releases (again, most-problematic utilities listed below). - What are user land tools those not match with 8.3 kernel on freebsd 8.2 system…? top and ps might complain about procsize mismatch. netstat has been known to have problems if the gap is too wide. That's about all that I can think off the top of my head. The quick solution is to just grab the 8.3-R copies of top, ps, and netstat *IFF* they cause problems (e.g., ps immediately dies with procsize mismatch error). -- Devin P.S. Been doing this kind of mismatching of kernel/userland for YEARS (all the way back to 4.4/4.8) and top and ps always prove to be problematic. _ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: disadvantages of running 8.3 kernel on freebsd 8.2 system
Are you simply apprehensive over the time of buildworld? no idea what you mean - my english isn't perfect. I normally have latest binaries and generic kernel built for FreeBSD 8 which i use on servers (don't upgrade now as it works and there is no need to). I have .tar.gz file with binaries, and compile custom kernel on given machine but with same sys sources. so all always in sync. I once had strange out of sync problems - but with virtualbox kernel module. recompiling this module solved all of them. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: disadvantages of running 8.3 kernel on freebsd 8.2 system
On 17 Jan 2013 17:13, Wojciech Puchar woj...@wojtek.tensor.gdynia.pl wrote: Are you simply apprehensive over the time of buildworld? no idea what you mean - my english isn't perfect. Sorry, was asking the OP. I normally have latest binaries and generic kernel built for FreeBSD 8 which i use on servers (don't upgrade now as it works and there is no need to). I have .tar.gz file with binaries, and compile custom kernel on given machine but with same sys sources. so all always in sync. I once had strange out of sync problems - but with virtualbox kernel module. recompiling this module solved all of them. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: disadvantages of running 8.3 kernel on freebsd 8.2 system
On Thursday, January 17, 2013 10:57:01 am Devin Teske wrote: On Jan 17, 2013, at 4:06 AM, Ali Okan YÜKSEL wrote: I know for UPDATING, it s not correct way, but i tried and 8.2 system works with 8.3 kernel (copied 8.3 /boot/kernel directory to freebsd 8.2 /boot/kernel) and it s not good solution but i want to know; - What are specific disadvantages that i can see clearly, running 8.3 kernel on freebsd 8.2? A couple user land tools might barf on you (listed below). Other than that, it's generally considered very safe. The quintessential test-case is running an 8.2 jail under an 8.3 host. We do this all the time with various releases (again, most-problematic utilities listed below). - What are user land tools those not match with 8.3 kernel on freebsd 8.2 system…? top and ps might complain about procsize mismatch. netstat has been known to have problems if the gap is too wide. These generally do not have problems in recent release branches. top and ps haven't complained about procsize since the 4.x days as 5.0 introduced a new kinfo_proc structure that the kernel exports and it hasn't changed in size since 5.0. The mfiutil issue dhw@ mentioned is real and is due to an mfi(4) driver change. I merged a fix for the panics to 8-stable, but it just makes old mfiutil binaries not work at all. -- John Baldwin ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: disadvantages of running 8.3 kernel on freebsd 8.2 system
On Jan 17, 2013, at 8:03 AM, John Baldwin wrote: On Thursday, January 17, 2013 10:57:01 am Devin Teske wrote: On Jan 17, 2013, at 4:06 AM, Ali Okan YÜKSEL wrote: I know for UPDATING, it s not correct way, but i tried and 8.2 system works with 8.3 kernel (copied 8.3 /boot/kernel directory to freebsd 8.2 /boot/kernel) and it s not good solution but i want to know; - What are specific disadvantages that i can see clearly, running 8.3 kernel on freebsd 8.2? A couple user land tools might barf on you (listed below). Other than that, it's generally considered very safe. The quintessential test-case is running an 8.2 jail under an 8.3 host. We do this all the time with various releases (again, most-problematic utilities listed below). - What are user land tools those not match with 8.3 kernel on freebsd 8.2 system…? top and ps might complain about procsize mismatch. netstat has been known to have problems if the gap is too wide. These generally do not have problems in recent release branches. top and ps haven't complained about procsize since the 4.x days as 5.0 introduced a new kinfo_proc structure that the kernel exports and it hasn't changed in size since 5.0. The mfiutil issue dhw@ mentioned is real and is due to an mfi(4) driver change. I merged a fix for the panics to 8-stable, but it just makes old mfiutil binaries not work at all. You're the perfect person to help us figure out why when we: 1. back-port mfi(4) from stable/8 into releng/8.3 (8.3-RELEASE-p5 at the time of back-port) 2. Succeed in getting 8.3 to boot on Thunderbolt card 3. mfiutil produces Inappropriate ioctl for device Even after… 4. Recompiling mfiutil from stable/8 (albeit in a releng/8.3 build environment -- back ported headers applied for new macros even) Any hints on where to go next to restore mfiutil access? -- Devin _ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: disadvantages of running 8.3 kernel on freebsd 8.2 system
- Original Message - From: Devin Teske devin.te...@fisglobal.com You're the perfect person to help us figure out why when we: 1. back-port mfi(4) from stable/8 into releng/8.3 (8.3-RELEASE-p5 at the time of back-port) 2. Succeed in getting 8.3 to boot on Thunderbolt card 3. mfiutil produces Inappropriate ioctl for device Even after… 4. Recompiling mfiutil from stable/8 (albeit in a releng/8.3 build environment -- back ported headers applied for new macros even) Any hints on where to go next to restore mfiutil access? You also need to backport mfiutil too. I have a patch set for 8.3 which include latest mfi driver, mfiutil and a large set of mfi driver fixes, even head has some rather serious issues although mainly around error handling on tbolt cards. We're running this in production so believe its a good stable set. If you would like the patch set just let me know. Regards Steve This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmas...@multiplay.co.uk. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: disadvantages of running 8.3 kernel on freebsd 8.2 system
On Jan 17, 2013, at 11:14 AM, Steven Hartland wrote: - Original Message - From: Devin Teske devin.te...@fisglobal.com You're the perfect person to help us figure out why when we: 1. back-port mfi(4) from stable/8 into releng/8.3 (8.3-RELEASE-p5 at the time of back-port) 2. Succeed in getting 8.3 to boot on Thunderbolt card 3. mfiutil produces Inappropriate ioctl for device Even after… 4. Recompiling mfiutil from stable/8 (albeit in a releng/8.3 build environment -- back ported headers applied for new macros even) Any hints on where to go next to restore mfiutil access? You also need to backport mfiutil too. I have a patch set for 8.3 which include latest mfi driver, mfiutil and a large set of mfi driver fixes, even head has some rather serious issues although mainly around error handling on tbolt cards. We're running this in production so believe its a good stable set. If you would like the patch set just let me know. I can't resist when you combine words like production and 8.3 (smiles) I'm definitely interested in the patch. Can you send it our way, please? -- Devin _ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: disadvantages of running 8.3 kernel on freebsd 8.2 system
On 17 Jan 2013, at 20:27, Devin Teske devin.te...@fisglobal.com wrote: On Jan 17, 2013, at 11:14 AM, Steven Hartland wrote: - Original Message - From: Devin Teske devin.te...@fisglobal.com You're the perfect person to help us figure out why when we: 1. back-port mfi(4) from stable/8 into releng/8.3 (8.3-RELEASE-p5 at the time of back-port) 2. Succeed in getting 8.3 to boot on Thunderbolt card 3. mfiutil produces Inappropriate ioctl for device Even after… 4. Recompiling mfiutil from stable/8 (albeit in a releng/8.3 build environment -- back ported headers applied for new macros even) Any hints on where to go next to restore mfiutil access? You also need to backport mfiutil too. I have a patch set for 8.3 which include latest mfi driver, mfiutil and a large set of mfi driver fixes, even head has some rather serious issues although mainly around error handling on tbolt cards. We're running this in production so believe its a good stable set. If you would like the patch set just let me know. I can't resist when you combine words like production and 8.3 (smiles) ? Are you saying 8.3 isn't production worthy ? Works like a charm here for us. 50+ boxes running 8.x, most of which are 8-stable. No offence meant, but I'd take 8.3 over 9.x any day. Any night too, for that matter. YMMV but PF + pfsync + carp (and some boxes with nginx or relayd on top) is pretty good for our workload on 8.3. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
RE: disadvantages of running 8.3 kernel on freebsd 8.2 system
-Original Message- From: Damien Fleuriot [mailto:m...@my.gd] Sent: Thursday, January 17, 2013 2:54 PM To: Devin Teske Cc: Steven Hartland; freebsd-hackers@freebsd.org; Devin Teske; Ali Okan YÜKSEL Subject: Re: disadvantages of running 8.3 kernel on freebsd 8.2 system On 17 Jan 2013, at 20:27, Devin Teske devin.te...@fisglobal.com wrote: On Jan 17, 2013, at 11:14 AM, Steven Hartland wrote: - Original Message - From: Devin Teske devin.te...@fisglobal.com You're the perfect person to help us figure out why when we: 1. back-port mfi(4) from stable/8 into releng/8.3 (8.3-RELEASE-p5 at the time of back-port) 2. Succeed in getting 8.3 to boot on Thunderbolt card 3. mfiutil produces Inappropriate ioctl for device Even after… 4. Recompiling mfiutil from stable/8 (albeit in a releng/8.3 build environment -- back ported headers applied for new macros even) Any hints on where to go next to restore mfiutil access? You also need to backport mfiutil too. I have a patch set for 8.3 which include latest mfi driver, mfiutil and a large set of mfi driver fixes, even head has some rather serious issues although mainly around error handling on tbolt cards. We're running this in production so believe its a good stable set. If you would like the patch set just let me know. I can't resist when you combine words like production and 8.3 (smiles) ? Are you saying 8.3 isn't production worthy ? With the right hardware, yes, that's what we're experiencing with latent hardware that we've been tasked with benchmarking. Works like a charm here for us. 50+ boxes running 8.x, most of which are 8-stable. But I bet you're not sitting 88 units of Thunderbolt cards that don't work in 8.3. 8.3 is also exhibiting major problems with the igb-based NICs on those same 88 units. No offence meant, but I'd take 8.3 over 9.x any day. Any night too, for that matter. (smiles) YMMV but PF + pfsync + carp (and some boxes with nginx or relayd on top) is pretty good for our workload on 8.3. I do indeed appreciate the vote of confidence. The hope is that when we get through our mfi and igb problems that 8.3 will be a slammin' victory on this hardware (but until then, we're fighting the good fight). -- Devin _ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: disadvantages of running 8.3 kernel on freebsd 8.2 system
- Original Message -
From: dte...@freebsd.org
But I bet you're not sitting 88 units of Thunderbolt cards that don't work in
8.3.
8.3 is also exhibiting major problems with the igb-based NICs on those same 88
units.
Only effects igb init but might want to make sure you have r245334 back ported
to
avoid memory leaks when mbuf clusters are exhausted.
8.3 version of the patch attached ;-)
For reference not only does this prevent the nic initialising properly it can
also hang
the boot process as when routing initialises route appears to trigger mbuf
allocation
with wait and as mbufs are exhaused and not freed correctly this hangs forever.
This will happen on an untuned kernel if more than 2 igb nics are configured as
each igb requires 8k of mbuf clusters (1k per queue x 8 queues on a machine with
8 or more cores) and the default kern.ipc.nmbclusters is only 25600.
For clarity by configured I mean if the nic is initialised either by
assigning an IP
or ifconfig igbX up the queues are not allocated if the nic is present but
unused.
Regards
Steve
This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it.
In the event of misdirection, illegible or incomplete transmission please
telephone +44 845 868 1337
or return the E.mail to postmas...@multiplay.co.uk.
Fixed mbuf free when receive structures fail to allocate.
This prevents quad igb card on high core machines, without any nmbcluster or
igb queue tuning wedging the boot process if all nics are configured.
--- sys/dev/e1000/if_igb.c.orig 2013-01-10 21:44:03.017805977 +
+++ sys/dev/e1000/if_igb.c 2013-01-10 21:44:55.751355018 +
@@ -4335,8 +4335,8 @@
* the rings that completed, the failing case will have
* cleaned up for itself. 'i' is the endpoint.
*/
- for (int j = 0; j i; ++j) {
- rxr = adapter-rx_rings[i];
+ for (int j = 0; j i; ++j) {
+ rxr = adapter-rx_rings[j];
IGB_RX_LOCK(rxr);
igb_free_receive_ring(rxr);
IGB_RX_UNLOCK(rxr);
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
