노트북이 정지되는 이유를 알아내는 방법은 무엇입니까?

노트북이 정지되는 이유를 알아내는 방법은 무엇입니까?

새 노트북을 가지고 있는데 계속 멈춥니다.

$ uname -a
Linux bpgergo-notebook 4.2.0-27-generic #32-Ubuntu SMP Fri Jan 22 04:49:08 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 15.10
Release:    15.10
Codename:   wily

충돌과 관련된 상황이나 응용 프로그램을 지정할 수 없습니다. 사고 원인을 알고 싶습니다. 충돌이 발생했을 때의 모습과 시스템 로그에서 볼 수 있는 내용을 설명하겠습니다. 이유를 알아내기 위해 진행 방법을 알려주셨으면 합니다.

충돌했을 때의 모습

재부팅 후 1시간 이내에 정지되는 경우도 있고, 이틀 내에 정지되는 경우도 있습니다. 예를 들어 가장 최근에 정지가 발생했을 때 재부팅한 후 브라우저 및 터미널과 같은 일부 일반 응용 프로그램을 실행하고 한 시간 동안 그대로 두었다가 다시 돌아왔을 때 어떤 콘텐츠에도 응답하지 않는 것을 발견했습니다. . Alt+Ctl+F1을 누를 수도 없습니다. 이 시점에서 내가 할 수 있는 유일한 일은 전원이 꺼질 때까지 전원 버튼을 누르고 있는 것입니다.

동결이 발생하면 일반적으로 노트북이 예상보다 약간 따뜻하다는 것을 알게 됩니다. 바로 재부팅하고 확인해 보면 sensors70도 안팎의 온도를 볼 수 있는데, 이는 극단적인 수준은 아니지만 정상 작동 온도(50도 안팎)보다 훨씬 높은 수준이다.

시스템 로그

/var/log/syslog를 확인했는데 이것이 충돌이 발생하기 전에 찾은 최신 로그 줄입니다. chrash1:

Feb 10 15:01:39 bpgergo-notebook kernel: [26093.242080] nouveau E[   PIBUS][0000:01:00.0] HUB0: 0x6013d4 0xffff5703 (0x1c408200)
Feb 10 15:01:39 bpgergo-notebook kernel: [26093.242132] nouveau E[   PIBUS][0000:01:00.0] HUB0: 0x10ecc0 0xffffffff (0x1a40822c)
Feb 10 15:02:09 bpgergo-notebook kernel: [26123.130129] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150619/nsarguments-95)
Feb 10 15:02:09 bpgergo-notebook kernel: [26123.130403] ACPI: \_SB_.PCI0.PEG0.PEGP: failed to evaluate _DSM
Feb 10 15:02:09 bpgergo-notebook kernel: [26123.130407] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150619/nsarguments-95)
Feb 10 15:02:11 bpgergo-notebook kernel: [26124.445525] nouveau E[   PIBUS][0000:01:00.0] HUB0: 0x10ecc0 0xffffffff (0x1c40822c)

충돌 2

