Bug#619433: Follow-up
Hello, Just to inform that the bug has found a fix upstream (commit 7bed50c5edf5cba8dd515a31191cbfb6065ddc85, details can be found at https://bugzilla.kernel.org/show_bug.cgi?id=31872). The fix has been included in linux-2.6 tree and is waiting in the queue-2.6.38 subdirectory. I am currently running a self built linux-2.6.38 image with the above fix included, and it seems that the bug did not touch any one but me (given my buggy bios). I can now wait for next upload in Debian (next 2.6.38 if any, or next 2.6.39 in experimental or unstable), so I believe you can just close this bug without any further action. Best regards and thank you for pointing me to the right place. Pascal Dormeau -- 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/1112777894.5661661303973013206.javamail.r...@spooler6-g27.priv.proxad.net
Bug#624400: linux-image-2.6.32-5-amd64: Intel Ethernetcard does not work
Package: linux-image-2.6.32-5-amd64 Severity: normal There is a problem with the e1000e driver, the Intel cards Intel Corporation 82571EB Gigabit Ethnernet Controller (rev 06) dual port Intel Corporation 82574L Gigabit Ethnet Connection dual port both cards show up via lspci and dmesg but they cant get any link and they dont activate when a network cable gets plugged in. -- System Information: Debian Release: 6.0.1 APT prefers stable APT policy: (990, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-2-xen-amd64 (SMP w/1 CPU core) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (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/20110428071302.12478.75684.report...@js-dev.intern.igb.de.key-systems.net
Re: [PATCH base-installer] Update i386 kernel selection for new flavours in wheezy
On Sun, 2011-04-24 at 15:59 +0100, Ben Hutchings wrote: The '686-bigmem' flavour will be renamed to '686-pae'; support both names. The '686' flavour will be removed, but we can still offer it if available. Do you also have patches for d-i's kernel-wedge and the main installer build? Also debian-cd will need changes too. Since the latter two are mainly due to Xen support I can take care of that if you like, although I think it will depend on the kernel actually being uploaded since I can't see an easy way to support both names in the main installer build. Ian. -- Ian Campbell I am currently transitioning to a new OpenPGP key, please see: http://www.hellion.org.uk/key-transition-2011-04-27-2F6BCD59-to-79074FA8.txt The avoidance of taxes is the only intellectual pursuit that carries any reward. -- John Maynard Keynes signature.asc Description: This is a digitally signed message part
armhf support in rules.real
Hi, The current 2.6.39-rc4 package has incomplete armhf support. Please consider adding the following patch, which adds armhf support in rules.real. -- Sebastian --- a/rules.real 2011-04-26 01:21:55.0 +0200 +++ b/rules.real 2011-04-28 09:44:36.0 +0200 @@ -39,7 +39,7 @@ # binary-arch-arch: install-headers_$(ARCH) binary-arch-arch: install-libc-dev_$(ARCH) -ifneq ($(filter alpha amd64 armel hppa i386 powerpc ppc64 s390 sh4 sparc sparc64,$(ARCH)),) +ifneq ($(filter alpha amd64 armel armhf hppa i386 powerpc ppc64 s390 sh4 sparc sparc64,$(ARCH)),) binary-arch-arch: install-tools_$(ARCH) endif binary-arch-featureset: install-headers_$(ARCH)_$(FEATURESET) @@ -364,6 +364,7 @@ install-image_arm_$(FEATURESET)_$(FLAVOUR)_plain_image \ install-image_armel_$(FEATURESET)_$(FLAVOUR)_plain_image \ +install-image_armhf_$(FEATURESET)_$(FLAVOUR)_plain_image \ install-image_sparc_$(FEATURESET)_$(FLAVOUR)_plain_image \ install-image_sparc64_$(FEATURESET)_$(FLAVOUR)_plain_image \ install-image_sh4_$(FEATURESET)_$(FLAVOUR)_plain_image: signature.asc Description: Digital signature
Bug#624418: modprobe fuse failed on Unknown symbol kstrtoull
Package: linux-2.6 Version: 2.6.38-4 Severity: normal When attempting to modprobe fuse (needed for ntfs-3g), it fails on kernel 2.6.38-2, leaving one line with error message in dmesg: [17105.390564] fuse: Unknown symbol kstrtoull (err 0) I tried reinstalling the kernel package (apt-get install --reinstall ...) to rule out possibility of the file being somehow replaced by some other version, but problem persisted. # modprobe fuse WARNING: All config files need .conf: /etc/modprobe.d/00local, it will be ignored in a future release. FATAL: Error inserting fuse (/lib/modules/2.6.38-2-amd64/kernel/fs/fuse/fuse.ko): Unknown symbol in module, or unknown parameter (see dmesg) # dmesg | tail [17105.390564] fuse: Unknown symbol kstrtoull (err 0) -- Package-specific info: ** Version: Linux version 2.6.38-2-amd64 (Debian 2.6.38-3) (b...@decadent.org.uk) (gcc version 4.4.5 (Debian 4.4.5-15) ) #1 SMP Thu Apr 7 04:28:07 UTC 2011 ** Command line: BOOT_IMAGE=/vmlinuz-2.6.38-2-amd64 root=/dev/mapper/sda5_crypt ro quiet ** Tainted: PO (4097) * Proprietary module has been loaded. * Out-of-tree module has been loaded. ** Kernel log: [16985.776538] Booting Node 0 Processor 3 APIC 0x3 [16985.868026] Switched to NOHz mode on CPU #3 [16985.894688] NMI watchdog enabled, takes one hw-pmu counter. [16985.896182] CPU3 is up [16985.899688] ACPI: Waking up from system sleep state S3 [16986.374227] i915 :00:02.0: restoring config space at offset 0xf (was 0x100, writing 0x10a) [16986.374253] i915 :00:02.0: restoring config space at offset 0x7 (was 0x0, writing 0x9030) [16986.374270] i915 :00:02.0: restoring config space at offset 0x6 (was 0x8, writing 0x8008) [16986.374286] i915 :00:02.0: restoring config space at offset 0x5 (was 0x1, writing 0x30b1) [16986.374303] i915 :00:02.0: restoring config space at offset 0x4 (was 0x0, writing 0x9048) [16986.374320] i915 :00:02.0: restoring config space at offset 0x1 (was 0x90, writing 0x900407) [16986.374374] pci :00:02.1: restoring config space at offset 0x4 (was 0x0, writing 0x9040) [16986.374392] pci :00:02.1: restoring config space at offset 0x1 (was 0x90, writing 0x97) [16986.374500] pcieport :00:1c.0: restoring config space at offset 0xf (was 0x100, writing 0x10a) [16986.374527] pcieport :00:1c.0: restoring config space at offset 0x9 (was 0x10001, writing 0x90719061) [16986.374545] pcieport :00:1c.0: restoring config space at offset 0x8 (was 0x0, writing 0x90209020) [16986.374562] pcieport :00:1c.0: restoring config space at offset 0x7 (was 0x0, writing 0x4040) [16986.374580] pcieport :00:1c.0: restoring config space at offset 0x6 (was 0x0, writing 0x10100) [16986.374601] pcieport :00:1c.0: restoring config space at offset 0x3 (was 0x81, writing 0x810010) [16986.374621] pcieport :00:1c.0: restoring config space at offset 0x1 (was 0x10, writing 0x100407) [16986.374701] pcieport :00:1c.3: restoring config space at offset 0xf (was 0x400, writing 0x40b) [16986.374727] pcieport :00:1c.3: restoring config space at offset 0x9 (was 0x10001, writing 0x90919081) [16986.374745] pcieport :00:1c.3: restoring config space at offset 0x8 (was 0x0, writing 0x90109010) [16986.374763] pcieport :00:1c.3: restoring config space at offset 0x7 (was 0x0, writing 0x2020) [16986.374780] pcieport :00:1c.3: restoring config space at offset 0x6 (was 0x0, writing 0x20200) [16986.374801] pcieport :00:1c.3: restoring config space at offset 0x3 (was 0x81, writing 0x810010) [16986.374821] pcieport :00:1c.3: restoring config space at offset 0x1 (was 0x10, writing 0x100407) [16986.374889] uhci_hcd :00:1d.0: restoring config space at offset 0xf (was 0x100, writing 0x10a) [16986.374917] uhci_hcd :00:1d.0: restoring config space at offset 0x8 (was 0x1, writing 0x3081) [16986.374945] uhci_hcd :00:1d.0: restoring config space at offset 0x1 (was 0x280, writing 0x281) [16986.374980] uhci_hcd :00:1d.1: restoring config space at offset 0xf (was 0x200, writing 0x20a) [16986.375008] uhci_hcd :00:1d.1: restoring config space at offset 0x8 (was 0x1, writing 0x3061) [16986.375036] uhci_hcd :00:1d.1: restoring config space at offset 0x1 (was 0x280, writing 0x281) [16986.375070] uhci_hcd :00:1d.2: restoring config space at offset 0xf (was 0x300, writing 0x30a) [16986.375098] uhci_hcd :00:1d.2: restoring config space at offset 0x8 (was 0x1, writing 0x3041) [16986.375127] uhci_hcd :00:1d.2: restoring config space at offset 0x1 (was 0x280, writing 0x281) [16986.375172] uhci_hcd :00:1d.3: restoring config space at offset 0xf (was 0x400, writing 0x40b) [16986.375202] uhci_hcd :00:1d.3: restoring config space at offset 0x8 (was 0x1, writing 0x3021) [16986.375231] uhci_hcd :00:1d.3: restoring config space at offset 0x1 (was 0x280, writing 0x281) [16986.375277] ehci_hcd :00:1d.7:
Bug#624418: marked as done (modprobe fuse failed on Unknown symbol kstrtoull)
Your message dated Thu, 28 Apr 2011 11:03:37 +0200 with message-id 20110428090337.gl2...@radis.liafa.jussieu.fr and subject line Re: Bug#624418: modprobe fuse failed on Unknown symbol kstrtoull has caused the Debian Bug report #624418, regarding modprobe fuse failed on Unknown symbol kstrtoull 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.) -- 624418: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=624418 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.38-4 Severity: normal When attempting to modprobe fuse (needed for ntfs-3g), it fails on kernel 2.6.38-2, leaving one line with error message in dmesg: [17105.390564] fuse: Unknown symbol kstrtoull (err 0) I tried reinstalling the kernel package (apt-get install --reinstall ...) to rule out possibility of the file being somehow replaced by some other version, but problem persisted. # modprobe fuse WARNING: All config files need .conf: /etc/modprobe.d/00local, it will be ignored in a future release. FATAL: Error inserting fuse (/lib/modules/2.6.38-2-amd64/kernel/fs/fuse/fuse.ko): Unknown symbol in module, or unknown parameter (see dmesg) # dmesg | tail [17105.390564] fuse: Unknown symbol kstrtoull (err 0) -- Package-specific info: ** Version: Linux version 2.6.38-2-amd64 (Debian 2.6.38-3) (b...@decadent.org.uk) (gcc version 4.4.5 (Debian 4.4.5-15) ) #1 SMP Thu Apr 7 04:28:07 UTC 2011 ** Command line: BOOT_IMAGE=/vmlinuz-2.6.38-2-amd64 root=/dev/mapper/sda5_crypt ro quiet ** Tainted: PO (4097) * Proprietary module has been loaded. * Out-of-tree module has been loaded. ** Kernel log: [16985.776538] Booting Node 0 Processor 3 APIC 0x3 [16985.868026] Switched to NOHz mode on CPU #3 [16985.894688] NMI watchdog enabled, takes one hw-pmu counter. [16985.896182] CPU3 is up [16985.899688] ACPI: Waking up from system sleep state S3 [16986.374227] i915 :00:02.0: restoring config space at offset 0xf (was 0x100, writing 0x10a) [16986.374253] i915 :00:02.0: restoring config space at offset 0x7 (was 0x0, writing 0x9030) [16986.374270] i915 :00:02.0: restoring config space at offset 0x6 (was 0x8, writing 0x8008) [16986.374286] i915 :00:02.0: restoring config space at offset 0x5 (was 0x1, writing 0x30b1) [16986.374303] i915 :00:02.0: restoring config space at offset 0x4 (was 0x0, writing 0x9048) [16986.374320] i915 :00:02.0: restoring config space at offset 0x1 (was 0x90, writing 0x900407) [16986.374374] pci :00:02.1: restoring config space at offset 0x4 (was 0x0, writing 0x9040) [16986.374392] pci :00:02.1: restoring config space at offset 0x1 (was 0x90, writing 0x97) [16986.374500] pcieport :00:1c.0: restoring config space at offset 0xf (was 0x100, writing 0x10a) [16986.374527] pcieport :00:1c.0: restoring config space at offset 0x9 (was 0x10001, writing 0x90719061) [16986.374545] pcieport :00:1c.0: restoring config space at offset 0x8 (was 0x0, writing 0x90209020) [16986.374562] pcieport :00:1c.0: restoring config space at offset 0x7 (was 0x0, writing 0x4040) [16986.374580] pcieport :00:1c.0: restoring config space at offset 0x6 (was 0x0, writing 0x10100) [16986.374601] pcieport :00:1c.0: restoring config space at offset 0x3 (was 0x81, writing 0x810010) [16986.374621] pcieport :00:1c.0: restoring config space at offset 0x1 (was 0x10, writing 0x100407) [16986.374701] pcieport :00:1c.3: restoring config space at offset 0xf (was 0x400, writing 0x40b) [16986.374727] pcieport :00:1c.3: restoring config space at offset 0x9 (was 0x10001, writing 0x90919081) [16986.374745] pcieport :00:1c.3: restoring config space at offset 0x8 (was 0x0, writing 0x90109010) [16986.374763] pcieport :00:1c.3: restoring config space at offset 0x7 (was 0x0, writing 0x2020) [16986.374780] pcieport :00:1c.3: restoring config space at offset 0x6 (was 0x0, writing 0x20200) [16986.374801] pcieport :00:1c.3: restoring config space at offset 0x3 (was 0x81, writing 0x810010) [16986.374821] pcieport :00:1c.3: restoring config space at offset 0x1 (was 0x10, writing 0x100407) [16986.374889] uhci_hcd :00:1d.0: restoring config space at offset 0xf (was 0x100, writing 0x10a) [16986.374917] uhci_hcd :00:1d.0: restoring config space at offset 0x8 (was 0x1, writing 0x3081) [16986.374945] uhci_hcd :00:1d.0: restoring config space at offset 0x1 (was 0x280, writing 0x281) [16986.374980] uhci_hcd :00:1d.1: restoring config space at offset 0xf (was 0x200, writing 0x20a)
Processed: re-tagging
Processing commands for cont...@bugs.debian.org: tags 613658 - experimental Bug #613658 [linux-2.6] Please enable SQUASHFS_XZ et al for =2.6.38-rc1. Removed tag(s) experimental. found 613658 2.6.38-3 Bug #613658 [linux-2.6] Please enable SQUASHFS_XZ et al for =2.6.38-rc1. There is no source info for the package 'linux-2.6' at version '2.6.38-3' with architecture '' Unable to make a source version for version '2.6.38-3' Bug Marked as found in versions 2.6.38-3. found 613658 2.6.38-4 Bug #613658 [linux-2.6] Please enable SQUASHFS_XZ et al for =2.6.38-rc1. There is no source info for the package 'linux-2.6' at version '2.6.38-4' with architecture '' Unable to make a source version for version '2.6.38-4' Bug Marked as found in versions 2.6.38-4. found 613658 2.6.39~rc4-1~experimental.1 Bug #613658 [linux-2.6] Please enable SQUASHFS_XZ et al for =2.6.38-rc1. There is no source info for the package 'linux-2.6' at version '2.6.39~rc4-1~experimental.1' with architecture '' Unable to make a source version for version '2.6.39~rc4-1~experimental.1' Bug Marked as found in versions 2.6.39~rc4-1~experimental.1. thanks Stopping processing here. Please contact me if you need assistance. -- 613658: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=613658 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.13039903902973.transcr...@bugs.debian.org
Bug#624433: psmouse: Unknown symbol _kstrtoul (err 0)
Package: linux-2.6 Version: 2.6.38-4 Severity: important Hello, When upgrading from version 2.6.38-3 to 2.6.38-4, my mouse stops working and I see the following error in dmesg: [75444.938735] psmouse: Unknown symbol _kstrtoul (err 0) I had to downgrade to 2.6.38-3 and then reload the psmouse module to get it to work again. Thanks, --Joe -- Package-specific info: ** Version: Linux version 2.6.38-2-686 (Debian 2.6.38-3) (b...@decadent.org.uk) (gcc version 4.4.5 (Debian 4.4.5-15) ) #1 SMP Thu Apr 7 05:24:21 UTC 2011 ** Command line: BOOT_IMAGE=/vmlinuz-2.6.38-2-686 root=/dev/mapper/diskvg-root ro vga=871 selinux=1 irqpoll splash quiet ** Tainted: O (4096) * Out-of-tree module has been loaded. ** Kernel log: [75366.264846] uhci_hcd :00:1d.0: power state changed by ACPI to D0 [75366.264848] uhci_hcd :00:1d.0: power state changed by ACPI to D0 [75366.264890] uhci_hcd :00:1d.1: restoring config space at offset 0x1 (was 0x285, writing 0x281) [75366.264904] uhci_hcd :00:1d.2: power state changed by ACPI to D0 [75366.264907] uhci_hcd :00:1d.2: power state changed by ACPI to D0 [75366.264952] uhci_hcd :00:1d.2: restoring config space at offset 0x1 (was 0x285, writing 0x281) [75366.264960] uhci_hcd :00:1d.2: power state changed by ACPI to D0 [75366.264963] uhci_hcd :00:1d.2: power state changed by ACPI to D0 [75366.265019] ehci_hcd :00:1d.7: restoring config space at offset 0x1 (was 0x2900106, writing 0x2900102) [75366.265038] ehci_hcd :00:1d.7: power state changed by ACPI to D0 [75366.265044] ehci_hcd :00:1d.7: power state changed by ACPI to D0 [75366.265088] pci :00:1e.0: restoring config space at offset 0x1 (was 0x15, writing 0x17) [75366.265215] ata_piix :00:1f.1: restoring config space at offset 0x1 (was 0x285, writing 0x2880005) [75366.265273] ahci :00:1f.2: restoring config space at offset 0x1 (was 0x2b7, writing 0x2b00407) [75366.280022] firewire_ohci :15:00.1: BAR 0: set to [mem 0xf8301000-0xf83017ff] (PCI address [0xf8301000-0xf83017ff]) [75366.280059] firewire_ohci :15:00.1: restoring config space at offset 0x3 (was 0x80, writing 0x804000) [75366.280068] firewire_ohci :15:00.1: restoring config space at offset 0x1 (was 0x210, writing 0x216) [75366.280302] PM: early resume of devices complete after 36.260 msecs [75366.280393] i915 :00:02.0: power state changed by ACPI to D0 [75366.280397] i915 :00:02.0: power state changed by ACPI to D0 [75366.280403] i915 :00:02.0: setting latency timer to 64 [75366.280428] e1000e :00:19.0: wake-up capability disabled by ACPI [75366.281704] e1000e :00:19.0: PME# disabled [75366.285091] e1000e :00:19.0: irq 45 for MSI/MSI-X [75366.295434] uhci_hcd :00:1a.0: PCI INT A - GSI 20 (level, low) - IRQ 20 [75366.295441] uhci_hcd :00:1a.0: setting latency timer to 64 [75366.295468] usb usb3: root hub lost power or was reset [75366.295481] uhci_hcd :00:1a.1: power state changed by ACPI to D0 [75366.295484] uhci_hcd :00:1a.1: power state changed by ACPI to D0 [75366.295489] uhci_hcd :00:1a.1: PCI INT B - GSI 21 (level, low) - IRQ 21 [75366.295496] uhci_hcd :00:1a.1: setting latency timer to 64 [75366.295522] usb usb4: root hub lost power or was reset [75366.295534] ehci_hcd :00:1a.7: power state changed by ACPI to D0 [75366.295539] ehci_hcd :00:1a.7: power state changed by ACPI to D0 [75366.295545] ehci_hcd :00:1a.7: PCI INT C - GSI 22 (level, low) - IRQ 22 [75366.295552] ehci_hcd :00:1a.7: setting latency timer to 64 [75366.295593] HDA Intel :00:1b.0: PCI INT B - GSI 17 (level, low) - IRQ 17 [75366.295600] HDA Intel :00:1b.0: setting latency timer to 64 [75366.295643] HDA Intel :00:1b.0: irq 48 for MSI/MSI-X [75366.295710] uhci_hcd :00:1d.0: power state changed by ACPI to D0 [75366.295713] uhci_hcd :00:1d.0: power state changed by ACPI to D0 [75366.295718] uhci_hcd :00:1d.0: PCI INT A - GSI 16 (level, low) - IRQ 16 [75366.295724] uhci_hcd :00:1d.0: setting latency timer to 64 [75366.295750] usb usb5: root hub lost power or was reset [75366.295762] uhci_hcd :00:1d.1: PCI INT B - GSI 17 (level, low) - IRQ 17 [75366.295769] uhci_hcd :00:1d.1: setting latency timer to 64 [75366.295796] usb usb6: root hub lost power or was reset [75366.295806] uhci_hcd :00:1d.2: power state changed by ACPI to D0 [75366.295809] uhci_hcd :00:1d.2: power state changed by ACPI to D0 [75366.295813] uhci_hcd :00:1d.2: PCI INT C - GSI 18 (level, low) - IRQ 18 [75366.295820] uhci_hcd :00:1d.2: setting latency timer to 64 [75366.295846] usb usb7: root hub lost power or was reset [75366.295858] ehci_hcd :00:1d.7: power state changed by ACPI to D0 [75366.295863] ehci_hcd :00:1d.7: power state changed by ACPI to D0 [75366.295870] ehci_hcd :00:1d.7: PCI INT D - GSI 19 (level, low) - IRQ 19 [75366.295877] ehci_hcd :00:1d.7: setting latency timer to 64
Bug#624433: marked as done (psmouse: Unknown symbol _kstrtoul (err 0))
Your message dated Thu, 28 Apr 2011 15:04:29 +0200 with message-id 20110428130429.gn2...@radis.liafa.jussieu.fr and subject line Re: Bug#624433: psmouse: Unknown symbol _kstrtoul (err 0) has caused the Debian Bug report #624433, regarding psmouse: Unknown symbol _kstrtoul (err 0) 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.) -- 624433: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=624433 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.38-4 Severity: important Hello, When upgrading from version 2.6.38-3 to 2.6.38-4, my mouse stops working and I see the following error in dmesg: [75444.938735] psmouse: Unknown symbol _kstrtoul (err 0) I had to downgrade to 2.6.38-3 and then reload the psmouse module to get it to work again. Thanks, --Joe -- Package-specific info: ** Version: Linux version 2.6.38-2-686 (Debian 2.6.38-3) (b...@decadent.org.uk) (gcc version 4.4.5 (Debian 4.4.5-15) ) #1 SMP Thu Apr 7 05:24:21 UTC 2011 ** Command line: BOOT_IMAGE=/vmlinuz-2.6.38-2-686 root=/dev/mapper/diskvg-root ro vga=871 selinux=1 irqpoll splash quiet ** Tainted: O (4096) * Out-of-tree module has been loaded. ** Kernel log: [75366.264846] uhci_hcd :00:1d.0: power state changed by ACPI to D0 [75366.264848] uhci_hcd :00:1d.0: power state changed by ACPI to D0 [75366.264890] uhci_hcd :00:1d.1: restoring config space at offset 0x1 (was 0x285, writing 0x281) [75366.264904] uhci_hcd :00:1d.2: power state changed by ACPI to D0 [75366.264907] uhci_hcd :00:1d.2: power state changed by ACPI to D0 [75366.264952] uhci_hcd :00:1d.2: restoring config space at offset 0x1 (was 0x285, writing 0x281) [75366.264960] uhci_hcd :00:1d.2: power state changed by ACPI to D0 [75366.264963] uhci_hcd :00:1d.2: power state changed by ACPI to D0 [75366.265019] ehci_hcd :00:1d.7: restoring config space at offset 0x1 (was 0x2900106, writing 0x2900102) [75366.265038] ehci_hcd :00:1d.7: power state changed by ACPI to D0 [75366.265044] ehci_hcd :00:1d.7: power state changed by ACPI to D0 [75366.265088] pci :00:1e.0: restoring config space at offset 0x1 (was 0x15, writing 0x17) [75366.265215] ata_piix :00:1f.1: restoring config space at offset 0x1 (was 0x285, writing 0x2880005) [75366.265273] ahci :00:1f.2: restoring config space at offset 0x1 (was 0x2b7, writing 0x2b00407) [75366.280022] firewire_ohci :15:00.1: BAR 0: set to [mem 0xf8301000-0xf83017ff] (PCI address [0xf8301000-0xf83017ff]) [75366.280059] firewire_ohci :15:00.1: restoring config space at offset 0x3 (was 0x80, writing 0x804000) [75366.280068] firewire_ohci :15:00.1: restoring config space at offset 0x1 (was 0x210, writing 0x216) [75366.280302] PM: early resume of devices complete after 36.260 msecs [75366.280393] i915 :00:02.0: power state changed by ACPI to D0 [75366.280397] i915 :00:02.0: power state changed by ACPI to D0 [75366.280403] i915 :00:02.0: setting latency timer to 64 [75366.280428] e1000e :00:19.0: wake-up capability disabled by ACPI [75366.281704] e1000e :00:19.0: PME# disabled [75366.285091] e1000e :00:19.0: irq 45 for MSI/MSI-X [75366.295434] uhci_hcd :00:1a.0: PCI INT A - GSI 20 (level, low) - IRQ 20 [75366.295441] uhci_hcd :00:1a.0: setting latency timer to 64 [75366.295468] usb usb3: root hub lost power or was reset [75366.295481] uhci_hcd :00:1a.1: power state changed by ACPI to D0 [75366.295484] uhci_hcd :00:1a.1: power state changed by ACPI to D0 [75366.295489] uhci_hcd :00:1a.1: PCI INT B - GSI 21 (level, low) - IRQ 21 [75366.295496] uhci_hcd :00:1a.1: setting latency timer to 64 [75366.295522] usb usb4: root hub lost power or was reset [75366.295534] ehci_hcd :00:1a.7: power state changed by ACPI to D0 [75366.295539] ehci_hcd :00:1a.7: power state changed by ACPI to D0 [75366.295545] ehci_hcd :00:1a.7: PCI INT C - GSI 22 (level, low) - IRQ 22 [75366.295552] ehci_hcd :00:1a.7: setting latency timer to 64 [75366.295593] HDA Intel :00:1b.0: PCI INT B - GSI 17 (level, low) - IRQ 17 [75366.295600] HDA Intel :00:1b.0: setting latency timer to 64 [75366.295643] HDA Intel :00:1b.0: irq 48 for MSI/MSI-X [75366.295710] uhci_hcd :00:1d.0: power state changed by ACPI to D0 [75366.295713] uhci_hcd :00:1d.0: power state changed by ACPI to D0 [75366.295718] uhci_hcd :00:1d.0: PCI INT A - GSI 16 (level, low) - IRQ 16 [75366.295724] uhci_hcd :00:1d.0: setting latency timer to 64 [75366.295750] usb usb5: root hub
easycap.ko absence
hi, why easycap.ko module, for usbframe grabber (device 05e1:0408) is not compiled as a module into the distribution's (amd64/testing) kernel (2.6.38-2-amd64)? $ grep EASYCAP /boot/config-2.6.38-2-amd64 # CONFIG_EASYCAP is not set this driver is nowadays part of vanilla kernel, not marked as experimental. i've compiled it manually and it worked with my device out of the box. are there any plans to include this driver in future kernel packages? -- pozdrawiam serdecznie / best regards, bartek szurgot http://www.baszerr.org (public key: http://www.baszerr.org/lib/exe/fetch.php/about_me/basz_pub_key.txt) signature.asc Description: OpenPGP digital signature
easycap.ko absence
hi, why easycap.ko module, for usb frame grabber (device 05e1:0408) is not compiled as a module into the distribution's (amd64/testing) kernel (2.6.38-2-amd64)? $ grep EASYCAP /boot/config-2.6.38-2-amd64 # CONFIG_EASYCAP is not set this driver is nowadays part of vanilla kernel, not marked as experimental. i've compiled it manually and it worked with my device out of the box. are there any plans to include this driver in future kernel packages? -- pozdrawiam serdecznie / best regards, bartek szurgot http://www.baszerr.org (public key: http://www.baszerr.org/lib/exe/fetch.php/about_me/basz_pub_key.txt) -- 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/4db98a4f.4030...@wp.pl
[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 #620480 (http://bugs.debian.org/620480) # * https://bugs.freedesktop.org/show_bug.cgi?id=36372 # * remote status changed: (?) - NEW usertags 620480 + status-NEW 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/20110428171939.22203.29981.btsl...@busoni.debian.org
Bug#624486: linux-image-2.6.38-2-amd64: bug in radeon driver module of linux 2.6.38 (since 2.6.35)
Package: linux-2.6 Version: 2.6.38-3 Severity: important Hi, I encountered a bug in the radeon driver module of 2.6.37 which still exists in 2.6.38. I have a mainboard called M2A-VM which has VGA, DVI and display port as graphic output ports. When I boot Debian GNU/Linux with Linux 2.6.37 or 2.6.38 I get every 10 seconds: radeon :01:05.0: HDMI-A-1: EDID block 0 invalid. [drm:radeon_dvi_detect] *ERROR* HDMI-A-1: probed a monitor but no|invalid EDID This error message is spamming to tty1 (and because of my configuration to ttyS0 too). With radeon.modeset=0 set, I get rid of this messages by disabling KMS for this driver. This behaviour is also described here: http://ubuntuforums.org/showthread.php?t=1607778 My board has no HDMI port btw. - I think the driver should either not search for the HDMI-A-1: EDID block 0 resp. a HDMI connected monitor while the board has no HDMI port at all or just probe for it once instead of every 10 seconds. I don't see any reason for probing every 10 seconds but I don't know if there is one. I already reportet this on the LKML btw. Regards, Martin -- Package-specific info: ** Version: Linux version 2.6.38-2-amd64 (Debian 2.6.38-3) (b...@decadent.org.uk) (gcc version 4.4.5 (Debian 4.4.5-15) ) #1 SMP Thu Apr 7 04:28:07 UTC 2011 ** Command line: BOOT_IMAGE=/vmlinuz-2.6.38-2-amd64 root=UUID=c491e50b-1626-4ab2-bb2f-9d9c795a0ea9 ro console=tty0 console=ttyS0,115200n8 drm_kms_helper.poll=0 ** Not tainted ** Kernel log: [7.020103] input: PS/2 Logitech Mouse as /devices/platform/i8042/serio1/input/input4 [7.029227] [drm:drm_edid_block_valid] *ERROR* Raw EDID: [7.034620] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.034623] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.034626] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.034628] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.034631] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.034633] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.034636] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.034639] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.034641] [7.086413] [drm:drm_edid_block_valid] *ERROR* Raw EDID: [7.091835] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.091838] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.091840] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.091843] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.091845] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.091848] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.091850] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.091853] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.091855] [7.142701] [drm:drm_edid_block_valid] *ERROR* Raw EDID: [7.148085] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.148088] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.148090] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.148093] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.148095] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.148098] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.148101] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.148103] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.148105] [7.198952] [drm:drm_edid_block_valid] *ERROR* Raw EDID: [7.204332] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.204335] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.204337] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.204340] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.204343] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.204345] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.204348] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.204350] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [7.204352] [7.205893] radeon :01:05.0: HDMI-A-1: EDID block 0 invalid. [7.211985] [drm:radeon_dvi_detect] *ERROR* HDMI-A-1: probed a monitor but no|invalid EDID [7.224664] [drm] fb mappable at 0xFA04 [7.228916] [drm] vram apper at 0xFA00 [7.233062] [drm] size 2150400 [7.236169] [drm] fb depth is 8 [7.239361] [drm]pitch is 1792 [7.250869] Console: switching to colour frame buffer device 200x75 [7.259926] fb0:
Re: easycap.ko absence
On Thu, Apr 28, 2011 at 05:39:59PM +0200, bartek szurgot wrote: hi, why easycap.ko module, for usb frame grabber (device 05e1:0408) is not compiled as a module into the distribution's (amd64/testing) kernel (2.6.38-2-amd64)? $ grep EASYCAP /boot/config-2.6.38-2-amd64 # CONFIG_EASYCAP is not set this driver is nowadays part of vanilla kernel, not marked as experimental. i've compiled it manually and it worked with my device out of the box. are there any plans to include this driver in future kernel packages? Staging modules are generally enabled on request, not by default. Please report this as a 'wishlist' bug, and we will probably add 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/20110428214448.gg2...@decadent.org.uk
Bug#593421: Bug not found in version 2.6.32-19
2011/4/25 Lisandro Damián Nicanor Pérez Meyer perezme...@gmail.com: On Saturday 23 April 2011 16:22:34 Moritz Mühlenhoff wrote: [snip] Does this bug still occur with the final version of the Linux kernel/Xorg ? Still happens with Squeeze's latest kernel/xorg. The only thing that changed is that, when an external monitor is connected to the VGA port, now the LCD comes back to life (with the other kernels, the VGA will show the screen). I'm now upgrading to testing. -- Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.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/BANLkTinhDZG=ppgwwndnanytqvq5pon...@mail.gmail.com
Bug#593421: Bug not found in version 2.6.32-19
Works with current kernel in testing :-) Kinds regards, Lisandro. -- Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.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/banlktimpesabsj+tkb2obks6escv58o...@mail.gmail.com
Re: armhf support in rules.real
On Thu, 2011-04-28 at 09:59 +0200, Sebastian Reichel wrote: Hi, The current 2.6.39-rc4 package has incomplete armhf support. Please consider adding the following patch, which adds armhf support in rules.real. -- Sebastian --- a/rules.real2011-04-26 01:21:55.0 +0200 +++ b/rules.real2011-04-28 09:44:36.0 +0200 @@ -39,7 +39,7 @@ # binary-arch-arch: install-headers_$(ARCH) binary-arch-arch: install-libc-dev_$(ARCH) -ifneq ($(filter alpha amd64 armel hppa i386 powerpc ppc64 s390 sh4 sparc sparc64,$(ARCH)),) +ifneq ($(filter alpha amd64 armel armhf hppa i386 powerpc ppc64 s390 sh4 sparc sparc64,$(ARCH)),) binary-arch-arch: install-tools_$(ARCH) endif binary-arch-featureset: install-headers_$(ARCH)_$(FEATURESET) The control file needs to be updated too. @@ -364,6 +364,7 @@ install-image_arm_$(FEATURESET)_$(FLAVOUR)_plain_image \ install-image_armel_$(FEATURESET)_$(FLAVOUR)_plain_image \ +install-image_armhf_$(FEATURESET)_$(FLAVOUR)_plain_image \ install-image_sparc_$(FEATURESET)_$(FLAVOUR)_plain_image \ install-image_sparc64_$(FEATURESET)_$(FLAVOUR)_plain_image \ install-image_sh4_$(FEATURESET)_$(FLAVOUR)_plain_image: Yes, we probably should include the kernel in the package! Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
Re: [PATCH base-installer] Update i386 kernel selection for new flavours in wheezy
On Thu, 2011-04-28 at 08:38 +0100, Ian Campbell wrote: On Sun, 2011-04-24 at 15:59 +0100, Ben Hutchings wrote: The '686-bigmem' flavour will be renamed to '686-pae'; support both names. The '686' flavour will be removed, but we can still offer it if available. Do you also have patches for d-i's kernel-wedge and the main installer build? No, I'm not familiar with those. I did the kernel installation selection myself because I've worked on it before. Also debian-cd will need changes too. Since the latter two are mainly due to Xen support I can take care of that if you like, although I think it will depend on the kernel actually being uploaded since I can't see an easy way to support both names in the main installer build. So it depends on when the d-i team decides to switch to 2.6.39 (or later). But you can get your patches ready before then. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
Bug#624343: linux-image-2.6.38-2-amd64: frequent message bio too big device md0 (248 240) in kern.log
On Wed, 2011-04-27 at 09:19 -0700, Jameson Graef Rollins wrote: Package: linux-2.6 Version: 2.6.38-3 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 As you can see from the kern.log snippet below, I am seeing frequent messages reporting bio too big device md0 (248 240). I run what I imagine is a fairly unusual disk setup on my laptop, consisting of: ssd - raid1 - dm-crypt - lvm - ext4 I use the raid1 as a backup. The raid1 operates normally in degraded mode. For backups I then hot-add a usb hdd, let the raid1 sync, and then fail/remove the external hdd. Well, this is not expected to work. Possibly the hot-addition of a disk with different bio restrictions should be rejected. But I'm not sure, because it is safe to do that if there is no mounted filesystem or stacking device on top of the RAID. I would recommend using filesystem-level backup (e.g. dirvish or backuppc). Aside from this bug, if the SSD fails during a RAID resync you will be left with an inconsistent and therefore useless 'backup'. I started noticing these messages after my last sync. I have not rebooted since. I found a bug report on the launchpad that describes an almost identical situation: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/320638 The reporter seemed to be concerned that their may be data loss happening. I have not yet noticed any, but of course I'm terrified that it's happening and I just haven't found it yet. Unfortunately the bug was closed with a Won't Fix without any resolution. Is this a kernel bug, or is there something I can do to remedy the situation? I haven't tried to reboot yet to see if the messages stop. I'm obviously most worried about data loss. Please advise! The block layer correctly returns an error after logging this message. If it's due to a read operation, the error should be propagated up to the application that tried to read. If it's due to a write operation, I would expect the error to result in the RAID becoming desynchronised. In some cases it might be propagated to the application that tried to write. If the error is somehow discarded then there *is* a kernel bug with the risk of data loss. I am starting to suspect that these messages are in face associated with data loss on my system. I have witnessed these messages occur during write operations to the disk, and I have also started to see some strange behavior on my system. dhclient started acting weird after these messages appeared (not holding on to leases) and I started to notice database exceptions in my mail client. Interestingly, the messages seem to have gone away after reboot. I will watch closely to see if they return after my next raid1 sync. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
Processed: bug 624343 is forwarded to linux-r...@vger.kernel.org
Processing commands for cont...@bugs.debian.org: forwarded 624343 linux-r...@vger.kernel.org Bug #624343 [linux-2.6] linux-image-2.6.38-2-amd64: frequent message bio too big device md0 (248 240) in kern.log Set Bug forwarded-to-address to 'linux-r...@vger.kernel.org'. thanks Stopping processing here. Please contact me if you need assistance. -- 624343: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=624343 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.130405200911444.transcr...@bugs.debian.org
Bug#624372: linux-source-2.6.39: Fix warnings for invalid symbol values (now boolean)
On Wed, 2011-04-27 at 22:48 +0200, Sedat Dilek wrote: Package: linux-source-2.6.39 Version: 2.6.39~rc4-1~experimental.1 Severity: normal Tags: patch Hi, attached patch against debian-dir from linux-2.6/trunk (r17251) fixes these warnings: .config:555:warning: symbol value 'm' invalid for LEDS_CLASS .config:917:warning: symbol value 'm' invalid for MFD_WM8994 .config:2292:warning: symbol value 'm' invalid for BT_L2CAP .config:2293:warning: symbol value 'm' invalid for BT_SCO diff -uprN debian-trunk.orig/config/config debian-trunk/config/config --- debian-trunk.orig/config/config 2011-04-27 17:14:59.169280262 +0200 +++ debian-trunk/config/config 2011-04-27 18:35:33.260507504 +0200 @@ -800,7 +800,7 @@ CONFIG_MISDN_L1OIP=m ## file: drivers/leds/Kconfig ## CONFIG_NEW_LEDS=y -CONFIG_LEDS_CLASS=m +CONFIG_LEDS_CLASS=y CONFIG_LEDS_NET48XX=m CONFIG_LEDS_ALIX2=m CONFIG_LEDS_PCA9532=m I don't understand why this is no longer tristate, and I'm not sure most Debian systems need it. @@ -1383,7 +1383,7 @@ CONFIG_HTC_PASIC3=m CONFIG_TPS65010=m CONFIG_MFD_WM8400=m # CONFIG_MFD_WM8350_I2C is not set -CONFIG_MFD_WM8994=m +# CONFIG_MFD_WM8994 is not set CONFIG_MFD_PCF50633=m CONFIG_PCF50633_ADC=m CONFIG_PCF50633_GPIO=m OK. I think most of these MFD drivers are useless without platform data anyway. @@ -3693,8 +3693,8 @@ CONFIG_BATMAN_ADV=m ## file: net/bluetooth/Kconfig ## CONFIG_BT=m -CONFIG_BT_L2CAP=m -CONFIG_BT_SCO=m +CONFIG_BT_L2CAP=y +CONFIG_BT_SCO=y ## ## file: net/bluetooth/bnep/Kconfig OK. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
Processed: tagging 624372
Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.10.35lenny7 tags 624372 + pending Bug #624372 [linux-source-2.6.39] linux-source-2.6.39: Fix warnings for invalid symbol values (now boolean) Added tag(s) pending. End of message, stopping processing here. Please contact me if you need assistance. -- 624372: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=624372 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.130405329315803.transcr...@bugs.debian.org
