[12:43] <BenC> it's sad that the 2x550Mhz A500 can compile faster than the 2x800Mhz i2k
[12:43] <BenC> the A500 is on it's third kernel while the i2k is still working on the first
[01:20] <BenC> jbailey: ping
[01:27] <jbailey> BenC: pong
[01:28] <BenC> jbailey: talked to benh, and got some things squared away...so I expect 2.6.15-6.8 to work for you
[01:28] <BenC> rtc and fan problem
[01:28] <jbailey> Ooo!
[01:28] <jbailey> What was it?
[01:29] <BenC> CONFIG_RTC => CONFIG_GEN_RTC (change in ppc for 2.6.15), since we are using the wrong rtc module
[01:29] <BenC> and for the cpu, therm_pm72 needs to be loaded
[01:29] <jbailey> Is that the generic timekeeping patch I saw on lkml a couple weeks ago?
[01:29] <jbailey> 'k.  Should therm_pm72 be loaded in the initramfs then, I guess, sam as fan.ko is on acpi systems?
[01:29] <BenC> nah
[01:30] <BenC> well, in breezy it was built-in
[01:30] <BenC> so I am going to do that for least-surprise reasons
[01:30] <jbailey> Hmm.
[01:30] <BenC> almost every G5 needs it
[01:30] <jbailey> I'm a strong fan of get-it-out-of-the-kernel.
[01:31] <BenC> without it, you get the "vaccum cleaner mode" as benh put it :)
[01:31] <jbailey> The initramfs has to handle it for laptops anyway.  Keybuk's laptop gets about 20 seconds before it overheats otherwise.
[01:31] <BenC> so in this case, since 99% of the users of this kernel will need it, I think it's best to put it in
[01:31] <BenC> yeah, but every laptop is different in someway, isn't it?
[01:32] <jbailey> Soudns like a trick question. =)
[01:32] <BenC> or is that general acpi?
[01:32] <BenC> yeah, it was a little tricky :)
[01:32] <jbailey> General acpi.
[01:33] <jbailey> In the init-premount hook, we have a scrip that just does:
[01:33] <jbailey> modprobe -q fan
[01:33] <jbailey> modprobe -q thermal
[01:33] <jbailey> It's be simple enough to just add therm_pm72 into there, too.
[01:35] <jbailey> FWIW, should I also test reboot and try to load the fan module to be sure on that one? =)
[01:35] <jbailey> My glibc build is almost done.
[01:35] <BenC> yeah, that would be good
[02:12] <jbailey> BenC: I'm giving it a moment for the fans to get going so that I can clearly hear tht they've stopped after.
[02:12] <BenC> ok
[02:12] <BenC> therm_p72 should be the module
[02:12] <jbailey> They're usually doing pretty good by about 4 minutes.
[02:13] <jbailey> yup, that does it. =)
[02:13] <BenC> fixed it?
[02:14] <jbailey> Yup
[02:14] <BenC> sweet, thanks!
[02:14] <jbailey> Are you going to build it in, or should I upload initramfs-tools with a fix?
[02:15] <jbailey> The other option is that you can link it in /lib/modules/${VER}/initrd
[02:15] <jbailey> initramfs honours those too.
[02:15] <jbailey> But I'd rather see those go away.
[02:17] <infinity> BENC LIED TO ME.
[02:18] <BenC> infinity: I'm about 30 minutes from an upload
[02:18] <infinity> (h is fair, given the number of times I've lied to him..)
[02:18] <infinity> s/(h/(Which/
[02:18] <BenC> jbailey: if you could upload it, it would give me more time to get -6.8 out :)
[02:18] <jbailey> Sure, but since infinity's here..
[02:19] <BenC> I didn't expect to take this long, had to back out and redo some patches for parisc at the last moment
[02:19] <jbailey> infinity: You planning an upload in the  next couple of minutes for initramfs-tools anyway?
[02:19] <BenC> yeah, infinity, initramfs-tools needs to load therm_pm72 for powerpc fans :)
[02:19] <jbailey> infinity: I was thinking of just stuffing it in scripts/init-premount/acpi =)
[02:19] <BenC> it's strictly a ppc64 thing
[02:20] <jbailey> Maybe rename it to heat
[02:20] <jbailey> We can have ikeaesque names.
[02:21] <jbailey> BenC: Are you still using all the space on concordia?
[02:21] <jbailey> It would probably be handy for me to try this build there, although the changes  are sufficiently non-invasive that I'm not worried about a multi-arch test right now.
[02:22] <BenC> I should be empty on there...let me do a clean
[02:23] <jbailey> Thanks/
[02:24] <BenC> ok, 6.6G free
[02:32] <infinity> If we want IKEA names, I should make it nonsensical, like scripts/init-premount/jerker or something.
[02:32] <infinity> "jerker is the name of my desk... I may have purchased it just for that reason)
[02:33] <infinity> s/"/(/
[02:34] <mkrufky> BenC: are you 1394 maintainer?
[02:36] <jbailey> Didn't Jody take that over?
[02:36] <infinity> Okay, I see two names in scrollback.  Is the module therm_pm72 or therm_p72
[02:36] <infinity> ?
[02:36] <jbailey> $ lsmod |grep therm
[02:36] <jbailey> therm_pm72             36856  0
[02:39] <infinity> I just uploaded.
[02:39] <jbailey> infinity: Hey, in terms of testsuites..  Right now I only test the glibc that I absoluely know can be run on every class of machine that might build it.  (Like I run ppc tests, but not ppc64.  However, all our buildds are i686 at least, so I run i386 and i686 tests).  Is it worth putting a hack in there to try and detect if the buildd is actually capable of running a particular test and enabling it?
[02:40] <jbailey> infinity: Or would you rather that builds be more deterministic than that?
[02:40] <infinity> Well, the more tests, the merrier.
[02:40] <infinity> Our buildds are all ppc64, fwiw.
[02:41] <infinity> I want deterministic BUILDS, but deterministic testsuites don't seem quite as crucial.  Testing based on detection of the metal you're currently running on doesn't seem so horrible.
[02:42] <jbailey> 'k.  I'll think about that for the next round of retooling, then.
[02:43] <jbailey> I'm going to actually start checking for regression in the testsuite instead of merely logging what failed, so it's a good time to think about this. =)
[02:44] <BenC> mkrufky: technically, but I don't really do much with it anymore
[02:52] <mkrufky> BenC: gotcha.... i only ask because stoth described an obscure 1394 problem to me, i thought u might be interested
[02:52] <mkrufky> i directed him to #linux1394
[02:53] <BenC> ok
[03:18] <jbailey> BenC: I'm afk for about 1h for dinner and hanging out with Angie.  I'll be back after to finish my glibc upload and stuff.  If there's anything you need me to do (test reboots, etc.) I can do them then.
[03:19] <BenC> ok
[03:22] <infinity> I wonder if I should be a do-gooder and make ltmodem build again, too.
[03:48] <jbailey> woohoo, all the testsuites passed.
[04:00] <jbailey> Is it expected that the new udev HW detection doesn't seem to find my nic?
[04:01] <jbailey> BenC: I think that the kernel should fail the install if update-initramfs fails.  When replacing current modules, there's a reasonable risk that if it fails that you have an unbootble system.
[04:01] <BenC> right now, it fails in postinst if update-initramfs returns an error
[04:02] <jbailey> Hmm.
[04:02] <jbailey> So update-initramfs needs to return an error then, I guess. =)
[04:02] <jbailey> I ha to revert to an old kernel and do a takeover.
[04:02] <BenC> it does already
[04:02] <jbailey> It did not as of about 10 minutes ago.
[04:03] <BenC> atleast it did when I tried installing with an existing initrd there
[04:03] <jbailey> The -5.7 that's in the archive.
[04:03] <BenC> hmm
[04:03] <BenC> the -5.7 you got from me wont
[04:03] <BenC> the one in the archive _should_
[04:03] <jbailey> It gave me the message saying that couldn't overwrite it, and then appeared to continue succesfully.
[04:03] <BenC> oh, weird
[04:03] <jbailey> I was replacing the -5.7 I got from you with the one in the archive.
[04:03] <jbailey> So maybe some sort of weird issue with replacing the current version?
[04:06] <jbailey> Dear infinity:  It's lovely that you've modprobed the thermal module, please also actually include it in the initramfs, kthxbye.
[04:07] <infinity> Dear jbailey: stop making requests before I've woken up.
[04:07] <jbailey> I've seen no evidence that you sleep.
[04:08] <jbailey> infinity: Would you like me to upload an actually tested version? =)
[04:11] <infinity> A version tested by someone with a ppc64 machine?... That's a novel idea.
[04:13] <jbailey> glibc is now officially in the "worksforme" category, up she goes.
[04:14] <BenC> infinity: -6.8 in T-Minus 1 minute
[04:15] <jbailey> Ahaha, sweet.  glibc and the kernel on the buildds.
[04:15] <jbailey> QUICK!  SOMEONE UPLOAD X!
[04:15] <BenC> and gcc :)
[04:17] <BenC> done
[04:17] <BenC> jbailey: did I beat your glibc upload?
[04:18] <BenC> well, the cron will run at the same time, guess linux-source-2.6.15 will become victim to glibc only because of the silly alphabet
[04:19] <BenC> infinity: *pomp* the ball's in your court now :)
[04:21] <infinity> No one will be anyone's victim, there's more than one buildd per arch. :)
[04:24] <jbailey> Well.  Here's hoping that particular crash was random and not my fault.
[04:24] <jbailey> Xorg spun out.
[04:40] <jbailey> g'n Ben.
[04:43] <BenC> jbailey: any chance you got glibc tested on sparc?
[04:43] <BenC> did you do any major updates to it?
[04:43] <jbailey> BenC: I tested it before the last round of changes, but those worked on ppc, i386 and amd64 so I'm expecting it to build everywhere.
[04:43] <BenC> debian's glibc just got broken for the 64-bit build, and I want to make sure we don't do the same :)
[04:43] <jbailey> I didn't get nptl on sparc64 working
[04:43] <jbailey> Nah, I actually test my changes.
[04:43] <jbailey> The NMU was poorly timed and lartable there.
[04:44] <jbailey> Although if I could still have access to your machine at some point.  Backporting on a sparc5 is really sucking rocks. =)
[04:45] <BenC> is TLS enabled for sparc?
[04:45] <BenC> lol, yeah, after this weekend, I can give out accounts for usage
[04:46] <jbailey> TLS and NPTL are on sparcv9 and sparcv9b
[04:46] <BenC> what about 64-bit?
[04:46] <jbailey> I gave it compiling on sparc64, but segfaulting in the linker. =)
[04:46] <jbailey> So I stuck with LT for this upload and did the minimal fix to get it building again.
[04:47] <BenC> cool
[04:48] <BenC> keep 64-bit the same until fabbione or I hear different from davem, he says TLS is broken on 64-bit
[04:48] <jb770> Roar
[04:49] <jb770> This machine seems to crash out x now
[04:49] <jb770> No idea yet which change is doing it. :(
[05:46] <jbailey_> BenC: So far no X hang when I revert to 2.6.12.  Dunno if that's the new udev or the new kernel though.
[05:46] <jbailey_> (-5.7)
[06:22] <infinity> BenC : Any plans to resurrect acx_pci?
[06:22] <fabbione> hey jbailey_
[07:30] <infinity> jbailey_ : Hahah.  Was that meant to be a subtle joke, or were you having editor woes? :)
[07:31] <infinity> jbailey_ : (initramfs...ubuntu3 has a debian/changelog.dch.save with a different changelog entry than debian/changelog..)
[10:45] <CataEnry> hi all
[11:00] <CataEnry> bye :)
[01:29] <jbailey__> infinity: *Lol*  I had been originally going to use that as the quote, and decided that I didn't feel that antagonistic.  Then X crashed on me. =)
[01:32] <BenC> jbailey__: are you running -6.8 now?
[01:32] <BenC> fabbione: ping
[01:32] <fabbione> BenC: pong
[01:33] <BenC> fabbione: -6.8 build on sparc yet?
[01:34] <fabbione> it's in the queue after perl and glibc
[01:34] <fabbione> it will take sometime to get there
[01:34] <jbailey> BenC: No, still -5.7
[01:34] <jbailey> Actually.
[01:34] <jbailey> Hmm
[01:34] <jbailey> No, I'm running 2.6.12 so that my session will stay running.
[01:34] <jbailey> I'll try -6.8 in a moment.
[01:34] <BenC> damnit, I knew glibc would slow me down :)
[01:35] <fabbione> BenC: glibc will also unleash modular X on sparc, for which we don't have sparc specific drivers
[01:36] <fabbione> later guys
[01:44] <BenC> fabbione: later
[01:45] <jbailey> BenC: Should I try -6.8 and see if it eats my machine?
[01:45] <BenC> yes, please
[01:45] <BenC> and reenable hwclock too, if you could
[02:15] <BenC> wow, I have malone bugs
[02:19] <jbailey> Yeah, the upshot of having two bug tracking systems is that people use both of them.  *sigh*
[02:29] <infinity> Most of my Malone bugs have been pretty simple wishlists so far, so I haven't minded.
[02:29] <infinity> Which is good, cause Malone and I don't get alone yet.
[02:30] <infinity> a/alone/along/
[02:36] <BenC> infinity: I think Malone will show _you_ a good time, since you're the one that has to "Submit" :)
[02:41] <infinity> BenC : I'm off to bed, lrm is waiting in binary NEW.  When elmo gets around to processing it, feel free to do the linux-meta ABI bump again (perhaps confirm with Kamion first that it won't screw his d-i mangling/testing)
[02:42] <BenC> ok
[02:42] <infinity> Though at this point in the game, where d-i gets screwed every 5 minutes by some random uploa,d he'll probably say "just do it".
[02:42] <BenC> is udev done?
[02:42] <infinity> Define "done".
[02:42] <BenC> uploaded
[02:42] <infinity> It's been uploaded several times.  It half works, and is half broken.
[02:43] <infinity> Yeah, it was uploaded ages ago, and linut-meta was already uploaded for 2.6.15-5... YOu missed that? :)
[02:43] <infinity> (mdz made the order, despite powerpc being broken)
[02:43] <BenC> no, I saw that
[02:43] <BenC> oh, I had missed that
[02:43] <infinity> So, yeah.  -meta just needs another bump for -6... When LRM gets out of NEW.
[02:44] <BenC> ok
[02:44] <infinity> I probably have 2 or 3 more "real" LRM uploads to do this cycle, but the rest I'm going to leave to you.
[02:45] <infinity> If you want to grab the source and look at the top of debian/rules, you'll see where it automagically figures out kernel versions and such.  ABI dumps are now a matter of changing one integer in debian/rules and adding a changelog entry.  Same as with linux-meta.
[02:45] <BenC> linux-meta needs a dh compat bump
[02:45] <infinity> And this concludes me signing off on "make sure Ben's up to speed on being able to update LRM"
[02:45] <BenC> sweet
[02:46] <BenC> later :)
[02:57] <CataEnry> hi all
[03:08] <jbailey> BenC: I'm on the new kernel, cat'ing that file works, hwclock works.
[03:08] <jbailey> My fans are behaving with the new initramfs-tools
[03:09] <jbailey> Now just need to see if X dies on me again. =)
[03:11] <BenC> nice
[03:18] <jbailey> Well, 10 minutes of idle didn't kill it.
[03:32] <jbailey> 'nother 10 minutes under steady usage, no prob.
[03:32] <jbailey> The only other thing I can think of it to surf a couple dozen pr0n pages to test the image cache.
[03:32] <CataEnry> bye
[03:37] <BenC> beat it into submission
[03:37] <BenC> let it know who's boss :)
[03:43] <jbailey> Right
[03:43] <jbailey> pr0n it is then. =)
[03:58] <zul> heylo
[04:06] <BenC> hey zul
[04:07] <jbailey> Zool!
[04:08] <jbailey> BenC: I just passed an hour of uptime.  glibc build going in a window, lots of email, web surfing, openning/closing terminals, etc.
[04:08] <jbailey> It didn't make it 10 minutes before like this, so I think that -6.8 also solves that.  I think we can stamp ppc64 as gold.
[04:08] <BenC> excellent! thanks
[04:25] <zul> must...do...kernel...work...tonight
[04:27] <jbailey770> Benc: x just died on me.  Anything  i can check before i reboot ?
[04:30] <CataEnry> hi all
[04:34] <BenC> jbailey: not sure
[04:35] <BenC> jbailey: any processes in D state?
[04:36] <BenC> jbailey: dmesg, "ps axuwww", send me those if you can
[04:36] <BenC> if any processes are in d-state, send me "cat /proc/<pid>/wchan" aswell
[04:37] <jbailey770> K
[04:38] <jbailey770> BenC: i think i narrowed it down a bitmto when im typing alot.
[04:39] <jbailey770> I don't see anything  in d state.
[04:41] <jbailey770> Ok to reboot  now?
[04:41] <BenC> yeah
[04:41] <BenC> X freezing, mouse still works, I'm wondering if this is a hal problem
[04:42] <BenC> sounds like some bug reports I've heard about concerning hal
[04:44] <jbailey770> Well mouse is usually hwcursor isn't it?
[04:45] <jbailey770> Kill -9 of x gets the rest of the system happy again .
[04:47] <jbailey> BenC: Fired off the email.
[04:47] <BenC> thanks
[04:48] <jbailey> New udev, I'll load that.
[04:49] <jbailey> BenC: When I look at when it's failed, it's been when I was editting a long changelog entry, doing lots of typing, writing emails, or writing things in RT.
[04:50] <jbailey> All primarily kbd based.
[04:51] <BenC> nothing in the process list sticks out, so I can only assume that it's the kernel that starts killing the load
[04:52] <BenC> all the processes are in sleep except X, so it something in the xserver directly
[04:52] <BenC> X definitely isn't waiting on something (else it would be in sleep too)
[04:53] <BenC> hard to say who is at fault
[04:53] <BenC> wish I had asked you to kill X, and try restarting it, but you can try that later when you have some time
[04:53] <BenC> oh, nm
[04:53] <BenC> I see you did that :)
[04:53] <jbailey> I'm still in 2.6.15, so it's going to recur at some point. =)
[04:53] <jbailey> Well, I didn't try restarting X.
[04:54] <jbailey> I typed, reboot, realised that it was going to take forever to do that, and did a kill -9 of X.
[04:54] <jbailey> It rebooted a moment or two after. =)
[04:54] <BenC> try "ctrl+alt+backspace" next time if you can, to see if it will restart X by itself
[04:55] <jbailey> I'd tried that before, it doesn't work.
[04:55] <jbailey> No keyboard input seems to have any effect, I cannot change VTs.
[04:55] <jbailey> Although, I could try a chvt from the ssh session.
[05:06] <BenC> ok
[05:13] <infinity> Everyone ignore the linux-meta upload I just did.  It wasn't me.  I'm asleep.
[05:13] <infinity> That is all.
[05:20] <infinity> Oh, also.
[05:21] <infinity> BenC : Misdirected complaint...
 infinity: linux-doc-2.6.15 conflict/overwrites linux-doc-2.6.12
