Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#12277 - evdev.c(EVIOCGBIT): Suspicious buffer size 511, limiting output to 64 bytes.
Attached to Project:
Arch Linux
Opened by Mr. Smith (eNTi) - Saturday, 29 November 2008, 15:00 GMT
Last edited by Jan de Groot (JGC) - Sunday, 30 November 2008, 14:26 GMT
Opened by Mr. Smith (eNTi) - Saturday, 29 November 2008, 15:00 GMT
Last edited by Jan de Groot (JGC) - Sunday, 30 November 2008, 14:26 GMT
|
DetailsDescription:
my kernel is acting up. i think it has something to do with the synaptics driver, as this is what i'm using on my laptop and i found quite some references about it during my web search. Full message from dmesg: evdev.c(EVIOCGBIT): Suspicious buffer size 511, limiting output to 64 bytes. See http://userweb.kernel.org/~dtor/eviocgbit-bug.html Also this is comming up quite often at the same time: APIC error on CPU0: 40(40) nut sure if those are related Additional info: xorg-server 1.4.2-2 xf86-input-evdev 2.0.1-1 kernel26 2.6.27.6-1 (base) synaptics 0.14.6.99-2 Steps to reproduce: just using xorg (fluxbox) and firefox. it's not only the message, but also the apps i'm using are quite unresponsive on times. |
This task depends upon
Closed by Jan de Groot (JGC)
Sunday, 30 November 2008, 14:26 GMT
Reason for closing: Fixed
Additional comments about closing: xf86-input-synaptics is in extra now.
Sunday, 30 November 2008, 14:26 GMT
Reason for closing: Fixed
Additional comments about closing: xf86-input-synaptics is in extra now.
Comment by Jan de Groot (JGC) -
Saturday, 29 November 2008, 17:40 GMT
This is a bug in the synaptics driver. It's fixed in xf86-input-synaptics which is in testing.