Public bug reported:
On my X1 Yoga Titanium (which has a fancy new "Sensel" trackpad with
haptic response to clicks), the trackpad stops working after a
suspend/resume cycle, although the red trackpoint continues to work fine
for controlling the pointer. I believe this system is using S0i3 for
Public bug reported:
I have a 7th gen Lenovo X1 Carbon with Ubuntu up-to-date on 21.04, and
fwupdmgr shows:
$ fwupdmgr update
Devices with no available firmware updates:
• UEFI Device Firmware
• UEFI Device Firmware
• UEFI Device Firmware
• UEFI dbx
Devices with the latest available
I've come up with a theory that I think matches what I observe. It
seems that my laptop gets into the bad state if I suspend too quickly
after hot unplug from thunderbolt. If I wait long enough after hot
unplug that all the thunderbolt devices are fully removed, then the
system remains fine. If
No BIOS options changed. I am on X1 Yoga 2nd gen - the BIOS exposes S3
by default. X1 Yoga 3rd gen is the first Lenovo generation that
defaults to S0i3 for suspend.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I see from https://pcsupport.lenovo.com/us/en/downloads/DS506115 that
there is a firmware update available for my dock. I am going to try and
borrow a windows system and perform that update.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
No, unfortunately I am on the latest BIOS. dmidecode reports
BIOS Information
Vendor: LENOVO
Version: N1NET45W (1.32 )
Release Date: 03/11/2019
and https://pcsupport.lenovo.com/us/en/products/laptops-and-
** Attachment added: "lspci after reconnection to thunderbolt dock -
non-working"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825395/+attachment/5258316/+files/post-replug-lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
I can boot either connected or not, and the first connection will
usually work. I'd say my more common workflow is to boot away from my
dock, use my laptop for a bit, suspend, and go to my desk and resume
while docked. That usually works, but if I then undock, use my laptop
for a bit, suspend,
** Attachment added: "dmesg from boot to reproduction of the thunderbolt issue"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825395/+attachment/5258312/+files/post-replug-dmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Attachment added: "lspci after unplug from thunderbolt dock"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825395/+attachment/5258315/+files/post-unplug-lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "lspci while connected to working thunderbolt dock"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825395/+attachment/5258314/+files/post-suspend-lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Attachment added: "lspci before laptop is docked"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825395/+attachment/5258313/+files/pre-suspend-lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Attaching dmesg showing failed thunderbolt attachment. There is a good
hotplug starting with
[35304.659358] thunderbolt 0-1: new device found, vendor=0x108 device=0x1630
[35304.659361] thunderbolt 0-1: Lenovo ThinkPad Thunderbolt 3 Dock
for example, you can see that the system discovers the
So I can confirm that this bug happens with upstream build
5.1.0-050100rc5-generic. Will attach full dmesg.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1825395
Title:
thunderbolt / PCIe hotplug
I will try the upstream kernel, although it will be a few days before I
can confidently report if the issue is not present.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1825395
Title:
thunderbolt
Public bug reported:
I have a Lenovo X1 Yoga 2nd gen along with the Lenovo thunderbolt
docking station. Initial connection to the dock works great, but after
a few plug/unplug and suspend/resume cycles, the system gets in a state
where a reboot is needed to make the dock work. The displayport
Public bug reported:
Not doing anything in particular other than using wifi on my laptop.
ProblemType: KernelOops
DistroRelease: Ubuntu 18.10
Package: linux-image-4.17.0-7-generic 4.17.0-7.8
ProcVersionSignature: Ubuntu 4.17.0-7.8-generic 4.17.12
Uname: Linux 4.17.0-7-generic x86_64
Annotation:
Public bug reported:
This seems related to LP: #1717995 but that is marked fixed.
I used my laptop at work, where I have a docking station with USB
ethernet included (interface enx0050b6cf4d4a). The dhcp on the wired
ethernet includes my work domain, purestorage.com. I undocked,
suspended, and
Great, let me know if you want me to try anything out.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1717995
Title:
extra domains not removed from resolv.conf when VPN disconnects
To manage
$ systemd-resolve webvpn.purestorage.com
webvpn.purestorage.com: resolve call failed: No appropriate name servers or
networks for name found
$ systemd-resolve --status
Global
DNS Domain: home.digitalvampire.org
purestorage.com
I wonder if the issue has anything to do with the fact that the VPN
creates a new network link that disappears when the VPN goes down - note
that the purestorage.com domains are listed for tun0 when the VPN is up.
When I turn off the VPN, tun0 disappears but the purestorage.com domains
stay in the
Public bug reported:
I use a VPN (network manager "vpnc" config) to connect to my work
network. The gateway is "webvpn.purestorage.com". When I connect, I
get "purestorage.com" added to the "search" line in my /etc/resolv.conf
(and /run/resolvconf/interface/systemd-resolved) - which makes
Public bug reported:
This is upstream bug https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67707
with a fix already in upstream gcc.
The following program:
#include
#include
#include
#include
template
struct my_allocator: public std::allocator
{
typedef size_t size_type;
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've found that the version of evince in 14.04 has perhaps become too
strict and won't open PDF files that work in other readers. For example
with the SPC-4 SCSI spec available from http://www.t10.org/cgi-
bin/ac.pl?t=ff=spc4r36q.pdf , I get:
$ evince spc4r36q.pdf
Syntax
** Bug watch added: freedesktop.org Bugzilla #75232
https://bugs.freedesktop.org/show_bug.cgi?id=75232
** Also affects: evince via
https://bugs.freedesktop.org/show_bug.cgi?id=75232
Importance: Unknown
Status: Unknown
** Project changed: evince = poppler
** No longer affects:
Is MST actually required for 4K / 60Hz monitors, or is HBR2 / DP 1.2
sufficient? (My understanding is that Intel Linux drivers already
support HBR2)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Actually I was wrong about lspci working with the upstream kernel. It
looks like I got lucky once, but the next time I tried it with upstream
3.13-rc8 the system hung just like it does with the Ubuntu kernel.
So the upstream kernel behavior looks to be pretty much the same as the
Ubuntu kernel.
I tried this with the latest upstream kernel (3.13-rc8) plus the patch
https://bugs.freedesktop.org/attachment.cgi?id=91164 to Intel graphics
displayport handling (needed to make my monitor connected to my docking
station work). If I get rid of the blacklist nouveau with this
kernel, suspend is
Public bug reported:
I have a new Lenovo T440p laptop, which has a Haswell CPU and NVidia GPU
in an optimus setup. In a default 14.04 install, the system is quite
flaky: suspend doesn't work and doing lspci apparently corrupts memory
(the system hits random weird failures and then freezes about
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
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Seems to be related to resume problems turning on the video outputg
ProblemType: KernelOops
DistroRelease: Ubuntu 13.10
Package: linux-image-3.10.0-6-generic 3.10.0-6.17
ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3
Uname: Linux 3.10.0-6-generic x86_64
Annotation:
affecting me on a system upgraded from raring around saucy-alpha1.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1197395
Title:
/run/user/$ID/pulse owned by root and not by the user
To manage
Public bug reported:
might be relevant that I suspended undocked and then resumed docked.
ProblemType: KernelOops
DistroRelease: Ubuntu 13.10
Package: linux-image-3.10.0-3-generic 3.10.0-3.12
ProcVersionSignature: Ubuntu 3.10.0-3.12-generic 3.10.1
Uname: Linux 3.10.0-3-generic x86_64
Annotation:
Public bug reported:
I use my laptop in two setups: by itself with its 1440x900 built-in
panel, and docked/closed using an external 2560x1440 monitor only. (So
only one active screen in both cases) I use multiple unity workspaces,
with (for example) a maximized browser window in the top right
I hit this bug by connecting a USB headset and trying to select its
microphone as my sound input device in the sound settings dialog. I
tried Conor's suggestion in comment #6 and indeed that edit to the
config file fixes things for me -- I am able to select the USB headset
microphone and sound
FWIW, my pactl list output is the following. The Plantronics device
is the USB headset I mentioned.
Module #0
Name: module-device-restore
Argument:
Usage counter: n/a
Properties:
module.author = Lennart Poettering
Public bug reported:
Looks like a missing dependency or an incompatibility with new
devscripts:
$ requestsync
Traceback (most recent call last):
File /usr/bin/requestsync, line 36, in module
from ubuntutools.config import UDTConfig, ubu_email
File
The new versions of the build-dependencies libibumad-dev, libibmad-dev
and libopensm-dev are all built and published in raring-proposed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1087380
Title:
The new versions of the build-dependencies libibumad-dev and libopensm-
dev are all built and published in raring-proposed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1087379
Title:
Sync ibutils
The libibumad-dev build dependency is now fully built and in raring-
proposed, so opensm can be sponsored.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1087374
Title:
Sync opensm 3.3.15-2
The new libibumad-dev build dependency (due to syncing libibumad from
Debian experimenal) is now fully built and in raring-proposed, so
libibmad can be sponsored.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
is architecture independent.
-- Roland Dreier r...@debian.org Tue, 27 Nov 2012 12:28:22 -0800
opensm (3.3.15-1) experimental; urgency=low
* Acknowledge NMU.
* Update to debhelper 9 and minimized rule file.
* Source is in format 3.0. (Closes: #664434)
* Remove opensm-boot initscripts.
-- Roland
is in format 3.0. (Closes: #664435)
* I'm officially part of the packaging team now.
-- Roland Dreier r...@debian.org Mon, 19 Nov 2012 12:03:53 -0800
libibumad (1.3.8-0.2) experimental; urgency=low
* Non-maintainer upload.
* Update to debhelper 9 and minimized rule file.
-- Roland Dreier r
The version of libibumad in Ubuntu is extremely outdated. The new
version is needed to allow a new version of opensm (separate sync
request filed for that), which is needed to enable new hardware
features.
This exact packaging is built for precise and quantal in my ppa:
) experimental; urgency=low
* Acknowledge NMU. (Closes: #690602)
* Convert to minimized rules file.
-- Roland Dreier r...@debian.org Mon, 03 Dec 2012 11:44:59 -0800
infiniband-diags (1.6.1-0.1) experimental; urgency=low
* Non-maintainer upload.
* Acknowledge NMU.
* New upstream release
* Acknowledge NMU. (Closes: #690603)
* Convert to minimized rules file.
-- Roland Dreier r...@debian.org Mon, 03 Dec 2012 11:45:32 -0800
ibutils (1.5.7-0.1) experimental; urgency=low
* Non-maintainer upload.
* Acknowledge NMU.
* New upstream release.
* Bump Standards-Version to 3.9.4
* Acknowledge NMU. (Closes: #690601)
* Update to debhelper 9 and minimized rule file.
-- Roland Dreier r...@debian.org Tue, 27 Nov 2012 12:01:36 -0800
libibmad (1.3.9-0.1) experimental; urgency=low
* Non-maintainer upload.
* Acknowledge NMU.
* New upstream release.
* Bump Standards
And the fix is to update to a new libmlx4 version, which is already in
12.10 / Quantal. I'm not sure if there's anything that can be done in
the context of continuing maintenance to 12.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I'm pretty sure things have gotten worse for me since updating precise
- quantal. I used to be able to build kernels with -j2, and since the
update, I get thermal shutdowns sometimes even running a single-threaded
(ie no -j) build.
Maybe this is just coincidence and my fan has gotten more
Public bug reported:
Since I've updated to Quantal, I notice that if I kick off a long-
running compile on my laptop (eg building a whole kernel), then I often
shutdown with messages like
Jul 27 15:07:25 roland-t410s kernel: [145070.016141] CPU0: Core temperature
above threshold, cpu clock
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1030156
Title:
long-running compile leads to laptop overheat shutdown
To manage notifications about this bug go to:
Yes, 3.5.0-6.6 is fine, just like upstream 3.5.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1026964
Title:
Lenovo T410s laptop suspends fine, won't resume any more
To manage notifications about
Looks like this was fixed upstream by 3e997130bd2e (timekeeping: Add
missing update call in timekeeping_resume()) in 3.5 final. I built 3.5
from source and suspend/resume seems good again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
This is a weird one, but...
I have a Lenovo T410s laptop, that I've run every release from 11.04 to
current 12.10 development code on. Suspend/resume has pretty much
always worked, except apparently with the latest Quantal kernel there is
a regression. The computer
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1026964
Title:
Lenovo T410s laptop suspends fine, won't resume any more
To manage notifications about this bug go to:
Huh, the mere act of installing the mainline 3.5.0-rc7 kernel seems to
have stopped this from happening ... I reproduced it a few times in a
row but now it is back to working fine. I'll reopen and reinvestigate
if it happens again.
** Changed in: linux (Ubuntu)
Status: New = Invalid
--
Happened again just now. It appears if I suspend and then resume within
30 seconds or so, I'm ok. If I suspend and leave the system for a
while, it may refuse to wake up.
I'm running the 3.5.0-030500rc7-generic mainline kernel now, will let
you know if I see this again or not.
** Changed in:
This happened to me with mainline:
Linux roland-t410s 3.5.0-030500rc7-generic #201207142035 SMP Sun Jul 15
00:35:57 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
so looks like a mainline regression.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
OK, here's the output of
sudo gdb --args /usr/sbin/NetworkManager --no-daemon --log-level=debug
| tee nm.gdb.txt
looks like we crash in the dns management code because priv-last_iface
is NULL. I haven't tried to understand what NM is doing here yet.
** Attachment added: debug log / backtrace
** Changed in: network-manager (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1025498
Title:
network-manager segfaulting after bringing up Wi-Fi link
Public bug reported:
On my system after updating today, I see network manager bring up my
wifi link and then immediately start reconnecting.
In my dmesg, I see many sequences of messages like
[ 2027.559748] NetworkManager[7265]: segfault at 0 ip 7f03d9939f7d sp
7fff1f62cbb0 error 4 in
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1025498
Title:
network-manager crashing after bringing up wifi
To manage notifications about this bug go 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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1023691
Title:
[arrandale] False GPU lockup IPEHR: 0x0182
To manage notifications about this bug go to:
FWIW, the fix is now upstream as
e35fca4791fcdd43dc1fd769797df40c562ab491 (in 3.5-rc4) and tagged for
stable.
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
** Tags removed: kernel-bug-exists-upstream
** Tags added: kernel-fixed-upstream
--
You received this bug
FWIW, I added a debug print to Tombstone.vala right before the assertion
that fails:
bool is_removed = file_map.unset(tombstone.get_file());
if (!is_removed)
debug(is_removed == false for %s,
tombstone.get_name());
FWIW, I added a debug print to Tombstone.vala right before the assertion
that fails:
bool is_removed = file_map.unset(tombstone.get_file());
if (!is_removed)
debug(is_removed == false for %s,
tombstone.get_name());
So I added the following to the insert side of that
Tombstone.vala:notify_contents_altered() function:
if (file_map.has_key(tombstone.get_file()))
debug(already have file for %s!,
tombstone.get_name());
and now in the log I see
L 6394 2012-06-28 01:57:38
I did
$ echo .dump | sqlite3 ~/.shotwell/data/photo.db | grep
IMG_6016_CR2_shotwell.jpg
INSERT INTO TombstoneTable
VALUES(862,'/home/roland/Pictures/CanonT1i-images/2012/06/05/IMG_6016_CR2_shotwell.jpg',4635334,NULL,1340417401,0);
INSERT INTO TombstoneTable
Not a problem... here's the log
** Attachment added: shotwell.log
https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1016859/+attachment/3205712/+files/shotwell.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
And here's the gdb backtrace. Unfortunately Ubuntu seems to strip
everything from shotwell so I'm not sure how useful this is...
** Attachment added: shotwell.gdb
https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1016859/+attachment/3205713/+files/shotwell.gdb
--
You received this
Public bug reported:
I've been using shotwell for a while on a 12.04 system, and now when I
start it up, it shows the window for a second or two and then crashes
with
**
ERROR:/build/buildd/shotwell-0.12.3/src/Tombstone.vala:38:tombstone_source_collection_real_notify_contents_altered:
assertion
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1016859
Title:
shotwell crashes on startup
To manage notifications about this bug go to:
FWIW, even
$ shotwell --no-runtime-monitoring --no-startup-progress
**
ERROR:/build/buildd/shotwell-0.12.3/src/Tombstone.vala:38:tombstone_source_collection_real_notify_contents_altered:
assertion failed: (_tmp29_)
Aborted (core dumped)
hits the same crash.
--
You received this bug
Yes, this bug still exists upstream. You can look at the lkml.org link
I posted -- there is agreement that my patch is correct (it is identical
to the one Chen Gong sent earlier) and that the edac maintainer will
merge it, but that has not happened yet.
** Tags removed: needs-upstream-testing
**
Public bug reported:
I was lucky enough to get a 4-socket Sandy Bridge (Xeon E5-4600 series)
box, but unfortunately the default install of 12.04 hangs during boot
while loading the sb_edac module. This is due to a bug in
drivers/edac/sb_edac.c, as of now not yet fixed in upstream. However I
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1007061
Title:
12.04 kernel hangs during boot (loading sb_edac) on 4-socket Sandy
Bridge
To manage notifications about this bug go to:
Public bug reported:
After my latest update (which pulled in all the Unity 5.8 packages),
when I log in to my normal Unity session, I never get a launcher or top
menu bar. I see errors about baddrawable in my X log (which I hope is
attached).
ProblemType: Bug
DistroRelease: Ubuntu 12.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/964977
Title:
desktop session doesn't start with unity 5.8 on intel graphics
To manage notifications about this bug go to:
Public bug reported:
After my latest update (which pulled in all the Unity 5.8 packages),
when I log in to my normal Unity session, I never get a launcher or top
menu bar. I see errors about baddrawable in my X log (which I hope is
attached).
ProblemType: Bug
DistroRelease: Ubuntu 12.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/964979
Title:
desktop session doesn't start with unity 5.8 on intel graphics
To manage notifications about this bug go to:
Thanks Leann. I'm running:
$ uname -a
Linux roland-t410s 3.2.0-13-generic #22+fdo44881v1 SMP Fri Feb 3 05:42:29 UTC
2012 x86_64 x86_64 x86_64 GNU/Linux
and I can confirm that the problem appears to be resolved. I rebooted
with my DP monitor connected, logged in, and came up in the native
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
Bugs, which is subscribed to 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
Bugs, which is subscribed to 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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/912387
Title:
Intel graphics stack regression (oneiric-precise) with external
displayport monitor
To manage notifications about this bug go to:
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
Public bug reported:
Using the latest default precise kernel on my Lenovo T410s laptop with
Intel integrated graphics ends up with a bunch of messages like
[ 98.467011] DRHD: handling fault status reg 2
[ 98.467014] DMAR:[DMA Write] Request device [00:02.0] fault addr 40002
[
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/912405
Title:
arrandale/5 series intel graphics on lenovo t410s requires
intel_iommu=igfx_off with precise/3.2 kernel
To manage notifications about
1 - 100 of 444 matches
Mail list logo
