kernel-packages team mailing list archive
-
kernel-packages team
-
Mailing list archive
-
Message #110946
[Bug 1438708] Re: frequent lockups asus g705js/GeForce GTX 870M
Relevant portion of syslog from a crash on Linux 3.17:
Apr 1 09:49:28 monster kernel: [ 10.722076] nouveau E[ PGRAPH][0000:01:00.0] HUB_INIT timed out
Apr 1 09:49:28 monster kernel: [ 10.722082] nouveau E[ PGRAPH][0000:01:00.0] 409000 - done 0x00000240
Apr 1 09:49:28 monster kernel: [ 10.722087] nouveau E[ PGRAPH][0000:01:00.0] 409000 - stat 0x00000000 0x00000000 0x00000000 0x00000000
Apr 1 09:49:28 monster kernel: [ 10.722091] nouveau E[ PGRAPH][0000:01:00.0] 409000 - stat 0x00000000 0x00000000 0x00000006 0x00000001
Apr 1 09:49:28 monster kernel: [ 10.722094] nouveau E[ PGRAPH][0000:01:00.0] 502000 - done 0x00000300
Apr 1 09:49:28 monster kernel: [ 10.722100] nouveau E[ PGRAPH][0000:01:00.0] 502000 - stat 0x00000000 0x00008c00 0x00000000 0x00000000
Apr 1 09:49:28 monster kernel: [ 10.722106] nouveau E[ PGRAPH][0000:01:00.0] 502000 - stat 0x00000000 0x00000000 0x00000000 0x00000000
Apr 1 09:49:28 monster kernel: [ 10.722108] nouveau E[ PGRAPH][0000:01:00.0] 50a000 - done 0x00000300
Apr 1 09:49:28 monster kernel: [ 10.722114] nouveau E[ PGRAPH][0000:01:00.0] 50a000 - stat 0x00000000 0x00000000 0x00000000 0x00000000
Apr 1 09:49:28 monster kernel: [ 10.722120] nouveau E[ PGRAPH][0000:01:00.0] 50a000 - stat 0x00000000 0x00000000 0x00000000 0x00000000
Apr 1 09:49:28 monster kernel: [ 10.722122] nouveau E[ PGRAPH][0000:01:00.0] 512000 - done 0x00000300
Apr 1 09:49:28 monster kernel: [ 10.722128] nouveau E[ PGRAPH][0000:01:00.0] 512000 - stat 0x00000000 0x00000000 0x00000000 0x00000000
Apr 1 09:49:28 monster kernel: [ 10.722134] nouveau E[ PGRAPH][0000:01:00.0] 512000 - stat 0x00000000 0x00000000 0x00000000 0x00000000
Apr 1 09:49:28 monster kernel: [ 10.722136] nouveau E[ PGRAPH][0000:01:00.0] 51a000 - done 0x00000300
Apr 1 09:49:28 monster kernel: [ 10.722142] nouveau E[ PGRAPH][0000:01:00.0] 51a000 - stat 0x00000000 0x00000000 0x00000000 0x00000000
Apr 1 09:49:28 monster kernel: [ 10.722148] nouveau E[ PGRAPH][0000:01:00.0] 51a000 - stat 0x00000000 0x00000000 0x00000000 0x00000000
Apr 1 09:49:28 monster kernel: [ 10.722149] nouveau E[ PGRAPH][0000:01:00.0] init failed, -16
Apr 1 09:49:32 monster NetworkManager[930]: <info> WiFi hardware radio set enabled
Apr 1 09:49:35 monster kernel: [ 17.847450] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20140724/nsarguments-95)
Apr 1 09:49:35 monster kernel: [ 17.847791] ACPI: \_SB_.PCI0.PEG0.PEGP: failed to evaluate _DSM
Apr 1 09:49:35 monster kernel: [ 17.847795] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20140724/nsarguments-95)
Apr 1 09:49:35 monster crontab[2536]: (root) LIST (root)
Apr 1 09:49:36 monster ntpd[2608]: ntpd 4.2.6p5@1.2349-o Fri Feb 6 15:24:12 UTC 2015 (1)
Apr 1 09:49:36 monster ntpd[2609]: proto: precision = 0.131 usec
Apr 1 09:49:36 monster ntpd[2609]: ntp_io: estimated max descriptors: 1024, initial socket boundary: 16
Apr 1 09:49:36 monster ntpd[2609]: unable to bind to wildcard address 0.0.0.0 - another process may be running - EXITING
Apr 1 09:49:36 monster puppet-agent[2071]: (/Stage[main]/Ntp::Service/Service[ntp]/ensure) ensure changed 'stopped' to 'running'
Apr 1 09:49:36 monster rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="760" x-info="http://www.rsyslog.com"] exiting on signal 15.
Apr 1 09:51:25 monster rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="895" x-info="http://www.rsyslog.com"] start
Apr 1 09:51:25 monster rsyslogd: rsyslogd's groupid changed to 104
Apr 1 09:51:25 monster rsyslogd: rsyslogd's userid changed to 101
-- at this point the system shows evidence of being rebooted --
Apr 1 09:51:25 monster kernel: [ 0.000000] Initializing cgroup subsys cpuset
Apr 1 09:51:25 monster kernel: [ 0.000000] Initializing cgroup subsys cpu
Apr 1 09:51:25 monster kernel: [ 0.000000] Initializing cgroup subsys cpuacct
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1438708
Title:
frequent lockups asus g705js/GeForce GTX 870M
Status in The Linux Kernel:
New
Status in linux package in Ubuntu:
Confirmed
Bug description:
Summary
=======
I think I am affected by this same bug, I have all the above systems and get hard lockups with Linux kernel 3.16 every 5 - 15 minutes.
Attempted upgrading to (x)ubuntu 14.10 to see if this improved
stability and laptop crashed so badly during the upgrade that it broke
grub and had to be recovered with ubuntu boot-repair. This alowed the
system to boot and I was able to complete configuration with dkpg
--configure -a --pending
System still crashes every few minutes when running (x)ubuntu 14.10
and about 50% of the time crashes before even reaching the login
screen. If I'm lucky attempting to swich VCs will resolve things but
the system always crashes eventually and has to be powered off by
holiding the power button for 10 seconds or via the magic sysreq key.
No other key cominations work.
Hardware
========
I also have an Asus laptop with an Nvida card which is what led me to this bug report, the following hardware is present:
* Laptop model Asus G750JS (ASUS-NotebookSKU)
* GK104M [GeForce GTX 870M]
* 4th Gen Core Processor Integrated Graphics Controller (i915 - not used)
* BCM4352 802.11ac Wireless Network Adapter
* QCA8171 Gigabit Ethernet
BIOS/DMI information
==================
I tried flashing the latest BIOS from (http://www.asus.com/Notebooks_Ultrabooks/ASUS_ROG_G750JS/HelpDesk_Download/) but it didn't fix anything.
Running the commands listed above gives:
$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
G750JS.208
07/17/2014
Driver info
========
This problem occurs with both the nouveau and nvidia drivers:
rc nvidia-331-updates 331.113-0ubuntu0.0.4 (removed by "additional drivers" application)
ii xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2
Workaround
==========
This configuration is rock solid on kernel 3.13. I was able to boot to a previously installed kernel (3.13.0-44-generic) and the system performs as expected and is stable.
Debug info
=========
The system has been generating a bunch of problem reports too so I've been clicking the submit button. Happy to rovide futher info or try a few experiments to get this resolved.
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: linux-image-3.16.0-33-generic 3.16.0-33.44
ProcVersionSignature: Ubuntu 3.16.0-33.44-generic 3.16.7-ckt7
Uname: Linux 3.16.0-33-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.14.7-0ubuntu8.2
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC1: geoff 3257 F.... pulseaudio
CurrentDesktop: XFCE
Date: Wed Apr 1 01:05:31 2015
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-09-23 (189 days ago)
InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2)
MachineType: ASUSTeK COMPUTER INC. G750JS
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-33-generic.efi.signed root=UUID=3fc94323-d40a-42ca-87c7-28a9e52ebcf4 ro recovery nomodeset
RelatedPackageVersions:
linux-restricted-modules-3.16.0-33-generic N/A
linux-backports-modules-3.16.0-33-generic N/A
linux-firmware 1.138.1
SourcePackage: linux
UpgradeStatus: Upgraded to utopic on 2015-03-29 (2 days ago)
dmi.bios.date: 07/17/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: G750JS.208
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: G750JS
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrG750JS.208:bd07/17/2014:svnASUSTeKCOMPUTERINC.:pnG750JS:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG750JS:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: G750JS
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1438708/+subscriptions
References