[06:24] <bbs> hmm
[06:25]  * bbs merges btrfs into jaunty testing locally
[09:00] <fabbione> anybody from the kernel team awake?
[09:06] <smb_tp> fabbione, Would not call it awake but there
[09:06] <fabbione> smb_tp: wtf is going on with your hardy kernel releases?
[09:06] <smb_tp> fabbione, Can you be more specific?
[09:07] <fabbione> yesterday there was an update from hardy-updates that had all the changes that were missing and I reported
[09:07] <fabbione> today there is an update from -security that kills them all
[09:08] <fabbione> smb_tp: remember when I come here to say that there were missing commits from 2.6.24 ?
[09:08] <smb_tp> fabbione, That is because I have to base -security on -updates. I will re-upload a new proposed today
[09:08] <fabbione> smb_tp: an update yesterday mentioend them in the changelog
[09:08] <fabbione> bah. this kind of release management stinks
[09:08] <fabbione> it's far from being serious
[09:08] <fabbione> specially on an LTS
[09:08] <fabbione> there have been weeks to get this right
[09:09] <fabbione> and you are still missing fixes from kernel stable branches
[09:09] <smb_tp> You alsway had this compared to a -propsed kernel
[09:09] <fabbione> i don't use -proposed
[09:09] <fabbione> it was pushed either by mistake or something
[09:10] <fabbione> fact is that either there is a bug in LP or somebody did push the wrong buttons, stuff like that _should not_ happen
[09:10] <smb_tp> thosse fixes you mention should not have been in -updates.
[09:10] <fabbione> well in one way or another they got there
[09:10] <fabbione> root@vultus5:~# grep proposed /etc/apt/sources.list
[09:10] <fabbione> root@vultus5:~# 
[09:11] <fabbione> and i am sure of what i saw because i was happy that i didn't have to rebuild my kernels one more time
[09:11] <smb_tp> That is bad. Good for you but wrong in the process
[09:11] <smb_tp> I have to check that
[09:11] <fabbione> well i strongly recommend you check what happened and why
[09:12] <fabbione> and also find a way to fix missing fixes a bit faster
[09:12] <fabbione> it's been over a month now that I reported those
[09:12] <fabbione> and not all of them affect just second class citizens
[09:12] <smb_tp> Well, sure
[09:13] <fabbione> anyway.. enough rant.. need to finish rebooting machines
[09:13] <fabbione> later
[09:14] <smb_tp> thanks anyway. later
[10:58] <johan> Hi, the ubuntu kernel is currently not including the utrace patches, what needs to happen for them to be included?
[12:00] <apw> smb_tp_, i see there are yet more stable updates being sucked up
[12:47] <smb_tp_> apw, Yeah, there were more this morning, for Jaunty as well
[12:54] <apw> yeah mad levels of updates these days
[12:55] <smb_tp_> a big chunk was the wrappers stuff of our former colleagues. but still quite some more serious stuff as well
[14:21] <scelestic> hi
[14:22] <scelestic> i'm trying to figure out what the cleanest way would be to get a openvz kernel in 8.10, seems there's no patches for the shipped kernel and the stable kernels on openvz.org seems to be a bit dated
[14:34] <smb_tp_> scelestic, I guess the cleanest way would be to build a patchset of openvz tree against the v2.6.27 base and then try to merge those on top of a 8.10 tree.
[14:43] <scelestic> smb_tp_: alright, will give that a try then
[15:47] <tjaalton> apw: does linux-libc-dev from linux-lpia ship the drm headers?
[15:48] <apw> tjaalton, i am just rebasing it to jaunty head as we speak
[15:49] <tjaalton> apw: excellent, so are you bumping the ABI version as well?
[15:49] <apw> so i would guess the answer is no right now and yes soon.  _if_ it has its own
[15:49] <apw> there will be an abi bump yes
[15:49] <tjaalton> to be in line with the rest?
[15:49] <apw> i am planning on just incrementing it
[15:50] <apw> would them being in line be helpful?
[15:50] <tjaalton> yes, otherwise it's confusing
[15:50] <apw> hmmm hadnt considered that
[15:50] <tjaalton> because libdrm-dev currently depends on linux-libc-dev (>= 2.6.28-5.15)
[15:51] <tjaalton> so I'd like to avoid having different deps for different archs
[15:51] <apw> i wonder if the linux-libc-dev is the same or an lpia version
[15:51] <apw> hmmmm
[15:52] <tjaalton> maybe, but in libdrm's case the only thing that matters is if it has the headers or not :)
[15:54] <apw> tjaalton, i am not entirly sure i can guarentee that they stay in step
[15:55] <apw> as there are bound to be different releases in each
[15:55] <apw> if there are ever more in lpia they will necessarily get out of sync
[15:55] <apw> and i don't think its recoverable at that point
[15:56] <tjaalton> let's worry about it then ;)
[15:56] <tjaalton> when that happens
[15:56] <tjaalton> or, I'll just bump the deps independently
[15:56] <tjaalton> not that hard
[22:53] <lesshaste> hi
[22:53] <lesshaste> is this the right place to ask about trying to report kernel panics?  Specifically I was looking for help with crashkernel
[23:02] <bbs> well whats the problem 1
[23:02] <bbs> and two please write a bug report
[23:02] <bbs> no matter where you are if you find a panic crash segfault whatever -- write the report :)
[23:03] <bbs> makes it documented for later perusal and hopefully repair
[23:04] <lesshaste> bbs, I am afraid it's all very unsatisfactory... For the last few ubuntu kernels including the current  2.6.27-11-generic my system simply freezes with caps lock blinking periodically
[23:04] <lesshaste> takes anything from a few hours of use to a few days
[23:04] <lesshaste> so it's not clear to report unless I can set up some sort of crash reporting I was thinking
[23:05] <lesshaste> I am trying to get kexec working as I thought might provide a way to get something useful to report
[23:05] <lesshaste> any help much appreciated as I don't really see any docs on this online
[23:06] <bbs> lesshaste: caps lock or everything blinking
[23:06] <bbs> that would be an OOPS
[23:06] <lesshaste> bbs, just caps lock
[23:06] <bbs> well blinking is an OOPS
[23:06] <lesshaste> everything else completely frozen
[23:06] <bbs> any logs?
[23:06] <lesshaste> ok
[23:06] <bbs> yes OOPS
[23:06] <lesshaste> not that I can see.. where should I look in case I missed anything
[23:08] <lesshaste> /var/log/messages seems to have nothing interesting
[23:10] <bbs> lesshaste: i'm concerned that maybe it cant be logged
[23:10] <bbs> but let me check something
[23:10] <lesshaste> ok thanks
[23:17] <bbs> hmm
[23:18] <bbs> lesshaste: what do your dmesg logs say
[23:18] <bbs> anything weird
[23:18] <lesshaste> bbs, is that the same as /var/log/messages?
[23:18] <bbs> what are you normally ding at the time
[23:18] <bbs> no its not
[23:18] <bbs> are you familiar with dmesg?
[23:18] <lesshaste> bbs, where is dmesg logged? Other than the current record you get just by typing dmesg
[23:19] <lesshaste> or do you just mean the current one?
[23:19] <bbs> /var/log/dmesg
[23:19] <bbs> .0
[23:19] <bbs> .1.gz
[23:19] <bbs> etc
[23:19] <lesshaste> of course.. sorry
[23:19] <bbs> np
[23:19] <bbs> check for OOPS or syscall or something weird
[23:19] <lesshaste> looks harmless to me.. would you like to see some?
[23:19] <bbs> well it would be at the bottom
[23:20] <bbs> zcat the ones with .gz and | less
[23:20] <lesshaste> zcat /var/log/dmesg*gz|grep -i oops  ?
[23:20] <bbs> no
[23:21] <lesshaste> they all end harmlessly
[23:21] <lesshaste> with 
[23:21] <lesshaste> [   36.498604] type=1505 audit(1233257658.981:3): operation="profile_load" name="/usr/sbin/cupsd" name2="default" pid=3920
[23:21] <lesshaste> [   36.701944] ip_tables: (C) 2000-2006 Netfilter Core Team
[23:22] <bbs> yes this is standard
[23:22] <bbs> weirdness
[23:22] <bbs> what are you normally doing when it hapens
[23:23] <lesshaste> just using X
[23:23] <lesshaste> I suppose I always have a web browser open
[23:23] <lesshaste> and I am using wireless
[23:24] <lesshaste> it's probably going to turn out to be the madwifi driver in the end
[23:24] <lesshaste> but it would be nice to actually be able to report something useful!
[23:24] <lesshaste> you don't think adding crashkernel to the bootprompt
[23:24] <lesshaste> and using kexec will work?
[23:27] <lesshaste> hi foka 
[23:28] <lesshaste> bbs, sorry I have to go in a moment.. what do you think?
[23:28] <lesshaste> bbs, I would love to fix this