On Fri, 2 May 2008 11:55:35 +0200, Julien Cristau wrote: > On Fri, May 2, 2008 at 08:35:04 +0200, David Paleino wrote: > > > Hi Julien, > > I've just upgraded my system and this wasn't fixed. I believe that this is a > > kernel problem though, but I don't know which package I should assign it to: > > kernel? linux-image? > > I've found, googling a bit, that this might be related (kernel option > > i8042.debug=1 at boot time -- relevant bits only): > > > > ===> dmesg <=== > > ... > > [ 1.357240] PNP: PS/2 Controller [PNP0303:C297,PNP0f13:C298] at 0x60,0x64 irq 1,12 > > [ 1.357480] drivers/input/serio/i8042.c: 20 -> i8042 (command) [0] > > [ 1.357541] drivers/input/serio/i8042.c: 65 <- i8042 (return) [0] > > [ 1.357547] drivers/input/serio/i8042.c: 60 -> i8042 (command) [0] > > [ 1.357606] drivers/input/serio/i8042.c: 74 -> i8042 (parameter) [0] > > ... (so on for a while) > > [ 1.359293] i8042.c: Detected active multiplexing controller, rev 1.1. > > ... > > [ 1.360088] serio: i8042 KBD port at 0x60,0x64 irq 1 > > [ 1.360189] serio: i8042 AUX0 port at 0x60,0x64 irq 12 > > [ 1.360292] serio: i8042 AUX1 port at 0x60,0x64 irq 12 > > [ 1.360394] serio: i8042 AUX2 port at 0x60,0x64 irq 12 > > [ 1.360496] serio: i8042 AUX3 port at 0x60,0x64 irq 12 > > [ 1.363310] mice: PS/2 mouse device common for all mice > > ... > > [ 1.384094] drivers/input/serio/i8042.c: MUX error, status is 75, data is fe [7] > > [ 1.384097] drivers/input/serio/i8042.c: fe <- i8042 (interrupt, 3, 12, timeout) [7] > > ... > > [ 1.386792] drivers/input/serio/i8042.c: 91 -> i8042 (command) [7] > > [ 1.386850] drivers/input/serio/i8042.c: ed -> i8042 (parameter) [7] > > [ 1.387027] drivers/input/serio/i8042.c: MUX error, status is 75, data is fe [7] > > [ 1.387030] drivers/input/serio/i8042.c: fe <- i8042 (interrupt, 3, 12, timeout) [7] > > [ 1.391204] drivers/input/serio/i8042.c: 92 -> i8042 (command) [8] > > [ 1.391263] drivers/input/serio/i8042.c: f2 -> i8042 (parameter) [8] > > [ 1.391738] drivers/input/serio/i8042.c: MUX error, status is b5, data is fe [8] > > [ 1.391741] drivers/input/serio/i8042.c: fe <- i8042 (interrupt, 4, 12, timeout) [8] > > [ 1.391750] drivers/input/serio/i8042.c: 92 -> i8042 (command) [8] > > [ 1.391808] drivers/input/serio/i8042.c: ed -> i8042 (parameter) [8] > > [ 1.392637] drivers/input/serio/i8042.c: MUX error, status is b5, data is fe [9] > > ... > > ===> <=== > > > > I attach my dmesg to this mail, so that anyone can see it. > > > > Please Julien, consider re-assigning this bug (as soon as possible, I'll try > > downgrading the whole system to testing, and see which package has problems) > > reassigning to the kernel. Thanks. > Please tell us what kernel image are you using, which version, etc, and > if your touchpad used to work, what kernel you were using at the time. I'm currently using: # uname -a Linux pingu 2.6.25-1-686 #1 SMP Mon Apr 28 13:54:58 UTC 2008 i686 GNU/Linux I installed it to see if a newer kernel made my touchpad work, but not. I used to run "2.6.23-3~snapshot.10051" (I know, I know, it was an experimental package), but everything worked fine. Same kernel both in working and non-working case. I suspect something very wrong went with device registering/detection, udev, or something similar. As already said to Julien, I'll try to downgrade my system to lenny, hoping I can spot the package which causes problems. Julien, I don't know if you still want to be informed about this bug, so I'm keeping you CCed. Please remove yourself if you're not interested. Thanks, David P.S.: re-attaching the dmesg, since Julien's reply didn't have it. -- . ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 ----|---- http://snipr.com/qa_page `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174
Attachment:
dmesg-after-boot
Description: Binary data
Attachment:
signature.asc
Description: PGP signature