=== dileks is now known as Guest20124 === bandit5432 is now known as led-bandit [07:25] bryceh, those people are maddening, can't they keep their branch still for one day ? [07:30] apw, I know it seems like we set up these auto builds, we use them twice, and then Intel's off on some new branch [07:32] morning [07:35] bryceh, so this replaces drm-intel-next as we call it [07:35] smb, moin [07:36] What, there's *another* drm-intel-next? [07:36] apw, essentially. There is still a drm-intel-next branch, but I gather that it's more of a stable snapshot of the drm-intel-next-queue thingee [07:37] RAOF, tis the season [07:37] bryceh, i guess the question i am asking is what do you want it called :) [07:37] RAOF, you might have noticed our drm-intel-* mainline builds became stagnant [07:37] I did, in fact. [07:38] RAOF, daniel vetter now maintains them, but in some new branches [07:38] :) [07:39] apw, what would you think if we just called these as 'drm-intel-experimental' henceforth? And then just map that to whatever branch-of-the-month Intel is pointing folks to? [07:40] bryceh, sounds like a plan to me, as they cannot make a common name we'll have to do it for them [07:40] moin [07:40] * smb proposes drm-intel-toad [07:40] I expect we'll have to tinker that when they get new maintainers, but hopefully that's not more than once every year or two [07:40] drm-intel-ygiagam ? [07:40] ppisati, ciao [07:40] apw, tml [07:41] bryceh, ok we have three at the moment: [07:41] drm-intel-next: git://git.kernel.org/pub/scm/linux/kernel/git/ickle/drm-intel drm-intel-next [07:42] drm-next: git://git.kernel.org/pub/scm/linux/kernel/git/airlied/drm-2.6 drm-next [07:42] drm-intel-fixes: git://git.kernel.org/pub/scm/linux/kernel/git/ickle/drm-intel drm-intel-fixes [07:42] the second should still be valid [07:43] the other two need changed. maintenance was handed from ickle over to daniel vetter. Use the git links from my email. [07:43] so, we should have a new drm-intel-next, the existing drm-next, and a new drm-intel-experimental. [07:44] technically, drm-intel-fixes still exists; it's maintained by keithp now, however I think it's not of very much interest for our purposes. [07:44] bryceh, so now there are 4 ? [07:44] yes [07:44] bryceh, the list you have sent me has a drm-intel-fixes ? [07:45] also with danvet [07:46] apw, yeah just ignore that. drop drm-intel-fixes, add drm-intel-next-queued (as drm-intel-experimental) [07:46] ok [08:21] bryceh, ok i think they are building now ... we'll know in an hour what it built [08:21] apw, excellent thanks [08:22] apw, meantime, I've posted a handful of gpu lockup reports that have mainline kernel patches pointed out as fixes [08:22] bryceh, remind me of that tag agin [08:23] apw, bugs are tagged 'kernel-handoff-graphics', and should show up on the report at http://reports.qa.ubuntu.com/reports/kernel-bugs/reports/_kernel_graphics_bugs_.html, but they're not there yet [08:23] apw, they'll all be titled like "GPU lockup blah IPEHR: 0x7....." [08:24] I spot checked half of them and the patches seem to be upstream in linus' tree so hopefully should be ripe for picking. [08:25] bryceh, can we not just stop supporting sandybridge it cannot need any more patches, really it can't :) [08:27] true, it's getting long in the teeth, we might be able to just declare it obsolete [08:33] I wish they showed their work for going from the i915_error_state to a given patch. But at least they're responding quickly. [08:34] you can ask them :] [08:34] #intel-gfx [08:35] but basically it's in the documentation, except when it's not; they find out an opcode that interlocks or something and locks up one of the rings [08:35] and races [08:37] bryceh, fix for bug #982410 seems to have come down via stable already [08:37] Launchpad bug 982410 in xserver-xorg-video-intel "[sandybridge-gt1] False GPU lockup render.IPEHR: 0x7a000003" [High,Confirmed] https://launchpad.net/bugs/982410 [08:38] apw, hmm, I wondered about that [08:47] http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-experimental/ <-- bryceh [08:48] yay, thanks apw! [08:49] smb, unity ... again ? [08:49] apw, ?redo from start? [08:50] * apw is getting about his 4th unity update of the week, some freeze [08:50] Ah [08:51] Could it be that this time the glibc/gcc nochange upload caused everything to no-change rebuild? [08:51] freezes are fiction for superfeatures! [08:51] its a good job the kernel isn't important [08:51] did sam ever sort out that whole post .8 being poopy thing [08:54] ohsix, e-no-parse :) [08:54] compiz .8 -> .9 was horrific [08:54] i still can't look at it or it will crash on me [09:14] * apw tries not to notice compiz is running [09:14] i utilize it pretty good, adjusting was tough; there's still some broken stuff, aside from teh crashes [09:15] edge snapping and stuff is broke, some of the plugins don't even work right anymore, windows wobble on focus changes [09:16] the preference migrator never worked either, had to manually translate the settings, a lot of them were plain gone [09:18] never worked = "x has encountered a problem", and compiz apoplexy [09:37] bryceh, ok the ones i can find on this list, there are actually three fixes, one we already have and two others which i have/am producing test kernels for [10:07] bryceh, ok drm-intel-next has also updated ... so i think they are all working [11:16] sforshee, bug #934707 seems to be another one of those affected by the backlight changes; i think you had some of those on your plate ? [11:16] Launchpad bug 934707 in linux "emachine e725 boots to valid display with no backlight" [High,Confirmed] https://launchpad.net/bugs/934707 [11:57] * ppisati -> lunch === BenC__ is now known as BenC [13:17] apw, sounds like yet another broken bios. I'll take a look. [13:35] sforshee, thanks [14:43] * ogasawara back in 20 [14:43] diwic, ok just tested that mumble. it seems to not change still [14:43] apw, mumble mumble...in both meanings [14:44] diwic, hehe [14:46] diwic, seems to be using the snowball whatever i do now with it on Default [14:57] apw, I will run some tests here and see if I can confirm what's happening [15:13] * ppisati -> out for some grocery, back in~30 === kamalmostafa is now known as kamalm [16:14] ogasawara: did pgraner get anywhere on that kernel hang he was getting on friday ? === bjf[afk] is now known as bjf [16:14] bjf[afk]: I don't believe so, and I wasn't able to get in. [16:14] bjf, no you said you were going to work on it, I was traveling remember [16:15] pgraner: ogasawara, have not been able to get to the console, tried *many* times [16:15] bjf, let me try [16:15] pgraner: am trying again right now [16:15] apw, bjf, cking, herton, jsalisbury, henrix, ppisati, sforshee, smb: fyi, top ten mumble call is mandatory today (ie 15min from now) [16:16] ogasawara, k [16:16] ogasawara, heh ... such notice :) [16:16] apw: the calendar event somehow went to /dev/null [16:17] ** [16:17] ** Ubuntu Kernel Team Meeting - Today @ 17:00 UTC - #ubuntu-meeting [16:17] ** [16:19] pgraner: "Error while getting the list of open Targets, please try again in a few seconds." [16:20] bjf, same for me [16:21] bjf, I'll power cycle it and see if that helps [16:21] pgraner: ack [16:25] bjf, no joy for me you try [16:25] pgraner: trying ... [16:28] pgraner: same error [16:29] bjf, precise? [16:29] pgraner: yes [16:29] bjf, did icedtea get updated recently? [16:29] * pgraner don't know [16:30] pgraner: there was an upload on 4/10 [16:30] bjf, hmmm I've used it since then [16:35] bjf, it works on my precise laptop but not on my desktop [16:35] pgraner: sweet [16:51] pgraner: i'm trying a different system, can you release the console [17:09] pgraner: got a console up but "No video from target server" [17:09] bjf, that means its powered down, just kick with with the pdu === jsalisbury changed the topic of #ubuntu-kernel to: Home: https://wiki.ubuntu.com/Kernel/ || Ubuntu Kernel Team Meeting - Tues April 24th, 2012 - 17:00 UTC || If you have a question just ask, and do wait around for an answer! [17:15] pgraner: i've power cycled it twice, no change. i'm using: http://192.168.22.5/main.html?1,1 outlet: A5 [17:16] bjf, hmmm [17:16] bjf, that the right PDU & Port [17:17] bjf, let me try and get in over the IPMI bmc [17:18] pgraner: ack, i've close the console [17:22] bjf, I think that box might be dead [17:22] bjf, try connecting to node1 you should see stuff on the screen [17:22] pgraner: that sucks [17:22] bjf, just to make sure your config is indeed working [17:23] pgraner: yup, it's working [17:23] ok, let me go have someone hit the pwr switch [17:29] bug 984180 [17:29] Launchpad bug 984180 in linux-ti-omap4 "ext2 module missing from fs-core-modules udeb." [High,Triaged] https://launchpad.net/bugs/984180 [18:18] * jsalisbury curses at thunderbird === kamalmostafa is now known as kamal [18:55] ppisati: I assume the fix you sent for 984180 needs uploading asap? [18:56] ogasawara: yes, if possible [18:56] ppisati: I'm also going to fixup the commit to insert the BugLink [18:57] ogasawara: ouch, right [19:07] Hello! I tried Canonical/Ubuntu image for running Ubuntu11.10 on Beagleboard B4. The image I used was - http://cdimage.ubuntu.com/releases/11.10/release/ubuntu-11.10-preinstalled-desktop-armel+omap.img.gz - and followed https://wiki.ubuntu.com/ARM/OmapNetbook but I see a blank screen on gtkterm. Is there anything I'm missing? [19:07] orated: uhm, strange [19:07] orated: that's an old release [19:08] orated: what do you see on the terminal screen? [19:09] I tried booting the SD card and I could see nothing on gtkterm or any other serial terminal. The ports are configured right [19:09] orated: then chances are you dd-ed wrong on the sd [19:09] orated: or the sd has problems [19:10] zcat $imgfile | sudo dd of=/dev/$sdX bs=64k [19:10] orated: try like that [19:11] ppisati: uploaded [19:11] ogasawara: thanks [19:11] ppisati: The command I used was - gunzip -c ubuntu-11.10-preinstalled-desktop-armel+omap.img.gz | sudo dd bs=4M of=/dev/mmcblk0- [19:11] orated: dd bs=4M of=/dev/mmcblk0 ?!?!? [19:12] orated: ls -la /dev/mmcblk* [19:14] Yes, my SD card is detected like that - Disk /dev/mmcblk0: 7948 MB, 7948206080 bytes. [19:14] brw-rw---- 1 root disk 179, 0 2012-04-18 00:42 /dev/mmcblk0 [19:14] brw-rw---- 1 root disk 179, 1 2012-04-18 00:42 /dev/mmcblk0p1 [19:14] Sorry, one moment [19:16] ppisati: http://pastebin.com/x1ChZWKQ [19:17] .. is the correct one. [19:19] orated: what do you see when you turn on the board? [19:20] Nothing, just a blank screen. I switched on the board with both reset and User1 depressed [19:21] I mean turning on while holding User1 button [19:21] orated: beagle look for the bottloader in the internal flash IIRC [19:21] orated: wait [19:21] You mean the bootloader of the board is required to be reflashed? [19:22] orated: http://code.google.com/p/beagleboard/wiki/BootingBeagleBoard [19:22] orated: if you don't see anything when you turn on the board, then yes [19:27] nand erase won't work? [19:29] ah, got it. Thanks ppisati [19:46] ppisati: Are you still there? [20:07] apw, moar gpu lockups. #982251 looks worth tending on the kernel side. [20:08] apw, surprised none of these are showing up still on http://reports.qa.ubuntu.com/reports/kernel-bugs/reports/_kernel_graphics_bugs_.html [20:09] Ooo, german [20:10] bryceh: I think apw is probably away at the moment, or at least he should be. I'll get a test kernel posted. [20:11] bryceh: I believe jsalisbury mentioned issues with reports on cranberry (running out of space). likely explains why the report is not getting updated as I think they've been turned off for the time being. [20:12] bryceh, ogasawara, correct. cranberry is out of disk space. I opened an RT ticket a week ago. The reports on people.canonical.com should still work. [20:12] ogasawara, jsalisbury ah [20:12] bryceh, This one should be up to date: [20:12] http://people.canonical.com/~kernel/reports/_kernel_graphics_bugs_.html [20:13] aha that looks better [20:13] This is the top level for all the reports: [20:13] http://people.canonical.com/~kernel/reports/ [20:14] 982415 also looks worthwhile to do a kernel for, if there isn't already one with this patch [20:14] bryceh: ack, will investigate [20:14] bug 982415 [20:14] Launchpad bug 982415 in linux "[i915gm] False GPU lockup render.IPEHR: 0x3f800000" [Undecided,Confirmed] https://launchpad.net/bugs/982415 [20:15] ogasawara, thanks [20:43] can someone confirm/deny pae kernel for precise? [20:43] right now it seems I can't install the current daily iso on non-pae hardware.. I thought we kept non-pae support for this cycle [21:04] balloons: we kept support, but the installer was changed to default to the pae kernel. there's a few alternative options... you could use the mini.iso which I believe uses the non-pae kernel by default, also I think Xubuntu does as well. Or you could install Oneiric and upgrade to Precise. [21:05] ogasawara, thanks for the response.. the only discussion I had seen on it was we were keeping support for it [21:05] so I was surprised to find it not working [21:05] balloons: there was a long thread on ubuntu-devel I think. lemme see if I can find it for you [21:09] balloons: and it was raised on the tech board as well [21:09] balloons: tech board minutes -> https://wiki.ubuntu.com/TechnicalBoard/TeamReports/11/December [21:09] balloons: ubuntu-devel thread -> https://lists.ubuntu.com/archives/ubuntu-devel/2011-November/034399.html [21:10] ogasawara, awesome.. I'll go read [21:10] balloons: the tech board minutes highlight the outcome and is more digestible than the mailing list thread [21:10] thank you much [21:11] * ogasawara wanders off for a bit === yofel_ is now known as yofel