[03:07] <DanaG> Say, why is drm-next kernel-ppa so old? http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-next/
[07:07] <lag> Mornin'
[07:12] <cooloney> lag: morning, man
[07:21] <lag> Hey Bryan :)
[08:28] <smb> cooloney, Morning. Any news from Freescale about the brickage?
[08:29] <cooloney> smb: morning, i am just wanna discussing with you. 
[08:29] <cooloney> smb: actually, i don't have any update as we got in the email
[08:30] <cooloney> i saw you post the security kernel in the email
[08:30] <smb> Ok, I had been looking at the source code on Friday. Right, there were two updates missing from the latest security, but otherwise it was as I would expect it
[08:31] <smb> And from the things missing its hard to believe that this can destroy things as it did
[08:31] <smb> Very strange
[08:31] <smb> The only other variance was that I built on tangerine but you do that too
[08:34] <cooloney> smb: for fsl-imx51, i built them in *.mills. 
[08:34] <cooloney> although it is different, i still don't think build machine is a issue.
[08:34] <cooloney> i have to say ' that's pretty odd'
[08:35] <cooloney> so what's our next?
[08:35] <cooloney> i am going to send out an email to ask?
[08:35] <smb> cooloney, So just to confirm that for myself. When you installed the bad kernel, you once could boot but it crashed. And only then was the board bricked?
[08:36] <cooloney> smb: oh, IIRC, it never boots any more
[08:36] <cooloney> we installed the whole system on babbage
[08:36] <cooloney> and copied your kernel .deb file to the board
[08:36] <smb> cooloney, So in theory it could be some weird wrongness in the flashing process as well?
[08:36] <cooloney> and sudo dpkg -i *.deb
[08:37] <cooloney> smb: yeah, at the end of the installation, it will try to update the kernel in flash
[08:37] <cooloney> so maybe corrupted sth
[08:38] <lag> cooloney: How 'bricked' are they?
[08:38] <lag> cooloney: Have you tried to JTAG them yet?
[08:38] <smb> Though quite mysterious to do that twice. Anyway, I guess we want to know what _did_ break things. As much as I understood mails. We only know that it was not what fsl thought it was.
[08:38] <cooloney> lag: cannot even boot from the bootloader
[08:38] <cooloney> lag: too bad, i don't have it
[08:38] <cooloney> and we shipped them back to fsl 
[08:39] <lag> Okay, I assume they'll try to JTAG them back to life then
[08:39] <cooloney> lag: yeah, i think so
[08:39] <cooloney> smb: let me send out email to sync up with fsl guys
[08:39] <ikepanhc> cooloney: you mean you update a can-not-boot kernel to babbage and have to send the board back to fsl?
[08:40] <smb> ikepanhc, We found out about the cannot-boot after flashing. :)
[08:40] <cooloney> ikepanhc: we tried to test smb's security kernel
[08:40] <cooloney> after we installed that kernel, the board cannot boot anymore
[08:40] <cooloney> bricked the board 
[08:40] <cooloney> smb: yeah
[08:40] <cooloney> update the kernel image in on board flash or somehow
[08:42] <ikepanhc> IIRC babbage board can boot from SD card...
[08:44] <simon___> bump to anybody: i have found a bug and don't know where to report it - i have a packard-bell laptop and the kernel loads asus_laptop driver by default (it's enabled in the stup process). it's a driver that's causing some problems (e.g. wifi) and the workaround is to blacklist it. where should i report it?
[08:44] <ikepanhc> simon___: please report it
[08:44] <smb> simon___, Launchpad against linux package
[08:45] <cooloney> ikepanhc: yes, but it needs it's on-chip bootrom supports that.
[08:45] <ikepanhc> simon___: you mean you have a dell laptop and asus-laptop loaded?
[08:45] <cooloney> ikepanhc: it does not boot from anywhere after that.
[08:45] <ikepanhc> cooloney: oh, too bad
[08:46] <ikepanhc> cooloney: ah? on-chip bootrom erased? *faint*
[08:46] <smb> ikepanhc, Hm, was it asus-laptop which got the handling for the lenove because they had the asustek acpi id?
[08:46] <ikepanhc> smb: asus-laptop.ko will look for ACPI HID ATK0101 or ATK0100
[08:47] <ikepanhc> but they shall not be there on dell laptops
[08:47] <smb> ikepanhc, So it might be the dell also has that
[08:47] <smb> ikepanhc, Its said to be packard-bell
[08:47] <ikepanhc> smb: that will be bad news
[08:48] <smb> not dell
[08:48] <ikepanhc> smb: ohoh, sorry for my poor eyes
[08:48] <smb> ikepanhc, I got that problem too often. :)
[08:48] <simon___> ikepanhc:smb is right, it's packard-bell
[08:49] <ikepanhc> simon___: if you filed the bug, please let me know the bug id
[08:49] <ikepanhc> simon___: I think I can try to help you
[08:49] <smb> simon___, The best way would be to use "ubuntu-bug linux"
[08:49] <simon___> ikepanhc:i'll file the bug right away.. tnx
[08:50] <simon___> smb:should i use "ubuntu-bug linux" with asus_laptop loaded?
[08:50] <ikepanhc> <---- has a laptop with asus-laptop
[08:51] <smb> simon___, If it is usable to reach the network yes.
[08:51] <ikepanhc> simon___: with or without is ok
[08:51] <smb> At least with the driver loaded it might show some of the problems in the logs
[08:52] <ikepanhc> yes
[08:52] <simon___> smb:wifi doesn't work, but the cable is ok
[08:52] <smb> simon___, Ok, then do it with it loaded. Sounds a bit like rfkill might be messed up in that case
[08:55] <simon___> smb:i agree..at first i thought it was a wifi driver issue so i filled a bug there:
[08:55] <simon___> http://bugzilla.intellinuxwireless.org/show_bug.cgi?id=2128
[08:55] <ubot2> bugzilla.intellinuxwireless.org bug 2128 in others "Intel 3945ABG sees networks but can't connect" [Normal,Resolved: tested_patch_exists]
[08:56] <cooloney> smb:  i am going to point fsl guys out where is the kernel source code.
[08:57]  * abogani waves all
[08:57] <cooloney> smb: do you know where is the source of your secuity kernel and our updates kernel
[08:57] <smb> cooloney, That is not yet released
[08:57] <akgraner> crimsun, in answer to your question about the mac air - nope :-( sorry not yet - I've been a bit busy :-/  I'll see what I can do after next week
[08:57] <smb> cooloney, I normally wait till the security releases are really out
[08:58] <smb> cooloney, The updates kernel is just the one in the topic branch
[08:58] <cooloney> smb: ok, got it. man
[09:00] <cooloney> smb: is this one? http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-lucid.git;a=shortlog;h=refs/heads/fsl-imx51
[09:01] <smb> cooloney, Sort of. If you take the additional stuff off after 608-15
[09:02] <cooloney> smb: got it. @tags/Ubuntu-2.6.31-608.15
[09:02] <smb> cooloney, yup
[09:03] <smb> cooloney, I hope the security release is going out soon, then I can push all of the code
[09:10] <cooloney> smb: ok, no problem. 
[09:27] <simon___> ikepanhc; it took me a while.. :)
[09:27] <simon___> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/612454
[09:27] <ubot2> Ubuntu bug 612454 in linux (Ubuntu) "[Packard-Bell EasyNote] asus_laptop problem: wifi (affects: 1) (heat: 6)" [Undecided,New]
[09:28]  * ikepanhc looking
[09:41] <simon___> ikepanhc: i just detected another bug - numlock is not working as expected (it's also an asus_laptop issue). should i add my findings to this bug?
[09:42] <ikepanhc> simon___: please do so.
[09:42] <ikepanhc> simon___: but numlock shall be nothing related to ACPI extra driver..
[09:45] <simon___> ikepanhc: i am quite sure it's related to asus_laptop - blacklisting it solves the problem
[09:50] <ikepanhc> simon___: I have some comment on the bug, I need the acpidump and dmi modalias. please help me dump those info
[09:50] <simon___> ikepanhc: sure, but how do i do that?
[09:51] <ikepanhc> simon___: I write how to do it on the bug comment :)
[10:00] <simon___> ikepanhc; the command "sudo iasl ..." is not found. is it a misspell?
[10:01] <ikepanhc> simon___: no, please "sudo apt-get install iasl", but you can skip that, using acpidump please
[10:01] <proppy> will 2.6.35 (retail) be build for lucid on ppa ?
[10:01] <proppy> is it 2.6.35-14 ?
[10:01] <simon___> ikepanhc: do i have to install acpidump as well?
[10:02] <ikepanhc> simon___: yes please
[10:05] <simon___> ikepanhc: done
[10:05]  * ikepanhc looking
[10:06] <apw> proppy, do you mean the final v2.6.35 version?  yes that will be built for lucid once its done for maverick
[10:07] <proppy> apw: yes, I meant the one which went out yesterday
[10:07] <proppy> apw: thanks for the confirmation
[10:07] <proppy> will it be -14 ?
[10:08] <apw> proppy, normally the abi number is the same in lucid yes
[10:08] <proppy> thanks
[10:10] <proppy> it seems like it will be built in 2 days :) https://launchpad.net/~kernel-ppa/+archive/ppa/+build/1900054
[10:14] <proppy> can I dget && debuild an ubuntu kernel .dsc, or are there additional steps needed ?
[10:17] <apw> proppy, in theory yes, not something i do regularly but the buildd's can build it that way
[10:19] <proppy> apw: thanks I'll give it a try
[11:01] <ikepanhc> simon___: I am tracing what ACPI method is executed, if some news, I will update as bug comment :)
[11:02] <simon___> ikepanhc: thanks a lot
[11:03] <ikepanhc> simon___: thanks you too for reporting :)
[11:03] <Corona> hi everybody
[11:04] <Corona> i'm trying to build a kernel in order to test a patch
[11:04] <Corona> i'm following these instructions https://wiki.ubuntu.com/KernelTeam/GitKernelBuild
[11:05] <Corona> but apparently they only work for linus's tree and I need to apply a patch to drm-intel-next
[11:05] <Corona> does anybody know where i can find instructions on how to do this?
[12:09] <apw> https://wiki.ubuntu.com/Kernel/Dev/QuickBuildLocal
[12:10] <apw> Corona, that one perhaps ^^
[12:16] <Corona> thanks apw, but that's not really what i'm looking for. can i just clone git://git.kernel.org/pub/scm/linux/kernel/git/anholt/drm-intel.git and then apply the patches or do i need to merge the drm-intel-next branch with linus's tree?
[12:17] <apw> Corona, as the drm-intel branch is just a derivative tree from linus' tree you should be able to do the same thing to it you can the linus tree
[12:17] <apw> though i'd have thought you really want an ubuntu tree and cherry-pick the patch you need onto it
[12:18] <Corona> the patch is in mailbox format so that's why i was told to use git
[12:18] <Corona> here's the patch, but i can't get the kernel to compile when i apply it
[12:18] <Corona> https://bugs.freedesktop.org/attachment.cgi?id=36959
[12:19] <apw> how does it fail
[12:20] <Corona> it doesnt say much, the compilation process stops with "error 2"
[12:20] <Corona> [debian/stamp/build/kernel] Error 2
[12:22] <Corona> i just started over with a clean tree so i'm going to have lunch while it compiles
[12:22] <Corona> and see if it works this time
[12:57] <jjohansen> gah sometimes /me can't stand C++
[12:57] <soren> jjohansen: Only sometimes?
[12:58] <jjohansen> soren: I can blissfully ignore it when I'm not doing something with it
[12:59] <soren> jjohansen: True.
[12:59] <soren> still... It's always lurking somewhere. *shudder*
[13:08]  * cking is glad ACPI AML code is not like C++
[13:10] <jjohansen> hehe, but are they really any more sane?
[13:10] <cking> both make me feel insane
[13:15]  * smb tries to imagine object oriented BIOS code and shudders
[13:33] <JFo> well that was a bit odd
[13:34] <smb> JFo, Odder than the usual oddness?
[13:39] <JFo> indeed
[13:39] <JFo> my machine went dark and wouldn't respond at all
[13:39] <smb> Thats odd
[13:39] <JFo> never done that before
[13:39] <JFo> heh
[13:40] <smb> Hm, were you still on Lucid or Maverick?
[13:40] <JFo> this is Lucid\
[13:40] <cking> JFo, run out of power? ;-)
[13:40] <JFo> no cking I checked that ;)
[13:41] <smb> Went black means just screen black but some parts still running or shutdown?
[13:42] <cking> can you ping it?
[13:43]  * smb imagines JFo sitting in front of his laptop with a triangle: "Yep, that works!" :-P
[13:43] <cking> gosh, we're being very literal today
[13:44] <smb> Yeah, must be something in my coffee today
[13:48] <JFo> heh
[13:48] <JFo> smb, looked like there was HDD activity
[13:48] <JFo> but no ping, ssh, etc
[13:48] <JFo> the backlight was still on
[13:48] <smb> Ok, so rather hang than thermal shutdown
[13:48] <JFo> just nothing displayed
[13:49] <smb> Really sounds like some stuff that apw had seen. But that was rather on boot
[13:49] <smb> Like the drm driver locked down hard while not refreshing or so
[13:50] <jjohansen> JFo: did it happen on resume, perchance?  I've seen the screen come back from resume briefly and then go dark.
[13:50] <JFo> no, this was a fresh startup
[13:50] <smb> during startup?
[13:50] <JFo> jjohansen, I did have that happen though at the sprint
[13:50] <JFo> smb, after
[13:51] <smb> ok
[13:51] <JFo> it came up, I logged in, started things
[13:51] <JFo> and then went for coffee
[13:51] <JFo> and when I came back it was like that
[13:51] <smb> So could be power save mode
[13:51] <smb> for the screen
[13:51] <JFo> could have been
[13:51] <JFo> but the backlight was still on
[13:51] <JFo> so the screen was on
[13:51] <cking> and maybe GPU lock up
[13:51] <JFo> and I have no screensaver configured
[13:52] <smb> I believe that DMPS thing sill kicks in
[13:52] <JFo> brb, i need more coffee :)
[13:53] <diwic> A bug is sitting on my screen.
[13:57] <smb> Hm, on it has the advantage that you can squash it more simply
[14:03] <diwic> smb, it's likely to turn into SAUCE then ;-)
[14:03] <smb> heh :)
[14:09] <JFo> don't look at me. I'm all for smashing bugs ;-)
[14:26] <apw> ogasawara, kernel has been NEW'd other than arm
[14:30] <JFo> Live NEW'd kernels?
[14:32]  * tgardner thinks jfo is a sick puppy
[14:34] <JFo> heh
[14:42] <diwic> What is your favorite C debugger?
[14:43] <diwic> ie GDB frontend
[14:48] <cnd> morning everyone :)
[14:48] <diwic> morning cnd
[14:49] <cnd> anyone know how linaro stuff flows to the ubuntu kernel
[14:49] <cnd> things like Dave Martin's perf patches that he posted about on the kernel-team mailing list?
[14:53] <cnd> apw, tgardner, ogasawara? ^^
[14:53] <apw> cnd, they have their own master tree
[14:54] <cnd> apw, so does that mean that if we want Dave's cool patches, we need to have them submitted specifically for the maverick kernel?
[14:56] <amitk> cnd: isn't that why he posted it to the k-t list? Do they not apply?
[14:57] <jwest-> hi
[14:57] <jwest-> is the 2.6.35 kernel released today
[14:57] <diwic> cnd, I look through the canonical-kernel-team list but can't find anything from Dave Martin...?
[15:00] <ogra> cnd, depends on the kernel
[15:00] <ogra> cnd, for omap4 we still have the separate branch, omap3 gets built from the ubuntu source package, i guess you will find linaro patches only in the linaro branch and binaries
[15:01] <cnd> diwic, the kernel-team@lists.ubuntu.com mailng list
[15:01] <jwest-> do you guys think i should update to the 2.6.35 kernel?
[15:01] <jwest-> or wait?
[15:01] <cnd> ogra, I'm interested in Dave's perf patches
[15:01] <cnd> which aren't arch specific
[15:01] <JFo> jwest-, depends on what the machine you are upgrading is used for
[15:02] <diwic> jwest-, we always need more testers :-)
[15:02] <amitk> cnd: you didn't answer me, do they not apply?
[15:02] <JFo> I don't recommend updates to dev unless it is a test machine
[15:02] <JFo> yeah, what diwic said :)
[15:02] <cnd> amitk, sorry, didn't see your msg
[15:02] <cnd> I don't know if they apply, because I haven't had time to really take a good look
[15:03] <cnd> amitk, so I was wondering if I needed to take a look, or if they would be pulled automagically into ubuntu
[15:04] <amitk> cnd: in general, I've been urging everything going into the linaro kernel to be made available for ubuntu (post to k-t). Then it is upto the k-t to decide if they want to them
[15:04] <amitk> s/for/to
[15:04] <jwest-> diwic: i could try:D
[15:04] <amitk> s/want to/want to apply/
[15:04] <amitk> *sigh*
[15:07] <tgardner> amitk, y'all could have your very own linux-linaro kernel if I could get the packaged accepted. I sent slangasek and email about it.
[15:07] <tgardner> s/and/an/
[15:08] <amitk> tgardner: sure, in this case though, the changes are general enough for other flavours too, I believe
[15:08] <cnd> sorry for going awol, I'm otp :(
[15:09] <tgardner> amitk, the perf bits? If they get accepted upstream then we'll likely be able to get 'em via stable (eventually)
[15:09] <amitk> cnd: understand, you're probably contorting at weird angles to get reception on the iPhone 4 :-p
[15:10] <JFo> just his hand though
[15:10] <JFo> he'll be great at gang signs after this
[15:10] <JFo> Snoop Dogg would be so proud
[15:11]  * JFo brings the bad humor out
[15:17] <amitk> lol
[15:23] <jjohansen> diwic: hrmm, lots of different gdb frontends, ddd is the generic fallback but its kindof slow, Insight and KDbg are worth looking at, I would avoid eclipse unless you want to setup a project just so you can debug
[15:23] <jjohansen> http://en.wikipedia.org/wiki/Debugger_front_end
[15:24] <jjohansen> diwic: that is assuming your doing userspace debugging
[15:24] <cnd> amitk, tgardner, the perf bits aren't really something I would expect to get through -stable
[15:24] <diwic> jjohansen, I've tried ddd and kdevelop's built-in and haven't really fallen in love with either of them
[15:24] <cnd> so I think we should just pull them
[15:25] <jjohansen> diwic: yeah, none of them are great
[15:25] <tgardner> cnd, once they are actually upstream perhaps
[15:25] <cnd> tgardner, they are already upstream
[15:25] <cnd> at least, they are in Arnaldo's tree
[15:25] <tgardner> cnd, in Linus' tree?
[15:26] <cnd> tgardner, not yet, but I would assume as soon as he pulls from arnaldo
[15:27] <cnd> I will try to take a look at the patches myself and test them out
[15:27] <cnd> and then send the patches on to kernel-team
[16:25] <slangasek> tgardner, amitk: I've looked at the package in NEW and my archive admin hat is presenting me with concerns, which I will try to get an email back to you about today
[16:25] <slangasek> (high latency on this stuff since I'm at DebConf this week)
[16:26] <tgardner> slangasek, ack
[16:35] <tgardner> smb, is Lucid mvl-dove subject to SRU ?
[16:35] <smb> tgardner, Only sort of SRU-light
[16:35] <smb> But you should still have bugs for things to change
[16:35] <smb> or reports that is
[16:36] <smb> tgardner, But if you ask about the mvl pull request 
[16:38] <smb> tgardner, If there is no tracking lp report there should be one. SRU team is looking over those things and it seems to complicate their process when this is missing.
[16:39] <smb> tgardner, I/we can mass-add the buglinks before applying, but need to know the number
[16:39] <tgardner> smb, why are you telling me all of this? you should be telling ericm
[16:39] <smb> tgardner, because you asked
[16:40] <tgardner> smb, I only asked if mvl-dove was subject to SRU.
[16:40] <smb> tgardner, Ok, ok, the rest you don't care. :) I'll post a reply
[16:43] <smb> bjf, Were you usually quick reading ARM pull requests
[16:44] <bjf> smb, not exactly sure what your question is but I did see eric's pull request, want me to review it?
[16:45] <tgardner> smb, bjfwhy bother? About all we can actually change is packaging, so the rest is just a waste of time.
[16:45] <smb> bjf, I just vaguely remembered you once going over some patches from Bryan for fsl. On their topic branches its not really required as they are ok to do what they want
[16:45] <tgardner> bjf^^
[16:46] <smb> bjf, The question was more were you planning
[16:46] <smb> But otherwise I'd agree not to bother too much
[16:46] <bjf> smb, yes I did look at some earlier mvl patches, was thinking about looking these new ones over, but there's not much we can do other than suck them in
[16:47] <smb> exactly
[16:49] <smb> sconklin, Was it you that had used some helper to quickly create man pages from text files?
[16:50] <octo777>  is the intellegacy driver, the same driver that was the intel driver in older kernels? If so, it should work the same as before once KMS is turned off right ?
[16:50] <ogasawara> tgardner: seems I don't have the permissions to upload lbm. I've got the package built in my home dir on zinc.  Could you sign it for me and upload in the mean time.
[16:51] <ogasawara> tgardner: I assume I just need to get cjwatson to add it to the list of packages for the ubuntu-kernel-uploaders team
[16:51] <smb> ogasawara, Yes, the joy of the name containing the version
[16:51] <ogasawara> smb: yep, figured that was it
[16:51] <tgardner> ogasawara, ack
[16:52] <sconklin> smb: there's a tool that is part of the debian packaging utilities which generates a man page template from the output of "command --help"
[16:53] <sconklin> smb: stand by and I'll figure out what it is
[16:54] <smb> sconklin, Hm that might be nice though a bit sparse in this special case
[16:55] <tgardner> ogasawara, done
[16:55] <ogasawara> tgardner: thanks
[16:56] <tgardner> ogasawara, arm finished?
[16:56] <smb> Hm, debhelper created an .ex maybe I just use that. Annoyingly high effort for such a small package
[16:56] <ogasawara> tgardner: not yet, I think it has 1 more hr to finish building
[16:57] <ogasawara> tgardner: once that's done, I'll upload linux-meta
[16:57] <tgardner> ogasawara, you cuold probably upload the -meta package now. the armel guys can just deal....
[16:57] <ogasawara> tgardner: true
[16:58]  * ogasawara uploads
[16:58] <manjo> JFo, is there a bug review now ?
[16:59] <JFo> yep
[17:00] <smb> Damn this time of day already!
[17:02] <JFo> heh
[17:02] <JFo> apw, are you joining us?
[17:04] <manjo> JFo, which list are we looking at now ?
[17:05] <manjo> JFo, http://qa.ubuntu.com/reports/jfo/kernel-buglist.html ?
[17:05] <JFo> the kernel-candidate
[17:05] <JFo> list
[17:05] <bjf> manjo, https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bugs?field.searchtext=&orderby=-importance&field.status:list=NEW&field.status:list=INCOMPLETE_WITH_RESPONSE&field.status:list=INCOMPLETE_WITHOUT_RESPONSE&field.status:list=CONFIRMED&field.status:list=TRIAGED&field.status:list=INPROGRESS&field.status:list=FIXCOMMITTED&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_supervisor=&field.bug_commenter=&f
[17:05] <bjf> ield.subscriber=&field.tag=kernel-candidate&field.tags_combinator=ALL&field.status_upstream-empty-marker=1&field.has_cve.used=&field.omit_dupes.used=&field.omit_dupes=on&field.affects_me.used=&field.has_patch.used=&field.has_branches.used=&field.has_no_branches.used=&search=Search
[17:05] <manjo> thanks got it 
[17:06] <bjf> manjo, there is a link off of https://wiki.ubuntu.com/Kernel/Tagging
[17:06] <manjo> bjf, yep I know... was not sure which list jfo was looking at 1st 
[17:08]  * ogasawara wonders if anyone can hear me
[17:08] <ogasawara> or if I've been talking to myself
[17:08] <bjf> ogasawara, no
[17:08] <ogasawara> awesome
[17:08] <JFo> heh
[17:09] <JFo> talk louder! >:-)
[17:13] <ogasawara> dammit!
[17:13] <JFo> :)
[17:13] <ogasawara> heh
[17:16] <ogasawara> bjf: http://cdimage.ubuntu.com/ubuntu-server/daily/current/
[17:16] <komputes> Hello kernel folks, I was wondering if there is a way to tell if KMS is currently enabled.
[17:27] <tgardner> smb, bjf, sconklin, would one of you guys take care of the patch in bug #576066 ? I know I sent it out for review at least once.
[17:27] <ubot2> Launchpad bug 576066 in linux (Ubuntu Maverick) (and 3 other projects) "ums_cypress missing from lucid server cd (affects: 1) (heat: 46)" [Medium,Fix released] https://launchpad.net/bugs/576066
[17:28]  * smb thinks he saw it but hasn't looked
[17:28] <smb> bjf, sconklin Feel free to grab
[17:29] <sconklin> I'll take it
[17:35] <bjf> tgardner, reading through the description for bug 611474, he tried a 2.6.35 kernel already
[17:35] <ubot2> Launchpad bug 611474 in linux (Ubuntu) "Boot fails with busybox prompt using LSI Logic / Symbios Logic SAS1068E PCI-Express Fusion-MPT SAS [1000:0058] (rev 08) SAS Disk Controller (affects: 1) (heat: 8)" [Undecided,Triaged] https://launchpad.net/bugs/611474
[17:36] <tgardner> bjf, hmm, what did he boot in order to get the SAS disk address ?
[17:37] <tgardner> CurrentDmesg.txt is only a fragment, so I can't tell what kernel it is
[17:37] <bjf> tgardner, don't know
[17:38] <bjf> tgardner, the apport-collect was done on 2.6.32
[17:39] <tgardner> bjf, he says 'Booting from a SATA drive seems to works'. I wonder if he means that the SAS drivers work when booting from SATA.
[17:39] <tgardner> SAS drives*
[17:39] <tgardner> in which case that inmplies its an initrd problem
[17:40] <smb> tgardner, The question would be whether those need additional handling beside of the diver being loaded
[17:40] <tgardner> smb, well, like what?
[17:41] <smb> Heck if I knew. But in those dmesg the drive came up quite late after the SATA drive and network stuff
[17:42] <smb> Do those things need special fw loaded?
[17:42] <tgardner> smb, yes IIRC
[17:43] <tgardner> it looks like he able to install to a SAS drive, so that means the boot kernel did the right thing
[17:43] <smb> Well the boot kernel had a different medium for the root fs
[17:43] <smb> ie the cd
[17:44] <tgardner> smb, thats beside the point. the boot kernel _did_ see the SAS drives.
[17:44] <smb> We are talking about the boot dmesg in the report, which was booted from SATA
[17:44] <smb> ?
[17:44] <tgardner> smb, I think so, but its hard to tell
[17:45] <smb> ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[17:45] <smb> [    3.772592] ata3.00: ATA-6: ST3120026AS, 8.05, max UDMA/133
[17:45] <smb> [    3.772596] ata3.00: 234375000 sectors, multi 0: LBA48 
[17:46] <tgardner> smb, [   34.819922] scsi6 : ioc0: LSISAS1068E B3, FwRev=00192f00h, Ports=1, MaxQ=266, IRQ=16
[17:46] <tgardner> [   34.856342] mptsas: ioc0: attaching ssp device: fw_channel 0, fw_id 0, phy 0, sas_addr 0x5000c500237abaf1
[17:46] <tgardner> [   34.857592] scsi 6:0:0:0: Direct-Access     SEAGATE  ST3300657SS      ES62 PQ: 0 ANSI: 5
[17:46] <tgardner> [   34.859752] sd 6:0:0:0: Attached scsi generic sg2 type 0
[17:46] <tgardner> in CurrentDmg.txt
[17:46] <smb> That is later on in the current dmesg
[17:46] <smb> yep
[17:47] <tgardner> huh? Its right at the top
[17:47] <tgardner> oh well, I'm gonna ask for some clarifications in the bug
[17:47] <smb> Like you need the root fs (or stuff from there), then it takes a bit to initialize and then the drive come up
[17:49]  * manjo getting lunch will be back soon
[17:49] <smb> I am not sure, but I thought boot.dmesg ends when switched from initrd root to real root fs. But I might be wrong
[18:19] <komputes> smb: ping
[18:20]  * smb is only available for really simple stuff
[18:22] <komputes> smb: Do you know a way to tell if KMS is currently enabled.
[18:23] <komputes> ^ simple?
[18:24] <smb> Not sure there is a single bit somewhere. apw do you know that. Otherwise usually you would see special drmfb devices...
[18:24] <tgardner> komputes, as far as the kernel team is concerned, the first step towards debugging desktop issues (like KMS) is to try a recent release.
[18:26] <komputes> tgardner: right, in mode cases that would do however I simply want to know if there is a way to tell if, in the current session, xorg or the kernel is doing mode switching
[18:27] <smb> Most drivers seem to emit stuff like
[18:27] <smb> [   15.602350] [drm] radeon defaulting to kernel modesetting.
[18:28] <smb> Hm, not intel as it seems
[18:28] <komputes> smb: interesting, dmesg...eh?
[18:28] <smb> komputes, Yep
[18:28] <komputes> tgardner: would explain why I can't see it for my intel card
[18:29] <smb> But there you would see inteldrmfb being used which iirc indicates kms
[18:29] <komputes> ok, well thanks guys, that helps - would be nice to see it on i915 driver as well, but this is good enough as an indication :)
[18:30] <komputes> and tgardner, thanks for following up on Bug #611474, much appreciated
[18:30] <ubot2> Launchpad bug 611474 in linux (Ubuntu) "Boot fails with busybox prompt using LSI Logic / Symbios Logic SAS1068E PCI-Express Fusion-MPT SAS [1000:0058] (rev 08) SAS Disk Controller (affects: 1) (heat: 8)" [Undecided,Triaged] https://launchpad.net/bugs/611474
[18:30] <tgardner> komputes, that bug is so old the original reported has probably given up
[18:30] <komputes> tgardner: bug is 3 days old
[18:31] <tgardner> hmm, I thought I saw Jan, 2010. oh well...
[18:31] <komputes> tgardner: probably one of the dupes
[18:31] <JFo> too many bugs, not enough brain cells
[18:31] <komputes> tgardner: feel free to mark the dupes in the description as actual dupes of this bug
[18:31] <JFo> brb, gone to take meds and lunch
[18:32] <JFo> komputes, we hatesss the duplicatessssss
[18:32] <JFo> :)
[18:32] <komputes> JFo: stuff happens
[18:48]  * tgardner lunches
[19:05]  * smb goes away
[19:30] <proppy> Hi, it seems kernel 2.6.35 headers package are broken
[19:30] <proppy>   linux-headers-2.6.35-14-generic: Depends: linux-headers-2.6.35-14 but it is not installable
[19:30] <proppy> E: Broken packages
[19:30] <proppy> does someone have a clue ?
[19:30] <proppy> (from kernel-ppa)
[19:31] <tgardner> proppy, i386 ?
[19:31] <proppy> amd64
[19:31] <proppy> just installed .../linux-image-2.6.35-14-generic_2.6.35-14.19~lucid1_amd64.deb
[19:31] <tgardner> proppy, you gotta wait until i386 finishes.
[19:31] <jjohansen> ->Lunch
[19:32] <proppy> oh ok, 
[19:33] <proppy> the package seems there thought linux-headers-2.6.35-14-generic_2.6.35-14.19~lucid1_amd64.deb
[19:33] <proppy> only one of its dependencies is missing
[19:33] <tgardner> proppy, all of the linux-headers packages depend on a package that is only built for i386, so it'll be awhile yet
[19:34] <proppy> oh ok, tgardner thanks for this information
[19:34] <proppy> so I should wait until https://launchpad.net/~kernel-ppa/+archive/ppa/+build/1900054 is done right ?
[19:34] <proppy> 05/08 ;0
[19:34] <proppy> :)
[19:34] <tgardner> proppy, I don't know whats taking so long, but I wanted to advertise the amd64 binaries so folks could do some testing
[19:35] <proppy> tgardner: do you want me to do any test in specific ?
[19:36] <tgardner> nothing particular other then just using the kernel
[19:39] <proppy> was looking for this patch http://git.kernel.org/?p=linux/kernel/git/tip/linux-2.6-tip.git;a=commit;h=a1e80fafc9f0742a1776a0490258cb64912411b0
[19:39] <proppy> obviously it is included in 2.6.35-14
[19:40] <proppy> tgardner: do you know if I could me the missing package myself ?
[19:40] <proppy> apt-get source linux-headers && debuild ?
[19:41] <tgardner> yeah, if you know a bit about building the kernel. https://wiki.ubuntu.com/Kernel/Dev
[19:43] <proppy> tgardner: thanks for the pointer
[19:43] <proppy> 'fakeroot debian/rules binary-indep' was what I was looking for
[20:06]  * ogasawara lunch
[20:09] <proppy> tgardner: asciidoc is also needed for building indep
[20:09] <proppy> https://wiki.ubuntu.com/Kernel/Dev/QuickBuildLocal#Packages%20required%20on%20a%20build%20system
[20:10] <tgardner> proppy, 'sudo apt-get build-dep linux'
[20:11] <proppy> oh ok, should we updated the wiki page ?
[20:11] <tgardner> proppy, I need to experiment a bit. I think build-dep doesn't work as well on older releases.
[20:11] <proppy> dpkg-deb: building package `linux-headers-2.6.35-14' in `../linux-headers-2.6.35-14_2.6.35-14.19~lucid1_all.deb'.
[20:11] <proppy> \o/
[20:45] <octo777> anyone having problems with the kms enabled intel driver locking up intermittently ?\
[20:53] <JFo> octo777, in Lucid?
[22:29] <Sarvatt> komputes: grep -E '(nouveau|drm)fb' /proc/fb
[23:08]  * manjo out for now