=== jmp_ is now known as _jmp_ === smb` is now known as smb [08:36] * apw watches 100s MB of updated download [08:52] Which was even there yesterday... [08:53] including just a new gcc... nothing to worry about... [08:56] smb, was that my '100s MB of updates' you are talking about ? [08:56] are you seeing "waiting for network configuration" as a plymouth message during boot? [08:56] apw, Only when my network is bust usually [08:57] So by now its a bad sign to me if I see it [08:57] smb, this is on everything and on multiple networks all of a suddent [08:58] Hm, strange. But then you don't see the waiting 60s more message? [08:58] And your network is up when you log in? [08:59] apw, ^ [08:59] yep just a single message [09:01] The question now is whether it is always there and just now long enough for you to notice or whether it gets printed when network setup is delayed for a certain time [09:01] any way, something seems slower for you [09:02] i don't normally see any messages on the boot screen other than whn its doing an fsck [09:02] this message i have never seen before, and indeed i thought networks were done after you logged in [09:03] apw, No that changed a while ago [09:03] Even with nm, your network was running even you being on the lightdm or gdm screen [09:04] ok, still never ever seen that message with network or without [09:04] and its all of a sudden on both my main machines and with two different network setups [09:05] ok, so something became slower. I assume just this mornings update (if one can say just to that) [10:25] apw, Hm, finished updating a test laptop and I do not see that message in my environment [10:25] smb, hrm, will do the same in a bit [10:26] apw, ok [10:26] cking, we are talking to you [10:27] cking, we heard you, a bit at least [10:27] * cking gives mumble a kick [11:09] brb [12:34] * apw loses mumble too [12:34] wtf is with this stuff these days [12:35] its all hangouts now anyway :( [12:36] bah [13:38] cking: ping [13:59] awe, pong [14:01] hi [14:01] so my machines has shutdown on me a few times in the last week [14:01] I tracked it down to excessive CPU temp [14:01] I was going to enter a bug against the kernel this morning, but noticed a new kernel was released [14:02] should I wait to hit the bug again before reporting? [14:02] ( also can it really be considered a kernel bug? ) [14:03] awe I'd say file a bug so at least we can track this [14:03] you are not the first to report this [14:03] ok [14:03] thanks [14:03] is there already a bug? [14:04] awe, file a new bug, as I expect your H/W is different [14:04] right [14:04] will do [14:06] awe, I have a bunch of things for you to try, which will help me corner this issue [14:06] ok [14:06] I'm in crunch mode right now, but will file a bug today [14:06] ack [14:07] ttyl [14:07] sforshee, ping [14:08] pgraner, hi [14:08] sforshee, hey, so I think the mystery of the dropping wifi is solved [14:09] really! what's causing it? [14:09] sforshee, I checked yesterday and running up2date precise kernel it happened twice yesterday on that netbook [14:10] I found https://bugs.launchpad.net/ubuntu/+source/linux/+bug/937118 [14:10] Launchpad bug 937118 in linux "Wireless stops passing packets" [High,Confirmed] [14:10] and mainline 3.3.0-030300rc6-generic has made it work [14:11] pgraner, sforshee yeah, the linux-backports-modules-cw-3.3-precise-generic package solved that bug because the bug was fixed upstream. [14:11] looks like its a dd-wrt issue and I'm guessing whatever it is exists on the cisco fw we use at events [14:11] sforshee, Its been running now for over 8 hours and no issue [14:12] sforshee, I could trigger it here in a matter of 2-3 hours [14:12] pgraner, interesting. I use dd-wrt on one of my routers, but it wasn't the one I was using to test that machine. [14:12] we may want to bisect then to see what fixed it so we can backport it to precise [14:13] jsalisbury, sounds like a job for you my friend :-D [14:13] pgraner, sforshee will do. I think it may be this that fixed it: eea79e0713d94b02952f6c591b615710fd40a562 [14:14] pgraner, sforshee But I didn't do an actual bisect yet. I came up with that commit after reviewing the git log. [14:14] jsalisbury, that's a merge commit, so it's not _the_ fix [14:14] it's just when the fix got merged to linus's tree [14:14] sforshee, ahh right. So a bisect of the merge commit will need to be done. [14:16] awe, can you boot with an oneiric kernel and see if the overheating re-occurs? [14:16] cking, let me catch you in a few minutes... [14:18] cking, I've only hit it twice in the last week... [14:18] unfortunately it's not reproduce on demand. ;( [14:19] awe, well, I can write up a bunch of things to try once you've file a bug ;-) [14:20] cking, ok cool === JanC_ is now known as JanC === smb` is now known as smb [14:40] apw, cking - still no crash today - and I've been stressing my machine pretty hard over the last couple of days - the fan thing seems to have fixed it [14:41] akgraner, that wasn't a fix, it was step #1 in me seeing what the problem could be - I've updated the bug - can you try the next step as instructed [14:43] cking, sure [14:43] thanks! [14:43] sorry I didn't see it sooner - I thought I would get an email when someone comments on it...weird [14:43] akgraner, LP email isn't instantaneous at times [14:44] cking, I didn't need to update a filter :-) [14:44] ugh [14:45] I meant - I did get it - just need to update my filters - English and typing fail today it seems [14:49] ah, no worries [14:50] * ogasawara back in 20 [15:02] sforshee, bug 952698 [15:02] Launchpad bug 952698 in linux "Backlight no longer works on Macbook Pro5,5 with EFI boot" [Undecided,Incomplete] https://launchpad.net/bugs/952698 [15:02] sforshee, backlight actually works with nouveau driver w/ EFI boot [15:02] sforshee, and backlight is controlled by the nouveau driver instead of apple_bl [15:03] sforshee, backlight used to work w/ BIOS compatible mode, I'll need to test again [15:04] ericm|ubuntu, apple_bl doesn't work on all macbooks, nouveau might be the only way to change it [15:04] * cking -> back in 20min [15:04] sforshee, apple_bl works sometimes as I remember but not reliable [15:05] sforshee, there is a small issue w/ nvidia-current though, when de-activating it in jockey, it makes nouveau un-usable, I have to purge it to get nouveau back again [15:06] ericm|ubuntu, it may be that it only works in bios-compatibility, or that it needs changes to work with efi boot. I'm not sure. [15:06] sforshee, I believe it's nvidia-current black-listed nouveau [15:06] that's nasty, probably need to file a bug for that [15:06] sforshee, yeah I doubt the I/O ports are still valid w/ EFI boot - brightness control never seems to be reliable to me [15:07] ericm|ubuntu, adjusting via the graphics card is probably your best bet then [15:08] sforshee, yes [15:08] the backlight situation on macbooks is horrendous [15:08] sforshee, and we won't have it w/ nvidia-current I guess [15:08] ericm|ubuntu, no, and there's nothing we can do about it [15:09] sforshee, there is a backlight driver in mactel ppa - but that's a bit hackish [15:10] sforshee, one other problem w/ nvidia-current + EFI boot, I cannot seem to find my framebuffer consoles [15:11] ericm|ubuntu, hackish yes, and I don't know what happens if you have it installed and try to use the nouveau driver [15:11] EFI boot still has lots of issues to iron out [15:11] graphics is the biggest one [15:12] most of the drm drivers rely on having access to the vbios, which doesn't seem to be possible in EFI boot [15:12] Sure it is [15:12] sforshee, yeah that's one issue [15:12] But Apple don't provide it on Radeon-based machines for reasons that are unclear [15:13] You can work around this by grabbing it out of the firmware during boot services and handing it off to the kernel [15:13] I've a patch for grub that does that, but haven't forward-ported it to grub2 yet [15:13] mjg59, thanks for the explanation. I confess I haven't looked into it much yet. [15:13] But yeah nvidia is going to work badly on EFI Macs [15:13] nouveau is a much better choice there [17:00] bjf, any idea who I talk to about problems with ubuntu-bug? I tried to run 'ubuntu-bug -p linux' and it just returns on my system... [17:00] I have a power-mgmt problem which I guess I'll report directly via LP, and then try to apport attach... === JanC_ is now known as JanC [17:16] awe, i think pitti knows more about ubuntu-bug than anyone [17:20] awe: its ubuntu-bug linux [17:21] Sarvatt, someone should fix: https://wiki.ubuntu.com/Kernel/Bugs [17:21] cause that's where I got the command-line from [17:21] '$ ubuntu-bug -p linux' [17:22] sorry about that, fixed the wiki [17:22] -p linux is for apport-collect [17:23] * ppisati -> brb [17:27] If i install a mainline upstream kernel to fix a bug, does that mess up updating from the repos or will it detect my newer kernel? [18:06] o [18:07] ogasawara, the enforcer deliberatly uses the enforcer file on master ... so that the rules are consistant on all branches [18:07] apw: just saw your email [18:07] ogasawara, and it has expressive power in theory at least to allow different rules to be expressed for different flavours [18:08] apw: will yank the patch from master-next [18:28] ppisati, you gave the arm peeps a way to test with an initramfs-less kernel didn't you, using the overlapping partition tables with puid fields ... right ? [18:33] apw: being one of those arm peeps directly involved with testing, I have heard nothing yet. [18:53] cking, another overheat related bug reported, bug 953205 Looks like the same type of hardware as bug 751689 so it may be a duplicate. [18:53] Launchpad bug 953205 in linux "System shuts down due to CPU temp exceeding critical thresh-hold (100C)" [Medium,Confirmed] https://launchpad.net/bugs/953205 [18:53] Launchpad bug 751689 in linux "ThinkPads overheat due to slow fans when on 'auto'" [Critical,In progress] https://launchpad.net/bugs/751689 [18:54] jsalisbury, cool, I was talking to tony about that early [18:54] earlier [18:54] cking, ahh, ok. [18:54] are the fans on the thinkpad not managed by acpi or are the thermal zones just wrong? [18:55] ohsix, they can be managed by the firmware or by the thinkpad_acpi driver (by prodding the EC memory if I recall correctly) [18:55] interesting [18:56] also strange that even if you can do it with thinkpad_acpi, TMM1/2 don't work; or the critical thermal zone in acpi doesn't overrule it [18:56] it's all in the thinkpad_acpi driver if you want to see the gory details [18:56] okie dokie [18:57] jsalisbury, I hacked up some code to monitor what's going on so I can get an idea of what's causing the grief [18:58] cking, cool. I can reproduce an overhead pretty quickly on my x201, so I can do some testing if needed. [18:58] jsalisbury, so is this happening more with precise than oneiric? [18:59] burnmmx ftw [18:59] cking, In my case, I would say it happens the same. My laptop will overheat and hit 100C shortly after kicking off a kernel build. [19:00] cking, That was also the case in Oneiric [19:00] jsalisbury, ok - that's bad, but not looking like a glaring regression. === rsalveti` is now known as rsalveti [21:05] * cking --> EOD === yofel_ is now known as yofel