| 2017-11-03 16:44:08 |
Daeld |
description |
Hi, not sure if this is the best place to file this bug report and I couldn't find any other similar.
System: Dell XPS 15 laptop late 2017, 32GB ram, 1TB SSD, 7th Gen i7 quad-core 8-thread, etc
OS: Fresh install Ubuntu 17.10; dual boot with windows 10 pro on AHCI
Bug: Total system freeze with certain commands
Always reproduced with lspci | grep network (ie I typed it with n instead of N)
also always reproduced with any other use of lspci | grep <any other parameter that is not found>
Often reproduced with lspci | grep Network (correctly spelled)
and occasionally reproduced with just lspci on its own.
when it doesn't freeze the system, it takes it about 2 or 3 seconds to respond (whereas on my old ASUS 8GB ram, dual core quad thread i5 3rd gen it works instantly; same on my ubuntu server running on a crappy headless HP pavillion tower)
Also happens when using lshw, esp with lshw -C <some parameter>.
It does not matter how long the system has been running.
At the same time, it will let me run crunch together with aircrack-ng when pen testing my home lab without any problems even though all 8 threads are maxed out to 100% and I can still use the system as if nothing else is happening. Also, running lspci and lshw on a virtualbox install of Kali 2017.2 will work instantly as expected without any problems.
Any suggestions or request of more info would be welcome.
Thanks |
Hi, not sure if this is the best place to file this bug report and I couldn't find any other similar.
System: Dell XPS 15 laptop late 2017, 32GB ram, 1TB SSD, 7th Gen i7 quad-core 8-thread, etc
OS: Fresh install Ubuntu 17.10; dual boot with windows 10 pro on AHCI
Bug: Total system freeze with certain commands
Always reproduced with lspci | grep network (ie I typed it with n instead of N)
also always reproduced with any other use of lspci | grep <any other parameter that is not found>
Often reproduced with lspci | grep Network (correctly spelled)
and occasionally reproduced with just lspci on its own.
when it doesn't freeze the system, it takes it about 2 or 3 seconds to respond (whereas on my old ASUS 8GB ram, dual core quad thread i5 3rd gen it works instantly; same on my ubuntu server running on a crappy headless HP pavillion tower)
Also happens when using lshw, esp with lshw -C <some parameter>.
It does not matter how long the system has been running.
At the same time, it will let me run crunch together with aircrack-ng when pen testing my home lab without any problems even though all 8 threads are maxed out to 100% and I can still use the system as if nothing else is happening. Also, running lspci and lshw on a virtualbox install of Kali 2017.2 will work instantly as expected without any problems.
Any suggestions or request of more info would be welcome.
Thanks |
|
