For what its worth, running 3.13.7 greatly mitigates this bug, to where
the dead time is barely noticeable. It happened three times in short
order here and I didn't notice any of them:
[ 4562.551141] [drm:ring_stuck] *ERROR* Kicking stuck semaphore on render ring
[ 4582.530028] [drm:ring_stuck] *
For what its worth, running 3.13.7 greatly mitigates this bug, to where
the dead time is barely noticeable. It happened three times in short
order here and I didn't notice any of them:
[ 4562.551141] [drm:ring_stuck] *ERROR* Kicking stuck semaphore on render ring
[ 4582.530028] [drm:ring_stuck] *
My stuck ring faults are completely gone with i915.i915_enable_rc6=0.
Fan stays on a bit more (subjectively) seems to be the only side effect.
HP Pavilion dv6 (Sandybridge).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
(In reply to comment #139)
> Oh that's interesting. We might be able to find a register to prevent rc6
> whilst waiting on a semaphore. (Hmm, too bad it isn't ivb or we could just
> frob forcewake directly.)
Happy to test patches. I'm updating to 3.13.9 tonight. I could add
something on top if y
My stuck ring faults are completely gone with i915.i915_enable_rc6=0.
Fan stays on a bit more (subjectively) seems to be the only side effect.
HP Pavilion dv6 (Sandybridge).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
(In reply to comment #139)
> Oh that's interesting. We might be able to find a register to prevent rc6
> whilst waiting on a semaphore. (Hmm, too bad it isn't ivb or we could just
> frob forcewake directly.)
Happy to test patches. I'm updating to 3.13.9 tonight. I could add
something on top if y
I helped my daughter install natty on her brand-new Asus K73E, which has
the Ra-Link RT5390. Wolfgang's suggestion in #11 was the jackpot.
For other's reference, I got her wireless working in three steps:
1) Installed kernel 3.0.0 from
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.0-oneiric/
dcam:
Please read the spec a little closer: "File Entry" as defined in 4/14.9
applies to "File Types" 0, and 4-10. Following the spec back to
4/14.6.6, you discover that file type #4 is a directory, and #5 is a
generic file. Types #6 through #10 are other well-understood *nixy
items.
In any ca
The mode and dmode options mentioned above by Jorge have been merged in
linux 2.6.30-rc as commits:
7ac9bcd5da59dd96eb1153d3fc04c3471fa5c09d
87bc730c07a0884d14d6af5c9d49f4669c0a0589
--
DVDs with restrictive permissions are unreadable for normal user
https://bugs.launchpad.net/bugs/10550
You rece
I cherry-picked those two commits into a fresh branch of v2.6.29. They
applied cleanly, and appear to work correctly. My fstab line now looks
like this:
/dev/cdrom /mnt/cdrom udf,iso9660
noauto,users,uid=0,gid=444,mode=0777,dmode=0777,nosuid,noexec 0 0
This combination will r/w mount any UDF di
I'm a recent upgrader from bionic to focal thanks to a new System76
laptop that came with 20.04 pre-installed. I've been moving my
netplan/dnsmasq configuration over to the new laptop and ran into this
bug (I use a networkd-dispatcher script to pass DNS to dnsmasq via
openresolv). I added a tempo
Any hope for this bug? A look at the corrupted json suggests that
networkd-dispatcher is assembling it by parsing log entries (?!?!?).
Something about my environment must be generating log entries that fit
the filters it is using but are normally not present (or many others
would be complaining).
12 matches
Mail list logo