Feb 10 16:17:58 bpgergo-notebook kernel: [ 1088.808587] nouveau E[   PIBUS][0000:01:00.0] HUB0: 0x6013d4 0xffff5700 (0x1c408200)
Feb 10 16:18:23 bpgergo-notebook kernel: [ 1113.486503] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150619/nsarguments-95)
Feb 10 16:18:23 bpgergo-notebook kernel: [ 1113.487291] ACPI: \_SB_.PCI0.PEG0.PEGP: failed to evaluate _DSM
Feb 10 16:18:23 bpgergo-notebook kernel: [ 1113.487305] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150619/nsarguments-95)
Feb 10 16:18:26 bpgergo-notebook kernel: [ 1116.831356] nouveau E[    PBUS][0000:01:00.0] MMIO read of 0x00000000 FAULT at 0x122130 [ IBUS ]
Feb 10 16:18:26 bpgergo-notebook kernel: [ 1116.835021] nouveau E[   PIBUS][0000:01:00.0] HUB0: 0xbad00100 0xbadf1002 (0xbad00100)
Feb 10 16:18:26 bpgergo-notebook kernel: [ 1116.835247] nouveau E[   PIBUS][0000:01:00.0] ROP4: 0xbadf1100 0xbadf1100 (0xbadf1100)
Feb 10 16:18:26 bpgergo-notebook kernel: [ 1116.835252] nouveau E[   PIBUS][0000:01:00.0] ROP6: 0xbadf1100 0xbadf1100 (0xbadf1100)
Feb 10 16:18:26 bpgergo-notebook kernel: [ 1116.835257] nouveau E[   PIBUS][0000:01:00.0] ROP7: 0xbadf1100 0xbadf1100 (0xbadf1100)
Feb 10 16:18:26 bpgergo-notebook kernel: [ 1116.835262] nouveau E[   PIBUS][0000:01:00.0] ROP9: 0xbadf1100 0xbadf1100 (0xbadf1100)
Feb 10 16:18:26 bpgergo-notebook kernel: [ 1116.835267] nouveau E[   PIBUS][0000:01:00.0] ROP11: 0xbadf1100 0xbadf1100 (0xbadf1100)
Feb 10 16:18:26 bpgergo-notebook kernel: [ 1116.835271] nouveau E[   PIBUS][0000:01:00.0] ROP12: 0xbadf1100 0xbadf1100 (0xbadf1100)
Feb 10 16:18:26 bpgergo-notebook kernel: [ 1116.835276] nouveau E[   PIBUS][0000:01:00.0] ROP13: 0xbadf1100 0xbadf1100 (0xbadf1100)
Feb 10 16:18:26 bpgergo-notebook kernel: [ 1116.835281] nouveau E[   PIBUS][0000:01:00.0] ROP15: 0xbadf1100 0xbadf1100 (0xbadf1100)
Feb 10 16:18:26 bpgergo-notebook kernel: [ 1116.835286] nouveau E[   PIBUS][0000:01:00.0] GPC8: 0xbadf1100 0xbadf1100 (0xbadf1100)
Feb 10 16:18:26 bpgergo-notebook kernel: [ 1116.835293] nouveau E[   PIBUS][0000:01:00.0] GPC20: 0x000000 0x00000000 (0x00000000)
Feb 10 16:18:26 bpgergo-notebook kernel: [ 1116.835298] nouveau E[   PIBUS][0000:01:00.0] GPC22: 0xbadf1100 0xbadf1100 (0xbadf1100)
Feb 10 16:18:26 bpgergo-notebook kernel: [ 1116.835303] nouveau E[   PIBUS][0000:01:00.0] GPC23: 0xbadf1100 0xbadf1100 (0xbadf1100)
Feb 10 16:18:26 bpgergo-notebook kernel: [ 1116.835308] nouveau E[   PIBUS][0000:01:00.0] GPC25: 0xbadf1100 0xbadf1100 (0xbadf1100)
Feb 10 16:18:26 bpgergo-notebook kernel: [ 1116.835312] nouveau E[   PIBUS][0000:01:00.0] GPC27: 0xbadf1100 0xbadf1100 (0xbadf1100)
Feb 10 16:18:26 bpgergo-notebook kernel: [ 1116.854481] nouveau E[   PIBUS][0000:01:00.0] GPC28: 0xbad00100 0xbad00100 (0xbad00100)
Feb 10 16:18:26 bpgergo-notebook kernel: [ 1116.877204] nouveau E[   PIBUS][0000:01:00.0] GPC29: 0xbad00100 0xbad00100 (0xbad00100)
Feb 10 16:18:26 bpgergo-notebook kernel: [ 1116.900634] nouveau E[   PIBUS][0000:01:00.0] GPC31: 0xbad00100 0xbad00100 (0xbad00100)
Feb 10 16:18:26 bpgergo-notebook kernel: [ 1116.992570] nouveau E[    PBUS][0000:01:00.0] MMIO read of 0x00000000 FAULT at 0x120058 [ IBUS TIMEOUT ]
Feb 10 16:18:26 bpgergo-notebook kernel: [ 1117.072344] nouveau E[   PIBUS][0000:01:00.0] HUB0: 0xbad00100 0xbad00100 (0xbad00100)
Feb 10 16:18:26 bpgergo-notebook kernel: [ 1117.078887] nouveau E[   PIBUS][0000:01:00.0] ROP4: 0xbad00100 0xbadf1100 (0xbadf1100)
Feb 10 16:18:26 bpgergo-notebook kernel: [ 1117.078904] nouveau E[   PIBUS][0000:01:00.0] ROP6: 0xbadf1100 0xbadf1100 (0xbadf1100)
Feb 10 16:18:26 bpgergo-notebook kernel: [ 1117.078910] nouveau E[   PIBUS][0000:01:00.0] ROP7: 0xbadf1100 0xbadf1100 (0xbadf1100)
Feb 10 16:18:26 bpgergo-notebook kernel: [ 1117.078917] nouveau E[   PIBUS][0000:01:00.0] ROP9: 0xbadf1100 0xbadf1100 (0xbadf1100)
Feb 10 16:18:26 bpgergo-notebook kernel: [ 1117.078923] nouveau E[   PIBUS][0000:01:00.0] ROP11: 0xbadf1100 0xbadf1100 (0xbadf1100)
Feb 10 16:18:26 bpgergo-notebook kernel: [ 1117.078939] nouveau E[   PIBUS][0000:01:00.0] ROP12: 0xbadf1100 0xbadf1100 (0xbadf1100)
Feb 10 16:18:26 bpgergo-notebook kernel: [ 1117.078945] nouveau E[   PIBUS][0000:01:00.0] ROP13: 0xbadf1100 0xbadf1100 (0xbadf1100)
Feb 10 16:18:26 bpgergo-notebook kernel: [ 1117.078950] nouveau E[   PIBUS][0000:01:00.0] ROP15: 0xbadf1100 0xbadf1100 (0xbadf1100)
Feb 10 16:18:26 bpgergo-notebook kernel: [ 1117.078954] nouveau E[   PIBUS][0000:01:00.0] GPC8: 0xbadf1100 0xbadf1100 (0xbadf1100)
Feb 10 16:18:26 bpgergo-notebook kernel: [ 1117.078960] nouveau E[   PIBUS][0000:01:00.0] GPC20: 0x000000 0x00000000 (0x00000000)
Feb 10 16:18:26 bpgergo-notebook kernel: [ 1117.078964] nouveau E[   PIBUS][0000:01:00.0] GPC22: 0xbadf1100 0xbadf1100 (0xbadf1100)
Feb 10 16:18:26 bpgergo-notebook kernel: [ 1117.078968] nouveau E[   PIBUS][0000:01:00.0] GPC23: 0xbadf1100 0xbadf1100 (0xbadf1100)
Feb 10 16:18:26 bpgergo-notebook kernel: [ 1117.078971] nouveau E[   PIBUS][0000:01:00.0] GPC25: 0xbadf1100 0xbadf1100 (0xbadf1100)
Feb 10 16:18:26 bpgergo-notebook kernel: [ 1117.078975] nouveau E[   PIBUS][0000:01:00.0] GPC27: 0xbadf1100 0xbadf1100 (0xbadf1100)
Feb 10 16:18:26 bpgergo-notebook kernel: [ 1117.078978] nouveau E[   PIBUS][0000:01:00.0] GPC28: 0xbadf1100 0xbadf1100 (0xbadf1100)
Feb 10 16:18:26 bpgergo-notebook kernel: [ 1117.078982] nouveau E[   PIBUS][0000:01:00.0] GPC29: 0xbadf1100 0xbadf1100 (0xbadf1100)
Feb 10 16:18:26 bpgergo-notebook kernel: [ 1117.078987] nouveau E[   PIBUS][0000:01:00.0] GPC31: 0x000000 0x00000000 (0x00000000)
Feb 10 16:18:26 bpgergo-notebook kernel: [ 1117.078997] nouveau E[    PBUS][0000:01:00.0] MMIO read of 0x00000000 FAULT at 0x120058 [ IBUS TIMEOUT ]
Feb 10 16:18:26 bpgergo-notebook kernel: [ 1117.079008] nouveau E[   PIBUS][0000:01:00.0] HUB0: 0x136928 0xbadf1100 (0x19400200)
Feb 10 16:18:26 bpgergo-notebook kernel: [ 1117.079014] nouveau E[   PIBUS][0000:01:00.0] ROP0: 0x10f904 0xffffffff (0x1e408201)

답변1

그래서 내 질문에 대답하자면,

  1. 충돌이 발생하기 전에 어떤 프로그램이나 패키지가 시스템 로그의 마지막 몇 줄을 썼는지 확인하세요.
  2. 이 디렉터리도 확인해야 합니다./var/crash/

논평자들이 지적했듯이 nouveau는 오픈 소스 nvidia 드라이버입니다.

특정 문제와 관련하여 독점 nvidia 드라이버를 설치했는데 그 이후로 또 다른 충돌이 발생하지 않았습니다.

관련 정보