* abogani waves all07:17
* apw yawns07:19
RAOFTime for the bees!07:19
=== smb` is now known as smb
* apw giggle insanly07:20
smbapw, Has there been back in 20mins mentioned?07:20
apwsadly not07:21
* smb wonders what made apw loose control. :)07:22
apwits just going to me one of those days07:22
aboganiogasawara: ping07:23
RAOFBah.  Bluetooth, why do you suck so?07:23
apwppisati, ok seems i've pushed an update to lucid master-next which should sort you out07:45
apwno idea why i didn't think it applied to lucid07:45
=== ikonia_ is now known as ikonia
ppisatiapw: cool, btw disabling that driver fixed the compilation09:10
ppisatiapw: when available, can you open CVE-2010-4805? thanks09:16
ubot2ppisati: The socket implementation in net/core/sock.c in the Linux kernel before 2.6.35 does not properly manage a backlog of received packets, which allows remote attackers to cause a denial of service by sending a large amount of network traffic, related to the sk_add_backlog function and the sk_rmem_alloc socket field.  NOTE: this vulnerability exists because of an incomplete fix for CVE-2010-4251. (http://cve.mitre.org/cgi-bin/cvename.c09:16
* ppisati -> out for food10:52
* apw lunche12:30
hertonsmb: natty is failing on QA for -virtual flavour, because CONFIG_DEBUG_RODATA is disabled for it (bug 802464)12:49
ubot2Launchpad bug 802464 in linux "linux: 2.6.38-10.46 -proposed tracker" [Medium,In progress] https://launchpad.net/bugs/80246412:49
hertonsmb: we don't remember now if it was you which was going submit a patch for it, as it was reported before, but I can do it in any case12:50
smbherton, wtf. Thanks, though I would have thought that Natty should not be able to get built without...12:50
smbThe last one it was not would have been hardy12:51
hertonah... ok, natty seems to require the same fix then12:51
smbI thought we had that in the big mean config checker, but I need to have a look at that12:51
tgardnersmb, its in the enforcer, but looks like virtual is excluded12:52
* smb wonders whether there was a case where that broke ec212:53
tgardnerherton, why is that failing now ?12:53
smbtgardner, Guess because now we are really really testing12:53
* smb will have a look and see whether it can be turned on and still boots on ec212:53
hertonit seems we got this reported in June, but was forgotten (https://lists.ubuntu.com/archives/ubuntu-kernel-sru/2011-June/000158.html)12:54
tgardnersmb, in the meantime I suggest we get an exception so it doesn't hold up everything else. its not like its a regression.12:54
tgardnerherton, ^^12:55
hertontgardner: yep, I agree12:55
smbherton, tgardner I think the problem should now be fixed through stable but we deliberately have been disabling that for i386 (see 0b111980fe515c5ab24bf21aca5aebd24c70f605)13:01
smbBut I'll better get it tested to be sure13:02
tgardnersmb, herton: so an exception should be acceptable since we made the change with malice aforethought.13:03
apwppisati: did someone do this for you: CVE-2010-480513:03
ubot2apw: The socket implementation in net/core/sock.c in the Linux kernel before 2.6.35 does not properly manage a backlog of received packets, which allows remote attackers to cause a denial of service by sending a large amount of network traffic, related to the sk_add_backlog function and the sk_rmem_alloc socket field.  NOTE: this vulnerability exists because of an incomplete fix for CVE-2010-4251. (http://cve.mitre.org/cgi-bin/cvename.cgi?n13:03
* smb has not13:04
hertonyes, +1 on that, it isn't a regression from the released natty kernel13:04
* ogasawara drowns in email13:04
tgardnerogasawara should never take vacation again13:05
ogasawaraI miss anything exciting?13:05
* apw votes for ogasawara to not have any too13:05
smb...ctrl-a del13:05
apwogasawara: na things went ok for the milestone13:06
ogasawaraapw: I thought you'd pushed over the top of linux-meta to drop versatile?13:08
apwogasawara: i did i thought  /me checks13:09
* tgardner defers UDS registration until August in case the dates change again.13:09
apwogasawara: i think its on master-next13:09
apwi think we need to shift that back13:10
apwogasawara: let me look maybe i've bust it13:11
tgardnerapw, you should drop an example of MSS clamping in that IPv6 wiki page.13:12
apwtgardner: will do ...13:12
ogasawaraapw: yep, looks like it's on master-next.  I'll get master updated.13:13
apwogasawara: yeah i think its time to lose master-next13:13
apw(from meta)13:13
ogasawaraapw: yah, I'll drop that branch too13:14
ogasawaraapw: I assume you have the commit for 3.0.0-5.6 for linux-meta in your tree then?  care to just push that to master?13:16
apwppisati: https://bugs.launchpad.net/bugs/80931813:17
ubot2Ubuntu bug 809318 in linux-ti-omap4 "CVE-2010-4805" [Undecided,New]13:17
ogasawaraapw: nm, looks like it's tgardner who's got it13:17
apwogasawara: ok ... get him to shove13:17
tgardnerogasawara, what am I shoving? apw did the last meta upload.13:18
ogasawaratgardner: am trying to find the commit which closed out linux-meta for 3.0.0-5.613:19
ppisatiapw: 10x13:20
tgardnerogasawara, well, I don't think anyone has done it yet. 5.6 isn't finished building.13:20
apwppisati: i am going to assume thats positive13:20
ogasawaratgardner: ack, you're right13:22
tgardnerogasawara, I just got it uploaded about 10P your time.13:22
ogasawaraI'll keep an eye on the builds and then get linux-meta uploaded/updated 13:23
tgardnerogasawara, I've nothing unpushed in my natty-meta repo, so feel free to hack and slash13:24
=== manjo` is now known as manjo
tgardnerbjf, given that you are the resident python expert, how about reviewing sforshee's patch lest he become discouraged? https://lists.ubuntu.com/archives/kernel-team/2011-July/016142.html14:26
bjftgardner, roger, roger14:27
sforsheetgardner, bjf: at this point it doesn't seem to matter much since we've switched back to 3 numbers in the version14:27
apwi recon we should fix them anyhow14:30
sforsheeit would be simpler if we could assume a '-' between the upstream version and the ABI, but right now it looks for '.' or '-'. I assume that's for legacy reasons?14:31
apwsforshee, per14:32
aboganiogasawara: ping14:32
apwsforshee, perhaps for meta as well14:32
apwwhich uses the . . . . form14:32
sforsheeI see14:32
ogasawaraogasawara: pong14:32
ogasawaraabogani: pong14:32
* apw giggles at ogasawara14:32
smbone of those days...14:33
aboganiogasawara: Could you renew me in bugcontrol, please?14:33
ogasawaraabogani: sure, just a sec14:33
aboganiogasawara: Thank you 14:34
ogasawaraabogani: done, renewed for another year14:34
aboganiogasawara: Thanks again 14:35
bjfsforshee, yes the '.' is to support meta14:44
bjf## Ubuntu Kernel Team Meeting - Today @ 17:00 UTC - #ubuntu-meeting14:45
bjf##      agenda: https://wiki.ubuntu.com/KernelTeam/Meeting14:45
apwbjf, again, so soon ?14:45
bjfapw, we could go to once a month, no-one would notice14:46
=== chrisccoulson_ is now known as chr1sccoulson
ogasawaraapw: aside from the 3.0.0-5.6 upload, anything else happen I should mention in the meeting?15:03
apwogasawara, no i don't think so, we were all quiet.  of course you should mention 3.0.0 change15:04
ogasawaraapw: right, will add that15:04
apwsconklin, i see a lot of our master-nexts have not 15:10
apwbeen rebased, its making the pre-proposed kernels come out with funny old version numbers15:10
tgardnerapw, we can fix that15:11
tgardnerthe rebase, I mean15:11
apwtgardner, i wanted to check he hasn't done them already15:11
apwtgardner, i guess as they are rebasable i can jstu do them and not care15:12
apwsconklin, scream now if you don't want them rebased15:13
tgardnerapw, he could be screaming, but his pulse-audio has died.15:13
* smb would sort of expect some "hold now" and "go" to know when one should be careful on touching -nexts15:14
apwsmb, well you can tell if you push over someone so ... its entirly safe, just hard-ish to un-fook when you do overlap15:14
smbapw, Just don't like to find out by the time I would push, I guess15:14
sconklinapw: I have no issues with fixing up the -next branches, I just usually don't use a rebase to do it. 15:18
sconklinFor reasons we discussed at the rally15:18
smbwe did?15:19
smbAh well15:19
apwsconklin, i am using the term rebase in its literal form, to move the base of the branch to the tip of master, not implying what you use to do it15:19
smbIts not really the rebase but the need to have a sensible (higher) version number15:19
sconklinThere was a long discussion of why I prefer to cherry pick all the new commits from -next to the last tag, and force push that over master-next15:19
sconklinit amounts to the same thing.15:20
* smb remembers now15:20
apwsconklin, right i don't care how one choses to do it, what i a complaining about is it not being dne15:20
sconklinWant me to do it, or does apw have it under control?15:20
apwsconklin, and if you haven't the time to do it i can do it, just say15:20
sconklinagreed. It's "yet another thing that doesn't have a checkbox that's enforced and gets forgotten"15:20
apwsconklin, i'll just go ahead and move them up then15:21
sconklinI can easily get it done today, probably in the next couple of hours including the meeting15:21
apwsconklin, ok i'll let you15:21
apw(and i am complaining cause the pre-proposed kernels are getting dumb versions not cause i inherantly care)15:22
sconklinno, I understand15:22
apwsconklin, are we close to releasng any of these -proposed kernels?15:23
sconklinafaik, it's all in qa and cert now. So the answer is a provisional yes15:24
sconklinI'm compiling that information now for the meeting15:25
apwsconklin, cool, i am getting bored waiting for the lts-backport for natty to arrive 15:26
sconklindid you prep and build that? I'm not sure we did15:27
sconklinIt ftbfs a while back and I don't think I got back to it15:27
apwi suspect i did originally15:27
sconklinI'll have a look15:28
apwit ftbs's on everything other than x86 and x86_64, but that is an archive error15:28
apwas we only target those two architectures, it is not even meant to start on the others15:28
apwi have been assured its not our fault15:28
apwthat the control file is right and does not specify those other arches, but it goes there anyhow15:28
sconklinthen it may just be sitting and waiting to be copied out of the ppa. I'll check15:29
hertonyes, the script probably didn't get the build status as FULLY_BUILT because of the other arches which failed15:30
hertonthus it didn't set the prepare-package to fix released for the lts-backport tracking bugs15:30
herton(script = shank bot)15:31
* apw will once more try and get to the bottom of whether we can fix this15:37
micahgare you aware that the new 3.0.0-x kernel is showing up under the 3.0-x kernel in grub1?15:40
apwmicahg, under? as in appearing 'lower' in version ?15:42
micahgapw: yes, options 3 and 4 :)15:42
apwmicahg, why the heck is grub1 still on anything ?15:42
micahgI've been upgrading since hardy on that machine I think :)15:42
micahgI can file a bug, I just wanted to make you aware15:43
apwcjwatson, do we care a15:43
tgardnermicahg, delete the 3.0-x kernel ?15:43
apwcjwatson, do we care any more about grub1 ?15:43
micahgtgardner: I can't be the only one with the issue ;)15:43
tgardnermicahg, perhaps, but I'm not sure its something we'll fix 'cause 3.0-x was temporary15:44
smbapw, Just fwiw, you may encounter similar code in pv-grub on ec215:44
apwok confirmed that grub2 is at least ordering them right15:44
apwsmb, nnng, well as we will release with a 3.0.0 i don't think we should hit it right ?15:44
tgardnerapw, right. its a developer issue15:45
smbapw, no, you are right. 15:45
micahgit's ascii ordering instead of version ordering15:45
apwmicahg, but do file a bug15:45
apwat least that way people will stumble on it, and we can document removing the old ones as a work-around15:45
micahgapw: bug 80940115:50
ubot2Launchpad bug 809401 in grub "grub is ascii ordering instead of version ordering kernels" [Undecided,New] https://launchpad.net/bugs/80940115:50
bjf## Kernel team meeting in one hour16:00
cjwatsonapw: we've never auto-upgraded people, so yes we do slightly care16:04
cjwatsonalso I thought the sorting in GRUB Legacy was the same as that in GRUB 2 ...16:04
cjwatsonhm, perhaps not16:06
cjwatsonanyway, it's my responsibility to fix, not yours16:06
cjwatsonand it's not just ascii-ordering, it's more complicated than that16:06
cjwatsonI'll have a look16:07
tgardnercjwatson, its really only a developer issue, i.e., only folks that had 3.0-x installed are affected. the normal upgrade from Natty to Oneiric should be fine.16:07
cjwatsontgardner: it's a bug, and should be fixed16:07
cjwatsonsure, not very high priority :)16:07
lamonttgardner/herton: 3.0.0-4.5 seemed to fix that.  what are the chances of getting a r8169 driver backport to natty?16:16
tgardnerlamont, hmm, I can check into it. perhaps an LBM backport ?16:17
tgardneron the other hand, the in-kernel driver is so broken that maybe I should just SRU a replacement16:18
lamonttgardner: I'd prefer to run "a natty kernel"  I have absolutely no care as to how we define that16:19
tgardnerlamont, I've forgotten. Is there an existing bug no this r8169 issue?16:31
lamont809000 is the best candidate16:32
tgardnerlamont, ack16:32
lamontI haven't proven it - turns out that my spare network card has more pins on its edge connector than the mobo has pins in the slot16:33
lamontthe plan for today is to go drop $20 on a network card on my way ome16:33
lamonthome. even16:33
tgardnerogasawara, given our policy of not modifying user space for backports, how do I note in the KernelOneiricUbuntuDeltaReview that we'll continue to carry a patch, likely in perpetuity ?16:34
tgardnerin particular 'UBUNTU: Sony laptop: Some Sony Vaia laptops do not enable wwan power by default.'16:34
ogasawaratgardner: add a note to the wiki, and on the next rebase I can munge the commit message to note "SAUCE: (no-up)" so we know we'll carry it going forward16:37
hertonlamont: hmm ok, would be good indeed to check with another network card still16:38
tgardnerogasawara, ack16:38
sconklinapw: The natty backports kernel needs to be respun, since we dropped some regressions out of Natty since it was made16:38
apwsconklin, excellent let me do it16:39
apwsconklin, as i think i have the fix for the erroring foun16:39
sconklinI suspect that the same is true of Maverick, checking16:39
apwsconklin, i will do both if they need it ... let me know16:39
hertonyes, maverick is the same16:39
hertonwe reverted two patches (1 failed verification, the other is the tlb regression)16:40
sconklinand - it's difficult to determine exactly what Natty the backports kernel is based on, because when we drop the patches and respin Natty and only change the upload number, that doesn't get propagated into the backports version or log that I can see16:40
apwsconklin, the version of the backports is identicle to the one is it based on16:40
apwsconklin, with ~lucid1 on the end16:41
sconklinoh, well then perhaps it does contain the reverts and is up to date16:42
sconklinone sec16:42
sconklinYes, it appears that what's in the PPA for natty backports reflects the latest natty (.46), so it only needs copying to -proposed.16:43
sconklinapw: I get it now, thanks16:44
apwsconklin, ok and i think i have the erroring out crap sorted for next time, pushed to natty and maverick backports branches16:44
sconklinapw, smb, tgardner: who is qualified to make a decision about whether it's OK to ship Natty with the CONFIG_DEBUG_RODATA issue? As it is it's stopped based on the QA testing failure, and we need to know whether to override that or respin (please be the former).16:52
tgardnersconklin, we talked about that earlier this morning. its not a regression so shouldn't hold up this release. smb is investigating....16:52
smbsconklin, We had been disabling that because of some i386 ec2 problem16:53
tgardnerit _used_ to cause ec2 issues, but has perhaps been fixed in the interim16:53
smbsconklin, So its not a regression. But it seems based on my current test that it could get enabled again16:53
smbsconklin, Is there a bug open for it already?16:53
sconklinok, I'm going to consider that two acks for releasing what we have16:53
sconklinsmb: Not that I'm aware of. herton may know16:54
hertonI think there is no bug open for that16:54
smbOk, so I will open one for submitting the patch to enable it again when I am done with all the tests I wanted to do16:55
bjfsconklin, as stable mgr. i think it's your call16:56
sconklinbjf: Updating the bug now to ship it.16:56
sconklinI just wasn't clear on the technical implications.16:56
sconklinapw: when do the build run on the master-next branches?16:58
bjfsconklin, new tag: "let 'er buck"16:58
sconklinbjf: http://en.wikipedia.org/wiki/File:Slim-pickens_riding-the-bomb_enh-lores.jpg17:01
ppisatidon't we have the meeting now?17:02
bjfppetraki, was daydreaming17:03
smbbjf, nice the tags listing sort of is just the right start point to look for some of my tags of interest17:20
bjfsmb, if there are other spins/mappings you'd like to see, let me know, i plan on adding more that I think are of value17:21
apwsconklin, as in when is pre-proposed uploaded?  09:00 UTC17:21
tgardnerbjf, how about a graph showing the number of comments in a bug? or the number of subscribers, or the number of 'affects me', etc17:22
apwthough i have been thinking it should be checked hourly and uploaded if its more than 24 hours since it last was uploaded and different17:22
sconklinok, I am commencing fixup of the -next branches17:24
bjftgardner, i'll put that on the list17:24
tgardnerbjf, just thoughts on how to gauge what bugs are really pissing people off17:25
apwheat ?17:25
bjftgardner, apw, "kernel gravity"17:25
bjftgardner, apw, "bitch factor"17:26
* smb thinks bugs against dapper, gutsy and feisty at least should be targets to kill...17:26
apwheh i meant there is already a heat17:26
bjfsmb, yes, a script is on my list17:26
bjfsmb, "won't fix" all unsupported series17:27
smbbjf, nice :)17:27
apwbjf, i may have the bones of that already, in the bugs/proc-cve-bugs17:27
apwwhich works out the same equasion, is this package supported on this release17:27
smbapw, There is definitely heat... oh you meant the bug heat :-P17:27
sconklinheat index is 105F here17:28
apw18.9c here, which is nowhere near that, less than 70f17:28
smb28°C -> 82°F in my room...17:29
apwsmb, man you need to smash some windows17:29
mjg59apw: That'll just let the heat in17:30
* smb hopes the distant grumble means coolness17:30
apwmjg59, without aircon, its almost cirtain that his machine heavy room is hotter than outside17:30
smbapw, Was suppusedly 30 outside17:31
apwsmb, you need to move17:31
apw(slowly :)17:31
smbapw, Was about to say that moving makes me feel even warmer17:32
bjfsmb, the high for the next 10 days is 26C, mostly 18 - 2317:36
smbbjf, I hope they are right17:37
* tgardner reboots to test CVE-2010-425117:43
ubot2tgardner: The socket implementation in net/core/sock.c in the Linux kernel before 2.6.34 does not properly manage a backlog of received packets, which allows remote attackers to cause a denial of service (memory consumption) by sending a large amount of network traffic, as demonstrated by netperf UDP tests. (http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-4251)17:43
=== bjf changed the topic of #ubuntu-kernel to: Home: https://wiki.ubuntu.com/Kernel/ || Natty Kernel Version: 2.6.38 || Ubuntu Kernel Team Meeting - July-19 - 17:00 UTC || If you have a question just ask, and do wait around for an answer!
tgardnersconklin, when a Q/A test fails do they stop testing right away?18:15
sconklintgardner: good question. I assumed not because the bug said something like "18 tests, 1 fail", but there may have been 30 tests total. I don't know.18:16
tgardnersconklin, likely worth following up on before setting a Q/A to released18:17
tgardnera Q/Q task*18:17
sconklinyeah, probably too late for this one, but good question. bjf, do you know? ^^18:17
tgardnersconklin, I know cert baila on the first failure18:17
sconklinthat's not terribly useful18:18
tgardnerdoesn't seem like it to me either18:18
bjfsconklin, from what i've seen, it depends on the failure18:18
bjfhggdh, ^^ thoughts?18:19
hggdhsconklin: no, I do not stop on first failure18:19
hggdhthe failure may be localised, or other archs/kernels may show different failures, so I consider it worth the time to keep on18:20
hggdhwhat I do is warn I found a failure, tag the bug accordingly, and keep on18:21
hggdhbjf: ^ 18:21
bjfhggdh, thanks, i think that is what we'd like to see done as well18:22
bjfsconklin, tgardner ^^18:22
sconklinhggdh: thanks!18:22
hggdhspecifically to the QRTs, all unit tests on each module are run to the end18:22
sconklinhggdh: did you see that I overrode your QA failure?18:23
hggdhsconklin: yes, I did see. I had just ended with the KVM tests, so all is kosher18:23
sconklinhggdh: Thanks!18:23
hggdhsconklin: and this is actually what I expect to happen. I should not decide on overriding or not18:24
hggdhso... Lucid and Natty done. bjf, sconklin, a specific version you would like me to work on now, or anyone left is good?18:25
sconklinhggdh: ok, thanks. We'll have to modify processes as appropriate as QA gets more integrated and automated.18:25
sconklinMaverick is important for some folks. It may not be back in -proposed yet, let me check - hold on18:26
hggdhaye. Hoiw do you want go to forward on this error (Natty EC2 m1.small/i386 CONFIG_DEBUG_RODATA)? Pass the next one, or still mark as failure?18:27
sconklinstill mark as failure, because we should have it fixed in the next release. Force me to override it if needed ;)18:27
hggdh:-) a pleasure to, er, help ;-)18:28
sconklinhggdh: Maverick is still awaiting copy to -proposed, and as soon as that is done we will mark it verification complete because it is simply a respin with some reverts.18:30
sconklinSo in the meantime, grab something else . . .18:30
hggdhsconklin: roger wilco18:30
* tgardner --> lunch18:32
* jjohansen -> lunch19:31
=== Quintasan_ is now known as Quintasan
njinhello, there's someone experiencing Error insetingpadlock_sha in 3.0.0-4 ? any workaround to restore system?19:35
njinError inserting padlock_sha19:36
=== yofel_ is now known as yofel
tgardnernjin, is it the right kind of CPU ? 19:41
tgardnerthis is not typically a fatal error19:41
njintgardner, is the yesterday update, system is locked at login screen, nothing working, no panic19:42
tgardnernjin, thats likely something other then a crypto engine failure19:43
njinencrypted /home cannot be mounted, no mouse or console, only sysrq19:43
njinunfortunately no thing in the log files19:43
tgardnernjin, and 3.0-3 consistently works ?19:43
njin3.0-3 yes fine19:44
tgardnernjin, boot 3.0-3 and run 'ubuntu-bug linux' with a description of the problem. 3.0.0-5.6 is almost ready as well (-rc7)19:44
njintgardner, many thanks, i'll do it19:45
bjfjjohansen, ok as roomie for orlando?19:55
tgardnerogasawara, oneiric is done building. would you like me to upload -meta ?19:57
ogasawaratgardner: go for it19:57
jjohansenbjf: yep20:01
bjfjjohansen, ok, i've entered it into the write-only registration system20:04
jjohansenbjf: ugh, I can't believe we have to use that system again20:05
tgardnerogasawara, uploaded and announcement sent20:06
ogasawaratgardner: awesome, thanks20:06
ogasawaratgardner: I'll post a blurb to voices.c.c too20:06
tgardnerogasawara, hmm, did ubuntu-mobile@lists.ubuntu.com go away? I got a bounce message20:07
ogasawaratgardner: it bounced for me as well so I quit sending to it20:07
tgardnerogasawara, I guess I'll fix the wiki20:08
hggdhsmb: there still?20:17
jjohansenhggdh: hopefully not, its 22:22 for him20:23
hggdhjjohansen: heh. I had to try... will ping him tomorrow, then, thank you20:23
jjohansenhggdh: anything I can help with?20:23
jjohansenhggdh: I could also rely a message when he comes on in the morning20:24
hggdhjjohansen: this is related to bug 790712 -- smb asked for a syslog. But a debian-installer "syslog" shows much of the installer activities, and almost nothing else...20:33
ubot2Launchpad bug 790712 in linux "20110531 i386 server ISO: order 5 allocation failure during install" [High,Confirmed] https://launchpad.net/bugs/79071220:33
hggdhjjohansen: so I added a d-i syslog to the bug, but I am unsure on what he will find there...20:33
jjohansenhggdh: can you add the kernel log as well20:34
hggdhjjohansen: there is no kernel log20:34
jjohansenhggdh: no kernel log?  How about dmesg?20:34
jjohansenis it possible to retrieve that20:35
hggdhnot directly -- the install never ends, so we do not have control/access to the VM. But I can run it manually here, reproduce the error, and collect it (I hope)20:35
jjohansenhggdh: if its doing order 5 allocations, it isn't surprising that it is failing20:36
jjohansenhggdh: worth a try20:36
hggdhI do not disagree. The thing is 480M should be enough to install an i386 kernel... and it does not happen always20:36
ogasawaraapw: just fyi, I'm able to post to voices.c.c/kernelteam20:41
manjoogasawara, in delta review Manoj Iyer21:22
manjoQuirk to fix suspend/resume on Lenovo Edge 11,13,14,1521:22
manjoUBUNTU: SAUCE: (drop after 2.6.38) add ricoh 0xe823 pci id.21:22
manjothose two patches can be dropped as they should be in stable already21:22
manjoogasawara, the 3rd one has original author as Timo so I have emailed him to report the status21:23
bjfmanjo, did you add your comments to the blueprint like everyone else?21:23
manjobjf, not yet ... this was just brought to my attn so going to do that next .. thought I will tell ogasawara 1st 21:24
bjfmanjo, and actually its the spec at: https://wiki.ubuntu.com/KernelTeam/Specs/KernelOneiricUbuntuDeltaReview21:24
manjobjf, thanks yes I know21:25
=== skaet is now known as skaet_afk
=== skaet_afk is now known as skaet
manjobjf, just updated blueprint21:27
manjobjf, I think ogasawara needs to mod the wiki? 21:28
ogasawaramanjo: thanks, if you can just make a note of this in the wiki under your section that'd be good.  I'll revert the two patches for now and then drop them upon the next rebase.21:55
=== Quintasan_ is now known as Quintasan
=== cking is now known as cking-afk

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