=== kentb_ is now known as kentb-out
=== ScottSanbar is now known as SanbarComputing
=== SanbarComputing is now known as ScottSanbar
=== ScottSanbar is now known as SanbarComputing
=== kengyu_ is now known as kengyu
=== smb` is now known as smb
smbMorning .+07:16
* apw yawns07:34
=== artnay_ is now known as artnay
=== yofel_ is now known as yofel
Kanohi apw , did you notice that your build server for mainline runs out of space?11:14
* ppisati -> lunch11:30
_rubenbah .. still can't seem to find out how to match 'ata4' to 'sdX' .. and seem to be not alone in that, but no solutions found thusfar :/13:47
apw_ruben, not sure i understand your problem13:48
_ruben[589302.281732] ata4: soft resetting link13:49
_rubenwant to know which disk to replace13:49
apwdoesn't udev have a like by-path name for each disk as well13:49
jk-apw: yes, but it doesn't show ataX13:50
jk-ls -l /sys/class/ata_device13:50
_rubenno such file or directory13:50
* apw wonders if he wants to know how old the release you are running is13:50
_rubenlucid server 32bits13:51
=== kentb-out is now known as kentb
mdeslaurherton: you reverted the commit that caused my dpms fuzzy screen? I thought it was an important part of hardware enablement?14:13
hertonmdeslaur: yes, hardware enablement team is aware of the revert, steve talked with them14:13
hertonit was agreed best action was to revert it for now14:14
mdeslaurherton: ah, ok, thanks for the explanation...I was just curious. I have the issue with the current oneiric kernel, fyi.14:14
ogasawaratgardner: you haven't already started on pulling in the 3.0.5 and 3.0.6 updates have you?  I just want to make sure I'm not duplicating work.14:15
tgardnerogasawara, yep, was just working on the compile14:16
ogasawaratgardner: sweet14:16
tgardnerthen I'm gonna look 'em all over pretty close14:16
bjf## Ubuntu Kernel Team Meeting - Today @ 17:00 UTC - #ubuntu-meeting14:27
bjf##      agenda: https://wiki.ubuntu.com/KernelTeam/Meeting14:27
* ogasawara back in 2014:29
apwsmb, might you be able to test a hardy cve for me, http://people.canonical.com/~apw/CVE-2011-2495-hardy/, test whether you can read /proc/$$/io as a user and root, both before and after the kerenl14:30
ubot2apw: ** RESERVED ** This candidate has been reserved by an organization or individual that will use it when announcing a new security problem.  When the candidate has been publicized, the details for this candidate will be provided. (http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-2495)14:30
apw(or more likely mitre is majorly out of date)14:30
smbapw, I can, but might be rather later today or tomorrow14:31
apwsmb, ahh yes poor timing on my part14:32
tgardnerogasawara, 'git://kernel.ubuntu.com/rtg/ubuntu-oneiric v3.0.6' if you want to do some smoke testing.15:07
ogasawaratgardner: cool, thanks.15:08
=== BenC__ is now known as BenC
bjf## Kernel team meeting in one hour16:00
sconklintgardner, hey I'm looking at the tool failure you pasted to mumble. Is the tree you ran it in pushed anywhere? I need to reproduce it17:18
tgardnersconklin, git://kernel.ubuntu.com/rtg/ubuntu-oneiric v3.0.617:19
tgardnersconklin, git://kernel.ubuntu.com/rtg/ubuntu-oneiric.git v3.0.617:20
sconklintgardner, thanks. It's choking on something it parsed from the Makefile. I'll reproduce it17:21
apwsconklin, hey ... looks liek the issue is that oneiric doesn't have anything on the EXTRAVERSION and your split there assume there will be ' = ' which isn't present17:25
sconklinprobably so. I'm cloning but it's only at 7%17:26
apwVERSION = 317:26
apwPATCHLEVEL = 017:26
apwSUBLEVEL = 417:26
sconklinthat's it then17:27
apwif am reading this right we don't use the value at all, so the split could be elided17:27
sconklinit assumes that is the string 'EXTRAVERSION" is there, then something follows it17:27
apwwell it assume its is EXTRAVERSION<space>=<space>17:28
apwas the next line has a strip, just splitting on '=' would like do the job17:28
sconklinapw, ack, and I think that's true for all those values which are parsed. And we should never have any other '=' characters in there17:31
apwsconklin, pretty sure that split takes a max splits, so you could add a 1 to make sure it only pops the first one17:31
ckinguntil the next time it breaks17:32
apw>>> print a.split('=', 1)17:32
sconklinapw, right, except that I would argue that if you have anything else on the line something should explode, as it's an error17:32
apw['this that ', ' you me = other']17:32
sconklingrrr input management17:36
apwfocus management with unity is perfect17:36
sconklinThis is a natty box17:45
=== bjf changed the topic of #ubuntu-kernel to: Home: https://wiki.ubuntu.com/Kernel/ || Oneiric Kernel Version: 3.0.0 || Ubuntu Kernel Team Meeting - October - 11 - 17:00 UTC || If you have a question just ask, and do wait around for an answer!
sconklintgardner, you spec 3.0.0 on the command line, but the makefile has 3.0.617:53
sconklinThat's not the cause of the original failure, just the 'next one' :-)17:53
tgardnersconklin, the _package_ version is 3.0.017:53
sconklinok, checking17:54
sconklintgardner, why are the package and kernel versions not the same?17:56
tgardnersconklin, well, they are. the package version is 3.0.0 as is the kernel.17:56
sconklintgardner, from the Makefile:17:57
sconklinVERSION = 317:57
sconklinPATCHLEVEL = 017:57
sconklinSUBLEVEL = 617:57
sconklinEXTRAVERSION =17:57
sconklinfrom your 3.0.6 branch17:58
tgardnersconklin, hmm, I guess thats some fallout from the version change.17:58
tgardnerEXTRAVERSION appears to be superfluous17:58
bjftgardner, isn't that because we are versioning differently than upstream ?17:58
bjftgardner, shouldn't the sublevel be 0 and the extraversion be 6 ?17:59
tgardnerbjf, thats the way it used to work.17:59
tgardnerso we're gonna have to accommodate that change17:59
bjftgardner, not sure what that means. who needs to accomodate, which change, do we need to make the Makefile reflect our versioning ?18:00
tgardnerbjf, our scripts are gonna have to recognize that if the version is 3.0 or higher, then EXTRAVERSION is empty18:01
sconklinnot to overstate it, but this breaks everything18:01
tgardnersconklin, well, it certainly adds some complications18:02
sconklinwell, ok. and until the complications are embodied in code, it breaks everything.18:02
sconklineverything == stable tools18:03
ckingor unstable tools perhaps? ;-)18:05
tgardnersconklin, herton: perhaps this is an opportunity to consolidate version checking into one module so we only have to fix this once.18:06
sconklinmore accurately, this challenges one of our fundamental assumptions. If it turns out we were wrong, we'll deal with it. But I don't think we're wrong.18:06
tgardnersconklin, you fundamentally assumed the kernel version would match the package name ?18:07
sconklinYes, and that (at least post-release) there is only one kernel version per series18:08
tgardnersconklin, don't we already break that assumption with mvl-dove ?18:09
sconklini.e. after release there's a 1:1 associative mapping between kernel version and series18:09
sconklinthe association is encoded by package name, so we can associate different kernels for ARM, etc - but it can't change18:09
bjftgardner, when you built and tested this kernel what did a uname -a give you 18:10
tgardnersconklin, I guess we're gonna have to figure out how to accommodate both 2 and 3 digit version numbers.18:11
tgardnerbjf, 3.0.0-12 (I think)18:11
tgardnerbjf, 3.0.0-13.2018:12
sconklinand why are we changing the way we use sublevel and extraversion?18:12
tgardnersconklin, whats the _we_ shit? Linus made that change.18:12
bjfsconklin, tgardner so if uname can report 3.0.0 maybe we can get the sublevel and extraversion from the same place that it references, that has to come from kernel sources somewhere18:13
tgardnerbjf, it comes from the changelog18:14
bjfsconklin, though i wrote it, i don't remember why i'm looking at the makefile, can we change to use the changelog version ?18:14
tgardnerbjf, actuall, it is extracted from the changelog and built into the kernel at prep time by setting CONFIG_VERSION_SIGNATURE18:15
tgardnerbjf, sconklin - I think you can depend on the changelog _always_ having a 3 digit version because we set the policy for that.18:16
sconklinbjf, yeah. I have no idea why it parses the Makefile, either18:16
bjfsconklin, i do agree that as part of this fix, "we" should look at where we parse the kernel version and do some refactoring if possible18:16
sconklintgardner, ack, we should probably abandon the Makefile and only parse the changelog18:17
tgardneris there a python equivalent of dpkg-parsechangelog ?18:17
bjfsconklin, i'm sure i did that for "a really good reason"(tm) but i can't remember what that might be now18:17
sconklinand also agree with bjf18:17
tgardnerremember that the kernel version isn't _really_ related to the package name, its only convention.18:17
* tgardner needs brain food18:18
* tgardner -> lunch18:18
sconklintgardner, noted, although that assumption really is deeply embedded in almost all the tools. Although, the reality is that we can change versions in the tools, you just won't be able to go back and use them for the older version (I think)18:19
tgardnersconklin, the assumption that should be deeply embedded in tools is that the version is extracted from the changelog. that is, after all, the debian way.18:50
sconklintgardner, ack, that's what I'm looking at now.18:58
bjftgardner, and everyone agrees that "uname -a" returns the package version, right? not the kernel version.19:28
tgardnerbjf, correct19:28
tgardnerbjf, Linux sb 3.0.0-13-server #20 SMP Tue Oct 4 15:28:19 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux19:29
* jjohansen -> lunch19:30
sconklintgardner, the way I read the uname man page, it returns "kernel release"19:33
sconklinand version and other things19:33
tgardnersconklin, true, but remember that the value returned by 'uname -a' is set in the kernel at build time.19:34
tgardnerits not extarcted from the Makefile, but rather from the changelog19:34
sconklinwell yeah, there's no other way to do it19:34
sconklinso debian (and we) have determined that "kernel release" means something other than what it means to upstream?19:35
tgardnersconklin, in fact the version returned by 'uname -a' comes from this line in debian/rules.d/2-binary-arch.mk: cat $^ | sed -e 's/.*CONFIG_VERSION_SIGNATURE.*/CONFIG_VERSION_SIGNATURE="Ubuntu $(release)-$(revision)-$* $(raw_kernelversion)"/' > $(builddir)/build-$*/.config19:37
sconklinand it returns 3.0.0(something), even though the makefile from upstream contains the version 3.0.619:40
ohsixwasn't the .0 thing a stopgap until things could catch up in the kernel build stuff?19:41
tgardnersconklin, but thats my point. the content of the makefile isn't relevant.19:41
tgardnerits convention, albeit one that some tools depend on19:41
sconklin;et 19:42
sconklinignoring the tools issue for a moment . . .19:42
sconklinIt's significant to me to know which version I am running. If uname and the package name tell me I am running 3.0.0, and I'm in fact running 3.0.6, then I have a problem with that19:43
sconklingranted at this point it's a personal problem . . . but I think it creates potential for widespread confusion19:44
tgardnersconklin, well, you're never running the version in the Makefile because we add our own patches, and sometimes don't include all of the patches in a stable update.19:44
sconklinright. But generally I want to know whether some improvement or fix from upstream is included in what I have, and now I've lost that19:45
tgardnerthats why we list the actual patches included in a stable update19:45
sconklinand you know how many of our consumers actually go read the changelog, right?19:46
tgardnersconklin, some of them do, but I agree it can be misleading.19:46
sconklinand how many "when are you going to ship 3.0.6?" questions will we get?19:47
tgardneryou say that like this is a new problem.19:48
Kanoapw: it seems you have to update your scripts for mainline stable builds to use http://git.kernel.org/?p=linux/kernel/git/stable/linux-stable.git;a=shortlog;h=refs/tags/v3.0.620:51
Kanoas there is no 3.0.5/3.0.6 build20:51
Kanowell 3.0.5 wil fail anyway20:51
Kanobut i would like to test 3.0.6 mainline21:13
Kanodaily seems to work so far21:14
=== jjohansen is now known as jj-afk
jj-afkback on later23:03

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