Computer blocked because of error smpboot CPU2: Not responding
Dear All, I am experiencing the following problem while booting Fedora 19: smpboot: CPU2: Not responding. The computer seems to be blocked. Is there some way of rebooting it without having to power off the computer? Thanks in advance, Paul -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Computer blocked because of error smpboot CPU2: Not responding
On Fri, Jul 12, 2013 at 6:49 PM, Paul Smith wrote: > I am experiencing the following problem while booting Fedora 19: > > smpboot: CPU2: Not responding. > > The computer seems to be blocked. Is there some way of rebooting it > without having to power off the computer? I believe that the cause of this problem was the fact that I had an external disk connected to the computer. I have meanwhile unplugged it, but the booting process is totally blocked and I do not know how to resume it. Paul -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Computer blocked because of error smpboot CPU2: Not responding
On Fri, Jul 12, 2013 at 8:54 PM, Reindl Harald wrote: >> I am experiencing the following problem while booting Fedora 19: >> >> smpboot: CPU2: Not responding. >> >> The computer seems to be blocked. Is there some way of rebooting it >> without having to power off the computer? > > https://www.kernel.org/doc/Documentation/kernel-parameters.txt > > nosmp [SMP] Tells an SMP kernel to act as a UP kernel, > and disable the IO APIC. legacy for "maxcpus=0" > > > however, if one CPU or core doe snot respond > all the time assume your hardware is dying Thanks, Reindl. The issue was caused by the fact that I rebooted the computer without having disconnected the external disk before. Since a hard power off, the computer has worked just fine. But I was keen to avoid the hard power off, as someone told me that it is maleficent for the hard drive. However, it seems that that opinion is not unanimous according to the discussions I have consulted meanwhile -- many claim that a hard power off is pretty safe regarding hardware. Paul -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Computer blocked because of error smpboot CPU2: Not responding
On 07/12/2013 01:00 PM, Paul Smith issued this missive: On Fri, Jul 12, 2013 at 8:54 PM, Reindl Harald wrote: I am experiencing the following problem while booting Fedora 19: smpboot: CPU2: Not responding. The computer seems to be blocked. Is there some way of rebooting it without having to power off the computer? https://www.kernel.org/doc/Documentation/kernel-parameters.txt nosmp [SMP] Tells an SMP kernel to act as a UP kernel, and disable the IO APIC. legacy for "maxcpus=0" however, if one CPU or core doe snot respond all the time assume your hardware is dying Thanks, Reindl. The issue was caused by the fact that I rebooted the computer without having disconnected the external disk before. Since a hard power off, the computer has worked just fine. But I was keen to avoid the hard power off, as someone told me that it is maleficent for the hard drive. However, it seems that that opinion is not unanimous according to the discussions I have consulted meanwhile -- many claim that a hard power off is pretty safe regarding hardware. Power cycling (more specifically thermal cycling) is harder on the hardware than simply leaving it on. In my 35+ years in electronics, generally if a piece of equipment is going to die, it's going to do so during power up or a really big swing in temperatures (such as the loss of aircon in a data center). I will say this observation is completely empirical and I can't back it up with hard numbers, but it is my experience. The occasional hard, poweroff boot shouldn't be a big deal and you may never experience a failure because of it. I have, which is one reason my systems at home never get powered off other than when I perform maintenance on them. I do turn off monitors and the like, but they're cheap to replace if they croak compared with my computers and the data contained thereon (and yes, I back up religiously). -- - Rick Stevens, Systems Engineer, AllDigitalri...@alldigital.com - - AIM/Skype: therps2ICQ: 22643734Yahoo: origrps2 - -- - "Daddy, why doesn't this magnet pick up this floppy disk?" - -- -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Computer blocked because of error smpboot CPU2: Not responding
On 07/12/2013 01:43 PM, Rick Stevens wrote: Power cycling (more specifically thermal cycling) is harder on the hardware than simply leaving it on. In my 35+ years in electronics, generally if a piece of equipment is going to die, it's going to do so during power up or a really big swing in temperatures (such as the loss of aircon in a data center). I will say this observation is completely empirical and I can't back it up with hard numbers, but it is my experience. This is why an incandescent lightbulb is much more likely to fail when you turn it on than at any other time. I've read stories about bulbs that have been working for decades because they've never been turned off. I have two reasons for leaving my desktop on 24/7: first, because Linux is designed to be run that way[1] and that allows me to use my uptime[2] as an example of how stable Linux is and second, I have BOINC installed and even when I'm away at a convention, or house sitting, it's doing useful work. [1]i.e., "because I can." [2]Normally, I only reboot for kernel upgrades. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Computer blocked because of error smpboot CPU2: Not responding
On 07/12/2013 04:02 PM, Joe Zeff wrote: <> This is why an incandescent lightbulb is much more likely to fail when you turn it on than at any other time. this is mainly caused by the 'inrush current" when bulb first has voltage applied. http://en.wikipedia.org/wiki/Inrush_current I've read stories about bulbs that have been working for decades because > they've never been turned off. i have a dual lamp fixture in kitchen that has been on a dimmer control from back in late 80's. neither of the bulbs have burned out because the dimmer is a 'zero cross on' type and because the dimmer always starts out at minimal voltage, there is no huge inrush current. as for leaving system power up, 'boinc' is one very good reason. other reason is that you eliminate heating and cooling of system and thereby causing early break down of components from inrush and dirtying contacts when they expand and contract between each other. as for leaving equipment turned on 24/7, systems stabilize and maintain their accuracy this way. granted, you electric bill will be increased, but i believe increased cost is worth the cost of down time and repairs. -- peace out. in a world with out fences, who needs gates. sl6.3 linux tc.hago. g . -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Computer blocked because of error smpboot CPU2: Not responding
On Sat, 2013-07-13 at 01:57 -0500, g wrote: > i have a dual lamp fixture in kitchen that has been on a dimmer > control from back in late 80's. neither of the bulbs have burned out > because the dimmer is a 'zero cross on' type and because the dimmer > always starts out at minimal voltage, there is no huge inrush current. It's common practice with film/tv/theatre lighting to preheat the lamps before turning them on. i.e. Before making them bright, you'll turn them on enough so that they just barely glow. Theatre technicians will swear that it makes their lamps last longer, that way. And that's ordinary incandescents, or halogen incandescents. -- [ Don't send private replies to my address, the mailbox is ignored. I read messages from the public lists. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Computer blocked because of error smpboot CPU2: Not responding
Am 12.07.2013 19:49, schrieb Paul Smith: > I am experiencing the following problem while booting Fedora 19: > > smpboot: CPU2: Not responding. > > The computer seems to be blocked. Is there some way of rebooting it > without having to power off the computer? https://www.kernel.org/doc/Documentation/kernel-parameters.txt nosmp [SMP] Tells an SMP kernel to act as a UP kernel, and disable the IO APIC. legacy for "maxcpus=0" however, if one CPU or core doe snot respond all the time assume your hardware is dying signature.asc Description: OpenPGP digital signature -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Computer blocked because of error smpboot CPU2: Not responding
Am 12.07.2013 22:00, schrieb Paul Smith: > On Fri, Jul 12, 2013 at 8:54 PM, Reindl Harald wrote: >>> I am experiencing the following problem while booting Fedora 19: >>> >>> smpboot: CPU2: Not responding. >>> >>> The computer seems to be blocked. Is there some way of rebooting it >>> without having to power off the computer? >> >> https://www.kernel.org/doc/Documentation/kernel-parameters.txt >> >> nosmp [SMP] Tells an SMP kernel to act as a UP kernel, >> and disable the IO APIC. legacy for "maxcpus=0" >> >> >> however, if one CPU or core does not respond >> all the time assume your hardware is dying > > Thanks, Reindl. The issue was caused by the fact that I rebooted the > computer without having disconnected the external disk before. Since a > hard power off, the computer has worked just fine. But I was keen to > avoid the hard power off, as someone told me that it is maleficent for > the hard drive. However, it seems that that opinion is not unanimous > according to the discussions I have consulted meanwhile -- many claim > that a hard power off is pretty safe regarding hardware i can not imagine why a connected external HD would result in "smpboot: CPU2: Not responding" - this makes pretty no sense because thes eboth facts have nothing to do with each other so yes, the power off resolved the problem most likely only temporary if it happens more than once at all signature.asc Description: OpenPGP digital signature -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
