=== shuduo_afk is now known as shuduo | ||
=== shuduo is now known as shuduo_afk | ||
=== shuduo_afk is now known as shuduo | ||
=== gfrog_afk is now known as gfrog | ||
=== gfrog is now known as gfrog_meeting | ||
=== gfrog_meeting is now known as gfrog | ||
* apw yawns | 08:47 | |
=== shuduo is now known as shuduo_afk | ||
* cking reboots | 10:29 | |
caribou | apw: morning, remember the small patch you sent my way a while ago (bug 1233175) | 10:44 |
---|---|---|
ubot2` | Launchpad bug 1233175 in linux (Ubuntu Precise) "Kernel panic : mempolicy potential use-after-free on server running mongodb" [High,In progress] https://launchpad.net/bugs/1233175 | 10:44 |
apw | caribou, some yep | 10:56 |
apw | caribou, not that i can find it right now, you got a copy? | 10:59 |
caribou | apw: sure, let me forward your email | 11:00 |
apw | it must be here somewhere, but if you have that is easier :) | 11:00 |
=== smoser` is now known as smoser | ||
apw | cking, THP did you notice any increase in resident set on your test rig when running? just noted the warning in the config option | 15:20 |
cking | apw, good question, I need to check for that, I completely overlooked that fact | 15:21 |
jdstrand | ogasawara: hey-- check out this paste: http://paste.ubuntu.com/6546723/. The machine is using wlan0, not eth0 but after a few minutes eth0 shows this weird output even though eth0 isn't being used. This is happening on a Lenovo IdeaPad U460 on precise | 17:18 |
jdstrand | ogasawara: I think this may have started with 56 (I"ve seen it on -56 and -57-- cursory testing of -55 didn't show it) | 17:19 |
jdstrand | ogasawara: have you seen any bug reports with weird networking on recent precise SRU kernels? | 17:19 |
ogasawara | jdstrand: hrm, I haven't heard of anything. jsalisbury, bjf: ^^ sounds familiar at alll? | 17:20 |
ogasawara | jdstrand: sounds fairly reproducible though from your description. would you have time to run through a few test kernels to bisect it? | 17:21 |
jdstrand | at some point-- it isn't my system (it is my wife's and she is using it) | 17:22 |
bjf | ogasawara, jdstrand news to me | 17:22 |
ogasawara | jdstrand: can you do an 'ubuntu-bug linux' from it for me | 17:23 |
ogasawara | jdstrand: we can check if we have hw in our possession to reproduce | 17:24 |
jdstrand | ogasawara: otoh, is there a trick with doing that from cli only? | 17:24 |
ogasawara | jdstrand: hrm, not sure there | 17:24 |
jdstrand | ok, let me see what I can do | 17:24 |
* jdstrand doesn't have lp credentials on that machine | 17:24 | |
* ogasawara wonders if we have the same kit in cert to test with | 17:25 | |
jdstrand | ok, I just ssh in and do it and it walks me through | 17:26 |
rtg | it might just be a stable update on that driver in -56. | 17:27 |
jdstrand | that is what I was wondering | 17:28 |
jdstrand | erf, lp timeout error | 17:30 |
jdstrand | ogasawara: bug #1259255 | 17:31 |
ubot2` | Launchpad bug 1259255 in linux (Ubuntu) "incorrect ifconfig output for unused wired ethernet" [Undecided,New] https://launchpad.net/bugs/1259255 | 17:31 |
ogasawara | jdstrand: thanks, we'll see if we can chase this down | 17:32 |
jdstrand | ogasawara: so, I've rebooted her into -55. I used the same networking tests that I did on -56 and -57 and ifconfig still looks ok. I'll keep an eye on it | 17:37 |
rtg | jdstrand, no changes to atl1c ethernet driver since Ubuntu-3.2.0-55.85. Does it happen right away ? | 17:38 |
jdstrand | no-- it seems to happen after I connect to a jabber server. I did that on -55 and it is still ok | 17:38 |
jdstrand | rtg: is atl1c the wired driver? | 17:39 |
jdstrand | rtg: cause note-- the machine doesn't have a cable connected to it on eth0. it is only using wireless on wlan0 | 17:39 |
rtg | jdstrand, but you're connecting via wifi, right ? According to your dmesg it is an atl1c ethernet device. | 17:39 |
rtg | [ 2.140905] atl1c 0000:04:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18 | 17:39 |
rtg | [ 2.140918] atl1c 0000:04:00.0: setting latency timer to 64 | 17:39 |
jdstrand | after using the network via wlan0, after a while eth0's ifconfig is weird | 17:39 |
rtg | ok | 17:40 |
jdstrand | yes, connecting via wifi | 17:40 |
rtg | so, its likely something external that changed interrupt routing, or stats updates in the net sub-system, etc. I imagine jsalisbury can help you with a bisect. | 17:41 |
jdstrand | she was complaing about networking issues in general on -57-- but she reboots so infrequently it is possible whe was running -55 until today/this weekend | 17:41 |
* jdstrand nods | 17:41 | |
jdstrand | I did see a lot of 'net' changes | 17:41 |
jdstrand | in the changelog | 17:42 |
rtg | yep, I saw those as well | 17:42 |
henrix | jdstrand: its weird that you have "[ 5322.316796] device eth0 entered promiscuous mode" | 17:42 |
henrix | jdstrand: was this some test you exec'ed? | 17:42 |
jdstrand | no. I used tcpdump on wlan0 | 17:42 |
* jdstrand just checked history | 17:42 | |
henrix | ah, ok. that could explain it | 17:43 |
* henrix notes that all the ifconfig values are roughly 2^32 (a hint for overflows?) | 17:43 | |
rtg | likely an underflow | 17:44 |
jdstrand | this was interesting in -proposed's kernel: net: heap overflow in __audit_sockaddr() | 17:44 |
jdstrand | but there were several things in -proposed kernel that looked interesting. I didn't try -proposed yet | 17:45 |
jdstrand | hrmm, -55 has it too | 17:46 |
jdstrand | it seemed to take a little longer, but I see it | 17:47 |
rtg | jdstrand, is it related to promiscuous mode ? | 17:47 |
jdstrand | I haven't used tcpdump since this reboot | 17:47 |
rtg | jdstrand, knowing the atl1c driver, this issue might have existed since the first release. there have only been 2 stable updates since then. | 17:50 |
jdstrand | I wonder if it is in linux-firmware | 17:50 |
jdstrand | I recorded that I upgraded linux-firmware on 12-04 | 17:50 |
rtg | jdstrand, checking... but I don't recall that it loads firmware. | 17:51 |
jdstrand | (the date that is) | 17:51 |
apw | atl1c, is that an ethernet device | 17:51 |
apw | having to rmmod that rings a bell, so i might have one | 17:51 |
rtg | jdstrand, only firmware load is from your wifi gizmo | 17:52 |
rtg | jdstrand, just for kicks try installing the Saucy LTS kernel to see if you get the same result | 17:54 |
jdstrand | I wonder if this is a red herring for her network issues. I guess I should try -23 to see if it was always there and -58 to see if it fixes it | 17:55 |
* rtg -> lunch | 18:29 | |
jdstrand | ok, -58 exhibits the problem. -23 didn't in the amount of time I tested it. the saucy-lts kernel did not either, but I couldn't test it for very long cause the nvidia driver wasn't behaving | 18:47 |
jdstrand | I updated the bug | 18:47 |
jdstrand | right now I put her on -58 and trying to see if her network issues go away | 18:48 |
xclaesse | Anyone knows what's causing https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1258838 ? | 18:51 |
ubot2` | Launchpad bug 1258838 in linux (Ubuntu) "[LENOVO 23252EG] suspend/resume failure" [Undecided,Confirmed] | 18:51 |
xclaesse | it's a really annoying regression in 13.10 | 18:52 |
xclaesse | if I can provide any extra info, please ask | 18:52 |
cking | apw, rss updated hugepage info in your inbox | 18:53 |
jsalisbury | jdstrand, I posed a comment in the bug. We can either perform a regular bisect to find the commit that introduced the bug, or we can perform a "Reverse" bisect to find what commit fixes this in Saucy. | 19:35 |
jdstrand | jsalisbury: well, I'm not 100% sure that it is not broken in -23 or fixed in saucy. | 19:50 |
jdstrand | I'll need to get back to you and let her run -23 for a while (since getting saucy to work for her would take me a bit of fiddling with nvidia) | 19:50 |
jsalisbury | jdstrand, ok. We can bisect if there is a way to reliably reproduce the bug. | 19:51 |
jdstrand | that's the trick. it seems to show up in -55 - -58 regularly, but I don't have a reduced test case yet | 19:51 |
* rtg -> EOD | 21:03 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!