Launchpad has imported 3 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=204837.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help
** Bug watch added: Linux Kernel Bug Tracker #204837
https://bugzilla.kernel.org/show_bug.cgi?id=204837
** Also affects: linux via
https://bugzilla.kernel.org/show_bug.cgi?id=204837
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member
Also happening with HP Zbook x360, but only recently started (today).
As a workaround to stop your HD from filling up with this, create the
file
/etc/rsyslog.d/10-hidsensor.conf
With the two lines:
# Disable runaway messages:
:msg, contains, "hid-sensor-hub 001F:8087:0AC2.0003" ~
Then run
su
@connork: Thank you for the update!
I'm unfamiliar with the patch to kernel release process.
How long do you think before it shows up for the 5.3.x kernel?
Is there a place to watch/monitor it's progress?
Or is https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850600 the best
place?
--
You
Okay, looks like an additional patch set has just landed that rate
limits this error when the threshold is spilled over and that's being
tracked here and THAT is what is fix committed:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850600
The patch for this bug raised the threshold and that
These patches were applied today[1] and therefore the fix is not
released yet. Sorry for the confusion, everyone. Setting this to "Fix
committed".
** Changed in: linux (Ubuntu Disco)
Status: Fix Released => Fix Committed
--
You received this bug notification because you are a member of Ub
and I meant to cite this as [1] in comment #39:
https://lists.ubuntu.com/archives/kernel-team/2019-November/105342.html
--
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 sp
This bug report has a status of "Fix Released" and looks like it can't
be changed (at least not by me), should we open a new bug report?
It seems that this is also related to the mic not working, as
mayurvirkar mentioned, so I'd love to get as much attention on this as
possible.
--
You received
** Summary changed:
- hid-sensor-hub spamming dmesg in 4.20
+ hid-sensor-hub spamming dmesg in 4.20 - 5.3
--
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
This is blasting 3.45 million messages into my dmesg per day ( at least
no longer in syslog thanks to @incognito666 )
Dell XPS 13 7390 2-in-1 Ubuntu 19.10 kernel 5.3.0-19-generic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
HP Spectre x360 affected with kernel 5.3.0-19-generic.
Is there a way to turn this sensor off??
--
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
HP Spectre x360 on 19.10 with 5.3.0-19-generic has this issue as well.
The sensor "id": hid-sensor-hub 001F:8087:0AC2.0004
Tip: Add the line `:msg, contains, "hid-sensor-hub 001F:8087:0AC2.0004"
~` at the top of you /etc/rsyslog.d/50-default.conf to temporarily get
rid of this message in your log
Also affects Lenovo Thinkpad X1 Yoga 4th on 5.3.5-arch1-1-ARCH
--
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
Also affects Dell XPS / Ubuntu Eoan 5.3.0-18-generic #19-Ubuntu
--
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
Problem persists on kernel 5.3.1-300.fc31.x86_64 (Fedora 31).
--
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 b
I confirm that the problem persists with kernel 5.2.9 on HP Spectre
x360.
I am using kernel 5.1.9, which has no problem.
In addition, kernel 5.1.9 with linux-firmware-20190815.07b925b-1 has a
problem with iwlwifi, so I had also to downgrade it to linux-
firmware-20190618.acb56f2-1
--
You receiv
Affects me to. Also HP Spectre x360. Kernel 5.2.9-050209.
--
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 g
I got the same bug on the 5.2 kernel in my HP Spectre x360.
--
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
This patch was reverted about a month ago, and made its way into the 5.1
kernel recently. The issue now showing up on my Dell Latitude 7400.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818547
Titl
This bug was fixed in the package linux - 5.0.0-11.12
---
linux (5.0.0-11.12) disco; urgency=medium
* linux: 5.0.0-11.12 -proposed tracker (LP: #1824383)
* hns3: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1]
(LP: #1824194)
- net: hns3: fix for not calcula
Is there an easy way to disable the sensor until a kernel arrives that
fixes the problem?
--
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 manag
** Changed in: linux (Ubuntu Disco)
Assignee: Kai-Heng Feng (kaihengfeng) => (unassigned)
--
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
** Description changed:
+ === SRU Justification ===
+ [Impact]
+ [ 406.165461] hid-sensor-hub 001F:8086:22D8.0002: hid_field_extract() called
with n (192) > 32! (kworker/5:1)
+
+ [Fix]
+ Let HID core allow longer input report length.
+
+ [Test]
+ User confirmed the fix works.
+
+ [Regression P
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.
https://bugs.lau
https://lkml.org/lkml/2019/3/8/2
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng)
--
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
I have the same laptop. Neither my orientation is working, nor my mic.
PS: its a late 2018 model.
--
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
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:
https://bugs.launchpad.net/ubunt
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
I think it didn't happen on older kernel because the report size 192 >
128 so the code bailed early.
Try this:
diff --git a/drivers/hid/hid-core.c b/drivers/hid/hid-core.c
index 9993b692598f..860e21ec6a49 100644
--- a/drivers/hid/hid-core.c
+++ b/drivers/hid/hid-core.c
@@ -1301,10 +1301,10 @@ stat
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 Ubun
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 3da354af7a0a..e
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 32->.
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, to
I may be able to shed some light on this issue.
I am facing the same problem as described by the FMstrat, but in my case, its
caused by Accelerometer orientation which of course doesn't work.
I am on kernel 5.0 mainline and I am still facing the same problem.
--
You received this bug notificatio
The instruction uses deb because it's easier to remove.
We can skip building the deb though.
Use "make -j`nproc` && make -j`nproc` modules && sudo make modules_install &&
sudo make install` instead.
When the bisection is done, the "artifacts" are in /boot/, /lib/modules/
and /var/lib/initramfs-t
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 no
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
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.
https://bugs.l
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 notificatio
It's better to find the last good v4.20-rc* and first bad v4.20-rc*,
then start a bisection between them.
--
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 i
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 recei
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:
hid-sensor
Would it be possible for you to do a kernel bisection?
First, find the last good -rc kernel and the first bad -rc kernel from
http://kernel.ubuntu.com/~kernel-ppa/mainline/
Then,
$ sudo apt build-dep linux
$ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
$ cd linux
$ g
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
Bugs
** 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
T
** 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:
hi
** 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:
47 matches
Mail list logo
