[00:47]  * kamalm frowns -- here's a puzzler - I sent my patch to LKML and cc: achiang more than 2.5 hours ago but it hasn't appeared on LKML (archive or my subscription) - I received my bcc: copy and I think achiang received the cc: copy but why hasn't it hit LKML?  been plenty of other traffic since then.  :-(
[00:50] <cnd> kamalm: lkml has a delay
[00:50] <cnd> I don't know why exactly, but it's a multi-hour delay
[00:54] <achiang> kamalm: i got it twice, actually
[00:54] <kamalm> cnd: ah, okay then, that would explain it.  By looking at the "Date:" headers on other messages, it appeared to me that there was no "extra" delay - i'll keep waiting
[00:55] <kamalm> achiang: I actually did re-send it again, after thinking that my excessively long To: line might have been the problem I fixed that and re-sent.  (wasn't patient enough - oops).
[00:55] <achiang> nod
[00:59]  * cnd fears lkml too much to resend unless it's been over a day :)
[00:59] <cnd> oh wait, kamalm, this is your acpi patch right?
[01:00] <kamalm> yes
[01:00] <cnd> did you send it to linux-acpi?
[01:00] <kamalm> yes
[01:00] <cnd> ok
[01:00] <kamalm> hasn't arrived there either
[01:00] <cnd> I don't think sending it to lkml is required as well
[01:00] <cnd> are you subscribed to linux-acpi?
[01:01] <kamalm> Documentation/SubmittingPatches said that you should also send to linux-kernel "unless you have a good reason not to"
[01:01] <kamalm> cnd: I think I'm not sub'd to linux-acpi
[01:02] <cnd> kamalm: ahhh, I learn something new every day then :)
[01:03] <kamalm> looks like LMKL might have a "greylist delay" thing going http://www.mail-archive.com/linux-kernel@vger.kernel.org/msg149954.html
[01:06] <kamalm> cnd: re: linux-acpi -- I'm not subscribed but watching its archive page for my post to appear.  I wonder if it accepts posts from non-subscribers.  I *am* subscribed to LKML
[01:06] <achiang> kamalm: it does. i'm on it. your mail hasn't hit the list yet
[01:07] <achiang> kamalm: i'd recommend going for a beer or a walk. :)
[01:08] <achiang> and speaking of beer... it's about that time. :)
[01:08] <kamalm> i suppose I should be on it too...  why not, just one more list, right?  yeah, I've decided that it's probably a greylist delay so I'll just wait till tomorrow :-)   beer sounds right.
[01:13]  * JFo recommends Crown Royal Black if you haven't tried it yet :)
[01:17] <cnd> JFo: is that whisky?
[01:17] <JFo> cnd, yep
[01:18] <cnd> sounds good to me, but all I've got here is some jim beam
[01:18] <JFo> that works too :-)
[01:18]  * JFo goes off to refill his glass and watch a movie
[01:18] <JFo> night all
[01:19] <cnd> at the rate I've been traveling though, I hardly need anything between my various trips
[07:11] <cmug> Hi. Does 10.04 have a kernel that has DMA remapping option enabled ? It is essential for kvm device passthrough virtualization
[07:15] <jk-> cmug: do you know the CONFIG_ parameter?
[07:18] <cmug> jk-, CONFIG_DMAR
[07:18] <cmug> CONFIG_DMAR=y
[07:18] <cmug> CONFIG_DMAR_DEFAULT_ON=y
[07:19] <jk-> # CONFIG_DMAR is not set
[07:19] <cmug> :( Is that same for every available kernel image ?
[07:19] <jk-> this is the generic flavour though...
[07:19] <cmug> yeah, perhaps there should be a linux-image-virtualization or something ?
[07:23] <jk-> doesn't look to be enabled in -server
[07:26] <cmug> :( I guess it's not called Experimental for no reason. But AFAIK it is crucial for the device passthrough functionality 
[07:26] <cmug> and it's kind of a showstopper for me
[07:27] <jk-> not keen to build you own?
[07:29] <cmug> I like updates
[07:29] <jk-> everyone likes updates :)
[07:29] <cmug> Yeah
[07:30] <cmug> Maybe somebody can create a PPA with the kernel with DMAR enabled
[07:30] <cmug> maybe it already exists, don't know
[07:30] <jk-> i volunteer you to do that :D
[07:31] <cmug> I can do that if I knew how
[07:31] <cmug> Need to investigate
[07:31] <cmug> btw, is lucid released today (28th) ?
[07:32] <lifeless> no
[07:32] <lifeless> 29th
[07:33] <cmug> ok, I was just hoping since it is still 27th in the west coast of USA :)
[08:11] <dmarkey> too late to request something for 10.04 i assume?
[08:12] <jk-> given that it's out tomorrow, probably yes :)
[08:15] <dmarkey> aww :(
[08:16] <dmarkey> i'll wait till 10.10 then
[09:33] <cking> csurbhi, so what's going wrong - I've not see this kind of problem before
=== Ng_ is now known as Ng
[11:25]  * akgraner waves to apw - got a sec?
[11:25] <apw> akgraner, wassup
[11:26] <akgraner> Open week :-D stuffs - see pm
[16:16]  * JFo stretches out
[16:18] <JFo> hi there cking :)
[16:20] <cking> JFo, hiya
[16:20] <akgraner> JFo, Rikki can't test the patch til Friday 
[16:21] <JFo> akgraner, hmmm
[16:21] <akgraner> is this an issue for you all
[16:21] <JFo> I think they are wanting this to go into a day 0 update
[16:21] <akgraner> she is doing some livestreaming
[16:21] <JFo> and steve will need the confirmation before he releases it from proposed
[16:21] <akgraner> hmm let me call her
[16:21] <JFo> ok
[16:22] <akgraner> k
[16:22] <JFo> don't quote me as that is an interpretation
[16:22] <akgraner> *nods*
[16:25] <akgraner> JFo, nope she can't til Friday - they yanked out her HD and her machine is the what they are using for streaming
[16:25] <apw> those changes should be in the kernel in the kernel pre-proposed PPA
[16:25] <akgraner> She wants to be a good bug reported - but the computer they were going to use for streaming never showed up yesterday
[16:31] <jjohansen> csurbhi: so basically server team was looking for an update on ext4 performance and I haven't followed if there has been anything new recently
[16:33] <psurbhi> jjohansen, I havent done any benchmarks recently
[16:34] <psurbhi> and have not read anything on osnwes or phoronix report as well
[16:34] <jjohansen> psurbhi: okay, so basically the same status as at the sprint
[16:34] <psurbhi> yes
[16:34] <jjohansen> psurbhi: it came up because of this http://www.phoronix.com/scan.php?page=article&item=ubuntu_lts_perf&num=2
[16:35] <jjohansen> looks like phoronix, rerunning the same tests again a couple weeks ago
[16:35] <psurbhi> ok
[16:36] <psurbhi> ya, comparing 2.6.24 ext3 and 2.6.32 ext4 :O
[16:42]  * JFo goes to have some lunch
=== bjf is now known as elBoto
=== elBoto is now known as bjf
[16:58] <bjf> elBoto list
[16:58] <elBoto> bjf: Admin, Channel, Config, Misc, Owner, and User
[16:58] <manjo> can you hear me now ? 
[16:58] <manjo> ogra, that worked
[16:58] <ogra> yeah
[17:20] <bjf> elBoto, ping
[17:20] <elBoto> pong
[17:22] <JFo> elBoto, Misc
[17:22] <elBoto> JFo: Error: "Misc" is not a valid command.
[17:22] <JFo> heh
[17:22] <JFo> elBoto, Owner
[17:22] <elBoto> JFo: Error: "Owner" is not a valid command.
[17:24] <bjf> elBoto, help Misc
[17:24] <elBoto> bjf: Error: There is no command "misc".
[17:24] <bjf> elBoto, list Misc
[17:24] <elBoto> bjf: apropos, help, last, list, more, ping, source, tell, and version
[17:25] <bjf> elBoto, help ping
[17:25] <elBoto> bjf: (ping takes no arguments) -- Checks to see if the bot is alive.
[17:25] <manjo> elBoto, whoami
[17:25] <elBoto> manjo: I don't recognize you.
[17:25] <JFo> heh
[17:26] <manjo> elBoto, who's your daddy
[17:26] <elBoto> manjo: Error: "who's" is not a valid command.
[17:26] <manjo> ah this bot is stupid 
[17:26] <vanhoof> ... and what does he do 
[17:26] <vanhoof> what kind of bot is it, supybot?
[17:27] <vanhoof>  elBoto [~supybot@pool-98-108-129-180.ptldor.fios.verizon.net]
[17:27] <vanhoof> guess so :)
[17:27] <jussi> pgraner: ping
[17:28] <JFo> jussi, he is in London, so he may be out for the night
[17:28] <pgraner> jussi: pong
[17:28] <JFo> or not :)
[17:28] <pgraner> JFo: nope I'm omnipresent
[17:28] <jussi> pgraner: hi, may I pm?
[17:28] <pgraner> jussi: sure
[17:28] <JFo> pgraner, hah!
[17:28] <alkisg> Hi, where can I find linux-image-2.6.32-20-generic? I can't find it in packages.ubuntu.com nor in http://kernel.ubuntu.com/~kernel-ppa/mainline/... I think it's the last one that'll boot with my intel 845 graphics card.
[17:29] <alkisg> (-19 boots, -21 doesn't, and I never tried -20)
[17:32] <JFo> alkisg, I have been fortunate enough to never need to go back to an older kernel that I hadn't installed
[17:32] <bjf> vanhoof, was going to add a launchpad plugin to it
[17:32] <JFo> bjf, any iodea where older kernels are located?
[17:32] <alkisg> JFo: I wish I was so lucky... :)
[17:32] <JFo> read, older recent kernels?
[17:32] <bjf> JFo, nope, was asking you that yesterday :-)
[17:32] <JFo> alkisg, :)
[17:32] <JFo> bjf, oh yeah :-)
[17:33] <JFo> apw, you still around?
[17:33] <apw> JFo, wassup
[17:33] <JFo> apw, where would one go to find 32.20 kernel now?
[17:33] <JFo> bjf and I were wondering yesterday too
[17:33] <apw> jfo an old build you mean?
[17:33] <JFo> yessir
[17:34] <JFo> apw, yes please :)
[17:35] <apw> JFo, they are all in the launchpad librararian
[17:35] <JFo> hmmmm
[17:35]  * JFo goes to look
[17:36] <apw> https://edge.launchpad.net/ubuntu/+source/linux/+publishinghistory
[17:36] <apw> then click on the version you want, and then the build arch you want
[17:36] <apw> and there are the .debs
[17:36] <JFo> ah hah!
[17:36] <JFo> thank you sir
[17:36] <alkisg> Thank you both very much :)
[17:37] <bjf> JFo, that rocks!
[17:37] <JFo> bjf, that does very much
[17:57] <bjf> @list
[17:57] <elBoto> bjf: Admin, Channel, Config, Misc, Owner, and User
[18:03] <apw> @list
[18:03] <elBoto> apw: Admin, Channel, Config, Misc, Owner, and User
[18:06] <amitk> bjf: use your powers and change topic :)
[18:07] <bjf> amitk, just tried and failed
=== bjf changed the topic of #ubuntu-kernel to: Home: https://wiki.ubuntu.com/KernelTeam/ || Lucid Kernel Version: 2.6.32 || Ubuntu Kernel Team Meeting - May-17 - 17:00 UTC
[18:15] <Sarvatt> apw, sconklin: did "UBUNTU: SAUCE: KMS: cache the EDID information of the LVDS"  get dropped on purpose or was it just lost with the drm backport as well? http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-lucid.git;a=commit;h=c5155725948be57010c4a558a1b9c5ddefb864c3
[18:21] <apw> Sarvatt, hrm not sure ... i thought that was an upstream job, and should still be in
[18:22] <apw> Sarvatt, i cannot see the expected messages in dmesg from it ... could you email me to remind me to look pls
[18:27] <Sarvatt> sure thing, sorry I didn't bring it up directly earlier
[20:06] <bguthro> I'm attempting to debug a suspend-resume issue with a new Dell Inspiron i3 based machine using the following methods: https://wiki.ubuntu.com/DebuggingKernelSuspend but am running into a brick wall. Was hoping for some other pointers.
[20:07] <bguthro> bjf says manjo might be a good resource...if you're around
[20:08] <manjo> bguthro, is the problem with suspend or resume ? 
[20:08] <bguthro> Resume: Things seem to go down fine...but never come back. I always have to cold boot.
[20:08] <manjo> bguthro, what graphics card do you have ? 
[20:08] <manjo> are you able to ssh to the box ? 
[20:09] <bguthro> no. completely dead. The backlight doesn't even light up. The power light goes from pulsing, to solid...and I get a blip of the HDD, but then it is just stuck
[20:10] <bguthro> I've tried adding modules to the list to unload in /usr/lib/pm-utils/defaults - but no dice, so far
[20:10] <bguthro> I've also reproduced this on an i5 (also an inspiron)
[20:11] <bguthro> graphics card is the integrated i3 chip
[20:11] <bguthro> it uses the i915 driver, though
[20:11] <manjo> bguthro, have you tried using PM_DEBUG & PM_TRACE ? 
[20:12] <bguthro> I tried the echo 1 > /sys/power/pm_trace - Is there more I can try?
[20:12] <manjo> bguthro, the instruction are in linux-2.6/Documentation/power/s2ram.txt
[20:13] <bguthro> I'll take a look, thanks
[20:13] <manjo> bguthro, also looks at basic-pm-debugging.txt
[20:14] <manjo> bguthro, its hard to remote help debug suspend/resume issues without real hw in front 
[20:15] <manjo> bguthro, if you can try that then we can figure out the offending module / device 
[20:15] <manjo> bguthro, also try with nokms
[20:15] <bguthro> will i915 still boot? I've had issues with that in the past...
[20:16] <bguthro> but I'll give it a shot
[20:16] <manjo> bguthro, ie nomodeset
[20:16] <bguthro> I guess I tried with i915.modeset=0
[20:17] <manjo> ok
[20:18] <manjo> bguthro, All drivers: nomodeset - this will disable the kernel modesetting feature 
[20:23] <bguthro> the only hash matches I got was against "tty tty57" - attempting with nomodeset now, but X doesn't seem too happy. I'm not getting any graphics
[20:24] <bguthro> plymouth came up (somewhat garbled) - and then it became unresponsive.
[20:26] <bguthro> yeah...even booting without "splash" - X fails to come up properly.
[20:26] <bguthro> unfortunately, this machine has no serial line, and no dock...so I can't even see if a trace is coming out or not.
[20:39] <manjo> bguthro, what model of dell is it ? 
[20:39] <bguthro> testing all modes in /sys/power/pm_test succeed, but when I echo none to it, the system does not come back. According to the documentation, this suggests that it is in the invocation of the platform firmware
[20:40] <bguthro> It is an Inspiron 1434
[20:40] <bguthro> sorry 1464
[20:40] <manjo> bguthro, my dell contact is offline, I will check with him to see if there is a bios update for this 
[20:40] <bguthro> also seen on a 1764
[20:40] <manjo> or firmware 
[20:41]  * manjo makes of note of the dell models 
[20:41] <bguthro> I updated the Bios today to the latest posted on the site.
[20:41] <bguthro> I did not check for firmware
[20:42] <manjo> bguthro, I will check on these models.. 
[20:42] <bguthro> thank you
[20:42] <manjo> to see if they have any recommendations
[20:43] <manjo> bguthro, pm me your email 
[20:49] <achiang> bguthro: that sounds a lot like what kamalm was working on.
[20:49] <achiang> bguthro: which kernel?
[20:50] <bguthro> 2.6.32-21-generic
[20:52] <achiang> bguthro: any chance you could try an upstream kernel? and pass acpi_sleep=sci_force_enable on the kernel cmdline?
[20:59] <kamalm> bguthro, achiang: the acpi_sleep=sci_force_enable feature looks like it was applied to Lucid http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-lucid.git;a=summary (see the Zhang Rui change) but I'm not sure where one would get a binary .deb which includes it.
[21:00] <bguthro> I'm not opposed to rebuilding myself. Should I just clone the git tree?
[21:01] <achiang> bguthro: this will be much easier: http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.34-rc5-lucid/
[21:02] <kamalm> ah yes, look at all those tasty kernels in .../mainline :-)  thanks achaing
[21:02] <bguthro> will give it a try after filing the launchpad bug for manjo
[21:03] <achiang> bguthro: which bug is that? a bug for this s/r problem?
[21:03] <manjo> achiang, he is filing now 
[21:04] <achiang> won't it just be dup'ed to whatever bug kamalm fixed with his recent patch that adds dell machines to the quirk list?
[21:04] <achiang> manjo: ^^
[21:04] <achiang> kamalm: what was the LP bug for your dell fix?
[21:05] <manjo> achiang, yes if its the same bug
[21:05] <kamalm> achiang: nope -- my patch specifically adds 3 different "Dell Studio" models -- no effect on other models
[21:05] <kamalm> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/553498
[21:05] <ubot3> Malone bug 553498 in linux "Dell Studio 1558 (Arrandale) hangs on resume from suspend" [Medium,Fix committed] 
[21:05] <manjo> kamalm, that looks diff 
[21:05] <manjo> lets wait for bguthro to finish filing his bug :) 
[21:08] <bguthro> grrr...got all the way through, and it failed.
[21:08] <bguthro> I'll start over...
[21:18] <bguthro> FWIW: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/571422
[21:18] <ubot3> Malone bug 571422 in linux "[LUCID] suspend/resume issue on Dell Inspiron 1464/1564/1764" [Undecided,New] 
[21:20] <manjo> kamalm, achiang we track degu on ^^ #bug
[21:21]  * manjo typing impaired 
[21:21] <achiang> eh?
[21:21] <kamalm> bguthro: the symptoms do sound the same -- the acpi_sleep=sci_force_enable sounds like a good thing to try here.
[21:22] <bguthro> with .32 or the .34 referenced above?
[21:22] <achiang> kamalm: manjo: btw, i had a conversation with lenb on #acpi this am ; intel are aware of these crappy BIOSes coming out
[21:22] <achiang> not sure what action they plan on taking right now
[21:22] <achiang> maybe forceful beating about the head and shoulders with a cluebat
[21:23] <manjo> well dell says they do a good job of testing bios etc before they release machines ... 
[21:23] <mjg59> Well, everyone's signed off on the generic fix other than Len
[21:23] <manjo> I guess they test only with windows
[21:23] <achiang> manjo: i have some great property in florida i'd like to sell you too. ;)
[21:23] <manjo> achiang, how many acres do you have ? 
[21:23] <kamalm> mjg59: the generic fix being to just force sci_enable on all the time?
[21:24] <manjo> I am not intersted in 42
[21:24] <achiang> manjo: as many as you'd like. ;)
[21:24] <manjo> heh
[21:24] <mjg59> kamalm: No, to do the register write if the system fails to set it itself
[21:24] <vish> hi.. I'm trying to use mainline kernel , but  why is there no *all.deb for this kernel?  http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.32.11-lucid/
[21:25] <mjg59> So, in order, follow the spec, do something that's mildly against spec, do something that wildly violates the spec
[21:28] <bguthro> OK, so .34 from http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.34-rc5-lucid/linux-image-2.6.34-020634rc5-generic_2.6.34-020634rc5_amd64.deb and the acpi_sleep=sci_force_enable flag seems to do the trick
[21:28] <manjo> bguthro, cool... can you throw that info in the bug ? 
[21:29] <manjo> achiang, so this bad bios that vendors are aware of ? 
[21:29] <bguthro> kamalm: Is this a generic flag in the .32 kernel - or is this only accepted upstream? (ie - can I Cherry-pick it for a build)
[21:29] <achiang> manjo: according to irc scuttlebutt, yes
[21:29] <achiang> maybe not dell, but lenovo are aware
[21:30] <manjo> bguthro, might be good to put that info in the bug ... I pointed jerone at it ... he will follow up with dell 
[21:31] <bguthro> manjo: bug updated
[21:31] <manjo> thnx
[21:31] <kamalm> bguthro: as far as I know, the fix has been applied upstream -- we cherry-picked it from kernel.org (I think).
[21:33] <vish> folks, according to the map it seems 2.6.32-21.32	is 2.6.32.11 mainline , but it doesnt have the *all.deb package.. how do i test with the mainline version then? [was asked to check for a bug]
[21:33] <vish> not there for >  http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.32.11-lucid/
[21:34] <achiang> manjo: still trying to understand this statement: " we track degu on ^^ #bug"
[21:34] <achiang> manjo: are you telling me to join a channel?
[21:37] <bguthro> kamalm: Same acpi_sleep=sci_force_enable added to 2.6.32-21-generic to no effect. Did this get cherry picked after this binary was built for us.archive.ubuntu.com?
[21:37] <manjo> achiang, my fingers did not follow my brain on that one 
[21:38] <kamalm> bguthro: looking
[21:39] <achiang> manjo: ok, just trying to make sure you're not asking me to take some action of some sort. :)
=== bjf is now known as bjf[afk]
[21:39] <manjo> heh 
[21:40] <manjo> achiang, now don't make me the action man :)
[21:40] <kamalm> bguthro: per http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-lucid.git;a=shortlog the acpi_sleep= feature was added 5 days ago and so first appears in 2.6.32-22.
[21:41] <kamalm> bguthro: I'm afraid I don't know how that relates to binaries on us.archive.ubuntu.com.
[21:42] <bguthro> kamalm: sounds like I'm one digit off.
[21:45]  * kamalm has recovered from momentary power loss here
[22:50] <manjo> hughhalf, around
=== bjf[afk] is now known as bjf
[23:37] <arand> Is Bug #547182 correctly targeted towards linux (since it happens on nouveau but not on nvidia-blob)?
[23:37] <ubot3> Malone bug 547182 in linux "Startup displays video artifacts from earlier 9.10 session" [Undecided,New] https://launchpad.net/bugs/547182
[23:37] <arand> Could I at this point comfortably mark it as confirmed or should I look for more confirmation?
[23:38] <arand> If previous is true, should it be sent upstream?
[23:39] <arand> Finally, since it does display clear data from the previous session, is this to be considered as a security issue? (And is it a bug in Karmic rather, that doesn't clear the video buffer properly?)
[23:40] <manjo> arand, do you have a dual boot setup ? 
[23:43] <arand> manjo: ubuntu kk & ll yes (and 3xWindows)
[23:45] <manjo> arand, does that commit you posted on the bug link fix the issue ? 
[23:46] <arand> manjo: Ah, no. That's the version (and from what I know the specific commit) of the upstream kernel I tested, and confirmed that the issue is still present, on.
[23:46] <arand> I'll clarify that in a comment...