This also occurs with the mainline kernel version
4.6.0-040600rc6.201605012031.
As far as I can tell the dmesg output is identical, but I'm including it
below in case there's something useful in there.
[ 135.984685] [drm:btc_dpm_set_power_state [radeon]] *ERROR*
I tested the new kernel 4.2.0-35 and it works.
--
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/1549354
Title:
After upgrading to 4.2.0.30 Elantech touchpad not detected
Status in linux
As another user confirms on
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1554613 , the
flickering has disappeared on the latest drm-intel-next
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
If the underlying issue is the same then fine. I can confirm that the
resulting appearance of this current bug is very different than what the
video shows in 91393
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I reproduce the same bug (suspend shut the screen by computer is still
running) but its not related to radeon in my case since I have a nvidia
card with optimimus. Was working well on 15.10.
* i7 6700HQ
* NVIDIA GeForce GTX 950M
--
You received this bug notification because you are a member of
** Also affects: vlc (Ubuntu)
Importance: Undecided
Status: New
--
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/1574130
Title:
radeon GPU lockup when using VLC and Firefox
Public bug reported:
When playing a video with VLC and running Firefox at the same time, the
radeon driver consistently (reproducibly) locks up and crashes on my
machine since upgrading to 16.04. I'm using a Radeon HD 6870.
This does not happen with other video players (totem, mpv). Tested with
** Attachment added: "lspci-vnvn.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1574130/+attachment/4644799/+files/lspci-vnvn.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Is there anything else I can to help with this?
--
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/1549354
Title:
After upgrading to 4.2.0.30 Elantech touchpad not detected
Status in linux
(Raising from customer request.)
** Changed in: ubuntu-ux
Importance: Medium => High
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1511525
Title:
Can't transfer file using
I've been on 4.6.0-997-generic drm-intel-next for a day and can confirm
that the flickering is gone
--
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/1554613
Title:
screen flickering on
(In reply to Rodrigo Vivi from comment #32)
> Uhm interesting that even with i915.enable_dc=0 you Thomas are getting
> [ 17.788425] [drm:gen9_set_dc_state] Setting DC state from 00 to 02
>
> What firmware version do you have loaded?
> cat /sys/kernel/debug/dri/0/i915_dmc_info
(In reply to Peter Y. Chuang from comment #39)
> I'm not sure if this is kind of expected for this particular bug, but it
> seems that the problem doesn't happen when the laptop is plugged into the
> power.
Flickering happens with AC plugged here
--
You received this bug notification because
(In reply to Rodrigo Vivi from comment #30)
> RC6p/RC6pp split got deprecated few generations ago. So on Skylake RC6 is
> the deepest already.
>
> Thomas, do you confirm disabling RC6 the flickerings goes away for you as
> well?
with i915.enable_rc6=0 the flickering is gone.
(In reply to thomas bonfort from comment #35)
> (In reply to Rodrigo Vivi from comment #30)
> > RC6p/RC6pp split got deprecated few generations ago. So on Skylake RC6 is
> > the deepest already.
> >
> > Thomas, do you confirm disabling RC6 the flickerings go
Created attachment 122845
dmesg with enable_dc=0 disable_power_well=0 , up to first flicker
--
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/1554613
Title:
screen flickering on XPS13 9350
Good news: upgrading to latest VirtualBox seems to resolve the issue!
--
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/1567622
Title:
Kernel Oops - unable to handle kernel NULL pointer
Created attachment 122843
dmesg with drm.debug on 4.4.0-18 up until first flicker
--
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/1554613
Title:
screen flickering on XPS13 9350
Status
>what graphical environment you use
KDE plasma
>do you have an external monitor attached?
No
>Is there anything special that triggers the flickering? something like: "it
>starts flickering when having more than one monitor I try to move the cursor
>to the external one"
No special trigger. First
Created attachment 122844
Xorg.0.log
--
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/1554613
Title:
screen flickering on XPS13 9350
Status in Linux:
Incomplete
Status in linux package
The bug's status is NEEDINFO. Is there anything more you need from me?
--
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/1554613
Title:
screen flickering on XPS13 9350
Status in Linux:
I updated my Auquaris E.4.5 with OTA-10 today and tested with my Alpine
Car Audio.
After a little bit of a struggle (one crash of the bluetooth on the
phone and a phone reboot) it connects now and shows the phone symbols
(signal strength and battery) on the display of the car audio.
It also does
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Released
--
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/612300
Title:
gspca_sonixb doesn't work with Genius VideoCam Look
Possibly relevant: the issue does *not* occur if I run my VM with a
single core.
--
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/1567622
Title:
Kernel Oops - unable to handle kernel NULL
I should mention that I had the Virtualbox Kernel modules installed in
the two latter oops, but that uninstalling them (which is why they are
not in first oops) does not make a difference.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Public bug reported:
Running in Virtualbox as a guest in a Macbook Pro, I'm running into a
reliably-reproducible kernel oops on Ubuntu 16.04 with Linux
4.4.0-17-generic.
The stack trace isn't always the same, although the error always happens
in the same `update_blocked_averages` function.
could you quickly walk me through as to how to apply these please? I
know nothing about patchwork.
--
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/1554613
Title:
screen flickering on
OK, I'm applying them manually.
The 7th one is failing:
git apply -v /home/tbonfort-scratch/Downloads/7-8*
Checking patch drivers/gpu/drm/i915/i915_dma.c...
error: while searching for:
#include
#include
#include
static int i915_getparam(struct drm_device *dev, void *data,
error: patch
using 3-way:
/**
* i915_driver_init_mmio - setup device MMIO
* @dev_priv: device private
*
* Setup minimal device state necessary for MMIO accesses later in the
* initialization sequence. The setup here should avoid any other device-wide
* side effects or exposing the driver via kernel
Flickering still present on watermarks-wa
cp /boot/config-4.4.0-17-generic .config
make -j 4 deb-pkg INSTALL_MOD_STRIP=1
#answer default on everything except i915 debugging
booted using no specific enable_psr flags
$ dmesg|grep i915
[1.754871] [drm] Finished loading i915/skl_dmc_ver1.bin
booting with enable_psr=1 leads to same results:
$ dmesg|grep i915
[0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.6.0-rc2+
i915.enable_psr=1 root=UUID=432cb01b-c9c7-4cb0-8129-5c0abadbf9f8 ro quiet
splash vt.handoff=7
[0.00] Kernel command line:
Rodrigo,
sorry for being a noob here...: what remote should I add to get to that branch?
--
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/1554613
Title:
screen flickering on XPS13 9350
can you please advise as to the workflow I should be using to compile a
meaningfull kernel to test this, starting from the config used by
ubuntu?
this is what I'm inclined to do:
make mrproper
cp /boot/config-4.4.0-17-generic .config
make oldconfig
#reply to the questions to the best of my
On top of which SHA do you want me to apply these? Should I apply them
all or test the one by one ?
--
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/1554613
Title:
screen flickering on
enable_psr=2 still flickers with 4.4.0-16. unable to try latest 4.4.0-17
as X doesn't start with it.
dmesg|grep i915
[0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.4.0-16-generic
i915.enable_psr=2 i915_bpo.enable_psr=2
root=UUID=432cb01b-c9c7-4cb0-8129-5c0abadbf9f8 ro quiet splash
4.4.0-17 (which backports i915 from 4.6.0-rc1 IIUC) flickers with enable_psr =
0, 1 and 2.
My impression after a short test is that the flickering occurs more frequently
when set to 0 than 1 or 2.
--
You received this bug notification because you are a member of Kernel
Packages, which is
Rodrigo:
I have already tried reverting that commit (in ubuntu's mainline kernel, i.e.
in their backported i915_bpo module) but the flickering still occurs.
I may have messed up my bisect: from memory, b1a14c6e40413f8
78e0d2e3477aa3e8bdac a6d09186fa27dea7 ca1a95334ddaf624c1b0424 may have been
Timo: with -extra installed I can now boot up successfully. The
flickering still occurs with enable_psr=0, 1 and 2 . It seems to occur
more frequently when set to 0
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
dmesg of failed startup with 4.4.0-17
** Attachment added: "dmesg.4.4.0-17"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1554613/+attachment/4622561/+files/dmesg.4.4.0-17
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
with 4.4.0-16: flickers with or without i915.enable_psr=1 , and with or without
reverting rodrigo's commit found by bisection
with 4.4.0-17: X does not start , I'm left with a blank screen. happens with or
without i915.enable_psr
--
You received this bug notification because you are a member
failed X startup with 4.4.0-17. Let me know if you want more info.
** Attachment added: "Xorg.0.log.old"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1554613/+attachment/4622524/+files/Xorg.0.log.old
--
You received this bug notification because you are a member of Kernel
Packages,
No change with 4.6-rc1-wily for me
--
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/1554613
Title:
screen flickering on XPS13 9350
Status in Linux:
Unknown
Status in linux package in
For me, the flickering happens with or without AC. And First flicker
always ends up having the FIFO error message being printed.
--
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/1554613
Anmar: I have removed tlp and rebooted but the flickering still occurs.
--
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/1552304
Title:
screen flicker on Dell XPS 13 9350 after kernel
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
1.3.3
03/01/2016
** Tags removed: latest-bios-1.3.2
** Tags added: latest-bios-1.3.3
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Reverting the commit solves the problem. The 4.2.0-34 kernel without
that commit works.
--
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/1549354
Title:
After upgrading to 4.2.0.30
** Tags removed: latest-bios-1.2.3
** Tags added: latest-bios-1.3.2
--
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/1554613
Title:
screen flickering on XPS13 9350
Status in linux
Stille present with 4.4.0-16 , and after updating BIOS to latest 1.3.3
version
** Description changed:
see LP: #1552304
does not affect 4.4.0-8
- affects 4.4.0-9 to 4.4.0-13
+ affects 4.4.0-9 to 4.4.0-16
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-generic
upstream issue opened at :
https://bugs.freedesktop.org/show_bug.cgi?id=94593
** Bug watch added: freedesktop.org Bugzilla #94593
https://bugs.freedesktop.org/show_bug.cgi?id=94593
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
I confirm that commit 78e5e67b89eec214d2a035865d31184ff8f6490b works.
--
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/1549354
Title:
After upgrading to 4.2.0.30 Elantech touchpad not
This is the exact same hardware and flickering as in LP: #1554613
--
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/1561729
Title:
[drm:intel_cpu_fifo_underrun_irq_handler [i915_bpo]]
I confirm that commit 0c07e5375a1bccb9c3acaedfadeb16fb8dd75760 works.
--
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/1549354
Title:
After upgrading to 4.2.0.30 Elantech touchpad not
Commit 6f786b3b2e4c71f8d573d069411ec1a23c0b6bc3 does NOT work.
--
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/1549354
Title:
After upgrading to 4.2.0.30 Elantech touchpad not detected
I confirm that commit 3e8e33a682b8c83b6079684834b1d6654c541df5 works.
--
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/1549354
Title:
After upgrading to 4.2.0.30 Elantech touchpad not
As described in my previous comment, the fs was available in read-write
mode again.
I added another disk to the btrfs and with the additional space I was
able to rerun and successfully finish the btrfs balance operation (as
described in https://www.slicewise.net/debian/balancierung-eines-vollen-
I confirm that commit a7dbd2e3268627cedc6b10adc39b5e544a71655f works.
--
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/1549354
Title:
After upgrading to 4.2.0.30 Elantech touchpad not
I confirm that commit cc0a33f849da5571bd1cae03bde0ac59f9fe9a45 works.
--
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/1549354
Title:
After upgrading to 4.2.0.30 Elantech touchpad not
Commit 0f8e1864193330c04ce01ba9c9ee45e43e91f540 does NOT work.
--
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/1549354
Title:
After upgrading to 4.2.0.30 Elantech touchpad not detected
I rebooted the system in the meantime. It now had Kernel 4.2.0-30.36
from previous updates:
cat /proc/version_signature
Ubuntu 4.2.0-30.36~14.04.1-generic 4.2.8-ckt3
During the reboot, the system performed some disk I/O for several hours.
Before services like sshd became available. I guess this
It also works with commit d06fcd4940477fb1b0f52f23e7fe4d23d060c7fd
--
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/1549354
Title:
After upgrading to 4.2.0.30 Elantech touchpad not
Thanks for your quick reply :-)
I've downloaded the kernel you built: I confirm that it is working up to
commit ce0ef8e1f348a9ef7522429c1dd3295df131285e.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
@jsalisbury
What exactly should I test on a broken file system with a newer Kernel?
How could this help you? If btrfs balance corrupted my file system, how
should a newer kernel fix that?
If you can tell me test a scenario which will help you to see if the bug
is fixed upstream, I'd be happy to
** Tags removed: verification-needed-wily
** Tags added: verification-done-wily
--
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/1552592
Title:
KVM/QEMU live migration fails with Ubuntu
Checking the underlying mdraid with
echo check > /sys/block/md0/md/sync_action
now has finished and it is just fine:
cat /proc/mdstat
Personalities : [raid1] [linear] [multipath] [raid0] [raid6] [raid5] [raid4]
[raid10]
md0 : active raid1 sda3[0] sdb3[1]
2929833792 blocks super 1.2
Now, this one is funny after ~2 days:
# btrfs balance status x
Balance on 'x' is running
0 out of about 2797 chunks balanced (533 considered), 100% left
# btrfs balance cancel x
ERROR: balance cancel on 'x' failed - Read-only file system
So the balance is still running, consuming 100% of one
I was not able to identify a non-working mainline kernel. Therefore, I
do not know what to bisect.
Both mainline 4.2.0-040200 and 4.2.4-040204 which are the mainline
builds available for wily closest to 4.2.0-30 work.
I suspect, the bug is not present in the mainline kernel at all.
** Changed
cat /proc/mounts
sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0
udev /dev devtmpfs rw,relatime,size=8157548k,nr_inodes=2039387,mode=755 0 0
devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0
tmpfs /run tmpfs
I found a few entries in kern.log, nothing special during btrfs balance:
Mar 19 03:47:03 server kernel: [2970569.341605] BTRFS info (device dm-0):
relocating block group 9553211031552 flags 36
Mar 19 04:01:08 server kernel: [2971415.588391] BTRFS info (device dm-0):
relocating block group
Error messages in dmesg |tail are still ongoing, presumably originating
from the btrfs command which still is eating 100% of the cpu,
I did not reboot yet nor kill the btrfs process (pid 27516).
Here's two lines from two of the latest error messages in dmesg:
[3111643.576434] []
Something noticable: The command btrfs is consuming 100% of the cpu for
a long time:
# top
[...]
PID BENUTZER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND
27516 root 20 0 15476132 0 R 100,0 0,0 1348:33 btrfs
I assume that this process originates from my
Currently, I'm checking the md-raid (raid 1) with
echo check > /sys/block/md0/md/sync_action
I have 2 x 3.5TB hard drives, so this will take some while.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
The underlying md-raid (mirroring) is fine. So according to md-raid
status, there's nothing wrong with the mirrored partitions:
cat /proc/mdstat
Personalities : [raid1] [linear] [multipath] [raid0] [raid6] [raid5] [raid4]
[raid10]
md0 : active raid1 sda3[0] sdb3[1]
2929833792 blocks
Some relevant lines from /var/log/syslog:
Mar 19 19:15:10 server smartd[2251]: Device: /dev/sdb [SAT], SMART Usage
Attribute: 194 Temperature_Celsius changed from 107 to 106
Mar 19 07:59:21 server console-kit-daemon[2041]: GLib-CRITICAL: Source ID 376
was not found when attempting to remove it
related: https://www.mail-archive.com/linux-
bt...@vger.kernel.org/msg48609.html
--
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/1559723
Title:
soft lockup during btrfs balance
Status
# apt-cache policy btrfs-tools
btrfs-tools:
Installiert: 3.12-1ubuntu0.1
--
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/1559723
Title:
soft lockup during btrfs balance
I have # btrfs --version
Btrfs v3.12
Kernel is from Hardware enablement stack 14.04.4, Btrfs-tools from
ubuntu's package respectively.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Related: https://www.spinics.net/lists/linux-btrfs/msg48037.html
--
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/1559723
Title:
soft lockup during btrfs balance
Status in linux package
Related: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1349711
--
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/1559723
Title:
soft lockup during btrfs balance
Status in linux
For my setup, btrfs file system runs on top of a LUKS encrypted
partition which itself is on top of a mdraid (mirroring).
The Layout is:
# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:00 2,7T 0 disk
├─sda1 8:10
Note that some months ago (when I got the error message), I still was
able to cleanly free up some diskspace and perform a clean btrfs balance
(which freed a lot of space).
My hope was that I'd get an error message and exit cleanly if disk space
is missing. Instead, I got the soft lockup.
--
Public bug reported:
I performed a btrfs balance for a disk which ran out of space. When I
did this some months ago, I got an error message, but this time, I got a
soft lockup and the file system got mounted read-only:
# cat /proc/version_signature
Ubuntu 4.2.0-27.32~14.04.1-generic 4.2.8-ckt1
** Attachment added: "uname-a.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1559723/+attachment/4605660/+files/uname-a.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Attachment added: "lspci-vvnn.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1559723/+attachment/4605659/+files/lspci-vvnn.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
related: #1349711
--
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/1559723
Title:
soft lockup during btrfs balance
Status in linux package in Ubuntu:
New
Bug description:
I
introduced in LP: #1540390
--
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/1554613
Title:
screen flickering on XPS13 9350
Status in linux package in Ubuntu:
Confirmed
Bug
Christopher: OK sorry about that. The bisections just takes such a
sh***load of times it seems unfair/unreasonable to ask it to be done
again unless you're certain the cause is different.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Christopher: This issue is identified and awaiting on upstream for a fix; Why
waste your user's time by opening a new issue on LP or by asking for yet
another bisect? It is not going to make the fix come faster.
LP: #1540390
LP: #1554613
https://bugs.freedesktop.org/show_bug.cgi?id=94593
** Bug
4.5.0-040500 is still affected
** Tags removed: kernel-bug-exists-upstream-4.5-rc7
** Tags added: kernel-bug-exists-upstream-4.5
--
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/1554613
Reported as bug #1559580
--
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/1549354
Title:
After upgrading to 4.2.0.30 Elantech touchpad not detected
Status in linux package in Ubuntu:
I've installed and booted mainline 4.5.0-040500-generic #201603140130 as
per the instructions. With this kernel, the touchpad is recognized and
works.
** Tags added: kernel-fixed-upstream kernel-fixed-upstream-4.5
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You
After a couple of hours using 4.0.0.13 the flickering has re-appeared.
** Description changed:
see #1552304
does not affect 4.4.0-8
- affects 4.4.0-9 to 4.4.0-11
+ affects 4.4.0-9 to 4.4.0-13
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-generic 4.4.0.11.12
I have finished bisecting the commits and the switch from i915 to
i915_bpo seems to be the culprit. There are quite a few candidates but
that's because all those skipped commits failed to build/compile.
Note that on the first flicker after booting, this message appears in
dmesg:
** Description changed:
- see #1552304
+ see LP: #1552304
does not affect 4.4.0-8
affects 4.4.0-9 to 4.4.0-13
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-generic 4.4.0.11.12
ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
Uname: Linux
I believe that this backport is causing screen flickering problems on
Dell XPS13 9350, c.f. LP: #1554613 (where you'll find a bisect log
pointing to this backport, and dmesg msg on first error)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
4.5.0-997-generic #201603142201 from drm-intel-next still shows
flickering
--
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/1540390
Title:
Backport more recent driver for SKL, KBL and BXT
also present in 4.5.0-994-generic_4.5.0-994.201603152201 from drm-intel-
nightly
--
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/1554613
Title:
screen flickering on XPS13 9350
Status in
I've filed https://bugs.freedesktop.org/show_bug.cgi?id=94593 . After
bisecting the intel-drm-next branch I believe
921ec285a6589cf3beb7f56a70744f75b09349f8 to be the culprit.
** Bug watch added: freedesktop.org Bugzilla #94593
https://bugs.freedesktop.org/show_bug.cgi?id=94593
--
You
No, I haven’t looked at this yet. Please reprioritize if necessary.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1511525
Title:
Can't transfer file using bluetooth
Status in
I have tested 4.0.0-13 which does not seem to exhibit the flickering
present from 4.0.0-9 to 4.0.0-12. It does however now present tearing
artifacts when switching focus between windows, see
https://www.dropbox.com/s/opirfyzklathw3i/VID_20160316_112021.m4v?dl=0
for a screengrab.
--
You received
Christopher,
Yes I have read that section but it is not useful as selecting between bad/good
is already the required workflow. The issue is that the documentation refers to
using the packaging scripts in the debian/ subdir, which is not present and/or
usable in the intermediate bisecting steps.
701 - 800 of 1182 matches
Mail list logo
