My computer locks up during long idles - continued

Weeks ago I posted my problem here on this forum and was given much help, but no solution, so I tried my own experiment. First a little background. My computer would freeze every 3 days until I posted on here that it was every three days. As soon as I posted that, it changed to every day. I tried downgrading my video driver. That didn’t work. I tried downloading MemTest (I think that’s what it was called) from the OpenSuse repos, but it just locked up, so I downloaded the ISO and burned a DVD with the memtest direct from their website. That ran for a couple of days and after the third scan, I stopped it as it showed no errors, so my memory is fine. It was suggested that it might be BOINC or TeamViewer. So I disabled BOINC and uninstalled TeamViewer. That made no difference. Then it was suggested that I delete some KDE config files, but I didn’t want to try that before I did an experiment.

Now for my experiment: I decided to disable my internet during the idle times. That worked for a couple of days, but I made the mistake of announcing my plan here, because against my own advice, I ran a system update from OpenSuse and a couple of hours later my computer froze, but not only did it freeze, it damaged my hardware. I got banned from this forum until today because I was so upset, but now I’m back and it’s been weeks that I have run my experiment without running Opensuse updates and I have had no problems other than not being able to run my computer normally.

What I think is that someone has hacked into my computer causing these lockups and I will not accept any other explanation. What I ask is how do I catch/stop this hacker. Should I stop my experiment and run an Opensuse update? What should I do next? Thanks for listening!!!>:(

Hi
Since you believe it’s the operating system, then as a test wipe openSUSE and install another OS, and move on with that, I doubt the hundreds of openSUSE installs on many different hardware systems and never seen anything like this means nothing…

Tested your power supply? Leaky electrolytic capacitors (bulging tops) on the motherboard?

What I think is that someone has hacked into my computer causing these lockups and I will not accept any other explanation. What I ask is how do I catch/stop this hacker. Should I stop my experiment and run an Opensuse update? What should I do next? Thanks for listening!!!>:(

Maybe format the partitions, reinstall, and make the installation most secure.

Set the firewall to protect “external” and examine the Services that you are allowing (see firewall in Yast).
Also, have a look at this from the wiki: SUSE Security Lockdown - Hardening Your Linux System - openSUSE Wiki
And also there are significant tools in Yast to help you, go to Yast ==> Security & users ==> Security center and hardening.
Examine your logs frequently, it beats surmising.

I think a tool like wireshark would help me identify the software installed on my computer, but I am not good at sifting through the hours of data that will be collected before the computer locks up, but I guess I have no choice. What network scanning program do you recommend?

It’s been a few days since I implemented wireshark and no lockups. I wonder if the hacker is reading my posts and I must have hit on the correct tool to fight him/her. Internet has been up for days.:stuck_out_tongue: I still wonder if wireshark is the best tool. Why hasn’t anyone suggested anything? Please help…

They’re probably a little bit wary of the earlier altercations. Most folk just dodge that sort of interaction.

Now: did you try out any of the suggestions I made in post #3? You didn’t respond to that?

If I do any of your advice, I will run updates on OpenSUSE and it will install the hacker’s software and I will be right back to where I was. I neglected to say in this thread that I recently switched back to OpenSUSE from a previous OS, so you might say I did that already. Since I have to supply my root password it installs the hacker’s software during an update.

Since my last post, The hacker froze my computer again. So, I am searching the Wireshark log for clues. Still haven’t found the culprit’s IP or Port. I will work on it for a week or two before I give up. Is there anyone who can give me hints on how to search for the culprit’s IP or Port? Any help would be appreciated.

Thanks

No, not even close. If any of it were true we would all see this. I think you have a problem but I doubt it is a hacker. Most common is the video system. To be a hacker he would need to act as a man in the middle to effect uploads and they all are signed and thus a flag would be raised if changed en-route . Also unless you have the fire wall down nothing can really get through unless you run a Internet facing system that has a bug. Could be hardware thermal problems I guess but without more info we can’t really know. You would be better off looking at logs rather then searching through packets.

Not quite, but close.

I confiscated his laptop and now the little rascal is on house arrest for the next few days without dessert after dinner. Maybe we should not have named him “little bobby tables” for a start.

(SCNR)

AK

I did these suggestions: “Set the firewall to protect “external” and examine the Services that you are allowing (see firewall in Yast).”

I’m not allowing any service…

We’ll see what happens. Thanks for the advice.

The title of this thread is a clue.
“My computer locks up during long idles” Sounds like a memory leak to me. There is a program running in the background or maybe even foreground that is eating memory until it finally exhausts the free memory, then locks up. Just for grins let it idle for a long period and during that period run free to check memory usage and see if you are losing memory. You never know.

I already checked memory. It’s a long story but here goes. One of the suggestions before I was banned was to check memory. So, I downloaded MemTest (Or whatever it was called) from the opensuse repos, but it locked up without running the test, so I went to the MemTest website and burned a DVD, booted off of it, ran the memtest for three days during which it was on it’s third pass on a list of tests without any errors, so I stopped it. Waste of time to test mem again. Also, I went weeks without a problem by disabling my internet during idles, but when I turned the internet on full time, two days later it froze. I will not accept any explanation other than a hacker…

Do you have Screen energy savings and or suspend or screen locking on?? These kick in after a set time of not being used. Any of those not waking may indicate a video or other driver problem

Which desktop?? try a different one. Try a different user account may be a user config issue

Could it be a hacker. Maybe highly unlikely but could be but if you want any here to believe this and you seem to refuse any other explanation then you need to present some evidence and not just your suspicions.

Hi
Unfortunately you have yet to provide any ‘Physical’ evidence of such intrusions… it could be your graphics card, or your ethernet port failing, logs logs and logs and post the info and folks will try to help.

If you can’t provide info or don’t know what to provide, just ask…

But, if you think it’s a hacker, then I suggest you remove openSUSE and find another operating system to see if the same thing happens…

I tried using a different user and it didn’t lock up either. I guess there will be suggestions already made since my original post was deleted. I am using KDE and I hate GNOME, so not willing to try that since my disabling the internet during idles has completely stopped the lockups. No configs or memory are causing the lockups. I ran for weeks with the internet disabled during idles without any lock ups, os my configs, memory, cpu, motherboard, desktop, are all fine. It is a piece of software loaded onto my computer during an update from OpenSuse that as of yet I cannot identify. To repeat myself, I will not accept any explanation other than a hacker.

Hi
OK, unless you can provide proof of said hacking, then it is pure speculation and FUD and I’m guessing. will be repeating that until the cows come home.

These forums are for technical help, provide the information requested for some help, else the thread will be closed.

I asked for help to catch the hacker. That’s the technical help I need. I love Opensuse and have tried 7 other OS’s in the last year and came back to Opensuse because there is nothing better. How can I get the proof you need for showing you it’s a hacker. I am willing to provide proof, but I don’t know how to get it. Please help me. Please do not close this thread. I will repeat my self yet again, I spent weeks without a lockup with the Internet being down during idles, but when I changed the internet to be up full time, it locked up again. You imply that maybe it is my WIFI card that is causing the lock ups. Okay, how do I prove it’s the WIFI card? How do I find the software I believe is on my system that allows the hacker to lock up my computer?

There, two tech requests. Please don’t close this thread…

On Thu 16 Feb 2017 11:26:01 PM CST, trekjunky wrote:

I asked for help to catch the hacker. That’s the technical help I need.
I love Opensuse and have tried 7 other OS’s in the last year and came
back to Opensuse because there is nothing better. How can I get the
proof you need for showing you it’s a hacker. I am willing to provide
proof, but I don’t know how to get it. Please help me. Please do not
close this thread. I will repeat my self yet again, I spent weeks
without a lockup with the Internet being down during idles, but when I
changed the internet to be up full time, it locked up again. You imply
that maybe it is my WIFI card that is causing the lock ups. Okay, how do
I prove it’s the WIFI card? How do I find the software I believe is on
my system that allows the hacker to lock up my computer?

Hi
OK, so your using wireless exclusively? No ethernet?

  1. Your connecting to your own wireless router, not a public or shared
    system?

  2. Provide as root user the output from the following two commands (use
    code tags when pasting the info);


hwinfo --netcard

  1. So, with the ‘lockup’ your whole system freezes or just the desktop
    (as in GUI)? Or you just don’t get internet access?

  2. Have you tried after a lockup to press ctrl+alt+del+F1 key to get a
    console session?


Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
openSUSE Leap 42.1|GNOME 3.16.2|4.1.36-44-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!

I really think you have hardware issues
a hard drive with bad sectors, bad ram chip, bad vram chip or an overheating cpu or gpu will cause said symptoms
if you think you’re being hacked (for testing purposes) create a new user with a new password and use that account, unless the ‘hacker’ knows the root password he shouldn’t be able to get to the new account
afiak the opensuse firewall blocks all unrequested incoming connections you could try going off line for a day or two or
if you think the install has been compromised you could try running a live system for a few days (you could burn the iso to a dvd and be sure that no hacker could modify that OS as it will be read only)
there is a a live tw image or try the live variation of leap ie opensuse li-f-e or even try ubuntu
https://en.opensuse.org/openSUSE:Education-Li-f-e
https://en.opensuse.org/openSUSE:Tumbleweed_installation

Yes, I use wireless exclusively as the WIFI router is on a different floor in my house. No ethernet.

  1. The router was provided by my ISP for the sole purpose of use by this household.

  2. Below is the results from those commands:

hwinfo --netcard
32: PCI 200.0: 0200 Ethernet controller                          
  [Created at pci.378]
  Unique ID: rBUF.1WVRdh9En64
  Parent ID: 8otl.om932x2mw06
  SysFS ID: /devices/pci0000:00/0000:00:04.0/0000:02:00.0
  SysFS BusID: 0000:02:00.0
  Hardware Class: network
  Model: "Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller"
  Vendor: pci 0x10ec "Realtek Semiconductor Co., Ltd."
  Device: pci 0x8168 "RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller"
  SubVendor: pci 0x1043 "ASUSTeK Computer Inc."
  SubDevice: pci 0x8505 "P8 series motherboard"
  Revision: 0x09
  Driver: "r8169"
  Driver Modules: "r8169"
  Device File: eth0
  I/O Ports: 0xd000-0xdfff (rw)
  Memory Range: 0xfa104000-0xfa104fff (ro,non-prefetchable)
  Memory Range: 0xfa100000-0xfa103fff (ro,non-prefetchable)
  IRQ: 37 (no events)
  HW Address: 40:16:7e:b3:f1:d1
  Permanent HW Address: 40:16:7e:b3:f1:d1
  Link detected: no
  Module Alias: "pci:v000010ECd00008168sv00001043sd00008505bc02sc00i00"
  Driver Info #0:
    Driver Status: r8169 is active
    Driver Activation Cmd: "modprobe r8169"
  Config Status: cfg=no, avail=yes, need=no, active=unknown
  Attached to: #9 (PCI bridge)

34: PCI 400.0: 0282 WLAN controller
  [Created at pci.378]
  Unique ID: y9sn.f5QlA0lzJS1
  Parent ID: WL76.sQx2zCXa1Z7
  SysFS ID: /devices/pci0000:00/0000:00:09.0/0000:04:00.0
  SysFS BusID: 0000:04:00.0
  Hardware Class: network
  Model: "Realtek RTL8192CE PCIe Wireless Network Adapter"
  Vendor: pci 0x10ec "Realtek Semiconductor Co., Ltd."
  Device: pci 0x8178 "RTL8192CE PCIe Wireless Network Adapter"
  SubVendor: pci 0x1043 "ASUSTeK Computer Inc."
  SubDevice: pci 0x85e3  
  Revision: 0x01
  Driver: "rtl8192ce"
  Driver Modules: "rtl8192ce"
  Device File: wlan0
  Features: WLAN
  I/O Ports: 0xc000-0xcfff (rw)
  Memory Range: 0xfe100000-0xfe103fff (rw,non-prefetchable)
  IRQ: 38 (9563457 events)
  HW Address: 34:97:f6:64:ca:20
  Permanent HW Address: 34:97:f6:64:ca:20
  Link detected: yes
  WLAN channels: 1 2 3 4 5 6 7 8 9 10 11 12 13
  WLAN frequencies: 2.412 2.417 2.422 2.427 2.432 2.437 2.442 2.447 2.452 2.457 2.462 2.467 2.472
  WLAN encryption modes: WEP40 WEP104 TKIP CCMP
  WLAN authentication modes: open sharedkey wpa-psk wpa-eap
  Module Alias: "pci:v000010ECd00008178sv00001043sd000085E3bc02sc80i00"
  Driver Info #0:
    Driver Status: rtl8192ce is active
    Driver Activation Cmd: "modprobe rtl8192ce"
  Config Status: cfg=no, avail=yes, need=no, active=unknown
  Attached to: #11 (PCI bridge)

  1. The whole system locks up as my running logs end at the time it locks up.
  2. I tried Ctrl+Alt+F1(through 7) and no response from the computer

Thanks for your prompt advice!!!