=== _human_blip_away [n=mike@220.157.65.29] has joined #ubuntu-kernel === doko_ [n=doko@dslb-088-073-124-011.pools.arcor-ip.net] has joined #ubuntu-kernel === Lure [n=lure@ubuntu/member/lure] has joined #ubuntu-kernel === Lure [n=lure@ubuntu/member/lure] has joined #ubuntu-kernel === johanbr [n=j@d154-20-238-192.bchsia.telus.net] has joined #ubuntu-kernel === BenC [n=bcollins@debian/developer/bcollins] has joined #ubuntu-kernel === zul_ [n=chuck@CPE0006258ec6c1-CM000a73655d0e.cpe.net.cable.rogers.com] has joined #ubuntu-kernel === BenC [n=bcollins@debian/developer/bcollins] has joined #ubuntu-kernel === gnomefreak [n=gnomefre@adsl-221-4-111.rmo.bellsouth.net] has joined #ubuntu-kernel === peeps [n=peeps@cpe-70-112-25-110.austin.res.rr.com] has joined #ubuntu-kernel === Lure [n=lure@ubuntu/member/lure] has joined #ubuntu-kernel === peeps [n=peeps@cpe-70-112-25-110.austin.res.rr.com] has joined #ubuntu-kernel === _human_blip_away [n=mike@220.157.65.29] has joined #ubuntu-kernel === Lure [n=lure@ubuntu/member/lure] has joined #ubuntu-kernel [08:40] BenC: linux-source ftbfs on all arches. === ivoks [n=ivoks@ubuntu/member/ivoks] has joined #ubuntu-kernel === peeps [n=peeps@cpe-70-112-25-110.austin.res.rr.com] has joined #ubuntu-kernel === Lure [n=lure@BSN-77-135-17.dsl.siol.net] has joined #ubuntu-kernel === crispin [n=crispin@grotto.flowerday.cx] has joined #ubuntu-kernel === Keybuk [n=scott@quest.netsplit.com] has joined #ubuntu-kernel [12:48] BenC: ping... poke me when you're around. === _human_blip_away [n=mike@220.157.65.29] has joined #ubuntu-kernel === BenC [n=bcollins@debian/developer/bcollins] has joined #ubuntu-kernel === zul [n=chuck@CPE0006258ec6c1-CM000a73655d0e.cpe.net.cable.rogers.com] has joined #ubuntu-kernel [02:12] infinity: blah [02:13] BenC: Waking up? [02:13] wow === BenC sees build failures galore === pitti [n=pitti@ubuntu/member/pitti] has joined #ubuntu-kernel [02:14] BenC: A few linux-libc-dev related ones, which I'm trying to sort whose fault they are. [02:14] hi [02:14] BenC: pitti's got one for you, and then I'll take my turn. :) [02:15] well all of l-s-2.6.17 failed too, so I'm checking that as well :) [02:15] Yeah, but if another upload's required, we may as well wait and see if the headers need fixing first. :) [02:20] BenC: Ping me when you're done pondering pitti's bug. [02:21] ok, I'm working on that one now [02:21] BenC: you agree that unaligned.h is legitimate for userspace? [02:22] pitti: Not sure yet [02:23] pitti: I'm going to have to say no [02:24] hey Ben [02:24] BenC: i assigned a few FTBFS to you since they involve mixture of kernel and userland headers (during a mass filing) [02:24] BenC: if it's a big time issue for you to work on them, i am sure pitti will love to help you :) [02:24] BenC: ok; any idea how programs can do an unaligned read/write in a platform independent manner? [02:25] pitti: main reason is that sparc64 uses asm-generic/unaligned.h and that can't be in userspace [02:25] pitti: Are there programs other than reiserfsprogs that try to do this? [02:25] BenC: not to my knowledge, but I can't really say [02:25] BenC: we have to check the other FTBFSes [02:26] pitti: Isn't there some gcc or glibc defined way of doing this already? === _human_blip_ [n=mike@220.157.65.29] has joined #ubuntu-kernel [02:27] I mean, if it's such a common thing, I would think that there is a more "official" method [02:27] BenC: (making a clueless face) [02:28] Amazingly, I can picture that face. [02:30] pitti: From what I can tell, accessing unaligned data is not a problem, and get_unaligned/put_unaligned is only important for some architectures to improve performance a bit [02:31] and from what I can tell, that's only the case for sparc64 for us [02:31] the other arch's, the macros are pretty much (foo) and (foo = bar) [02:31] BenC: it's definitively not a problem on x86/amd64, but I wasn't sure whether some arches would spill SIGBUSes for that [02:32] BenC: and on sparc64? will it work, just slowly? or sigbus? [02:36] I could just remove reiserfsprogs from the archive and solve the problem that way. [02:36] :P === pitti will fix it once he knows whether or not it will break sparc64 [02:39] pitti: It should not...come to think of it, using asm-* in userspace is pointless for a few reasons, but mainly because it says nothing about the actual cpu you are running on [02:40] ppc -> ppc64, sparc ->sparc64, i386 -> x86_64 [02:40] ok [02:40] BenC: ok, I'll fix that the naive way then; thank you! [02:40] (bug updated and rejected for l-s-2.6.17 [02:40] ) [02:40] pitti: I would just copy the macros from i386 unaligned.h and plug those in instead of the asm/unaligned.h include [02:41] yeah, I did something similar [02:41] the code already had such a fallback for powerpc [02:41] I just made that non-ppc-specific [02:41] BenC: My turn? :) [02:41] shoot :) [02:42] http://librarian.launchpad.net/4822044/buildlog_ubuntu-edgy-i386.directfb_0.9.24-4ubuntu2_FAILEDTOBUILD.txt.gz [02:42] Now, I'm not entirely sure how this could possibly build WITHOUT agpgart.h, so I'm curious if you need to mangle agpgart.h to be userspace-friendly, or if I should be pulling all the symbols from agpgart.h into directfb (ugh) === pitti [n=pitti@ubuntu/member/pitti] has left #ubuntu-kernel ["Bye"] [02:48] infinity: icky...that just looks like newer agp API [02:49] BenC: Any urge to take this one off my hands and make it build on amd64/i386? I got it building on all other arches (yes, the package had at least 4 different FTBFS bugs) [02:49] infinity: I can give it a go === ph8 [i=henri@85.234.155.95] has joined #ubuntu-kernel [02:49] BenC: Once I start diving into kernel/userspace separation, I get a bit hazy as to whose bug is whose (kernel, headers, app) [02:50] infinity: This is basically a "directfb is too old" bug [02:51] That doesn't shock. The bitrot can't be too bad, though. :/ === _human_blip_ [n=mike@220.157.65.29] has joined #ubuntu-kernel === kbyrd [n=Miranda@mailout1.vmware.com] has joined #ubuntu-kernel === stuart__ [n=stuart@209.67.233.220.exetel.com.au] has joined #ubuntu-kernel === tuxmaniac [n=aanjhan@unaffiliated/tuxmaniac] has joined #ubuntu-kernel === ..[topic/#ubuntu-kernel:BenC] : Ubuntu kernel development discussion ONLY | Kernel GIT tree info (updated): https://wiki.ubuntu.com/KernelGitGuide | 2.6.17-10.33 uploaded. Most likely the final edgy kernel | Daily kernel builds (for debug and testing purposes only) http://people.ubuntu.com/~bcollins/kernels-daily/ | Kernel Wiki: https://wiki.ubuntu.com/CategoryKernel | KernelFreeze in effect === gnomefreak [n=gnomefre@ubuntu/member/gnomefreak] has joined #ubuntu-kernel === gnomefreak [n=gnomefre@ubuntu/member/gnomefreak] has joined #ubuntu-kernel === nixternal [n=nixterna@ubuntu/member/nixternal] has joined #ubuntu-kernel [06:17] [17180132.352000] APIC error on CPU0: 01(01) [06:18] ever since tuesday, i switched to the -generic kernel, and now i get those [06:18] i had this with the k7 kernel previously, and when i went back to the 386 kernel, the problem went away [06:28] nixternal: Try booting with noapic [06:29] it won't [06:29] nixternal: Then I suggest for now sticking with the -386 kernel [06:29] hehe, i am ;) [06:29] nixternal: File a bug and attach dmesg (or digital photo) of the problem boot without "quiet splash" [06:30] just wanted to know if anyone knew of this..i didn't even see a bug for it..so i am filing one...also, you research the error on google, they say defective hardware, which i doubt that is the issue [06:30] a little info on your hardware too [06:30] no problem [06:30] nixternal: I don't doubt that it could be buggy or defective hardware, but it could be something that can be worked around [06:31] it is top knotch stuff here ;) [06:31] however, im pointing towards memory if it is an issue though [06:31] i think i noticed it with a 1gb stick installation [06:32] first [06:40] nixternal: New doesn't mean "not broken" :) [06:41] nixternal: You may want to check on a BIOS update as well [06:44] hehe, believe me i know. this is a kt333 mobo, i think they stopped with bios hacks years back...need to find out if there are any custom ones out there though [06:53] BenC: the noapic option actually didn't lock the machine up like it had before. and it seems to have fixed something else i had an issue with on startx kicking in kdm in automatically, don't know if htey are tied in, but thats my story and im sticking to it [06:54] however,t he error is still there ;( === jwest- [n=jwest@unaffiliated/jwest/x-422957] has joined #ubuntu-kernel === nixternal [n=nixterna@ubuntu/member/nixternal] has left #ubuntu-kernel ["New] === peeps [n=peeps@cpe-70-112-25-110.austin.res.rr.com] has joined #ubuntu-kernel [08:17] zul: hmm, you said that xen git was up-to-date now? [08:17] zul: is that the git://dev.laptop.org/projects/ubuntu-xen repo or some other? [08:29] ubuntu-xen-2.6.17 [08:30] cloning now. [08:31] any idea when we'll have working xrm? [08:31] when the headers are fixed again [08:31] any idea when that happens? :-P [08:31] this weekend probably :) [08:31] ok === johanbr [n=j@jupiter.physics.ubc.ca] has joined #ubuntu-kernel === ph8 [n=ph8@85-210-62-111.dsl.pipex.com] has joined #ubuntu-kernel === zul_ [n=chuck@CPE0006258ec6c1-CM000a73655d0e.cpe.net.cable.rogers.com] has joined #ubuntu-kernel === gnomefreak [n=gnomefre@ubuntu/member/gnomefreak] has joined #ubuntu-kernel === gnomefreak [n=gnomefre@ubuntu/member/gnomefreak] has joined #ubuntu-kernel