[opensuse] Suddenly CPU1 Not Working
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 For some reason, today CPU1 is not working properly while the machine is in openSuSE 10.2. My machine is a dual-boot machine with the other OS being... well... the OTHER OS. It's an Intel core duo. Until today, everything was working fine. Suddenly, CPU1 is not working. CPU0 works fine. CPU1 works fine in the other OS. Below are some messages that occurred during boot up today: Initializing CPU#1 Kernel panic - not syncing: smp_callin: CPU1 started up but did not get a callout! Stuck ?? Inquiring remote APIC #1... ... APIC #1 ID: failed ... APIC #1 VERSION: failed ... APIC #1 SPIV: failed Brought up 1 CPUs Anyone have any ideas as to what might be happening? Thanks, Rick - -- Rick's Law: What cannot be imagined will be accomplished by a fool. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFGy7SvPIcjS54RJeARAoVrAJ9jdegMPVTtP2twc3i++Y0KMEMRiQCfShUY B2U+odlrP+H26F5x8AA3vdM= =XNgY -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Rick Friedman wrote:
For some reason, today CPU1 is not working properly while the machine is in openSuSE 10.2. My machine is a dual-boot machine with the other OS being... well... the OTHER OS. It's an Intel core duo.
Until today, everything was working fine. Suddenly, CPU1 is not working. CPU0 works fine. CPU1 works fine in the other OS. Below are some messages that occurred during boot up today:
Initializing CPU#1 Kernel panic - not syncing: smp_callin: CPU1 started up but did not get a callout!
Stuck ?? Inquiring remote APIC #1... ... APIC #1 ID: failed ... APIC #1 VERSION: failed ... APIC #1 SPIV: failed Brought up 1 CPUs
Anyone have any ideas as to what might be happening?
Thanks, Rick
Anyone have any ideas?? If not, I'll probably have to restore a system backup from before the problem occurred. Then, I'll do updates one by one until I see what the cause is. It would be great if someone already has an idea. :) Rick - -- Rick's Law: What cannot be imagined will be accomplished by a fool. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFGzhj9PIcjS54RJeARAoUgAJ9ug7PywxzEVdlkw+e5d/MiaIMybgCeNYvj UQxLww3G6gl9q5trm+T2l0w= =bZVV -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thursday 23 August 2007, Rick Friedman wrote:
Rick Friedman wrote:
For some reason, today CPU1 is not working properly while the machine is in openSuSE 10.2. My machine is a dual-boot machine with the other OS being... well... the OTHER OS. It's an Intel core duo.
Until today, everything was working fine. Suddenly, CPU1 is not working. CPU0 works fine. CPU1 works fine in the other OS. Below are some messages that occurred during boot up today:
Initializing CPU#1 Kernel panic - not syncing: smp_callin: CPU1 started up but did not get a callout!
Stuck ?? Inquiring remote APIC #1... ... APIC #1 ID: failed ... APIC #1 VERSION: failed ... APIC #1 SPIV: failed Brought up 1 CPUs
Anyone have any ideas as to what might be happening?
Thanks, Rick
Anyone have any ideas?? If not, I'll probably have to restore a system backup from before the problem occurred. Then, I'll do updates one by one until I see what the cause is.
It would be great if someone already has an idea. :)
Rick -- Rick's Law: What cannot be imagined will be accomplished by a fool.
------------- Do you remember what files you've installed or upgraded recently? Do you recall when was the last time you knew it was working correctly? I would try backtracing my steps of any recent actions to find the problem first. I think there is a history of those things done, but sorry don't remember where that file is located. Could this be part of the recent problems showing up with Intel dual core chips? good luck, Lee -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
* BandiPat <penguin0601@earthlink.net> [08-23-07 20:36]:
Do you remember what files you've installed or upgraded recently? Do you recall when was the last time you knew it was working correctly? I would try backtracing my steps of any recent actions to find the problem first. I think there is a history of those things done, but sorry don't remember where that file is located.
rpm -qa --last | head -20 will give the last 20 installed/updated rpms with date and time of change. -- Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://counter.li.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Thursday 2007-08-23 at 21:00 -0400, Patrick Shanahan wrote:
problem first. I think there is a history of those things done, but sorry don't remember where that file is located.
rpm -qa --last | head -20
will give the last 20 installed/updated rpms with date and time of change.
I use this: rpm -q -a --queryformat "%{INSTALLTIME}\t%{INSTALLTIME:day} \ %{BUILDTIME:day} %-30{NAME}\t%15{VERSION}-%-7{RELEASE} \ %25{PACKAGER}\n" | sort | less -S which is similar. I'll have to look up that --last option, seems interesting. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFGzsl9tTMYHG2NR9URAqpIAJ4ydRWkiGluaK5dOxdm1/xvn+mokgCfVYJd 1oJJglB7XsNtQU93icPApto= =ZKGr -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (4)
-
BandiPat -
Carlos E. R. -
Patrick Shanahan -
Rick Friedman