/srv/irclogs.ubuntu.com/2014/11/24/#ubuntu-kernel.txt

=== hughhalf is now known as hughhalf_afk
=== hughhalf_afk is now known as hughhalf
Kanohi, when will there be 3.18 rc6 in vivid?16:43
Kanoits rebased but not tagged16:44
sajanI was wondering if someone can tell me when the following iwlwifi patch would be pulled in and available in the Ubuntu kernel.  I installed 3.17.1 on a Utopic system and doesn't seem to be there. - http://bit.ly/15f4WIn.  Would it be there in the next 3.17.x build?  If so, when does that happen?  Thanks.17:00
sforsheesajan: I'm not sure when that will make it to vivid. It should be in the utopic kernel that was just released, but it won't make it into trusty for several more weeks.17:13
sajansforshee: Thanks.17:14
infinitysforshee: If it's in utopic, it's in vivid.18:34
infinityWell, vivid-proposed.18:34
binBASHHi tinoco, I saw you assigned yourself https://bugs.launchpad.net/ubuntu/+source/linux/+bug/131855118:49
ubot5Launchpad bug 1318551 in linux (Ubuntu) "Kernel Panic - not syncing: An NMI occurred, please see the Integrated Management Log for details." [High,Confirmed]18:49
binBASHIf you need more info you can write me :-)18:49
tinocobinBASH: hey18:50
tinocoi did..  cause i just got a UA bug around this18:50
tinocorecommended customer to (workaround) deactivate max cstates 18:50
tinocoasked him to update their firmware (using some HP already reported cases)18:50
tinocoand im investigating little further now18:50
tinocoi got a crash on the idle task :D18:51
binBASHThe workaround I use is noautogroup kernel boot parameter18:51
tinocobinBASH: i´ve seen the bisect. you made it ?18:51
binBASHNope, because I dunno where I should start18:51
binBASHI'm not kernel specialist, sorry18:52
tinocobinBASH: did it work with you ?18:52
tinocohave u tried de-activating c-states ?18:52
binBASHCould try it18:52
tinococould you ? and report it back on the public bug ?18:52
binBASHIf bios allows it. I have the issue on my desktop...18:52
tinocotry appending this to kernel cmdline (/etc/default/grub) "intel_idle.max_cstate=0 processor.max_cstate=0"  18:53
tinocoand/or disabling it by BIOS18:53
tinocobinBASH: what server are u using ?18:53
tinocois it a proliant ? or just your workstation ?18:53
binBASHWell, I have it on multiple systems18:54
tinoco:\ hum18:54
binBASHBut the desktop here is Gigabyte board...18:54
binBASHCheap Desktop HW :)18:55
tinocoyep. but it might be related to samething18:55
tinocogood for us if you can test these and report it on the public bug18:55
tinocoits always good to get feedback from other platforms 18:55
binBASHI will try it in the next 5 mins :)18:55
binBASHJust let me finish eating up my dinner please18:56
tinocogreat :D . did noautogroup solve the thing for you ?18:56
binBASHyup18:56
binBASHit did. No issue with it18:56
tinocohum.. it might be related to the way idle_task handles cpu instructions18:56
tinocoi´ll check code and see what is modified by using this18:56
tinocobinBASH: really appreciate 18:56
tinocolet me know any feedback you might have regarding this18:56
binBASHWhen I don't use the param it crash during boot in 99%18:57
tinocobinBASH: yep.. i´ve been informed people are getting this randomly with proliant servers18:57
tinocoi received a kernel dump with the idle task causing the panic18:57
tinocoand found the public bug.. looks like it fits on my case18:57
binBASHyeah, it can happen also after boot process randomely. It crashs so bad even Magic-Sysreq doesn't work then18:58
tinocoyep.. lets see if c-states being disabled handles the issue18:58
tinocoif they do.. i´ll look deeper why18:58
binBASHok, sec. I'll add the params you gave to cmd line18:58
tinocotake your time ;) lol18:59
binBASHOk, will reboot now, brb19:01
binBASHok tinoco, I've tested boot now several times, the params don't fix it19:08
tinocobinBASH: what about disabling C-states under BIOS ?19:09
tinocodo you have that option ?19:09
binBASHI can test it as well np19:09
tinocobinBASH: please, tks19:10
binBASHtinoco: The mainboard I'm using btw. is Gigabyte H77-D3H with Intel i7-3770K cpu19:11
tinocoim getting errors with this: Intel(R) Xeon(R) CPU E5-2630 v2 @ 2.60GHz      19:12
tinocobut i´ve seen cases where upgrading bios/firmware solved similar issues for proliant19:12
binBASHDo you have EFI system?19:13
binBASHBecause I'm using EFI boot19:13
tinocobinBASH: have u tried upgrading your firmwar e?19:13
binBASHNope19:13
tinocoi wonder if we are having the same problem here19:13
tinococause people informed about not using c-states to fix19:13
tinocoand you fixed by changing way scheduler behaves19:14
tinocois it possible for you to generate a crash19:14
binBASHI will try to disable C-states in bios19:14
tinocoand upload it to the case ?19:14
tinocoyep, please19:14
binBASHreboot brb... :)19:14
tinoco;)19:14
binBASHtinoco: nope, didn't fix it19:25
tinocoyep.. i think we might be facing different things19:25
tinocoanyway, could you generate a kernel dump19:25
tinocoand attach to the public case ?19:25
tinocoi can further analyse if is the same case, if they are related or not19:26
tinocobinBASH: but i would suggest you a bios update before19:26
tinocojust in case19:26
tinocoand tks for the tries, anyway :)19:26
binBASHnp19:28
binBASHWill try to find out how to do it :)19:28
tinocobinBASH: https://wiki.ubuntu.com/Kernel/CrashdumpRecipe19:28
binBASHYeah, currently reading it, thx19:29

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