* NMI received for unknown reason, 2.6.38-rc6 regression? @ 2011-03-01 15:03 denys 2011-03-01 16:08 ` Cyrill Gorcunov 0 siblings, 1 reply; 6+ messages in thread From: denys @ 2011-03-01 15:03 UTC (permalink / raw) To: Thomas Gleixner, Ingo Molnar, H. Peter Anvin, x86, linux-kernel I upgrade around 140 hosts (from 2.6.33 till 2.6.37), and got on many of them error/warining, flooding kernel log. Here is short snapshot: [ 1882.057474] Uhhuh. NMI received for unknown reason 3c on CPU 0. [ 1882.057576] Do you have a strange power saving mode enabled? [ 1882.057672] Dazed and confused, but trying to continue [ 2421.419732] Uhhuh. NMI received for unknown reason 3c on CPU 0. [ 2421.419835] Do you have a strange power saving mode enabled? [ 2421.419930] Dazed and confused, but trying to continue [ 2636.016831] Uhhuh. NMI received for unknown reason 2c on CPU 1. [ 2636.016934] Do you have a strange power saving mode enabled? [ 2636.017003] Dazed and confused, but trying to continue Full dmesg from 2 machines: http://www.nuclearcat.com/dmesg1.txt http://www.nuclearcat.com/dmesg2.txt I can provide more, if required. It seems nmi_watchdog is enabled by default, and it is causing issue. I am checking now with nmi_watchdog=0, but i need more time to confirm that. Also i am experiencing some problem with ppp users(all of them is pppoe servers), but i am not sure it is related to that, so maybe this NMI warning is just cosmetic regression. All systems is x86, same kernel config. If you need more information - let me know. ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: NMI received for unknown reason, 2.6.38-rc6 regression? 2011-03-01 15:03 NMI received for unknown reason, 2.6.38-rc6 regression? denys @ 2011-03-01 16:08 ` Cyrill Gorcunov 2011-03-01 16:42 ` denys 0 siblings, 1 reply; 6+ messages in thread From: Cyrill Gorcunov @ 2011-03-01 16:08 UTC (permalink / raw) To: denys; +Cc: Thomas Gleixner, Ingo Molnar, H. Peter Anvin, x86, linux-kernel On 03/01/2011 06:03 PM, denys@visp.net.lb wrote: > I upgrade around 140 hosts (from 2.6.33 till 2.6.37), and got on many of them error/warining, flooding kernel log. Here is short snapshot: > > [ 1882.057474] Uhhuh. NMI received for unknown reason 3c on CPU 0. > [ 1882.057576] Do you have a strange power saving mode enabled? > [ 1882.057672] Dazed and confused, but trying to continue > [ 2421.419732] Uhhuh. NMI received for unknown reason 3c on CPU 0. > [ 2421.419835] Do you have a strange power saving mode enabled? > [ 2421.419930] Dazed and confused, but trying to continue > [ 2636.016831] Uhhuh. NMI received for unknown reason 2c on CPU 1. > [ 2636.016934] Do you have a strange power saving mode enabled? > [ 2636.017003] Dazed and confused, but trying to continue > > Full dmesg from 2 machines: > http://www.nuclearcat.com/dmesg1.txt > http://www.nuclearcat.com/dmesg2.txt > I can provide more, if required. > > It seems nmi_watchdog is enabled by default, and it is causing issue. I am checking now with nmi_watchdog=0, but i need more time to confirm that. > Also i am experiencing some problem with ppp users(all of them is pppoe servers), but i am not sure it is related to that, so maybe this NMI warning is just cosmetic regression. > > All systems is x86, same kernel config. > If you need more information - let me know. > nmi_watchdog=0 should help here, actually a nit was fixed by https://patchwork.kernel.org/patch/566611/ which is not in 2.6.38-rc6 but I rather suspect it'll be in -rc7 or final .38. If you have an ability to pickup it and test -- this would be great! -- Cyrill ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: NMI received for unknown reason, 2.6.38-rc6 regression? 2011-03-01 16:08 ` Cyrill Gorcunov @ 2011-03-01 16:42 ` denys 2011-03-01 17:03 ` Cyrill Gorcunov 2011-03-02 7:59 ` Ingo Molnar 0 siblings, 2 replies; 6+ messages in thread From: denys @ 2011-03-01 16:42 UTC (permalink / raw) To: Cyrill Gorcunov Cc: Thomas Gleixner, Ingo Molnar, H. Peter Anvin, x86, linux-kernel On Tue, 01 Mar 2011 19:08:43 +0300, Cyrill Gorcunov wrote: > On 03/01/2011 06:03 PM, denys@visp.net.lb wrote: >> I upgrade around 140 hosts (from 2.6.33 till 2.6.37), and got on >> many of them error/warining, flooding kernel log. Here is short >> snapshot: >> >> [ 1882.057474] Uhhuh. NMI received for unknown reason 3c on CPU 0. >> [ 1882.057576] Do you have a strange power saving mode enabled? >> [ 1882.057672] Dazed and confused, but trying to continue >> [ 2421.419732] Uhhuh. NMI received for unknown reason 3c on CPU 0. >> [ 2421.419835] Do you have a strange power saving mode enabled? >> [ 2421.419930] Dazed and confused, but trying to continue >> [ 2636.016831] Uhhuh. NMI received for unknown reason 2c on CPU 1. >> [ 2636.016934] Do you have a strange power saving mode enabled? >> [ 2636.017003] Dazed and confused, but trying to continue >> >> Full dmesg from 2 machines: >> http://www.nuclearcat.com/dmesg1.txt >> http://www.nuclearcat.com/dmesg2.txt >> I can provide more, if required. >> >> It seems nmi_watchdog is enabled by default, and it is causing >> issue. I am checking now with nmi_watchdog=0, but i need more time to >> confirm that. >> Also i am experiencing some problem with ppp users(all of them is >> pppoe servers), but i am not sure it is related to that, so maybe this >> NMI warning is just cosmetic regression. >> >> All systems is x86, same kernel config. >> If you need more information - let me know. >> > > nmi_watchdog=0 should help here, actually a nit was fixed by > https://patchwork.kernel.org/patch/566611/ > which is not in 2.6.38-rc6 but I rather suspect it'll be in -rc7 or > final .38. If you have an ability > to pickup it and test -- this would be great! I test it, and it seems helps. At least on one host, and yes, seems all of them P4. ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: NMI received for unknown reason, 2.6.38-rc6 regression? 2011-03-01 16:42 ` denys @ 2011-03-01 17:03 ` Cyrill Gorcunov 2011-03-02 7:59 ` Ingo Molnar 1 sibling, 0 replies; 6+ messages in thread From: Cyrill Gorcunov @ 2011-03-01 17:03 UTC (permalink / raw) To: denys; +Cc: Thomas Gleixner, Ingo Molnar, H. Peter Anvin, x86, linux-kernel On 03/01/2011 07:42 PM, denys@visp.net.lb wrote: ... >> >> nmi_watchdog=0 should help here, actually a nit was fixed by >> https://patchwork.kernel.org/patch/566611/ >> which is not in 2.6.38-rc6 but I rather suspect it'll be in -rc7 or >> final .38. If you have an ability >> to pickup it and test -- this would be great! > > I test it, and it seems helps. At least on one host, and yes, seems all of them P4. > ok, thanks! ping me if any :) -- Cyrill ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: NMI received for unknown reason, 2.6.38-rc6 regression? 2011-03-01 16:42 ` denys 2011-03-01 17:03 ` Cyrill Gorcunov @ 2011-03-02 7:59 ` Ingo Molnar 2011-03-02 13:16 ` denys 1 sibling, 1 reply; 6+ messages in thread From: Ingo Molnar @ 2011-03-02 7:59 UTC (permalink / raw) To: denys Cc: Cyrill Gorcunov, Thomas Gleixner, Ingo Molnar, H. Peter Anvin, x86, linux-kernel * denys@visp.net.lb <denys@visp.net.lb> wrote: > On Tue, 01 Mar 2011 19:08:43 +0300, Cyrill Gorcunov wrote: > >On 03/01/2011 06:03 PM, denys@visp.net.lb wrote: > >>I upgrade around 140 hosts (from 2.6.33 till 2.6.37), and got on > >>many of them error/warining, flooding kernel log. Here is short > >>snapshot: > >> > >>[ 1882.057474] Uhhuh. NMI received for unknown reason 3c on CPU 0. > >>[ 1882.057576] Do you have a strange power saving mode enabled? > >>[ 1882.057672] Dazed and confused, but trying to continue > >>[ 2421.419732] Uhhuh. NMI received for unknown reason 3c on CPU 0. > >>[ 2421.419835] Do you have a strange power saving mode enabled? > >>[ 2421.419930] Dazed and confused, but trying to continue > >>[ 2636.016831] Uhhuh. NMI received for unknown reason 2c on CPU 1. > >>[ 2636.016934] Do you have a strange power saving mode enabled? > >>[ 2636.017003] Dazed and confused, but trying to continue > >> > >>Full dmesg from 2 machines: > >>http://www.nuclearcat.com/dmesg1.txt > >>http://www.nuclearcat.com/dmesg2.txt > >>I can provide more, if required. > >> > >>It seems nmi_watchdog is enabled by default, and it is causing > >>issue. I am checking now with nmi_watchdog=0, but i need more > >>time to confirm that. > >>Also i am experiencing some problem with ppp users(all of them > >>is pppoe servers), but i am not sure it is related to that, so > >>maybe this NMI warning is just cosmetic regression. > >> > >>All systems is x86, same kernel config. > >>If you need more information - let me know. > >> > > > >nmi_watchdog=0 should help here, actually a nit was fixed by > >https://patchwork.kernel.org/patch/566611/ > >which is not in 2.6.38-rc6 but I rather suspect it'll be in -rc7 or > >final .38. If you have an ability > >to pickup it and test -- this would be great! > I test it, and it seems helps. At least on one host, and yes, seems > all of them P4. Mind checking -rc7, does it work 'out of box', without requiring any workarounds? -rc7 already has this fix included: 7d44ec193d95: perf, x86: P4 PMU: Fix spurious NMI messages -rc6 did not have it yet. Thanks, Ingo ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: NMI received for unknown reason, 2.6.38-rc6 regression? 2011-03-02 7:59 ` Ingo Molnar @ 2011-03-02 13:16 ` denys 0 siblings, 0 replies; 6+ messages in thread From: denys @ 2011-03-02 13:16 UTC (permalink / raw) To: Ingo Molnar Cc: Cyrill Gorcunov, Thomas Gleixner, Ingo Molnar, H. Peter Anvin, x86, linux-kernel On Wed, 2 Mar 2011 08:59:31 +0100, Ingo Molnar wrote: > * denys@visp.net.lb <denys@visp.net.lb> wrote: > >> On Tue, 01 Mar 2011 19:08:43 +0300, Cyrill Gorcunov wrote: >> >On 03/01/2011 06:03 PM, denys@visp.net.lb wrote: >> >>I upgrade around 140 hosts (from 2.6.33 till 2.6.37), and got on >> >>many of them error/warining, flooding kernel log. Here is short >> >>snapshot: >> >> >> >>[ 1882.057474] Uhhuh. NMI received for unknown reason 3c on CPU 0. >> >>[ 1882.057576] Do you have a strange power saving mode enabled? >> >>[ 1882.057672] Dazed and confused, but trying to continue >> >>[ 2421.419732] Uhhuh. NMI received for unknown reason 3c on CPU 0. >> >>[ 2421.419835] Do you have a strange power saving mode enabled? >> >>[ 2421.419930] Dazed and confused, but trying to continue >> >>[ 2636.016831] Uhhuh. NMI received for unknown reason 2c on CPU 1. >> >>[ 2636.016934] Do you have a strange power saving mode enabled? >> >>[ 2636.017003] Dazed and confused, but trying to continue >> >> >> >>Full dmesg from 2 machines: >> >>http://www.nuclearcat.com/dmesg1.txt >> >>http://www.nuclearcat.com/dmesg2.txt >> >>I can provide more, if required. >> >> >> >>It seems nmi_watchdog is enabled by default, and it is causing >> >>issue. I am checking now with nmi_watchdog=0, but i need more >> >>time to confirm that. >> >>Also i am experiencing some problem with ppp users(all of them >> >>is pppoe servers), but i am not sure it is related to that, so >> >>maybe this NMI warning is just cosmetic regression. >> >> >> >>All systems is x86, same kernel config. >> >>If you need more information - let me know. >> >> >> > >> >nmi_watchdog=0 should help here, actually a nit was fixed by >> >https://patchwork.kernel.org/patch/566611/ >> >which is not in 2.6.38-rc6 but I rather suspect it'll be in -rc7 or >> >final .38. If you have an ability >> >to pickup it and test -- this would be great! >> I test it, and it seems helps. At least on one host, and yes, seems >> all of them P4. > > Mind checking -rc7, does it work 'out of box', without requiring any > workarounds? > -rc7 already has this fix included: > > 7d44ec193d95: perf, x86: P4 PMU: Fix spurious NMI messages > > -rc6 did not have it yet. Yes, rc7 fine too, tested it now. > > Thanks, > > Ingo ^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2011-03-02 13:16 UTC | newest] Thread overview: 6+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2011-03-01 15:03 NMI received for unknown reason, 2.6.38-rc6 regression? denys 2011-03-01 16:08 ` Cyrill Gorcunov 2011-03-01 16:42 ` denys 2011-03-01 17:03 ` Cyrill Gorcunov 2011-03-02 7:59 ` Ingo Molnar 2011-03-02 13:16 ` denys
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox