Booting up my machine after it has been off for the night resulted in one CPU core out of two not responding. I tried several attempts to boot my machine with one attempt also resulting in a kernel panic. The machine is running Jessie (devuanised). I am taking this as an omen of nearing hardware failure although in 2011 a bug was registered claiming a similar symptom.
Since many people on these fora work with computer hardware, I would very kindly ask their opinion regarding this issue.
Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230
[SOLVED] Again! CPU 1 not responding, cannot use it!
[SOLVED] Again! CPU 1 not responding, cannot use it!
Last edited by edbarx on 2017-01-29 11:38, edited 2 times in total.
Debian == { > 30, 000 packages }; Debian != systemd
The worst infection of all, is a false sense of security!
It is hard to get away from CLI tools.
The worst infection of all, is a false sense of security!
It is hard to get away from CLI tools.
-
deborah-and-ian
- Posts: 182
- Joined: 2016-07-13 08:40
Re: CPU 1 not responding, cannot use it!
I find it hard to believe that it could be software-related if you suddenly experience this (unless you're using testing or sid).
Debian GNU/Linux 9 Stretch w/Openbox
Acer Aspire E5-521G
AMD A8-6410 APU
4 GB RAM
integrated AMD Mullins
dedicated AMD Hainan Radeon R5 M240 2 GB
240 GB Toshiba Q300 SSD
Realtek RTL8111/8168/8411 ethernet
Qualcomm Atheros QCA9565 wireless
Acer Aspire E5-521G
AMD A8-6410 APU
4 GB RAM
integrated AMD Mullins
dedicated AMD Hainan Radeon R5 M240 2 GB
240 GB Toshiba Q300 SSD
Realtek RTL8111/8168/8411 ethernet
Qualcomm Atheros QCA9565 wireless
Re: CPU 1 not responding, cannot use it!
Have you tried booting it with a Debian live cd?
DebianStable
Code: Select all
$ vrms
No non-free or contrib packages installed on debian! rms would be proud.Re: CPU 1 not responding, cannot use it!
Post replaced as it was irrelevant: the problem repeated itself the day after (today). Comments are appreciated as this is the machine on which I code and graphics on the newer machine do not work well in Jessie. I am attributing the bad behaviour to the kernel. Maybe, a backported kernel has the issue resolved.
Debian == { > 30, 000 packages }; Debian != systemd
The worst infection of all, is a false sense of security!
It is hard to get away from CLI tools.
The worst infection of all, is a false sense of security!
It is hard to get away from CLI tools.
Re: CPU 1 not responding, cannot use it!
Added Later:edbarx wrote:Post replaced as it was irrelevant: the problem repeated itself the day after (today). Comments are appreciated as this is the machine on which I code and graphics on the newer machine do not work well in Jessie. I am attributing the bad behaviour to the kernel. Maybe, a backported kernel has the issue resolved.
I installed a kernel from backports, 4.8.0-0.bpo.2-amd64, something that I reluctantly do on Stable. As the failure is intermittent, damn those tiny integrated MOSFETS, I have to give it more time to conclude whether the problem has been resolved.
Debian == { > 30, 000 packages }; Debian != systemd
The worst infection of all, is a false sense of security!
It is hard to get away from CLI tools.
The worst infection of all, is a false sense of security!
It is hard to get away from CLI tools.
Re: Again! CPU 1 not responding, cannot use it!
Hey, Ed.
After all you have posted, I would personally start thinking about backing up all the data and take a good look at the machine itself. If the CPU itself isn't reaching breakdown point, it is at least reasonable to consider that the PSU might be.
After all you have posted, I would personally start thinking about backing up all the data and take a good look at the machine itself. If the CPU itself isn't reaching breakdown point, it is at least reasonable to consider that the PSU might be.
Stop hitting me with anvils!|Parem de me bater com bigornas!
Willie E. Coyote
Running Debian 9.2
Willie E. Coyote
Running Debian 9.2
Re: Again! CPU 1 not responding, cannot use it!
The error was reported by Devuan. I am assuming this is a kernel bug from 2011 that is still lurking around. That is why I upgraded the kernel. As I said, I will give it time. If the problems exhibits itself again and again, it will be a clear indication that there is a serious problem with the hardware. Sadly, it will be the end of life for this faithful machine that I bough a week before my late mother's departure. For this reason, the machine also has some rudimentary sentimental value to me.
Debian == { > 30, 000 packages }; Debian != systemd
The worst infection of all, is a false sense of security!
It is hard to get away from CLI tools.
The worst infection of all, is a false sense of security!
It is hard to get away from CLI tools.
Re: [SOLVED] Again! CPU 1 not responding, cannot use it!
The machine did not experience this error since I upgraded the kernel. 
Debian == { > 30, 000 packages }; Debian != systemd
The worst infection of all, is a false sense of security!
It is hard to get away from CLI tools.
The worst infection of all, is a false sense of security!
It is hard to get away from CLI tools.