1418342450 M * gnarface or are you saying that the it87 module might not be loading because of a fault in ACPI ?
1418342470 M * gnarface or rather, ACPI reserving it somehow for something else
1418342735 M * Bertl yes, ACPI probably checks the sensor and thus claims the range
1418342763 M * Bertl recent kernels check for ACPI allocations and typically block loading a sensor driver which would access this area
1418342776 M * Bertl (giving a busy return code)
1418343207 Q * jpierre03 Ping timeout: 480 seconds
1418343666 J * derjohn_mob ~aj@tmo-110-129.customers.d1-online.com
1418344202 J * jpierre03 ~jpierre03@voyage.prunetwork.fr
1418344392 Q * Wermwud Quit: Leaving (Please imagine me slamming the door on my way out)
1418344551 Q * PowerKe Ping timeout: 480 seconds
1418345180 M * gnarface ah i see
1418345722 J * PowerKe ~tom@d54C6A573.access.telenet.be
1418345928 Q * Guy- Ping timeout: 480 seconds
1418346002 Q * fstd Remote host closed the connection
1418346011 J * derjohn_mobi ~aj@tmo-111-120.customers.d1-online.com
1418346038 J * Guy- ~korn@elan.rulez.org
1418346049 J * fstd ~fstd@xdsl-87-78-190-202.netcologne.de
1418346097 Q * derjohn_mob Ping timeout: 480 seconds
1418346587 Q * zerick Ping timeout: 480 seconds
1418352603 M * Bertl off to bed now ... have a good one everyone!
1418352610 N * Bertl Bertl_zZ
1418361594 J * zerick ~eocrospom@190.118.16.131
1418366287 Q * zerick Ping timeout: 480 seconds
1418366514 J * zerick ~eocrospom@190.118.16.131
1418370029 J * BlackPanx ~kvirc@93-103-10-34.static.t-2.net
1418370427 Q * zerick Ping timeout: 480 seconds
1418370839 J * jeroen ~jeroen@mail.nl02.searchtrends.eu
1418370870 N * jeroen Guest1402
1418371005 J * Ghislain ~aqueos@adsl1.aqueos.com
1418371152 Q * derjohn_mobi Ping timeout: 480 seconds
1418375738 J * beng_ ~BenG@cpc29-aztw22-2-0-cust128.18-1.cable.virginm.net
1418376710 J * derjohn_mobi ~aj@2001:6f8:1337:0:1a2:14bd:d6a9:dbd9
1418377086 M * ard gnarface : it actually isn't a fault in ACPI, it actually says: hands off, I am handling this
1418377120 M * ard On servers with ipmi and a whole BMC running linux, you should just not touch it
1418377131 M * ard as you will be interfering with the BMC
1418377139 M * ard (same i2c bus I guess)
1418377184 A * ccxbnc wonders about compatibility of overlayfs with vserver
1418377196 M * ard glen : do not underestimate the power of arping -b (the correct arping from iputils)
1418377210 N * ccxbnc CcxCZ
1418377249 M * ard glen : and routers tend to cache arp for 4 hours, as they do not want to spoil the network with arp traffic, but sending a vrrp packet every second is fine...
1418377251 A * ard sighs
1418377312 M * ard CcxCZ : currently a problem if you use vanilla :-). Since you would need 3.18 for that.
1418377395 M * CcxCZ yea I know that the vserver patchset didn't catch up with that version yet
1418377407 M * CcxCZ just curious if some of the devs have looked at it
1418377453 M * CcxCZ since aufs & unionfs were always notoriously incompatible
1418377602 M * ard and aufs is a release critical requirement for a debian kernel (yech!)
1418377632 M * ard because if the kernel is not patched with aufs, the debian live build does not work
1418377679 M * ard But I think overlayfs might just be different, since linus has accepted it.
1418377694 M * ard This means it must be very "simple"
1418377707 M * CcxCZ it's name-based, as opposed to inode-based
1418377733 M * ard You might have an issue if you use tags I think...
1418377752 M * ard Or will the contex be propagated automagically?
1418377791 M * CcxCZ dunno. it's supposed to play well with namespaces tho
1418377851 N * Bertl_zZ Bertl
1418377854 M * Bertl morning folks!
1418380748 M * Ghislain yop
1418381430 Q * Defaultti Quit: Quitting.
1418386573 Q * beng_ Quit: I Leave
1418387839 J * damnboy2012 ~damnboy20@host86-187-140-122.range86-187.btcentralplus.com
1418387956 Q * damnboy2012 
1418387977 J * Defaultti defaultti@lakka.kapsi.fi
1418389202 Q * fstd Remote host closed the connection
1418389245 J * fstd ~fstd@xdsl-87-78-190-138.netcologne.de
1418391160 M * Bertl off for now ... bbl
1418391165 N * Bertl Bertl_oO
1418392314 Q * _br_ Ping timeout: 480 seconds
1418392400 J * _br_ ~bjoern_of@213-239-215-232.clients.your-server.de
1418394110 J * Wermwud ~Wermwud@69-29-150-18.stat.centurytel.net
1418394311 J * tgunkel_ ~Thorsten@2a02:908:e039:e80:d992:95be:2cad:50b0
1418394438 J * BenG_ ~bengreen@cpc65450-aztw23-2-0-cust26.18-1.cable.virginm.net
1418394679 M * tgunkel_ Hi everybody, I have a very simple question. I want to switch to a newer kernel but I have problems to understand which recent Kernel is supported by linux vserver. 3.18 does not yet to supported? So I thought maybe the latest longterm kernel 3.14.26 would be a good idea? But then I could only find patches for 3.14.17. Those do patch 3.14.26 but the compile fails with fs/namei.c:283:2: error: implicit declaration of function ‘
1418394679 M * tgunkel_ vx_check’ [-Werror=implicit-function-declaration]    fs/namei.c:283:40: error: ‘VS_ADMIN’ undeclared (first use in this function)    So I am confused. Which kernel should I go for?
1418395015 M * undefined tgunkel_: look on the mailing list
1418395028 M * undefined i send you a link for patch fix-ups for 3.14
1418395038 M * undefined (or 3.10 if you prefer; those are the two i maintain)
1418395048 M * undefined i did the last 3.14 kernel just this last weekend
1418395086 M * undefined tgunkel_: http://list.linux-vserver.org/archive?mss:6806:201412:iokekghdlgmiiocgbkmo
1418395169 M * undefined i personally run 3.10, but in preparation for upstream/gkh dropping long-term support for 3.10, i've started maintaining 3.14
1418395222 M * undefined and let me be more clear: "maintaining patch fix-ups for the linux-vserver patch"
1418395286 M * undefined that's the little bit i maintain: just the patch fix-ups
1418395616 M * tgunkel_ Hi undefined, thanks for replying! I'm still a bit confused which kernel version is like the "recommended" one. For 3.10.62 there also does not seem to be a patch linked on the website (newest I find is 3.10.53).
1418395654 M * undefined for 3.10.62: http://list.linux-vserver.org/archive?mss:6805:201412:jbhdhcccmmjfjihpoflo
1418395727 M * undefined i'll defer to Bertl_oO about which one is "recommended", but the answer might be "which ever one works best for you and if there's a bug then let us know"
1418395977 M * tgunkel_ Thanks again, I'm just a bit confused because I would expect that everybody (including all of you and Bertl) would from time to time head for the latest kernel version, at least if it fixed security issues. Therefore I wonder if I do something wrong that every patch I found so far on the website is not for the most recent version of the kernel?
1418396220 M * undefined those emails provide/reference patches for the latest versions of two upstream long terms kernels (one of them being the latest long-term 3.x: 3.14)
1418396234 M * Ghislain well kernel does daily new ones, there is no ressources to patch everyone of them i think
1418396278 M * Ghislain there is regular updates , any ressource you can provide would help this is a small project ^^
1418396717 M * tgunkel_ I see, so picking either the latest 3.10 or latest 3.14 together with what undefined provided would not be something out of the ordinary but the normal thing to do.
1418396745 M * Bertl_oO yep
1418396813 N * Bertl_oO Bertl
1418396830 M * Bertl if everything goes well, there will be another update round this weekend
1418396990 M * tgunkel_ Thanks alot to all of you! undefined did you ever think about mentioning your extra patches on the download site?
1418397017 M * undefined i've left that up to the people that run the website (who i presume are also subscribed to the mailing list)
1418397050 M * Bertl web pages are currently unmaintained, but we will probably find a solution
1418397067 M * tgunkel_ I though it's wiki so everybody could change stuff?
1418397180 M * Bertl yes and no, some pages are protected
1418397462 J * kiorky ~kiorky@cryptelium.net
1418397530 J * g_en__ ~glen@scratchy.delfi.ee
1418397618 Q * sannes Ping timeout: 480 seconds
1418397671 Q * derjohn_mobi graviton.oftc.net weber.oftc.net
1418397671 Q * gnarface graviton.oftc.net weber.oftc.net
1418397671 Q * mnemoc graviton.oftc.net weber.oftc.net
1418397671 Q * kiorky_ graviton.oftc.net weber.oftc.net
1418397671 Q * glen graviton.oftc.net weber.oftc.net
1418397691 J * mnemoc ~amery@geeks.cl
1418397721 J * derjohn_mobi ~aj@2001:6f8:1337:0:1a2:14bd:d6a9:dbd9
1418397722 J * gnarface ~gnarface@108-227-52-42.lightspeed.irvnca.sbcglobal.net
1418398151 J * sannes ~ace@2a02:fe0:c120:ae50:ac93:7d8e:d87b:2a93
1418401951 Q * BenG_ Quit: I Leave
1418403572 Q * derjohn_mobi Ping timeout: 480 seconds
1418404169 M * Bertl off for a nap ... bbl
1418404173 N * Bertl Bertl_zZ
1418413223 N * Bertl_zZ Bertl
1418413225 M * Bertl back now ...
1418416058 J * Aiken ~Aiken@d63f.h.jbmb.net
1418417135 J * bonbons ~bonbons@2001:a18:22e:fb01:e073:8a3c:5eb0:e427
1418417914 Q * bonbons Quit: Leaving
1418418021 J * bonbons ~bonbons@2001:a18:22e:fb01:8903:3145:254f:3bf6
1418418066 J * zerick ~zerick@190.118.16.131
1418422178 Q * Ghislain Quit: Leaving.
1418422437 Q * bonbons Quit: Leaving
1418422589 J * bonbons ~bonbons@2001:a18:22e:fb01:cc15:244d:c3af:a43b
1418424231 J * derjohn_mobi ~aj@ip-178-203-221-8.hsi10.unitymediagroup.de
1418425307 Q * tgunkel_ Remote host closed the connection
1418427754 Q * trey- Remote host closed the connection