** Attachment added: "dmesg.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818547/+attachment/5243433/+files/dmesg.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818547
Title:
** Attachment added: "lspci-vnvn.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818547/+attachment/5243434/+files/lspci-vnvn.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818547
Public bug reported:
Dmesg is a constant barrage of the same error:
```
[ 406.165461] hid-sensor-hub 001F:8086:22D8.0002: hid_field_extract() called
with n (192) > 32! (kworker/5:1)
```
This does not occur in 4.19 but does occur in all mainline 4.20 releases
including 4.20.13
** Attachment added: "version.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818547/+attachment/5243435/+files/version.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818547
Title:
How do I find the commit for the bisect good/bad command? The last good
version was 4.19.27, the first bad version was 4.20.0.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818547
Title:
I think I figured it out, I can't use 4.19.27, but have to use 4.19.
However:
# git bisect good v4.19
# git bisect bad v4.20
Some good revs are not ancestors of the bad rev.
git bisect cannot work properly in this case.
Maybe you mistook good and bad revs?
#
Is it safe to continue?
--
You
It happens in 4.20-rc1, so should I try to bisect between 4.19 and
4.20-rc1?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818547
Title:
hid-sensor-hub spamming dmesg in 4.20
To manage
I've just tried official 4.19.0, and no issue there. So I'm not sure
what's going on.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818547
Title:
hid-sensor-hub spamming dmesg in 4.20
To manage
As a note, the issue shows up in the first build attempt which was
"linux-image-4.19.0+_4.19.0+-1_amd64.deb". This seems like before the
4.19.27 I did not see the issue in.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
It happens in 4.20-rc1, so should I try to bisect between 4.19 and
4.20-rc1?
I gave that a shot, but after labeling the first try "bad", the next
make gave me:
...
dpkg-source: warning: no source format specified in debian/source/format, see
dpkg-source(1)
dpkg-source: info: using source format
Just tested in 5.0 kernel, same output. Please see second dmesg.log for
5.0 output.
** Attachment added: "dmesg.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818547/+attachment/5243448/+files/dmesg.log
--
You received this bug notification because you are a member of Ubuntu
Public bug reported:
Similar issue to
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784152, however
the fix in 4.18 does not seem to work for this one.
When using the pen included with the HP Spectre x360 13" and
libinput1.10 or libinput 1.12, dmesg is flooded with:
...
[ 87.571189]
Version is 5.0.0+ (only patch applied for
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818547), so should
not have impact here as the error exists with or without that patch.
** Attachment added: "version.log"
** Attachment added: "lspci-vnvn.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819389/+attachment/5245275/+files/lspci-vnvn.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1819389
That did the trick.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818547
Title:
hid-sensor-hub spamming dmesg in 4.20
To manage notifications about this bug go to:
Hrm, I went looking to see if I could help resolve, but I have to admit,
at first glance I don't get it. The commit diff:
$ git diff 7a324b3f0535ceb0f6676fa20ca2a7b6213008cb
71f6fa90a353605bf25c36417c9ae529ac1a9a8d
diff --git a/drivers/hid/hid-core.c b/drivers/hid/hid-core.c
index
There are a lot of HID changes in the previous commit of
61c4fc1eaf736344904767d201b0d4f7a2ebaf79, so I guess it's possible there
is perhaps something in the previous commit that is causing the 128/256
conflict.
Thanks again!
--
You received this bug notification because you are a member of
I will give that a shot and report back. Should the implement function
on line 1347 be changed as well?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818547
Title:
hid-sensor-hub spamming dmesg in
71f6fa90a353605bf25c36417c9ae529ac1a9a8d is the first bad commit
commit 71f6fa90a353605bf25c36417c9ae529ac1a9a8d
Author: Song, Hongyan
Date: Fri Aug 3 14:45:59 2018 +0800
HID: increase maximum global item tag report size to 256
The maximum globale report size has changed from
My device also has orientation (that works) (HP Spectre x360 13").
I am attempting the bisection without the deb pkg now. Just keeping a
log for if it's helpful.
1) 4.19.0+ Erorr displayed, touchpad didn't function
2) 4.19.0-rc8+ Did not show the error, touchpad functioned
3) 4.19.0+ No error,
As per Mayur's comments, orientation does work in 4.20, and in 5.0. Mic
does not. I'm working on debugging and will submit a ticket for that if
I can figure anything out.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "dmidecode.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819282/+attachment/5244994/+files/dmidecode.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1819282
Public bug reported:
Hardware: HP Spectre x360 13" i7 2018 Gem Cut
No s3 support and ACPI errors in dmesg:
[0.165087] ACPI FADT declares the system doesn't support PCIe ASPM, so
disable it
[0.165087] ACPI: bus type PCI registered
[0.165087] acpiphp: ACPI Hot Plug PCI Controller
** Attachment added: "lspci-vnvn.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819282/+attachment/5244989/+files/lspci-vnvn.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1819282
** Attachment added: "version.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819282/+attachment/5244988/+files/version.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1819282
Title:
** Attachment added: "cat-sys-power-mem_sleep.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819282/+attachment/5244991/+files/cat-sys-power-mem_sleep.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I will give this a shot today, however after pulling the latest kernel
source, it looks like part of that patch made it in, but not all of it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1819389
NOTE: The pen also reports a 1% battery all of the time. I'm not sure if
this is directly related.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1819389
Title:
i2c_hid_get_input: incomplete report
I was hoping that would be it, but no luck, dmesg with F23f:
[ 13.498936] Bluetooth: Core ver 2.22
[ 13.498948] Bluetooth: HCI device and connection manager initialized
[ 13.498950] Bluetooth: HCI socket layer initialized
[ 13.498951] Bluetooth: L2CAP socket layer initialized
[
Hmm, blacklisting iwlwifi didn't do anything, but I still see this in my
lsmod:
iwlmvm364544 0
mac80211 778240 1 iwlmvm
iwlwifi 286720 1 iwlmvm
cfg80211 622592 3 iwlmvm,iwlwifi,mac80211
Should I be blacklisting more?
--
You received
Ignore that, typo. Blacklisting correctly didn't help.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824703
Title:
Intel 8260 Bluetooth non-functioning, command timeouts
To manage notifications
Ok, well, no idea what happened, but I did a hard power cycle with that
kernel parameter, and it started working. I rebooted again without it,
and it still worked. Perhaps the hard power cycle did something
different this time with the new BIOS, but I thought I had done that
since. In any event,
4.15.18
Uname: Linux 4.15.0-47-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: fmstrat2489 F pulseaudio
/dev/snd/controlC0: fmstrat2489 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Sun Apr
I was redirected here as a duplicate of
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824703
The proposed fix does not work for me as I still receive the same error.
Installed deb, updated initrd, rebooted. Still issues.
--
You received this bug notification because you are a member of
Just wanted to let others know this impacts me in 19.10 as well, and
http://ftp.us.debian.org/debian/pool/main/a/adcli/adcli_0.9.0-1_amd64.deb
worked for me as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I am getting the same issue with a new device. Everything works fine on
one BT USB, but the intel one fails. It is a PCIe card with Intel AX200
Wifi+BT, with BT being passed through a USB header.
First boot with new card (dmesg):
```
[ 20.708957] Bluetooth: Core ver 2.22
[ 20.708971]
I should also note, if it helps, that when this BT device is installed
on the system, using the hotkeys to adjust volume on my keyboard no
longer works.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Current reports from `sensors` for Zen 3 CPUs:
```
PCH_CHIP_CPU_MAX_TEMP: +0.0°C
PCH_CHIP_TEMP: +0.0°C
PCH_CPU_TEMP: +0.0°C
```
This bug is due to the lack of Zen 3 support in Ubuntu's implementation
of k10temp.
Zen 3 (Ryzen 5XXX)
I am also affected with HPLIP and Nextcloud. Icon's do not display as
there is no System Tray. Killing the apps and restarting them works, so
the "delay" is likely the issue again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
39 matches
Mail list logo
