/srv/irclogs.ubuntu.com/2013/10/10/#ubuntu-kernel.txt

stgraberhey there, just tried using a standard generic kernel on my wandboard (imx6) and I'm getting this in dmesg followed pretty shortly by a full system hang: http://paste.ubuntu.com/6216221/00:54
stgraberthat's with the latest saucy kernel though I actually never managed to get a stable distro kernel to work on that one00:55
stgrabertaking the same 3.11 kernel built by fedora (so probably slightly different kernel config) works fine00:55
stgraber(but I'd rather use the Ubuntu one from the archive since it gives me aufs and overlayfs which are rather nice on a system I use as a buildd)00:55
stgraberinfinity: not sure if that rings a bell ^00:58
infinitystgraber: I suspect you'll find that our kernel and fedora's differ a lot more than just in configs. :/00:59
infinitystgraber: But not familiar with that bug in particular, no.  My imx6 has been idle a while.00:59
stgraberyeah, I'm already trying to get a config diff here and it seems rather massive, then I have no idea how many patches fedora has on top of upstream01:00
infinitystgraber: Anyhow, file a bug, point to the sources matching the working Fedora kernel.  I suspect it might take someone with a bit of smarts very little time to diff A B, compare to backtrace, and see where we might have gone wrong.01:00
stgraberand the current upstream git is failing to build for me (fails in some devicetree code) so I can't test if 3.12-rc4 is any better01:01
stgraberbug 123773301:21
ubot2Launchpad bug 1237733 in linux (Ubuntu) "Kernel hangs on wandboard (freescale imx6)" [Undecided,New] https://launchpad.net/bugs/123773301:21
=== fmasi_afk is now known as fmasi
* henrix -> lunch11:59
=== fmasi is now known as fmasi_afk
apw* powerpc12:36
apw  blktap (2.0.90-2ubuntu1): blktap-utils12:36
apwbah12:36
=== psivaa is now known as psivaa-afk
ppisatiwhy is there an ubuntu-desktop metapkg but no ubuntu-server metapkg?14:28
ppisatii see the edubuntu-server* but no ubuntu-server14:29
ppisatiweird14:29
ppisatiactually the edubuntu pkgs are not meta14:30
=== psivaa-afk is now known as psivaa
=== ricmm_ is now known as ricmm
manjoppetraki, around ? 15:09
ppetrakimanjo, uh yeah15:19
manjooh15:19
manjoppisati, around ? 15:19
ppisatimanjo: what?15:20
manjoppetraki, there is a thread with Andre ... seems like we need an option for virtio console 15:21
manjoppisati, ^15:21
ppisatimanjo: http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-saucy.git;a=shortlog;h=refs/heads/master-next15:21
ppisatimanjo: build it and check it out15:21
manjoawesome! thanks 15:22
bjfkamal, what's the story on bug 1162026 and bug 1163720 ?15:44
ubot2Launchpad bug 1162026 in linux (Ubuntu Raring) "backlight not adjustable after screen turns off and then back on" [Medium,Fix released] https://launchpad.net/bugs/116202615:44
ubot2Launchpad bug 1163720 in Linux "Brightness control broken on XPS13 with 3.8.0-16 and 3.8.0-22" [Medium,Incomplete] https://launchpad.net/bugs/116372015:44
* kamal throws self from top of nearest spire . . .15:45
* ppisati goes out for a bit15:46
bjfkamal, the "issue" for me is that these have been backported to precise, are in the precise changelog, there is no precise task on the bug and they need verification15:47
bjfkamal, i guess that should be "issues" :-P15:47
manjoppisati, what branch is it on ? master-next ? 15:47
ppisatimanjo: yes15:48
kamalbjf, ok, I think 1162026 is actually fixed nowadays (do you want to create a precise task for it?  same for quantal, I suppose?)15:49
* ppisati notes my push-to-talk button is broken15:50
ppisati:P15:50
bjfkamal, i really just care that the "verification" tag gets added to the bug so that my report turns green 15:50
kamalbjf, 1163720 is an open issue (problem exists upstream also) ... I don't actually know if that bug can manifest on precise or not (I really don't even want to go find out).15:51
kamalbjf, oh, so you just want me to verify it then change the verification-{needed/done}-precise tag ?   no new task line required?15:51
apwif the bug is being released into precise in an lts kernel or similar then we should have tasks for it , so that launchpad has something to close15:52
bjfkamal, really both should happen but the tag is what i care most about15:52
bjfkamal, what apw said15:52
apwkamal, if you cannot nominate let me know what you need adding to what bug and i'll slam them in15:53
bjfkamal, i've taken care of adding the precise series to the bugs15:57
kamalbjf, ok thanks ... but I'm scratching my head about 1163720 ...  its certainly _not_ fixed at this point, but that fact should not make "this fix will be dropped from the source code, and this bug will be closed" occur!15:59
kamalbjf ... because "this fix" wasn't actually supposed to be the fix for that bug.16:00
kamalbjf, can I just take away "Fix Released" from 1163720?  (make it "In Progress" or something?) ... and remove the verification-needed-* tags?16:02
bjfkamal, well ... wasn't it fix released for raring? (or are you telling me it's not?)16:04
apwkamal, it ought to have only flagged up on bjfs list cause it has the bug number in the commit log right?16:05
kamalbjf, 1163720 is *not* fixed for any release at all16:05
bjfkamal, when i read that bug it looked like the commit fixed the original issue and then there was a new issue16:05
apwkamal, not even saucy ?16:05
kamalbjf, apw: the commit just shouldn't have referenced 1163720 at all16:05
bjfkamal, ok, fair enough16:06
kamalthat bug does still exists in saucy (and upstream)16:06
apwommit 8029954e6aa79d3fdc44b0353f6c9c4a8a65672516:06
apwAuthor: Kamal Mostafa <kamal@canonical.com>16:06
apwDate:   Fri Jul 19 15:02:01 2013 -070016:06
apw    drm/i915: quirk no PCH_PWM_ENABLE for Dell XPS13 backlight16:06
apw    16:06
apwkamal, that one lists it 16:06
apwso the tools assume it is fixed16:06
kamalapw, that was a mistake on my part then.16:06
bjfkamal, then in that case i would think the right thing to do is to change the status to in-progress16:06
apwkamal, and we need to find out which bug you meant to put in there16:07
bjfkamal, and we'll just ignore the verification tags for this bug for this cycle16:07
bjfapw, that commit has 3 bugs listed i believe16:07
kamalapw, bjf, yes, that commit already has (also) the correct buglink16:08
apwbjf, yeah, it does indeed, there will be some fallout to fix the bugs it does not fix16:08
kamalbjf, ok, I will change 1163720 to "In Progress", and I think I should remove the verification tags from it also (yes?)16:10
=== yofel_ is now known as yofel
=== ChickenCutlass is now known as ChickenCutlass_l
* cking -> EOD17:34
eriduhey ubuntu kernellers, I'm tedks on launchpad, and I mistakenly closed this bug after corresponding with jsalisbury about it: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/113308717:56
ubot2Launchpad bug 1133087 in linux (Ubuntu) "Ubuntu shows grains like screen after the splash from kernel (3.8.0-5)" [High,Fix released]17:56
jsalisburyeridu, ok.  I'll take a look.17:57
eriduit turns out that after installing the generic linux package and upgrading via apt, I installed the Ubuntu linux-image package, but wouldn't boot from it. So I made a mistake by closing that bug. With the latest (as of now) version of linux-image, I can't get to X on my system.17:57
eridujsalisbury: thanks -- sorry for screwing this up, I'm still willing to test any bisected kernels you throw my way. and I'll double-check the uname this time :-)17:58
jsalisburyeridu, np.  I'll re-open the bug and add some comments.17:58
eriduawesome, thanks.18:00
=== ChickenCutlass_l is now known as ChickenCutlass
* rtg -> lunch19:05
rtgbjf, care to chime in on this thread so I can get it out of my inbox ? https://lists.ubuntu.com/archives/kernel-team/2013-September/032841.html20:27
bjflooking, i thought it was handled so i deleted it already20:28
rtgbjf, just looking for the 2nd opinion20:28
bjfrtg, didn't we ask for more testing on that?20:32
rtgbjf, He says he tested on 4 other platforms20:32
bjfrtg, i ack'd it20:34
rtgbjf, k20:34
* rtg -> EOD21:27

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!