Now I'm on
linux-image-4.18.0-14-generic 4.18.0-14.15
(without btusb.enable_autosuspend=0) and it's broken again.
--
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/1796553
Tit
Public bug reported:
I removed an old, not currently booted kernel:
apt-get purge linux-image-4.4.0-135-generic
linux-image-extra-4.4.0-135-generic
Paketlisten werden gelesen … Fertig
Abhängigkeitsbaum wird aufgebaut.
Statusinformationen werden eingelesen. … Fertig
Die folgenden Pakete
Still the same 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/1796553
Title:
BT mouse getting reset during operation
Status in Linux:
Unknown
Status in linux package in Ubuntu:
hildeb@humbaba:~$ ls -lihsa /lib/firmware/intel/
total 16M
3801225 12K drwxr-xr-x 2 root root 12K Sep 29 20:24 .
3801094 40K drwxr-xr-x 85 root root 36K Sep 29 20:25 ..
38171590 lrwxrwxrwx 1 root root 21 Aug 6 20:26 dsp_fw_bxtn.bin ->
dsp_fw_bxtn_v3366.bin
3814817 496K -rw-r--r-- 1 r
btusb.enable_autosuspend=0 seems to have worked (so far)...
--
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/1796553
Title:
BT mouse getting reset during operation
Status in Linux:
Unkn
btusb.enable_autosuspend=0 definitely made the issue go away.
--
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/1796553
Title:
BT mouse getting reset during operation
Status in Linux:
U
Public bug reported:
(note: It's unclear to me if that's a kernel regression or an issue with bluez)
I've been using this particular combination of Bluetooth mouse ("TECKNET
BM306") & laptop ("Dell Latitude E7240") for over a year now.
It used to work with 18.04 and 17.10, but with 18.10 I'm
It's definitely NOT happening while supending/resuming.
It happens while I'm using the machine, literally while moving the mouse.
--
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/1796553
Tit
Bluetooth adapter is builtin. so I can't change the port.
--
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/1796553
Title:
BT mouse getting reset during operation
Status in linux package i
My next step is to test the upstream kernels, I guess?
--
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/1796553
Title:
BT mouse getting reset during operation
Status in linux package in U
Tested:
$ uname -a
Linux humbaba 4.19.0-041900rc7-generic #201810071631 SMP Sun Oct 7 16:33:10 UTC
2018 x86_64 x86_64 x86_64 GNU/Linux
and the error is still there.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Tags added: kernel-bug-exists-upstream
--
You received
I cloned the repo and copied the new firmware to the appropriate place.
Testing now.
--
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/1796553
Title:
BT mouse getting reset during operation
Testing the kernel from https://people.canonical.com/~khfeng/lp1796553/
without btusb.enable_autosuspend=0
--
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/1796553
Title:
BT mouse gettin
After a few days of testing (work, suspend, resume, work) it seem to
work OK with the new kernel.
--
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/1796553
Title:
BT mouse getting reset dur
Public bug reported:
I spend the better part of a day debugging this.
Symptom: Outgoing connections (ssh, tcp to port 80, to port 8080) fail
to establish about 25% of my attempts.
I then switched the kernel from
linux-image-4.10.0-20-generic (zesty)
back to
linux-image-4.8.0-49-generic (yakkety
I was able to pinpoint which upstream kernel introduces the breakage:
last good kernel: v4.9.25 (a8c90ef62281db933118aa84489eb0e1e9cc347c)
first bad kernel: v4.10-rc1 (7ce7d89f48834cefece7804d38fc5d85382edf77)
--
You received this bug notification because you are a member of Kernel
Packages, whi
I was able to pinpoint which more recent upstream kernel fixes the
breakage:
last bad kernel: v4.11-rc5 (a71c9a1c779f2499fb2afc0553e543f18aff6edf)
first good kernel: v4.11-rc6 (39da7c509acff13fc8cb12ec1bb20337c988ed36)
--
You received this bug notification because you are a member of Kernel
Pa
[1.967522] e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
[1.967523] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
[1.967685] e1000e :00:19.0: Interrupt Throttling Rate (ints/sec) set to
dynamic conservative mode
[2.063252] e1000e :00:19.0 :00:19.0 (uninitiali
Just asking, is the bisect something I need to do? Should we bisect
between v4.11-rc5 and v4.11-rc6?
--
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/1686636
Title:
outgoing tcp connection
test that kernel and report back if it has the bug or not?
This kernel is working OK! No problems.
--
Ralf Hildebrandt Charite Universitätsmedizin Berlin
ralf.hildebra...@charite.deCampus Benjamin Franklin
https://www.charite.de Hindenburgdamm 30, 12203 Berli
test that kernel and report back if it has the bug or not? I
> will build the next test kernel based on your test results.
That kernel is also working OK!
It does NOT have the bug.
--
Ralf Hildebrandt Charite Universitätsmedizin Berlin
ralf.hildebra...@charite.deCampus
* Joseph Salisbury :
> I built the next test kernel, up to the following commit:
> b768b16de58d5e0b1d7c3f936825b25327ced20c
>
> The test kernel can be downloaded from:
> http://kernel.ubuntu.com/~jsalisbury/lp1686636/b768b16de58d5e0b1d7c3f936825b25327ced20c
>
> Can you test that kernel and report
test that kernel and report back if it has the bug or not? I
> will build the next test kernel based on your test results.
This kernel HAS the bug!
Linux vsw-it-nw-10 4.11.0-041100rc3-generic #201705041331 SMP Thu May 4
17:37:08 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
--
Ralf Hildebrandt
* Joseph Salisbury :
> The test kernel can be downloaded from:
> http://kernel.ubuntu.com/~jsalisbury/lp1686636/a80db69e47d764bbcaf2fec54b1f308925e7c490
>
> Can you test that kernel and report back if it has the bug or not? I
> will build the next test kernel based on your test results.
This ker
5e6bc84d
>
> Can you test that kernel and report back if it has the bug or not? I
> will build the next test kernel based on your test results.
This kernel is working OK!
Linux vsw-it-nw-10 4.11.0-041100rc3-generic #201705151753 SMP Mon May 15
21:57:15 UTC 2017 x86_64 x86_64 x86_64 G
test that kernel and report back if it has the bug or not? I
> will build the next test kernel based on your test results.
Kernel is working OK.
Linux vsw-it-nw-10 4.11.0-041100rc3-generic #201705161235 SMP Tue May 16
16:37:55 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
--
Ralf Hildebrandt
test that kernel and report back if it has the bug or not? I
> will build the next test kernel based on your test results.
Linux vsw-it-nw-10 4.11.0-041100rc3-generic #201705170654 SMP Wed May 17
10:57:24 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
has the bug!
--
Ralf Hildebrandt
has the bug or not? I
> will build the next test kernel based on your test results.
Linux vsw-it-nw-10 4.11.0-041100rc3-generic #201705181210 SMP Thu May 18
16:13:25 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
Kernel is working OK!
--
Ralf Hildebrandt Charite Universitätsmedi
ee if this kernel resolves the bug? With this test kernel, you need
> to install both the linux-image and linux-image-extra .deb packages.
Linux vsw-it-nw-10 4.10.0-21-generic #23~lp1686636 SMP Fri May 19 17:59:12 UTC
2017 x86_64 x86_64 x86_64 GNU/Linux
is working OK and does NOT expose th
Which version would that be? Currently, my system has:
ii linux-image-4.10.0-21-generic 4.10.0-21.23
amd64Linux kernel image for version 4.10.0
on 64 bit x86 SMP
ii linux-image-4.10.0-22-generic
ii linux-image-4.10.0-22-generic
4.10.0-22.24amd64Linux kernel
image for version 4.10.0 on 64 bit x86 SMP
is working OK for me!
$ uname -a
Linux vsw-it-nw-10 4.10.0-22-generic #24-Ubuntu SMP Mon May 22 17:43:20 UTC
2017 x86_64 x86_64 x86_64 GNU/Linux
--
Public bug reported:
When /boot is too full to accept another kernel/initial ram disk, the
installation process stops.
But at the same time mkinitramfs is leaving files and directories in /var/tmp,
filling up the disk.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-70-
Public bug reported:
During upgrade from trusty to xenial, thing went amiss
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-16-generic 4.4.0-16.32
ProcVersionSignature: Ubuntu 3.19.0-56.62~14.04.1-generic 3.19.8-ckt15
Uname: Linux 3.19.0-56-generic x86_64
AlsaDevices:
can confirm the bug with almost identical setup:
32GB RAM
00:00.0 Host bridge: Intel Corporation 4th Gen Core Processor DRAM Controller
(rev 06)
00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen
Core Processor Integrated Graphics Controller (rev 06)
00:14.0 USB contro
Public bug reported:
After the initial boot, the bluetooth connected mouse is working ok.
Up to a point where all over a sudden, it stops. The only thing being logged is:
[ 6089.525351] Bluetooth: hci0 command 0x0c03 tx timeout
[ 6097.530209] Bluetooth: hci0 sending initial HCI reset command fail
Public bug reported:
[ 4460.265149] [ cut here ]
[ 4460.265221] WARNING: CPU: 2 PID: 1234 at
/build/buildd/linux-3.16.0/drivers/net/wireless/iwlwifi/mvm/tx.c:191
iwl_mvm_set_tx_params+0x5da/0x6d0 [iwlmvm]()
[ 4460.265228] Got an HT rate for a non data frame 0x28
[ 4460.26
This happened after upgrading to 14.10.
--
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/1392982
Title:
Got an HT rate for a non data frame 0x28
Status in “linux” package in Ubuntu:
Con
Same issue here with a Dell Latitude e7240
--
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/1561474
Title:
Bluetooth will be disable after resume from suspend on Xenial
Status in linux pa
Also, landscape-sysinfo doesn't repaort any temperature any more:
# /usr/bin/landscape-sysinfo
System load: 2.72 Processes: 212
Usage of /: 61.0% of 13.75GB Users logged in: 1
Memory usage: 38%IP address for eth0: 141.42.1.203
Swap usage:
In the most recent Ubuntu release, there's no /proc/acpi/thermal_zone
anymore.
root@proxy-cbf-2:~# find /proc/acpi/
/proc/acpi/
/proc/acpi/battery
/proc/acpi/ac_adapter
/proc/acpi/event
/proc/acpi/wakeup
--
You received this bug notification because you are a member of Kernel
Packages, which is
This used to work in 13.04, so it's actually a regression.
--
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/1229307
Title:
paired device doesn't reconnect after suspend
Status in “bluez”
Public bug reported:
I use a bluetooth mouse. After I suspend/resume the system, I have
issues using it.
One workaround I found is to go into the bluetooth menu, select the menu
"Microsoft bluetooth mouse 5000", and click on the (already ticked!)
"Connection" submenu.
This causes the bluetooth m
Added hci.log as per debugging instructions.
* mouse was working
* I started the generation of the hci.log
* I supended
* I resumed
* Mouse was not working
* I performed my "workaround" (during which the generation of the log ended)
** Attachment added: "hci.log as per debugging instructions."
Public bug reported:
Recent kernel suddenly complain in dmesg:
[ 3605.513316] [ cut here ]
[ 3605.513379] WARNING: CPU: 1 PID: 1146 at
/build/buildd/linux-3.11.0/drivers/gpu/drm/i915/intel_display.c:8292
check_crtc_state+0x58f/0x9c0 [i915]()
[ 3605.513384] pipe state doe
Seems to be happening quite a lot:
[5.127523] WARNING: CPU: 1 PID: 457 at
/build/buildd/linux-3.11.0/drivers/gpu/drm/i915/intel_display.c:8292
check_crtc_state+0x58f/0x9c0 [i915]()
[7.336903] WARNING: CPU: 0 PID: 202 at
/build/buildd/linux-3.11.0/drivers/gpu/drm/i915/intel_display.c:829
Public bug reported:
I made a fresh install of Ubuntu Ringtail and Upgraded to Saucy.
Turns out that the machine won't boot with linux-image-3.11.0-12-generic, but
*will* boot with the old ringtail kernel
linux-image-3.8.0-31-generic!
I created two screenshots, one shows the point where the boo
Boot process with kernel 3.11 when hanging (the disk led is on all the
time)
** Attachment added: "3.11 when hanging (the disk led is on all the time)"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1237336/+attachment/3868764/+files/IMG_20131009_123429.jpg
--
You received this bug not
It's 3.8 from raring ringtail, not quantal (sorry about that)
--
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/1237336
Title:
linux-image-3.11.0-12-generic doesn't boot
Status in “linux”
Boot process on the same machine with the 3.8 kernel from quantal. It succeeeds.
Incidentially, the machine is fsck-ing the disk, due to the sheer number of
reboots I did...
** Attachment added: "IMG_20131009_123531.jpg"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1237336/+attachmen
I tried disabling swap, but that doesn't change a thing. So it must be
something after swapon.
--
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/1237336
Title:
linux-image-3.11.0-12-generic
Falling back to linux-image-3.11.0-11-generic makes things work again.
So it's a change between -11 and -12...
--
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/1237336
Title:
linux-image-3
Adding apparmor=0 to the kernel boot parameters doesn't change a thing
--
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/1237336
Title:
linux-image-3.11.0-12-generic doesn't boot
Status in
3.11.0-11.17: working
3.11.0-12.18: not working
Hm, looking at the changelog it's maybe due to the apparmor changes?
Don't have the calxedaxgmac at all, and the Upstream Kernel Change seems to
refer to an apple trackpad.
--
You received this bug notification because you are a member of Kernel
P
So, I even updated the BIOS to the most recent version, no change.
--
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/1237336
Title:
linux-image-3.11.0-12-generic doesn't boot
Status in “li
Turns out that it's a driver in the extra package. PCMCIA is being
probed and the kernel freezes; this happens for the mainline kernel as
well.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bug
apport information
** Attachment added: "BootDmesg.txt"
https://bugs.launchpad.net/bugs/1237336/+attachment/3868921/+files/BootDmesg.txt
--
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/
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1237336/+attachment/3868924/+files/IwConfig.txt
--
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/12
apport information
** Attachment added: "AlsaInfo.txt"
https://bugs.launchpad.net/bugs/1237336/+attachment/3868920/+files/AlsaInfo.txt
--
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/12
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1237336/+attachment/3868923/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1237336/+attachment/3868925/+files/Lspci.txt
--
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/1237336
Blacklisting yenta_socket makes the machine boot OK!
If I modprobe yenta_socket after booting up, the machine locks up.
** Tags added: apport-collected
** Description changed:
I made a fresh install of Ubuntu Ringtail and Upgraded to Saucy.
Turns out that the machine won't boot with lin
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1237336/+attachment/3868922/+files/CRDA.txt
--
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/1237336
Ti
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1237336/+attachment/3868933/+files/WifiSyslog.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages,
On 3.11 I got:
# sync && modprobe yenta_socket o2_speedup=off
Oct 9 14:50:18 ishtar kernel: [ 62.095581] yenta_cardbus :0d:06.0:
CardBus bridge found [1025:013c]
Oct 9 14:50:18 ishtar kernel: [ 62.095607] yenta_cardbus :0d:06.0: O2:
disabling read prefetch/write burst. If you exper
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1237336/+attachment/3868926/+files/Lsusb.txt
--
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/1237336
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1237336/+attachment/3868930/+files/RfKill.txt
--
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/1237336
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1237336/+attachment/3868931/+files/UdevDb.txt
--
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/1237336
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1237336/+attachment/3868929/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
Leaving o2_speedup at i's default "on" doesn't change the picture on
3.11:
# sync && modprobe yenta_socket
Oct 9 14:52:55 ishtar kernel: [ 57.637446] yenta_cardbus :0d:06.0:
CardBus bridge found [1025:013c]
Oct 9 14:52:55 ishtar kernel: [ 57.637472] yenta_cardbus :0d:06.0: O2:
enab
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1237336/+attachment/3868927/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
On 3.8, modprobe'ing yenta_socket works ok and gives:
# sync && modprobe yenta_socket
Oct 9 14:46:46 ishtar kernel: [ 68.809008] yenta_cardbus :0d:06.0:
CardBus bridge found [1025:013c]
Oct 9 14:46:46 ishtar kernel: [ 68.809031] yenta_cardbus :0d:06.0: O2:
enabling read prefetch/w
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1237336/+attachment/3868928/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
apport information
** Attachment added: "UdevLog.txt"
https://bugs.launchpad.net/bugs/1237336/+attachment/3868932/+files/UdevLog.txt
--
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/1237
Public bug reported:
pps_core taints the kernel:
# dmesg|grep -i4 taint
[1.370203] Write protecting the kernel text: 6356k
[1.370257] Write protecting the kernel read-only data: 2644k
[1.370260] NX-protecting the kernel data: 5932k
[1.388264] systemd-udevd[90]: starting version 20
So I'm digging through the CHANGELOGS between the mainline kernels
3.8.13.8 and 3.11.3 (which correspond to the mainline kernels for the
working and broken kernel).
There's only two kernels with changes to PCMCIA (which strikes me as
odd, but hey), and both contain the SAME change:
https://www.ke
* Joseph Salisbury :
> 3.11.0-11.17 was rebased to upstream 3.11.3, so it has all 3.11.3
> changes. 3.11.0-12.18 is still based off of upstream 3.11.3, so the bug
> may have been introduced by a SAUCE patch between 3.11.0-11.17 and
> 3.11.0-12.18.
>
> Can you first test the mainline 3.11.3 kern
Which previous kernel do you have in mind?
Something from raring?
--
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/1234232
Title:
check_crtc_state: pipe state doesn't match!
Status in “li
I'll boot into 3.8.x from raring and see what's going on there
--
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/1234232
Title:
check_crtc_state: pipe state doesn't match!
Status in “linux
* Joseph Salisbury :
> @Ralf, @naphta,
>
> Can you test the kernel posted in comment #33?
I hope @naphta can, since I don't have access to the machine in
question.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://
Public bug reported:
While surfing, I clicked on something,, X died, I was thrown back to a console
and finally was able to log back in.
dmesg is cluttered with:
[79849.958943] [drm:intel_pipe_config_compare [i915]] *ERROR* mismatch in
dpll_hw_state.wrpll (expected 0xb0210614, found 0x00
* Joseph Salisbury :
> Do you have a way to reproduce this bug, or was it a one time event?
So far it was a one time event, but I didn't update that long ago.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.l
81 matches
Mail list logo
