[03:00] <arpu> thx for this https://launchpad.net/~chogydan/+archive/ppa/+packages
[03:00] <arpu> works greate 
[03:00] <arpu> now i can use lucid to work :>
[03:57] <jk-> arpu: what didn't work previously?
[04:07] <arpu> jk-,  response time of the gui on file copy 
[04:07] <arpu> or apt upgrade ...
[04:41] <mase_wk> hi guys, just wondering if there is a reason CONFIG_DMAR and CONFIG_INTR_REMAP is not set for the _server kernel in Lucid ?
[04:41] <mase_wk> according to http://www.linux-kvm.org/page/How_to_assign_devices_with_VT-d_in_KVM it's required for KVM PCI passthrough
[04:48] <jjohansen> mase_wk: no one has asked for it, I can added to the config review of M
[04:50] <mase_wk> jjohansen: well i think it was enabled in karmic. i performed an upgrade of a test system yesterday which uses PCI passthrough
[04:50] <mase_wk> and it seems PCI passthrough was supported / working in karmic.
[04:50] <mase_wk> so if this could be added it would be much appreciated
[04:51] <jjohansen> mase_wk: hrmm, I'll have to check on that but we didn't disable almost anything
[04:51] <mase_wk> hmm ok
[04:51] <mase_wk> thats interesting
[04:52] <jjohansen> mase_wk: I am unsure if it will get added to the Lucid kernel, we can look at SRUing it but no promises
[04:52] <mase_wk> SRU ?
[04:52] <jjohansen> stable release update
[04:52] <mase_wk> ah ok. well i dunno, maybe it's not required then. i am confused
[04:53] <mase_wk> see i'm getting the No IOMMU found
[04:53] <mase_wk> and i assumed it was because that config option was disabled in the kernel
[04:53] <mase_wk> since it was listed as required on the linux-kvm page
[04:54] <mase_wk> but if your saying that wasn't enabled in karmic either then maybe i'm hitting something else
[04:54] <mase_wk> since the PCI passthrough was working on karmic
[04:58] <mase_wk> jjohansen: do you know who the most appropriate person to talk to in the ubuntu virt team would be ? I should probably make sure that this is actually required before asking for it to be added to the config review.
[04:58] <jjohansen> mase_wk: kirkland knows the most about kvm
[04:58] <persia> It was set in karmic, it seems.
[04:59] <jjohansen> persia: interesting
[04:59] <mase_wk> persia: thanks for verifying that. I have upgraded all my test boxes so that saves me a reinstall at least
[04:59] <persia> I might be misreading the output of `grep -rin CONFIG_DMAR` though.
[05:00] <mase_wk> persia: is that for the -server kernel ?
[05:00] <persia> Seems to only be for x86_64 and ia64 though, not for i386.  Dunno why.
[05:00] <mase_wk> that makes sense i am using x86_64
[05:01] <jjohansen> persia: I am not seeing that
[05:01] <persia> Maybe I'm reading it wrong.  Maybe it's only enabled in ports.
[05:01] <mase_wk> persia: what do you mean by ports sorry ?
[05:01] <persia> I'm looking at the 2.6.31-21.59 source, but I'm not sure I'm reading it properly
[05:01] <persia> mase_wk: sparc/powerpc/ia64
[05:01] <mase_wk> ok , i understand now.
[05:02] <jjohansen> persia: I am looking at the configs right now for x86_64 karmic and the only one that is enabled is PCI Stub driver
[05:02] <jjohansen> the other 2 options are experimental and not enabled
[05:02] <persia> I'll trust your check more than mine :)
[05:03] <persia> maybe upstream kvm behaviour changed?
[05:03] <mase_wk> well my understanding was that they couldn't  / would never allow software iommu
[05:06] <mase_wk> jjohansen: the config you checked was that the -server kernel for x86_64 karmic ?
[05:09] <mase_wk> i guess i could create a lvm snapshot and install a kernel with it enabled and see if that works
[05:15] <jjohansen> mase_wk: yes, double and triple checked
[05:15] <jjohansen> mase_wk: yeah I would give that a try
[05:16] <mase_wk> k will do :)
[05:18] <mase_wk> i guess i could reinstall karmic just to make sure i'm not going completely mad
[06:43] <Laibsch> Can I build a Lucid Kernel on a Debian system (for testing only)?
[06:43] <Laibsch> or do I need a chroot on that Debian system?
[06:45] <persia> You'd be better off with a chroot, so you can install all the build-deps easily.  No reason you can't do it in Debian, but I'm not sure it's a well-tested path.
[06:47] <ikepanhc> yeah, and if your system need external kernel module, make sure it combiled with the same gcc and reasonable kernel header
[07:04] <Laibsch> I'll compile on the faster Debian machine natively now
[07:05] <Laibsch> I merely want to test a patch for a) compilability and b) functionality (things work as expected from the patch)
[07:05] <Laibsch> iF things break, I'll need to reconsider
[09:56] <ogasawara> https://wiki.ubuntu.com/MaverickReleaseSchedule
[10:29] <ogasawara> amitk: https://wiki.ubuntu.com/KernelTeam/Specs/KernelMaverickUbuntuDeltaReview
[10:29] <ogasawara> amitk: that has a list of patches (grouped by whom I thought was the owner) that I think should go upstream this cycle
[11:59]  * psurbhi breaks for lunch
[12:14] <cmug> Hi, 10.04 alternate does not work with my USB cddrive. What gives ?
[12:15] <cmug> Desktop and Server installed fine
[12:55] <Laibsch> Anybody I should subscribe to bug 521967 to make sure that patch now lands quickly?
[12:55] <ubot3> Malone bug 521967 in linux-backports-modules-2.6.32 "support for new atheros wifi chipset - AR2427/ath9k" [Medium,Triaged] https://launchpad.net/bugs/521967
[12:55] <Laibsch> tested both compilation and function on-device
[13:01] <fabbione> smb: btw.. i just remembered that there was already a bug related to the DVB HVR patch. but hell if i remember the number
[14:03] <amitk> hey all, we just started gardening our kernel wiki by creating a new namespace wiki.ubuntu.com/Kernel and moving to a more activity-based wiki like wiki.ubuntu.com/X
[14:21] <JFo> tgardner, is there anything we need to do for bug 521967 or will it land in updates?
[14:21] <ubot3> Malone bug 521967 in linux-backports-modules-2.6.32 "support for new atheros wifi chipset - AR2427/ath9k" [Medium,Triaged] https://launchpad.net/bugs/521967
[14:53] <bjf> amitk, good for you, let us know how that works out for you :-)
[14:53] <JFo> heh
[14:53] <JFo> manjo, are you still doing suspend/resume stuff/
[14:53] <JFo> err?
[14:53] <JFo> if so bug 44058 looks to be for you
[14:54] <ubot3> Malone bug 44058 in gnome-power "suspend when closing laptop lid doesn't work" [Unknown,In progress] https://launchpad.net/bugs/44058
[14:54] <JFo> it is HP hardware
[14:54] <JFo> morning bjf 
[14:54] <JFo> meant to say that first
[14:54] <JFo> <-brain still slow
[14:54] <bjf> moin JFo 
[14:54] <JFo> coffee brewing as we speak
[15:00]  * psurbhi sees a function definition within a function definition in grub legacy code
[15:00] <amitk> bjf: I _started_ the page, I move to newcore next week :-p
[15:01] <bjf> amitk, figures
[15:02] <JFo> amitk, ship jumper :-P
[15:03] <JFo> I bet it is an action item for me :)
[15:03] <JFo> amitk, as pete what the rest of "Why be a buddy, when you can..." is ;0
[15:03] <amitk> JFo: hehe
[15:03] <JFo> heh
[15:04] <mjg59> psurbhi: That is, by far, not the worst thing about grub
[15:05] <amitk> JFo: no actions, just establishing the namespace. We'll leave the fixing to the newbies ;)
[15:05] <JFo> heh, either way :)
[15:05] <psurbhi> mjg59, thats inspiring to know
[15:05] <psurbhi> :)
[15:08] <bjf> amitk, we're referred to as "the little people"
[15:08]  * JFo has a pot o gold for ye
[15:09] <bjf> amitk, isn't there a somehands attendees page somewhere?
[15:12] <amitk> bjf: *shrug* us little people dunno
[15:13] <bjf> amitk, I thought the lead of the newcore kernel team would be going
[15:14] <tgardner> JFo, I thought I'd wait until Luis releases an official 2.6.34 compat-wireless before backporting t o Lucid.
[15:14] <JFo> cool
[15:15] <JFo> just wanted to check :)
[15:15] <JFo> thanks tgardner 
[15:16] <tgardner> bjf, can you surf vger.kernel.org ?
[15:16] <bjf> tgardner, trying to catch a wave right now
[15:17] <bjf> tgardner, not looking good
[15:17] <bjf> tgardner, nope
[15:17] <tgardner> bjf, must be down. I've not received any LKML email in several hours
[15:18] <JFo> manjo, bug 540643 another HP S/R issue
[15:18] <ubot3> Malone bug 540643 in linux "[Hewlett-Packard HP Compaq 6910p (AK677US)] suspend/resume failure [non-free: hsfengine wl]" [Medium,Triaged] https://launchpad.net/bugs/540643
[15:19] <manjo> JFo, taking a look
[15:19] <JFo> cool, thanks man :)
[15:23] <kirkland> apw: what can you tell me about this stack trace: http://launchpadlibrarian.net/46615447/kernel_stack_trace
[15:23] <kirkland> apw: 10.04 host, 10.04 guest
[15:24] <kirkland> apw: virtio networking
[15:24] <kirkland> apw: guest continues running, but networking is dead
[15:32] <manjo> kirkland, looks like you are runing out of swap ?
[15:32] <kirkland> manjo: oh?
[15:32] <kirkland> manjo: checks ...
[15:33] <apw> kirkland, looks like we tried to recv a packet, and were not prepared to fail the allocation
[15:33] <apw> i'd say i'd expect the allocation to be allowed to fail and the packet simply be dropped
[15:34] <apw> as it wasn't and tripped an oom i'd say its a bug
[15:34] <kirkland> apw: cool, filed: https://bugs.launchpad.net/bugs/572368
[15:34] <ubot3> Malone bug 572368 in linux "virtio networking dies in KVM guest with kernel backtrace" [Undecided,New] 
[15:35] <apw> kirkland, so is it reproducible?
[15:42] <apw> kirkland, be worth trying to reproduce and monitor /proc/slabinfo to see if we are leaking
[15:42] <kirkland> apw: i rebooted;  will post as soon as it happens again
[15:42] <kirkland> apw: will monitor that
[15:43] <apw> kirkland, thanks, let us know
[15:49] <JFo> this looks interesting: bug 571977
[15:49] <ubot3> Malone bug 571977 in linux "[Lucid] Possible race condition involving rtc wakealarm when hibernating a system" [Undecided,New] https://launchpad.net/bugs/571977
[15:50]  * bjf heading to the airport, back on in a bit
[16:23]  * psurbhi quits for today...see u all on monday
[16:31] <JFo> tgardner, don't we have something for bug 521967 going in soon, or am I thinking of a different one?
[16:31] <ubot3> Malone bug 521967 in linux-backports-modules-2.6.32 "support for new atheros wifi chipset - AR2427/ath9k" [Medium,Triaged] https://launchpad.net/bugs/521967
[16:31] <JFo> heh
[16:31] <JFo> nevermind
[16:31] <JFo> that is a duplicate of the one from earlier
[16:31] <JFo> heh
[16:31] <JFo> <-brain needs more coffee
[16:56] <JFo> yet another interesting bug: bug 571807
[16:56] <ubot3> Malone bug 571807 in linux "Lucid fails to spin down hard-drive on shutdown" [Undecided,New] https://launchpad.net/bugs/571807
[16:56]  * jjohansen bets JFo is getting a deluge of interesting bugs
[16:57] <JFo> jjohansen would be absolutely right :)
[16:57] <JFo> most are actually coming in by way of people reassigning them from the ubuntu package
[16:58] <JFo> so they may have been filed, the reporter just didn't know the right package to assign
[17:01] <jjohansen> makes sense, its easier to file against
[17:04] <JFo> yeah
[17:04] <JFo> just sucks that by the time I get them they are stale
[17:05] <jjohansen> well you could triage all the ubuntu package bugs ;)
[17:12] <JFo> jjohansen, :-|
[17:14] <jjohansen> JFo: actually /me thinks it would make the problem worse as the sheer volume of bugs would make it so that on average you would find the kernel bugs even later
[17:28] <manjo> JFo, the previous hibernate bug seems to be either NOT a bug or a bug in pm scripts
[17:28] <manjo> I added a comment there 
[17:29] <JFo> cool, thanks manjo :)
[17:29] <JFo> nice recovery attempt jjohansen, but the suggestion is like a genie once it is out of the bottle. ;-)
[17:30] <JFo> you know what happens when you make suggestions like that? God kills a kitten :-P
[17:30] <JFo> j/k
[17:31] <manjo> JFo, you should mark 571807 invalid.. there is not any information in that bug to support his claim
[17:31]  * jjohansen will have to do penance and buy JFo a beer
[17:31] <JFo> jjohansen, I can live with that :-)
[17:32] <JFo> manjo, looking
[17:34] <manjo> say you are marking invalid coz there is no data in the bug to support the claim. either use ubuntu-bug to attach the logfiles 
[17:34] <JFo> I just asked him for more info
[17:35] <manjo> there are possibly hundreds of aspire ones and no one has reported data failure 
[17:36] <JFo> or odd spin down issues
[17:36] <JFo> but we will see what is said
[17:37] <sbeattie> jjohansen: your penance is to triage bugs against no package with hints: http://people.canonical.com/~brian/reports/no-package-clues.html :-)
[17:37] <JFo> sbeattie, :-)
[17:38] <manjo> JFo, https://launchpad.net/bugs/44058 is from 4yrs ago ? 
[17:38] <ubot3> Malone bug 44058 in gnome-power "suspend when closing laptop lid doesn't work" [Unknown,In progress] 
[17:39] <JFo> manjo, yep, but they have provided info from Lucid also 
[17:39] <JFo> same issue, they are telling me
[17:41] <manjo> JFo, I think I have a HP 5101 let me check... 
[17:41] <JFo> manjo, ok
[17:41] <JFo> could be an artifact left over from upgrade, but there are several people affected
[17:42] <jjohansen> sbeattie: argg, no!!!!
[17:43] <manjo> JFo, could be a regression in gnome-power-manager
[17:43] <manjo> checking 
[17:43] <JFo> manjo, k
[17:43] <JFo> jjohansen, ;P
[17:46] <manjo> JFo, looks like its a valid gnome-power-management bug
[17:47] <JFo> manjo, I see
[17:47] <JFo> do you have a link to a g-p-m bug?
[17:47] <JFo> or just in looking through the bug itself?
[17:48] <jjohansen> sigh, you would hope after 4 years it would have been fixed
[17:49] <JFo> jjohansen, you know as well as I, things fall through the cracks :-/
[17:49] <JFo> as much as we hate for them to
[17:50] <JFo> man, this hammock was money well spent :)
[17:50] <jjohansen> s/cracks/crevices/
[17:50] <JFo> yeah
[17:52] <manjo> JFo, not a kernel bug
[17:53] <JFo> manjo, cool
[17:53] <JFo> so I need to set it to g-p-m/
[17:53] <manjo> JFo, probably it is already
[17:54] <JFo> wow, so it is
[17:54] <JFo> so the kernel task is invalid?
[17:55] <manjo> yep we could call it that 
[17:58] <JFo> k
[18:02] <JFo> marked as such
[18:09] <bigcx2> hey all
[18:09] <bigcx2> i have a question about using make-kpkg
[18:09] <bigcx2> if i do something like make-kpkg --append-to-version some-foo
[18:09] <bigcx2> that string gets duplicated in the resultant deb that gets created, e.g:
[18:10] <bigcx2> linux-image-2.6.32.7-some-foo_2.6.32.7-some-foo-10.00.Custom_i386.deb
[18:10] <bigcx2> how do i get rid of that duplication and get rid of the "10.00.Custom_i386" string at the end
[18:24] <kro> hi
[18:24] <kro> got a question
[18:24] <kro> I want to use lucid... but plymouth doesn't seem to be compatible with my kernel, it dies on boot-up
[18:25] <kro> it's generic non-modular kernel optimised for headless usage.
[18:26] <kro> now the question: what does plymouth NEED? So far I tried adding support for framebuffer (VESA), DRM, AGP, ... but doesn't seem to be it
[18:26] <bigcx2> kro: do you need a splash screen?
[18:27] <kro> no
[18:28] <bigcx2> try taking the "splash" option out of your grub menu.lst and see what happens
[18:28] <kro> it's for dedicated servers... so the output is not needed except some debugging stuff
[18:28] <kro> yes, did that already...
[18:29] <bigcx2> and nothing?
[18:29] <kro> replaced it by "debug"
[18:29] <kro> http://demo.ovh.com/view/9aa6de29af7a198cac0e9a675c78f23f/0   screenshot of the KVM console
[18:30] <kro> I added "--debug" to the /etc/init/plymouth* files
[18:30] <kro> but doesn't really bring me further
[18:30] <bjf> ?
[18:31] <kro> bjf: init: plymoth main process (1421) killed by SEGV signal
[18:31] <kro> init: plymouth-splash main process (2275) terminated with status 2
[18:32] <Sarvatt> bigcx2: check out /etc/kernel-pkg.conf
[18:32] <bjf> kro, the '?' was a typo in the wrong window :-)
[18:32] <kro> bjf: :)
[18:33] <bigcx2> Sarvatt: aha! thanks
[18:34] <bigcx2> can these be set via environment variables?
[18:34] <bigcx2> before running?
[18:34] <bigcx2> or just in the conf, and debian/rules
[18:36] <bigcx2> kro: perhaps this applies to your problem? http://www.linode.com/forums/viewtopic.php?t=5522&sid=6a540b7bab2c42cebcddb265752594e6
[18:37] <kro> thx, but already tried that too :-)
[18:38] <bigcx2> kro: ok sorry, that was my best shot
[18:38] <bigcx2> kro: i'm not a kernel dev, just camping out
[18:38] <kro> I'm stuck since nearly two days now, so I hit the google bookmark quite a lot :-)
[18:38] <bigcx2> :)
[18:38] <bigcx2> heh
[18:40]  * JFo does a long overdue git fetch on his kernel sources
[18:40] <JFo> apparently very long overdue
[18:49] <kro> how about the "ply_terminal_open:terminal /dev/tty7 is already open" message - is this the fatal one?
[18:55] <bigcx2> kro: probably a good guess
[18:56] <bigcx2> kro: but then again here's a log of somebody having that exact same error, but w/o failure
[18:57] <bigcx2> http://users.csc.calpoly.edu/~dgoyette/no_splash_for_you.log
[19:00] <kro> yeah... that shouldn't be the cause for such an ungraceful exit...
[19:00] <bigcx2> kro: is this your own kernel, or a stock one
[19:01] <kro> "my" kernel (our company kernel)
[19:01] <bigcx2> https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/571258
[19:01] <ubot3> Malone bug 571258 in plymouth "plymouth main process (341) killed by SEGV signal" [Undecided,New] 
[19:02] <kro> [drm] Initialized drm 1.1.0 20060810   <== my log stops before that line... maybe I should look in that direction
[19:02] <kro> bigcx2: thx, didn't see that one yet :)
[19:03] <bigcx2> np
[19:42] <mvk> is that 3d support of the built-in kernel module for radeon buggy?
[19:51] <mvk> lets see if i can trick this radeon driver into panicing again 
[20:34] <mdz> can anyone recommend a USB wifi dongle which is well supported?
[20:38] <Dandel> mdz, look for edimax EW-7717Un wifi adapter, the drivers should be included in 10.04 since 9.10 also has the driver.
[20:39] <mdz> Dandel, thanks for the suggestion, looking at it
[20:40] <mdz> seems to have very bad reviews on http://www.newegg.com/Product/Product.aspx?Item=N82E16833315081&Tpk=EW-7717Un
[20:41] <Dandel> people on newegg can and will give a bad review because a printer "seems" to have 6 cartridges, when it's really 4 cartridges and a pair of print heads.
[20:41] <Dandel> same rule of thumb applies to usb devices
[20:41] <mdz> Dandel, true, it's not always reliable. these are "stopped working after 2 months" kind of reviews though
[20:42] <mdz> another one I'm looking at is http://www.newegg.com/Product/Product.aspx?Item=N82E16833127244&cm_re=usb_wifi_adapter-_-33-127-244-_-Product
[20:42] <mdz> which looks like it should be supported by rt2870sta
[20:43] <mdz> but then there's bug 507375
[20:43] <ubot3> Malone bug 507375 in linux "Wireless DLINK Adapter DWA-140 not working" [Undecided,Confirmed] https://launchpad.net/bugs/507375
[20:43] <mdz> seems to be one of those devices which has different revs, indistinguishable before purchase
[20:45] <Dandel> look at the  EDIMAX EW-7718Un device then.
[20:46] <Dandel> that uses the RT2870 chipset.
[20:47] <mdz> Dandel, I think I will, thanks
[20:47] <Dandel> anyways, i never trust newegg reviews until the device has 300+
[20:48] <mdz> Dandel, have you tried 802.11n? WPA2?
[20:48] <Dandel> 802.11g using madwifi tho.
[20:48] <Dandel> no, but the router i have is 802.11n with wpa2.
[20:49] <Dandel> and yes, i'm using wpa2 right now.
[20:50] <mdz> Dandel, madwifi? I thought it was an rt2870?
[20:50] <Dandel> no, that's what i am using right now.
[20:51] <Dandel> My laptop wifi card  is the atheros AR5001.
[20:51] <mdz> Dandel, oh, I was wondering if you'd had success with WPA2 with the adapter you were recommending
[20:52] <mdz> the edimax
[20:52] <Dandel> haven't checked.
[20:52] <Dandel> since the devices uses the rt2870sta chipset you can go to realtek's website and find out for sure.
[20:53] <Dandel> oops... rt2870 is ralink
[20:55] <mdz> yes, confusing that
[20:58] <Dandel> the ralink driver that is proprietary does support wpa2 from what i am reading.
[20:59] <Dandel> oh and the rt2770 v2.3.0.0 does appear to fall under the gpl license.
[22:43] <kamalm> Advice?... My "fakeroot debian/rules binary-generic" is failing at the final packaging step with:
[22:43] <kamalm>   dpkg-deb - error: (upstream) version (`unknown') doesn't contain any digits
[22:43] <kamalm> What might I have done to get into this state and how might I get out of it?
[22:50] <crimsun> mdz: certainly anything atheros ar9285-based is rock-solid IME
[22:51] <crimsun> kamalm: interesting; that implies something is fubar in debian/changelog
[22:51] <kamalm> crimsun: its certainly possible that I've fu'd it bar -- but I think this is what I usually do...
[22:51] <kamalm>   linux (2.6.32-21.33~kamal~dell_155x_bri) lucid; urgency=low
[22:54] <crimsun> nah, that seems fine, but something is overriding it
[22:54] <crimsun> i.e., it becomes unknown-foo at some point, which is odd
[22:57] <jjohansen> kamalm: hrmm, I have hit that before I trying to remember what caused it
[22:57] <kamalm> hmmm.  I just changed it to   linux (2.6.32-21.33~kamal) lucid; urgency=low    and it worked -- sort of ...
[22:57] <kamalm> It built these .debs:
[22:57] <kamalm> linux-headers-2.6.32-21-generic_2.6.32-21.33~kamal_amd64.deb
[22:57] <kamalm> linux-image-2.6.32-21-generic_2.6.32-21.33~kamal_amd64.deb
[22:58] <jjohansen> kamalm: okay what is wrong with those?
[22:58] <kamalm> I think bigcx2 was asking about this same issue -- the version numbers seem unusually "redundant" there.
[22:59] <kamalm> no, I take it back -- i guess that's "normal".
[23:00] <jjohansen> yeah
[23:01] <kamalm> I still don't know what's wrong with my original version string -- I've used that same pattern  (~kamal~foo_bar_bing) successfully before.
[23:02] <jjohansen> hrmm, no idea unfortunately
[23:04] <kamalm> ok, anyway -- I'm unstuck -- thanks for the help folks :-)