[01:34] <TheMuso> bjf[afk]: I think we have a problem with alsa daily snapshots and missing/unknown symbols for both lucid and maverick. Had some users report bugs where they are using daily build packages, and no sound devices are found. Dmesg shows symbols not being found. I'm going to see what I can find out.
[01:35] <TheMuso> bjf[afk]: I can reproduce on maverick, and about to do a lucid install on some hardware to attempt to reproduce there to be 100% sure.
[07:28] <TheMuso> bjf[afk]: Seems that some symbols are undefined at link time for some modules. I'll try and track this down some more tomorrow, not in a mental state atm to work out where to go from here, and dig hrough more autotools foo for alsa-driver...
[12:53] <avinashhm> hi, any one familiar with this ??? "fs_initcall(inet_init);" .. i commented this and my linux isn't booting ... its running on an SOC ..
[13:02] <smb> avinashhm, It adds inet_init to the functions called when the system boots. There are various stages of this and fs_initcall ususally initializes filesystem related modules.
[13:03] <avinashhm> smb, i dont need inet_init ... its something related to network .... So thought of remvonig it ... Is it very necessary for the system to run or we can remove ???
[13:06] <avinashhm> It does something before last login time ... 
[13:06] <avinashhm> init: ureadahead main process (524) terminated with status 5
[13:06] <avinashhm> -->
[13:06] <avinashhm> Last login: Sun Jan  2 04:34:55 CET 2000 on tty1
[13:06] <smb> Are you really sure you don't need it if you cannot boot after you remove it? Don't know where this is and whether maybe other people would not be happy about removing it. Also keep in mind that loopback is network, too and it is neaded.
[13:07] <avinashhm> So after removing the initcall, it hangs at the arrow marked point ... 
[13:08] <avinashhm> I am testing it on an SOC ... We observe once in about 2 hours, it crashes in a fucntion rt_worker_func ...
[13:08] <avinashhm> This function is in route.c ...So we thought we ll remove network related and removed the initcall ...
[13:09] <avinashhm> smb, Whats loopback ?? 
[13:09] <smb> lo0 the network device that represents the localhost
[13:09] <smb> and a lot of things use it
[13:10] <smb> I cannot really help with details but I think removing that initcall sounds like a bad idea
[13:11] <avinashhm> oh .. .:-( .... seems like i can't get rid of it ...
[13:11] <RAOF> smb: Sorry for not getting back to you re: those radeon patches; I've replied now.
[13:12] <avinashhm> smb, thanks .. for the replies ... I ll try to have initcall and look what else i can do ... thanks again
[13:13] <smb> RAOF, He is alive! ;) Ok, thanks, I'll have a look
[13:13] <RAOF> smb: Sorry; traveling from Toulouse to Hobart takes me through any number of un-wifi'd airport terminals.
[13:13] <smb> avinashhm, no problem and good luck
[13:14] <RAOF> And leaves me ~110% asleep.
[13:14] <RAOF> :)
[13:14] <smb> RAOF, Why do you need to live on the other half of the world. :)
[13:15] <RAOF> Because I'm much cooler than you.  I live in the future, damnit!
[13:15] <RAOF> Spending 36 hours to travel anywhere is surely a small price to pay to live in the future :P
[13:18] <smb> RAOF, d-; ˙əɹnʇnɟ ʎɯ sɐ sıɥʇ ƃuıʇdəɔɔɐ ɯoɹɟ ʇuəsəɹ ı
[13:18] <RAOF> :)
[13:19] <smb> RAOF, Though I must admit its a good pickup line: "I come from the future and must warn you..." :)
[13:19] <RAOF> Heh.
[13:20] <smb> So the answer seems to be we can take the patches or not. Whatever we want. So I guess if its ok well try with them
[13:20] <RAOF> They seem to make sense, yes.
[13:22] <smb> Ok, thanks a lot. Then we can go on to have them included in your world (the future, usually even more into it than you could ever live)
[13:56] <avinashhm> smb, how did you do that .. pasted invert :-) ...nice
[13:57] <smb> avinashhm, Used an upside down generator on the web and pasted the result. :)
[13:59] <avinashhm> smb, )-: əuo əɔıu ʎəɥ
[15:42] <bjf> tgardner: fly to the other side of the world to have a public holiday? :-) (how are things going?)
[15:45] <tgardner> bjf, s'okay. its hot here though.
[15:46] <tgardner> really hot.
[17:37] <jjohansen> ogasawara: how soon do you want the AA patches?  I have them but I am still working on updating regression testing
[17:40] <ogasawara> jjohansen: definitely no hurry as they likely won't get uploaded until after the 10.10 official release.  So maybe just get them to the list by beginning-mid next week or earlier if you want.
[17:41] <jjohansen> ogasawara: earlier, I just want to make sure they are thoroughly tested
[17:41] <ogasawara> jjohansen: ack
[17:55] <vanhoof> hello friends :)
[17:55] <vanhoof> im willing to buy someone a beer if they can build me a kernel on a machine with actual power :)
[17:56] <ogasawara> vanhoof: I can kick a build off for you
[17:56] <ogasawara> vanhoof: what's the patch you need and what arch?
[17:56] <vanhoof> ogasawara: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=e259befd9013e212648c3bd4f6f1fbf92d0dd51d
[17:56] <vanhoof> ogasawara: amd64
[17:56] <vanhoof> ogasawara: on top of the latest mav kernel
[17:56] <ogasawara> vanhoof: ack, gimme a few minutes and I'll get it going
[17:56] <vanhoof> ogasawara: \o/ thank you
[17:56] <vanhoof> last time it took me 4 hours to build :D
[17:57] <ogasawara> yuck
[17:58] <bjf> vanhoof: you need tgardner to give you access to tangerine
[17:58]  * vanhoof is down for that
[17:58] <vanhoof> I don't need to build often, but when i do i cringe
[18:03] <ogasawara> smb, sconklin, bjf: EtienneG is inquiring about bug 554569
[18:03] <ubot2> Launchpad bug 554569 in gentoo (and 6 other projects) "[lucid] Blank screen with KMS on Thinkpad X201 with Arrandale (i915) (affects: 43) (dups: 1) (heat: 300)" [Unknown,Fix released] https://launchpad.net/bugs/554569
[18:03] <ogasawara> [10:00:37] <ogasawara> EtienneG: no worries, anything you need me to ping them about?
[18:03] <ogasawara> [10:01:02] <EtienneG> ogasawara, yes, status of bug #554569 in lucid
[18:03] <ogasawara> [10:01:18] <EtienneG> it is marked fix Commited, and milestoned for 10.04.2
[18:03] <ogasawara> [10:01:38] <EtienneG> i was wondering if the patch will appear in an SRU earlier than 10.04.2
[18:03] <ogasawara> [10:01:53] <EtienneG> and if yes, approx ETA for that
[18:03] <vanhoof> heh
[18:03] <vanhoof> its sitting in -proposed
[18:04] <vanhoof> its been bumped twice by security
[18:04] <ogasawara> I always love the ETA questions
[18:04] <smb> yeah
[18:04] <smb> eta somewhen
[18:04] <ogasawara> heh
[18:04] <vanhoof> that bug has a special place in my heart
[18:11] <bjf> vanhoof: it really hasn't been bumped by security, the clock has not been reset on it really
[18:12] <bjf> vanhoof: it's just that that patchset was so large the sru team wanted to let it bake a while
[18:12] <smb> on the status page yes, but that should not matter that much. it also suffered from not really many people doing verification on their bugs
[18:14] <vanhoof> bjf: well it has been once at least
[18:14] <vanhoof> bjf: how has the clock not been reset?  it went from ~18 to 3 last i checked?
[18:15] <smb> vanhoof, Yes but that probably can be argued with the sru team
[18:15] <vanhoof> do you say that since the bugs that has been verified stayed verified?
[18:15] <smb> we know it has been out longer
[18:15] <smb> Yes, the verification tags do not get reset
[18:17] <vanhoof> ah ok
[18:23] <lamont> why does the maverick kernel have a 25GB footprint on the build machine?
[18:24] <kees> lamont: lots of flavor?
[18:24] <lamont> 23GB in lucid, 14GB in karmic
[18:24] <lamont> kees: and a build process that doesn't believe in /bin/rm
[18:24] <smb> and each compiled with debug info which is only stripped on packaging
[18:24] <lamont> well, lucid fails to build on most of our ppa builders, and maverick will only be worse
[18:26] <smb> Hm, I was not aware that there are problems with it
[18:26] <ogasawara> vanhoof: I'm seeing build failures with that patch, gimme a sec to see if I can get it fixed up
[18:26] <lamont> it helps even less that when it fails, it sometimes decides to just loop
[18:27] <lamont> and what I'll assert is likely the second largest package in the archvie (openoffice.org) has a build footprint of a "mere" 6.5GB
[18:29] <vanhoof> ogasawara: cool, i hope its not too much trouble
[18:29] <lamont> smb: sounds like time for me to file a bug, I guess
[18:30] <smb> lamont, most if that footprint really is that the compile stage is done with full debug symbols. Maybe it would be possible to clean between flavour builds, but I am not sure. Yes, if that needs to change I guess a bug will remind us to...
[18:31] <lamont> ta
[18:47] <vanhoof> wow, my tv viewing just got screwed up pretty bad for the next few months :\
[18:47] <vanhoof> "For Thu: Ghost Whisperer: Season 1: Disc 1"
[18:48] <vanhoof> ... I sure didnt put that in queue, I bet I know what's coming after that
[19:03] <ogasawara> vanhoof: are you testing this kernel yourself or giving to someone else to test?
[19:03] <vanhoof> ogasawara: myself
[19:03] <vanhoof> ogasawara: and Sarvatt 
[19:04] <ogasawara> vanhoof: so I forgot to tweak the version, but I can change that and rebuild, will be about 10 more min
[19:25] <vanhoof> ogasawara: cool, thank you very much!
[19:27] <ogasawara> vanhoof: http://people.canonical.com/~ogasawara/test-build/vanhoof/
[19:27] <Sarvatt> vanhoof: it may not be just that patch :( 20100921 resumes with a garbled display, 20100922 is fine
[19:28] <Sarvatt> thanks ogasawara! testing now
[19:30] <vanhoof> was on the phone
[19:30]  * vanhoof grabs kernel
[19:30] <vanhoof> Sarvatt: i tried 22, and did not resume at all
[19:31] <vanhoof> i guess we'll know here in a second :D
[19:31] <Sarvatt> yeah, 0921 comes up at least but its garbled and 0922 with it works right and it doesn't come up at all on maverick
[19:32] <vanhoof> Sarvatt: https://bugs.freedesktop.org/show_bug.cgi?id=29631
[19:33] <ubot2> Freedesktop bug 29631 in DRM/Intel "[Huron River] Resume does not work on HR CRB (resume screen corruption issue)." [Normal,Resolved: fixed]
[19:33] <vanhoof> which i found from https://bugs.freedesktop.org/show_bug.cgi?id=30199
[19:33] <ubot2> Freedesktop bug 30199 in DRM/Intel "[Huron River] render corruption after S3 resume (with tiling)" [Major,Resolved: fixed]
[19:36] <Lollipop56> hi there
[19:37] <Lollipop56> I was wondering why Ubuntu doesn't allow software to auto-update itself instead of working with PPAs, Ubuntu uses the Linux kernel whereas OSX uses the Darwin kernel. Now, both are stable, if not Linux is even more stable, so why??
[20:32] <scrllock2> anyone know if this kernel: http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.36-rc5-maverick/  has been patched for the recent root exploit? (http://www.ubuntu.com/usn/usn-988-1)
[20:37] <ogasawara> scrllock2: all the patches for CVE-2010-3081 and CVE-1020-3301 should be upstream as of 2.6.36-rc5
[20:37] <ubot2> ogasawara: ** RESERVED ** This candidate has been reserved by an organization or individual that will use it when announcing a new security problem.  When the candidate has been publicized, the details for this candidate will be provided. (http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-3081)
[20:38] <scrllock2> ogasawara: thank you very much.
[20:39] <jjohansen> -> Lunch
[21:01] <rsalveti> argh, sometimes I'm getting a weird issue with my radeon card at my thinkpad t400
[21:02] <rsalveti> my monitor suspends after a while, and when I try to wake him up sometimes the display just goes blank
[21:02] <rsalveti> X turns dead, but I still get console
[21:02] <rsalveti> and at my kernel log: [90595.959747] [drm:drm_mode_getfb] *ERROR* invalid framebuffer id
[21:03] <rsalveti> doesn't happen all the time
[21:03] <rsalveti> with current maverick
[23:31] <lfaraone> ogasawara: btw, what was changed in linux-meta 2.6.35.22.23 that casued the ABI bump? the changelog gives me no hints.
[23:33] <ogasawara> lfaraone: nothing in the linux-meta package changed, but the linux package required an ABI bump which resulted in the ABI bump for linux-meta
[23:33] <lfaraone> oops, I should have looked at "linux".
[23:35] <lfaraone> background: after upgrading today, resume-from-suspend stopped working, and disabling nvidia drivers didn't help. I'm thinking of rolling back to 21 to see if that was the cause.