(It took 30 seconds on the next boot)
--
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/1916314
Title:
HP Spectre x360 14-ea0xxx Tiger Lake Keyboard does not work until
~30-60 seconds
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1916314/+attachment/5468223/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1916314/+attachment/5468226/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/1916314/+attachment/5468228/+files/acpidump.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages,
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1916314/+attachment/5468221/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1916314/+attachment/5468222/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1916314/+attachment/5468225/+files/RfKill.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1916314/+attachment/5468224/+files/PulseList.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
In the apport-collected CurrentDmesg.txt, the keyboard is detected at:
[ 11.664651] input: AT Translated Set 2 keyboard as
/devices/platform/i8042/serio0/input/input44
That's sooner than it usually takes!
--
You received this bug notification because you are a member of Kernel
Packages,
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1916314/+attachment/5468227/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1916314/+attachment/5468219/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1916314/+attachment/5468220/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "PaInfo.txt"
https://bugs.launchpad.net/bugs/1916314/+attachment/5468218/+files/PaInfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1916314/+attachment/5468217/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1916314/+attachment/5468214/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1916314/+attachment/5468210/+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/1916314
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1916314/+attachment/5468216/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1916314/+attachment/5468211/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1916314/+attachment/5468215/+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/1916314
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1916314/+attachment/5468212/+files/IwConfig.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1916314/+attachment/5468213/+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/1916314
apport information
** Tags added: apport-collected groovy
** Description changed:
On the HP Spectre x360 14-ea0xxx (Tiger Lake), the keyboard is
inoperable for ~30-60 seconds after system boot.
Kernel logging reveals that it did not detect the keyboard during this
time.
An
> Have you compiled kernel with that patch?
No, I haven't. The workaround of setting i8042.nopnp is satisfactory for
me, and the patch creator has done a thorough write up of the problem.
My objective in filing this bug is to raise awareness that the current
version of Ubuntu has this problem -
Public bug reported:
On the HP Spectre x360 14-ea0xxx (Tiger Lake), the keyboard is
inoperable for ~30-60 seconds after system boot.
Kernel logging reveals that it did not detect the keyboard during this
time.
An analysis of this and a patch can be found at:
I also have this exact model of laptop.
I have installed kernel 5.11 from https://kernel.ubuntu.com/~kernel-
ppa/mainline/v5.11/
Following a cold boot to Ubuntu, sound can be made to work via the
workaround GPIO commands detailed in
https://bugzilla.kernel.org/show_bug.cgi?id=210633#c13
The
** Also affects: linux (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/1765911
Title:
Major performance regression from Ubuntu 17.10
It is expected that the -22.ucode file is missing because it was
deliberately removed per https://lists.ubuntu.com/archives/kernel-
team/2017-July/085667.html
The -27.ucode file was added in linux-firmware 1.165 and updated in
1.168
None of the other versions were ever released by Intel
Adding linux-firmware as an affected package - on further investigation,
it turns out that the real problem here appears to be firmware
incompatibility between the Wifi and Bluetooth parts of the 8260
package.
Relevant bug in Kernel bugzilla:
https://bugzilla.kernel.org/show_bug.cgi?id=197807
** Also affects: linux-firmware (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1719210
Title:
Bluetooth audio to A2DP
The exact manifestation of this seems to have changed (now the gnome
settings UI claims that my hardware doesn't have bluetooth support at
all - despite CLI bluetoothctl still being aware of it) but the basic
issue still very much remains: 4.13 from artful => bluetooth inoperable;
4.10 from zesty
It is not possible to test the latest upstream kernel. It appears to
introduce further problems apparently related to apparmor which prevent
dhclient running, preventing a wifi connection from being successful at
all, as well as apparently causing display flickering, which is barely
perceptible at
Unfortunately as the issue is intermittent, it is difficult to pinpoint
a starting version exactly, but here's my best attempt:
Ubuntu zesty 4.10 series: definitely not affected
Ubuntu artful 4.12 kernels: problem not observed, though other iwlwifi
issues (bug 1719210) observed - probably not
I also seem to now be having Bluetooth-unrelated issues with iwlwifi,
filed in bug 1722109
--
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/1719210
Title:
Bluetooth audio to A2DP headset
Public bug reported:
Recently I have been experiencing intermitted total packet loss over
wifi.
I've already been looking at another issue in which Bluetooth
coexistence seems to be causing controller hardware to crash - bug
1719210 - so I'm rather suspicious of the updated iwlwifi microcode
Confirming this is very much *not* fixed - the last linux-firmware
upload doesn't seem to have touched anything iwlwifi-related at all:
https://launchpadlibrarian.net/339888041/linux-
firmware_1.168_1.169.diff.gz
--
You received this bug notification because you are a member of Kernel
Packages,
OK, I think I finally found the real trigger, helped by John Tanner's
comment and Googling the bt_coex_active option. It's trying to
simultaneously use bluetooth and a *2.4GHz* wifi network.
Trying that on my hardware results in lots of iwlwifi kernel logging
reporting that the device microcode
Or so I thought :-(I got set up for bisecting again, and now I can't
reproduce the problem at all.
--
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/1719210
Title:
Bluetooth audio to
Hmm... empirically, I seem to have discovered a factor related to why
this sometimes works and sometimes does not with 4.13 - for me, the bug
only occurs if my laptop is booted *without* AC power applied.
Which makes no sense. But seems to be happening anyway.
--
You received this bug
I am seriously confused.
As requested, I tested out a 4.14-rc - actually, I tested -rc2 since
that had come out - and the problem was present - audio playback would
freeze after around 40-50 seconds.
Then I went back to various 4.13 versions and attempted to get the start
of a bisection going -
Mainline ppa 4.12.14 is working OK
--
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/1719210
Title:
Bluetooth audio to A2DP headset no longer works following upgrade from
4.12 to 4.13 in
Lack of functionality also a problem in mainline-ppa 4.13.3 version. The
following messages are logged to the journal:
Sep 24 21:44:05 spectre bluetoothd[826]: Unable to get Headset Voice gateway
SDP record: Connection timed out
Sep 24 21:44:46 spectre bluetoothd[826]: connect error: Connection
Public bug reported:
Using artful kernel 4.12.0-13.14, Bluetooth audio works great.
Upgrading to artful kernel 4.13.0-11.12, there are severe Bluetooth
audio issues which have manifested in a variety of weird ways:
1) Playback would stall after 10-20 seconds
2) Upon removing the device and
Acting on Cyril's suggestion above, I downloaded the Debian 8.0-2 source
package, rebuilt it locally, and installed it. It seems to have fixed
the problem for me. So perhaps the problem really is in the Ubuntu
delta?
--
You received this bug notification because you are a member of Kernel
I'm not sure if this helps, but I see pulseaudio logging an "Operation
Not Authorized" message when things do not work:
Apr 26 01:46:52 zenbook pulseaudio[3346]: [pulseaudio] module-bluez5-device.c:
Acquiring transport /org/bluez/hci0/dev_20_74_CF_02_DB_F2/fd0
Apr 26 01:46:52 zenbook
No, I have no Thunderbolt hardware in this computer, nor will any ever
be installed.
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.17.4-vivid/ has so far
been successfully running for an uptime of 2 days. So far so good,
though I didn't always experience a crash within this time on the utopic
I've just looked back through my /var/log/kern.log and I've noticed
something strange - I can't tell for certain which reboots are due to a
system lockup (since /var/log/syslog has rotated away too much, so I
can't look for rsyslogd shutting down to identify a clean reboot), but
it looks very much
Dell's release notes for this BIOS update state We do not recommend you
to upgrade to A10 BIOS if your system doesn't support Thunderbolt
hardware.
I decline to install a BIOS update that the manufacture recommends
against.
--
You received this bug notification because you are a member of
Public bug reported:
Since upgrading to utopic, I've been experiencing occasional system
lockups - when this occurs, nothing at all is responsive including the
mouse pointer and Alt-SysRq combinations.
Lockups only occur infrequently - perhaps once every day or two days -
so testing this is
48 matches
Mail list logo
