linux-kernel - Regression in 2.6.21-mm1 (git-input) on Dell D610 laptop

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 10 May 2007 15:05:25 +0200
From:	Remi Colinet <remi.colinet@...e.fr>
To:	linux-kernel@...r.kernel.org
Subject: Regression in 2.6.21-mm1 (git-input) on Dell D610 laptop

Hello,

My D610 ALPS Glide Point is unresponsive with 2.6.21-mm1 patch.
No problem noticed with 2.6.21.

The culprit seems to be git-input. I have applied 2.6.21-mm1 on top of 2.6.21
and then removed git-input patch. It is ok since then.

>From what i can see, no interrupt is raised from the GlidePoint with git-input
applied. IRQ count 12 does not increase. It is when using the touchpad.

           CPU0
  0:        160   IO-APIC-edge      timer
  1:        935   IO-APIC-edge      i8042
  7:          0   IO-APIC-edge      parport0
  8:          1   IO-APIC-edge      rtc
  9:          2   IO-APIC-fasteoi   acpi
=> 12:        114   IO-APIC-edge      i8042 <=
 14:       3223   IO-APIC-edge      libata
 15:          5   IO-APIC-edge      libata
 16:          0   IO-APIC-fasteoi   uhci_hcd:usb1, ehci_hcd:usb5, Intel ICH6
 17:          1   IO-APIC-fasteoi   uhci_hcd:usb2, ipw2200, Intel ICH6 Modem
 18:          0   IO-APIC-fasteoi   uhci_hcd:usb3
 19:          1   IO-APIC-fasteoi   uhci_hcd:usb4, yenta
NMI:          0
LOC:       4051
ERR:          0
MIS:          0

I have also tried to disable the ALPS driver in the .config file. IRQ 12 are
then raised when using the Glide Point. X refuses to start.

Any idea?

Remi Colinet

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/