Re: Ivy Bridge-EP Xeon (E5-2637v2) and Intel C602 Patsburg-A Chipset support
On Mon, Nov 11, 2013 at 10:56 AM, Andy a...@brandwatch.com wrote: On Fri 08 Nov 2013 18:28:38 GMT, Chris Cappuccio wrote: Andy [a...@brandwatch.com] wrote: Hi Chris, Yea that makes sense, as you say its pretty trivial and a divide by zero check is a common coding practice... I will try again as I only tried 'Max Performance' but it might mean until this is fixed we cannot enable 'Turbo+' at all. With the GIANT lock in OpenBSD I was really hoping that Turbo+ would work as that gives me a few hundred extra MHz on top of the default 3.5GHz Ivy clock in a single core etc. Please let me know if a commit for this is done and I will test using a snapshot :) Thanks for your time, Andy. My patch is almost certainly not the right solution. But it will possibly allow you to boot in turbo mode. So, it might be interesting to try it, or to try a version with the patch (to get a turbo mode dmesg for phessler) and also some extra info like: printf(high: %d low: %d cpuspeed %d\n,high,low,cpuspeed); in the est_init() function after high and low are calculated (of course). Perhaps the way that the est_fqlist is built is faulty for new CPUs, dmesg output from this might show this. For some reason I thought I had a Xeon 55xx but it's actually an E5-26xx, and not a v2 either. And doesn't show this problem as far as I can tell. Maybe I need to test it more! Ok, I'll have a go at writing the fix and test it, but expect some pretty newbie questions.. It's been a /very/ long time since I've written any C and I've never tried to compile OpenBSD. I'll read http://www.openbsd.org/faq/faq5.html next weekend.. and man release ...
Re: Ivy Bridge-EP Xeon (E5-2637v2) and Intel C602 Patsburg-A Chipset support
On Fri 08 Nov 2013 18:28:38 GMT, Chris Cappuccio wrote: Andy [a...@brandwatch.com] wrote: Hi Chris, Yea that makes sense, as you say its pretty trivial and a divide by zero check is a common coding practice... I will try again as I only tried 'Max Performance' but it might mean until this is fixed we cannot enable 'Turbo+' at all. With the GIANT lock in OpenBSD I was really hoping that Turbo+ would work as that gives me a few hundred extra MHz on top of the default 3.5GHz Ivy clock in a single core etc. Please let me know if a commit for this is done and I will test using a snapshot :) Thanks for your time, Andy. My patch is almost certainly not the right solution. But it will possibly allow you to boot in turbo mode. So, it might be interesting to try it, or to try a version with the patch (to get a turbo mode dmesg for phessler) and also some extra info like: printf(high: %d low: %d cpuspeed %d\n,high,low,cpuspeed); in the est_init() function after high and low are calculated (of course). Perhaps the way that the est_fqlist is built is faulty for new CPUs, dmesg output from this might show this. For some reason I thought I had a Xeon 55xx but it's actually an E5-26xx, and not a v2 either. And doesn't show this problem as far as I can tell. Maybe I need to test it more! Ok, I'll have a go at writing the fix and test it, but expect some pretty newbie questions.. It's been a /very/ long time since I've written any C and I've never tried to compile OpenBSD. I'll read http://www.openbsd.org/faq/faq5.html next weekend..
Re: Ivy Bridge-EP Xeon (E5-2637v2) and Intel C602 Patsburg-A Chipset support
Hi back in the office now.
On Thu 07 Nov 2013 20:54:20 GMT, Chris Cappuccio wrote:
Andy Lemin [a...@brandwatch.com] wrote:
Hi, sadly OpenBSD does not boot with the latest Ivy Bridge EP (E5-2637v2) with
'Power Technology' in the supermicro BIOS set to 'Max Performance', on both 5.4
release and the snapshot dated Nov 3rd;
This is a bug that needs to be fixed.
So enabling the 'Power Technology' results in trace;
kernel: integer divide fault trap, code=0
Stopped atest_init+0xc3: idivl %ebx,%ea%
est_init() at est_init+0xc3
mainbus_attach() at mainbus_attach+0xd5
config_attach() at config_attach+0x1d4
cpu_configure() at cpu_configure+0x17
main() at main+0x3f5
end trace frame: 0x0, count: 6
ddb{0}
However even with the BIOS set to defaults I still see these errors though
during boot;
Those aren't errors. There is nothing wrong here.
I understand that these are not errors but are warnings for found
devices which OpenBSD has no drivers for etc.. However their are a
/lot/ of missing devices which is worrying and makes me wonder what on
the motherboard is not working... The chipset is Intel and these are
all missing Intel drivers.
vendor Intel unknown product 0x0e80 (class system subclass
miscellaneous, rev 0x04) at pci14 dev 8 function 0 not configured
vendor Intel unknown product 0x0e90 (class system subclass
miscellaneous, rev 0x04) at pci14 dev 9 function 0 not configured
vendor Intel unknown product 0x0ec0 (class system subclass
miscellaneous, rev 0x04) at pci14 dev 10 function 0 not configured
vendor Intel unknown product 0x0ec1 (class system subclass
miscellaneous, rev 0x04) at pci14 dev 10 function 1 not configured
vendor Intel unknown product 0x0ec2 (class system subclass
miscellaneous, rev 0x04) at pci14 dev 10 function 2 not configured
vendor Intel unknown product 0x0e1e (class system subclass
miscellaneous, rev 0x04) at pci14 dev 11 function 0 not configured
.
.
.
Their are 37 missing drivers with most being class subtypes
'miscellaneous' and several 'DASP subclass Time and Frequency' types.
Seems like a lot of missing functions? On our older firewall hardware
not one warning like this was seen.. Anyway I'll start testing this new
hardware in the coming weeks now I have the 5.4 release installed.
Cheers, Andy.
Re: Ivy Bridge-EP Xeon (E5-2637v2) and Intel C602 Patsburg-A Chipset support
On 2013 Nov 08 (Fri) at 10:31:56 + (+), Andy wrote:
:On Thu 07 Nov 2013 20:54:20 GMT, Chris Cappuccio wrote:
:Andy Lemin [a...@brandwatch.com] wrote:
:Hi, sadly OpenBSD does not boot with the latest Ivy Bridge EP (E5-2637v2)
with 'Power Technology' in the supermicro BIOS set to 'Max Performance', on
both 5.4 release and the snapshot dated Nov 3rd;
:
:
:This is a bug that needs to be fixed.
:
:
:So enabling the 'Power Technology' results in trace;
:kernel: integer divide fault trap, code=0
:Stopped atest_init+0xc3: idivl %ebx,%ea%
:est_init() at est_init+0xc3
:mainbus_attach() at mainbus_attach+0xd5
:config_attach() at config_attach+0x1d4
:cpu_configure() at cpu_configure+0x17
:main() at main+0x3f5
:end trace frame: 0x0, count: 6
:ddb{0}
:
Please include the full dmesg from this machine. It will have important
information for us to look at this problem.
:However even with the BIOS set to defaults I still see these errors though
during boot;
:
:Those aren't errors. There is nothing wrong here.
:
:
:I understand that these are not errors but are warnings for found
:devices which OpenBSD has no drivers for etc.. However their are a
:/lot/ of missing devices which is worrying and makes me wonder what
:on the motherboard is not working... The chipset is Intel and these
:are all missing Intel drivers.
:
:vendor Intel unknown product 0x0e80 (class system subclass
:miscellaneous, rev 0x04) at pci14 dev 8 function 0 not configured
This is 100% not a problem. Feel free to ignore them. Or, if they do
bother you, patches are welcome :).
--
Procrastinators do it tomorrow.
Re: Ivy Bridge-EP Xeon (E5-2637v2) and Intel C602 Patsburg-A Chipset support
On Fri 08 Nov 2013 10:42:52 GMT, Peter Hessler wrote:
On 2013 Nov 08 (Fri) at 10:31:56 + (+), Andy wrote:
:On Thu 07 Nov 2013 20:54:20 GMT, Chris Cappuccio wrote:
:Andy Lemin [a...@brandwatch.com] wrote:
:Hi, sadly OpenBSD does not boot with the latest Ivy Bridge EP (E5-2637v2)
with 'Power Technology' in the supermicro BIOS set to 'Max Performance', on both 5.4
release and the snapshot dated Nov 3rd;
:
:
:This is a bug that needs to be fixed.
:
:
:So enabling the 'Power Technology' results in trace;
:kernel: integer divide fault trap, code=0
:Stopped atest_init+0xc3: idivl %ebx,%ea%
:est_init() at est_init+0xc3
:mainbus_attach() at mainbus_attach+0xd5
:config_attach() at config_attach+0x1d4
:cpu_configure() at cpu_configure+0x17
:main() at main+0x3f5
:end trace frame: 0x0, count: 6
:ddb{0}
:
Please include the full dmesg from this machine. It will have important
information for us to look at this problem.
Ok, might take me a while though as didn't manage to configure IPMI
yesterday and I'm no where near the data centre now and have since
rebooted with 'Power Technology' disabled..
:However even with the BIOS set to defaults I still see these errors though
during boot;
:
:Those aren't errors. There is nothing wrong here.
:
:
:I understand that these are not errors but are warnings for found
:devices which OpenBSD has no drivers for etc.. However their are a
:/lot/ of missing devices which is worrying and makes me wonder what
:on the motherboard is not working... The chipset is Intel and these
:are all missing Intel drivers.
:
:vendor Intel unknown product 0x0e80 (class system subclass
:miscellaneous, rev 0x04) at pci14 dev 8 function 0 not configured
This is 100% not a problem. Feel free to ignore them. Or, if they do
bother you, patches are welcome :).
Ok, as long as we're not missing out on any performance gaining
features.
Cheers, Andy.
Re: Ivy Bridge-EP Xeon (E5-2637v2) and Intel C602 Patsburg-A Chipset support
Andy [a...@brandwatch.com] wrote:
Hi back in the office now.
On Thu 07 Nov 2013 20:54:20 GMT, Chris Cappuccio wrote:
Andy Lemin [a...@brandwatch.com] wrote:
Hi, sadly OpenBSD does not boot with the latest Ivy Bridge EP (E5-2637v2)
with 'Power Technology' in the supermicro BIOS set to 'Max Performance', on
both 5.4 release and the snapshot dated Nov 3rd;
This is a bug that needs to be fixed.
So enabling the 'Power Technology' results in trace;
kernel: integer divide fault trap, code=0
Stopped atest_init+0xc3: idivl %ebx,%ea%
est_init() at est_init+0xc3
mainbus_attach() at mainbus_attach+0xd5
config_attach() at config_attach+0x1d4
cpu_configure() at cpu_configure+0x17
main() at main+0x3f5
end trace frame: 0x0, count: 6
ddb{0}
est_init() in /usr/src/sys/arch/amd64/amd64/est.c has this bit:
low = est_fqlist-table[est_fqlist-n - 1].mhz;
high = est_fqlist-table[0].mhz;
and the only division happening is:
perflevel = (cpuspeed - low) * 100 / (high - low);
So an integer divide trap means a divide-by-zero? That means high and low
are the same?
A stupid fix might be:
if (high - low == 0)
perflevel = 99
else
perflevel = (cpuspeed - low) * 100 / (high - low);
I understand that these are not errors but are warnings for found devices
which OpenBSD has no drivers for etc.. However their are a /lot/ of missing
devices which is worrying and makes me wonder what on the motherboard is not
working... The chipset is Intel and these are all missing Intel drivers.
Their are 37 missing drivers with most being class subtypes 'miscellaneous'
and several 'DASP subclass Time and Frequency' types.
I don't think FreeBSD or Linux match these devices yet either. It is
interesting but not critical.
Re: Ivy Bridge-EP Xeon (E5-2637v2) and Intel C602 Patsburg-A Chipset support
Hi Chris,
Yea that makes sense, as you say its pretty trivial and a divide by
zero check is a common coding practice...
I will try again as I only tried 'Max Performance' but it might mean
until this is fixed we cannot enable 'Turbo+' at all.
With the GIANT lock in OpenBSD I was really hoping that Turbo+ would
work as that gives me a few hundred extra MHz on top of the default
3.5GHz Ivy clock in a single core etc.
Please let me know if a commit for this is done and I will test using a
snapshot :)
Thanks for your time, Andy.
On Fri 08 Nov 2013 17:05:33 GMT, Chris Cappuccio wrote:
Andy [a...@brandwatch.com] wrote:
Hi back in the office now.
On Thu 07 Nov 2013 20:54:20 GMT, Chris Cappuccio wrote:
Andy Lemin [a...@brandwatch.com] wrote:
Hi, sadly OpenBSD does not boot with the latest Ivy Bridge EP (E5-2637v2) with
'Power Technology' in the supermicro BIOS set to 'Max Performance', on both 5.4
release and the snapshot dated Nov 3rd;
This is a bug that needs to be fixed.
So enabling the 'Power Technology' results in trace;
kernel: integer divide fault trap, code=0
Stopped atest_init+0xc3: idivl %ebx,%ea%
est_init() at est_init+0xc3
mainbus_attach() at mainbus_attach+0xd5
config_attach() at config_attach+0x1d4
cpu_configure() at cpu_configure+0x17
main() at main+0x3f5
end trace frame: 0x0, count: 6
ddb{0}
est_init() in /usr/src/sys/arch/amd64/amd64/est.c has this bit:
low = est_fqlist-table[est_fqlist-n - 1].mhz;
high = est_fqlist-table[0].mhz;
and the only division happening is:
perflevel = (cpuspeed - low) * 100 / (high - low);
So an integer divide trap means a divide-by-zero? That means high and low
are the same?
A stupid fix might be:
if (high - low == 0)
perflevel = 99
else
perflevel = (cpuspeed - low) * 100 / (high - low);
I understand that these are not errors but are warnings for found devices
which OpenBSD has no drivers for etc.. However their are a /lot/ of missing
devices which is worrying and makes me wonder what on the motherboard is not
working... The chipset is Intel and these are all missing Intel drivers.
Their are 37 missing drivers with most being class subtypes 'miscellaneous'
and several 'DASP subclass Time and Frequency' types.
I don't think FreeBSD or Linux match these devices yet either. It is
interesting but not critical.
Re: Ivy Bridge-EP Xeon (E5-2637v2) and Intel C602 Patsburg-A Chipset support
Andy [a...@brandwatch.com] wrote: Hi Chris, Yea that makes sense, as you say its pretty trivial and a divide by zero check is a common coding practice... I will try again as I only tried 'Max Performance' but it might mean until this is fixed we cannot enable 'Turbo+' at all. With the GIANT lock in OpenBSD I was really hoping that Turbo+ would work as that gives me a few hundred extra MHz on top of the default 3.5GHz Ivy clock in a single core etc. Please let me know if a commit for this is done and I will test using a snapshot :) Thanks for your time, Andy. My patch is almost certainly not the right solution. But it will possibly allow you to boot in turbo mode. So, it might be interesting to try it, or to try a version with the patch (to get a turbo mode dmesg for phessler) and also some extra info like: printf(high: %d low: %d cpuspeed %d\n,high,low,cpuspeed); in the est_init() function after high and low are calculated (of course). Perhaps the way that the est_fqlist is built is faulty for new CPUs, dmesg output from this might show this. For some reason I thought I had a Xeon 55xx but it's actually an E5-26xx, and not a v2 either. And doesn't show this problem as far as I can tell. Maybe I need to test it more!
Re: Ivy Bridge-EP Xeon (E5-2637v2) and Intel C602 Patsburg-A Chipset support
Hi, sadly OpenBSD does not boot with the latest Ivy Bridge EP (E5-2637v2) with 'Power Technology' in the supermicro BIOS set to 'Max Performance', on both 5.4 release and the snapshot dated Nov 3rd; [demime 1.01d removed an attachment of type image/jpeg which had a name of image.jpeg] If I reset the bios to optimised defaults it does boot which is good.. But as soon as I enable the max performance mode I get the error seen in the attached image. Thankfully disabling HTT and disabling the other cores (leaving only 2 running) to enable 'Turbo' does work! However even with the BIOS set to defaults I still see these errors though during boot; [demime 1.01d removed an attachment of type image/jpeg which had a name of image.jpeg] Cheers, Andy Sent from my iPhone Sent from my iPhone On 5 Nov 2013, at 21:18, Pedro Federico pedfre...@gmail.com wrote: Sorry for replying my own message but my comment to Andy got wrongly into the quote. Just to ensure he sees it: Ok, when you test it please tell us how it worked Thank you both. 2013/11/5 Pedro Federico pedfre...@gmail.com 2013/11/5 Andy a...@brandwatch.com Hi, No I have been waiting for the hardware to arrive as the chips are so new (Sept 2013). C6xx chipsets work fine as Chris said, crossing fingers for Ivy Bridge-EP, this is a few generations ahead of the 55xx CPUs, but I'm sure they will work great as the instruction set is the same. Will be testing in the next week or two. Ok, when you test it please tell us how it worked. Thank you both.
Re: Ivy Bridge-EP Xeon (E5-2637v2) and Intel C602 Patsburg-A Chipset support
Andy Lemin [a...@brandwatch.com] wrote: Hi, sadly OpenBSD does not boot with the latest Ivy Bridge EP (E5-2637v2) with 'Power Technology' in the supermicro BIOS set to 'Max Performance', on both 5.4 release and the snapshot dated Nov 3rd; This is a bug that needs to be fixed. However even with the BIOS set to defaults I still see these errors though during boot; Those aren't errors. There is nothing wrong here.
Re: Ivy Bridge-EP Xeon (E5-2637v2) and Intel C602 Patsburg-A Chipset support
Hi, No I have been waiting for the hardware to arrive as the chips are so new (Sept 2013). C6xx chipsets work fine as Chris said, crossing fingers for Ivy Bridge-EP, this is a few generations ahead of the 55xx CPUs, but I'm sure they will work great as the instruction set is the same. Will be testing in the next week or two. On Tue 05 Nov 2013 00:42:44 GMT, Chris Cappuccio wrote: Pedro Federico [pedfre...@gmail.com] wrote: Andy, did you finally get that server? If so, is OpenBSD running fine? I am interested in that server too. I have some Xeon 55xx with intel C6xx chipsets. Works fucking awsome.
Re: Ivy Bridge-EP Xeon (E5-2637v2) and Intel C602 Patsburg-A Chipset support
13/11/5 Chris Cappuccio ch...@nmedia.net Pedro Federico [pedfre...@gmail.com] wrote: Andy, did you finally get that server? If so, is OpenBSD running fine? I am interested in that server too. I have some Xeon 55xx with intel C6xx chipsets. Works fucking awsome. Nice to read, what is the most powerful configuration (RAM , CPU, net card speed) you have? 2013/11/5 Andy a...@brandwatch.com Hi, No I have been waiting for the hardware to arrive as the chips are so new (Sept 2013). C6xx chipsets work fine as Chris said, crossing fingers for Ivy Bridge-EP, this is a few generations ahead of the 55xx CPUs, but I'm sure they will work great as the instruction set is the same. Will be testing in the next week or two. Ok, when you test it please tell us how it worked. Thank you both.
Re: Ivy Bridge-EP Xeon (E5-2637v2) and Intel C602 Patsburg-A Chipset support
Sorry for replying my own message but my comment to Andy got wrongly into the quote. Just to ensure he sees it: Ok, when you test it please tell us how it worked Thank you both. 2013/11/5 Pedro Federico pedfre...@gmail.com 2013/11/5 Andy a...@brandwatch.com Hi, No I have been waiting for the hardware to arrive as the chips are so new (Sept 2013). C6xx chipsets work fine as Chris said, crossing fingers for Ivy Bridge-EP, this is a few generations ahead of the 55xx CPUs, but I'm sure they will work great as the instruction set is the same. Will be testing in the next week or two. Ok, when you test it please tell us how it worked. Thank you both.
Re: Ivy Bridge-EP Xeon (E5-2637v2) and Intel C602 Patsburg-A Chipset support
Pedro Federico [pedfre...@gmail.com] wrote: Andy, did you finally get that server? If so, is OpenBSD running fine? I am interested in that server too. I have some Xeon 55xx with intel C6xx chipsets. Works fucking awsome.
Ivy Bridge-EP Xeon (E5-2637v2) and Intel C602 Patsburg-A Chipset support
Andy, did you finally get that server? If so, is OpenBSD running fine? I am interested in that server too. On 2013 Sep 16 (Mon) at 16:42:26 +0100 (+0100), Andy wrote: Hi, Does OpenBSD 5.3/5.4 support the very new Ivy Bridge-EP Xeon processors (E5-2637v2) and the Intel C602 Patsburg-A Chipset? http://shop.transtec.co.uk/GB/E/products/server/application_server.html?mod=prodname= http://shop.transtec.co.uk/GB/E/products/server/application_server.html?mod=prodname= \ SA1260A304Rdisp=config I know that OpenBSD runs on any CPU which is based on the AMD64 architecture, however someone has worried me and said that this CPU and chipset is different somehow and might not boot with BSD!? Also according to http://www.openbsd.org/i386.html#hardware the 82599 controller is supported, so I'm also going to buy some Intel X520-DA2 10Gig cards which have the '82599ES' controller. Quite excited at the thought of building a 3.5GHz Ivy Bridge-EP based 10GBit OpenBSD firewall with DDR3-1866MHz RAM :) Planning to test Hennings new ALTQ subsystem diff on OpenBSD 5.4 with this hardware :D Thanks, Andy.
Re: Ivy Bridge-EP Xeon (E5-2637v2) and Intel C602 Patsburg-A Chipset support
* Andy a...@brandwatch.com [2013-09-17 15:36]: On Tue 17 Sep 2013 13:48:45 BST, Stuart Henderson wrote: On 2013-09-16, Andy a...@brandwatch.com wrote: Planning to test Hennings new ALTQ subsystem diff on OpenBSD 5.4 with this hardware :D pardon the pedantry, but it's not altq.. Lol, yes sorry ;) *ALTQ's replacement.. Does it have a name yet, or are you sticking with; new super duper simple prio queuer? I'm not into marketing. It's just the new queueing subsystem. -- Henning Brauer, h...@bsws.de, henn...@openbsd.org BS Web Services GmbH, http://bsws.de, Full-Service ISP Secure Hosting, Mail and DNS Services. Dedicated Servers, Root to Fully Managed Henning Brauer Consulting, http://henningbrauer.com/
Re: Ivy Bridge-EP Xeon (E5-2637v2) and Intel C602 Patsburg-A Chipset support
On Thu, Sep 19, 2013 at 09:14, Henning Brauer wrote: *ALTQ's replacement.. Does it have a name yet, or are you sticking with; new super duper simple prio queuer? I'm not into marketing. It's just the new queueing subsystem. JTNQ it is, then.
Re: Ivy Bridge-EP Xeon (E5-2637v2) and Intel C602 Patsburg-A Chipset support
On Thursday, September 19, 2013, Ted Unangst wrote: On Thu, Sep 19, 2013 at 09:14, Henning Brauer wrote: *ALTQ's replacement.. Does it have a name yet, or are you sticking with; new super duper simple prio queuer? I'm not into marketing. It's just the new queueing subsystem. JTNQ it is, then. pronounced jett'n que? --patrick
just the new queueing subsystem [Was: Re: Ivy Bridge-EP Xeon (E5-2637v2) and Intel C602 Patsburg-A Chipset support]
pkesh...@gmail.com (patrick keshishian), 2013.09.19 (Thu) 09:39 (CEST): On Thursday, September 19, 2013, Ted Unangst wrote: On Thu, Sep 19, 2013 at 09:14, Henning Brauer wrote: *ALTQ's replacement.. Does it have a name yet, or are you sticking with; new super duper simple prio queuer? I'm not into marketing. It's just the new queueing subsystem. Or more correctly: the new just queueing subsystem A byword would be handy nonetheless... JTNQ it is, then. searching the archives for JTNQ would yield better results than searching for just the new queueing subsystem, I suppose. pronounced jett'n que? And have all these wet people [1] here asking where to queue up? :-) Other obvious suggestions: HENQ, NEWQ, PQ [1] http://en.wikipedia.org/wiki/Jetski
Re: just the new queueing subsystem [Was: Re: Ivy Bridge-EP Xeon (E5-2637v2) and Intel C602 Patsburg-A Chipset support]
My vote - *HENQ Chickens lined up.. On Thu 19 Sep 2013 11:34:03 BST, MERIGHI Marcus wrote: pkesh...@gmail.com (patrick keshishian), 2013.09.19 (Thu) 09:39 (CEST): On Thursday, September 19, 2013, Ted Unangst wrote: On Thu, Sep 19, 2013 at 09:14, Henning Brauer wrote: *ALTQ's replacement.. Does it have a name yet, or are you sticking with; new super duper simple prio queuer? I'm not into marketing. It's just the new queueing subsystem. Or more correctly: the new just queueing subsystem A byword would be handy nonetheless... JTNQ it is, then. searching the archives for JTNQ would yield better results than searching for just the new queueing subsystem, I suppose. pronounced jett'n que? And have all these wet people [1] here asking where to queue up? :-) Other obvious suggestions: HENQ, NEWQ, PQ [1] http://en.wikipedia.org/wiki/Jetski
Re: just the new queueing subsystem [Was: Re: Ivy Bridge-EP Xeon (E5-2637v2) and Intel C602 Patsburg-A Chipset support]
On 2013-09-19, MERIGHI Marcus mcmer-open...@tor.at wrote: Other obvious suggestions: HENQ, NEWQ, PQ pff, the old one was ALTQ, clearly this should be NEUQ ;)
Re: just the new queueing subsystem [Was: Re: Ivy Bridge-EP Xeon (E5-2637v2) and Intel C602 Patsburg-A Chipset support]
fair for the german, it is not zen tough NEUQ, like NUKE ? i vote for TheQueue, because What else ?! On Thu, Sep 19, 2013 at 9:14 AM, Stuart Henderson s...@spacehopper.orgwrote: On 2013-09-19, MERIGHI Marcus mcmer-open...@tor.at wrote: Other obvious suggestions: HENQ, NEWQ, PQ pff, the old one was ALTQ, clearly this should be NEUQ ;) -- - () ascii ribbon campaign - against html e-mail /\
Re: just the new queueing subsystem [Was: Re: Ivy Bridge-EP Xeon (E5-2637v2) and Intel C602 Patsburg-A Chipset support]
2013/9/19 Stuart Henderson s...@spacehopper.org On 2013-09-19, MERIGHI Marcus mcmer-open...@tor.at wrote: Other obvious suggestions: HENQ, NEWQ, PQ pff, the old one was ALTQ, clearly this should be NEUQ ;) NEUQ sound like a region from Argentina: Neuquén
Re: Ivy Bridge-EP Xeon (E5-2637v2) and Intel C602 Patsburg-A Chipset support
On 2013 Sep 16 (Mon) at 16:42:26 +0100 (+0100), Andy wrote: :I know that OpenBSD runs on any CPU which is based on the AMD64 :architecture, however someone has worried me and said that this CPU and :chipset is different somehow and might not boot with BSD!? Does Windows work with it? Does it claim it is x86 compatible? Then, yes it Just Works(tm). -- Goto, n.: A programming tool that exists to allow structured programmers to complain about unstructured programmers. -- Ray Simard
Re: Ivy Bridge-EP Xeon (E5-2637v2) and Intel C602 Patsburg-A Chipset support
On Tue 17 Sep 2013 08:58:12 BST, Peter Hessler wrote: On 2013 Sep 16 (Mon) at 16:42:26 +0100 (+0100), Andy wrote: :I know that OpenBSD runs on any CPU which is based on the AMD64 :architecture, however someone has worried me and said that this CPU and :chipset is different somehow and might not boot with BSD!? Does Windows work with it? Does it claim it is x86 compatible? Then, yes it Just Works(tm). Hi, apparently Window support is not quite there yet (http://www.theregister.co.uk/2013/09/10/intel_ivy_bridge_xeon_e5_2600_v2_launch/) for OS Guard, which is an extension feature so I agree that it should work fine, just wanted to be careful before I spend a lot of cash on this new CPU and the C602 Patsburg-A Chipset. But otherwise yes its standard amd64, with the Intel AVX instruction set extensions. Thanks :)
Re: Ivy Bridge-EP Xeon (E5-2637v2) and Intel C602 Patsburg-A Chipset support
On 2013-09-16, Andy a...@brandwatch.com wrote: Planning to test Hennings new ALTQ subsystem diff on OpenBSD 5.4 with this hardware :D pardon the pedantry, but it's not altq..
Re: Ivy Bridge-EP Xeon (E5-2637v2) and Intel C602 Patsburg-A Chipset support
On Tue 17 Sep 2013 13:48:45 BST, Stuart Henderson wrote: On 2013-09-16, Andy a...@brandwatch.com wrote: Planning to test Hennings new ALTQ subsystem diff on OpenBSD 5.4 with this hardware :D pardon the pedantry, but it's not altq.. Lol, yes sorry ;) *ALTQ's replacement.. Does it have a name yet, or are you sticking with; new super duper simple prio queuer?
Re: Ivy Bridge-EP Xeon (E5-2637v2) and Intel C602 Patsburg-A Chipset support
On Tue, Sep 17, 2013 at 02:35:48PM +0100, Andy wrote: On Tue 17 Sep 2013 13:48:45 BST, Stuart Henderson wrote: On 2013-09-16, Andy a...@brandwatch.com wrote: Planning to test Hennings new ALTQ subsystem diff on OpenBSD 5.4 with this hardware :D pardon the pedantry, but it's not altq.. Lol, yes sorry ;) *ALTQ's replacement.. Does it have a name yet, or are you sticking with; new super duper simple prio queuer? IIRC simple prio emulates/uses just 'prio' in VLAN header. The new queueing is called in henning@'s paper new OpenBSD queueing subsystem :) j.
Re: Ivy Bridge-EP Xeon (E5-2637v2) and Intel C602 Patsburg-A Chipset support
Oh yea, just look at the slides.. Dohh ;) On Tue 17 Sep 2013 14:54:12 BST, Jiri B wrote: On Tue, Sep 17, 2013 at 02:35:48PM +0100, Andy wrote: On Tue 17 Sep 2013 13:48:45 BST, Stuart Henderson wrote: On 2013-09-16, Andy a...@brandwatch.com wrote: Planning to test Hennings new ALTQ subsystem diff on OpenBSD 5.4 with this hardware :D pardon the pedantry, but it's not altq.. Lol, yes sorry ;) *ALTQ's replacement.. Does it have a name yet, or are you sticking with; new super duper simple prio queuer? IIRC simple prio emulates/uses just 'prio' in VLAN header. The new queueing is called in henning@'s paper new OpenBSD queueing subsystem :) j.
Ivy Bridge-EP Xeon (E5-2637v2) and Intel C602 Patsburg-A Chipset support
Hi, Does OpenBSD 5.3/5.4 support the very new Ivy Bridge-EP Xeon processors (E5-2637v2) and the Intel C602 Patsburg-A Chipset? http://shop.transtec.co.uk/GB/E/products/server/application_server.html?mod=prodname=SA1260A304Rdisp=config I know that OpenBSD runs on any CPU which is based on the AMD64 architecture, however someone has worried me and said that this CPU and chipset is different somehow and might not boot with BSD!? Also according to http://www.openbsd.org/i386.html#hardware the 82599 controller is supported, so I'm also going to buy some Intel X520-DA2 10Gig cards which have the '82599ES' controller. Quite excited at the thought of building a 3.5GHz Ivy Bridge-EP based 10GBit OpenBSD firewall with DDR3-1866MHz RAM :) Planning to test Hennings new ALTQ subsystem diff on OpenBSD 5.4 with this hardware :D Thanks, Andy.
