keesapw: I've finished the 3-phase old kernel bug tracker sync stuff now. I've done a bunch of status and description updates as well.03:08
keesapw: there are a few more corner cases I ran into, but I've been documenting it in the uct README file. of most note is how to add and remove SHAs from the bug descriptions.03:09
=== smb` is now known as smb
* smb -> BOD07:27
* apw yawns08:39
* smb waves08:41
* abogani waves back to all08:43
tjaaltonwere there some scripts to aid debugging when suspend fails to work?08:56
tjaaltonmy snb desktop hangs while trying that on oneiric08:56
smbNot sure how much Colin built into fwts, but he also had some system tap scripts somewhere08:57
smbBut there also was some bug (I fail to remember atm) that system tap in oneiric was broken..08:58
tjaaltoni'll try fwts08:58
smbbug 81594408:59
ubot2Launchpad bug 815944 in systemtap "systemtap on Oneiric breaks because of kernel commit 449a66fd1fa75d36dca917704827c40c8f416bca" [High,Confirmed] https://launchpad.net/bugs/81594408:59
apwsmb, i suspect that systemtap needs to change to follow, it is its lot (to break ceaslesly)09:02
smbapw, Yeah, I don't think we want to follow a road of changing back the kernel, when the upstream path is to have it removed.09:04
marcoceppiDo I need to do anything special in order to create a deb source of the kernel that LP can build?12:30
marcoceppiMaybe a magic wiki article that I missed?12:30
ubot2The core of Ubuntu is the Linux kernel: see https://help.ubuntu.com/community/Kernel - You shouldn't have to compile your own, and if you need to troubleshoot issues, you can try a !Mainline kernel instead, but if you insist, see https://help.ubuntu.com/community/Kernel/Compile (see also !Stages)12:33
smbmarcoceppi, Something like that?12:33
ubot2A list of common questions about the Ubuntu Kernel can be found in http://wiki.ubuntu.com/Kernel/FAQ12:33
apwmarcoceppi, how did it fail ?  we covered clean yesterday i think12:33
marcoceppiYeah, here is the last line from the build line12:36
marcoceppienable deprecated sysfs features which may confuse old userspace tools (SYSFS_DEPRECATED_V2) [Y/?] y12:38
marcoceppimake deprecated sysfs layout dynamically (SYSFS_DEPRECATED_DYN) [Y/n/?] (NEW) aborted!12:38
marcoceppiConsole input/output is redirected. Run 'make oldconfig' to update configuration.12:38
marcoceppimake[5]: *** [silentoldconfig] Error 112:38
marcoceppimake[4]: *** [silentoldconfig] Error 212:38
marcoceppimake[3]: *** [sub-make] Error 212:38
marcoceppimake[2]: *** [silentoldconfig] Error 212:38
marcoceppimake[1]: *** [sub-make] Error 212:38
marcoceppimake[1]: Leaving directory `/build/buildd/linux-2.6.32-33.72'12:38
marcoceppimake: *** [/build/buildd/linux-2.6.32-33.72/debian/stamps/stamp-prepare-tree-generic] Error 212:38
marcoceppidpkg-buildpackage: error: debian/rules build gave error exit status 212:38
marcoceppiThe source was built properly, lp build spit this back. I ran make oldconfig in my source tree and it built the .config without an issue. So I wonder if it's not getting my saved config somehow12:38
apwyou seem to have an out of date config12:39
apwfakeroot debian/rules updateconfigs12:40
marcoceppiSo running that seems to produce check-config errors. I assume that I'll need to do something about that.12:43
smbherton, That new lucid kernel upload, I guess that means I should prepare an ec2 tree. Though I cannot remember having seen any bot or person bugging me about that...12:46
hertonsmb: the new lucid kernel was just a respin to revert 2 changes for bug 811745. We should be creating new tracking bugs for you, but this isn't ready yet12:49
ubot2Launchpad bug 811745 in linux "Whole system freeze after safely remove external usb drive" [High,Fix committed] https://launchpad.net/bugs/81174512:49
hertonsmb: not a respin, but a new update I mean just for that bug12:49
smbherton, Ah, ok. So I better wait until you are ready. I was just wondering whether I missed something there12:51
smbUnplugging an external usb drive in the cloud is difficult anyways...12:51
apwsmb, does it not have usb emulation ?12:52
smbapw, Not the normal usage. There could be ide or scsi emulation but actually only the virtual block devices are used as the are quicker12:54
marcoceppiThanks for your help thus far. I'm getting closer. The build servers are telling me that the source isn't clean and that I need to make mrproper - however, when I run that in my local source it removes a lot of the debian control items.13:58
apwmarcoceppi, you need to "rmdir include/config" normally to fix that13:58
marcoceppiAh, I'll give that a try. Thank you14:00
* ogasawara back in 2014:24
bjf## Ubuntu Kernel Team Meeting - Today @ 17:00 UTC - #ubuntu-meeting14:30
bjf##      agenda: https://wiki.ubuntu.com/KernelTeam/Meeting14:30
=== kamalmostafa is now known as kamal
bjf## Kernel team meeting in one hour16:00
ogasawarabjf: I noticed bug 819632 from the daily bug report16:13
ubot2Launchpad bug 819632 in linux "WARNING: at /build/buildd/linux-2.6.31/net/sched/sch_generic.c:246 dev_watchdog 0x1f6/0x210()" [Undecided,New] https://launchpad.net/bugs/81963216:13
ogasawarabjf: it's against a karmic kernel (which your scripts correctly detected)16:13
ogasawarabjf: just curious if you'd want to auto close it rather than have it appear on the report?16:14
bjfogasawara, yes, but it didn't get the right tag (and it's an unsupported series)16:14
bjfogasawara, i'll look into it16:14
ohsixherton: i just got an unrelated panic (in the wifi stack) on wakeup with -9, so i'm running -11 now and i'll get a screen asap16:25
hertonohsix: ok16:30
marcoceppiHum, so I removed include/config and I'm still getting mrproper error during the build. Is there anything else I might need to do?16:55
BenCmarcoceppi: make mrproper16:55
apwmarcoceppi, well the tree should be made clean, so checkin anything you have changed16:55
apwthen git clean -f -x -d, note this will DELETE any files not tracked by git16:56
apwthen fakeroot debian/rules clean, then package it16:56
marcoceppimrproper removes all the debian/ files - so I won't be able to run debuild16:56
BenCmarcoceppi: mv debian ../debian.orig; make mrproper; mv ../debian.orig debian16:56
marcoceppiAh, makes sense. Let me try that16:57
marcoceppiShuould I rape mrproper in fakeroot?16:58
apwdon't think so16:58
bjf## Meeting starting now17:01
apwbdmurray, i'd be interested in more details of the changes if you able to send them out17:11
bdmurrayapw: the changes already made or what I think should happen now?17:13
apwbdmurray, right, but of what we might find different17:14
alfmatosjust reported bug #81992517:20
ubot2Launchpad bug 819925 in linux "iwlwifi driver exports all packets through netlink" [Undecided,New] https://launchpad.net/bugs/81992517:20
apwogasawara, ^^ that sounds like something to put on your config-review list17:20
* ogasawara looks17:21
* ogasawara adds a work item17:21
alfmatosthat should default to N i would assume =)17:21
bjfapw, hah! you beat the script17:22
apwbjf, yeah stop the spam17:22
alfmatoswell, that's all i got, thanks guys =)17:23
ogasawaraalfmatos: I'll get it flipped to N and it'll be in the next upload after Alpha317:23
cprofitthell all...17:29
ubot2Ubuntu bug 776999 in linux "[Lenovo W520] laptop freezes on ACPI-related actions" [Undecided,Confirmed]17:29
cprofittwas looking for a little bit of advice on how to move this from confirmed to triage17:30
cprofittI have a W520 and could assist gather some information17:30
marcoceppiI seem to be getting a lot closer to it actually compiling. The seemingly last hurdle is that 7 configuration values fail check-config. Should I just remove those? Is it maybe they no longer exist in this version of the kernel and are just old?17:35
apwmarcoceppi, what version of the kernel is the config from and what is the version of the kerenl17:47
marcoceppiapw I have the latest from ubuntu-lucid.git -33.72 I copied the config from a lucid VM with the latest installed from the repo17:53
apwmarcoceppi, then no i would not exect the config to change at all17:54
ogasawarabjf: pastebin me the minutes, I'll shove em to voices17:55
apwbjf, i say don't bother to publish them17:55
apwits not a high priority for us apparently17:56
marcoceppiapw: The build fails at these 7 entries: http://paste.ubuntu.com/657368/17:56
apwmarcoceppi, but the config for a lucid kernle would have those set17:56
bjfapw, ogasawara i've been assured that this will be fixed today, if not i will send email to pgraner that we will no longer be blogging our meeting minutes17:56
apwand set correctly else the same failure would have prevented the kernel you have from building in the first place17:56
ogasawarabjf: ack17:56
marcoceppiapw: Makes sense. I'll try to figure out where I went wrong. I may try re-copying the configurations over and running updateconfig again17:58
bjfogasawara, http://pastebin.ubuntu.com/657372/ (thanks)17:58
apwwhy not use the config which is in the tree?  given it is for the same kernel17:58
marcoceppiI was just following the instructions from https://wiki.ubuntu.com/KernelTeam/GitKernelBuild I may have gotten confused and copied when I shouldn't have.17:59
marcoceppiSo should I just checkout the configuration files from the last clean commit in the ubuntu-lucid.git? I assume it's in debian/build/ directory?18:02
bjfmarcoceppi, https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel is a good, basic starting point18:02
marcoceppibjf: Thanks, I was linked to it yesterday - I'll probably just start from their this time18:04
jjohansenmarcoceppi: ping me if you run into problems18:05
marcoceppiI'm trying to avoid starting from scratch. It took me about 5 hours to patch the kernel. Soo, let me see if I can back up until right after I patched18:08
marcoceppiOkay, I think I've gotten to a point where I can try to perform a clean build. Would it be beneficial to build the kernel locally before trying to get LP to build it? 18:16
apwmarcoceppi, depends how fast your local build is18:20
marcoceppiIt's still failing at those configurations. I wonder if it's because I patched v2.6.32 in the git line, then merged down the changes up to 2.6.32-33.7218:25
* tgardner --> lunch18:25
* smb -Y eod18:25
marcoceppiIf I remove those values, I assume it would make me re-enter them if it really needed it, right?18:25
apwmarcoceppi, nope, it will then not have things set you need in order to boot most likely18:26
apwif you mean removing them from the config check18:26
marcoceppiI mean removing them from the build's .config18:26
apwit will ask you to set thme yes on updateconfigs18:26
marcoceppiThen what would be causing check-config to throw the error? Could it be expecting a different value?18:27
apwwhat values do the config options have in your config ... git grep FOO debian.master/config18:28
marcoceppiWhen I search the debian/build/build-generic/.config file those keys don't exist18:28
apwif you got the configs and the enforcer file from the same or nearly the same version of the kernel then they should match18:28
apwmarcoceppi, thats generated during the build and not interesting as much as the master for them18:29
marcoceppiLet me check the master18:29
marcoceppiAll of these keys and values exist in config/enforce config/config.common.ubunut and config/config.common.ports18:31
marcoceppiSo, I should run debian/control updateconfigs then try again?18:33
apwif you do a fakeroot debian/rules prepare-generic (or whatver falvour you care about)18:34
apwyou can see if the built cdonfig has what you need in it18:34
marcoceppiIt built, but failed with the same 7 check-config errors like before18:35
apwyou said they were present and correct in the config master files yes ?18:36
apwso then the question is what patches have you applied18:36
marcoceppiI applied the OpenVZ patch18:36
marcoceppifor 2.6.3218:37
apwso perhaps they prevent those options being set, and you are in a world of hurt18:37
apwdoes the openvz patch set include any configuration (Kconfig) file updates, add any additional depends ?18:37
marcoceppiIt changes a few kconfigs. It doesn't add any external dependencies that I know of18:38
apwwell if an option is in the master configs and not in the resultant built .config in debian/build18:38
apwthen there must be a configuration dependancy that is stopping them18:38
apwso you need to pick one and validate its pre-requisites18:39
apwand find out why its now off/difffernet18:39
* apw eyes the beer on his desk ... you are mine18:39
marcoceppiI see, so it's it's time to chase down "why"?18:40
apwyep sadly so18:40
marcoceppiWell the majority is related to SELINUX and APPARMOR which I know does not work with OpenVZ18:41
apwthen that would explain why they go missing18:41
apwif they are incompatible18:41
marcoceppiSo, updating the enforce file would be...the solution?18:41
apwthen you need to remove the enforcement for them, as they can never be set18:41
apwand pay the consequences if userspace needs them18:41
marcoceppiWell, I'll chase down the others to make sure it's something that is supposed to be missing. Thanks for your help apw enjoy your beer :)18:42
marcoceppiAwesome, OpenVZ doesn't support DEVTMPFS as well. This is going to be a pain now that I look at it.18:51
apwnow that is going to be a tricky one18:56
apwupstart may cope18:56
marcoceppiI hope so18:58
marcoceppiI mean, if people are able to use the linus 2.6.32 kernel on 10.04 I *should* be able to use 2.6.32-33.72 with the patch? right?18:59
marcoceppiwell _maybe_18:59
apwexcept that that supports devtmpfs19:00
marcoceppiwhat I mean was 2.6.32 with the OpenVZ patch (which it was created for)19:01
apwif the openvz patch is known to work on ubuntu then yours should, is what i think you are saying19:02
keesapw: how did yesterday's bug status sync look to you?19:07
marcoceppiapw: Yes, only I didn't articulate it very well.19:10
apwkees, didn't see anything out of order19:13
keesapw: excellent19:13
apwwil keep a weather eye19:13
keesherton: do you know who is doing the publication of the maverick linux package? it seems to have only hit -updates...19:14
hertonkees: no idea19:14
keesherton: okay, thanks19:14
hertonkees: sconklin is looking into it, he was told slangasek did the publishing19:56
sconklinkees: it's being worked19:56
marcoceppibjf apw:  Thanks for your help. I'm able to get past the configuration issues from earlier - now I just need to fix the code errors!19:59
keessconklin: thanks!20:00
* tgardner -> EOD20:18
* jjohansen -> lunch20:20
keesapw, sconklin: do either of you know the status of ti-omap4 for maverick?20:27
sconklinkees: no20:27
keessconklin: what's needed to make it show up on http://people.canonical.com/~kernel/reports/sru-report.html ? just open bugs?20:28
sconklina tracking bug that's in process20:28
keessconklin: hm, okay. I guess I don't know what takes stuff from http://people.canonical.com/~apw/cve/pkg/ALL-linux.html in "pending" to showing up on http://people.canonical.com/~kernel/reports/sru-report.html20:29
keesI'll ping apw tomorrow20:29
sconklinkees: is this helpful? http://people.canonical.com/~kernel/reports/versions.html20:29
sconklinprobably not20:29
keessconklin: I think that just shows me that there isn't something in the PPA waiting for workflow progress20:30
sconklinthat's right, and nothing in -proposed20:30
keessconklin: oh, what about linux-lts-backport-maverick? it seems to be missing a tracking bug?20:33
sconklinkees: looking20:35
hertonsconklin, kees: for linux-lts-backport-maverick it's bug 811215, but it doesn't show on sru-report20:37
ubot2Launchpad bug 811215 in kernel-sru-workflow "linux-lts-backport-maverick: 2.6.35-30.56~lucid1 -proposed tracker" [Undecided,In progress] https://launchpad.net/bugs/81121520:37
keesherton: ah, thanks.20:37
sconklinherton: thanks, I was waiting for git to fetch20:37
sconklinwe'll figure out why that's not in the report20:38
bjfsconklin, i'm looking at the kernel-sru-worflow and the tracking bug shows there, heading to the sru-report20:44
sconklinbjf: thanks!20:44
hertonyep, the sru-report is the one which misses it20:47
=== yofel_ is now known as yofel
medberrycnd, the recent 10.04.3 kernel update "broke" my clickpad in Lucid. I've got an HP ProBook 4320s and stayed on Lucid as Maverick forward don't work properly with the clickpad.21:49
medberrynow that forward problem has come back to haunt me.21:49
medberryAny suggestions?21:49
cndmedberry, can you provide more details on what's wrong?21:50
medberrythe left center right areas are treated as one area cnd.21:52
medberryand it's also really "touchy". Making it much more difficult to click and drag now.21:52
medberryI suspect the 10.04.3 kernel SRU pulled in some mouse/input changes (similar to what were in Mav and Nat all along.)21:52
cndmedberry, can you describe the layout of your trackpad? what do you mean by left center right areas?21:53
medberrysure: the clickpad has a "T" shape overlay on the bottom 20% where the middle of the T is in center bottom.21:54
medberryrepresenting "left" and "right" mouse buttons. Moreover, the bar of the "T" functioned as a middle click.21:55
medberryNow, I'm back to the whole area representing a left click (irrespective of the markings.)21:55
cndmedberry, I'm guessing there was a kernel patch that was in lucid that was not upstream to handle these trackpads21:57
medberryso "left" is more less the bottom 20-25% and the left 40%, center is the bottom 20-25% and the middle 20% and right is the right most 40% of the bottom 20-25%. I can send a picture if it helps.21:57
cndbased on a vague memory of what's happened in this area21:58
cndsconklin, do you remember any changes in drivers/input/mouse/synaptics.c that went into the latest lucid kernel updates?21:58
sconklincnd: no but it's really easy for me to check21:59
cndmedberry, I'll add that upstream still doesn't have a great solution for this, IIRC21:59
medberrycnd, to clarify, afaict, this is still broken/crippled in M/N/O-alpha as well.21:59
medberrycnd, yes, I think that's the issue.21:59
cndthe kernel should provide the raw coordinates, which is what occurs in M/N/O/etc.21:59
medberrydid lucid release with a kernel that didn't have the pointer stuff "in kernel". That's my understanding (or misunderstanding)22:00
cndbut xserver-xorg-input-synaptics needs to handle clickpads properly22:00
cndwhich it doesn't right now22:00
sconklincnd: I don't see any recent changes to that at all22:00
sconklini.e. last patch was in April 201022:01
medberryI'm going to double check my assumption that it was a kernel change that made the difference. Please disregard until I've completely verified that is the delta.22:01
cndmedberry, can you check to see what events are emitted by the kernel in the good and bad kernels?22:01
cndyou can use evtest to see the events22:01
medberryI'll do that and get back to you. Thanks.22:01
cndthe "good" kernel probably is emitting BTN_LEFT, BTN_RIGHT, and BTN_MIDDLE22:01
cndwhereas the "bad" kernel is probably only emitting BTN_LEFT22:02
sconklincnd: I may have found what happened with input22:10
ubot2Ubuntu bug 814186 in linux-backports-modules-2.6.32 "linux-backports-modules-wwan and -input packaged incorrectly" [Medium,Fix committed]22:10
sconklinpreviously the input driver from lbm wasn't getting loaded, and apparently now it is22:11
cndmedberry, do you have linux-backports-modules-synaptics installed?22:12
cndsconklin, I'm not sure that works out though22:12
cndso if lbm is installed, the synaptics module may be the server version22:12
cndand so it would fail to load22:13
cndbut then you'd end up without any input modules loaded22:13
sconklinyeah, it only applies if lbm is installed22:13
cndactually, that might work out22:13
cndI dunno :)22:13
sconklinwell, the kernel also has some input drivers without lbm, so I believe you would just get a different driver22:13
cndit could be picking up a static standard PS2 driver instead22:14
cndand I wouldn't be too surprised if these clickpads worked better in PS2 mode than in full synaptics mode :)22:14
sconklincnd: a bug with collected info would be helpful. And is this from -proposed? because that change hasn't been released yet22:17
sconklinmedberry: are you running -proposed?22:17
cndsconklin, meet medberry :)22:17
sconklinmedberry: the most helpful thing now is to run 'ubuntu-bug linux' and get all your info into a bug22:19
medberrysconklin, cnd, nod.22:21
medberrysconklin, dpkg -l linux-backport\* reports nothing 22:22
jwinote that several touchpad "regressions" have been reported after the update to -33.70; 811420, 811753, 811962, 81535722:22
=== medberry is now known as med_brb
=== med_brb is now known as med
=== med is now known as medberry
bjfjwi, bug 811753 is against .32-32.62 where the other three are .32-33.7022:40
ubot2Launchpad bug 811753 in linux "Synaptics Touchpad keys stoped working" [Undecided,Confirmed] https://launchpad.net/bugs/81175322:40
medberrysconklin, my experience is similar to 811753. cnd: evtest reported  can't get version: Inappropriate ioctl for device (no matter which mouse dev I chose.)22:41
cndgah, the stupid evdev protocol version issue22:41
cndmedberry, get the oneiric evtest package and install it22:42
bjfjwi, how do you happen to be tracking those bugs, are you watching input bugs or lucid regressions or ... ?22:42
cndit should work just fine22:42
medberrynod, will do.22:42
bjfogasawara, ping (just if you happen to be around right now)22:42
medberrycnd, oneiric evtest behaved the same: Inappropriate ioctl for device23:00
medberryI then ran "xinput test ##" with my device on both23:00
medberrythe new kernel reports only button 1 events (and they occur anywhere on the clickpad). The old kernel reports all three buttons but only in the lower 20-25% of the screen.23:01
medberryBoth report movement but the old kernel only reports mouse motion in the top 75-80% of the clickpad. The new kernel reports all over. So it's just one giant button/mouse in its behavior.23:01
medberry(which as I understand accurately reflects the hardware--software heuristics are required to get the B1, B2, B3 and to distinguish between the "mouse" and "button" areas.)23:02
medberrymy work around for now is to use the 2.6.32-32 kernel23:03
jwibjf: incoming regressions, mostly. re 811753: note the user's description, I guess it was reported from the old/working kernel23:06
bjfjwi, i was looking at the bootdmesg23:07
medberryjwi, bjf : if you need a guinea pig for these issues let me know. My issue most closely resembles 811753.23:08
bjfmedberry, i have nothing to offer right now23:19
medberryno worries. Thanks guys.23:21
cndsconklin, bjf: where's the code for the workflow mgr bot?23:31
bjfcnd kteam-tools23:31
bjfcnd, it's kind of complicated because it's trying to manage a specific workflow, but it wouldn't be bad to start with, gut it and do your own23:33
cndbjf, how do you develop? what's your testbed?23:33
bjfcnd, unfortunately the best thing to use is the qastaging server23:33
bjfcnd, if you look at the code, there is a --staging command line flag that you can use23:34
cndwhat's the qastaging server?23:34
cndis it some semi-permanent instance?23:34
bjfcnd, you can create any bugs over on that server/service (a testing LP instance)23:34
bjfcnd, it's got a snapshot of the DB, so any changes you make there are not seen on the production server23:35
cndahh, cool23:36
bjfcnd, the problem with it is that it isn't real stable23:37
* cnd just hit an error23:37
cndbjf, I assume things are wiped every so often?23:38
bjfcnd, yes, something like weekly23:38
bjfcnd, https://bugs.qastaging.launchpad.net/ubuntu/+source/evolution/+bug/77777723:39
ubot2Ubuntu bug 777777 in evolution "Mark read / unread only works once in message window" [Low,New]23:39
bjfcnd that worked for me23:39
cndbjf, where's the documentation for the launchpad api?23:39
bjfcnd the bot uses the LPLTK which is a slick on top of the LP api23:40
bjfcnd bzr+ssh://bazaar.launchpad.net/~arsenal-devel/arsenal/python-launchpadlib-toolkit/23:46
bjfcnd https://launchpad.net/~arsenal-devel/+archive/ppa23:50

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