key bounce problem with 2.6.11-rc5
Hi,
since I upgraded my ASUS M2400N laptop from 2.6.10 to 2.6.11-rc5, I got an annoying key bounce problem. I'm not sure if it's purely a kernel problem, because it seems to occur only in xwindows, but booting back to 2.6.10 made the bouncing disappear, and 2.6.11-rc5 seems to contain some changes to the keyboard driver.
It looks like the sequence of events is the following:
Usually, when I press a key, the char shows up on the screen immediately. But sometimes, the char does not show up until I press a second key, and in that moment, the first char shows up twice, together with the second one. (But I may be wrong with that observation, because the sequence of events is really fast - it's more like an impression than a real observation)
What can I do to help debugging that problem? Are there certain -rc versions between 2.6.10 and 2.6.11-rc5 you want me to try out?
Yours,
Jan
Linux 2.6.11
Ok,
there it is. Only small stuff lately - as promised. Shortlog from -rc5
appended, nothing exciting there, mostly some fixes from various code checkers (like fixed init sections, and some coverity tool finds).
So it's now _officially_ all bug-free.
Linus
----
Summary of changes from v2.6.11-rc5 to v2.6.11
============================================
<c.lucas:com.rmk.(none)>:
o [SERIAL] drivers/serial/*: convert to pci_register_driver
<takis:lumumba.luc.ac.be>:
o prism54 not releasing region
Alex Williamson:
o [SERIAL] 8250 woraround for buggy uart
Alexander Nyberg:
o SELinux: Leak in error path
o SELinux: null dereference in error path
Andrea Arcangeli:
o Make the new merged pipe writes check for SIGPIPE
Andrew Morton:
o binfmt_elf build fix
o [IA64] ia64 audit build fix
o genhd: NULL checking fix
Andries E. Brouwer:
o __devinitdata in parport_pc
o __init in cfq-iosched.c
o remove __initdata in scsi_devinfo.c
o __initdata in apic.c
o more apic.c
Aurelien Jarno:
o USB: Fix usbfs regression
Bartlomiej Zolnierkiewicz:
o [ide] fix build for built-in hpt366 and modular ide-disk
o [ide] fix IRQ masking in ide_do_request()
Ben Dooks:
o [ARM PATCH] 2498/1: CREDITS - add Ben Dooks
o [ARM PATCH] 2505/1: Remove FTVPCI from debug code
Bjorn Helgaas:
o [SERIAL] discover PNP ports before PCI, etc
o [SERIAL] add TP560 data/fax/modem support
Chris Wright:
o fix audit inode filter
o send audit reply to correct socket
David Gibson:
o ppc64: hugepage hash flushing bugfix
David Howells:
o Make keyctl(KEYCTL_JOIN_SESSION_KEYRING) use the correct arg
David S. Miller:
o [IPV4]: Fix lost routes in fn_hash netlink dumps
o [AF_UNIX]: Fix SIOCINQ for STREAM and SEQPACKET
Dmitry Torokhov:
o Input: add more PNP IDs to i8042 driver
Greg Kroah-Hartman:
o sysfs: fix signedness problem
o fix module paramater permissions in radeon_base.c
o USB: fix bug in acm's open function
Harald Welte:
o [NETFILTER]: ipt_hashlimit rule load time race condition
Hideaki Yoshifuji:
o add sysctl helper functions to provide milliseconds-based interfaces
o [IPV4] Use appropriate sysctl helpers for gc_min_interval_ms
o [IPV6]: Unregister per-device snmp6 proc entry earlier
Jens Axboe:
o [PATCH] Fix bounced bio and dm panic
Kenji Kaneshige:
o [IA64] pci_irq.c: need signed variable to handle error return from acpi
Linus Torvalds:
o Fix possible pty line discipline race
o Properly limit keyboard keycodes to KEY_MAX
o Make pipe "poll()" take direction of pipe into account
o Linux 2.6.11
Nishanth Aravamudan:
o [PKTGEN]: Replace interruptible_sleep_on_timeout()
Olaf Hering:
o Fix incorrect __init on 'modedb[]' array
Patrick McHardy:
o [NETFILTER]: Prevent NAT from seeing fragments
Randy Dunlap:
o [ide] make 1-bit fields unsigned
o srat: initdata section references
o sound/oss/aedsp16: init/exit section cleanups
o sonicvibes: fix initdata references
o sound/oss/opl3as2: fix init section reference
o isdn: use __init for ICCVersion()
o dc395x: fix section references
o hp100: fix section references
o rrunner: fix section references
Robert Olsson:
o [PKTGEN]: reduce stack usage
Russell King:
o [ARM] Fix dma_mmap() size argument
Sascha Hauer:
o [ARM PATCH] 2496/1: i.MX DMA fix
o [ARM PATCH] 2497/1: i.MX pll decode
Re: Linux 2.6.11
Quoted 3 lines · Linus Torvalds
there it is. Only small stuff lately - as promised. Shortlog from -rc5
appended, nothing exciting there, mostly some fixes from various code checkers (like fixed init sections, and some coverity tool finds).
ftp.kernel.org:/pub/linux/kernel/v2.6 doesn't seem to carry a crypto signature for the patch, patch-2.6.11.gz.sign
Re: Linux 2.6.11
Quoted 8 lines · Matthias Andree
Quoted 3 lines · Linus Torvalds
there it is. Only small stuff lately - as promised. Shortlog from -rc5
appended, nothing exciting there, mostly some fixes from various code checkers (like fixed init sections, and some coverity tool finds).ftp.kernel.org:/pub/linux/kernel/v2.6 doesn't seem to carry a crypto signature for the patch, patch-2.6.11.gz.sign
The full 2.6.10 -> 2.6.11 Changelog also seems to be missing, but I guess I'm just impatient :)
Congrats on the new release, can't wait to try it out. 2.6.11-rc has been working great, I have high hopes for this one :) Good work!
--
Jesper Juhl
Re: Linux 2.6.11
In reply to Matthias AndreeQuoted 3 lines · Matthias Andree
ftp.kernel.org:/pub/linux/kernel/v2.6 doesn't seem to carry a crypto signature for the patch, patch-2.6.11.gz.sign
It's there now (along with the ChangeLog).
The signatures are automatically generated at the master site, and the mirroring out to the public sites is a separate event, so sometimes (if you check early) you may miss the signatures for a while until the next time the scripts run.
The same is true of the .bz2 files, btw (I only upload the .gz ones, the rest is generated). And obviously the incremental patches.
(In contrast the full ChangeLog was missing because the generation script I use is not exactly the smart way, so it's O(slow(n)), where slow is n**3 or worse, so the log from the last -rc release is fast, but going back all the way to 2.6.10 took long long enough that I didn't wait for it).
Linus
Re: Linux 2.6.11
Quoted 11 lines · Linus Torvalds
Quoted 3 lines · Matthias Andree
ftp.kernel.org:/pub/linux/kernel/v2.6 doesn't seem to carry a crypto signature for the patch, patch-2.6.11.gz.sign
It's there now (along with the ChangeLog).
The signatures are automatically generated at the master site, and the mirroring out to the public sites is a separate event, so sometimes (if you check early) you may miss the signatures for a while until the next time the scripts run.
Is the master side a hidden host rather than ftp.kernel.org?
Quoted 4 lines
(In contrast the full ChangeLog was missing because the generation script I use is not exactly the smart way, so it's O(slow(n)), where slow is n**3 or worse, so the log from the last -rc release is fast, but going back all the way to 2.6.10 took long long enough that I didn't wait for it).
If that is an issue with the shortlog script or its integration with BK, contact me off-list so we can resolve the issue.
Thanks,
Signature · 1 line
Matthias Andree
Re: Linux 2.6.11
Quoted 2 lines · Matthias Andree
Is the master side a hidden host rather than ftp.kernel.org?
Yes. The private keys etc used to generate the signatures are not on the public sites, which is what I assume your question _really_ is.
Quoted 7 lines
Quoted 4 lines
(In contrast the full ChangeLog was missing because the generation script I use is not exactly the smart way, so it's O(slow(n)), where slow is n**3 or worse, so the log from the last -rc release is fast, but going back all the way to 2.6.10 took long long enough that I didn't wait for it).
If that is an issue with the shortlog script or its integration with BK, contact me off-list so we can resolve the issue.
No, it's just my stupid release script.
Linus
Re: Linux 2.6.11
In reply to Linus TorvaldsQuoted 4 lines · Linus Torvalds
(In contrast the full ChangeLog was missing because the generation script I use is not exactly the smart way, so it's O(slow(n)), where slow is n**3 or worse, so the log from the last -rc release is fast, but going back all the way to 2.6.10 took long long enough that I didn't wait for it).
Is there some reason why
bk changes -aem -rv2.6.10..+ | shortlog
isn't sufficient?
I'd guess your script will want to calculate the 2.6.10 part automatically, but that seems to run in a second or so on my machine, from a largely cold cache. I *think* this gets all the changes where a -d (date) based method gets very confused by parallel trees. Am I missing something?
Signature · 2 lines
Ryan Anderson sometimes Pug Majere
Re: Linux 2.6.11
Ryan Anderson schrieb am 2005-03-03:
Quoted 3 lines
Is there some reason why
bk changes -aem -rv2.6.10..+ | shortlogisn't sufficient?
For some reason, this omits some changes, perhaps from sibling branches, I haven't checked.
A similar change however warrants for a huge speedup of the changelog script, using bk changes rather than bk prs, without affection output at all. I have made such a change and committed it to my BK copy, see the "shortlog" announcement I posted two minutes ago.
Signature · 1 line
Matthias Andree
Re: Linux 2.6.11
In reply to Linus TorvaldsQuoted 7 lines · Linus Torvalds
Ok,
there it is. Only small stuff lately - as promised. Shortlog from -rc5
appended, nothing exciting there, mostly some fixes from various code checkers (like fixed init sections, and some coverity tool finds).So it's now _officially_ all bug-free.
BUG_ON() and friends are still broken (at least on x86)
the following 'patch':
init/main.c Sun Feb 27 05:13:45 2005 renamed from init/main.c.orig Thu Feb 17 19:25:21 2005 +2 -0
@@ -684,6 +684,8 @@ static int init(void * unused) * trying to recover a really broken machine. */ + BUG_ON(0==0); + if (execute_command) run_init_process(execute_command);
results in this oops:
(look at the filename and linenumber ;)
Freeing unused kernel memory: 244k freed
------------[ cut here ]------------ kernel BUG at <bad filename>:9377! ~~~~~~~~~~~~~~~~~~~
best,
Herbert
Quoted 128 lines
Linus
----
Summary of changes from v2.6.11-rc5 to v2.6.11
============================================<c.lucas:com.rmk.(none)>:
o [SERIAL]drivers/serial/*: convert topci_register_driver<takis:lumumba.luc.ac.be>:
o prism54 not releasing regionAlex Williamson:
o [SERIAL] 8250 woraround for buggy uartAlexander Nyberg:
o SELinux: Leak in error path
o SELinux: null dereference in error pathAndrea Arcangeli:
o Make the new merged pipe writes check for SIGPIPEAndrew Morton:
obinfmt_elfbuild fix
o [IA64] ia64 audit build fix
o genhd: NULL checking fixAndries E. Brouwer:
o__devinitdatainparport_pc
o__initincfq-iosched.c
o remove__initdatainscsi_devinfo.c
o__initdatainapic.c
o moreapic.cAurelien Jarno:
o USB: Fix usbfs regressionBartlomiej Zolnierkiewicz:
o [ide] fix build for built-in hpt366 and modular ide-disk
o [ide] fix IRQ masking inide_do_request()Ben Dooks:
o [ARM PATCH] 2498/1: CREDITS - add Ben Dooks
o [ARM PATCH] 2505/1: Remove FTVPCI from debug codeBjorn Helgaas:
o [SERIAL] discover PNP ports before PCI, etc
o [SERIAL] add TP560 data/fax/modem supportChris Wright:
o fix audit inode filter
o send audit reply to correct socketDavid Gibson:
o ppc64: hugepage hash flushing bugfixDavid Howells:
o Makekeyctl(KEYCTL_JOIN_SESSION_KEYRING)use the correct argDavid S. Miller:
o [IPV4]: Fix lost routes infn_hashnetlink dumps
o [AF_UNIX]: Fix SIOCINQ for STREAM and SEQPACKETDmitry Torokhov:
o Input: add more PNP IDs to i8042 driverGreg Kroah-Hartman:
o sysfs: fix signedness problem
o fix module paramater permissions inradeon_base.c
o USB: fix bug in acm's open functionHarald Welte:
o [NETFILTER]:ipt_hashlimitrule load time race conditionHideaki Yoshifuji:
o add sysctl helper functions to provide milliseconds-based interfaces
o [IPV4] Use appropriate sysctl helpers forgc_min_interval_ms
o [IPV6]: Unregister per-device snmp6 proc entry earlierJens Axboe:
o [PATCH] Fix bounced bio and dm panicKenji Kaneshige:
o [IA64]pci_irq.c: need signed variable to handle error return from acpiLinus Torvalds:
o Fix possible pty line discipline race
o Properly limit keyboard keycodes toKEY_MAX
o Make pipe "poll()" take direction of pipe into account
o Linux 2.6.11Nishanth Aravamudan:
o [PKTGEN]: Replaceinterruptible_sleep_on_timeout()Olaf Hering:
o Fix incorrect__initon 'modedb[]' arrayPatrick McHardy:
o [NETFILTER]: Prevent NAT from seeing fragmentsRandy Dunlap:
o [ide] make 1-bit fields unsigned
o srat: initdata section references
osound/oss/aedsp16: init/exit section cleanups
o sonicvibes: fix initdata references
osound/oss/opl3as2: fix init section reference
o isdn: use__initforICCVersion()
o dc395x: fix section references
o hp100: fix section references
o rrunner: fix section referencesRobert Olsson:
o [PKTGEN]: reduce stack usageRussell King:
o [ARM] Fixdma_mmap()size argumentSascha Hauer:
o [ARM PATCH] 2496/1: i.MX DMA fix
o [ARM PATCH] 2497/1: i.MX pll decode-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: Linux 2.6.11
Herbert Poetzl wrote:
[]
Quoted 1 line
BUG_ON()and friends are still broken (at least on x86)
[]
Quoted 4 lines
Freeing unused kernel memory: 244k freed
------------[ cut here ]------------ kernel BUG at <bad filename>:9377! ~~~~~~~~~~~~~~~~~~~
Have you tried compiling with CONFIG_DEBUG_INFO=y ? (Looks like CONFIG_DEBUG_BUGVERBOSE should either depend on CONFIG_DEBUG_INFO or turn it on).
/mjt
Re: Linux 2.6.11
Quoted 4 lines · Michael Tokarev
Herbert Poetzl wrote:
[]Quoted 1 line
BUG_ON()and friends are still broken (at least on x86)[]
Quoted 8 lines
Quoted 4 lines
Freeing unused kernel memory: 244k freed
------------[ cut here ]------------ kernel BUG at <bad filename>:9377! ~~~~~~~~~~~~~~~~~~~Have you tried compiling with
CONFIG_DEBUG_INFO=y? (Looks likeCONFIG_DEBUG_BUGVERBOSEshould either depend onCONFIG_DEBUG_INFOor turn it on).
egrep 'CONFIG_DEBUG_(INFO|BUGVERBOSE)' .config
# CONFIG_DEBUG_BUGVERBOSE is not setCONFIG_DEBUG_INFO=y
good point, just it seems to be the other way round ..
with CONFIG_DEBUG_BUGVERBOSE set I get the correct file and line, but no stack information ...
Freeing unused kernel memory: 104k freed
------------[ cut here ]------------ kernel BUG at init/main.c:692! invalid operand: 0000 [#1] PREEMPT CPU: 0 EIP: 0060:[<c0100330>] Not tainted VLI EFLAGS: 00000246 (2.6.11-rc1) eax: 00000000 ebx: c01002b0 ecx: 00000000 edx: 00000000 esi: 00000000 edi: 00000000 ebp: 00000000 esp: c10bdff0 ds: 007b es: 007b ss: 0068 Process swapper (pid: 1, threadinfo=c10bc000 task=c10b3aa0) Stack: c0100635 00000000 00000000 00000000 Call Trace: [<c0100635>] Code: 29 c0 01 00 00 00 6a 00 6a 02 68 97 0a 24 c0 e8 47 07 06 00 83 c4 0c 85 c0 78 60 6a 00 e8 a9 80 07 00 6a 00 e8 a2 80 07 00 58 5a <0f> 0b b4 02 13 0a 24 c0 a1 24 21 29 c0 85 c0 75 32 68 a4 0a 24
maybe there is another option which sneaked in, will investigate ...
thanks,
Herbert
PS: was it ever considered to hard code the explicit BUG_* files and lines via a macro instead of that (probably very fancy and efficient but nevertheless) strange address stuff?
I mean, are bug reports with missing/wrong file/line info really what the kernel developers want to see in the future?
Quoted 1 line
/mjt
Re: Linux 2.6.11
In reply to Linus TorvaldsLinux 2.6 Compile Statistics (gcc 3.4.1)
Web page with links to complete details:
http://developer.osdl.org/cherry/compile/
Kernel bzImage bzImage bzImage modules bzImage modules
(defconfig) (allno) (allyes) (allyes) (allmod) (allmod)
----------- ----------- -------- -------- -------- -------- ---------
2.6.11 13w/0e 0w/0e 352w/0e 6w/0e 17w/0e 431w/0e
2.6.11-rc5 14w/0e 0w/0e 353w/0e 6w/0e 18w/0e 431w/0e
2.6.11-rc4 14w/0e 0w/0e 353w/0e 6w/0e 18w/0e 431w/0e
2.6.11-rc3 14w/0e 0w/0e 356w/0e 6w/0e 18w/0e 435w/0e
2.6.11-rc3 13w/0e 0w/0e 356w/0e 6w/0e 18w/0e 435w/0e
2.6.11-rc2 18w/0e 0w/0e 365w/0e 6w/0e 22w/0e 440w/0e
2.6.11-rc1 20w/0e 0w/0e 497w/0e 6w/0e 22w/0e 577w/0e
2.6.10 13w/0e 0w/0e 778w/0e 6w/0e 15w/0e 861w/0e
2.6.9-rc3 13w/0e 0w/0e 774w/0e 6w/0e 15w/0e 857w/0e
2.6.9-rc2 14w/0e 0w/0e 1815w/11e 65w/0e 19w/0e 2157w/0e
(Compiles with gcc 3.2.2)
2.6.9-rc1 5w/0e 1w/0e 1069w/15e 6w/0e 4w/0e 1062w/1e
2.6.9 0w/0e 0w/0e 1930w/0e 41w/0e 11w/0e 1950w/0e
2.6.9-final 0w/0e 0w/0e 1930w/0e 41w/0e 11w/0e 1950w/0e
2.6.9-rc4 0w/0e 0w/0e 1930w/0e 41w/0e 11w/0e 1950w/0e
2.6.9-rc3 0w/0e 0w/0e 2752w/17e 41w/0e 11w/0e 2782w/5e
2.6.9-rc2 0w/0e 0w/0e 3036w/0e 41w/0e 11w/0e 3655w/0e
2.6.9-rc1 0w/0e 0w/0e 77w/10e 4w/0e 3w/0e 68w/0e
2.6.8.1 0w/0e 0w/0e 78w/ 0e 4w/0e 1w/0e 72w/0e
2.6.8 0w/0e 0w/0e 78w/ 0e 4w/0e 1w/0e 72w/0e
2.6.8-rc4 0w/0e 0w/0e 78w/ 0e 4w/0e 1w/0e 72w/0e
2.6.8-rc3 0w/0e 0w/0e 78w/ 0e 4w/0e 1w/0e 72w/0e
2.6.8-rc2 0w/0e 0w/0e 85w/ 0e 5w/0e 1w/0e 79w/0e
2.6.8-rc1 0w/0e 0w/0e 87w/ 0e 5w/0e 1w/0e 82w/0e
2.6.7 0w/0e 0w/0e 108w/ 0e 5w/0e 2w/0e 102w/0e
2.6.7-rc3 0w/0e 0w/0e 108w/ 0e 5w/0e 2w/0e 104w/0e
2.6.7-rc2 0w/0e 0w/0e 110w/ 0e 5w/0e 2w/0e 106w/0e
2.6.7-rc1 0w/0e 0w/0e 111w/ 0e 6w/0e 2w/0e 107w/0e
2.6.6 0w/0e 0w/0e 123w/ 0e 7w/0e 4w/0e 121w/0e
2.6.6-rc3 0w/0e 0w/0e 124w/ 0e 7w/0e 5w/0e 121w/0e
2.6.6-rc2 0w/0e 0w/0e 122w/ 0e 7w/0e 4w/0e 121w/0e
2.6.6-rc1 0w/0e 0w/0e 125w/ 0e 7w/0e 4w/0e 123w/0e
2.6.5 0w/0e 0w/0e 134w/ 0e 8w/0e 4w/0e 132w/0e
2.6.5-rc3 0w/0e 0w/0e 135w/ 0e 8w/0e 4w/0e 132w/0e
2.6.5-rc2 0w/0e 0w/0e 135w/ 0e 8w/0e 3w/0e 132w/0e
2.6.5-rc1 0w/0e 0w/0e 138w/ 0e 8w/0e 3w/0e 135w/0e
2.6.4 1w/0e 0w/0e 145w/ 0e 7w/0e 3w/0e 142w/0e
2.6.4-rc2 1w/0e 0w/0e 148w/ 0e 7w/0e 3w/0e 145w/0e
2.6.4-rc1 1w/0e 0w/0e 148w/ 0e 7w/0e 3w/0e 145w/0e
2.6.3 1w/0e 0w/0e 142w/ 0e 9w/0e 3w/0e 142w/0e
2.6.3-rc4 1w/0e 0w/0e 142w/ 0e 9w/0e 3w/0e 142w/0e
2.6.3-rc3 1w/0e 0w/0e 145w/ 7e 9w/0e 3w/0e 148w/0e
2.6.3-rc2 1w/0e 0w/0e 141w/ 0e 9w/0e 3w/0e 144w/0e
2.6.3-rc1 1w/0e 0w/0e 145w/ 0e 9w/0e 3w/0e 177w/0e
2.6.2 1w/0e 0w/0e 152w/ 0e 12w/0e 3w/0e 187w/0e
2.6.2-rc3 0w/0e 0w/0e 152w/ 0e 12w/0e 3w/0e 187w/0e
2.6.2-rc2 0w/0e 0w/0e 153w/ 8e 12w/0e 3w/0e 188w/0e
2.6.2-rc1 0w/0e 0w/0e 152w/ 0e 12w/0e 3w/0e 187w/0e
2.6.1 0w/0e 0w/0e 158w/ 0e 12w/0e 3w/0e 197w/0e
2.6.1-rc3 0w/0e 0w/0e 158w/ 0e 12w/0e 3w/0e 197w/0e
2.6.1-rc2 0w/0e 0w/0e 166w/ 0e 12w/0e 3w/0e 205w/0e
2.6.1-rc1 0w/0e 0w/0e 167w/ 0e 12w/0e 3w/0e 206w/0e
2.6.0 0w/0e 0w/0e 170w/ 0e 12w/0e 3w/0e 209w/0eDaily compiles (ia32):
http://developer.osdl.org/cherry/compile/2.6/linus-tree/running.txt
Latest changes in Linus' bitkeeper tree:
http://linux.bkbits.net:8080/linux-2.5
John
bouncing keys and skipping sound with 2.6.11
In reply to Linus TorvaldsHello,
the problem with bouncing keys I reported with 2.6.11-rc5 is still present in 2.6.11. Additionally, I noticed that audio has short outages every few seconds, which sound like latency problems would do.
And I saw with 'top' that often, when the sound skips, the kacpid process shows up using a big percentage of CPU time. (Perhaps it's always the kacpid waking up, but 'top' is just to slow to show it accurately)
Have there been changes between 2.6.10 and 2.6.11-rc5 which could cause these problems, perhaps together with ACPI bugs on the ASUS M2400N or anything like that? I'd be happy helping to debug this, if anybody could give me a hint where to start.
Yours,
Jan
Re: bouncing keys and skipping sound with 2.6.11
Quoted 2 lines · Jan Niehusmann
the problem with bouncing keys I reported with 2.6.11-rc5 is still present in 2.6.11. Additionally, I noticed that audio has short outages
By trying different kernel versions, I traced down the problem to the changes introduced between linux-2.6.11-rc2-bk9 and linux-2.6.11-rc2-bk10, and, more specifically, to the ACPI changes within that patch. (Therefore the Cc: to Len Brown, who wrote or submitted most of these changes, as far as I can tell from the changelog)
Len, do you have any idea which of the ACPI changes could have caused the described key bouncing problems on my ASUS M2400N laptop, or how I could debug this?
Yours,
Jan
Re: bouncing keys and skipping sound with 2.6.11
Quoted 6 lines · Jan Niehusmann
By trying different kernel versions, I traced down the problem to the changes introduced between linux-2.6.11-rc2-bk9 and linux-2.6.11-rc2-bk10, and, more specifically, to the ACPI changes within that patch. (Therefore the Cc: to Len Brown, who wrote or submitted most of these changes, as far as I can tell from the changelog)
I bet you have CONFIG_ACPI_DEBUG enabled. Disable it or try to put #define ACPI_ENABLE_OBJECT_CACHE 1
at the end of include/acpi/acpi.h (before the last #endif) This fixed it for me (and some others).
There is also a patch for a "CONFIG_ACPI_DEBUG_LITE" from Thomas Renninger on the acpi-devel list, which leaves some of the debugging in, but disables the worst offenders IIUC.
Hope that helps,
Stefan
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
Re: bouncing keys and skipping sound with 2.6.11
Quoted 4 lines · Stefan Seyfried
I bet you have
CONFIG_ACPI_DEBUGenabled. Disable it or try to put #defineACPI_ENABLE_OBJECT_CACHE1
at the end ofinclude/acpi/acpi.h(before the last #endif) This fixed it for me (and some others).
...and for me - thanks for the hint, I've been running 2.6.11 now for a few days without any problems.
Jan
Re: Linux 2.6.11
In reply to Linus TorvaldsQuoted 6 lines · Linus Torvalds
Ok,
there it is. Only small stuff lately - as promised. Shortlog from -rc5
appended, nothing exciting there, mostly some fixes from various code checkers (like fixed init sections, and some coverity tool finds).So it's now _officially_ all bug-free.
At least it builds 14 out of 23 arch defconfigs (http://l4x.org/k/),
which is quite an improvement over 10/22 of 2.6.10.
Congrats,
Jan
Re: Linux 2.6.11
In reply to Linus TorvaldsQuoted 8 lines · Linus Torvalds
Ok,
there it is. Only small stuff lately - as promised. Shortlog from -rc5
appended, nothing exciting there, mostly some fixes from various code checkers (like fixed init sections, and some coverity tool finds).So it's now _officially_ all bug-free.
Mmm, conflicts in NFS ?
nfsd/nfsctl.c reads:
static int __init init_nfsd(void)
{
...
if (proc_mkdir("fs/nfs", NULL)) {
struct proc_dir_entry *entry;
entry = create_proc_entry("fs/nfs/exports", 0, NULL);
if (entry)
entry->proc_fops = &exports_operations;
}...
But nfs-utils 1.0.7 say that you can mount nfsd at /proc/fs/nfsd. What 'exports' would kernel use ? Just duplicate info or a bug ?
TIA
--
J.A. Magallon <jamagallon()able!es> \ Software is like sex:
werewolf!able!es \ It's better when it's free
Mandrakelinux release 10.2 (Cooker) for i586
Linux 2.6.11-jam1 (gcc 3.4.3 (Mandrakelinux 10.2 3.4.3-3mdk)) #1
Re: Linux 2.6.11
su den 06.03.2005 Klokka 00:19 (+0000) skreiv J.A. Magallon:
Quoted 9 lines
static int
__initinit_nfsd(void)
{
...if (proc_mkdir("fs/nfs", NULL)) { struct proc_dir_entry *entry; entry = create_proc_entry("fs/nfs/exports", 0, NULL); if (entry) entry->proc_fops = &exports_operations; }
Quoted 4 lines
...
But nfs-utils 1.0.7 say that you can mount nfsd at
/proc/fs/nfsd. What 'exports' would kernel use ? Just duplicate info or a bug ?
Not sure why /proc/fs/nfs was originally chosen (perhaps Neil knows?), but the above code has nothing to do with where you mount the "nfsd" filesystem. It is rather part of the legacy support for older versions of nfs-utils.
We should aim to deprecate it at some point soon.
Cheers,
Trond
Signature · 1 line
Trond Myklebust <[email protected]>
Re: Linux 2.6.11
Quoted 13 lines · On Sunday March 6, [email protected] wrote:
su den 06.03.2005 Klokka 00:19 (+0000) skreiv J.A. Magallon:
Quoted 11 lines
static int
__initinit_nfsd(void)
{
...if (proc_mkdir("fs/nfs", NULL)) { struct proc_dir_entry *entry; entry = create_proc_entry("fs/nfs/exports", 0, NULL); if (entry) entry->proc_fops = &exports_operations; }...
Quoted 5 lines
Quoted 2 lines
But nfs-utils 1.0.7 say that you can mount nfsd at
/proc/fs/nfsd. What 'exports' would kernel use ? Just duplicate info or a bug ?Not sure why
/proc/fs/nfswas originally chosen (perhaps Neil knows?),
No, before my time./proc/fs/nfs/exports has "always" been a file listing the kernels current understanding of the exports table.
The same information is provided by the "/exports" file in the nfsd filesystem which (obviously) can be mounted anywhere you like, but nfs-utils will only work with it if it is mounted on /proc/fs/nfsd (the preferred location) or /proc/fs/nfs (because for a little while /proc/fs/nfsd didn't exist).
Quoted 5 lines
but the above code has nothing to do with where you mount the "nfsd" filesystem. It is rather part of the legacy support for older versions of nfs-utils.
We should aim to deprecate it at some point soon.
I would like to deprecate the nfssvc system call and /proc/fs/nfs, and I was planning to do it when 2.7 came out .....
Maybe June 2005 would be a good time to mark it 'deprecated' and June 2006 would be a good time to remove it.
NeilBrown