Thanks. Looks like some other recent update fixed this again... I tried
to reproduce and couldn't any more (and as I said, it was happening
every time before).
I'll go ahead and close this.
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: New = Invalid
--
You received this bug
Public bug reported:
I have a lenovo T440p laptop (Intel Haswell integrated graphics + nvidia
GPU, I'm not using the nvidia at all). I have a docking station with a
single 2560x1440 displayport monitor attached, and I typically use my
laptop in the docking station with the lid closed (so I have
Public bug reported:
I have a Lenovo T440p laptop with a displayport monitor attached to the
docking station. If I turn on the laptop in the docking station, the
monitor works under the BIOS but once I get into Linux the monitor
doesn't light up. I see the following in kernel log (full logs
seems related to https://bugs.freedesktop.org/show_bug.cgi?id=71267
** Bug watch added: freedesktop.org Bugzilla #71267
https://bugs.freedesktop.org/show_bug.cgi?id=71267
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
Public bug reported:
Connected my Lenovo T410s to a 1080p TV via its Displayport output,
through a DP-HDMI dongle and to the TV's HDMI input. First I got a
black screen on both the internal LCD and the TV; after a reboot both
outputs lit up, and the TV worked at 1920x1080. However it looked
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1023691
Title:
[arrandale] False GPU lockup IPEHR: 0x0182
To manage notifications about this bug go to:
OK, here's a kernel log of me booting up and then going through the
dance to get my DP monitor lit up at the right resolution.
** Attachment added: graphics-dp3-trace.txt
OK, here's a kernel log of me booting up and then going through the
dance to get my DP monitor lit up at the right resolution.
** Attachment added: graphics-dp3-trace.txt
OK, here's a kernel log of me booting up and then going through the
dance to get my DP monitor lit up at the right resolution.
** Attachment added: graphics-dp3-trace.txt
Public bug reported:
Suspended while docked with external DP monitor, resumed while undocked
(only LVDS display)
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: xserver-xorg-video-intel 2:2.15.901-1ubuntu4
ProcVersionSignature: Ubuntu 3.2.0-8.14-generic 3.2.0
Uname: Linux 3.2.0-8-generic
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/914131
Title:
[arrandale] False GPU lockup render.IPEHR: 0x0182
To manage notifications about this bug go to:
BTW, was able to get to the text console, do a DISPLAY=:0 xrandr
--output LVDS1 --auto and hit alt-f1/alt-f7 a few times and get back to
a working X session.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
So xdiagnose doesn't work for me (I seem to hit bug #903484) but I added
drm.debug=0xe to my kernel command line by hand, and got the following
output.
This is not exactly the scenario described above -- I actually booted up at
home away from my dock, suspended the laptop, came to work, and
I get the same
sudo xdiagnose
Traceback (most recent call last):
File /usr/bin/xdiagnose, line 59, in module
app.run()
File /usr/lib/python2.7/dist-packages/xdiagnose/applet.py, line 337, in run
del cmdline_default_params['nopat']
KeyError: 'nopat'
but no nopat anything in grub.cfg
Actually the code in question is
if self.__disable_pat:
cmdline_default_params['nopat'] = None
else:
del cmdline_default_params['nopat']
and presumably __disable_pat is not set and cmdline_default_params
doesn't have a 'nopat' entry, so
Public bug reported:
I have a Lenovo t410s laptop (Arrandale graphics) that I use with a
docking station that is connected to an external monitor via
displayport. I just updated from Oneiric to the latest Precise daily,
and I've seen big regressions using this setup. I went into the display
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/912387
Title:
Intel graphics stack regression (oneiric-precise) with external
displayport monitor
To manage notifications
Actually, just went into the display control panel and I am able to get
the external monitor to light up now at 1024x768, but native 2560x1440
still fails.
Note that sometimes I am able to get the external monitor working at the
native resolution with precise -- but I don't know what the
OK, going into the display settings control panel and making sure the
laptop LVDS is _off_ and the DP is at native resolution worked. But if
I reboot there is a good chance the DP monitor won't come up and I'll
have to go through the whole dance of going to the console, running
DISPLAY=:0 xrandr
Also I see messages like
[ 5098.944951] [drm:drm_mode_getfb] *ERROR* invalid framebuffer id
which seem correlated as well.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
Public bug reported:
Problem seems to be related to the fact that I suspended my laptop while
it was docked and attached to an external monitor (displayport attached
to output DP3), and then undocked and resumed with the monitor
disconnected.
(By the way, in case it matters, with this laptop and
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/912134
Title:
[arrandale] GPU lockup render.IPEHR: 0x0184
To manage notifications about this bug go to:
Agreed. I have an Apple magic trackpad that I occasionally play with,
and this issue / design choice makes it pretty unusable with current
Unity. The multitouch gestures for moving windows are great and all,
but what's the substitute for highlight text with click and drag, and
then middle click
With linux-image-2.6.39-999-generic_2.6.39-999.201104201108_amd64.deb
docking/undocking seems to work pretty well. There is a bit of a delay
in switching, but even through a few cycles with unity running, I was
able to switch successfully between the internal LCD and the two
external monitors.
I
I don't think the elderberry stuff is related to my issue -- I see a
monitor stuck with no signal because (if I understood correctly) KMS got
confused and forgot about it. Probably fixing KMS would fix my
problems.
Is there some i915 tracing I could turn on to figure out what is confusing the
Bruce, thanks for all the info. I will do some more testing today.
One clarification though: when I get in the black screen + mouse pointer
situation, my machine is not hung. In fact the mouse pointer is still
responsive, I can log in via network, etc. It just that I lose the X
root
Bryce, first off, sorry for mistyping your name ;)
I did a bit more testing, and I tried the classic/no effects login
again. If I start undocked and dock, I do get the black
screen/responsive mouse pointer. However, if I log in with classic/no
effects *and* do xrandr --output LVDS1 --off and
I added that ppa and updated, and did a bit more testing. It seemed to
work a bit better, though not in the way I would have expected.
classic/no-effects: I started undocked, and actually got docking once to
work perfectly (both monitors lit up, desktop displayed on both).
However when I
I just noticed something while looking at my Xorg.0.log after a couple
of dock/undock cycles leading to the black screen. I'm attaching the
full log, but what I noticed was:
boot up undocked:
[ 5.897] (II) intel(0): Allocated new frame buffer 1472x900 stride 6144,
tiled
matches a 1440x900
OK, I got a chance to run intel_reg_dumper when the system is in the
following states:
- docked-good.txt : in the dock with unity working properly spanning two
external 1920x1080 monitors
- docked-bad.txt: in the dock with a black screen on the left monitor and the
right monitor off
-
** Attachment added: in the dock with one black screen
https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/745112/+attachment/2058075/+files/docked-bad.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in
** Attachment added: no dock, working properly
https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/745112/+attachment/2058076/+files/undocked-good.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
** Attachment added: out of the dock, screen black
https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/745112/+attachment/2058077/+files/undocked-bad.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in
correction: I said two 1920x1080 monitors but they are really 1920x1200
monitors.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/745112
Title:
[arrandale] desktop is messed
OK, with ia32-libs uninstalled:
$ dpkg --list|grep ia32
rc ia32-libs 20090808ubuntu11
ia32 shared libraries for use on amd64 and ia64 systems
I get roughly the same behavior. I started with the laptop docked, and
when I undocked it
Yes, I get similar issues when logging into a classic session and in
fact when the system is at the gdm screen before logging in. So I
reassigned to the intel driver, since this appears to be a generic X
problem.
** Project changed: unity = xserver-xorg-video-intel
** Package changed: unity
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/48413502/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/48413503/CurrentDmesg.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/48413504/Dependencies.txt
**
Public bug reported:
Binary package hint: xserver-xorg-video-intel
On my Lenovo X200 notebook (GM45 graphics), the backlight sometimes (not
always -- maybe one fifth of the time or so) stays off after a
suspend/resume cycle. In other words, the system resumes properly
except that the backlight
I'm trying today's Lucid daily (x86-64) inside a kvm guest running on a
Karmic host (started with testdrive), and if I pass -vga vmware to
kvm, then I also end up in low-graphics mode because the vmware X driver
doesn't work.
kvm/qemu is creating this PCI device:
00:02.0 VGA compatible
Applying the patch from
https://bugs.freedesktop.org/show_bug.cgi?id=24541#c6 and rebuilding
xserver-xorg-video-vmware in my Lucid guest fixed things for me.
Probably should be done for Lucid.
** Bug watch added: freedesktop.org Bugzilla #24541
I think I'm hitting this bug too -- I have a fancy new system (2 socket
nehalem xeon, radeon 4650) that I just installed the latest karmic daily
on, and it seems to behave the same way: boots fine to GDM screen, but
then logging into gnome crashes back to the GDM screen. xterm login
works fine.
With -intel version 2:2.7.99.901+git20090702.74227141-0ubuntu1 and
kernel 2.6.30-rc2, I've not seen any freezes or other issues, even
running compiz KMS.
--
[GM45] [karmic] X lockup on idle compiz/gnome desktop on X200
https://bugs.launchpad.net/bugs/394952
You received this bug notification
With -intel version 2:2.7.99.901+git20090702.74227141-0ubuntu1 and
kernel 2.6.30-rc2, I've not seen any freezes or other issues, even
running compiz KMS.
--
[GM45] Intel/X: Session freezes on login with compiz and KMS
https://bugs.launchpad.net/bugs/391220
You received this bug notification
Interesting -- I am running a self-built kernel (basically ubuntu karmic
kernel + latest Linus git as of yesterday) and suspend/resume is solid
for me; I haven't seen any X hangs related to suspend since updating to
2.6.31-rc1 (and I suspend from an X session running compiz). I am using
a Lenovo
OK, will try xserver-xorg-video-
intel_2.7.99.901+git20090702.74227141-0ubuntu1 (one heck of a version
number there :)
It may take a while to find out if the hangs are fixed, since they don't
happen that often and are not very reproducible.
--
[GM45] [karmic] X lockup on idle compiz/gnome
*** This bug is a duplicate of bug 389911 ***
https://bugs.launchpad.net/bugs/389911
Yes, does look like it.
** This bug has been marked a duplicate of bug 389911
kms: screen doesnt turn on resume from suspend
--
Lenovo X200 fails to resume from suspend
Public bug reported:
Binary package hint: xserver-xorg-video-intel
After the recent update on my Lenovo X200 laptop (with GM45 graphics) to
kernel 2.6.30-10, which enables KMS by default, when I log into my gnome
session, things freeze before any panel or other apps open; the pointer
does still
47 matches
Mail list logo
