dholbachdo you know of any reports of e1000e not working in raring?07:32
=== smb` is now known as smb
smbdholbach, not me, maybe some of the others07:54
dholbachsmb, a friend in the office just told me about it and I just yesterday noticed the same at home07:55
smbdholbach, I should have some boxes myself. not sure I noticed, but maybe I have not upgraded latest enough07:56
dholbachfor me it's on a x220, the friend of mine downgraded to 12.04 already :-/07:56
* cking has a x220, will sanity check this07:57
smbdholbach, did you have that with all versions of raring and quantal?07:57
smb12.04 would be precise...07:57
dholbachcking, not sure if you saw the original question - it's about ethernet not working07:57
dholbachsmb, no - I haven't used ethernet in a long while - just noticed it yesterday07:58
apwcking, yours is a ... oh you said that :)07:59
apwdiwic, about?  this = false thing ...08:01
diwicapw, any news?08:01
smbdholbach, one box is using e1000e in raring and still working but the kernel is back at 3.8.0-13. upgrading now08:01
apwdiwic, so i think this is a race, a race caused by the now double clear of that variable08:01
apwdiwic, i note that later you have produced a patch set adding locking in this area08:02
apwso clearly there is some race potential here08:02
apwbut the main point is actuall that variable is = false and made so by the memset just above08:02
* cking just upgrading his x220i - confirming it has e1000e and currently working08:02
apwand i think the double adds a window where it gets cleared twice08:02
diwicapw, what I don't get is how any kind of race related to eld_valid could affect analog (non-HDMI) playback08:03
apwall true, ... its hard to fathom, but the patch as is seems redundant08:04
apwdiwic, the only other reasonable inference (for me) is that the code layout changes it causes affects one of the other routines in the same file, and that is scarey08:06
diwicapw, that memset looks weird. 08:06
apwcking and i looked it over yesterday, it seemed to do something sane ish08:06
apwie. it clears out the first 3/4 of the structure, but not the buffers at the end08:07
diwicapw, ah, now I understand it08:07
apwa little odd i concur08:07
ckingthe memset() does the job08:07
Kanohi, does anybody update the unstable-3.9 branch soon?08:08
apwKano, it is likely to be a little delayed, we are in freezes right now and have other priorities08:09
Kanobasically it would be interesting to combine it with the uvd patches08:10
diwicapw, or the additional = false causes a gcc bug because it tries to optimise it away having seen the memset, but fails in some weird way?08:10
apwdiwic, we read the asm for both forms and they seemed right to us08:10
diwicapw, oh, you went that deep08:11
* diwic bows down in admiration08:11
apwdiwic, yeah we found pretty  much any addition to the routine also  avoided whatever the issue08:11
apwdiwic, there is clearly something nasty in there, whether it is related to races your new locking (in later kernels) avoid or not ... how to tell08:12
ckingit certainly seemed racy08:13
diwicapw, is it easy for you to file up a broken and a working kernel and attach alsa-info for both to compare for differences?08:13
diwicapw, for best reference alsa-info should be taken while playback is in progress08:14
apwyet, the code in question on the machine in question should be static as there is nothing in the port, ...08:14
diwicapw, did I miss anything?08:20
diwicapw, latest is <apw> yet, the code in question on the machine in question should be static as there is nothing in the port, ...08:20
apwdiwic, noope you miseed nothing08:20
apwdiwic, i'll try and get what you wanted.  it's my main machine08:21
smbcking, dholbach, server now on 3.8.0-17 and e1000e still working (82574L NIC)08:26
dholbachwhat kind of info would you need in a bug report?08:26
dholbachI'll double check in a bit08:26
ckinghrm, my X220i with e1000e and latest kernel works OK08:27
smbdholbach, whatever ubuntu-bug linux collects. Though you probably need to work via apport-cli as you have no network at that time08:27
dholbachall right, will do - thanks08:28
infinityapw: I assume you noticed that lowlatency exploded in make oldconfig?08:35
apwhow is that even possible08:36
infinityCause there was something new? :P08:36
apwi don't doubt that it did so, but ... the configs are made from the main ones on rebase, and those would have to explode too... in theory08:36
infinityAnd you didn't sync configs when you rebased?  I'm guessing?08:36
apwthat happens on rebase as part of the rebase08:37
apwbut i will go and poke it, as this 'cannot' happen08:37
Laneyhello kernel friends. Is there some badness with the -17 kernel in raring? I'm seeing nvidia-310 now not compiling: http://paste.ubuntu.com/5691789/ and http://paste.ubuntu.com/5691769/08:57
apwLaney, i don't think we expect it to be significantly different from the previous version, which worked i assume09:16
Laneyhmm, it's checking for SUBLEVEL -le 5 and that's now 609:21
apwLaney, so an issue with nvidia then?09:22
Laneywell, assuming that SUBLEVEL increase is right then I guess so09:22
Laneytseliot: ^ looks like bug #1166639; do you know if n-g-d-310 needs an update?09:26
ubot2Launchpad bug 1166639 in nvidia-graphics-drivers-310 (Ubuntu) "nvidia-310 310.32-0ubuntu2: nvidia-310 kernel module failed to build" [Undecided,New] https://launchpad.net/bugs/116663909:26
tseliotLaney: I guess the correct headers were simply not installed: *** Unable to determine the target kernel version. ***09:27
tseliotLaney: or the DKMS log is bogus09:27
Laneytseliot: They are - I got a set -x log of conftest.sh and it's failing when (presumably) checking the kernel version at line 170609:28
tseliotLaney: I'll have a look at it here. Thanks09:30
LaneySeems like that check should be reworked a bit09:31
Laneythanks tseliot 09:31
ppisatimumble down?09:38
ckingppisati, seems to be borked09:48
ppisaticking: i'm back in09:48
ppisaticking: yep09:48
* ppisati -> out for lunch10:26
tseliotLaney, apw, ogasawara: do you know why SUBLEVEL was changed to 6 in the Makefile in 3.8.0-17.27? It was previously set to 5. This makes nvidia's build fail13:54
tseliotand by previously I mean in ABI 1613:55
apwtseliot, it is the third number of the upstream version, it changes when that changes13:56
apwVERSION = 313:56
apwPATCHLEVEL = 813:56
apwSUBLEVEL = 613:56
ogasawaratseliot: what apw said, we rebased to upstream stable v3.8.613:56
apwso that says this is based on 3.8.6 stable update from upstream13:56
apwit would be a completely normal action when we are in rebase territory, ie before release13:57
apwand actaully any time we apply stable we'd do it, so expect it :)13:57
tseliotapw: does this check make any sense to you? http://pastebin.ubuntu.com/5692393/13:58
tseliotI don't see why sublevel should be less than or equal to 513:58
apwso i think that is probabally designed for the 2.x days, it feels like it is trying to check for versions greater than 2.6.5 when perhaps the makefile name changed? something like that, it also just lookes borkes14:00
tseliothmm... removing the "-a $SUBLEVEL -le 5" part gets it to work... I'll send NVIDIA a patch14:01
Laneyit is borked14:01
Laneyprobably ought to check the major version too?14:01
apwtseliot, yeah i think ... it assumes the first digit is always 2, then it says for 2.6.x where .x < 5 then we need to change makefile to the old one14:01
apwbut ... as it doesn't check the 2, that means it now hits for 3.6 and above14:02
apw(i think)14:02
tseliotthe comments in the code look a bit dated: http://pastebin.ubuntu.com/5692404/14:03
apwtseliot, so that matches what I guessed i think, i suspect just zapping the whole lot is reasonable now, we don't have anything that old any more14:09
tseliotapw: are you suggesting that I skip the entire check or just the -le 5 thing (which seems less risky)?14:11
apwif the comments concur that they intended to select one bit of code for 2.6.5 and older and one for 2.6.6 and later, then we can rip out the decision en toto and use the code for 2.6.6 and above14:12
tseliotapw: here's the complete picture (with some code ripped out), just to give you an idea: http://pastebin.ubuntu.com/5692420/ (and we're hitting the "else"14:16
ppisatilp 116407414:21
ubot2Launchpad bug 1164074 in linux (Ubuntu Raring) "[Highbank] Quantal to Raring upgrade issues" [High,Confirmed] https://launchpad.net/bugs/116407414:21
ppisatirtg_: ^14:21
ppisatirtg_: there's a patch attached, can you give it a look? it's for raring-meta14:22
rtg_ppisati, will do14:22
apwrtg_, are you applying patches ?14:22
rtg_apw, haven't started yet, but did push some updates this AM (to existing patches)14:23
apwrtg_, i was going to apply jj's patch but don't want to step on our bags of man sausage14:23
rtg_apw, go ahead, I'll look at ppisati's upgrade bug14:23
apwrtg_, ack14:23
apwrtg_, forget that ... ogasawara is on the case anyhow14:25
ogasawaraapw: ah yep, applied both jj's and piti's patches to Raring14:26
* ppisati goes for an apple...14:26
ogasawaraapw: I didn't touch Lucid, Precise, or Quantal, was gonna leave that to bjf and his minions14:26
apwogasawara, ta14:30
bjfGen0me, we are not a very touchy-feely channel, if you have a question, ask it14:32
apwGen0me, yep we are pretty passive14:39
rtg_some are more aggressively passive then others14:40
Nafallohey... what happened to chumby kernels? ;-)14:40
ogra_Nafallo, we dropped support for armel quite a while ago ...14:40
Nafalloseems these things are dead-weight unless someone revive them :-)14:40
ogra_mine still runs fine 14:40
ogra_showing the LCARS clock in my living room 14:41
Nafallooh? I thought the server it syncs with died?14:41
Nafallocompany went bust or whatever14:41
ogra_there is a hacked image you can install that doesnt require the network14:41
Nafallothat's the answer I was looking for I guess ;-)14:41
* ogra_ forgot how it was named, i did that right when they shot down ... was a while ago14:41
Nafallozurk perhaps?14:43
ogra_Nafallo, http://sourceforge.net/projects/chumby/ and http://sourceforge.net/projects/zurk/14:43
NafalloI've already binned that device :-P14:43
Nafallohow pointless14:44
ogra_still does its job for me (being a nice start trek clock) 14:44
Nafallothought it was still hiding in a corner somewhere, but I didn't realise it would be at a tip ;-)14:44
ogra_you could have proted ubuntu touch to it :P14:45
* ogasawara back in 2014:45
Nafalloyeah... :-P14:45
jsalisbury** Ubuntu Kernel Team Meeting - Today @ 17:00 UTC - #ubuntu-meeting14:58
rtg_ppisati, https://bugs.launchpad.net/ubuntu/raring/+source/linux-meta/+bug/1164074/comments/6 , uploaded linux-meta15:06
ubot2Launchpad bug 1164074 in linux-meta (Ubuntu Raring) "[Highbank] Quantal to Raring upgrade issues" [High,Fix committed]15:06
ppisatirtg_: nice, thanks15:07
Gen0mehelp : Run `bundle install` to install missing gems.15:42
Gen0meCould not find pg-0.15.0 in any of the sources15:42
Gen0mebundel install -> Bundler::GemfileNotFound15:42
rtg_Gen0me, try #ubuntu-devel15:44
bjfjsalisbury, i think bug 1140716 can be removed from the hotlist. henrix will be submitting patches to the mailing list shortly15:45
ubot2Launchpad bug 1140716 in linux (Ubuntu Quantal) "[regression] 3.5.0-26-generic and 3.2.0-39-generic GPU hangs on Sandybridge" [Critical,Confirmed] https://launchpad.net/bugs/114071615:45
jsalisburybjf, will do, thanks15:48
Gen0mertg_, ubuntu-devel -> not found15:48
bjfGen0me, ubuntu-devel is an irc channel on this same server, try  '/join ubuntu-devel'15:50
Gen0mebjf, ;) thanks15:50
ppisatiapw: assuming 'ubuntu-raring' is an up to date ubuntu-raring got tree15:54
apwppisati, ?15:55
ppisatiapw: is './kteam-tools/devel/devel-config-summary --html ubuntu-raring foobar' the correct rune to invoke your review script?15:56
ppisatiapw: sorry i'm juggling between different things :P15:56
apwppisati, yep that would do it15:56
apwppisati, assuming the branch you want to check is checked out15:56
ppisatiapw: http://paste.ubuntu.com/5692711/15:59
apwppisati, ahh i fixed that somewhere one sec15:59
apwppisati, ok pushed, try that16:02
rtg_henrix, how about a pull request for the i915 regression patch sets ?16:21
henrixrtg_: ack, will do that16:21
bjfrtg_, you can still ack/nak and let sconklin deal with them since he's trying to turn the crank16:28
rtg_bjf, I'm busy reading them16:28
bjfrtg_, i wasn't trying to rush you16:29
rtg_bjf, I just prefer pull requests when there are more then a couple of patches 'cause using thunderbird is a PITA16:30
bjfrtg_, ack16:31
rtg_sconklin, i915 patch sets applied. crank away.16:39
sconklinrtg_: thanks16:39
rtg_now, back to figuring out why mumble is borked16:40
* henrix is also a little bit nervous about the i915 patchset...16:45
rtg_henrix, has it been tested to show that the regression is at least mitigated ?16:48
henrixrtg_: no, not really. Chris commented on the bug 2 or 3 times identifying these patches as the solution16:50
rtg_yeah, that bug report is getting to be kind of a mess16:50
henrixrtg_: yep, there are definitely different bugs being reported there and its hard to follow all the discussions/reports16:52
jsalisbury## Meeting starting now17:00
=== jsalisbury changed the topic of #ubuntu-kernel to: Home: https://wiki.ubuntu.com/Kernel/ || Ubuntu Kernel Team Meeting - Tues April 16th, 2013 - 17:00 UTC || If you have a question just ask, and do wait around for an answer!
* henrix -> out for a bit17:12
rtg_ogasawara, re: Minutes from the Ubuntu Kernel Team meeting, 2013-04-09. Where is that work item 'rtg       || hardware-r-delta-review' actually defined ?17:17
* rtg_ -> lunch17:22
* smb mischief accomplished -> EOD17:42
* cking EOT (rewind)17:54
* rtg_ -> EOD19:58
=== Traxer|on is now known as Traxer
=== elmo__ is now known as elmo
charlieI just had another kernel panic from here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1165985 but using the upstream kernel instead. I've still got it displayed on the screen, and was wondering what would be the most useful information to transcribe from it before I reboot the machine.23:30
ubot2Launchpad bug 1165985 in linux (Ubuntu) "13.04 - kernel panic - unable to handle kernel paging request ffffffec -- Dell Inspiron 9300" [High,Confirmed]23:30

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