[02:12] <bjf[]> exit
[02:12] <bjf[afk]> -EWRONGWINDOW
[08:11]  * apw yawns
[08:15] <RAOF> apw: You should sleep in, then :)
[08:18] <apw> pgraner, frylock is off the world ... for the 3rd time in two days ... both links to nowhere
[08:32] <apw> pgraner, actually dsl and ubuntu point to the same IP address ?
[09:20] <kraut> moin
[09:38] <ikepanhc> ouch, sent a empty subject to k-t list
[09:53] <ericm> ikepanhc, yeah - but fortunately it didn't end up in my spam box
[09:53] <apw> cking, morning ?
[09:54] <ikepanhc> ericm: ya, fortunately.
[09:55] <ericm> ikepanhc, it's quite old kernel, why the building issue was revealed recently?
[09:56] <ikepanhc> ericm: oh, the compile error happen after rebase to lastest hardy master branch
[09:56] <ericm> ikepanhc, I see
[09:56] <ikepanhc> ericm: it wasnt there last week
[10:17]  * apw pokes pgraner 
[10:18] <ikepanhc> apw: good question on lquest - I dont think we need lguest on netbook branch
[10:19] <ikepanhc> s/lquest/lguest
[10:20] <ericm> apw, I cannot connect to pgraner's machine, what about you?
[10:21] <apw> ericm, indeed been down all morning
[10:22] <cooloney> try tyler
[10:22] <apw> i think both are out 
[10:22] <ericm> apw, I guess helena is also down
[10:23] <apw> ericm, that has been announced as down, the machine is going to boston
[10:23] <apw> but it has been 6 damn weeks in transition
[10:23]  * ericm has to build a kernel on his tiny mini fan-noisy slow machine now
[10:24] <apw> pgraner should be awake within the hour and we should get .mills back
[10:30] <ericm> any one has hint for the error below: ERROR: ld.so: object 'libfakeroot-sysv.so' from LD_PRELOAD cannot be preloaded: ignored.
[10:30]  * ericm is doing a fdr binary
[10:32] <ikepanhc> ericm: I just ignore the error message. fdr binary still give me the linux-image.deb and the deb works
[10:33] <ericm> ikepanhc, you are having the same issue? interesting - this never happens on pgraner's machine (never noticed the release difference though)
[10:34] <apw> ericm, i've seen that before i think but cannot remember what it was about any more sorry
[10:43] <cooloney> ericm: i got that error several times
[10:43] <cooloney> ericm: so a) sudo su to get root to build the package
[10:43] <cooloney> b) sbuild
[10:44] <cooloney> that's might be a issue from fakeroot upstream
[10:44] <cooloney> i found that bug was tracked in debian's bug list
[10:48] <smb> lag, Hey just wanted to let you know that your "make perf more useful in case of error" change likely sneaks into Lucid anyway when apw does his abstracted magic. :)
[10:48]  * smb waves to apw
[10:48] <apw> smb, indeed so ... its in the ones i am test building now
[10:49] <lag> Good news :)
[10:49] <smb> apw, Did I expect too much or is there only Karmic master updated for now? I fetched but only master changed...
[10:49] <lag> Will my "fdr editconfigs" change get in?
[10:49] <smb> I believe to have seen that too
[10:50] <apw> smb, i thought the plan was i did master, you tie the bow on that than we can rebase the others and do them too
[10:50] <apw> (ie. i can rebase them during the day)
[10:50] <smb> apw, I think you are right
[10:50] <apw> the plan may be flawed but i think that was the plan
[10:50] <apw> pgraner, ping
[10:51] <smb> apw, Meh, I think its alright. I do the ties and push, can I hand test building that to you?
[10:52] <apw> smb, yep... i have to build it anyhow
[10:52] <smb> Doh!
[10:52] <apw> doh ?
[10:52] <smb> apw, You surely have
[10:53] <apw> yep ... _if_ the build boxes come back of course so i can free up my local box for it
[10:53] <smb> apw, And me just making little updates to the changelog won't break that
[10:53] <apw> there is that too, though i thought there may be more updates coming for -proposed for karmic i forget
[10:54] <smb> apw, No, I know nothing more for KArmic
[10:54] <apw> i'll re-test buuld it once i have a free box anyhow
[10:57] <smb> apw, You have something with the bow tie on when you pull
[10:57] <apw> smb, thanks
[10:59] <smb> apw, Thanks for going through the rebases. I think to remember there will be a little fallout with the debian.env when doing those. Anything else to expect? Or simpler let me know what happens. :)
[10:59] <apw> i think it was simpler than i expected actually, but yes will let you know
[11:09] <ogra> were the omap3 udeb changes for lucid already uploaded before the new d-i was uploaded yesterday ? 
[11:13] <ericm> smb, reviewing the DOS CR/LF format issue with Marvell code, it looks like a _too_ big issue, (https://pastebin.canonical.com/33183/)
[11:14]  * apw doesn't remember any omap3 stuff aimed at lucid
[11:15] <apw> ogra, the bug we had was for maverick was it not
[11:15] <ogra> the missing USB NIC drivers in udbes ? 
[11:15] <ogra> *udebs
[11:15] <ogra> no, that was lucid omap3
[11:15] <ogra> fixed several weeks ago by mpoirier
[11:15] <apw> that i don't think i remember that at all, presumably someone else was dealing with that, so ignore me
[11:16] <ogra> LP#588805: enable armel-omap udebs for netboot use
[11:16] <ogra> you commented on it 6 days ago
[11:17] <ogra> oh, though thats a different bug number
[11:17] <ogra> bug 584920
[11:17] <ubot2> Launchpad bug 584920 in linux-ti-omap (Ubuntu) "netinstall fails, it has no network driver for moschip (affects: 1) (heat: 264)" [Medium,Fix committed] https://launchpad.net/bugs/584920
[11:17] <ogra> pull request from may 27th
[11:17] <ogra> ~two weeks ago
[11:18] <ogra> since thats stuff needed for netinstall, having it in before d-i gets rebuild is essential
[11:18] <ogra> else it makes no sense :)
[11:30] <cooloney> ericm: try dos2unix?
[11:30] <apw> ogra, i would not be supprised if its not yet uploaded, as we have been under -security for the last 3 weeks
[11:31] <ogra> hrm, k 
[11:31] <ericm> cooloney, yeah - but the format itself isn't a big issue, a noisy patch and the problem of application of subsequent patches would be the biggest issue
[11:31] <apw> the SRU process is not in the least bit determininstic time wise especially when -security pops up its ugly head
[11:32] <apw> ogra, if your patch has a bug link in it then its not showing up on ti-ompa
[11:32] <ogra> yeah, understood
[11:32] <ogra> ompa lompa :)
[11:32] <ogra> its not my patch
[11:33] <ogra> https://lists.ubuntu.com/archives/kernel-team/2010-May/010757.html
[11:33] <ogra> the ,mail had a buglink
[11:34] <ogra> and according to smb it was applied to the tree two days ago
[11:34] <apw> ogra, ok found it ... it'll be in the next upload, its right at the tip of the tree
[11:34] <ogra> i just dont know if it went in with an upload
[11:34] <ogra> ok
[11:34] <apw> thats post -security which is only just in
[11:34] <ogra> ok
[11:34] <ogra> no prob then, i just want to know what to tell users that ask 
[11:46] <ghostcube> hmmm ureadhead still gets killed for me at startup :) is there anything known about
[11:54] <cking> ghostcube, i think it's known about: bug 491943
[11:54] <ubot2> Launchpad bug 491943 in ureadahead (Ubuntu) (and 1 other project) "Kernel trace buffer should be set to less unrealistic value (affects: 11) (dups: 2) (heat: 54)" [High,Triaged] https://launchpad.net/bugs/491943
[11:55] <ghostcube> cking: thx looking :)
[11:56] <ghostcube> hmmm yeah my system has 4 gig mem too 
[11:57] <ghostcube> looks nearly the same must check this athome later thx for the bug
[11:57] <cking> my pleasure
[13:54] <ericm> apw, what if I want to change a blueprint to M+1 (it was target for M, but apparently the topic/work grows more than that)?
[14:00] <apw> ericm, is there work in M still?  if so leave it as it is, but then move the target on the blueprint front page to N when that starts existing
[14:00] <ericm> apw, what do you mean by "when that starts existing"? after UDS-N?
[14:01] <apw> i am not sure uds-n even exists as a goal really
[14:01] <apw> as yet
[14:01] <ericm> apw, no - checked and not available in the drop down box
[14:01] <apw> just put the work-items which flow out under like
[14:01] <apw> Work Items for NN:
[14:02] <apw> or something which won't match our current release, and they will not show up
[14:02] <ericm> apw, I see
[14:02] <apw> arm work going to take forever ?
[14:31] <sebjan> Hello, I am wondering if BUG 507503 was fixed in .34 upstream (I see some patches from .34). Anyone to confirm? Thanks!
[14:31] <ubot2> Launchpad bug 507503 in linux-ti-omap (Ubuntu Lucid) (and 5 other projects) "VFP/NEON state is not preserved around signal handlers, causing state corruption between user processes (affects: 1) (heat: 10)" [High,Fix released] https://launchpad.net/bugs/507503
[14:37] <pgraner> cooloney: ping
[14:54] <cooloney> pgraner: hey, pete
[14:54] <apw> sebjan, i thin that was fixed upstream yes, i am pretty sure it was a backport in our trees
[14:54] <pgraner> cooloney: hey some one was asking about an OMAP bug in the scroll back:  [09:32] <sebjan> Hello, I am wondering if BUG 507503 was fixed in .34 upstream (I see some patches from .34). Anyone to confirm? Thanks!
[14:54] <ubot2> Launchpad bug 507503 in linux-ti-omap (Ubuntu Lucid) (and 5 other projects) "VFP/NEON state is not preserved around signal handlers, causing state corruption between user processes (affects: 1) (heat: 10)" [High,Fix released] https://launchpad.net/bugs/507503
[14:55] <pgraner> cooloney: and apw just answered
[14:55] <pgraner> cooloney: so never mind
[14:55] <cooloney> pgraner: thanks for ping me this. hehe
[14:55] <cooloney> apw is a nice man, always help us
[14:56] <cooloney> apw and sebjan, the patch we backported into our lucid tree might be different from upstream. I need to double check
[14:57] <cooloney> since at that time, we applied the patch from arm mail list
[14:57] <cooloney> but it might be changed a little bit after rmk reviewed before it entered upstream mainline
[14:59] <sebjan> cooloney: yes, the lucid backport is different, and the .34 upstream contains the latest patch revision (v5) discussed in this thread: http://thread.gmane.org/gmane.linux.ports.arm.kernel/58722/focus=58724
[15:01] <cooloney> sebjan: got it, thanks for heading up.
[15:02] <cooloney> sebjan: i think the upstream version is the right one, in lucid, we just wanna fix the bug in .31/.32/.33 kernel
[15:02] <cooloney> sebjan: so if you rebase the on .34, you can ignore that backported VFP patches. 
[15:03] <sebjan> cooloney, apw, pgraner: thanks guys for checking!
[15:03] <sebjan> cooloney: yep, this is what I did, and wanted to confirm as the patch content did not seem obvious to me :) Thanks!
[15:19] <JFo> moin bjf 
[15:19] <bjf> JFo, i'll take your word for that
[15:19] <bjf> bjf, not awake yet
[15:20] <JFo> speaking of which...
[15:20]  * JFo goes for more coffee
[15:40] <tgardner> ogasawara, please hold off on my LP591416 pull request. I'm working with upstream to build a better solution.
[15:41] <statik> hi hi
[15:41] <statik> one of my colleagues is having trouble with an e1000e on the maverick kernels (works fine in lucid)
[15:42] <statik> I wanted to see whether the patch talked about in this thread was in the maverick kernel already http://kerneltrap.org/mailarchive/linux-netdev/2010/5/11/6276964
[15:42] <statik> i'm kinda ignorant about kernel stuff, what is the right way for me to get the tree for the ubuntu kernels?
[15:43] <tgardner> statik, git clone git://kernel.ubuntu.com/ubuntu/ubuntu-maverick.git
[15:43] <statik> thanks tgardner
[15:44] <tgardner> statik, drivers/net/e1000e/hw.h:#define E1000_DEV_ID_PCH_D_HV_DM                0x10EF
[15:45] <statik> thanks
[15:46] <statik> dmesg seems to show that it is failing probe during boot, and the patch talked about does a hw reset
[15:46] <statik> http://git.kernel.org/?p=linux/kernel/git/davem/net-next-2.6.git;a=commitdiff;h=627c8a041f7aaaea93c766f69bd61d952a277586
[15:46] <statik> i have no idea what i'm talking about, but figured this seemed relevant and worth double checking whether it was present or not
[15:51] <tgardner> statik, that commit is in Maverick. 'e1000e: Reset 82577/82578 PHY before first PHY register read'
[15:52] <statik> tgardner, thanks :) my clone was still running. nessita has a bug report here: https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/591702 , and the dmesg shows a line like this: e1000e: probe of 0000:00:19.0 failed with error -3 
[15:52] <apw> tgardner, in which upload ?
[15:52] <ubot2> Launchpad bug 591702 in linux (Ubuntu) "After upgrade lucid -> maverick eth0 interface is gone (dup-of: 591707)" [Undecided,New]
[15:52] <ubot2> Launchpad bug 591707 in linux (Ubuntu) "After upgrade lucid -> maverick eth0 interface is gone (affects: 1) (dups: 1) (heat: 14)" [Undecided,New]
[15:53] <tgardner> apw, I'm looking at the tip of the Maverick tree, so its at least in -rc2
[15:53] <apw> statik, which kernel are you testing when seeing this?
[15:53] <apw> cat /proc/version_signature
[15:54] <manjo> tgardner, olimpiya was a good suggestion 
[15:54] <statik> nessita, ^ can you check the version_signature ?
[15:54] <statik> it was from a dist-upgrade yesterday
[15:55] <tgardner> which should be Ubuntu-2.6.35-2.2
[15:55] <JFo> bjf, got the boxes
[15:55] <JFo> just 2 of them yes?
[15:56] <tgardner> statik, oh, maybe not. -meta has not been updated.
[15:56] <nessita> tgardner: I'll let you know in a sec
[15:56] <nessita> statik: version_signature where?
[15:56] <statik> nessita, cat /proc/version_signature as apw suggested above
[15:56] <JFo> run that from a terminal
[15:57] <nessita> Ubuntu 2.6.35-1.1-generic 2.6.35-rc1
[15:57] <nessita> statik: thanks, I missed apw comment above
[15:58] <tgardner> nessita, can you download and try https://edge.launchpad.net/ubuntu/maverick/+package/linux-image-2.6.35-2-server ?
[15:58] <nessita> tgardner: yessir
[15:59] <tgardner> http://launchpadlibrarian.net/49983143/linux-image-2.6.35-2-server_2.6.35-2.2_amd64.deb
[16:14] <nessita1> tgardner: no luck with rc2 kernel, look http://nessita.pastebin.com/A9zdSyWt
[16:15] <tgardner> nessita: ok, I'll see if I can grok the error code (right after I scarf some breakfast)
[16:16] <nessita1> tgardner: ok, I'm in the troubled machine right now, I plugged in a dongle
[16:16] <nessita1> tgardner: so I can copy and paste more easily :-P
[16:21] <bjf> JFo, you got both pkgs?
[16:23] <JFo> yep
[16:27] <tgardner> nessita: has this e1000e _ever_ worked with any kernel?
[16:31] <apw> ogasawara, yo ... 
[16:31] <ogasawara> apw: yo
[16:31] <apw> seems we had some FTBS's :(
[16:31] <ogasawara> apw: yep, just looking at those.  it's the firmware not being optional
[16:31] <apw> yeah i think we may have to make them optional again
[16:32] <ogasawara> apw: I agree.  I'm gonna send a patch to flip them back.
[16:32] <apw> though you should speak to tgardner 
[16:32] <ogasawara> tgardner: ^^
[16:32]  * ogasawara jump on mumble
[16:32] <nessita> tgardner: yes, of course
[16:33] <nessita> tgardner: until yesterday 7pm it was working
[16:33] <nessita> tgardner: and right now it works with kernel 2.6.32
[16:33] <nessita> tgardner: which was the kernel from lucid
[16:35] <nessita1> tgardner: http://nessita.pastebin.com/UHKNCXKM
[16:36] <cking> manjo, ping
[16:36] <manjo> cking, pong 
[16:36] <cking> manjo, hows that UEFI box getting on? Did you get any joy from it?
[16:37] <manjo> cking, I am talking to 2 people at intel regarding EFI, unfortunately looks like most of the EFI devs are going to be in santa clara during the plugfest week 
[16:38] <manjo> cking, I read up some docs yesterday regarding EFI 
[16:39] <manjo> cking if you hop on some channel on mumble we can chat ? 
[16:39] <cking> OK - gotta bear with me - I've got a migrane
[16:39] <manjo> oh sorry to hear that 
[16:39] <manjo> I am looking at the grub2 code right now 
[16:39] <tgardner> nessita, ok, this seems like a serious regression. 
[16:39] <manjo> cking, I read your wikis on EFI and they are pretty detailed
[16:40] <manjo> was wondering with your permission I could move it to our ubuntu wiki ?
[16:40] <cking> manjo, hold on.. 
[16:40] <nessita> tgardner: how can I help debug?
[16:40] <manjo> cking, ok be back with some more coffee
[16:42] <tgardner> nessita: the first thing is to make sure it really, really works with 2.6.32 lucid. please reboot and paste the whole dmesg just to make sure you've not coincidentally encountered a HW issue. I'd be really surprised to find a regression in a well supported driver like e1000e.
[16:42] <tgardner> reboot to lucid, that is.
[16:43] <nessita1> tgardner: rebooting to 2.6.32
[16:49] <nessita1> tgardner: dmesg for kernel 2.6.32 attached to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/591707
[16:49] <ubot2> Launchpad bug 591707 in linux (Ubuntu) "After upgrade lucid -> maverick eth0 interface is gone (affects: 1) (dups: 1) (heat: 14)" [Undecided,New]
[16:49] <nessita1> tgardner: I'm currently using net connectivity through eth0 and e1000e
[16:51] <dob1> hi, after installing the new ubuntu release on my acer 5100 this problem https://bugs.launchpad.net/ubuntu/+source/linux/+bug/446274 happen again, with the 9.04 the problem wasn't present, with the precedent release to 9.04 (i don't remember the version number) the problem was present, i know is very difficult to find the cause, but someone has some idea to what is changed in the kernel in these releases that can create the p
[16:51] <ubot2> Launchpad bug 446274 in linux (Ubuntu) "System freeze with ACER aspire 5100 (affects: 2) (heat: 12)" [Undecided,Incomplete]
[16:51] <tgardner> nessita: cool, now if you could do the same for the 2.6.35-rc2 Maverick kernel? 
[16:51] <nessita1> tgardner: yessir
[16:52] <dob1> it's a very bad problem, every time i had to hard reboot the system
[16:52] <dob1> and i can't find nothing in log or what else
[16:54] <apw> dob1, sadly there is such a huge ammount of stuff has changed between 9.04 and 10.04 LTS, that we're pretty unlikely to find the issue
[16:54] <apw> does the previous kernel still boot for you with the updated userspace ?
[16:54] <dob1> apw: i don't have it anymore
[16:54] <apw> dob1, the next steps are normally to try and find out if upstream has this fixed via the mainline builds
[16:55] <apw> dob1 you can likely find it in the lauchpad librariant, it keeps every kernel forever
[16:56] <nessita> tgardner: second output attached to bug report
[16:56] <dob1> apw: well can i find some precompiled kernel with no ubuntu patches ?  or i can download it from kernel.org
[16:56] <dob1> just to test
[16:56] <apw> dob1, yep in the miainline archive: https://wiki.ubuntu.com/KernelTeam/MainlineBuilds
[16:57] <apw> report any testing results to the bug
[16:58] <dob1> apw: the problem is that when this problem happen i can't do nothing, the pc is freeze, no log , it doesn't respond to ping, like dead, i have to hard reboot
[16:58] <apw> dob1, so you can very easily tell if its happehing or not on that kernel then
[16:58] <apw> when does it happen, instantly at boot or do you have to do something to trigger it
[16:59] <dob1> it can happen at boot, after hours i am using the pc, there is no applications that i can identify as a cause
[17:00] <apw> if you can trigger it at boot, then booting without quiet and splash on the command line may get you something on the screen to report
[17:01] <dob1> apw: to be clear, i have to login to the system
[17:01] <apw> never occurs before that ... hrm ... 
[17:01] <apw> a pig to debug for sure
[17:02] <dob1> it was happen 1 time before the login, i was at login screen, the screen was ok but the sound of the login was repeated a lot of time, and it was freezed, but not stripe pattern  on the screen
[17:03] <dob1> as sound of login, i mean the ubuntu login music, you understand what i mean
[17:03] <tgardner> nessita, 'apport-collect 591707' to get the rest of your system info. Looks like you've got some ATI nouveau issues as well.
[17:04] <tgardner> is this a thinkpad or something?
[17:04] <nessita> tgardner: yes, video sucks at the moment, though I have a nvidia card...
[17:05] <nessita> tgardner: ImportError: No module named gi after running apport-collect, though it keeps running
[17:07] <tgardner> nessita, do you remember ever havinf flash issues with this e1000e? there was a serious problem during Hardy days when flash could get partially corrupted.
[17:08] <tgardner> thinkpads were particularly vulnerable
[17:08] <nessita> tgardner: this is a new box so I only had lucid installed on it
[17:08] <nessita> tgardner: first installation was during March this year
[17:09] <tgardner> s/ATI nouveau/nVidia nouveau/ in my previous comment. I get 'em confused sometimes
[17:09] <tgardner> nessita, then you should be OK there
[17:09] <tgardner> firmware wise....
[17:11] <nessita> tgardner: apport-collect finished
[17:13] <tgardner> nessita, got it, thanks. I know there are a couple of these thinkpads within the canonical IS group. I'll see if I can get someone to duplicate your issue.
[17:14] <nessita> tgardner: ok, let me know if I can do anything else
[17:15] <tgardner> nessita, maybe one last thing, attach the 'sudo dmidecode' to the report so I have the BIOS versions, etc.
[17:16] <nessita> coming right up
[17:16] <tgardner> I wish apport-collect did taht autmatically
[17:17] <bjf> tgardner, am talking to cking about adding that to apport
[17:17] <nessita> tgardner: fill a bug! :-P
[17:17] <nessita> tgardner: output attached
[17:17] <tgardner> bjf, why would cking be doing it?
[17:18] <bjf> tgardner, he wants the information for some of the bios testing work he is doing
[17:18] <bjf> tgardner, i'll do the work to apport
[17:19] <tgardner> bjf, it means you'll have to run apport-collect as sudo
[17:19] <bjf> tgardner, yup, know that
[17:29] <bjf> tgardner, there is code in apport to collect certain logs as root, gksudo, ksudo, or whatever will run as necessary
[17:30] <tgardner> cool
[17:36] <tgardner> nessita, just for kicks and giggles, can you try the nVidia driver? 
[17:37] <nessita> tgardner: I'd love, how can I? aptitude complains with the xorg packages
[17:38] <tgardner> nessita, it used to be system/administration/hardware manager
[17:40] <nessita> tgardner: as per that application, NVIDIA accelerated graphics driver (version 173) is activated and currently in use
[17:41] <nessita> tgardner: and I can not update xserver-xorg-core because it breaks xserver-xorg-input-7
[17:41] <nessita> xserver-xorg-core breaks xserver-xorg-video-6 (provided by nvidia-173 173.14.22-0ubuntu11, ...)
[17:41] <tgardner> nessita, perhaps the best way to test this is to reinstall Lucid and then run the LTS backport kernel? That would get your video issues out of the loop.
[17:42] <tgardner> maverick is in a bit of flux right now
[17:42] <tgardner> wrt X packages
[17:42] <nessita> yes :-)
[17:43] <tgardner> nessita, you can get the LTS backported kernel from http://ppa.launchpad.net/kernel-ppa/ppa/ubuntu
[17:43] <nessita> tgardner: what do you mean with "reinstall" Lucid? reinstall from scratch?
[17:43] <tgardner> nessita, uh, yep. I know that might be painful
[17:44] <nessita> tgardner: *a lot* :-/ dependencies for ubuntu one are hige
[17:44] <nessita> huge*
[17:45] <tgardner> nessita, well, I hesitate to bug the upstream guys about this 'cause the _first_ thing they'll bitch about is the video faults you have in your dmesg.
[17:45] <nessita> tgardner: I see. Let me talk about this with statik
[17:45] <tgardner> once you have an oops, all bets are off for future behaviors.
[17:46] <nessita> statik: ping
[17:47] <tgardner> nessita, in the future you should try the LiveCD first before stepping off the edge :)
[17:48] <nessita> tgardner: part of my job is to do this
[17:48] <nessita> tgardner: isn't argument enough to show that kernel 2.6.32 works?
[17:48] <nessita> tgardner: for upstream guys, I mean
[17:48] <tgardner> nessita, not with an oops in your dmesg
[17:48] <nessita> tgardner: video is totally broken in 2.6.32 but net works
[17:48] <nessita> ok
[17:50] <tgardner> nessita, in fact, if you _do_ reinstall, then just install the server (no video issues). you can always update by installing ubuntu-desktop
[17:51] <nessita> tgardner: reinstall lucid or maverick?
[17:51] <tgardner> nessita, reinstall lucid. Is this your only machine?
[17:52] <nessita> tgardner: nopes, I have a laptop as well, with Lucid in it
[17:52] <tgardner> nessita, um, I thought this _was_ your laptop. Thinkpad, right?
[17:53] <nessita> tgardner: nopes, laptop is a toshiba satellite (works well so far)
[17:53] <tgardner> that would explain the DMI information.
[17:53] <nessita> tgardner: computer with this net issue is a desktop
[17:53] <tgardner> OK.
[17:57] <nessita> tgardner: want me to add those details to the report?
[17:57] <tgardner> nessita, lets just start with the Lucid server re-install first, then add the LTS kernel and report on the results of that.
[18:11] <nessita> tgardner: just to be sure, how which one would be the LTS kernel backport and how shall I install it? dpkg -i?
[18:14] <tgardner> nessita, use can do that, or just add the repo to your apt sources, e.g., 'echo "deb http://ppa.launchpad.net/kernel-ppa/ppa/ubuntu lucid main" | sudo tee /etc/apt/sources.list.d/kernel-ppa.list', then 'apt-get update;apt-get install linux-image-server-lts-backport-maverick'
[18:14] <tgardner> s/use/you/
[18:15] <nessita> right, thanks
[19:26] <ppires> hi there. am i wrong if i put a kernel package building question here?
[19:29] <jjohansen> -> Lunch
[20:17] <ogasawara> tgardner: heh, I forgot that enabling bnx2 in armel results in additional build failures which I've hopefully fixed up now.
[20:18] <tgardner> ogasawara, how much fun could that be :)
[20:18] <ogasawara> tgardner: so hopefully the latest test build will finish soon and then I'll upload
[20:19] <tgardner> ogasawara, what kind of fixes did you have to make?
[20:19] <ogasawara> tgardner: needed to define dma_get_ops
[20:19] <ogasawara> drivers/net/bnx2.c:3102: error: implicit declaration of function 'get_dma_ops'
[20:20] <ogasawara> make that needed to define get_dma_ops
[20:20] <tgardner> ogasawara, just a header file inclusion 
[20:20] <tgardner> ?
[20:20] <tgardner> I'm wondering if its an upstreamable patch
[20:21] <ogasawara> I just threw in a #define get_dma_ops(dev) platform_dma_get_ops(dev)
[20:44] <dupondje> whats the best way to make a bugreport for a kernel bug ?
[20:45] <tgardner> dupondje, 'ubuntu-bug linux'
[20:47] <dupondje> [ 2313.242321] BUG: unable to handle kernel NULL pointer dereference at (null)
[20:47] <dupondje> [ 2313.242329] IP: [<ffffffffa025e0d6>] iwl3945_get_channels_for_scan+0xc6/0x210 [iwl3945]
[20:47] <dupondje> and firefox gets locked totally .. weird thing :)
[21:01] <dupondje> https://patchwork.kernel.org/patch/103568/
[21:02] <dupondje> don't need to make bug for it then? As it hopefully gets fixed upstream ?
[21:07] <tgardner> ogasawara, dave says he's gonna take that net patch that I sent you earlier today.
[21:07] <ogasawara> tgardner: cool, I've already applied it locally
[22:18] <manjo> bjf, where can I get the scripts to generate the modified ISO?
[22:38] <manjo> bjf, found it... but I get an error chroot: cannot run command `mount': Exec format error
[22:39] <bjf> manjo, you got it from the kteam-tools repo
[22:39] <manjo> yes
[22:40] <manjo> bjf, do I need to fun it from PWD? ie where the script is ? 
[22:40] <bjf> manjo, don't know, i've run it on three different systems
[22:40] <bjf> manjo, that's how I normally run it look at the daily script
[22:40] <manjo> I coped the script to a directory called newiso/ and ran it 
[22:40] <manjo> so I should run it from kernel-tools/daily-test-isos
[22:41] <manjo> hmmm ran it from that dir and still get chroot: cannot run command `mount': Exec format error
[22:42] <bjf> the "daily-iso-builder.sh" script shows you exactly how I run it
[22:42] <bjf> manjo, are you running it on a lucid system?
[22:42] <manjo> yes
[22:42] <bjf> hmmm
[22:43] <manjo> I have a maverick iso
[22:44] <bjf> that error seems familiar but I can't recall why
[22:44] <manjo> bjf, do I need to be in a chroot ?
[22:45] <bjf> no, the script should take care of any of that
[22:45] <bjf> manjo, I run that script just as it is from a cron job on emerald.pgraner
[22:46] <bjf> manjo, just for a test, try to build it as you on emerald.pgraner
[22:46] <bjf> manjo, in your home dir
[22:46] <manjo> bjf, yeah emerald is not connecting atm
[22:46] <manjo> bjf, looks like its dead from here 
[22:47] <manjo> ssh: connect to host  XX port 22: Connection timed out
[22:47] <manjo> pgraner, ^
[22:47] <ogasawara> manjo: should be up, I'm currently watching a build on it as we speak
[22:48] <bjf> ogasawara, same error for me
[22:48] <apw> seems to work for me
[22:53] <bjf> ogasawara, apw, same problem from two systems (was able to ssh in yesterday and maybe earlier today)
[22:53] <bjf> getting ssh_exchange_identification: Connection closed by remote host
[22:53] <manjo> bjf, any idea why sudo mount --bind /dev $CHROOT/dev would fail ? 
[22:55] <apw> bjf, using the main link in right?  dsl is firewalled off when main is up
[22:55] <ogasawara> bjf: did you just catch what I said on mumble?
[22:55] <apw> bjf, just logged in successfully right now
[22:55] <ogasawara> bjf: you probably need to update your .ssh/config
[22:55] <bjf> ogasawara, why?
[22:56] <ogasawara> bjf: I'm assuming firewall changes?
[22:56] <bjf> ogasawara, since yesterday?
[22:57] <ogasawara> bjf: no idea, but I know I had issues connecting this morning and once I updated my .ssh config to use ubuntu.redvoodoo.org it started working
[22:57] <apw> ogasawara, the secondary link is not open unless the main goes down, so you have to use the right one
[22:57] <bjf> ogasawara, yup, that was it
[22:58] <apw> and we were on the secondary for the first few hours of the day
[22:58] <bjf> apw, but i've been using dsl for a while, for long enough i forgot i'd changed
[22:58] <bjf> apw, anyway, can connect now
[22:58] <bjf> manjo, ^^
[22:58] <apw> perhaps that bit wasn't working
[22:59] <apw> bjf, ahh yes i know why, the dyndns on the dsl link was reporting the main address instead of the correct one
[22:59] <manjo> yeah I switched to ubuntu. 
[22:59] <manjo> from dsl
[22:59] <manjo> as per ogasawara 
[22:59] <apw> so it was no use for fall back
[22:59] <bjf> ah
[23:00] <apw> we should get pete to publish a name which points to the up link
[23:00] <bjf> manjo, as per mount question, don't know why it would fail
[23:02]  * bjf is going to get some exercise, back later
[23:17] <manjo> bjf[afk], ogasawara, take a look at http://uck.sourceforge.net/
[23:23] <manjo> bjf[afk], same script seems to work on emerald, something wrong with my machine setup, I tried uck and that fails on my machines as well.. so using emerald now