=== smb` is now known as smb | ||
=== gavin__ is now known as gavinguo | ||
=== fmasi_afk is now known as fmasi | ||
jjohansen | brendand: are you done with https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1205381 | 09:26 |
---|---|---|
ubot2` | Launchpad bug 1205381 in Kernel SRU Workflow security-signoff "linux: 3.2.0-52.78 -proposed tracker" [Medium,In progress] | 09:26 |
brendand | jjohansen, yeah i just reset it to fix released. you can go ahead | 09:27 |
jjohansen | brendand: alright, thanks | 09:27 |
=== psivaa_ is now known as psivaa | ||
=== psivaa is now known as psivaa-lunch | ||
rtg | apw, kernel.ubuntu.com/~rtg/3.11.0-3.6 for -rc6 test binaries | 13:03 |
=== psivaa-lunch is now known as psivaa | ||
smb | rtg, There might be no him this week | 13:24 |
rtg | ogasawara, http://kernel.ubuntu.com/~rtg/3.11.0-3.6 to try out on your misc HW. I'm gonna upload this since it has passed smoke testing on 3 relatively disparate platforms. | 14:14 |
ogasawara | rtg: ack | 14:15 |
=== kamal__ is now known as kamal | ||
ogasawara | rtg: boot tested on 3 different intel boxes here, all running fine here on 3.11.0-3 | 14:32 |
rtg | ogasawara, cool | 14:33 |
=== rtg is now known as rtg-afk | ||
=== kees_ is now known as kees | ||
=== JayF_ is now known as JayF | ||
infinity | brendand: Around? | 16:42 |
brendand | infinity, yep. hi | 16:42 |
infinity | brendand: What's the ETA on cert testing for raring finishing up? | 16:42 |
brendand | infinity, tomorrow morning. i was hoping to get results today but our test lab was a bit undermanned this morning and a snag was hit | 16:43 |
brendand | infinity, if you really want to i can push it now, but spoke with bjf on friday and the consensus was that it's better to get it fully tested since it will be the kernel for 12.04.3 | 16:44 |
infinity | brendand: Ahh, hrm. Has it passed on any reasonable cross-section of machines yet? Yeah, it'll be the .3 kernel, but that also puts in a bit of a scheduling mess. ;) | 16:44 |
infinity | (Unless we slip the .3 release, which we're considering, if Cert won't have the time/manpower to catch up) | 16:45 |
brendand | infinity, catch up with what? | 16:45 |
brendand | infinity, it's passed on a fair number of systems already | 16:45 |
infinity | brendand: Catch up with whatever magic you guys do for ISO cert for point releases. I'm a bit hazy on that, personally. :) | 16:46 |
=== rtg-afk is now known as rtg | ||
=== slangase` is now known as slangasek | ||
* rtg -> lunch | 18:01 | |
=== masACC is now known as maswan | ||
=== fmasi is now known as fmasi_afk | ||
lamont | I really am hating the lockups I see with my NVIDIA Corporation GT218 [GeForce 8400 GS Rev. 3] (rev a2) | 18:38 |
infinity | lamont: nvidia or nouveau, which kernel, etc? | 18:43 |
lamont | infinity: since about quantal | 18:44 |
lamont | beyond that, give me commands | 18:44 |
lamont | 3.8.0-27-generic is the kernel version that just locked up on me | 18:44 |
infinity | lamont: lsmod might be helpful if you honestly don't know which video driver you're using. :) | 18:45 |
lamont | nouveau | 18:45 |
lamont | is loaded and depending on things, anyway | 18:45 |
lamont | | grep nvid has 0 lines | 18:45 |
infinity | lamont: But if it's nouveau's fault, you probably want to whine at tjaalton, and possibly try the non-free driver to see if it suffers similar issues. | 18:45 |
infinity | (If both drivers hate you, it could be hardware, overheating, etc) | 18:46 |
lamont | heh. ok | 18:46 |
lamont | ISTR switching didn't help much. OTOH, it's pretty well ventilated, etc. | 18:46 |
lamont | but ok | 18:46 |
infinity | It's pretty rare for both drivers to fail in the same or similar ways, unless your card is bust. | 18:46 |
infinity | And heat's the usual cause of video lockups. | 18:47 |
infinity | Unless you have an i915, then the usual cause is lolintel. | 18:47 |
lamont | infinity: the driver thing was more not really remembering if I'd ever cared enough to switch to non-free | 18:48 |
lamont | but I'll do that, and see what it does, then assume heatdeath if that's relevant. | 18:48 |
tjaalton | lamont: you might have luck triaging that one with mlankhorst | 18:48 |
lamont | fwiw, it tends to happen when one is stupid enough to scroll with the thumbwheel or otherwise switch rapidly between screens/windows | 18:49 |
tjaalton | he's working on the driver upstream | 18:49 |
lamont | there was a time when I didn't call that behavior 'stupid' | 18:49 |
infinity | tjaalton: mlankhorst was going to be my other suggestion, but he's not in here and fails to tab complete. ;) | 18:49 |
tjaalton | infinity: yeah, noticed the same :) | 18:49 |
tjaalton | lamont: file a bug (ubuntu-bug xorg) and then poke him on #ubuntu-x for instance | 18:50 |
infinity | lamont: Ahh, hrm. That's a curious behaviour pattern. It's a hard video lockup when you do that? | 18:50 |
tjaalton | and if it's easy to reproduce, maybe try the saucy kernel, or fresh mainline | 18:50 |
lamont | infinity: SYSTEM lockup, frequently | 18:50 |
infinity | lamont: I'd give 20-to-1 odds the non-free driver won't have that same problem, then. | 18:50 |
lamont | but yeah, video locks hard, then goes all whackamole | 18:51 |
lamont | getting into the box to get info has proven problematic | 18:51 |
infinity | lamont: Well, it could still potentially be bad hardware if the actual precipitating event is just "flipping a ton of buffers" and you have bad RAM. | 18:51 |
lamont | infinity: two identical machines (ordered/shipped in the same order) both exhibit the problem. | 18:51 |
infinity | But it smells more like a driver bug, from your description. | 18:52 |
lamont | needless to say, my wife is not happy either | 18:52 |
infinity | Ahh, and that nails it even more. | 18:52 |
infinity | Definitely try the non-free driver, at least on her kit. :P | 18:52 |
tjaalton | yeah | 18:52 |
infinity | Wife happiness is important. | 18:52 |
lamont | heh. shall do | 18:52 |
lamont | it might actually have started in precise... can't recall for sure | 18:52 |
lamont | I mean, it's _possible_ that there was a defective lot of graphics cards, but.... | 18:53 |
infinity | Possible, but unlikely. Especially since that sort of behaviour would be "a bad batch of video RAM that happened to land on my two video cards", which is slimming the odds a bit. | 18:53 |
infinity | Or you have two fans that have both stopped spinning, and you haven't noticed. :P | 18:54 |
arges | bjf[afk]: hi i noticed that bug 1201869 was marked 'fix released', but that particular bug was reverted from the kernel. is this a mistake, or do i just need to create a new bug when I submit a new SRU | 20:46 |
ubot2` | Launchpad bug 1201869 in linux (Ubuntu Raring) "poor networking throughput across an OpenStack Neutron router on 3.5/3.8 kernels" [Medium,Fix committed] https://launchpad.net/bugs/1201869 | 20:46 |
infinity | arges: That was just the LP janitor marking it Fix Released because it was mentioned in the changelog, just set it back to In Progress. | 20:49 |
* infinity does that. | 20:49 | |
infinity | arges: Same thing will happen for raring when it's released, same remedy applies. | 20:49 |
arges | infinity: ok i'll set it when i see it. thanks | 20:50 |
* rtg -> EOD | 21:12 | |
=== ShapeShi- is now known as ShapeShifter499 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!