Created attachment 119042 [details] dmesg output Stuck occurs always when Google Chrome is running, but actual triggering time/action/environment is still not clear. It was tested even using another laptop of the same model and there it was the same problem. The screen turns black when it hangs. The system continues working in the background, I just ssh'd into the machine (as I'm remote) to collect evidence. - system architecture: x86_64 - kernel version: 3.13.0-61-generic - linux distribution: Ubuntu - machine: Lenovo T61 (6466-9MG) - display connector: panel connected via LVDS, VGA disconnected
18:17:30,10 root@ntb-006: ~ > lspci -d 8086:2a02 -vv 00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Lenovo ThinkPad T61/R61 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 48 Region 0: Memory at f8100000 (64-bit, non-prefetchable) [size=1M] Region 2: Memory at e0000000 (64-bit, prefetchable) [size=256M] Region 4: I/O ports at 1800 [size=8] Expansion ROM at <unassigned> [disabled] Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee0300c Data: 4182 Capabilities: [d0] Power Management version 3 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Bridge: PM- B3+ Kernel driver in use: i915 18:17:32,11 root@ntb-006: ~ >
Created attachment 119043 [details] GPU crash dump
We seem to have neglected this bug a bit, apologies. Is this still an issue with recent kernels?
Created attachment 123116 [details] dmesg output, kernel 3.13.0-85 crash snippet from dmesg
The problem still occurs for me in kernel 3.13.0-85 (lubuntu 14.04). Happens close to 100% of the time when trying to print from Google Chrome. latest dmesg output attached.
(In reply to Ian Gough from comment #5) > The problem still occurs for me in kernel 3.13.0-85 (lubuntu 14.04). > > Happens close to 100% of the time when trying to print from Google Chrome. > > latest dmesg output attached. Is this still an issue with *recent* kernels? Say, v4.5?
I can upgrade to lubuntu 16.04 this weekend which is based on v4.4. Would that be recent enough?
(In reply to Ian Gough from comment #7) > I can upgrade to lubuntu 16.04 this weekend which is based on v4.4. Would > that be recent enough? Since 4.4 is the new longterm support version, it would be sufficient to use it for this test. I myself am going to upgrade several workstations and laptops to 16.04, to see if the problem is gone with the newer software and later update the rest of the machines to 16.04 as well.
Since upgrading to Lubuntu 16.04 about 2 weeks ago, I have seen no more occurrences of this problem. Perhaps the original reporter can see if he has the same experience.
(In reply to Marc Kolly from comment #8) > (In reply to Ian Gough from comment #7) > > I can upgrade to lubuntu 16.04 this weekend which is based on v4.4. Would > > that be recent enough? > > Since 4.4 is the new longterm support version, it would be sufficient to use > it for this test. > > I myself am going to upgrade several workstations and laptops to 16.04, to > see if the problem is gone with the newer software and later update the rest > of the machines to 16.04 as well. Do you have any update, does issue is still occurring after that upgrade?
Since the upgrade to Ubuntu 16.04, I have not experienced this problem. Marc, since you raised the issue, have you seen this problem?
(In reply to Jani Nikula from comment #6) > (In reply to Ian Gough from comment #5) > > The problem still occurs for me in kernel 3.13.0-85 (lubuntu 14.04). > > > > Happens close to 100% of the time when trying to print from Google Chrome. > > > > latest dmesg output attached. > > Is this still an issue with *recent* kernels? Say, v4.5? It was not a kernel bug, but one in mesa.
Timeout. Assuming that it is fixed by now. If this is not the case, please re-test with latest kernel & Mesa (12-13) to see if this issue is still occurring since there were improvements pushed in kernel and Mesa that will benefit to your system.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.