Bug#679750: Lenovo G360: ALPS Touchpad Recognized as PS/2 Generic Mouse
On Wed, 4 Jul 2012 22:20:09 -0500 Jonathan Nieder jrnie...@gmail.com wrote: (dropping Debian bug from cc list) Hi, littlebat wrote: I report a kernel bug about ALPS touchpad to you. My lenovo G360 has an ALPS touchpad, show in Windows 7 Home Editition OEM in this laptop. Under Debian Squeeze or Ubuntu 12.04 LTS LiveCD in same laptop, the left and right key, single and double tap, tracking of touchpad works well. But, there isn't touchpad tab in gnome mouse setting dialog, so I can't setup edge scrolling and disable touchpad on typing. xinput shows it is a PS/2 Generic Mouse. [...] Tell me If need more detail information. Thanks. Forgive me for being dense: can you spell this out a little more for me? Is the following summary correct? - 2.6.32.y (Debian squeeze) works well, using xinput or synclient to configure - 3.2.y (Ubuntu 12.04 LTS) sees a generic mouse, unconfigurable - 3.2.y (Debian squeeze-backports) is likewise unconfigurable - 3.4.4 (Debian experimental) is also unconfigurable No, none of these four kernels can configure a full functional ALPS touchpad. Under all of these four kernels: 1, synclient -l shows Couldn't find synaptics properties. No synaptics driver loaded? 2, xinput --list shows it is a PS/2 Generic Mouse 3, cat /proc/bus/input/devices shows it is N: Name=PS/2 Generic Mouse 4, Can't find any string like touchpad, synaptics in /var/log/Xorg.0.log 5, There isn't touchpad tab in gnome mouse setting dialog, so I can't setup edge scrolling and disable touchpad on typing. Could you provide full dmesg output from booting a working and non-working kernel? The laptop isn't here, I will post full dmesg output under 3.4.4 (Debian experimental) kernel later. Thanks. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120705154545.8d7492cc.dashing.m...@gmail.com
Bug#679750: Lenovo G360: ALPS Touchpad Recognized as PS/2 Generic Mouse
Very sorry, I post the wrong xinput --list information, it's my Asus EEEPC. Here's the correct xinput --list information of my Lenovo G360: â¡ Virtual core pointer id=2[master pointer (3)] â â³ Virtual core XTEST pointer id=4[slave pointer (2)] â â³ USB OPTICAL MOUSE id=11 [slave pointer (2)] â â³ PS/2 Generic Mouseid=14 [slave pointer (2)] ⣠Virtual core keyboard id=3[master keyboard (2)] â³ Virtual core XTEST keyboardid=5[slave keyboard (3)] â³ Power Button id=6[slave keyboard (3)] â³ Video Bus id=7 [slave keyboard (3)] â³ Video Bus id=8[slave keyboard (3)] â³ Power Button id=9[slave keyboard (3)] â³ Sleep Button id=10 [slave keyboard (3)] â³ Lenovo EasyCamera id=12 [slave keyboard (3)] â³ AT Translated Set 2 keyboardid=13 [slave keyboard (3)] â³ Ideapad extra buttons id=15 [slave keyboard (3)] â³ ACPI Virtual Keyboard Device id=16 [slave keyboard (3)] On Thu, 5 Jul 2012 11:30:57 +0800 littlebat dashing.m...@gmail.com wrote: found 679750 linux-2.6/2.6.32-45 , linux-2.6/3.2.4-1 , linux/3.4.4-1 quit Because send by web gmail.com has html content so failed send to linux-in...@vger.kernel.org at first time, so send again. Hi, Dear kernel developers. According to the advice at http://bugs.debian.org/679750 , I report a kernel bug about ALPS touchpad to you. My lenovo G360 has an ALPS touchpad, show in Windows 7 Home Editition OEM in this laptop. Under Debian Squeeze in same laptop, the left and right key, single and double tap, tracking of touchpad works well. But, there isn't touchpad tab in gnome mouse setting dialog, so I can't setup edge scrolling and disable touchpad on typing. xinput shows it is a PS/2 Generic Mouse. Below is the detail information. System information: Debian Squeeze, tried kernel: 2.6.32-45, 3.2.4-1~bpo60+1, 3.4.4-1~experimental.1 And tried Ubuntu 12.04 LTS LiveCD, kernel: 3.2 (has the same bug as in Debian) synclient -l shows: Couldn't find synaptics properties. No synaptics driver loaded? xinput --list shows: â¡ Virtual core pointer id=2 [master pointer (3)] â â³ Virtual core XTEST pointer id=4 [slave pointer (2)] â â³ USB Mouse id=10 [slave pointer (2)] â â³ ETPS/2 Elantech Touchpad id=14 [slave pointer (2)] ⣠Virtual core keyboard id=3[master keyboard (2)] â³ Virtual core XTEST keyboardid=5[slave keyboard (3)] â³ Power Button id=6 [slave keyboard (3)] â³ Video Bus id=7[slave keyboard (3)] â³ Power Button id=8 [slave keyboard (3)] â³ Sleep Button id=9 [slave keyboard (3)] â³ Digital_Cameraid=11 [slave keyboard (3)] â³ Asus EeePC extra buttons id=12 [slave keyboard (3)] â³ AT Translated Set 2 keyboard id=13 [slave keyboard (3)] â³ ACPI Virtual Keyboard Device id=15 [slave keyboard (3)] cat /proc/bus/input/devices shows (only post the section of PS/2 Generic Mouse): I: Bus=0011 Vendor=0002 Product=0001 Version= N: Name=PS/2 Generic Mouse P: Phys=isa0060/serio4/input0 S: Sysfs=/devices/platform/i8042/serio4/input/input9 U: Uniq= H: Handlers=mouse1 event9 B: PROP=0 B: EV=7 B: KEY=7 0 0 0 0 B: REL=3 Some related section in /var/log/Xorg.0.log is: [30.929] (II) config/udev: Adding input device PS/2 Generic Mouse (/dev/input/event9) [30.929] (**) PS/2 Generic Mouse: Applying InputClass evdev pointer catchall [30.929] (II) Using input driver 'evdev' for 'PS/2 Generic Mouse' [30.929] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so [30.929] (**) PS/2 Generic Mouse: always reports core events [30.929] (**) PS/2 Generic Mouse: Device: /dev/input/event9 [30.929] (--) PS/2 Generic Mouse: Found 3 mouse buttons [30.929] (--) PS/2 Generic Mouse: Found relative axes [30.929] (--) PS/2 Generic Mouse: Found x and y relative axes [30.929] (II) PS/2 Generic Mouse: Configuring as mouse [30.929] (**) PS/2 Generic Mouse: YAxisMapping: buttons 4 and 5 [30.929] (**) PS/2 Generic Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200 [30.929] (**) Option config_info udev:/sys/devices/platform/i8042/serio4/input/input9/event9 [30.929] (II) XINPUT: Adding extended input device PS/2 Generic Mouse (type: MOUSE) [30.929] (II) PS/2 Generic Mouse: initialized for relative axes. [30.929] (**) PS/2 Generic Mouse: (accel) keeping
Bug#670398: Deadlock in hid_reset when Dell iDRAC is reset
Hello, we have the same problem with all our DELL R210 and R210 II and Debian Squeeze. Jul 5 09:44:51 da16 kernel: [10760029.449586] usb 1-1.1: reset full speed USB device using ehci_hcd and address 3 Jul 5 09:45:06 da16 kernel: [10760044.513750] usb 1-1.1: device descriptor read/64, error -110 Jul 5 09:45:21 da16 kernel: [10760059.680488] usb 1-1.1: device descriptor read/64, error -110 and then no keyboard after ssh login and all processes hangs. I'm doing reboot with ssh root@host reboot and for few months or more everything is ok. Nobody is logged in DRAC and we don't have any Dell apps for DRAC control running. It occurs randomly. Kernel: linux-image-2.6.32-5-amd64 2.6.32-45 Can you tell us when it will be fixed upstream? Regards, Adam -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4ff55617.8010...@domeny.pl
Bug#679750: Lenovo G360: ALPS Touchpad Recognized as PS/2 Generic Mouse
Hi, I believe this is the same bug as launchpad bug 606238: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/606238 The bug discusses various Dell laptops with ALPS touchpad that don't work. They now work in the ubuntu 12.04 kernel (and I believe upstream as well), but some (such as the one found in an Inspiron 15R N5110) still don't work because they use yet another protocol version. Regards, Rik -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAPwv0J=wwMJZn0mZpH4c5U9Td=y4ltzxj2xruekur4ez38p...@mail.gmail.com
Bug#680366: linux-image-3.2.0-0.bpo.2-amd64: md raid6 deadlock on write
Package: src:linux Version: 3.2.20-1~bpo60+1 Severity: important Tags: upstream We have a group of servers with a LVM over a RAID6 of 16 drives. During normal work loads, sometimes, the md raid enter on deadlock for writes and only a power off/power on allows to recover the machine. The raid was created some time ago with something like: mdadm --create /dev/md2 --level=6 -n=16 /dev/sd[a-p] Following an old discussion on this list http://www.spinics.net/lists/raid/msg37708.html. And another discussion http://marc.info/?l=linux-raidm=134126754029228w=4 The back ported kernel 3.2.0 for squeeze is affected by this and it's possible to confirm that running the fio command can make the raid enter on deadlock. The command used was: fio --name=global --rw=randwrite --size=1G --bsrange=1k-128k \ --filename=/dev/md2 --name=job1 --name=job2 --name=job3 --name=job4 \ --end_fsync=1 I have been doing tests to see what kernels where affected by this bug. For the deadlock by running fio on back ported 3.2.0 was observed on the raid: - increasing the stripe_cache_size would allow some extra IO. This problem was found in back ported kernel 3.2.0 for squeeze and in the vanilla kernels 3.4.0, 3.4.0-rc2, 3.2.0. The Debian kernel 2.6.32 seams to be immune. It's under investigation if a possible fix is now in the Linus git tree. Jose Calhariz -- Package-specific info: ** Version: Linux version 3.2.0-0.bpo.2-amd64 (Debian 3.2.20-1~bpo60+1) (debian-kernel@lists.debian.org) (gcc version 4.4.5 (Debian 4.4.5-8) ) #1 SMP Fri Jun 29 20:42:29 UTC 2012 ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.2.0-0.bpo.2-amd64 root=UUID=8ceab9f5-8d93-44f1-ac09-c2f0ca118275 ro printk.time=n quiet ** Not tainted ** Kernel log: [81124e6e] ? writeback_sb_inodes+0x169/0x1ff [81124f71] ? __writeback_inodes_wb+0x6d/0xab [81125197] ? wb_writeback+0x128/0x222 [810c47b6] ? determine_dirtyable_memory+0xd/0x1d [810c482e] ? global_dirty_limits+0x29/0x10b [8112544f] ? wb_do_writeback+0x1be/0x1de [81055a7b] ? del_timer_sync+0x34/0x3e [81125532] ? bdi_writeback_thread+0xc3/0x1fe [8112546f] ? wb_do_writeback+0x1de/0x1de [8112546f] ? wb_do_writeback+0x1de/0x1de [810633c5] ? kthread+0x7a/0x82 [8136ca74] ? kernel_thread_helper+0x4/0x10 [8106334b] ? kthread_worker_fn+0x147/0x147 [8136ca70] ? gs_change+0x13/0x13 INFO: task md2_resync:3145 blocked for more than 120 seconds. echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. md2_resync D 880037842140 0 3145 2 0x 880037842140 0046 8800 88007d3e5610 00013540 88007c137fd8 88007c137fd8 00013540 880037842140 88007c136010 880037b83000 0001a019c970 Call Trace: [a01971a0] ? get_active_stripe+0x2ab/0x588 [raid456] [81045fb3] ? try_to_wake_up+0x190/0x190 [a019d1d3] ? sync_request+0x257/0x1084 [raid456] [810555e3] ? lock_timer_base+0x49/0x49 [a00ffe80] ? md_do_sync+0x78a/0xb98 [md_mod] [81044620] ? update_curr+0xbc/0x160 [8100d65c] ? __switch_to+0x175/0x2b1 [81044620] ? update_curr+0xbc/0x160 [a0100513] ? md_thread+0x105/0x123 [md_mod] [a010040e] ? md_rdev_init+0xea/0xea [md_mod] [a010040e] ? md_rdev_init+0xea/0xea [md_mod] [810633c5] ? kthread+0x7a/0x82 [8136ca74] ? kernel_thread_helper+0x4/0x10 [8106334b] ? kthread_worker_fn+0x147/0x147 [8136ca70] ? gs_change+0x13/0x13 INFO: task fio:4922 blocked for more than 120 seconds. echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. fio D 88007a290730 0 4922 4917 0x 88007a290730 0082 8800 88007d3a20c0 00013540 88000c61bfd8 88000c61bfd8 00013540 88007a290730 88000c61a010 0046 00017a290730 Call Trace: [a01971a0] ? get_active_stripe+0x2ab/0x588 [raid456] [8103882a] ? __wake_up_common+0x41/0x78 [81045fb3] ? try_to_wake_up+0x190/0x190 [a019ad03] ? make_request+0x1b9/0x373 [raid456] [81063801] ? wake_up_bit+0x20/0x20 [8112aebe] ? T.1024+0x17/0x17 [a00fea9b] ? md_make_request+0xbe/0x1b1 [md_mod] [811aa026] ? generic_make_request+0x8e/0xcd [811aa13e] ? submit_bio+0xd9/0xf7 [8112aebe] ? T.1024+0x17/0x17 [8112dc78] ? bio_alloc_bioset+0x44/0xb3 [81129b3d] ? submit_bh+0xe5/0x105 [8112c1a8] ? __block_write_full_page+0x1dd/0x2b5 [8112e1ce] ? blkdev_max_block+0x2e/0x2e [810c3ff2] ? __writepage+0xa/0x21 [810c50e5] ? write_cache_pages+0x226/0x31e [810c3fe8] ? set_page_dirty+0x61/0x61 [810c521b] ? generic_writepages+0x3e/0x55 [810bd480] ? __filemap_fdatawrite_range+0x4b/0x50
Bug#679750: Lenovo G360: ALPS Touchpad Recognized as PS/2 Generic Mouse
On Thu, Jul 05, 2012 at 03:45:45PM +0800, littlebat wrote: Is the following summary correct? - 2.6.32.y (Debian squeeze) works well, using xinput or synclient to configure - 3.2.y (Ubuntu 12.04 LTS) sees a generic mouse, unconfigurable - 3.2.y (Debian squeeze-backports) is likewise unconfigurable - 3.4.4 (Debian experimental) is also unconfigurable No, none of these four kernels can configure a full functional ALPS touchpad. Under all of these four kernels: 1, synclient -l shows Couldn't find synaptics properties. No synaptics driver loaded? 2, xinput --list shows it is a PS/2 Generic Mouse 3, cat /proc/bus/input/devices shows it is N: Name=PS/2 Generic Mouse 4, Can't find any string like touchpad, synaptics in /var/log/Xorg.0.log 5, There isn't touchpad tab in gnome mouse setting dialog, so I can't setup edge scrolling and disable touchpad on typing. ALPS refuses to provide information about their touchpad protocols, so any support we have for ALPS touchpads is based on reverse engineering the protocol. It's likely that yours uses some version of the protocol that isn't supported, in which case someone with access to the hardware will need to do the reverse engineering work. There's a slight chance that it uses a known protocol but just has an unknown model signature. In that case the fix is easy, but it will require some trial and error to see if that's the case. Could you provide full dmesg output from booting a working and non-working kernel? The laptop isn't here, I will post full dmesg output under 3.4.4 (Debian experimental) kernel later. When you send dmesg it would help if you could use a build with the following line added to the top of drivers/input/mouse/alps.c, before the includes. #define DEBUG This will cause the model signature for your touchpad to be included in the log. Thanks, Seth -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120705133036.GA28604@thinkpad-t410
Processed: [bts-link] source package linux-2.6
Processing commands for cont...@bugs.debian.org: # # bts-link upstream status pull for source package linux-2.6 # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org Setting user to bts-link-upstr...@lists.alioth.debian.org (was bts-link-de...@lists.alioth.debian.org). # remote status report for #509338 (http://bugs.debian.org/509338) # Bug title: Thinkpad T400: mouse pointer gets temporarily stuck (input0 lost sync at byte 1; issuing reconnect request) # * http://bugzilla.kernel.org/show_bug.cgi?id=8740 # * remote status changed: CLOSED - REOPENED # * remote resolution changed: INVALID - (?) usertags 509338 - status-CLOSED resolution-INVALID Bug#509338: Thinkpad T400: mouse pointer gets temporarily stuck (input0 lost sync at byte 1; issuing reconnect request) Usertags were: resolution-INVALID status-CLOSED. Usertags are now: . usertags 509338 + status-REOPENED Bug#509338: Thinkpad T400: mouse pointer gets temporarily stuck (input0 lost sync at byte 1; issuing reconnect request) There were no usertags set. Usertags are now: status-REOPENED. # remote status report for #557802 (http://bugs.debian.org/557802) # Bug title: linux-image-2.6.26-2-686: No sound with snd-ens1371.ko # * http://bugzilla.kernel.org/show_bug.cgi?id=15450 # * remote status changed: NEW - CLOSED # * remote resolution changed: (?) - OBSOLETE # * closed upstream tags 557802 + fixed-upstream Bug #557802 [linux-2.6] linux-image-2.6.26-2-686: No sound with snd-ens1371.ko Added tag(s) fixed-upstream. usertags 557802 - status-NEW Bug#557802: linux-image-2.6.26-2-686: No sound with snd-ens1371.ko Usertags were: status-NEW. Usertags are now: . usertags 557802 + status-CLOSED resolution-OBSOLETE Bug#557802: linux-image-2.6.26-2-686: No sound with snd-ens1371.ko There were no usertags set. Usertags are now: resolution-OBSOLETE status-CLOSED. # remote status report for #571242 (http://bugs.debian.org/571242) # Bug title: linux-image-2.6.32-2-amd64: running 8 copies of bonnie deadlocks(?) in sync # * http://bugzilla.kernel.org/show_bug.cgi?id=15426 # * remote status changed: NEW - RESOLVED # * remote resolution changed: (?) - OBSOLETE # * closed upstream tags 571242 + fixed-upstream Bug #571242 [linux-2.6] linux-image-2.6.32-2-amd64: running 8 copies of bonnie deadlocks(?) in sync Added tag(s) fixed-upstream. usertags 571242 - status-NEW Bug#571242: linux-image-2.6.32-2-amd64: running 8 copies of bonnie deadlocks(?) in sync Usertags were: status-NEW. Usertags are now: . usertags 571242 + status-RESOLVED resolution-OBSOLETE Bug#571242: linux-image-2.6.32-2-amd64: running 8 copies of bonnie deadlocks(?) in sync There were no usertags set. Usertags are now: status-RESOLVED resolution-OBSOLETE. # remote status report for #677880 (http://bugs.debian.org/677880) # Bug title: iwlwifi: flakey and slow connection, high invalid misc count # * http://bugzilla.intellinuxwireless.org/show_bug.cgi?id=2370 # * remote status changed: (?) - NEW usertags 677880 + status-NEW Bug#677880: iwlwifi: flakey and slow connection, high invalid misc count There were no usertags set. Usertags are now: status-NEW. # remote status report for #658662 (http://bugs.debian.org/658662) # Bug title: drm/i915: no signal via DisplayPort on Sandy Bridge since Linux 3.2 # * https://bugs.freedesktop.org/show_bug.cgi?id=45801 # * remote status changed: REOPENED - RESOLVED # * remote resolution changed: (?) - FIXED # * closed upstream tags 658662 + fixed-upstream Bug #658662 [linux-2.6] drm/i915: no signal via DisplayPort on Sandy Bridge since Linux 3.2 Added tag(s) fixed-upstream. usertags 658662 - status-REOPENED Bug#658662: drm/i915: no signal via DisplayPort on Sandy Bridge since Linux 3.2 Usertags were: status-REOPENED. Usertags are now: . usertags 658662 + status-RESOLVED resolution-FIXED Bug#658662: drm/i915: no signal via DisplayPort on Sandy Bridge since Linux 3.2 There were no usertags set. Usertags are now: status-RESOLVED resolution-FIXED. thanks Stopping processing here. Please contact me if you need assistance. -- 557802: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=557802 571242: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=571242 658662: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=658662 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.134150628111023.transcr...@bugs.debian.org
[bts-link] source package src:linux
# # bts-link upstream status pull for source package src:linux # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org # remote status report for #679039 (http://bugs.debian.org/679039) # Bug title: linux-image-3.2.0-2-686-pae: boot crash with VT6415 controller (pata_via) # * http://bugzilla.kernel.org/show_bug.cgi?id=44111 # * remote status changed: (?) - ASSIGNED usertags 679039 + status-ASSIGNED thanks -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120705163800.32142.94736.btsl...@busoni.debian.org
[bts-link] source package linux-2.6
# # bts-link upstream status pull for source package linux-2.6 # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org # remote status report for #509338 (http://bugs.debian.org/509338) # Bug title: Thinkpad T400: mouse pointer gets temporarily stuck (input0 lost sync at byte 1; issuing reconnect request) # * http://bugzilla.kernel.org/show_bug.cgi?id=8740 # * remote status changed: CLOSED - REOPENED # * remote resolution changed: INVALID - (?) usertags 509338 - status-CLOSED resolution-INVALID usertags 509338 + status-REOPENED # remote status report for #557802 (http://bugs.debian.org/557802) # Bug title: linux-image-2.6.26-2-686: No sound with snd-ens1371.ko # * http://bugzilla.kernel.org/show_bug.cgi?id=15450 # * remote status changed: NEW - CLOSED # * remote resolution changed: (?) - OBSOLETE # * closed upstream tags 557802 + fixed-upstream usertags 557802 - status-NEW usertags 557802 + status-CLOSED resolution-OBSOLETE # remote status report for #571242 (http://bugs.debian.org/571242) # Bug title: linux-image-2.6.32-2-amd64: running 8 copies of bonnie deadlocks(?) in sync # * http://bugzilla.kernel.org/show_bug.cgi?id=15426 # * remote status changed: NEW - RESOLVED # * remote resolution changed: (?) - OBSOLETE # * closed upstream tags 571242 + fixed-upstream usertags 571242 - status-NEW usertags 571242 + status-RESOLVED resolution-OBSOLETE # remote status report for #677880 (http://bugs.debian.org/677880) # Bug title: iwlwifi: flakey and slow connection, high invalid misc count # * http://bugzilla.intellinuxwireless.org/show_bug.cgi?id=2370 # * remote status changed: (?) - NEW usertags 677880 + status-NEW # remote status report for #658662 (http://bugs.debian.org/658662) # Bug title: drm/i915: no signal via DisplayPort on Sandy Bridge since Linux 3.2 # * https://bugs.freedesktop.org/show_bug.cgi?id=45801 # * remote status changed: REOPENED - RESOLVED # * remote resolution changed: (?) - FIXED # * closed upstream tags 658662 + fixed-upstream usertags 658662 - status-REOPENED usertags 658662 + status-RESOLVED resolution-FIXED thanks -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120705163800.32142.16501.btsl...@busoni.debian.org
Bug#664461: [squeeze] atl1c: AR8152: transmit queue 0 timed out and network is unusable until reset
On Wed, Jul 04, 2012 at 01:16:14PM -0500, Jonathan Nieder wrote: Jonathan Nieder wrote: Luis R. Rodriguez wrote: FWIW we already provide daily backports of code through compat-wireless. compat-wireless will eventually be changed to compat-drivers to reflect that it has drivers backported other than 802.11. We also have stable releases of the Linux kernel backported for use on older releases. I looked at the relevant repositories and am afraid I am too dim to see how to use them. Ok, it's becoming a little clearer now. Is the appropriate procedure something like this? git clone git://github.com/mcgrof/compat.git git clone git://github.com/mcgrof/compat-wireless.git git clone git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git git clone git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git cd compat-wireless git checkout linux-3.0.y GIT_COMPAT_TREE=$(pwd)/compat/ this ones always assumes $HOME/compat so if you have it there already there is no need to specify this variable. NEXT_TREE=/path/to/src/linux GIT_TREE=/path/to/linux/repo export GIT_TREE GIT_COMPAT_TREE Nope, export GIT_TREE=/home/foo/linux-stable.git git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git I use Greg's linux-stable.git so I can use all the extra version stable kernels, but on top of that I have a remote set up to also pull in Linus' junk: [remote linus] fetch = +refs/heads/*:refs/remotes/origin/* url = git://github.com/torvalds/linux.git So I just do this on linux-stable: git fetch linus git reset --hard origin Then I get reset --hard v3.5-rc5 given that Linus will typically have a delta on top of the latest RC. scripts/gen-stable-release.sh some appropriate arguments The arguments allows you to specify which delta you want to suck in, if at all. http://wireless.kernel.org/en/users/Download/stable/#Legend http://wireless.kernel.org/en/users/Download/stable/#Additional_patches_to_stable_releases And then this will not generate a list of patches but just a patched source code tree with appropriate #ifdefs to make the code build against old kernels. #ifdef'ing around code to provide kernel backporting is a strategy of the stone age. We have taken a slightly different approach, we have stuffed as much into a module / headers: compat.git so that the code can remain as pristine as possible. This also means that you can backport *more* subsystems with less effort and I've proven this through a graph which shows the overhead cost of backporting a new subsystem once you have a lot of code within a shared compat module: https://docs.google.com/presentation/d/1axVNEGwKZjnzG1ocdd289WMqPxzJ3qfMv70ghGcnUKc/edit The only #ifdef crap needed really would then just be things that *cannot* be backported through a module / headers. In turn we've been discovering that some of this #ifdef'able stuff actually can be represented also using SmPL and that this SmPL actually represents collateral evolutions of the Linux kernel. So the patches/ directory represents just this: collateral evolutions of the Linux kernel. I've started to formally document this slowly. The first one is the patch with 4 digits: patches/0001-netdev_ops.patch Jesper Andersen however has written a tool called spdiff which I intend on using to extract SmPL *from* a patch file ! What this means is if one collateral evolution *which could not be backported through compat.git* is backported for *two drivers* it means that we can backport that collateral evolution for *all drivers*. Furthermore if we design collateral evolutions on the Linux kernel *with* SmPL it means we also can backport that respective collateral evolution with the *inverse* of SmPL ! That sounds useful. How about with all the other junk I just mentioned ? :) I should mention that stable releases are already made: http://wireless.kernel.org/en/users/Download/stable/ But surely you can also just make your own as well. The stable releases also are test compiled accross 21 kernels, and soon, thanks to Ozan's GSoC project I hope we'll have video backported as well. Luis -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120705203235.GE11228@tux
Bug#664461: [squeeze] atl1c: AR8152: transmit queue 0 timed out and network is unusable until reset
Hi, Xiong, everything has been running stable without any problems with these patches (whereas without them it never worked), so⦠$ ls -l kern.log* -rw-r- 1 root adm 688988 Jul 5 23:12 kern.log -rw-r- 1 root adm 421701 Jul 2 05:50 kern.log.1 -rw-r- 1 root adm 141255 Jun 28 19:27 kern.log.2.gz -rw-r- 1 root adm 151227 Jun 18 20:09 kern.log.3.gz -rw-r- 1 root adm 210761 Jun 10 11:50 kern.log.4.gz â¦and my oldest log entry is from June 3. Sorry. Axel On Wed, 4 Jul 2012, Huang, Xiong wrote: Hi Axel Just curious, it seems that the kern log is un-complete, you missed some lines just before the line of Mar 18 08:14:54 bamboo kernel: [ 1379.37] [ cut here ] Could you paste here ?
Bug#664461: [squeeze] atl1c: AR8152: transmit queue 0 timed out and network is unusable until reset
Got it, Axel , thanks ! -Original Message- From: Dr. Axel Stammler [mailto:dr_a_stamm...@versanet.de] Sent: Friday, July 06, 2012 5:35 To: Huang, Xiong Cc: Jonathan Nieder; Ben Hutchings; 664...@bugs.debian.org; nic-devel; Rodriguez, Luis Subject: RE: [squeeze] atl1c: AR8152: transmit queue 0 timed out and network is unusable until reset Hi, Xiong, everything has been running stable without any problems with these patches (whereas without them it never worked), so… $ ls -l kern.log* -rw-r- 1 root adm 688988 Jul 5 23:12 kern.log -rw-r- 1 root adm 421701 Jul 2 05:50 kern.log.1 -rw-r- 1 root adm 141255 Jun 28 19:27 kern.log.2.gz -rw-r- 1 root adm 151227 Jun 18 20:09 kern.log.3.gz -rw-r- 1 root adm 210761 Jun 10 11:50 kern.log.4.gz …and my oldest log entry is from June 3. Sorry. Axel On Wed, 4 Jul 2012, Huang, Xiong wrote: Hi Axel Just curious, it seems that the kern log is un-complete, you missed some lines just before the line of Mar 18 08:14:54 bamboo kernel: [ 1379.37] [ cut here ] Could you paste here ?
Bug#617453: restarting doesn't always work on Dell Latitude E6400
Hi, On 2012-07-04 20:55:56 +0200, Rik Theys wrote: Vincent Lefevre wrote: When I want to restart (reboot) my Dell Latitude E6400 laptop, the machine sometimes remain on without restarting. The last message on the console is: Restarting system. Can you try adding the following parameter to your kernel boot line? Add it to the GRUB_CMDLINE_LINUX parameter in /etc/default/grub and run update-grub. reboot=pci I don't have a /etc/default/grub on this machine. It seems to be available with grub-pc, but here I have grub-legacy. Perhaps I should use defoptions=quiet reboot=pci After a search on Google, I've found http://linux.koolsolutions.com/2009/08/04/howto-fix-linux-hangfreeze-during-reboots-and-restarts/ where a comment says: Had issues with Dell latitude E6420 had to add reboot=pci to fix the issue -- Vincent Lefèvre vinc...@vinc17.net - Web: http://www.vinc17.net/ 100% accessible validated (X)HTML - Blog: http://www.vinc17.net/blog/ Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120705221901.gz5...@xvii.vinc17.org
Re: Finding missing epochs
On Thu, 2012-07-05 at 23:34 +0200, Jakub Wilk wrote: Package: linux-image-3.2.0-3-486 Suggests: lilo (= 22.8-8.2~) == 1:22.8-8.2~ Package: linux-image-3.2.0-3-686-pae Suggests: lilo (= 22.8-8.2~) == 1:22.8-8.2~ Package: linux-image-3.2.0-3-amd64 Suggests: lilo (= 22.8-8.2~) == 1:22.8-8.2~ Package: linux-image-3.2.0-3-rt-686-pae Suggests: lilo (= 22.8-8.2~) == 1:22.8-8.2~ Wow, how did I miss that one?! We can actually drop the versioned dependency now but it should be fixed in squeeze. Ben. -- Ben Hutchings When in doubt, use brute force. - Ken Thompson signature.asc Description: This is a digitally signed message part
Bug#680467: Versioned Breaks (and Recommends) on lilo is missing epoch
Package: src:linux-2.6 Version: 2.6.32-45 Severity: serious Jakub Wilk spotted that the minimum version number specified for lilo (22.8-8.2~) does not include the epoch (1:), which means that we don't actually require it to be upgraded and #593683 was never fully fixed. Ben. -- System Information: Debian Release: wheezy/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: i386 (x86_64) Foreign Architectures: amd64 Kernel: Linux 3.2.0-3-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120706044909.30373.55180.report...@deadeye.wl.decadent.org.uk
Processed: tagging 680467
Processing commands for cont...@bugs.debian.org: tags 680467 + pending Bug #680467 [src:linux-2.6] Versioned Breaks (and Recommends) on lilo is missing epoch Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 680467: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680467 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.134155106019735.transcr...@bugs.debian.org
Bug#679750: Lenovo G360: ALPS Touchpad Recognized as PS/2 Generic Mouse(with newly dmesg information)
On Fri, Jul 06, 2012 at 11:39:42AM +0800, littlebat wrote:
I found these lines in my dmesg information:
[ 19.995850] psmouse serio4: alps: E6 report: 00 00 64
[ 20.021288] psmouse serio4: alps: E7 report: 73 03 50
[ 20.623609] input: PS/2 Generic Mouse
as /devices/platform/i8042/serio4/input/input9
Thanks, this is the information we need to check whether or not your
touchpad uses any of the known ALPS protocols.
I'm attaching a patch to use as a starting point. Basically we're just
going to try each protocol version until either we find one that works
or run out of options. You should have an external mouse available,
because it's likely that your touchpad will not be usable. I've also
heard that some of the workarounds that people use to get the disable
touchpad while typing behavior can cause the touchpad to no longer
function once it starts behaving as a touchpad, so you should look out
for that as well.
I won't be able to respond further until next Monday, but it's pretty
simple to modify the driver to try different protocol versions so I'll
give you some instructions. The patch adds the following line. I've
identified the two fields you'll need to change.
{ { 0x73, 0x03, 0x50 }, 0x8a, ALPS_PROTO_V4, 0x8f, 0x8f, 0 },
^ ^
| |
command_mode_resp |
proto_version
Not surprisingly, to try different protocol versions you just need to
change the proto_version field. Try ALPS_PROTO_V4 first, if that doesn't
work try ALPS_PROTO_V3, etc., until you've tried them all or found one
that works.
The first time you run the patch though you need to be on the lookout
for a message in dmesg that says Unknown command mode response
followed by two hex digits. If you see this then you need to change
command_mode_resp to match the response printed in the message. Be sure
to leave the 0x characters in place; only replace the 8a characters.
Then try the same protocol version again.
The basic test procedure after booting with a test version of the driver
is:
1. Check dmesg for any errors from the alps driver. If you see anything
other than the Unknown command mode response message then it
probably means your touchpad doesn't use that protocol version, so
you should move on to the next one. If the device name isn't showing
up as something with ALPS in it, that also indicates your device
isn't using that version.
2. Thoroughly test the touchpad. You may see erratic behavior -- the
pointer jumping around, random clicks, etc -- which means it's using
a different protocol.
If you find a protocol version that works, let me know and I'll help get
it added to the driver. If you don't then there's not much more I can do
to help without hardware.
Seth
diff --git a/drivers/input/mouse/alps.c b/drivers/input/mouse/alps.c
index 4c6a72d..979339c 100644
--- a/drivers/input/mouse/alps.c
+++ b/drivers/input/mouse/alps.c
@@ -15,6 +15,8 @@
* the Free Software Foundation.
*/
+#define DEBUG
+
#include linux/slab.h
#include linux/input.h
#include linux/input/mt.h
@@ -112,6 +114,7 @@ static const struct alps_model_info alps_model_data[] = {
{ { 0x73, 0x02, 0x64 }, 0x9b, ALPS_PROTO_V3, 0x8f, 0x8f, ALPS_DUALPOINT },
{ { 0x73, 0x02, 0x64 }, 0x9d, ALPS_PROTO_V3, 0x8f, 0x8f, ALPS_DUALPOINT },
{ { 0x73, 0x02, 0x64 }, 0x8a, ALPS_PROTO_V4, 0x8f, 0x8f, 0 },
+ { { 0x73, 0x03, 0x50 }, 0x8a, ALPS_PROTO_V4, 0x8f, 0x8f, 0 },
};
/*
Processed: tagging 680467
Processing commands for cont...@bugs.debian.org: tags 680467 + squeeze Bug #680467 [src:linux-2.6] Versioned Breaks (and Recommends) on lilo is missing epoch Added tag(s) squeeze. thanks Stopping processing here. Please contact me if you need assistance. -- 680467: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680467 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.134155165322401.transcr...@bugs.debian.org
