It didn't for me. I found the solution in bug #655001. Not sure if it's
the same problem.
--
Xorg freeze drm radeon 'Faild to schedule IB'
https://bugs.launchpad.net/bugs/588940
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-
Adding "nomodeset" in the option GRUB_CMDLINE_LINUX_DEFAULT of file
/etc/default/grub and issuing the command update-grub solved the issue
for me.
--
Xorg freeze drm radeon 'Faild to schedule IB'
https://bugs.launchpad.net/bugs/588940
You received this bug notification because you are a member of
Hey,
I had similar messages on a Thinkpad r51 in which I came back from
sleep. Things worked enough to have a mouse move around, to be able to
switch virtual terminals, even to login if I could guess where to click,
but none of the widgets would get drawn on X anymore.
I did not solve the bug in
Rob, it's better if you file a separate bug, since the original reporter
here is seeing the issue resolved now.
** Changed in: xserver-xorg-video-ati (Ubuntu)
Status: Confirmed => Fix Released
--
Xorg freeze drm radeon 'Faild to schedule IB'
https://bugs.launchpad.net/bugs/588940
You rece
Output of log:
Jun 28 12:54:44 rob-laptop kernel: [15348.456789] [drm:radeon_cs_ioctl] *ERROR*
Faild to schedule IB !
Jun 28 12:54:44 rob-laptop kernel: [15348.463706] [drm:radeon_ib_schedule]
*ERROR* radeon: couldn't schedule IB(1).
Jun 28 12:54:44 rob-laptop kernel: [15348.463709] [drm:radeon_
This bug is still ongoing. I notice it specifically when I am trying to
to adjust volume or switch quickly between audacity and volume control.
** Changed in: xserver-xorg-video-ati (Ubuntu)
Status: Fix Released => Confirmed
--
Xorg freeze drm radeon 'Faild to schedule IB'
https://bugs.la
Had enough running time now to consider the issue closed, my best guess
is that it must have been some kind of firmware issue that was fixed by
the newer linux-firmware package, since I seem to be the only one that
was affected, changing the status of the bug.
** Changed in: xserver-xorg-video-ati
I'm a little hesitant to say this is fixed until I get more running
time, but since the framebuffer and linux-firmware packages were updated
I switched X back to using the radeon driver, ran for a while with no
lock ups, took the 'nomodeset' option out of the boot up and am
currently running Gnome
"Have you tried booting with pci=nomsi ?"
Nothing in /proc/interupts made it look like msi was being used, but I
tried the 'pci=nomsi' thing anyway, no difference.
There is a difference with the 'nomodeset' in there, in that it takes
longer for there to be a problem, less likely to be hard locked
** Changed in: xserver-xorg-video-ati (Ubuntu)
Status: New => Confirmed
--
Xorg freeze drm radeon 'Faild to schedule IB'
https://bugs.launchpad.net/bugs/588940
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailin
** Package changed: xorg (Ubuntu) => xserver-xorg-video-ati (Ubuntu)
--
Xorg freeze drm radeon 'Faild to schedule IB'
https://bugs.launchpad.net/bugs/588940
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubu
Have you tried booting with pci=nomsi ?
--
Xorg freeze drm radeon 'Faild to schedule IB'
https://bugs.launchpad.net/bugs/588940
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
htt
I guess it should also be noted that I booted with some of my previously
installed kernels including linux-image-2.6.32-22-generic and the issue
is the same so it seems to be something in the mesa/xorg part of the
equation.
--
Xorg freeze drm radeon 'Faild to schedule IB'
https://bugs.launchpad.n
For other who might run into this even going into failsafe mode I had to
hit the 'E' key to edit the boot entry and add 'nomodeset' to the boot
options, then choose the 'root console' option off the failsafe menu,
then create the generic xorg.conf to specify vesa as the driver to use:
# Generic xo
** Attachment added: "system log since"
http://launchpadlibrarian.net/49576192/syslog
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/49575737/BootDmesg.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/49575738/Dependencies.txt
** Attachment
15 matches
Mail list logo