[05:21] <BenC> yeah, got a bug report already
[05:43] <fs> fabbione: ping
[05:59] <trevilor> hi guys
[07:31] <jbailey_> Hmm, actually had a real kernel crash that time.
[07:31] <jbailey_> BenC: No idea what from, nothing in the logs.  I got out of the shower to a machine with the fans going full tilt and not answering pings or ssh
[07:33] <jbailey_> BenC: Do you have a -6.8 kernel done with gcc-3.4 at all?  I wonder if that would make a difference.
[08:56] <fabbione> fs: pong?
[08:57] <fs> fabbione: hi =)
[08:57] <fabbione> fs: hey dude
[08:58] <fabbione> i don't have much time now.. we have a meeting in 3 minutes or so
[08:58] <fabbione> what can i do for you my friend?
[08:58] <fs> fabbione: do you remember by chance what the amd64-int3-fix.patch in linux-2.6 was for?
[08:58] <fs> it was added in 2.6.10 along with another couple of patches which where all merged upstream, just this one not
[08:58] <fabbione> fs: hmm i think i saw it in the Debian kernel, but i did never look at it
[08:59] <fabbione> or was it in our kernel?
[08:59] <fs> ok thanks =)
[08:59] <fs> I think it was in both
[08:59] <fs> thus the question
[08:59] <fabbione> i am checking
[09:00] <fabbione> as soon as my raid will resume from sleep
[09:00] <fabbione> and somebody will explain me why my disks went to sleep
[09:00] <fs> btw, do you have a current rediffed version of drivers-scsi-megaraid_splitup.patch or was it dropped from ubuntu kernel too?
[09:00] <fabbione> fs: it's in git
[09:00] <fs> heh, asleep raid disks?
[09:00] <fabbione> on my workstation
[09:00] <fabbione> scary
[09:01] <fs> indeed :)
[09:01] <fabbione> i just upgraded to 15-rc3
[09:01] <fabbione> fs: what does the patch patch?
[09:01] <fabbione> i don't see anything like that in my patch list
[09:01] <fabbione> perhaps a different name?
[09:01] <fs> the megaraid one? it lists you as the author =)
[09:02] <fs> it splits pci ids from newgen and legacy megaraid drivers, so both can be compiled
[09:02] <fabbione> no sorry i am talking about the amd64 one
[09:02] <fs> the legacy supports a few old cards the newgen one does not
[09:02] <fabbione> i know about the megaraid
[09:03] <CataEnry> bye all
[09:03] <fs> oh, it adds 2 lines to a case DIE_INT3 in arch/x86_64/kernel/kprobes.c
[09:03] <fabbione> it's debian specific
[09:03] <fs> I dropped it for 2.6.14, and it caused no harm so far
[09:03] <fabbione> lsdiff -H * |grep kprobes
[09:03] <fs> I just wonder
[09:03] <fabbione> null
[09:04] <fs> ok, then I'll remove it
[09:04] <fabbione> eheh
[09:04] <fs> thanks man =)
[09:04] <fabbione> no problem dude
[09:04] <fabbione> any time
[09:07] <makx> fs: should be fixed since 2.6.12
[09:07] <makx> -> http://www.ussg.iu.edu/hypermail/linux/kernel/0503.3/1974.html
[09:07] <mdz> BenC: #ubuntu-meeting
[09:11] <fs> makx: looks good, thank you =)
[09:11] <makx> fs: no thank you dude for going 2.6.15.
[09:41] <BenC> mdz: already there
[09:58] <fabbione> BenC: we might not even need or want to merge them, if the packages we have work fine
[09:59] <BenC> I was thinking that too
[09:59] <fabbione> we probably want to look at possible kernel-wedge bug fixes
[09:59] <fabbione> but kernel-package has been taking a direction that we might have problems with
[09:59] <BenC> yeah, it's been broken up into "module" scripts
[09:59] <fabbione> yes
[09:59] <fabbione> we can for sure give it a shot
[09:59] <fs> interesting how the ubuntu kernel build infrastructure has grown completely different than the debian one
[10:00] <BenC> fs: git pushed us into a different direction
[10:00] <fs> fabbione: I searched around in git, you don't have a debian/patches dir anymore? is the megaraid driver split implemented directly in drivers/scsi/megaraid?
[10:00] <fabbione> fs: what ben sais :)
[10:00] <fabbione> fs: yes. it's in a git commit
[10:00] <fs> yeah, looks pretty interesting =)
[10:01] <BenC> fs: yes, "git-whatchanged <file>"
[10:01] <fs> especially building the udebs from the same source
[10:01] <fabbione> fs: that will never be accepted in Debian
[10:01] <fabbione> i had that discussion already on debian-boot
[10:01] <fabbione> when the 2 build systems were closer
[10:01] <fs> well then, I guess I have to checkout the whole thing
[10:02] <fabbione> fs: yes...
[10:02] <fs> fabbione: we had the discussion again a week ago, it soon went a highly emotional way
[10:03] <fabbione> fs: i am not surprised :)
[10:03] <fs> maybe if someone makes a decent proposal with some working code, it will be accepted
[10:04] <fabbione> fs: the code was working... and it still does
[10:04] <fabbione> it kinda needs to be updated to your new build system
[10:04] <fabbione> we still use it :)
[10:05] <fabbione> fs: in regards of keeping 2 different build system i think it's good
[10:05] <fabbione> fs: we keep developing different bits merging/splitting/remerging and so on
[10:06] <fabbione> fs: if you look at the history..
[10:06] <fabbione> we started with the same build system done by herbert
[10:06] <fabbione> we landed in 2 different places
[10:06] <fs> yeah
[10:07] <fabbione> debian did push later (after sarge) in a similar directions that we did already explore here
[10:07] <fabbione> (build all from one source)
[10:07] <fabbione> using a different and probably more clean implementation
[10:07] <fabbione> on my suggestion and discussion with others
[10:07] <fabbione> Debian did the config. file split/allignement
[10:07] <fabbione> that now we are partially pulling back
[10:07] <fabbione> so even if the code is not exactly the same
[10:07] <fabbione> we rely on the same concepts
[10:08] <fabbione> and we are both improving by a bit of competition
[10:08] <zul> who is doing what now?
[10:08] <fabbione> that imho is very good
[10:08] <fabbione> zul: what?
[10:08] <zul> what are you guys on about?
[10:08] <fabbione> Debian <-> Ubuntu kernel build system sync
[10:09] <zul> ah ok..
[10:09] <fabbione> fs: personally i believe we did achieve a lot working this way.. probably more than sharing the same code
[10:09] <makx> fs: not convinced. ;)
[10:09] <makx> ehh upps fabbione. :)
[10:10] <fs> I guess I need to track your development much closer ;)
[10:39] <zul> you can start with our git tree ;)
[10:43] <lamont__> BenC: linux-source-2.6.15 needs to Depend: gcc-3.4 on architectures using 3.4...
[10:43] <lamont__> more to the point, linux-source-2.6.12 has this issue, and causes some ftbfs pain
[10:43] <BenC> only one I know of is hppa
[10:43] <BenC> which is does
[10:44] <BenC> *it
[10:44] <lamont__> see http://buildd.mmjgroup.com/buildLogs/c/cpqarrayd/2.2-1/cpqarrayd_2.2-1_20051129-1652-hppa-failed.gz
[10:45] <lamont__> and the last (sparc) build in the same directory
[10:45] <BenC> linux-source-2.6.15 the .deb, you mean?
[10:45] <lamont__> --> linux-source-2.6.12 has a bug
[10:45] <lamont__> yes.
[10:45] <lamont__> the deb
[10:45] <lamont__> needs to Depends: $THERIGHTGCC
[10:46] <BenC> ok, that should only affect hppa
[10:46] <lamont__> uh... sparc cpqarrayd has the same failure....
[10:46] <lamont__> gcc-3.4: command not found
[10:47] <lamont__> ISTR 2.6.12 was all built with gcc-3.4
[10:47] <BenC> sparc builds with gcc-4, unless fabbione is forcing something
[10:47] <fabbione> no i don't force anything
[10:47] <lamont__> cpqarrayd build-depends: linux-source-2.6.12
[10:47] <lamont__> so that probably needs to change to -2.6.15
[10:47] <BenC> yeah
[10:48] <BenC> crappy, I can't do build-dep like arch depends :)
[10:57] <fabbione> mjg59: ping?
[11:03] <lamont__> BenC: nope... have to gen them into existance
[11:04] <dilinger> fabbione: have you got anyone using amd64-k8-smp on dual opterons?
[11:04] <dilinger> er, for breezy that is
[11:04] <fabbione> dilinger: no idea, why?
[11:04] <fabbione> are you going to send me for testing?
[11:05] <fabbione> actually
[11:05] <dilinger> hehe
[11:05] <fabbione> Mithrandir does run that stuff
[11:05] <dilinger> my machine blows up spectacularly w/ smp
[11:05] <fabbione> Linux rho 2.6.12-9-amd64-k8-smp #1 SMP Mon Oct 10 13:18:18 BST 2005 x86_64 GNU/Linux
[11:05] <fabbione> there
[11:05] <fabbione> it works great here
[11:05] <fabbione> up to make -j1000 on the kernel
[11:05] <fabbione> no OOPS or anything
[11:06] <fabbione> tested on heavy load for about 3 days
[11:06] <fabbione> it's a 2xdual core amd64...
[11:07] <fabbione> dilinger: fix your hw :)
[11:07] <Mithrandir> dilinger: I do, why?
[11:07] <Mithrandir> on like five different boxes.
[11:07] <Mithrandir> some dualcore, some just SMP
[11:09] <dilinger> fabbione: haha, thanks!
[11:09] <dilinger> it looks like it oops when it switches into framebuffer
[11:09] <dilinger> so maybe it's a video card thing
[11:09] <Mithrandir> blacklist the fb module?
[11:12] <dilinger> is the fb module actually in the initramfs?
[11:12] <Mithrandir> no idea
[11:12] <Mithrandir> it probably is
[11:12] <Mithrandir> remove "splash"?
[11:12] <dilinger> i already removed splash and quiet
[11:12] <Mithrandir> but, I'm off to bed.
[11:12] <dilinger> 'night
[11:14] <dilinger> oh man
[11:15] <dilinger> the initramfs stuff is *so* much easier to understand..
[11:15] <makx> s/rote/torte/ # local cake
[11:19] <dilinger> meh
[11:19] <dilinger> i can't actually tell what's going on here
[11:19] <dilinger> and my serial cable is in nyc
[11:19] <dilinger> damnit
[11:20] <dilinger> oh well, guess i'll go UP for now
[11:20] <dilinger> i give 2.6.15 a try, if i get bored