[05:50] apw: you mean making the headers in libdrm-dev to match the kernel ones, and when they work make the switch to using kernel headers? [06:48] Dec 19 06:19:29 quest kernel: [246164.090552] BUG: unable to handle kernel pagin [06:48] g request at ffffe22001651e98 [06:48] ... what does that mean? [07:48] <\sh> morning [07:49] <\sh> did anyone had a kernel panic with amd opteron quad core cpus reading "your cpu is defect...this is not a software problem?" but board system check tells you : cpus are ok...and after a reboot everything is ok again? [10:18] grazie [10:25] grazie a tutti! ciao [11:17] so nope, no memory errors found === lamont` is now known as lamont [14:54] apw: Intrepid -11.22 pushed. [14:54] Good news! [14:55] did you intend this one for everyone? [14:55] UBUNTU: Default CONCURRENCY_LEVEL to _NPROCESSORS_ONLN [14:55] apw: yep [14:56] apw: it only affects local builds. [14:57] ok cool [15:00] apw: please update bug #300803 with the revert notice. [15:00] Malone bug 300803 in linux "linux-libc-dev: please include video/uvesafb.h" [Medium,Fix committed] https://launchpad.net/bugs/300803 [15:00] doh, yep [15:01] lieb: please write the SRU justification for bug #281647 [15:01] Malone bug 281647 in linux "Support IR remote for MSI TV Anywhere Plus tuner card" [Low,In progress] https://launchpad.net/bugs/281647 === lamont` is now known as lamont [15:13] rtg bug update done [15:36] dh_installchangelogs -plinux-image-2.6.28-3-server [15:36] parsechangelog/debian: error: found trailer where expected start of change data, at file debian/changelog line 4 [15:36] dh_installchangelogs: changelog parse failure [15:37] whats the problem? [15:38] also i got this error before: [15:38] fatal: ambiguous argument 'Ubuntu-2.6.28-3.4..HEAD': unknown revision or path not in the working tree. [15:38] Use '--' to separate paths from revisions [15:47] looks like you are missing some tags? [15:48] where are you building this tree? [16:11] well yes [16:11] but now i rebuild 2.6.27 tree [16:12] btw. i adopted my 2.6.27 patch for ubuntu studio 17 to 2.6.28, just a very small diff [16:12] err dell studio of course [16:13] http://kanotix.com/files/kernel/unused-patches/2.6.27.9-patch_sigmatel_dell_studio_17.diff [16:13] http://kanotix.com/files/kernel/unused-patches/2.6.28-rc9-patch_sigmatel_dell_studio_17.diff [16:14] first is for intrepid the other for jaunty git [16:18] Kano, and those have been confirmed to work on the hardware? [16:19] Kano, Also, did you send the patch upstream as Luis suggested? [16:19] well the first, for the 2nd i have to compile the kernel [16:19] smb_tp: i sent it to the suse guy, the first one [16:19] a previous owner of a Studio 1837 (i assume its one of those as they had the same ids) claimed that selecting that model didn't work for them [16:19] he said he will add it [16:20] Kano, Ok, thats cool. Makes it simpler for the sru process [16:20] apw: maybe that studio 18 has also + 1 in the id? [16:20] no that was a typo on my part, its a 1737 [16:20] stupid fingers [16:21] well he just played with the mixer and heard something [16:21] with this setting [16:22] rtg, wrt sru, will do [16:22] lieb: I already did for that bug 'cause it was holding the upload [16:22] i could not confirm teh 2.6.28 patch [16:23] but as soon as i can compile the 2.6.28 git this should be no real problem to do so [16:23] ok. I''l go back and check what I missed [16:23] lieb: its best to write the SRU justification right after you commit the patch. [16:24] Might even make sense to do it concurrent with the mail. The text can just be the same [16:26] did somebody test nfs with 2.6.28 yet? [16:36] Kano, is there a bug associated with your studio 1737 patches yet? [16:36] not that i know, it is only a kanotix not ubuntu user with that laptop [16:37] maybe there is a ubuntu user with it too? [16:37] under bug #309512 we have a user with the same laptop [16:37] Malone bug 309512 in alsa-driver "Dell Studio 17 (1737), 2 headphones jack do not work in Intrepid 8.10" [Undecided,New] https://launchpad.net/bugs/309512 [16:37] who i have been talking who claims to have tried enabling that speciifc quirk via [16:37] options snd-hda-intel model=dell-m6 and failed to get sound [16:38] your patch enabled that same quirk, so wondering about the testing, one of the testers must be wrong [16:38] hopefully ours [16:38] well maybe he did not play with the mixer settings? [16:38] that is entirly possible [16:39] perhaps you could attach your patch to that bug? [16:41] Right, we have to have the patch attached to a bug anyways and this one seems to match perfect. [16:42] ok, will add the 2.6.27 patch there, as it is for 8.10 [16:42] Kano, Ok, thanks [16:43] perfect [16:44] attached it [18:26] could somebody change the insertchanges targe that it does not insert anything when no changes are made? [18:56] rtg, I checked on that SRU and I did write one but the subject line was "PATCH SRU LP...." which probably choked in mail filters. I take it "SRU" should be the first token? [18:57] lieb: are you talking about the SRU justification comment in the LP report? [18:57] ye [18:57] yep [18:57] did I just miss it? [18:57] remind what the bug number is [18:57] probably because of the "PATCH" [18:59] PATCH SRU Bug #281647 Add support for MSI TV@nywhere Plus remote [18:59] Malone bug 281647 in linux "Support IR remote for MSI TV Anywhere Plus tuner card" [Low,Fix committed] https://launchpad.net/bugs/281647 [19:00] lieb: uh, I'm talking about the SRU justification clause in the LP report. While the bug might have been ACK's on the mailling list, we still need to tell the SRU folks what we're doing. [19:01] an entry in launchpad? [19:02] lieb: https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/281647/comments/8 [19:02] Malone bug 281647 in linux "Support IR remote for MSI TV Anywhere Plus tuner card" [Low,Fix committed] [19:04] ok, I cna do that. you were pulling from my repo so which git url do I put in there? [19:05] I was wondering how I tie off my end once I push it up to my repo. these things are hanging about... [19:06] lieb: well, don't write the SRU justification until _after_ the commit has been made to the core repo, then use the URL from gitweb to point at the core repo. [19:07] ok. so I wait for your "pulled" reply and go to LP and write this up. correct? [19:07] lieb: yep [19:08] and thats pretty much the tie-ff as far as you are concerned. [19:08] I cna do that. pls add the commit sha in your "pulled" so I cna find it [19:08] s/ff/off/ [19:09] lieb: do you know the gitweb URL ? your commit will generally be near the top of the listing of the particular repo. [19:09] http://kernel.ubuntu.com/git [19:10] I'll work it out. If you had the commit sha, I know it's really in as opposed being in your queue. think memory barrier ;) [19:11] lieb: oh no, when I respond via email that its been pulled, that means I've really committed it to the core repo. [19:11] ok gotcha [19:12] I'll update the kernel bug wiki with this bit. [19:51] my local build died w/ "ABI file missing" on a schroot 32 bit build. what Fu am I missing? [19:51] amd64 builds worked just fine in same git workspace [19:59] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/309268 [19:59] Malone bug 309268 in linux "[regression] nfs-kernel-server fails with 2.6.28 (dup-of: 306016)" [High,Triaged] [19:59] Malone bug 306016 in nfs-utils "nfs client broken since 2.6.28-2-generic upgrade" [High,Confirmed] [20:00] it seems somoebody reported that problem alredy [20:12] Kano: what would you have it do if there are no changes? [20:13] well somebody has nfs working,but he did not enable all options [20:13] on my other pc i have got his kernel config [20:13] Kano: I mean insertchanges [20:14] well it cleaned the changelog completely and then no package could be created [20:14] it was just empty, no * at all [20:25] Kano: I know what it does...what would you expect it to do is my question [20:26] BenC: just do nothing [20:27] then i could leave it enabled in my script and it would never break [20:27] Kano: then the builds will still fail [20:27] nope, with the placeholder it compiles [20:27] then don't run insertchanges [20:28] well then i need a check for that... [20:28] I want it to fail if there are no changes [20:28] sure, as long as the changelog is untouched [20:44] Kano: write a patch...the current behavior works for our purposes [21:33] BenC, are you here ? [21:33] mjg59, you too ? [21:34] dade`: yeah