Bug 1528708 - lshw stop laptop
Summary: lshw stop laptop
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: lshw
Version: 27
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Terje Røsten
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-12-22 22:02 UTC by sokotar
Modified: 2018-01-01 12:10 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-01-01 12:10:32 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
lspci, just before the laptop dies (1.92 KB, text/plain)
2017-12-22 22:02 UTC, sokotar
no flags Details

Description sokotar 2017-12-22 22:02:03 UTC
Created attachment 1371447 [details]
lspci, just before the laptop dies

Description of problem:
1/ when i start lshw program to control hardware, no result is showed, and the laptop stop.
2/ i use lshw, because lspci also stops laptop.
3/ i want to control hardware, because laptop does not poweroff when shutdown.

Version-Release number of selected component (if applicable):


How reproducible:
start lshw

Steps to Reproduce:
1.start lshw
2.
3.

Actual results:
wait for result, but nothing appears
after few seconds the laptop stop without message

Expected results:
show hardware configuration

Additional info:
- Laptop ASUS N705UD-GC084T
- BIOS 3.01
- kernel 4.14.6-300.fc27.x86_64
- plasma kde environment

with lspci, the result is quite the same . the result appears then the first procesor get 100%, after the 2sd get 100%, after the 3td get 100%, after the 4td get 100%, and then nothing more.

when i activate the shutdown, all processes are killed, the screen get black, but no the laptop does not poweroff.

Comment 1 sokotar 2018-01-01 12:09:53 UTC
adding nouveau.modeset=0 in grub.cfg, i have no more problems whith : 
1/ lspci , who does not stop the laptop
2/ lshw
3/ shutdown does power off the laptop


Note You need to log in before you can comment on or make changes to this bug.