/srv/irclogs.ubuntu.com/2008/11/04/#ubuntu-kernel.txt

=== asac_ is now known as asac
lamontso when I run kvm -cdrom foo.iso, can I change foo.iso to a different iso without rebooting?02:36
stgraberlamont: yes, you need to use the qemu console for that, use ctrl+alt+2 to access the console ctrl+alt+1 to go back to the VM02:43
stgraberyou can then eject and mount a new CD (don't remember the syntax but there is help included IIRC)02:43
lamontcool02:45
lamontand if the machine has never been defined in qemu, I can still talk to it (kvm cli instance) with the qemu console?02:46
stgraberyeah, kvm is using qemu so the ctrl+alt+X shortcuts should work (even with the other frontends like VNC)02:48
lamontcoolness02:55
CarlFKI am trying to track down a memory leak.  the memory does not get freed when I exit the app.  someone suggested I look at /proc/meminfo14:44
CarlFKis there a tool that will show me those on a graph so I can look for deltas?14:45
amitkCarlFK: something like slabtop?14:47
amitkassuming you are looking at a kernel mem leak14:48
CarlFKamitk: not what I was hoping for (a graph) but I am open to suggestions - looking at slabtop14:51
amitkCarlFK: another one to look at might be sysstat14:54
CarlFKisag - Interactive System Activity Grapher for sysstat14:54
CarlFKthat sounds like what I want 14:54
CarlFKamitk: um... how do I run sysstat?  "sysstat is already the newest version; -bash: sysstat: command not found; $ man sysstat; No manual entry for sysstat15:01
_rubensysstat package has iostat and some other tools15:02
CarlFKah - got it15:02
rtgmjg59: Does 'Input: atkbd - expand Latitude's force release quirk to other Dells' seem like a candidate for 2.6.27.y ?15:04
mjg59I don't see why not15:09
BenCrtg: is that related to eject key hang?15:17
rtgBenC: thats what I'm thinking.15:17
BenCrtg: definitely sounds like it15:17
BenCrtg: too bad my latitude doesn't have a cdrom or I would test that theory15:18
rtgBenC: I don't have the equipment back yet to test with, but shold by weeks end15:18
mjg59It is, yeah15:18
mjg59Since there's a keyboard grab for the eject key and it doesn't get released until the key gets released15:18
BenCgood deal then15:18
mjg59Which it never does15:19
asacrtg: there?16:41
rtgasac: yep16:41
asacrtg: do you have an ipw 50XX chipset somewhere?16:41
asacapparently the thing that came after 496516:41
rtgasac: Shirley Peak, iwlwifi  5K16:42
rtgasac: I have 2 of those16:43
asacrtg: are those identical?16:47
rtgasac: Model 512_AN, and Model 533_AN. don't know the differences between them since they are too big to fit any PCIe slots that I have.16:49
asacrtg: oh so you cannot test them?16:49
rtgasac: not easily.16:51
asacrtg: so. do you have any chipset at hand that doesnt connect with WPA in intrepid ;)?17:04
asac(and that connects properly with wpasupplicant manually)17:04
rtgasac: do you mean with a simple Open AP?17:05
asacno with WPA17:05
asacthere are a bunch of regressions with iwl ... and other drivers17:05
rtgasac: oh, you are asking if there are any drivers that _fail_ to connect with WPA, right?17:05
asacrtg: and at best such chipsets that still work with wpasupplicant manually17:05
rtgI use iwl4965 and ath5k every day, connecting to a WPA/PSK/TKIP AP. I never have problems.17:06
asacrtg: with NM?17:06
rtgasac: always. in fact. I've never use wpa_supplicant manually.17:07
asacrtg: i think the biggest prob is the IPW 50XX chipset ... i have reports that that doesnt even work with PSK17:07
asacbut works with supplicant alone17:07
asacall others have issues with enterprise network17:07
rtgstock 2.6.27, or LBM?17:07
asaconly some users report that its just slow17:07
asacrtg: thats all stock i think.17:07
rtgasac: I'm not surprised that there are issues with the stock kernel. The wireless release was totally flubbed.17:08
asacrtg: maybe you have a setup where connecting with NM takes a bit longer than one want?17:09
rtgasac: 1-2 seconds, about what I'd expect.17:09
asacrtg: so how can we ensure better in future17:09
asac?17:09
asacis there anyway to better deal with such "flubbed" wireless releases on our side17:09
asac?17:09
rtgasac: since we aren't upstream developers for wireless, we pretty much get what we're given.17:10
asacrtg: who is upstream for iwl? just those intelliwireless folks?17:12
rtgasac: yep - I think we'll meet some of them at UDS.17:12
asacand who maintains the wireless stack in vanilla kernel?17:13
rtglinville and crew17:13
asaci mean most likely someone pulls in stuff from those intelli folks17:13
asacok17:13
asacso redhat ;)17:13
asacor is that wrong?17:13
rtgI think John Linville is pretty distro agnostic.17:14
asacok. thought he had a redhat address17:14
asacrtg: and atheros is done by atheros in-house and then pushed over the wall?17:14
rtgAll of these wireless drivers are developed in the open using Linville as the maintainer. Subscribe to linux-wireless@vger.kernel.org17:16
asacok thanks17:17
NCommanderhey amitk & lamont 18:29
lamontmorning18:31
NCommanderhow goes it lamont?18:32
rtglamont: I'm getting complaints that LBM didn't fix the b44 problem.18:32
lamontrtg: last I looked it wasn't in the archive (as I saw it)... where should I go grab it from18:33
lamont?18:33
rtgchecking...18:33
rtghttps://edge.launchpad.net/ubuntu/+source/linux-backports-modules-2.6.27/2.6.27-7.518:34
rtglamont: does it need further stroking? Its marked DONE18:34
NCommanderrtg, hi18:42
lamontrtg: no, it means I need to add intrepid-proposed to my list18:42
rtglamont: doh :)18:45
rtgNCommander: need something?18:46
NCommanderrtg, I'm trying to figure out who knows what I need to do to get a ports kernel release (and to get my branch blessed as the next offical tree). I have someone willing to sponsor to upload once the kernel team says its ok18:46
rtgsmb_tp is the guy18:47
smb_tphuh?18:47
smb_tpNCommander, Ah sure. If you have updates, post a message to the kernel-team mailing list, stating where to get (ideally pull) the changes from18:49
NCommandersmb_tp, I have a 2.6.27.4 tree, but its not based off the old tree (git rebase was never meant to go four releases, so I had to start from linus branch and cherry pick)18:50
smb_tpNCommander, are you working on a specific architecture?18:50
NCommandersmb_tp, all of them, but PowerPC is my priority18:50
NCommanderIts been test built on all architectures18:50
NCommanderANd smoke tested on x86 and powerpc. I'm looking for people to smoke test them on sparc, ia64, and hppa (qemu-system-sparc doesn't like my laptop, and I can't find a good ia64 or hppa emulator)18:50
smb_tpNCommander, I guess munkfish would have to be involved a bit (since he did a lot up to now)18:51
NCommandersmb_tp, he already has been involved :-)18:52
smb_tpNCommander, Cool :) ia64 is a bit of a trouble. I only got access to a porter machine, so I can compile but not run a kernel18:53
NCommandersmb_tp, yeah, same problem here18:53
NCommandersmb_tp, but I did get permission to run daily runs on my ia64 porting box18:53
smb_tprtg, Did you have such a beast or was that BenC 18:53
NCommander(my contact at HP is trying to get the same for HPPA)18:53
NCommanderI'm handling powerpc dailies, and I'm using spooky for sparc18:53
NCommanderI just need to throw dak or repopro somewhere18:54
rtgBenC has the ia6418:54
NCommanderTHe installer is hosed on ia64 (a lot of things that should be built as modules are compiled a y, but I don't know enough about the architecture to know what should and shouldn't even be built)18:54
smb_tpNCommander, sounds great. So maybe you just have to announce what you want on kernel-team mailing list and if there are no objections just let me know where your tree can be pulled from18:55
NCommandersmb_tp, its on zinc already: mcasadevall\ubuntu-jaunty-ports :-)18:56
smb_tpNCommander, Yep same with me. I got it somewhat to compile but saw there were several module issues like that18:56
smb_tpNCommander, Great. :) So there were is done18:56
NCommanderSomeone with an ia64 is going to have to bash the kernel with a hammer. I found ski, but it needs a special kernel configuration to be usable, so I might add a flavor18:56
smb_tpNCommander, yeah, most likely. But otherwise you seem to have covered the ground well. The only thing left is some sort of announcement (if you didn't already and I missed that). Not that someone feels stepped onto...19:01
NCommandersmb_tp, I also ported AppArmour to the port architectures ;-)19:02
* NCommander was extremely busy19:02
NCommanderIt compiled without issue, its just testing it since there is no documentation that I could find :-/19:02
smb_tpNCommander, If it boots, its not too bad ;-)19:04
* NCommander is working hard to make the port architecture be awesome again19:04
smb_tpNCommander, Thanks a lot for that19:05
NCommanderOnly doing what I do best :-)19:06
* NCommander is a debian porter19:06
NCommanderA part of me wants to port Ubuntu to the m68k ...19:06
smb_tp:)19:07
NCommanderAlthough mips is much more realistic19:07
sebnerA part of sebner only wants to support x86 and x86_64 :P19:07
NCommanderMostly because I know someone with suitable buildd hardware, and I have an interest in architecture19:07
NCommanderinfinity, ping21:02
infinityNCommander: Yeah?21:02
NCommanderinfinity, I need you to weigh in on a question about PPAs, and giving one to the ports kernel team that is non-virtualized. Cprov told me to ask the distro team for permission who passed me to the buildd admins :-)21:03
NCommander(building the ports kernel on x86 is sorta an exercise in futility)21:04
infinityNCommander: Ugh.  As much as I love ports (and would like the see the ports kernels stop sucking), there are some policy and security reasons for not allowing community PPAs to touch the non-virtual buildds.21:05
* NCommander whacks head on the desk21:05
NCommanderI was told an exception could be granted if I got an ack by the proper teams21:05
NCommanderBut I seem to be going around in a circle21:05
NCommanderinfinity, second BTW, I have a question about the powerpc builders (I'm told they have issues with Hardy, and I was hoping I could get more information so we could track down equivelent hardware and debug)21:06
infinityNCommander: If you can get your hands on some old Xserves, it becomes pretty self-evident under load.21:07
infinityNCommander: Repeated OOPSing until you get a hard lock.21:07
NCommanderinfinity, oh, its an issue under load?21:07
NCommanderDamn it, thats anonying21:07
NCommanderTHe kernel post hardy hasn't been touched until about two weeks ago21:08
infinityNCommander: I tihnk we have some dumps somewhere of the OOPSes.  I'm a bit swamped right now to go hunting, though. :)21:08
NCommanderIF you could get me the specific model of Xserve21:08
NCommanderI can try and track one down before the next LTS21:08
NCommander(or issue a SRU for hardy to fix it if I can track it down)21:08
infinityNCommander: Yeah, I can dig up some info.  I just can't do so right this instant.21:08
NCommanderSUre, no rush, we still have two years to fix it ;-)21:08
infinityWell, I'd *love* to see it fixed in an SRU.21:10
infinityHaving the PPC buildds on an ancient release is not my idea of good times.21:10
NCommanderNo kidding21:10
NCommanderOUr glibc build has about five hacks to disable parts of the test suite21:10
NCommanderITs no just PPC team member has an xserve21:11
infinityI know.21:11
infinityYeah, I don't either.21:11
NCommander(a few IBM servers, and a small army of G4/G5s :-))21:11
infinityMy main PPC devel machines are a 32-bit G3, and an IBM PowerStation.21:11
NCommanderYou will be happy to know jaunty will be sporting a 2.6.27.4 kernel21:11
NCommander(and I'm seeing if I can get the TB to approve a backport of the kernel as linux-ports-backport to intrepid so we have parity on that distribution)21:11
infinityWhich also reminds me, I need to make our yaboot love my Powerstation.21:12
NCommanderugh21:12
NCommanderI don't even want to think the last time yaboot was touched21:12
infinityUnless someone feels like finding YDL's patches and doing so for me.  *hint*21:12
* NCommander adds it to the TODO for today21:12
NCommanderinfinity, if you care to sponsor, and help ACK making my kernel branch the offical jaunty ports one ;-)21:12
infinityGiven that it came with YDL installed, I know they have patches.  They weren't kind enough to send me a source CD, though, and I've not had a chance to go hunting.21:13
NCommanderI don't have the same hardware, but I'll post a source package to my PPA (at least THAT works), and then point you to it to test21:13
infinityBut, yeah.  Regarding non-virtual PPAs... We'll need to discuss precisely who and how many people would be able to upload to it, and then perhaps see if we'd need any formal paperwork, or if we're happy with our trust level with those people, etc.21:14
NCommanderinfinity, personally, I would just want it to be snapshots of our git tree21:14
NCommanderNo direct uploads would be necessary21:15
infinityThe general problem with PPAs is that they're much lower exposure than the archive itself, so it leaves much longer windows of opportunity for people doing Very Bad Things to those machines through PPA uploads.21:15
NCommanderRight21:15
NCommanderI have managed to get approval to run sbuld and friends on four of the five port architectures21:15
NCommanderso if I can't get a non-virtual PPA21:15
NCommanderI'll cobble something together21:15
infinityWhich are you missing?21:15
NCommanderHPPA21:16
infinityI can do that.21:16
NCommanderCool21:16
NCommanderHP provided the itantic21:16
NCommanderI have a (slow) PPC21:16
infinityI have some very fast PPC hardware too.21:16
NCommanderAnd sistpoty already blessed using spooky (aka REVU) as the sparc builder21:16
NCommanderI need people to smoke test kernels21:16
NCommanderI don't have physical access to any of these machines21:16
NCommanderand someone has to beat the ia64 installer w/ a hammer of pain21:17
infinitySo, yeah.  If we don't want to be bothered too much with the possibility of red tape involved in abusing LP for this, I can certainly help with daily builds.21:17
NCommanderinfinity, I need a place to setup dak and wanna-build ... (I've done it before; back when I was an archive manager briefly for the m68k port ;-))21:17
infinityYou worked in Debian 68k?21:18
infinityMust have been after I stepped down.21:18
NCommanderand ARM21:18
NCommanderAnd MIPS21:18
NCommanderI ran four buildds21:18
NCommanderand our w-b after we got kicked off buildd.d.o before moving to d-ports.org21:18
infinityYeah, that's way after my time.21:18
infinityI kinda gave up around the time we became a non-release arch.21:19
infinityLost motivation.21:19
NCommanderActually, we got a new glibc now21:19
NCommanderFreeScale did the enginneering work21:19
NCommanderWhich means its likely we will return in squeeze21:19
infinityNPTL?21:19
NCommanderNPTL21:19
NCommander:-)21:19
infinityNice.  I wonder how much of my groundwork got included in that.21:20
* infinity shrugs.21:20
NCommanderOne of the cool things about coldfire and m68k being nearly the same architecture21:20
* NCommander also did work bootstrapping coldfire debian21:20
NCommanderSadly, I got the board with a hardware fault on it21:20
infinityThey are the same, module a few instructions.21:20
infinityNo one ever claims that i386 and i686 aren't the same arch, so why split hairs? :)21:20
NCommanderinfinity, well, that's why we have lpia21:20
NCommanderFor better or worse21:20
infinityMy ColdFire board is very dusty these days.21:20
NCommanderinfinity, I got my from Stephan21:20
NCommanderinfinity, I actually got as far as a native GCC bootstrap, and booting from flash directly21:21
NCommanderinfinity, actually, I think our yaboot problem is simply we're a year behind on the last current release21:27
infinityNCommander: That's possible.  Given that YDL's Powerstation release is actually a completely seperate CD from their "normal" PPC release, though, I'm assuming there's either a custom yaboot, custom kernel, or (likely) both on there.21:28
NCommanderThere are issues with the kernel when you compile in support for multiple platforms21:28
NCommanderIt crashed and burned when I tried to add anything beyond CHRP and NewWorld21:28
infinityThey can get more than one kernel on a CD, mind you.21:29
infinityBut, yeah, that might be beyond YDL.21:29
infinityThey have some great technical people, but when it comes to user-friendly, they fail.21:29
NCommanderinfinity, what happens when you try and boot on the powerstation?21:29
infinityI almost audibly cried when I saw their default desktop.  It's... It's why most people think UNIX is terrible.21:30
NCommanderIts based off Red Hat21:30
NCommanderWhat do you expert?21:30
infinityAnd, to be honest, I don't recall what exactly happens.  Dies in yaboot land, though.21:30
* NCommander is trying to find their SRPMs21:30
infinityNo, RedHat's default desktop is a pretty clean and friendly place.21:30
NCommanderNot in the 6.x days which YDL was based off of21:30
infinityYDL's reminds me of CDE, circa 1993.21:31
NCommanderinfinity, what version of yellow dog are we talking about?21:31
infinityBooted, and was like, "Oh hai, IRIX, I've missed you!"21:31
NCommanderIRIX was my first UNIX ever ;.;21:32
infinityNCommander: The "latest", I imagine... Whatever shipped with my Powerstation.  Let me find the DVD.21:32
infinityDVD claims it's "Version 6".21:32
NCommanderOk21:32
infinity"Powerstation Edition"21:32
NCommanderso there are no yaboot differences between powerstation and regular21:32
NCommanderX11 and the kernel is where the changes are21:32
NCommanderinfinity, ok, YDL ships with yaboot 1.3.13 with specific changes21:34
NCommanderso its a just matter of diffing21:34
NCommandero_o; wow, lot of patches21:36
NCommanderand no patch system in the deban packaging21:36
NCommandernice21:36
TheMusoNCommander: Yeah I know, kinda annoying.21:37
NCommandernothing powerstation specific here21:37
NCommanderWait21:38
NCommanderwho makes powerstations?21:39
infinityIBM does, but they're unbranded.21:39
infinityhttp://www.terrasoftsolutions.com/products/powerstation/21:39
NCommanderThere are a whole bunch of amiga, and pegasos patches21:39
infinityEvery part inside is IBM, but the box just says "YDL Powerstation".21:39
NCommanderand one ppc64 intrd patch21:39
infinityAnyhow, I have lots of work to do, sadly.21:40
NCommanderinfinity, I'll ping you if/when I h ot test21:40
infinityI'd love to take a weekend and figure out the most minimal way to make Hardy support this machine, though.21:40
NCommanderinfinity, if you however figure out what the error is, it can isolate which patches I need to merge21:40
infinityNCommander: Ping me on Friday?21:40
* NCommander shall do so21:41
NCommanderThat will be after the jaunty kernel lands I hope21:41
infinityNCommander: I'm taking Fridays off work for a while, so I might have some "community fiddling time".21:41
NCommandervery awesome21:41
NCommanderspeaking of community fiddling21:41
NCommanderTheMuso, feel like uploading something?21:41
TheMusoNCommander: Sure. What may that be?21:41
NCommandera kernel21:41
NCommander*hears a gunshot*21:41
TheMusoum... Shouldn't the kernel team bless that?21:41
infinityThe kernel team has almost entirely washed their hands of ports.21:42
NCommander^- infinity 21:42
TheMusoI'm not willing to touch it unless the kernel team really don't want to worry about uploading ports kernels.21:42
infinityTheMuso: You have my blessing to sponsor any ports kernel uploads.  Assuming you have the know-how to do the usual sponsorship vetting/review.21:43
infinityTheMuso: The primary kernel team has almost no interest in them, hence the split. :/21:43
infinityI'm just glad the split happened after Hardy, so the hardy kernels are at least somewhat homogenous.21:44
NCommanderinfinity, the only reason they support lpia is because its not that hard to keep it building21:44
infinityIntrepid ports kernels are a mess. :/21:44
NCommanderinfinity, yeah, it took most of the cycle to clean that up. We only got it fully working towards final freeze (and the installer is still an absolute trainwreck)21:44
TheMusoinfinity: Yeah the sponsoring is no problem. NCommander Alright, what git tree am I working with, your ports tree?21:44
NCommanderTheMuso, that would be mine, but the changelog isn't up to date (you need to call the proper rules to make the changelog be generated correctly)21:45
infinityNCommander: Are there plans to keep ports kernels based on the non-ports git from here on it?21:45
infinitys/it/in/21:45
TheMusoNCommander: I understand that.21:45
NCommanderinfinity, unless a port because offically supported again, yeah21:45
infinityNCommander: Having different kernel versions, slightly different patchset, etc, between ports is... Terribad.21:45
NCommanderinfinity, not for jaunty21:45
NCommanderinfinity, we're actually half a revision higher than the mainline :-)21:46
NCommander(mainline is .2 with cherry picking, ports is .4)21:46
infinityThat still feels icky, to a man who has many different arches at home.21:46
NCommanderSame here21:46
TheMusoAgreed.21:46
NCommanderHow abotu I add amd64 and i386-generic support to ports21:46
infinityI like all my systems to be predictably similar.21:46
NCommanderThen you can run the same kernel across the board ;-)21:46
* NCommander actually did his inital cherry picking patch work on amd64, and then removed those files before committing21:47
* NCommander makes sure the ports tree is up to do21:47
NCommander*date21:47
NCommanderTheMuso, you do know how to do a kernel release, right?21:47
TheMusoNCommander: Yeah there are docs on the wiki. I'll take care of it once I've processed my morning email and taken care of some other things, but it is on my TODO for today.21:48
NCommanderOk, I'll generate all the ABI files in the meantime, and then add them to the tree once 1.1 is uploaded so we have a constant ABI to base against21:49
TheMusoRight.21:49
NCommanderTheMuso, since I have done some work in linux-ports-lrm ;-)21:49
TheMusoNCommander: Ok cool.21:49
NCommander(its just madwifi, but I figure its worth having)21:49
NCommanderlinux-rt will need an upload, but thats multiverse, and I need to clear it by its maintainer anyway21:49
TheMusoNCommander: I see you posted to the kernel list re this kernel. Are you still waiting for a response to that before we go ahead?22:00
NCommanderThats more moving my tree to ubuntu-jaunty-ports.git22:00
TheMusoNCommander: Right.22:00
NCommanderI personally want the kernel to hit jaunty so people can test the damn thing22:00
NCommander(its only been smoke tested on powerpc)22:00
NCommanderalso, not having a kernel package available has blocked work on linux-rt on powerpc, and linux-ports-lrm (its hardware to work against packages that only exist on 127.0.0.1 ;-))22:01
NCommanders/hardware/harder22:01
TheMusoRight.22:02
NCommanderWe probably should look at linux-ports-lbm as well, but I first rather just make sure the kernel is usable (since I can probably find a PS3 or two user willing to test jaunty)22:03
NCommanderalso, once this kernel is uploaded, the next ports daily image will tell us if the installer is completely broken22:04
NCommanderTheMuso, second BTW< please leave my name on the changelog so if a build FTBFS, I can get direct notification of it22:04
TheMusoWell the installer still needs to have some udebs added. Once Colin has merged d-i, I'll add them.22:04
NCommanderTheMuso, I added them to the d-i files in the kernel22:05
TheMusoNCommander: Ok.22:05
TheMusoNCommander: But work needs doing on the d-i side as well.22:05
NCommanderok, well, at least this is progress ;-)22:05
NCommanderbrb, dinner22:05
TheMusoNCommander: hrm when attempting to isnert the change in the changelog using your ports tree, I get the following error. Looks like there may be a tag missing or some such:23:53
TheMusofatal: ambiguous argument 'Ubuntu-2.6.27-0.0..HEAD': unknown revision or path not in the working tree.23:53
TheMusoUse '--' to separate paths from revisions23:53
TheMusoNCommander: I think you missed something.23:53
NCommandero_o;23:53
NCommanderIts possible the repo needs to be tagged 1.123:54
* NCommander hasn't done this before23:54
TheMusoRight, and I think the tag is used to display changes between the last upload and head.23:54
NCommanderSo what do I need to do to fix the tree?23:54
TheMusoNCommander: I am not entirely sure.23:55
NCommanderLet me see if I can tag and get it to work here23:55
NCommanderWhat was the command you used?23:55
=== CarlFK1 is now known as CarlF1
TheMusoNCommander: ./debian/rules insertchanges23:57
NCommanderWorked fine here23:57
TheMusohrm.23:58
NCommanderI'm going to tag it ubuntu-ports-2.6.27-1.1 (we can't overlap with the main kernel, or it will break remotes)23:58
NCommanderTheMuso, I'll just tag and commit with the changelog generated and all that23:58
TheMusoWell my copy of your tree has no tags.23:58
NCommanderMy tree has no tags23:58
TheMusoNCommander: hrm ok.23:58
NCommanderwel23:59
NCommanderI do have tags from remotes23:59
NCommanderVery strange23:59
NCommanderI think its because I restarted the branch things broke23:59
NCommanderIf it does this again next upload, we'll investiage futher23:59
TheMusoNCommander: have a look at this page for instructinos: https://wiki.ubuntu.com/KernelMaintenance23:59

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!