[00:14] jjohansen: could you help take a look at bug 624915 [00:14] Launchpad bug 624915 in linux (Ubuntu Maverick) (and 3 other projects) "maverick kvm guests not seeing virtio disks (affects: 1) (heat: 6)" [High,Confirmed] https://launchpad.net/bugs/624915 [00:23] ogasawara: Yeah, those (or specifically the intel ones) are the patches I'm thinking of. [00:24] RAOF: I've been trying to find the irc logs to back up what I remember, but I've been unsuccessful. Basically what I "recall" is that we purposely didn't carry those kms-disablement patches forward to Maverick as they appeared to be a temporary work around at the time and we were hoping to see a proper fix in Maverick. [00:24] RAOF: Obviously if that's not the case I'm can reapply them to Maverick. Just let me know. And I assume you'd want all 6 patches reapplied [00:24] ? [00:26] or just the intel ones? [00:26] All the intel ones, certainly; we've given up on them working properly. [00:27] (For Maverick, at least. Maybe, *maybe* the “throw a flock of writes at the GTT and wait untill they stick” patch will be in Natty's kernel) [00:27] RAOF: do you want the radeon ones too just for good measure? [00:28] This is where I want an inverse-launchpad. [00:28] Where I can go and see “hey, everyone with a ES1000 is doing fine” :/ [00:29] ogasawara: sure [00:29] jjohansen: thanks [00:30] RAOF: I can get these applied no problem. we are in beta freeze though so the actual upload will have to wait till post beta. we can add a beta release note though. [00:31] ogasawara: So, I haven't found any new bugs on the ES 1000 for Maverick. Maybe that means kms is working for it now. [00:31] RAOF: hrm, so maybe we still leave that patch out then [00:32] Yeah. Keep an eye on it, but leave it out for now. [00:32] RAOF: ack === jjohansen is now known as jj-afk [01:32] back on later === amitk is now known as amitk-afk === fddfoo is now known as fdd === amitk-afk is now known as amitk === yofel_ is now known as yofel === amitk is now known as amitk-afk === amitk-afk is now known as amitk === ivoks_away is now known as ivoks [12:07] * amitk smiles at GregKH poking fun at Ubuntu's colors: http://lwn.net/Articles/402328/rss [13:06] Found Xen hypervisor 3.2, kernel: /boot/vmlinuz-2.6.24-28-xen.dpkg-tmp [13:06] giggle [13:07] * smb is not sure he wants to know how that happened [13:09] it went away before the end of the package install [13:09] that was just apt-get dist-upgrade [13:09] Ah, then I guess I can relax again :) [13:10] well, it probably shouldn't notice .dpkg-* kernels [13:12] Maybe, but it would be a update-grub problem which is nothing I need to immediately worry. At least not enough to cause a Friday boc delay. [13:13] correct [13:13] boc? [13:13] beer o clock [13:13] beer on [13:14] not yet [13:14] About 3hrs away, though === ivoks is now known as ivoks_away [14:30] mjg59: do you know if there are any additional power savings that we could do with radeon and RS880 (e.g. in the Northbridge) so as to make laptops run cooler? (The RS780 guides on AMD's website should also be relevant for the RS880) [14:32] mjg59: I'm using kernel 2.6.35 (and I've also tried some patches to disable plls for display controllers that are not in use, without heat reduction though) === sconklin-gone is now known as sconklin === bjf[afk] is now known as bjf [15:13] good morning [15:14] i'd like to know if i compile a kernel vanilla i will lose something ? [15:16] because i'm using lucid n i'd like to compile it [15:23] rafael_n_azevedo: if you get the right sources and build correctly you shouldn't "lose" anything https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel [15:23] rafael_n_azevedo: why do you want to build your own kernel? [15:24] just to compile it on my laptop to "run better" [15:24] or u think isn't necessary [15:24] rafael_n_azevedo: that implies that you are going to change something and that you know what to change to make it "run better" [15:25] rafael_n_azevedo: i don't think it's necessary [15:26] the realy thing it that i would like to learn it [15:26] to learn to compile a kernel [15:27] rafael_n_azevedo: well, see the link i posted above and give it a shot [15:27] ok thanks a lot === ivoks_away is now known as ivoks [15:44] GrueMaster: hiya, thanks for jumping in here, just wanted to inquire about bug 605488 [15:44] Launchpad bug 605488 in linux-ti-omap4 (Ubuntu Maverick) (and 1 other project) "BUG: scheduling while atomic: mmcqd/46/0x00000002 (affects: 2) (heat: 12)" [High,In progress] https://launchpad.net/bugs/605488 [15:45] GrueMaster: seems like the original conditions (ie swap enabled) to trigger the bug are not the same with the latest images [15:45] GrueMaster, lag: do either of you know if swap will be re-enabled in later images? [15:45] Unfortunately we haven't had a properly working image since Alpha 3 to test this. [15:45] GrueMaster: ah [15:46] And ogra would know more about whether or not swap will be reenabled. [15:46] GrueMaster: for now then I'm going to leave the bug open for tracking purposes. [15:46] i only disabled it because of the existing bugs [15:47] but it appears nobody can reproduce it anymore [15:47] I'm pulling today's images. If I can get them to work somewhat, I will reenable swap and test this. [15:47] ogra: so would you consider if ok to close the bug for now? or would you rather we leave it open into better testing can be done. [15:48] close it and lets see if it comes up again ... we can always re-open [15:48] ogra: ack, thanks [15:48] GrueMaster: if it re-appears after your testing, re-open the bug. [15:48] ok [18:36] * smb is out === ivoks is now known as ivoks_away === simar__mohaar is now known as simar === ivoks_away is now known as ivoks [19:44] * ogasawara lunch === ivoks is now known as ivoks_away [21:48] I'm tracking down a mostly repeatable crash in ath5k, but when I switched from the Lucid kernel to the packaged mainline kernel, I stopped getting crash dumps. Any ideas on why that would be, or how I can get crash dumps with the mainline kernel? === bjf is now known as bjf[afk] === sconklin is now known as sconklin-gone [23:15] I'm having trouble with trying to run 2.6.32-24. I get "Error: cannot read the Linux header.. error: you need to lead the kernel first. Failed to boot both default and fallback entries. Press any key to continue." If i press a key it just gives the same error. I'm with Jono at a Global Jam and he recommended you all might be of help. [23:20] JFo-swap: we're listening to "Cooking by the Book".. Jono shared it w/ us [23:48] <[reed]> I'm trying to get the packages from bug 554099 for lucid, but I'm having a hard time. I added ppa:kernel-ppa/pre-proposed, but now I'm getting errors complaining about symbol module_layout version disagreement and such [23:48] Launchpad bug 554099 in linux-backports-modules-2.6.32 (Ubuntu Maverick) (and 9 other projects) "Qualcomm Gobi 2000 3G (gobi_loader/qcserial) broken (affects: 56) (dups: 4) (heat: 341)" [Undecided,Invalid] https://launchpad.net/bugs/554099 [23:48] <[reed]> should I have only pulled a specific package or something? [23:49] <[reed]> or what exactly