[02:50] <zul> BenC: do you need a newer udev for 2.6.19?
[02:50] <BenC> zul: Don't think so
[02:50] <zul> ok
[02:25] <zorglu_> q. i got a dapper on 2.6.15-26-386, and it just trashed (aka disk active all the time and no more answering ping), i rebooted and /var/log/message is full of oom-killer, is there a way to determine the source of this ?
[02:25] <zorglu_> like the name of the process which consume the memory so suddently
[02:36] <neuralis> there's no guarantee that it was any one process, and discovering which process the oom killed, in particular, will not give you much of any useful information.
[02:40] <zorglu_> well it was a box which was running not doing anything but running a azureus bittorrent (which was not transfering anything)
[02:40] <zorglu_> and from /var/log/message all the swapped was used
[02:40] <zorglu_> usually on the same condition, it has like 380 of free ram + 1gbyte of swap free
[02:41] <zorglu_> so something did consume this 1.4gbyte of memory :)
[02:41] <zorglu_> and quite 'out of the blue' as the box was not doing anything i know of
[02:43] <neuralis> i don't really care about the situation on your machine; i was merely answering your question.
[02:43] <zorglu_> ok :)
[02:44] <zorglu_> so anybody around willing to help ? 
[02:44] <neuralis> i don't see what kind of help you're looking for. in general, no, it's not easily possible to figure out which conditions led to an oom after you've rebooted.
[02:45] <zorglu_> well i would like to determine what caused this box, which was quite idle, to use 1.4gbyte
[02:45] <zorglu_> so i ask for more info
[02:46] <zorglu_> to people who may care :)
[02:46] <neuralis> yes, and i just told you that it generally can't be done.
[02:49] <zorglu_> ok will retry later on a more active hour, see ya
[02:49] <neuralis> sigh.
[02:59] <fabbione> neuralis: hey dude
[02:59] <neuralis> fabbione: hey, i was sick all week and never made it to the office
[02:59] <fabbione> neuralis: feeling better now?
[02:59] <neuralis> somewhat, i can mostly walk now
[03:00] <fabbione> neuralis: ouch
[03:00] <fabbione> neuralis: i did install the t2000
[03:00] <neuralis> ah, cool. so you did the bios upgrade?
[03:00] <fabbione> i left a text file in /root of the gw what i did install and changed
[03:00] <fabbione> no, i didn't do the alom update. the machine can work without but crashes at reboot
[03:01] <fabbione> and there is no way on earth to backport the driver to dapper
[03:01] <fabbione> it pulls in too many changes all over
[03:01] <fabbione> so we will need to live with edgy
[03:01] <neuralis> that was my suspicion when i dug around git, yeah :/
[03:01] <fabbione> the major bloker are the changes to the scsi_sas transport layer
[03:02] <fabbione> otherwise it was a matter of a sed call to revert mutex to semaphores
[03:02] <neuralis> gotcha. yeah, i remember looking at the scsi_sas stuff and thinking that's not going to fly..
[03:03] <fabbione> nope
[03:03] <fabbione> i did install on sdb btw.. 
[03:04] <fabbione> you can trash the install if you want
[03:04] <neuralis> well, it's unfortunate we can't have a lts release on it, but edgy works well, so it's probably not that big of a deal.
[03:04] <fabbione> the gw is all set for you to grab a new installer and do a netboot/netinstall
[03:04] <neuralis> great, thanks.
[03:04] <fabbione> just read the file i left there
[03:04] <neuralis> yep, read it already.
[03:04] <fabbione> i also created an account for me on the ALOm, so you can change the admin passwd
[03:05] <neuralis> will do.
[03:05] <fabbione> and you did place eth0 on the external network btw
[03:05] <fabbione> it took me a while to figure it wasn't on the internal one :)
[03:05] <neuralis> i didn't have a static ip allocated for the machine yet, so it was just picking up an external ip from dhcp, yes
[03:06] <neuralis> i'll create a short page on the wiki about the t2000 rev2 requiring edgy, so there's record of it.
[03:10] <neuralis> by the way, do you know why the machine has a pci card with an fpga on it? 
[03:11] <neuralis> i sort of boggled when i saw that
[03:11] <fabbione> soirry had to go for my son
[03:11] <neuralis> np
[03:12] <fabbione> yeah i know about the dhcp.. i configured .21 static 
[03:12] <fabbione> the pci card you saw is the ALOM
[03:12] <fabbione> it's ppc based card.. 
[03:12] <neuralis> right, i figured, but i'd have assumed they pressed their own asics for that. why on earth an fpga? 
[03:13] <fabbione> no idea
[03:13] <neuralis> maybe it's cheaper if they're doing really low volumes..
[03:13] <fabbione> same volumes as Niagara's :)
[03:13] <neuralis> yeah
[03:14] <fabbione> ok i am off again to play with my son
[03:14] <fabbione> ttyl
[03:14] <neuralis> cheers
[03:14] <neuralis> oh, by the way
[03:15] <neuralis> am i misremembering, or does d-i not have a way of running a b&w install (i.e. not sending the ansi color codes)?
[03:19] <fabbione> it does autodetect :/
[03:19] <fabbione> neuralis: look for sparc64-installer spec for feisty
[03:19] <fabbione> it will make you happy
[03:20] <neuralis> okay, cool. yeah, partitioning with boot on raid and root on lvm on raid took about 2 hours over 9600bps. 
[05:03] <MouseJstr> If I was hoping for a new pre-built kernel variant, should I just add a note to the effect in the EdgyIdeas/Kernel wiki page?
[10:13] <freeflying_> malone #67458
[11:06] <justin420> hi all. anybody help with building a kernel on ubuntu dapper the correct ubuntu way? that includes the ubuntu splash image? and all other ubuntu features?
[11:17] <crimsun> wiki page. (topic)
[11:28] <Xal2> Hi
[11:30] <Xal2> are the daily kernel builds built with the latest kernel?