11-04-2017, 11:35 PM
They say if you can't reproduce it, it's not a bug.
Well this is a bug. I was able to reproduce the problem in a Live Boot environment with just a few mouseclicks. Think that rules out a few things like user management, tweaks, updates or installed software, and possibly implicates hardware.
Problem computer is a a Toshiba Satellite C8558D that's 7..8 years old. I was unable to reproduce it on a newer HP machine following the same steps.
Steps to reproduce.
1. Boot from stick
2. Open Task Manager and observe stable low CPU usage.
3. Connect to a wireless Router and observe a few normal usage spikes followed by 50% idle CPU. Notice that this high usage remains stable.
4. Dis-connect the router and observe normal low CPU
5. Re-connect router and observe normal low CPU.
The last two steps can be repeated over and over. This strongly suggests the problem occurs only on the initial wireless connection. The initial connection can be made manually, as in the above scenario, or automatically on power-up boot as was my original issue.
So dunno, that's as far as I can go. It still feels like an ill behaved interrupt service routine. BIOS perhaps? ACPI mangling state transitions? Leave that for the next curious soul. Now I gotta figure out some kindof script to toggle the wireless.
And I leave this post hoping it may help some other wanderer down the path.
Jim
Well this is a bug. I was able to reproduce the problem in a Live Boot environment with just a few mouseclicks. Think that rules out a few things like user management, tweaks, updates or installed software, and possibly implicates hardware.
Problem computer is a a Toshiba Satellite C8558D that's 7..8 years old. I was unable to reproduce it on a newer HP machine following the same steps.
Steps to reproduce.
1. Boot from stick
2. Open Task Manager and observe stable low CPU usage.
3. Connect to a wireless Router and observe a few normal usage spikes followed by 50% idle CPU. Notice that this high usage remains stable.
4. Dis-connect the router and observe normal low CPU
5. Re-connect router and observe normal low CPU.
The last two steps can be repeated over and over. This strongly suggests the problem occurs only on the initial wireless connection. The initial connection can be made manually, as in the above scenario, or automatically on power-up boot as was my original issue.
So dunno, that's as far as I can go. It still feels like an ill behaved interrupt service routine. BIOS perhaps? ACPI mangling state transitions? Leave that for the next curious soul. Now I gotta figure out some kindof script to toggle the wireless.
And I leave this post hoping it may help some other wanderer down the path.
Jim
If not looking for things, I'm waiting for things.