Fix identified per
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1508944/comments/21
Closing
** Changed in: linux (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
http
** Changed in: linux (Ubuntu)
Assignee: Rahul (rahulshantagiri) => (unassigned)
** Changed in: linux (Ubuntu)
Status: In Progress => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.l
This may be related to the ticket #1507150 (
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1507150 ) .
Both tickets have the following in common :
1. radeon.dpm=1
2. Radeon Mobile 3650
3. Lockup with dmesg that mentions 'stalling' and 'rings'
4. Both using open source radeon driver.
--
Y
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Rahul (rahulshantagiri)
** Changed in: linux (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.l
RE: previous comment - my cables are connected and screwed in tightly.
I often switch the monitors off when leaving at night. 99% of the time
the machine is left running and has no problems.
Sometimes, however, like again today, the X-Server HANGs !!
:
$ gdb /usr/bin/Xorg 1855
GNU gdb (GDB) 7.9
I encountered the same issue just a moment ago.The possible reason i
think is that the monitor was not connected to computer well while it
booted with no problem.This reason may lead to crash frequently.
--
You received this bug notification because you are a member of Kernel
Packages, which is s
It just happened again , with 3.13.0-46-lowlatency #79 &
1:7.7+1ubuntu8.1 :
Radeon CP lockup stall dmesg :
[393791.346730] radeon :01:00.0: GPU lockup CP stall for more than 1msec
[393791.346741] radeon :01:00.0: GPU lockup (waiting for 0x0004
last fence id 0x
That last comment was from last week - I still had it in my firefox
"Restore Session" and had not pressed "Post Comment" yet.
But it just happened again today - it looks like the frequency of this bug is
increasing with newer kernel, xorg-server, and
xorg-drivers-radeon releases .
Here is the
It just happened again, this time with latest 3.13.0-46-lowlatency kernel and
1:7.7+1ubuntu8.1 .
The messages are slightly different :
[78988.537888] radeon :01:00.0: GPU lockup CP stall for more than 1msec
[78988.537900] radeon :01:00.0: GPU lockup (waiting for 0x07e3579e
It just happened again, this time with latest 3.13.0-46-lowlatency kernel and
1:7.7+1ubuntu8.1 .
The messages are slightly different :
[78988.537888] radeon :01:00.0: GPU lockup CP stall for more than 1msec
[78988.537900] radeon :01:00.0: GPU lockup (waiting for 0x07e3579e
I've been seeing this problem also, abeit rather infrequently ( about once
every 1-2 months),
with all Ubuntu 14.04.1 kernels issued via updates since July 2014 .
This is on my machine at work which is left on all the time and only
reboots when a new kernel is installed .
Machine:
8 core Intel(
So I've tried the mainline kernel
kat@korat:~$ uname -a
Linux korat 3.19.0-031900rc4-generic #201501112135 SMP Sun Jan 11 21:36:48 UTC
2015 x86_64 x86_64 x86_64 GNU/Linux
On my laptop and tried all the steps before to try and reproduce the lockup.
MySQL workbench
Google Chrome
Fast switching bet
lshw of my development machine.
I'll test with my laptop with the mainline kernel later today.
** Attachment added: "lshw of g1dev"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1409393/+attachment/4297746/+files/lshw_g1dev.txt
--
You received this bug notification because you are a
lscpi -vvv of my development machine
** Attachment added: "lcpci -vvv"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1409393/+attachment/4297747/+files/lspci_g1dev-vvv.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux i
These GPU lockups are now happening on two machines of mine.
I tested the mainline kernel on my development machine and the problem
is worse not better.
kat@g1dev:~$ uname -a
Linux g1dev 3.19.0-031900rc4-generic #201501112135 SMP Sun Jan 11 21:36:48 UTC
2015 x86_64 x86_64 x86_64 GNU/Linux
On my
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.19 kernel[
16 matches
Mail list logo
