I'll try and do that some time this week. Thanks Joseph.
Excerpts from Joseph Salisbury's message of 2016-12-13 20:01:45 UTC:
> This issue appears to be an upstream bug, since you tested the latest
> upstream kernel. Would it be possible for you to open an upstream bug
> report[0]? That will allow
I was able to play about 12 hours of the game without a crash. So things
definitely improved. But eventually it happened again.
[160126.986645] [drm] GPU HANG: ecode 8:0:0x85db, in Cities.x64 [23989],
reason: Hang on render ring, action: reset
[160126.986646] [drm] GPU hangs can indicate a bu
Excerpts from Joseph Salisbury's message of 2016-12-06 16:36:24 UTC:
> Can you also give the latest DRM nightly kernel a test? It is available from:
> http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-nightly/2016-12-06/
>
I'm installing it now. The crash is less frequent with 4.9 (have go
Launchpad must have changed since I last did this. It says the bug won't
be visible by you even though I subscribed you. Let me know if that
error file will help and I'll send it somewhere, but I'm concerned it
may have sensitive information from system RAM in it.
--
You received this bug notific
Hello!
This game never worked properly. I installed it and it had these hangs
starting immediately. It got better after I turned graphics detail _way_
down, but it still happens every 20 - 45 minutes of game play.
I installed the mainline build from today, and it did not help:
[ 103.860280] per
subair, Can you open a new bug with a full description of the problem
you are having, including the steps you took to get there so we can
reproduce? This one is pretty specific to booting the deploy ramdisk on
machines with less than 1GB of RAM.
THANKS!
** Changed in: diskimage-builder
Assig
Raring is EOL since January 27:
https://wiki.ubuntu.com/Releases
Excerpts from Alessandro Moscatelli's message of 2014-06-12 22:23:52 UTC:
> It looks I have this problem with Ubuntu Raring
> kernel version : 3.8.13
>
> I attached a screenshot with dmesg after I tried to start again my
> containe
FYI, I have experienced this again. It seems to only happen on resume
from suspend.
Excerpts from Joseph Salisbury's message of 2014-05-13 18:34:24 UTC:
> ** Changed in: linux (Ubuntu)
>Status: Triaged => Incomplete
>
> --
> You received this bug notification because you are subscribed t
Excerpts from Joseph Salisbury's message of 2014-04-23 18:46:43 UTC:
> Hmm, do you still have acpi_backlight=vendor? If not, I guess it would
> be good to test the 3.13.0-24-generic kernel for a while to ensure the
> bug doesn't come back.
>
I do not.
I wonder if it is also possible that I boot
Actually.. this is quite embarrassing, I installed 3.12, but my system
didn't show a grub menu and I actually booted 3.13.0-24-generic
Not sure how that happened, but it actually appears that the issue has
gone away somehow. Could still be a race maybe?
--
You received this bug notification beca
Backlight controls work flawlessly with 3.12 final.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1309584
Title:
[HP EliteBook Folio 9470m Notebook PC] Backlight does not work on
inte
Trying 3.12 now. Note that I discovered a new symptom today: when a
monitor is plugged into the DisplayPort, the brightness controls in
"Brightness and Lock" work, but the keyboard controls still don't work.
--
You received this bug notification because you are a member of Kernel
Packages, which
Tested with 3.15-rc2, backlight control still did not work.
** Tags added: kernel-bug-exists-upstream
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1309584
Title:
[HP EliteBook Folio 9
I just booted with acpi_backlight=vendor and that solves the issue.
Happy to help debug the issue to help other users of this hardware avoid
the problem.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchp
Seems this is a kernel/firmware/acpi issue.
** Package changed: xserver-xorg-video-intel (Ubuntu) => linux (Ubuntu)
** Summary changed:
- Backlight does not work on intel driver after upgrade from 13.10 -> 14.04
+ Backlight does not work on intel driver after upgrade from 13.10 -> 14.04,
acpi_b
Excerpts from Steve Langasek's message of 2014-01-22 16:51:06 UTC:
> On Wed, Jan 22, 2014 at 09:19:13AM -, Benny wrote:
> > Lennert of systemd refers to this bug on google+. He outlines a fix for
> > the simple case:
>
> The fix he outlines is not for this bug. It's not for a bug we have in
>
Excerpts from Bernd's message of 2014-01-05 21:37:21 UTC:
> due the respawn of some processes i think they are (re)started again even on
> shutdown
> so they are running if the / is remounted readonly
> and that is why it fails
>
> i think upstart should insure that all processes are killed (
Public bug reported:
Have done this before without fail. It was definitely exactly timed with
unplugging the USB cable from the computer. Will attach a picture I took
of the screen.
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: linux-image-3.11.0-13-generic 3.11.0-13.20
ProcVersionSignatu
Excerpts from Alexander's message of 2013-10-25 05:39:16 UTC:
> Guys, come on!
> What the heck network-manager and network connections are you talking about?!
> This really pissed me off already!
> As I've said earlier, the problem is NOT in network-manager!
> https://bugs.launchpad.net/ubuntu/+sou
Excerpts from Steve Dodd's message of 2013-10-21 16:16:29 UTC:
> That sounds plausible - I would guess wireless connections are usually torn
> down at the end of the user session (i.e. logout) whereas I assume wired
> connections persist right to system shutdown??
In theory they're brought down wh
20 matches
Mail list logo
