Bug#465278: Mouse freeze fixed in linux-2.6 (2.6.24-4)
Package: linux-image-2.6.24-1-powerpc Followup-For: Bug #465278 I am seeing the mouse freeze issue has gone away with 2.6.24-4. Anyone else getting the same results. Mark -- Package-specific info: ** Version: Linux version 2.6.24-1-powerpc (Debian 2.6.24-4) ([EMAIL PROTECTED]) (gcc version 4.1.3 20080114 (prerelease) (Debian 4.1.2-19)) #1 Mon Feb 11 12:53:42 CET 2008 ** Command line: root=/dev/hda3 ro ** Not tainted ** Kernel log: usb 2-1: configuration #1 chosen from 1 choice cdc_acm 2-1:1.8: ttyACM0: USB ACM device usbcore: registered new interface driver cdc_acm drivers/usb/class/cdc-acm.c: v0.25:USB Abstract Control Model driver for USB modems and ISDN adapters usbcore: registered new interface driver cdc_ether usb 2-1: bad CDC descriptors usbcore: registered new interface driver rndis_host usb 2-1: USB disconnect, address 7 usb 2-1: new full speed USB device using ohci_hcd and address 8 usb 2-1: configuration #1 chosen from 1 choice scsi0 : SCSI emulation for USB Mass Storage devices usb-storage: device found at 8 usb-storage: waiting for device to settle before scanning usb-storage: device scan complete scsi 0:0:0:0: Direct-Access NokiaS60 1.0 PQ: 0 ANSI: 0 Driver 'sd' needs updating - please use bus_type methods sd 0:0:0:0: [sda] 996352 512-byte hardware sectors (510 MB) sd 0:0:0:0: [sda] Write Protect is off sd 0:0:0:0: [sda] Mode Sense: 03 00 00 00 sd 0:0:0:0: [sda] Assuming drive cache: write through sd 0:0:0:0: [sda] 996352 512-byte hardware sectors (510 MB) sd 0:0:0:0: [sda] Write Protect is off sd 0:0:0:0: [sda] Mode Sense: 03 00 00 00 sd 0:0:0:0: [sda] Assuming drive cache: write through sda: sd 0:0:0:0: [sda] Attached SCSI removable disk usb 2-1: USB disconnect, address 8 usb 2-1: new full speed USB device using ohci_hcd and address 9 usb 2-1: configuration #1 chosen from 1 choice scsi1 : SCSI emulation for USB Mass Storage devices usb-storage: device found at 9 usb-storage: waiting for device to settle before scanning usb-storage: device scan complete scsi 1:0:0:0: Direct-Access NokiaS60 1.0 PQ: 0 ANSI: 0 sd 1:0:0:0: [sda] 996352 512-byte hardware sectors (510 MB) sd 1:0:0:0: [sda] Write Protect is off sd 1:0:0:0: [sda] Mode Sense: 03 00 00 00 sd 1:0:0:0: [sda] Assuming drive cache: write through sd 1:0:0:0: [sda] 996352 512-byte hardware sectors (510 MB) sd 1:0:0:0: [sda] Write Protect is off sd 1:0:0:0: [sda] Mode Sense: 03 00 00 00 sd 1:0:0:0: [sda] Assuming drive cache: write through sda: sd 1:0:0:0: [sda] Attached SCSI removable disk usb 2-1: USB disconnect, address 9 usb 2-1: new full speed USB device using ohci_hcd and address 10 usb 2-1: configuration #1 chosen from 1 choice cdc_acm 2-1:1.8: ttyACM0: USB ACM device usb 2-1: bad CDC descriptors wlan0_rename: deauthenticate(reason=3) ADDRCONF(NETDEV_UP): eth0: link is not ready input: b43-phy0 as /class/input/input19 Registered led device: b43-phy0:tx Registered led device: b43-phy0:rx Registered led device: b43-phy0:radio ADDRCONF(NETDEV_UP): wlan0_rename: link is not ready wlan0_rename: Initial auth_alg=0 wlan0_rename: authenticate with AP 00:13:10:17:be:4d wlan0_rename: RX authentication from 00:13:10:17:be:4d (alg=0 transaction=2 status=0) wlan0_rename: authenticated wlan0_rename: associate with AP 00:13:10:17:be:4d wlan0_rename: RX AssocResp from 00:13:10:17:be:4d (capab=0x401 status=0 aid=1) wlan0_rename: associated wlan0_rename: switched to short barker preamble (BSSID=00:13:10:17:be:4d) ADDRCONF(NETDEV_CHANGE): wlan0_rename: link becomes ready IN= OUT=wlan0_rename SRC=202.81.78.134 DST=202.83.82.162 LEN=76 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=123 DPT=123 LEN=56 IN= OUT=wlan0_rename SRC=202.81.78.134 DST=210.9.136.13 LEN=87 TOS=0x00 PREC=0x00 TTL=64 ID=54391 DF PROTO=TCP SPT=38307 DPT=143 WINDOW=2003 RES=0x00 ACK PSH URGP=0 IN= OUT=wlan0_rename SRC=192.168.1.205 DST=203.2.193.67 LEN=61 TOS=0x00 PREC=0x00 TTL=64 ID=55149 DF PROTO=UDP SPT=59595 DPT=53 LEN=41 IN= OUT=wlan0_rename SRC=192.168.1.205 DST=202.135.30.4 LEN=61 TOS=0x00 PREC=0x00 TTL=64 ID=55149 DF PROTO=UDP SPT=49503 DPT=53 LEN=41 IN= OUT=wlan0_rename SRC=192.168.1.205 DST=203.2.193.67 LEN=61 TOS=0x00 PREC=0x00 TTL=64 ID=55170 DF PROTO=UDP SPT=60325 DPT=53 LEN=41 IN= OUT=wlan0_rename SRC=192.168.1.205 DST=202.135.30.4 LEN=61 TOS=0x00 PREC=0x00 TTL=64 ID=55170 DF PROTO=UDP SPT=49248 DPT=53 LEN=41 IN= OUT=wlan0_rename SRC=192.168.1.205 DST=203.2.193.67 LEN=61 TOS=0x00 PREC=0x00 TTL=64 ID=55172 DF PROTO=UDP SPT=39660 DPT=53 LEN=41 IN= OUT=wlan0_rename SRC=192.168.1.205 DST=202.135.30.4 LEN=61 TOS=0x00 PREC=0x00 TTL=64 ID=55172 DF PROTO=UDP SPT=44625 DPT=53 LEN=41 IN= OUT=wlan0_rename SRC=192.168.1.205 DST=203.2.193.67 LEN=80 TOS=0x00 PREC=0x00 TTL=64 ID=55192 DF PROTO=UDP SPT=55141 DPT=53 LEN=60 IN= OUT=wlan0_rename SRC=192.168.1.205 DST=202.135.30.4 LEN=80 TOS=0x00 PREC=0x00 TTL=64 ID=55192 DF PROTO=UDP SPT=59996 DPT=53 LEN=60 IN= OUT=wlan0_rename SRC=192.168.1.205 DST=203.2.193.67
Automatic reply - No longer at this email address
Thanks for your mail. I am no longer receiving email at my University of Maryland address ([EMAIL PROTECTED]) -- I have now moved to Rennselaer Polytechnic Institute. My new email address is hendler (at) cs.rpi.edu (same as before but umd replaced by RPI) your mail will NOT automatically have forwarded, so please note the new address, and send your mail there if you want to reach me. I apologize to everyone for this inconvenience, and I especially apologize to anyone who is seeing this email on a mailing list which replies to everyone and not just to sender. If you are a mailing list administrator and are receiving this, please change my address on your mailing list. My contact information will be available through my web page http://www.cs.rpi.edu/~hendler thanks for taking the time to fix things, and I apologize for the inconvenience. -Jim Hendler p.s If you are getting this message and have no idea why, it is likely caused by forged email headers, a major spam contributor, and there's nothing either of us can do about it until IETF gets its act together on modernizing the email protocols. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
