/srv/irclogs.ubuntu.com/2010/08/27/#ubuntu-kernel.txt

ogasawarajjohansen: could you help take a look at bug 62491500:14
ubot2Launchpad 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/62491500:14
RAOFogasawara: Yeah, those (or specifically the intel ones) are the patches I'm thinking of.00:23
ogasawaraRAOF: 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
ogasawaraRAOF: 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 reapplied00:24
ogasawara?00:24
ogasawaraor just the intel ones?00:26
RAOFAll the intel ones, certainly; we've given up on them working properly.00:26
RAOF(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
ogasawaraRAOF: do you want the radeon ones too just for good measure?00:27
RAOFThis is where I want an inverse-launchpad.00:28
RAOFWhere I can go and see “hey, everyone with a ES1000 is doing fine” :/00:28
jjohansenogasawara: sure00:29
ogasawarajjohansen: thanks00:29
ogasawaraRAOF: 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:30
RAOFogasawara: 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
ogasawaraRAOF: hrm, so maybe we still leave that patch out then00:31
RAOFYeah.  Keep an eye on it, but leave it out for now.00:32
ogasawaraRAOF: ack00:32
=== jjohansen is now known as jj-afk
jj-afkback on later01:32
=== 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
* amitk smiles at GregKH poking fun at Ubuntu's colors: http://lwn.net/Articles/402328/rss12:07
lamontFound Xen hypervisor 3.2,  kernel: /boot/vmlinuz-2.6.24-28-xen.dpkg-tmp13:06
lamontgiggle13:06
* smb is not sure he wants to know how that happened13:07
lamontit went away before the end of the package install13:09
lamontthat was just apt-get dist-upgrade13:09
smbAh, then I guess I can relax again :)13:09
lamontwell, it probably shouldn't notice .dpkg-* kernels13:10
smbMaybe, 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:12
lamontcorrect13:13
lamontboc?13:13
smbbeer o clock13:13
lamontbeer on13:13
smbnot yet13:14
smbAbout 3hrs away, though13:14
=== ivoks is now known as ivoks_away
tseliotmjg59: 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:30
tseliotmjg59: 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)14:32
=== sconklin-gone is now known as sconklin
=== bjf[afk] is now known as bjf
rafael_n_azevedogood morning15:13
rafael_n_azevedoi'd like to know if i compile a kernel vanilla i will lose something ?15:14
rafael_n_azevedobecause i'm using lucid n i'd like to compile it15:16
bjfrafael_n_azevedo: if you get the right sources and build correctly you shouldn't "lose" anything  https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel15:23
bjfrafael_n_azevedo: why do you want to build your own kernel?15:23
rafael_n_azevedojust to compile it on my laptop to "run better"15:24
rafael_n_azevedoor u think isn't necessary15:24
bjfrafael_n_azevedo: that implies that you are going to change something and that you know what to change to make it "run better"15:24
bjfrafael_n_azevedo: i don't think it's necessary15:25
rafael_n_azevedothe realy thing it that i would like to learn it 15:26
rafael_n_azevedoto learn to compile a kernel15:26
bjfrafael_n_azevedo: well, see the link i posted above and give it a shot15:27
rafael_n_azevedook thanks a lot15:27
=== ivoks_away is now known as ivoks
ogasawaraGrueMaster: hiya, thanks for jumping in here, just wanted to inquire about bug 60548815:44
ubot2Launchpad 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/60548815:44
ogasawaraGrueMaster: seems like the original conditions (ie swap enabled) to trigger the bug are not the same with the latest images15:45
ogasawaraGrueMaster, lag: do either of you know if swap will be re-enabled in later images?15:45
GrueMasterUnfortunately we haven't had a properly working image since Alpha 3 to test this.15:45
ogasawaraGrueMaster: ah15:45
GrueMasterAnd ogra would know more about whether or not swap will be reenabled.15:46
ogasawaraGrueMaster: for now then I'm going to leave the bug open for tracking purposes.15:46
ograi only disabled it because of the existing bugs15:46
ograbut it appears nobody can reproduce it anymore15:47
GrueMasterI'm pulling today's images.  If I can get them to work somewhat, I will reenable swap and test this.15:47
ogasawaraogra: 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:47
ograclose it and lets see if it comes up again ... we can always re-open15:48
ogasawaraogra: ack, thanks15:48
ogasawaraGrueMaster: if it re-appears after your testing, re-open the bug.15:48
GrueMasterok15:48
* smb is out18:36
=== ivoks is now known as ivoks_away
=== simar__mohaar is now known as simar
=== ivoks_away is now known as ivoks
* ogasawara lunch19:44
=== ivoks is now known as ivoks_away
MarkKohlerI'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?21:48
=== bjf is now known as bjf[afk]
=== sconklin is now known as sconklin-gone
nUboon2Age__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:15
nUboon2Age__JFo-swap: we're listening to "Cooking by the Book".. Jono shared it w/ us23:20
[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 such23:48
ubot2Launchpad 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/55409923:48
[reed]should I have only pulled a specific package or something?23:48
[reed]or what exactly23:49

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!