[01:46] <leleobhz> how can i see if a calltrace is a bug or not?
[01:46]  * leleobhz using kernel 2.6.27 from intrepid
[05:19] <juanpaul> hello, how do i clean an already build kernel git directory (aka make mrproper on standard kernels)?
[08:55] <thekorn> hi, since a few days I've thousands of lines like
[08:55] <thekorn> DoRxHighPower(): RF_ZEBRA, Upper Threshold: 99 LOWER Threshold: 70
[08:56] <thekorn> in my kern.log
[08:56] <thekorn> does this indicate a bug, or are this just debug messages
[09:19] <mjg59> You're using ndiswrapper?
[09:22] <thekorn> mjg59, no, I'm not using ndiswrapper
[09:28] <mjg59> Hm. Which wireless driver is this?
[09:35] <thekorn> mjg59, rtl8187
[13:28] <abogani> Could i know if linux-source-2.6.26 package will be dropped from intrepid? I have built -rt kernel package against it...
[13:52] <soren> rtg: If you want to see the kvm update before I file an SRU, it's in my git tree: http://kernel.ubuntu.com/git?p=soren/ubuntu-hardy.git;a=summary
[13:53] <smb_tp> soren, Thanks, we will have a look at it
[13:58] <rtg> soren: big patch. I'm assuming you've been testing it and are happy with its functionality?
[13:59] <smb_tp> They seem to consider kvm not experimental anymore. hmm...
[14:01] <rtg> soren: I'm just wondering how well these applied. did you have to do much conflict resolution to get stuff working?
[14:01] <soren> rtg: I didn't actually apply those patches I list.
[14:02] <soren> rtg: I grabbed the stuff from the kvm-72 release, copied it in, and fixed up the missing/changed data types.
[14:03] <soren> rtg: For the changelog entry, I grabbed the output of something like "git-log Ubuntu-2.6.24-19.36..kvm-72 arch/x86/kvm/* include/*/kvm* virt", IIRC.
[14:04] <soren> So the list of patches in the changelog entry specifies which patches were "logically" applied, even though I didn't actually apply them one-by-one.
[14:05] <soren> It seemed like a good balance between maintaining my sanity, while still giving credit where credits are due.
[14:05] <rtg> soren: ok, back to my original question. Since this is too big to review, I assume you've thoroughly tested it?
[14:07] <soren> I've tested the same code compiled outside the kernel tree (i.e. the same code, but from the kvm-72 tarball). I intend to test it as applied to the kernel tree before I actually ask you to merge it.
[14:07] <soren> There shouldn't be any difference, though.
[14:08] <rtg> soren: ah, so this is just a preview?
[14:08] <soren> rtg: Yeah.
[14:08] <rtg> soren: do you have a test suite for kvm?
[14:08] <soren> i don't expect it to change, though. It compiled for me for both i386 and amd64.
[14:09] <soren> rtg: No.
[14:09] <soren> rtg: ...which adds significantly to the complexity of getting it SRU'ed.
[14:09] <rtg> soren: how can we tell if there are regressions ?
[14:11] <soren> Lots and lots of testing.
[14:11] <abogani> BenC: Dear Sir, Could i know if linux-source-2.6.26 package will be dropped from intrepid? I have built -rt kernel package against it.
[14:11] <rtg> soren: if this stuff builds outside the kernel OK, then how about packaging using DKMS for awhile. Once we 're pretty sure its good, then we could fold it back into the kernel.
[14:12] <soren> upstream does a lot of testing, though, and kvm-72 has been widely deployed (or so I'm told), and no regressions have been found.
[14:12] <soren> rtg: That's what I intend to do in Intrepid.
[14:12] <rtg> soren: I assume that it against an upstream kernel, not 2.6.24
[14:12] <rtg> s/it/is/
[14:12] <soren> rtg: Sorry, what is?
[14:13] <BenC> abogani: Have you tried it against 2.6.27?
[14:13] <rtg> soren: I assume kvm-72 testing has been done against an upstream kernel.
[14:13] <pwnguin> did anyone ever pacify mdz?
[14:14] <soren> rtg: During development, yes. After release, it's used with many different kernel versions. They provide a compatibility layer so that it's usable with older kernels (all the way back to 2.6.18, I believe).
[14:14] <abogani> BenC: rt patchset isn't available for 27 and i don't have enough time to do a forwardporting to 27.
[14:14] <pwnguin> rt isnt in kernel.org?
[14:15] <BenC> abogani: Send it over, and I'll help
[14:15] <BenC> abogani: worst case, we set you up as your own kernel tree for -rt
[14:15] <rtg> soren: have you done the dkms work for Intrepid? It shouldn't be too hard to ifdef to build for Hardy.
[14:16] <abogani> pwnguin: Yes http://www.kernel.org/pub/linux/kernel/projects/rt/
[14:16] <soren> rtg: I've not uploaded it, but I will today or tomorrow.
[14:17] <soren> rtg: I'm not entirely sure, what you're getting at w.r.t. to hardy.
[14:17] <rtg> soren:  I'm just thinking Steve will have a cow if I drop this on him as one huge SRU.
[14:18] <soren> rtg: Does he actually review the code?
[14:18] <rtg> soren: indeed he does.
[14:18] <rtg> soren: but this one will likely overwhelm him.
[14:19] <rtg> soren: both Steve and Martin are meticulous about matching code changes with changelog entries.
[14:19] <soren> rtg: Well, let me worry about that. I'll be the one talking to Steve about KVM, I imagine. The fact that most of the updates are in the kernel shouldn't put the burden on you.
[14:20] <soren> rtg: I've swamped until Thurday (feature freeze stuff), so I won't be pushing this much until then.
[14:21] <rtg> soren: pursuant to the SRU policy, the first thing he is gonna want to know is what actual bugs this patch set fixes. The commit log is too fine grained to glean that info.
[14:21] <soren> rtg: I know. I've done this quite a few times before :)
[14:28] <pwnguin> hrm. im reading why -rt doesn't have a git tree... does git not have a way to pull a specific changeset?
[15:50] <ciol> who is n0u?
[15:51] <BenC> pwnguin: git-cherry-pick
[20:23] <Ng> ogasawara: aha, I'm not on that list. So should that be hitting -proposed shortly? I see the subsequent thread is a an upload of -21.42, but the changelog doesn't mention it?
[20:25] <smb_tp> Ng, the upload for -21.42 seems to be building but I am not sure I know what it is. ;-)
[20:27] <ogasawara> smb_tp:  this was in regards to bug 260664 - https://lists.ubuntu.com/archives/kernel-team/2008-August/002995.html
[20:27] <smb_tp> ogasawara, Ah ok. This is part of lum
[20:28] <smb_tp> ogasawara, lum-...-21.32 (waiting for approval)
[20:29] <ogasawara> Ng: ^^
[20:29] <smb_tp> ogasawara, Ng If someone needs than really quick. It is on my PPA as well
[20:40] <Ng> oh right, lum, of course
[20:41] <Ng> thanks folks :)
[20:41] <smb_tp> Ng, np :)