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