Bug#655314: linux-image-3.1.0-1-amd64: ICMPv6 debugging message
Package: linux-2.6 Version: 3.1.6-1 Severity: normal Tags: ipv6 I'm running a Teredo relay/server using miredo-server and the system logs are being filled with this message: Jan 10 09:24:33 6to4 kernel: [93060.760149] icmpv6_send: no reply to icmp error Jan 10 09:24:42 6to4 kernel: [93069.812879] icmpv6_send: no reply to icmp error This message is generated when the kernel feels it should send an ICMP error for a packet that itself was an ICMP error. RFC says that you don't send errors for errors, so it's dropped, but the developers have decided to put a debugging message in that if-branch. Normally that debugging message should never be displayed, because under normal server conditions it should never occur. However, due to the way Teredo works, this can and will happen quite often. Would it be possible to remove or comment out this particular debuggin message, because on normal servers it has no value and on Teredo servers ... well ... it has no value either but it fills the logs. Or if it can't be removed, it should be possible to turn it on and off using some sysctl. -- Package-specific info: ** Kernel log: boot messages should be attached -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages linux-image-3.1.0-1-amd64 depends on: ii debconf [debconf-2.0] 1.5.41 ii initramfs-tools [linux-initramfs-tool] 0.99 ii linux-base 3.4 ii module-init-tools 3.16-1 Versions of packages linux-image-3.1.0-1-amd64 recommends: ii firmware-linux-free 3 Versions of packages linux-image-3.1.0-1-amd64 suggests: pn grub-pc1.99-14 pn linux-doc-3.1 Versions of packages linux-image-3.1.0-1-amd64 is related to: pn firmware-bnx2 pn firmware-bnx2x pn firmware-ipw2x00 pn firmware-ivtv pn firmware-iwlwifi pn firmware-linux pn firmware-linux-nonfree 0.34 pn firmware-qlogic pn firmware-ralink pn xen-hypervisor -- debconf information excluded -- 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/20120110093458.5046.1240.report...@halli.atm.tut.fi
Processed (with 1 errors): Re: Bug#654876:
Processing commands for cont...@bugs.debian.org: > retitle 654876 CVE-2012-0207: divide error and panic when receiving Bug #654876 {Done: Ben Hutchings } [linux-2.6] "divide error" while receiving from iwlagn 5300, leading to kernel panic Changed Bug title to 'CVE-2012-0207: divide error and panic when receiving' from '"divide error" while receiving from iwlagn 5300, leading to kernel panic' > mixed IGMP queries Unknown command or malformed arguments to command. > thanks Stopping processing here. Please contact me if you need assistance. -- 654876: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=654876 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.132618942114389.transcr...@bugs.debian.org
Re: Bug#648207: Please add support for newest Dell touchpad
I have been using Seth Forshee's patches together with the testing kernels for several month now. They appear to work flawlessly. -- 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/4f0c08bf.5050...@mi.fu-berlin.de
Bug#655316: [arm] Please add patch for A1 revision of Kirkwood 6282 chip
Package: linux-2.6 Version: 2.6.32-38 Severity: minor Please add a87d89e74f0a4b56eaee8c3ef74bce69277b780f to the squeeze kernel so the A1 revision of the Kirkwood 6282 chip is recognized properly. http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commitdiff;h=a87d89e74f0a4b56eaee8c3ef74bce69277b780f Thanks. -- Martin Michlmayr http://www.cyrius.com/ -- 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/20120110101529.ga29...@jirafa.cyrius.com
Re: Re: Bug#648207: Please add support for newest Dell touchpad
... on a Dell Latitude E6510, that is. -- 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/4f0c1607.9050...@mi.fu-berlin.de
Processed: retitle 654876 to CVE-2012-0207: divide error and panic when receiving mixed IGMP queries
Processing commands for cont...@bugs.debian.org: > retitle 654876 CVE-2012-0207: divide error and panic when receiving mixed > IGMP queries Bug #654876 {Done: Ben Hutchings } [linux-2.6] CVE-2012-0207: divide error and panic when receiving Changed Bug title to 'CVE-2012-0207: divide error and panic when receiving mixed IGMP queries' from 'CVE-2012-0207: divide error and panic when receiving' > thanks Stopping processing here. Please contact me if you need assistance. -- 654876: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=654876 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.132619307832005.transcr...@bugs.debian.org
Processed: Re: Bug#601198: mdadm: Says it sets faulty even when it actually doesn't
Processing commands for cont...@bugs.debian.org: > reassign 601198 src:linux-2.6 Bug #601198 [mdadm] mdadm: Says it sets faulty even when it actually doesn't Bug reassigned from package 'mdadm' to 'src:linux-2.6'. Bug No longer marked as found in versions mdadm/3.1.4-1+8efb9d1. > fixed 601198 3.1.0-1 Bug #601198 [src:linux-2.6] mdadm: Says it sets faulty even when it actually doesn't The source linux-2.6 and version do not appear to match any binary packages Bug Marked as fixed in versions linux-2.6/3.1.0-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 601198: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=601198 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.132620324017191.transcr...@bugs.debian.org
Processed: Re: Bug#628668: mdadm: Impossible to clear the write-mostly flag in metadata
Processing commands for cont...@bugs.debian.org: > reassign 628668 src:linux-2.6 Bug #628668 [mdadm] mdadm: Impossible to clear the write-mostly flag in metadata Bug reassigned from package 'mdadm' to 'src:linux-2.6'. Bug No longer marked as found in versions mdadm/3.1.4-1+8efb9d1. > fixed 628668 3.1.0-1 Bug #628668 [src:linux-2.6] mdadm: Impossible to clear the write-mostly flag in metadata The source linux-2.6 and version do not appear to match any binary packages Bug Marked as fixed in versions linux-2.6/3.1.0-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 628668: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=628668 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.132620342517731.transcr...@bugs.debian.org
Bug#655342: linux-patch-debian-3.1: changes only the version number from 3.1.8-1 to 3.1.8-2
Package: linux-patch-debian-3.1 Version: 3.1.8-2 Severity: normal Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? I applied the patch to my source tree (3.1.8-1) * What exactly did you do (or not do) that was effective (or ineffective)? See the previous answer * What was the outcome of this action? Only the version number changed, as mentioned in the subject line * What outcome did you expect instead? Changes in some source programs (I created a tree from the tarball and compared with "diff -r") *** End of the template - remove these lines *** -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-rc7-amd64 (SMP w/4 CPU cores) Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages linux-patch-debian-3.1 depends on: ii bzip2 1.0.6-1 ii linux-support-3.1.0-1 3.1.8-1 ii python 2.7.2-9 linux-patch-debian-3.1 recommends no packages. Versions of packages linux-patch-debian-3.1 suggests: ii linux-source-3.1 3.1.8-1 -- no debconf information -- 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/20120110141040.3308.98708.reportbug@chakravarti
Bug#655344: linux-image-3.1.0-1-kirkwood: Missing support for LaCie machines
Package: linux-2.6 Version: 3.1.6-1 Severity: important Dear Maintainer, The kernel image provided by package linux-image-3.1.0-1-kirkwood don't support the LaCie Kirkwood boards. Please, consider applying the following patch: diff --git a/config/armel/config.kirkwood b/config/armel/config.kirkwood index 1eae313..85b0c64 100644 --- a/config/armel/config.kirkwood +++ b/config/armel/config.kirkwood @@ -63,6 +63,12 @@ CONFIG_MACH_DOCKSTAR=y CONFIG_MACH_OPENRD_BASE=y CONFIG_MACH_OPENRD_CLIENT=y CONFIG_MACH_OPENRD_ULTIMATE=y +CONFIG_MACH_NETSPACE_V2=y +CONFIG_MACH_INETSPACE_V2=y +CONFIG_MACH_NETSPACE_MAX_V2=y +CONFIG_MACH_D2NET_V2=y +CONFIG_MACH_NET2BIG_V2=y +CONFIG_MACH_NET5BIG_V2=y CONFIG_MACH_T5325=y ## @@ -172,6 +178,11 @@ CONFIG_GPIO_SYSFS=y # CONFIG_DRM is not set ## +## file: drivers/hwmon/Kconfig +## +CONFIG_SENSORS_GPIO_FAN=m + +## ## file: drivers/i2c/Kconfig ## CONFIG_I2C=y @@ -244,6 +255,8 @@ CONFIG_ISDN_DIVAS_MAINT=m CONFIG_NEW_LEDS=y CONFIG_LEDS_CLASS=y CONFIG_LEDS_GPIO=y +CONFIG_LEDS_NS2=y +CONFIG_LEDS_NETXBIG=y CONFIG_LEDS_TRIGGERS=y CONFIG_LEDS_TRIGGER_TIMER=y CONFIG_LEDS_TRIGGER_DEFAULT_ON=y Regards, Simon -- Package-specific info: Here are the boot logs: Marvell>> set bootcmd "ext2load ide 0:1 0x80 /boot/uImage-3.1.0-1-kirkwood; ext2load ide 0:1 0x120 /boot/initrd.img-3.1.0-1-kirkwood; setenv bootargs console=ttyS0,115200 initrd=0x120 root=/dev/sda1; bootm 0x80" Marvell>> saveenv Marvell>> run bootcmd ## Valid DOS partition found ## ## Valid DOS partition found ## 1577596 bytes read ## Valid DOS partition found ## ## Valid DOS partition found ## 6559762 bytes read ## Booting image at 0080 ... Image Name: linux-3.1 Created: 2011-11-19 5:20:45 UTC Image Type: ARM Linux Kernel Image (uncompressed) Data Size:1577532 Bytes = 1.5 MB Load Address: 8000 Entry Point: 8000 Verifying Checksum ... OK OK bootargs from environment variables : console=ttyS0,115200 initrd=0x120 root=/dev/sda1 cap=gpt,lba64 Starting kernel ... Uncompressing Linux... done, booting the kernel. Error: unrecognized/unsupported machine ID (r1 = 0x0899). Available machine support: ID (hex)NAME 0690Marvell DB-88F6281-BP Development Board 0691Marvell RD-88F6192-NAS Development Board 0692Marvell RD-88F6281 Reference Board 078cMarvell 88F6281 GTW GE Board 0a76Marvell eSATA SheevaPlug Reference Board 0831Marvell SheevaPlug Reference Board 0a63Marvell GuruPlug Reference Board 0bb6Seagate FreeAgent DockStar 085bQNAP TS-119/TS-219 09c6QNAP TS-41x 0b44Marvell OpenRD Ultimate Board 0939Marvell OpenRD Client Board 0915Marvell OpenRD Base Board 0b1eHP t5325 Thin Client Please check your kernel config and/or bootloader. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: armel (armv5tel) Kernel: Linux 2.6.31.14-g2d85800-dirty Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages linux-image-3.1.0-1-kirkwood depends on: ii debconf [debconf-2.0] 1.5.28 ii initramfs-tools [linux-initramfs-tool] 0.99 ii linux-base 3.4 ii module-init-tools 3.12~pre1-1 Versions of packages linux-image-3.1.0-1-kirkwood recommends: ii firmware-linux-free 3 ii uboot-mkimage2011.12-2 Versions of packages linux-image-3.1.0-1-kirkwood suggests: pn fdutils pn linux-doc-3.1 Versions of packages linux-image-3.1.0-1-kirkwood is related to: pn firmware-bnx2 pn firmware-bnx2x pn firmware-ipw2x00 pn firmware-ivtv pn firmware-iwlwifi pn firmware-linux pn firmware-linux-nonfree pn firmware-qlogic pn firmware-ralink pn xen-hypervisor -- debconf information excluded signature.asc Description: Digital signature
Bug#655342: marked as done (linux-patch-debian-3.1: changes only the version number from 3.1.8-1 to 3.1.8-2)
Your message dated Tue, 10 Jan 2012 15:06:05 + with message-id <1326207965.2930.5.camel@deadeye> and subject line Re: Bug#655342: linux-patch-debian-3.1: changes only the version number from 3.1.8-1 to 3.1.8-2 has caused the Debian Bug report #655342, regarding linux-patch-debian-3.1: changes only the version number from 3.1.8-1 to 3.1.8-2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 655342: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=655342 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-patch-debian-3.1 Version: 3.1.8-2 Severity: normal Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? I applied the patch to my source tree (3.1.8-1) * What exactly did you do (or not do) that was effective (or ineffective)? See the previous answer * What was the outcome of this action? Only the version number changed, as mentioned in the subject line * What outcome did you expect instead? Changes in some source programs (I created a tree from the tarball and compared with "diff -r") *** End of the template - remove these lines *** -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-rc7-amd64 (SMP w/4 CPU cores) Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages linux-patch-debian-3.1 depends on: ii bzip2 1.0.6-1 ii linux-support-3.1.0-1 3.1.8-1 ii python 2.7.2-9 linux-patch-debian-3.1 recommends no packages. Versions of packages linux-patch-debian-3.1 suggests: ii linux-source-3.1 3.1.8-1 -- no debconf information --- End Message --- --- Begin Message --- On Tue, 2012-01-10 at 19:40 +0530, R S Chakravarti wrote: > Package: linux-patch-debian-3.1 > Version: 3.1.8-2 > Severity: normal > > Dear Maintainer, > *** Please consider answering these questions, where appropriate *** > >* What led up to the situation? I applied the patch to my source tree > (3.1.8-1) Unpatch it first. Ben. -- Ben Hutchings Life is what happens to you while you're busy making other plans. - John Lennon signature.asc Description: This is a digitally signed message part --- End Message ---
Bug#655353: XFS lockups on 2.6.32 [task xfssyncd blocked for more than 120 seconds]
Source: linux-2.6 Version: 2.6.32-39 Severity: normal Hello, Since the upgrade from lenny to squeeze I am getting in several servers random kernel lockups related to the XFS filesystem. The errors looks the same on all servers. All servers are running Debian kernel 2.6.32-39 Server 1 running Debian/Squeeze with linux-image-2.6.32-5-686/2.6.32-39 - [539160.520045] INFO: task xfssyncd:985 blocked for more than 120 seconds. [539160.520077] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [539160.520123] xfssyncd D f9197020 0 985 2 0x [539160.520129] c340fb40 0046 f6c32200 f9197020 c141d100 c141d100 c14186ac [539160.520137] c340fcfc c2108100 0001 a0bf 0010 f6a7f280 [539160.520145] c21036ac c340fcfc 0806c251 f6a38b90 0082 [539160.520154] Call Trace: [539160.520179] [] ? schedule_timeout+0x20/0xb0 [539160.520184] [] ? __lookup_tag+0x8e/0xee [539160.520189] [] ? radix_tree_gang_lookup_tag+0x8a/0xd5 [539160.520193] [] ? wait_for_common+0xa4/0x100 [539160.520199] [] ? default_wake_function+0x0/0x8 [539160.520225] [] ? xfs_reclaim_inode+0x85/0xc8 [xfs] [539160.520259] [] ? xfs_inode_ag_walk+0x73/0xbd [xfs] [539160.520280] [] ? xfs_reclaim_inode+0x0/0xc8 [xfs] [539160.520302] [] ? xfs_inode_ag_iterator+0x58/0x8f [xfs] [539160.520324] [] ? xfs_reclaim_inode+0x0/0xc8 [xfs] [539160.520345] [] ? xfs_reclaim_inodes+0x12/0x16 [xfs] [539160.520367] [] ? xfs_sync_worker+0x23/0x5c [xfs] [539160.520388] [] ? xfssyncd+0x134/0x17d [xfs] [539160.520410] [] ? xfssyncd+0x0/0x17d [xfs] [539160.520415] [] ? kthread+0x61/0x66 [539160.520418] [] ? kthread+0x0/0x66 [539160.520423] [] ? kernel_thread_helper+0x7/0x10 Server 2 running Debian/Squeeze with linux-image-2.6.32-5-vserver-amd64/2.6.32-39 - [864600.444518] INFO: task xfssyncd:933 blocked for more than 120 seconds. [864600.444563] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [864600.444608] xfssyncd D 0 933 2 0x [864600.444612] 88022f06b980 0046 880050925e40 [864600.444617] 2000 8118af2b f9e0 88022c607fd8 [864600.444620] 00015780 00015780 88022f195640 88022f195938 [864600.444625] Call Trace: [864600.444632] [] ? generic_make_request+0x299/0x2f9 [864600.444637] [] ? schedule_timeout+0x2e/0xdd [864600.444659] [] ? _xfs_buf_ioapply+0x204/0x22f [xfs] [864600.444663] [] ? __lookup_tag+0xad/0x11b [864600.444666] [] ? wait_for_common+0xde/0x15b [864600.444671] [] ? default_wake_function+0x0/0x9 [864600.444685] [] ? xfs_reclaim_inode+0x95/0xe0 [xfs] [864600.444698] [] ? xfs_inode_ag_walk+0x92/0xef [xfs] [864600.444711] [] ? xfs_reclaim_inode+0x0/0xe0 [xfs] [864600.444724] [] ? xfs_inode_ag_iterator+0x71/0xb2 [xfs] [864600.444737] [] ? xfs_reclaim_inode+0x0/0xe0 [xfs] [864600.444751] [] ? xfs_sync_worker+0x26/0x5f [xfs] [864600.444764] [] ? xfssyncd+0x150/0x1bb [xfs] [864600.444777] [] ? xfssyncd+0x0/0x1bb [xfs] [864600.444780] [] ? kthread+0x79/0x81 [864600.444784] [] ? child_rip+0xa/0x20 [864600.444788] [] ? generic_unplug_device+0x0/0x34 [864600.444791] [] ? kthread+0x0/0x81 [864600.444794] [] ? child_rip+0x0/0x20 Server 3 running Debian/Squeeze with linux-image-2.6.32-5-vserver-amd64/2.6.32-39 - [ 5520.764046] INFO: task xfssyncd:1376 blocked for more than 120 seconds. [ 5520.764080] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 5520.764126] xfssyncd D 0 1376 2 0x [ 5520.764132] 88007fb5d640 0046 88001f342540 [ 5520.764138] 00ff 8118af2b f9e0 88007e291fd8 [ 5520.764143] 00015780 00015780 880037baab20 880037baae18 [ 5520.764148] Call Trace: [ 5520.764159] [] ? generic_make_request+0x299/0x2f9 [ 5520.764166] [] ? schedule_timeout+0x2e/0xdd [ 5520.764200] [] ? _xfs_buf_ioapply+0x204/0x22f [xfs] [ 5520.764205] [] ? __lookup_tag+0xad/0x11b [ 5520.764210] [] ? wait_for_common+0xde/0x15b [ 5520.764216] [] ? default_wake_function+0x0/0x9 [ 5520.764234] [] ? xfs_reclaim_inode+0x95/0xe0 [xfs] [ 5520.764251] [] ? xfs_inode_ag_walk+0x92/0xef [xfs] [ 5520.764268] [] ? xfs_reclaim_inode+0x0/0xe0 [xfs] [ 5520.764285] [] ? xfs_inode_ag_iterator+0x71/0xb2 [xfs] [ 5520.764301] [] ? xfs_reclaim_inode+0x0/0xe0 [xfs] [ 5520.764318] [] ? xfs_sync_worker+0x26/0x5f [xfs] [ 5520.764335] [] ? xfssyncd+0x150/0x1bb [xfs] [ 5520.764351] [] ? xfssyncd+0x0/0x1bb [xfs] [ 5520.764356] [] ? kthread+0x79/0x81 [ 5520.764362]
Processed: reassign bug
Processing commands for cont...@bugs.debian.org: > reassign 646117 linux-2.6 2.6.32-38 Bug #646117 [bluez] bluez: Kernel bug at bluetooth/rfcomm/tty.c:96 Bug reassigned from package 'bluez' to 'linux-2.6'. Bug No longer marked as found in versions bluez/4.66-3. Bug #646117 [linux-2.6] bluez: Kernel bug at bluetooth/rfcomm/tty.c:96 There is no source info for the package 'linux-2.6' at version '2.6.32-38' with architecture '' Unable to make a source version for version '2.6.32-38' Bug Marked as found in versions 2.6.32-38. > thanks Stopping processing here. Please contact me if you need assistance. -- 646117: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=646117 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.132621900331325.transcr...@bugs.debian.org
Bug#655377: Kernel panic when turning off screen backlight using laptop Fn key since 3.1 (has patch)
Package: linux-image-3.1.0-1-amd64 Version: 3.1.6-1 Hello, there's patch available to fix the kernel panic when 'turning off screen backlight' which me and other people experienced (on various distros including debian testing on lenovo). Link to issue/patch: https://lkml.org/lkml/2011/10/19/485 includes link to the PATCH in the bottom. Thanks - Debian Testing installed 10 january 2012 on lenovo g series laptop -- 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/CAFVLVSNZ0dU_UTh_hLpYzH9u2H-nYF=5lqbdfi8f6+0fmhp...@mail.gmail.com
Bug#655377:
Patch also could be related to i386 architecture too IIRC. -- 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/CAFVLVSPFiCD0rwPB_VPXdv0eoyCTp2VK=wtNDfrVHaL=gfy...@mail.gmail.com
Bug#655377: [?? -> 3.1.6 regression] Kernel panic when turning off screen backlight using laptop Fn key
retitle 655377 [ideapad_laptop] NULL pointer dereference turning off backlight with fn key # regression severity 655377 important tags 655377 + upstream fixed-upstream reassign 655377 src:linux-2.6 3.1.6-1 quit Hi, Artem X wrote: > Hello, there's patch available to fix the kernel panic when 'turning > off screen backlight' > which me and other people experienced (on various distros including > debian testing on lenovo). Might be fixed by v3.2-rc1~111^2~22 (ideapad: Check if acpi already handle backlight power to avoid a page fault, 2011-10-23). Could you try a 3.2.y release candidate from experimental to check? Thanks, Jonathan -- 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/20120110194046.GF22184@burratino
Processed: Re: [?? -> 3.1.6 regression] Kernel panic when turning off screen backlight using laptop Fn key
Processing commands for cont...@bugs.debian.org: > retitle 655377 [ideapad_laptop] NULL pointer dereference turning off > backlight with fn key Bug #655377 [linux-image-3.1.0-1-amd64] Kernel panic when turning off screen backlight using laptop Fn key since 3.1 (has patch) Changed Bug title to '[ideapad_laptop] NULL pointer dereference turning off backlight with fn key' from 'Kernel panic when turning off screen backlight using laptop Fn key since 3.1 (has patch)' > # regression > severity 655377 important Bug #655377 [linux-image-3.1.0-1-amd64] [ideapad_laptop] NULL pointer dereference turning off backlight with fn key Severity set to 'important' from 'normal' > tags 655377 + upstream fixed-upstream Bug #655377 [linux-image-3.1.0-1-amd64] [ideapad_laptop] NULL pointer dereference turning off backlight with fn key Added tag(s) upstream and fixed-upstream. > reassign 655377 src:linux-2.6 3.1.6-1 Bug #655377 [linux-image-3.1.0-1-amd64] [ideapad_laptop] NULL pointer dereference turning off backlight with fn key Bug reassigned from package 'linux-image-3.1.0-1-amd64' to 'src:linux-2.6'. Bug No longer marked as found in versions linux-2.6/3.1.6-1. Bug #655377 [src:linux-2.6] [ideapad_laptop] NULL pointer dereference turning off backlight with fn key Bug Marked as found in versions linux-2.6/3.1.6-1. > quit Stopping processing here. Please contact me if you need assistance. -- 655377: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=655377 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.132622415227581.transcr...@bugs.debian.org
Bug#602956: nfs-kernel-server: not limited to ext4
Subject: nfs-kernel-server: not limited to ext4 Followup-For: Bug #602956 Package: nfs-kernel-server Version: 1:1.2.5-3 Dear Maintainer, I have experienced this error with ubifs rootfs (on the NAND of the SheevaPlug). /etc/exports: / 192.168.0.0/24(ro,sync,subtree_check) #exportfs -a 'exportfs: Warning: / does not support NFS export.' $mount ubi0:rootfs on / type ubifs (rw,relatime) -- Package-specific info: -- rpcinfo -- program vers proto port service 104 tcp111 portmapper 103 tcp111 portmapper 102 tcp111 portmapper 104 udp111 portmapper 103 udp111 portmapper 102 udp111 portmapper 3910022 tcp 1005 sgi_fam 1000241 udp 39957 status 1000241 tcp 50068 status 132 tcp 2049 nfs 133 tcp 2049 nfs 134 tcp 2049 nfs 132 udp 2049 nfs 133 udp 2049 nfs 134 udp 2049 nfs 1000211 udp 50431 nlockmgr 1000213 udp 50431 nlockmgr 1000214 udp 50431 nlockmgr 1000211 tcp 44568 nlockmgr 1000213 tcp 44568 nlockmgr 1000214 tcp 44568 nlockmgr 151 udp 48987 mountd 151 tcp 43941 mountd 152 udp 54945 mountd 152 tcp 45423 mountd 153 udp 50490 mountd 153 tcp 54109 mountd -- /etc/default/nfs-kernel-server -- RPCNFSDCOUNT=8 RPCNFSDPRIORITY=0 RPCMOUNTDOPTS=--manage-gids NEED_SVCGSSD= RPCSVCGSSDOPTS= -- /etc/exports -- / 192.168.0.0/24(ro,sync,subtree_check) -- /proc/fs/nfs/exports -- # Version 1.1 # Path Client(Flags) # IPs -- System Information: Debian Release: wheezy/sid APT prefers unstable-grip APT policy: (500, 'unstable-grip'), (500, 'testing-grip'), (500, 'testing') Architecture: armel (armv5tel) Kernel: Linux 3.2.0-1-ga042133-dirty (PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages nfs-kernel-server depends on: ii libblkid1 2.19.1-5em1 ii libc6 2.13-21em1 ii libcomerr21.42~WIP-2011-10-16-1em1 ii libgssapi-krb5-2 1.10+dfsg~alpha2-1 ii libgssglue1 0.3-3.1em1 ii libk5crypto3 1.10+dfsg~alpha2-1 ii libkrb5-3 1.10+dfsg~alpha2-1 ii libnfsidmap2 0.25-1em1 ii libtirpc1 0.2.2-5em1 ii libwrap0 7.6.q-21em1 ii lsb-base 3.2-28em1 ii nfs-common1:1.2.5-3 ii ucf 3.0025+nmu2em1 nfs-kernel-server recommends no packages. nfs-kernel-server suggests no packages. -- no debconf information -- 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/4913923.Cz9kbPvJR4@ubuntu-sd
Bug#655385: linux-image-2.6.32-5-openvz-amd64: "Cannot allocate memory" when doing "cat /proc/self/mountinfo" inside a vm
Package: linux-2.6 Version: 2.6.32-38 Severity: important When doing a "cat /proc/self/mountinfo" inside a guest the result is "Cannot allocate memory". What really makes it evil: the page cache of the whole machine is flushed and all swap space available consumed. This effectively causes the whole system to freeze because of the high load / disk io. -- Package-specific info: ** Version: Linux version 2.6.32-5-openvz-amd64 (Debian 2.6.32-38) (b...@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Mon Oct 3 05:12:50 UTC 2011 ** Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-openvz-amd64 root=UUID=1924430b-93b2-4781-b1bb-6281966c64fc ro quiet ** Tainted: W (512) * Taint on warning. ** Kernel log: [1.954245] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 [1.954260] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [1.954371] sda: sda1 sda2 < sda5 > [1.955496] sd 0:0:0:0: [sda] Attached SCSI disk [2.043616] e1000: :00:08.0: e1000_probe: (PCI:33MHz:32-bit) 08:00:27:29:8c:5c [2.094618] e1000: eth1: e1000_probe: Intel(R) PRO/1000 Network Connection [2.094726] alloc irq_desc for 22 on node -1 [2.094731] alloc kstat_irqs on node -1 [2.094769] ohci_hcd :00:06.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22 [2.094817] ohci_hcd :00:06.0: OHCI Host Controller [2.094832] ohci_hcd :00:06.0: new USB bus registered, assigned bus number 2 [2.094906] ohci_hcd :00:06.0: irq 22, io mem 0xf0804000 [2.150065] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001 [2.150080] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [2.150088] usb usb2: Product: OHCI Host Controller [2.150093] usb usb2: Manufacturer: Linux 2.6.32-5-openvz-amd64 ohci_hcd [2.150100] usb usb2: SerialNumber: :00:06.0 [2.150345] usb usb2: configuration #1 chosen from 1 choice [2.150430] hub 2-0:1.0: USB hub found [2.150502] hub 2-0:1.0: 8 ports detected [2.286615] PM: Starting manual resume from disk [2.286620] PM: Resume from partition 8:5 [2.286622] PM: Checking hibernation image. [2.286770] PM: Error -22 checking image file [2.286773] PM: Resume from disk failed. [2.306573] kjournald starting. Commit interval 5 seconds [2.306650] EXT3-fs: mounted filesystem with ordered data mode. [2.561494] usb 2-1: new full speed USB device using ohci_hcd and address 2 [2.606712] udev[288]: starting version 164 [2.684580] processor LNXCPU:00: registered as cooling_device0 [2.684580] processor LNXCPU:01: registered as cooling_device1 [2.684607] processor LNXCPU:02: registered as cooling_device2 [2.684647] processor LNXCPU:03: registered as cooling_device3 [2.684715] processor LNXCPU:04: registered as cooling_device4 [2.684720] processor LNXCPU:05: registered as cooling_device5 [2.684756] processor LNXCPU:06: registered as cooling_device6 [2.684796] processor LNXCPU:07: registered as cooling_device7 [2.686623] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 [2.686630] ACPI: Power Button [PWRF] [2.686704] input: Sleep Button as /devices/LNXSYSTM:00/LNXSLPBN:00/input/input3 [2.686714] ACPI: Sleep Button [SLPF] [2.691095] ACPI: AC Adapter [AC] (on-line) [2.692524] ACPI: Battery Slot [BAT0] (battery present) [2.701210] input: PC Speaker as /devices/platform/pcspkr/input/input4 [2.701866] piix4_smbus :00:07.0: SMBus base address uninitialized - upgrade BIOS or use force_addr=0xaddr [2.705098] parport_pc 00:04: reported by Plug and Play ACPI [2.732204] input: ImExPS/2 Generic Explorer Mouse as /devices/platform/i8042/serio1/input/input5 [2.759987] Error: Driver 'pcspkr' is already registered, aborting... [2.828204] usb 2-1: New USB device found, idVendor=80ee, idProduct=0021 [2.828231] usb 2-1: New USB device strings: Mfr=1, Product=3, SerialNumber=0 [2.828238] usb 2-1: Product: USB Tablet [2.828243] usb 2-1: Manufacturer: VirtualBox [2.828515] usb 2-1: configuration #1 chosen from 1 choice [2.858372] usbcore: registered new interface driver hiddev [2.873203] input: VirtualBox USB Tablet as /devices/pci:00/:00:06.0/usb2/2-1/2-1:1.0/input/input6 [2.873366] generic-usb 0003:80EE:0021.0001: input,hidraw0: USB HID v1.10 Mouse [VirtualBox USB Tablet] on usb-:00:06.0-1/input0 [2.873450] usbcore: registered new interface driver usbhid [2.873462] usbhid: v2.6:USB HID core driver [3.167371] Adding 477176k swap on /dev/sda5. Priority:-1 extents:1 across:477176k [3.245533] EXT3 FS on sda1, internal journal [3.293283] loop: module loaded [3.808534] e1000: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX [3.816591] e1000: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX [3.816981] ADDRCONF(NETDEV_UP): eth1: link is not ready [3.819172] ADDRCONF(NETDEV_CHANG
Bug#655377: [3.0 -> 3.1 regression] Kernel panic when turning off screen backlight using laptop Fn key
tags 655377 + patch moreinfo quit Jonathan Nieder wrote: > Artem X wrote: >> Hello, there's patch available to fix the kernel panic when 'turning >> off screen backlight' >> which me and other people experienced (on various distros including >> debian testing on lenovo). > > Might be fixed by v3.2-rc1~111^2~22 (ideapad: Check if acpi already > handle backlight power to avoid a page fault, 2011-10-23). Could you > try a 3.2.y release candidate from experimental to check? Even better, please try this patch against a 3.1.y kernel.org kernel. Instructions for testing a patched kernel are at [1]. If it works, we can send it to Greg to consider applying to the 3.1.y branch. Luckily the ideapad-laptop backlight driver was only introduced in v3.1-rc1~14^2~29, so older kernels do not have this bug. Many thanks, Jonathan [1] http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-kernel-org-package -- >8 -- From: Rene Bollford Date: Sun, 23 Oct 2011 09:56:42 +0200 Subject: ideapad: Check if acpi already handle backlight power to avoid a page fault commit d4afc7754a60b885b63ef23fd194984e2d53a4e6 upstream. This patch avoid a page fault in the ideapad-laptop extras when turning the backlight power on or off. Signed-off-by: Rene Bolldorf Signed-off-by: Matthew Garrett Signed-off-by: Jonathan Nieder --- drivers/platform/x86/ideapad-laptop.c |2 ++ 1 files changed, 2 insertions(+), 0 deletions(-) diff --git a/drivers/platform/x86/ideapad-laptop.c b/drivers/platform/x86/ideapad-laptop.c index 0c595410e788..0d94eec00f4d 100644 --- a/drivers/platform/x86/ideapad-laptop.c +++ b/drivers/platform/x86/ideapad-laptop.c @@ -493,6 +493,8 @@ static void ideapad_backlight_notify_power(struct ideapad_private *priv) unsigned long power; struct backlight_device *blightdev = priv->blightdev; + if (!blightdev) + return; if (read_ec_data(ideapad_handle, 0x18, &power)) return; blightdev->props.power = power ? FB_BLANK_UNBLANK : FB_BLANK_POWERDOWN; -- 1.7.8.3 -- 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/20120110201508.GG22184@burratino
Processed: Re: [3.0 -> 3.1 regression] Kernel panic when turning off screen backlight using laptop Fn key
Processing commands for cont...@bugs.debian.org: > tags 655377 + patch moreinfo Bug #655377 [src:linux-2.6] [ideapad_laptop] NULL pointer dereference turning off backlight with fn key Added tag(s) moreinfo and patch. > quit Stopping processing here. Please contact me if you need assistance. -- 655377: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=655377 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.13262262175115.transcr...@bugs.debian.org
Bug#655387: Samsung galaxy S won't tether trough usb due to bad CDC descriptors
Iker Salmón San Millán wrote: > This bug affects all kernels i've tried in debian wheezy, sid and > experimental, I found a bug report in ubuntu where i found this patch that > solves the problem, but the user who wrote the patch described it as > workaroung instead of fix: Link, please. Also, could you describe the symptoms further? What steps would I perform to reproduce the bug if I had the hardware, what are the expected and actual results, and how does the difference indicate a bug? Thanks for your work, Jonathan -- 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/20120110202107.GH22184@burratino
Bug#655387: Samsung galaxy S won't tether trough usb due to bad CDC descriptors
El 10 de enero de 2012 21:21, Jonathan Nieder escribió: > Iker Salmón San Millán wrote: > > > This bug affects all kernels i've tried in debian wheezy, sid and > > experimental, I found a bug report in ubuntu where i found this patch > that > > solves the problem, but the user who wrote the patch described it as > > workaroung instead of fix: > > Link, please. > > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/796006 > Also, could you describe the symptoms further? What steps would I > perform to reproduce the bug if I had the hardware, what are the > expected and actual results, and how does the difference indicate a > bug? > > If you connect the samsung galaxy S (i know also SII is affected) to the usb hub and activate usb tethering it won't create usb0 interface and dmesg shows this: [ 509.033511] usb 2-2: USB disconnect, device number 5 [ 509.304059] usb 2-2: new high-speed USB device number 6 using ehci_hcd [ 509.438155] usb 2-2: New USB device found, idVendor=04e8, idProduct=6881 [ 509.438165] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 509.438172] usb 2-2: Product: SAMSUNG_Android [ 509.438178] usb 2-2: Manufacturer: SAMSUNG [ 509.438183] usb 2-2: SerialNumber: 353271BC9D8400EC [ 509.743606] usbcore: registered new interface driver cdc_ether [ 509.745205] usb 2-2: bad CDC descriptors [ 509.745231] usbcore: registered new interface driver rndis_host [ 509.753788] usb 2-2: bad CDC descriptors [ 509.753821] usbcore: registered new interface driver rndis_wlan If you apply the patch and rebuild the kernel the usb0 interface is created correctly when you activate usb tether. I don't know what else can i comment, surely there are people much more prepared than me to report this things, but i'll try my best if you ask me something or ask me tro try anything > Thanks for your work, > Jonathan > No, Thanks for yours Iker
Bug#655377:
>Could you try a 3.2.y release candidate from experimental to check? This issue is fixed for me in 3.2.0-rc7-amd64 in experimental. --- 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/cafvlvsprrg4dp0bwcfa2-t0_qyuzkjyqrlkfz-mey6p+o-r...@mail.gmail.com
Bug#655377:
Do i really need vanilla kernel? Or can i apply that patch to debian testing kernel 3.1.0 by using "9.7.5. Compiling the kernel source: Debian standard method" in debian reference? -- 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/cafvlvsokj7wrxto_o-ofts4ugpg4eva6sza3ncps+kamach...@mail.gmail.com
Bug#655377: [ideapad_laptop] NULL pointer dereference turning off backlight with fn key
Artem X wrote: > Or can i apply that patch to debian testing kernel 3.1.0 by using > "9.7.5. Compiling the kernel source: Debian standard method" in debian > reference? That's almost as good, sure. -- 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/20120110205939.GK22184@burratino
Bug#655377: marked as done ([ideapad_laptop] NULL pointer dereference turning off backlight with fn key)
Your message dated Tue, 10 Jan 2012 14:58:50 -0600 with message-id <20120110205850.GJ22184@burratino> and subject line Re: [ideapad_laptop] NULL pointer dereference turning off backlight with fn key has caused the Debian Bug report #655377, regarding [ideapad_laptop] NULL pointer dereference turning off backlight with fn key to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 655377: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=655377 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-image-3.1.0-1-amd64 Version: 3.1.6-1 Hello, there's patch available to fix the kernel panic when 'turning off screen backlight' which me and other people experienced (on various distros including debian testing on lenovo). Link to issue/patch: https://lkml.org/lkml/2011/10/19/485 includes link to the PATCH in the bottom. Thanks - Debian Testing installed 10 january 2012 on lenovo g series laptop --- End Message --- --- Begin Message --- Version: 3.2~rc7-1~experimental.1 Artem X wrote: >> Could you try a 3.2.y release candidate from experimental to check? > > This issue is fixed for me in 3.2.0-rc7-amd64 in experimental. Yay. :) Marking accordingly. --- End Message ---
Processed: Re: Samsung galaxy S won't tether trough usb due to bad CDC descriptors
Processing commands for cont...@bugs.debian.org: > forwarded 655387 http://thread.gmane.org/gmane.linux.usb.general/56830 Bug #655387 [linux-2.6] Samsung galaxy S won't tether trough usb due to bad CDC descriptors Set Bug forwarded-to-address to 'http://thread.gmane.org/gmane.linux.usb.general/56830'. > End of message, stopping processing here. Please contact me if you need assistance. -- 655387: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=655387 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.132623072328107.transcr...@bugs.debian.org
Processed: Re: Samsung Galaxy S won't tether through USB due to bad CDC descriptors
Processing commands for cont...@bugs.debian.org: > tags 655387 + upstream - patch Bug #655387 [linux-2.6] Samsung galaxy S won't tether trough usb due to bad CDC descriptors Added tag(s) upstream. Bug #655387 [linux-2.6] Samsung galaxy S won't tether trough usb due to bad CDC descriptors Removed tag(s) patch. > End of message, stopping processing here. Please contact me if you need assistance. -- 655387: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=655387 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.132623122731302.transcr...@bugs.debian.org
Bug#655404: firmware-linux-nonfree Radeon R300-family problem
Package: firmware-linux-nonfree Version: 0.34 Severity: low Hi there, I recently tried to install a couple distributions on a Fujitsu Amilo M 1420 laptop. Kubuntu 11.10, Fedora 16 and PCLinuxOS KDE 2011 all crashed either during install or when booting the installed system. Debian Squeeze installed fine. Until I installed the firmware-linux-nonfree package to get rid of the missing microcode error message from xorg. If firmware-linux-nonfree is installed under Wheezy the system won't boot properly. In Squeeze it is still possible to remove the firmware-linux-nonfree package and reboot, but you first have to stop the error messages spamming the console. X11 won't work at all. Trying to use it will lock the machine. This problem could be related to the Xorg-Radeon driver as well as a hardware bug in either the ATI Mobility Radeon 9600 PRO (RV350) chip generally, of this particular laptop or even this very machine. Nonetheless, removing or not installing firmware-linux-nonfree is my current workaround. The graphics still work fine. thx, Malte -- 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/4f0cafda.6000...@2c2.de
Bug#655387: [PATCH] usb: cdc_ether: Ignore bogus union descriptor for RNDIS devices
Some RNDIS devices include a bogus CDC Union descriptor pointing to non-existing interfaces. The RNDIS code is already prepared to handle devices without a CDC Union descriptor, so we can just ignore it. Cc: Markus Kolb Cc: Iker Salmón San Millán Cc: Jonathan Nieder Cc: Oliver Neukum Cc: 655...@bugs.debian.org Cc: sta...@vger.kernel.org Signed-off-by: Bjørn Mork --- How about this, which IMHO is less intrusive? Only build-tested, as I don't have any of the failing devices, so it will obviously need testing from anyone with such a device. drivers/net/usb/cdc_ether.c | 10 +- 1 files changed, 9 insertions(+), 1 deletions(-) diff --git a/drivers/net/usb/cdc_ether.c b/drivers/net/usb/cdc_ether.c index 41a61ef..2109f34 100644 --- a/drivers/net/usb/cdc_ether.c +++ b/drivers/net/usb/cdc_ether.c @@ -195,7 +195,15 @@ int usbnet_generic_cdc_bind(struct usbnet *dev, struct usb_interface *intf) info->control, info->u->bSlaveInterface0, info->data); - goto bad_desc; + /* Fallback to guessing for rndis +* class devices with bogus union +* descriptor. +* Fixes some Samsung Android devices +*/ + if (rndis) + info->u = NULL; + else + goto bad_desc; } if (info->control != intf) { dev_dbg(&intf->dev, "bogus CDC Union\n"); -- 1.7.7.3 -- 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/1326233716-11083-1-git-send-email-bj...@mork.no
Re: [Fwd: Latest kernel stable/longterm status]
Am 10.01.2012 02:42, schrieb Ben Hutchings: We need to make a decision soon on whether we will use Linux 3.2 for wheezy or wait for a later release. Whichever one we choose, we need to make sure someone (possibly one of us) maintains a longterm branch for it. I am strongly disinclined to choose a version that puts us on our own, and therefore I would prefer to use Linux 3.2 along with Ubuntu. Hi, I'm just a user, but using 3.2 along with Ubuntu LTS looks more than reasonable to me. Unfortunatly, upstream maintains only 3.0. Is there any longterm version beyond 3.0 in sight, which might be an adequate alternative for Wheezy? If not, the sum of Debian/UbuntuLTS installations should have a critical mass to justify the maintenance of a 3.2-DEBline on their own without offcial "support" from upstream. Regards, Marcus Forwarded Message From: Greg KH To: linux-ker...@vger.kernel.org Cc: sta...@vger.kernel.org Subject: Latest kernel stable/longterm status Date: Mon, 9 Jan 2012 16:37:05 -0800 As 3.2 is now out, here's a note as to the current status of the different stable/longterm kernel trees. First off, please everyone remember to mark any patch that you want to have applied to the stable kernel trees with a simple: Cc: stable marking in the Signed-off-by: area. Once the patch hits Linus's tree, I will automatically be notified of it and it will be applied if possible. If it does not applied, you will be notified of that. Note that the address is sta...@vger.kernel.org, not the older address that used to be used before October of 2011. At this time, all stable and longterm kernel trees are being maintained in one big git tree, located at: git.kernel.org:/pub/scm/linux/kernel/git/stable/linux-stable.git There are different branches for every different major kernel version. Here's the different active kernel versions that I am maintaining at the moment: 3.2.y - this will be maintained until 3.3 comes out 3.1.y - there will be only one, maybe two, more releases of this tree 3.0.y - this is the new "longterm" kernel release, it will be maintained for 2 years at the minimum by me. 2.6.32.y - this is the previous "longterm" kernel release. It is approaching it's end-of-life, and I think I only have another month or so doing releases of this. After I am finished with it, it might be picked up by someone else, but I'm not going to promise anything. All other longterm kernels are being maintained in various forms (usually quite sporadically, if at all), by other people, and I can not speak for their lifetime at all, that is up to those individuals. If anyone has any questions about any of this, please let me know. thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html -- 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/4f0cbfb2.20...@googlemail.com
Bug#649626: [agnonc...@yandex.ru: Re: iwl3945: Microcode SW error detected. Restarting 0x82000008]
Agnonchik wrote: > I REPRODUCED exactly the same error in 2.6.32-5-686-bigmem. That's what I did: Thanks! Forwarding to the bug log. --- Begin Message --- Hi Jonathan, 08.01.2012, 21:31, "Jonathan Nieder" : > Hi Agnonchik, > > Agnonchik wrote: >> I'll test. How can I install 2.6.32-40? > [...] >> My /etc/apt/sources.list points to >> deb http://ftp.de.debian.org/debian/ testing main contrib non-free >> # apt-cache search linux-image-2.6.32 >> gives >> linux-image-2.6.32-trunk-686-bigmem - Linux 2.6.32 for PCs with 4GB+ RAM > One way is to temporarily add > > deb http://ftp.de.debian.org/debian/ stable-proposed-updates main > > to /etc/apt/sources.list and run > > apt-get update > apt-get install linux-image-2.6.32-5-686-bigmem > > Thanks, > Jonathan I REPRODUCED exactly the same error in 2.6.32-5-686-bigmem. That's what I did: Added stable-proposed-updates to /etc/apt/sources.list # apt-get update gave a warning: W: Conflicting distribution: http://ftp.de.debian.org stable-proposed-updates InRelease (expected stable-proposed-updates but got squeeze-proposed-updates) # apt-get install linux-image-2.6.32-5-686-bigmem worked fine, except a couple of dkms modules which need kernel headers. I tried to install linux-headers-2.6.32-5-686-bigmem but fauiled because the package depends on gcc-4.3 which appeared to be not installable on my system. I wonder if gcc-4.4 can be accepted instead of 4.3? Nevertheless, the kernel is installed. Though nvidia and virtualbox drivers are missed, they are not so important for debugging I think. I can observe that wi-fi connection is broken with 2 minutes or so period. The strange microcode SW error is issued each time. I can debug further if it makes any sense for the community. Thanks, Val. --- End Message ---
Bug#649626: iwl3945: Microcode SW error detected. Restarting 0x82000008
found 649626 linux-2.6/2.6.32-40 quit Agnonchik wrote: > I REPRODUCED exactly the same error in 2.6.32-5-686-bigmem. That's > what I did: > > Added stable-proposed-updates to /etc/apt/sources.list [...] > worked fine, except a couple of dkms modules which need kernel > headers. I tried to install linux-headers-2.6.32-5-686-bigmem but > fauiled because the package depends on gcc-4.3 which appeared to be > not installable on my system. I wonder if gcc-4.4 can be accepted > instead of 4.3? > > Nevertheless, the kernel is installed. Though nvidia and virtualbox > drivers are missed, they are not so important for debugging I think. > > I can observe that wi-fi connection is broken with 2 minutes or so > period. The strange microcode SW error is issued each time. Drat. Thanks very much for checking. > I can debug further if it makes any sense for the community. A few directions for that: - What version of the firmware-iwlwifi package do you have installed? Is the behavior any different if you update it? - If you have time for it, please try some kernels halfway between from the list at [1] so we can discover which one introduced the fix. If a 3.0-rc2 or newer kernel reproduces the problem, a log would also be helpful, since the output for microcode errors was improved. - You said you are only able to reproduce this with network-manager and not ifupdown. Can you reproduce it using iw and iproute by hand, like this? /etc/init.d/NetworkManager stop ip link set wlan0 up iw dev wlan0 connect -w key d:0: dhclient wlan0 This would help us get help from upstream. Thanks, Jonathan [1] http://snapshot.debian.org/package/linux-2.6/ -- 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/20120110232120.GQ22184@burratino
Processed: Re: iwl3945: Microcode SW error detected. Restarting 0x82000008
Processing commands for cont...@bugs.debian.org: > found 649626 linux-2.6/2.6.32-40 Bug #649626 {Done: Jonathan Nieder } [linux-2.6] network-manager: iwl3945 microcode SW error Bug Marked as found in versions linux-2.6/2.6.32-40. > quit Stopping processing here. Please contact me if you need assistance. -- 649626: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=649626 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.132623738832614.transcr...@bugs.debian.org
Re: [Fwd: Latest kernel stable/longterm status]
On Tue, Jan 10, 2012 at 11:46:10PM +0100, Marcus Osdoba wrote: > Am 10.01.2012 02:42, schrieb Ben Hutchings: > >We need to make a decision soon on whether we will use Linux 3.2 for > >wheezy or wait for a later release. Whichever one we choose, we need to > >make sure someone (possibly one of us) maintains a longterm branch for > >it. I am strongly disinclined to choose a version that puts us on our > >own, and therefore I would prefer to use Linux 3.2 along with Ubuntu. > > > Hi, I'm just a user, but using 3.2 along with Ubuntu LTS looks more > than reasonable to me. > Unfortunatly, upstream maintains only 3.0. Is there any longterm > version beyond 3.0 in sight, which might be an adequate alternative > for Wheezy? If not, the sum of Debian/UbuntuLTS installations should > have a critical mass to justify the maintenance of a 3.2-DEBline on > their own without offcial "support" from upstream. [...] There is no restriction that only Greg K-H can maintain longterm series; in fact he will be handing over 2.6.32 shortly. And 'upstream' isn't an exclusive club; many kernel team members in both distributions are upstream developers too. Whatever mainline version we start with, I will try to make sure that there is a longterm series based on it. If necessary, I will volunteer to do that myself, but I would rather find some other mug to do it! Ben. -- Ben Hutchings We get into the habit of living before acquiring the habit of thinking. - Albert Camus -- 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/20120110233304.gv20...@decadent.org.uk
Bug#655377: [ideapad_laptop] NULL pointer dereference turning off backlight with fn key
I've compiled vanilla 3.1.6 with that patch and turning off blacklight was working. -- 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/cafvlvsop750x4l+qgr16qc53v+joksxa-ujskx3k0bx9kqo...@mail.gmail.com
Bug#655427: ITP: firmware-crystalhd -- Crystal HD Video Decoder (firmware)
Package: wnpp Severity: wishlist Owner: Andres Mejia * Package name: firmware-crystalhd Version : 0.0~git20120110.fdd2f19 Upstream Author : Broadcom Corporation * URL : http://git.linuxtv.org/jarod/crystalhd.git * License : other Description : Crystal HD Video Decoder (firmware) I'm not sure if this is something I ask the kernel team, or maintain myself, so I'm reporting this as an ITP for now. This is an ITP for the firmware needed by the crystalhd library which has already been uploaded to Debian. Crystal HD Solution is a product offered by Broadcom. It is used to enable flawless playback of 1080p high definition video across a wide range of systems. The firmware has this disclaimer. FIRMWARE BINARIES ARE DISTRIBUTED UNDER THE FOLLOWING LICENSE - BINARIES COVERED WITH THIS LICENSE ARE bcm70015fw.bin and bcm70012fw.bin Copyright 2007-2010 Broadcom Corporation Redistribution and use in binary forms of this software, without modification, are permitted provided that the following conditions are met: Redistributions must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. Neither the name of Broadcom nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED “AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL BROADCOM BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. The above notice is found in a source file for the crystalhd package. It can be read from http://git.linuxtv.org/jarod/crystalhd.git/blob/HEAD:/linux_lib/libcrystalhd/libcrystalhd_fwcmds.cpp -- 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/4f0cd840.0762e00a.538b.d...@mx.google.com
Bug#655387: [PATCH] usb: cdc_ether: Ignore bogus union descriptor for RNDIS devices
Sorry, but didn't work, same dmesg with bad cdc descriptors and usb0 interface is not created. I tested with 3.2.0-rc7 kernel. Regards, iker 2012/1/10 Bjørn Mork > Some RNDIS devices include a bogus CDC Union descriptor pointing > to non-existing interfaces. The RNDIS code is already prepared > to handle devices without a CDC Union descriptor, so we can just > ignore it. > > Cc: Markus Kolb > Cc: Iker Salmón San Millán > Cc: Jonathan Nieder > Cc: Oliver Neukum > Cc: 655...@bugs.debian.org > Cc: sta...@vger.kernel.org > Signed-off-by: Bjørn Mork > --- > How about this, which IMHO is less intrusive? Only build-tested, as I > don't have any of the failing devices, so it will obviously need > testing from anyone with such a device. > > drivers/net/usb/cdc_ether.c | 10 +- > 1 files changed, 9 insertions(+), 1 deletions(-) > > diff --git a/drivers/net/usb/cdc_ether.c b/drivers/net/usb/cdc_ether.c > index 41a61ef..2109f34 100644 > --- a/drivers/net/usb/cdc_ether.c > +++ b/drivers/net/usb/cdc_ether.c > @@ -195,7 +195,15 @@ int usbnet_generic_cdc_bind(struct usbnet *dev, > struct usb_interface *intf) >info->control, >info->u->bSlaveInterface0, >info->data); > - goto bad_desc; > + /* Fallback to guessing for rndis > +* class devices with bogus union > +* descriptor. > +* Fixes some Samsung Android devices > +*/ > + if (rndis) > + info->u = NULL; > + else > + goto bad_desc; >} >if (info->control != intf) { >dev_dbg(&intf->dev, "bogus CDC Union\n"); > -- > 1.7.7.3 > >
Bug#655377: [ideapad_laptop] NULL pointer dereference turning off backlight with fn key
tags 655377 = upstream patch quit Artem X wrote: > I've compiled vanilla 3.1.6 with that patch and turning off blacklight > was working. Excellent. I've passed this information on to Greg so hopefully the patch will be part of a stable 3.1.y kernel soon. Debian kernel maintainers: please consider applying commit d4afc7754a60b (ideapad: Check if acpi already handle backlight power to avoid a page fault) in sid. -- 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/20120111013130.GV22184@burratino
Processed: Re: [ideapad_laptop] NULL pointer dereference turning off backlight with fn key
Processing commands for cont...@bugs.debian.org: > tags 655377 = upstream patch Bug #655377 {Done: Jonathan Nieder } [src:linux-2.6] [ideapad_laptop] NULL pointer dereference turning off backlight with fn key Removed tag(s) fixed-upstream and moreinfo. > quit Stopping processing here. Please contact me if you need assistance. -- 655377: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=655377 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.13262451995242.transcr...@bugs.debian.org
Bug#655387: [PATCH] usb: cdc_ether: Ignore bogus union descriptor for RNDIS devices
Iker Salmón San Millán writes: > Sorry, but didn't work, same dmesg with bad cdc descriptors and usb0 > interface is not created. > I tested with 3.2.0-rc7 kernel. OK, thanks for testing. I must have missed some finer detail somewhere. Bjørn -- 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/871ur6wytx@nemi.mork.no
Bug#655387: [PATCH] usb: cdc_ether: Ignore bogus union descriptor for RNDIS devices
Bjørn Mork writes: > Iker Salmón San Millán writes: > >> Sorry, but didn't work, same dmesg with bad cdc descriptors and usb0 >> interface is not created. >> I tested with 3.2.0-rc7 kernel. > > OK, thanks for testing. I must have missed some finer detail somewhere. Pretty obvious detail: The next if() will fail since info->control is NULL and therefore != intf. Could be fixed by e.g. setting info->control = intf inside the if (rndis) {} section if you have the patience to test yet-another-patch. Bjørn -- 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/87wr8yvhz2@nemi.mork.no
Bug#655387: [PATCH] usb: cdc_ether: Ignore bogus union descriptor for RNDIS devices
Am Dienstag, 10. Januar 2012, 23:15:16 schrieb Bjørn Mork: > - goto bad_desc; > + /* Fallback to guessing for rndis > +* class devices with bogus union > +* descriptor. > +* Fixes some Samsung Android devices > +*/ > + if (rndis) > + info->u = NULL; > + else > + goto bad_desc; You are trying something subtle here. Stop doing that. Use a dedicated flag or a clearly named goto. Regards Oliver -- 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/201201110833.13790.oli...@neukum.org