Processed: your mail
Processing commands for cont...@bugs.debian.org: found 701489 3.10.5-1 Bug #701489 [src:linux] linux-image-3.7-trunk-amd64: asix_rx_fixup error messages from Lenovo ethernet dongle Marked as found in versions linux/3.10.5-1. thanks Stopping processing here. Please contact me if you need assistance. -- 701489: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701489 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.137735397610154.transcr...@bugs.debian.org
Processed: Re: #681418 debugfs is a big security hole
Processing commands for cont...@bugs.debian.org: package src:linux Limiting to bugs with field 'package' containing at least one of 'src:linux' Limit currently set to 'package':'src:linux' notfound 681418 3.8.5-1~experimental.1 Bug #681418 [src:linux] debugfs is a big security hole No longer marked as found in versions linux/3.8.5-1~experimental.1. fixed 681418 3.2.29-1 Bug #681418 [src:linux] debugfs is a big security hole Marked as fixed in versions linux/3.2.29-1. close 681418 Bug #681418 [src:linux] debugfs is a big security hole Marked Bug as done thanks Stopping processing here. Please contact me if you need assistance. -- 681418: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681418 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.137735478714075.transcr...@bugs.debian.org
Bug#720716: initramfs-tools: workaround in 707286 solves serious problem
Followup-For: Bug #707286 Package: initramfs-tools Version: 0.113 Dear Maintainer, The workaround from 707286 (add ‘sleep 1’ before “modprobe -q dm-mod” in scripts/local-top/lvm2) has made the latest Debian kernels bootable again! They all got stuck in the initramfs shell because the root on LVM could not be found. Hugo Vanwoerkom -- Package-specific info: -- initramfs sizes -rw-r--r-- 1 root root 12M Jul 31 09:36 /boot/initrd.img-3.10-1-amd64 -rw-r--r-- 1 root root 12M Aug 24 10:06 /boot/initrd.img-3.10-2-amd64 -rw-r--r-- 1 root root 3.1M Aug 15 11:01 /boot/initrd.img-3.10.4-nodeb-amd64 -rw-r--r-- 1 root root 3.1M Aug 20 20:11 /boot/initrd.img-3.10.7-nodeb-amd64 -rw-r--r-- 1 root root 11M Jul 4 15:02 /boot/initrd.img-3.2.0-4-amd64 -rw-r--r-- 1 root root 3.1M Jul 4 17:30 /boot/initrd.img-3.8.1-nodeb-amd64 -rw-r--r-- 1 root root 12M Jul 18 10:37 /boot/initrd.img-3.9-1-amd64 -- /proc/cmdline root=/dev/mapper/vgHDB-HDBB vga=791 nouveau.modeset=0 resume=LABEL=HD502HJ_02.08 -- resume RESUME=UUID=f2b6dbbe-6ed3-4d57-8c11-823ce166b7c5 -- /proc/filesystems ext2 -- lsmod Module Size Used by nvidia 9315617 50 drm 211856 2 nvidia pci_stub 12429 1 vboxpci19094 0 vboxnetadp 25443 0 vboxnetflt 23697 0 vboxdrv 217395 4 vboxnetadp,vboxnetflt,vboxpci nf_conntrack_irc 12427 0 nf_conntrack_ftp 12651 0 xt_helper 12507 12 xt_tcpudp 12570 32 nf_conntrack_ipv4 18549 61 nf_defrag_ipv4 12483 1 nf_conntrack_ipv4 xt_conntrack 12681 49 xt_limit 12638 14 nf_conntrack 59788 5 xt_helper,xt_conntrack,nf_conntrack_ftp,nf_conntrack_irc,nf_conntrack_ipv4 ipt_ULOG 12862 13 nfnetlink_log 17396 1 nfnetlink 12989 2 nfnetlink_log iptable_filter 12536 1 ip_tables 22036 1 iptable_filter x_tables 19041 7 xt_helper,ipt_ULOG,ip_tables,xt_tcpudp,xt_limit,xt_conntrack,iptable_filter loop 22869 0 snd_hda_codec_via 22832 1 snd_hda_intel 35718 13 snd_hda_codec 122850 2 snd_hda_codec_via,snd_hda_intel snd_hwdep 13189 1 snd_hda_codec snd_pcm68525 6 snd_hda_codec,snd_hda_intel acpi_cpufreq 13280 1 i2c_nforce212628 0 edac_mce_amd 17070 0 edac_core 43448 0 mperf 12453 1 acpi_cpufreq psmouse74832 0 serio_raw 12940 0 snd_page_alloc 13018 2 snd_pcm,snd_hda_intel video 17792 0 kvm_amd47719 0 processor 28526 1 acpi_cpufreq i2c_core 24353 3 drm,nvidia,i2c_nforce2 snd_timer 22773 5 snd_pcm kvm 301458 1 kvm_amd snd53068 24 snd_hwdep,snd_timer,snd_hda_codec_via,snd_pcm,snd_hda_codec,snd_hda_intel hid_a4tech 12531 0 pcspkr 12632 0 soundcore 13026 1 snd wmi13243 0 thermal_sys23137 2 video,processor microcode 30413 0 button 12944 0 asus_atk0110 17246 0 evdev 17611 15 ext2 59601 8 mbcache13082 1 ext2 hid_generic12393 0 usb_storage48158 0 usbhid 40964 0 hid81894 3 hid_a4tech,hid_generic,usbhid sr_mod 21988 0 cdrom 35212 1 sr_mod sg 26095 0 sd_mod 40541 10 crc_t10dif 12348 1 sd_mod dm_mod 64008 27 ata_generic12490 0 firewire_ohci 31931 0 firewire_core 49211 1 firewire_ohci crc_itu_t 12347 1 firewire_core ehci_pci 12472 0 ohci_hcd 26678 0 ehci_hcd 40590 1 ehci_pci ahci 25148 9 libahci23136 1 ahci pata_amd 13378 0 forcedeth 54034 0 libata141969 4 ahci,libahci,pata_amd,ata_generic scsi_mod 158249 5 sg,usb_storage,libata,sd_mod,sr_mod usbcore 134993 5 usb_storage,ohci_hcd,ehci_hcd,ehci_pci,usbhid usb_common 12440 1 usbcore -- /etc/initramfs-tools/modules dm_mod -- /etc/kernel-img.conf # Kernel image management overrides # See kernel-img.conf(5) for details do_symlinks = yes do_bootloader = no do_initrd = yes link_in_boot = no -- /etc/initramfs-tools/initramfs.conf MODULES=most BUSYBOX=y KEYMAP=n COMPRESS=gzip DEVICE= NFSROOT=auto -- /etc/initramfs-tools/update-initramfs.conf update_initramfs=yes backup_initramfs=no -- mkinitramfs hooks /etc/initramfs-tools/hooks/: /usr/share/initramfs-tools/hooks: busybox dmsetup keymap klibc kmod lvm2 thermal udev -- System Information: Debian Release: jessie/sid APT prefers unstable APT
Bug#720735: initramfs-tools: mkinitramfs uses ldd, which is insecure and generates core dumps
Package: initramfs-tools Version: 0.113 Severity: important Tags: security I've noticed that when running update-initramfs, a core dump was generated in the current directory, which is in itself a first bug. After looking at this problem with strace, I saw that this came from: /usr/bin/ldd /lib/firmware/cis/PCMLM28.cis apparently via mkinitramfs. The strace output shows: 23190 execve(/libx32/ld-linux-x32.so.2, [/libx32/ld-linux-x32.so.2], [/* 115 vars */]) = 0 23190 syscall_1073741836(0, 0, 0x400c, 0xbfebfbff, 0x37f, 0x64, 0x1000, 0x1000, 0x1000, 0x1000, 0x1000, 0x1000, 0x1000, 0x1000, 0x1000, 0x1000, 0x1000, 0x1000, 0x1000, 0x1000, 0x1000, 0x1000, 0x1000, 0x1000, 0x1000, 0x1000, 0x1000, 0x1000, 0x1000, 0x1000, 0x1000, 0x1000) = -1 (errno 38) 23190 syscall_1073742340(0x2, 0xfffbaa70, 0x1, 0xbfebfbff, 0xf77b0a3e, 0xf776d8cc, 0xf776ef7d, 0xf776ef7d, 0xf776ef7d, 0xf776ef7d, 0xf776ef7d, 0xf776ef7d, 0xf776ef7d, 0xf776ef7d, 0xf776ef7d, 0xf776ef7d, 0xf776ef7d, 0xf776ef7d, 0xf776ef7d, 0xf776ef7d, 0xf776ef7d, 0xf776ef7d, 0xf776ef7d, 0xf776ef7d, 0xf776ef7d, 0xf776ef7d, 0xf776ef7d, 0xf776ef7d, 0xf776ef7d, 0xf776ef7d, 0xf776ef7d, 0xf776ef7d) = -1 (errno 38) 23190 syscall_1073742055(0x7f, 0x403c, 0x7f, 0xbfebfbff, 0x40e7, 0xf776d8cc, 0x7, 0x7, 0x7, 0x7, 0x7, 0x7, 0x7, 0x7, 0x7, 0x7, 0x7, 0x7, 0x7, 0x7, 0x7, 0x7, 0x7, 0x7, 0x7, 0x7, 0x7, 0x7, 0x7, 0x7, 0x7, 0x7) = -1 (errno 38) 23190 syscall_1073741884(0x7f, 0x403c, 0x7f, 0xbfebfbff, 0x40e7, 0xf776d8cc, 0x7, 0x7, 0x7, 0x7, 0x7, 0x7, 0x7, 0x7, 0x7, 0x7, 0x7, 0x7, 0x7, 0x7, 0x7, 0x7, 0x7, 0x7, 0x7, 0x7, 0x7, 0x7, 0x7, 0x7, 0x7, 0x7) = -1 (errno 38) 23190 --- SIGSEGV (Segmentation fault) @ 0 (0) --- I wonder whether it may be a security bug. /libx32 is not necessarily a standard directory, and could for instance be NFS mounted, have write-access to more people, or whatever; only some particular packages use this directory, but if they are not installed, I assume that the admin is free to do whatever he wants with it, and tools like mkinitramfs are not supposed to run anything from it. And this is not a bug in ldd, as the ldd man page says: Security In the usual case, ldd invokes the standard dynamic linker (see ld.so(8)) with the LD_TRACE_LOADED_OBJECTS environment variable set to 1, which causes the linker to display the library dependencies. Be aware, however, that in some circumstances, some versions of ldd may attempt to obtain the dependency information by directly executing the program. Thus, you should never employ ldd on an untrusted executable, since this may result in the execution of arbitrary code. A safer alternative when dealing with untrusted executables is: $ objdump -p /path/to/program | grep NEEDED For this reason, I think that the use of ldd should be dropped entirely from initramfs-tools. It might ease privilege escalation if there's another security bug on the system. -- Package-specific info: -- initramfs sizes -rw-r--r-- 1 root root 13M 2013-08-24 23:54:26 /boot/initrd.img-3.10-1-amd64 -rw-r--r-- 1 root root 13M 2013-08-24 23:35:31 /boot/initrd.img-3.10-2-amd64 -rw-r--r-- 1 root root 13M 2013-08-24 23:36:02 /boot/initrd.img-3.8-1-amd64 -rw-r--r-- 1 root root 13M 2013-08-24 23:35:55 /boot/initrd.img-3.8-2-amd64 -rw-r--r-- 1 root root 13M 2013-08-24 23:35:46 /boot/initrd.img-3.9-1-amd64 -- /proc/cmdline root=/dev/mapper/xvii-root ro quiet reboot=pci -- resume RESUME=/dev/mapper/xvii-swap_1 -- /proc/filesystems ext3 fuseblk ext2 -- lsmod Module Size Used by cuse 12971 3 cpufreq_powersave 12454 0 cpufreq_stats 12866 0 cpufreq_userspace 12576 0 cpufreq_conservative14184 0 xt_multiport 12548 2 iptable_filter 12536 1 ip_tables 22036 1 iptable_filter x_tables 19041 3 ip_tables,xt_multiport,iptable_filter parport_pc 22409 0 ppdev 12763 0 lp 13025 0 parport31901 3 lp,ppdev,parport_pc bnep 17535 2 rfcomm 33471 0 bluetooth 170002 10 bnep,rfcomm crc16 12343 1 bluetooth binfmt_misc12925 1 uinput 17439 1 nfsd 192007 2 auth_rpcgss39085 1 nfsd oid_registry 12419 1 auth_rpcgss nfs_acl12511 1 nfsd nfs 110304 0 lockd 59673 2 nfs,nfsd dns_resolver 12641 1 nfs fscache37551 1 nfs sunrpc164583 6 nfs,nfsd,auth_rpcgss,lockd,nfs_acl ext2 59601 1 firewire_sbp2 17956 0 loop 22869 0 fuse 67503 2 cuse uvcvideo 66788 0 arc4 12543 2 iwldvm111931 0 coretemp 12898 0
Bug#720735: initramfs-tools: mkinitramfs uses ldd, which is insecure and generates core dumps
Control: tag -1 - security On Sun, 2013-08-25 at 00:37 +0200, Vincent Lefevre wrote: Package: initramfs-tools Version: 0.113 Severity: important Tags: security I've noticed that when running update-initramfs, a core dump was generated in the current directory, which is in itself a first bug. After looking at this problem with strace, I saw that this came from: /usr/bin/ldd /lib/firmware/cis/PCMLM28.cis apparently via mkinitramfs. The strace output shows: 23190 execve(/libx32/ld-linux-x32.so.2, [/libx32/ld-linux-x32.so.2], [/* 115 vars */]) = 0 23190 syscall_1073741836(0, 0, 0x400c, 0xbfebfbff, 0x37f, 0x64, 0x1000, 0x1000, 0x1000, 0x1000, 0x1000, 0x1000, 0x1000, 0x1000, 0x1000, 0x1000, 0x1000, 0x1000, 0x1000, 0x1000, 0x1000, 0x1000, 0x1000, 0x1000, 0x1000, 0x1000, 0x1000, 0x1000, 0x1000, 0x1000, 0x1000, 0x1000) = -1 (errno 38) 23190 syscall_1073742340(0x2, 0xfffbaa70, 0x1, 0xbfebfbff, 0xf77b0a3e, 0xf776d8cc, 0xf776ef7d, 0xf776ef7d, 0xf776ef7d, 0xf776ef7d, 0xf776ef7d, 0xf776ef7d, 0xf776ef7d, 0xf776ef7d, 0xf776ef7d, 0xf776ef7d, 0xf776ef7d, 0xf776ef7d, 0xf776ef7d, 0xf776ef7d, 0xf776ef7d, 0xf776ef7d, 0xf776ef7d, 0xf776ef7d, 0xf776ef7d, 0xf776ef7d, 0xf776ef7d, 0xf776ef7d, 0xf776ef7d, 0xf776ef7d, 0xf776ef7d, 0xf776ef7d) = -1 (errno 38) 23190 syscall_1073742055(0x7f, 0x403c, 0x7f, 0xbfebfbff, 0x40e7, 0xf776d8cc, 0x7, 0x7, 0x7, 0x7, 0x7, 0x7, 0x7, 0x7, 0x7, 0x7, 0x7, 0x7, 0x7, 0x7, 0x7, 0x7, 0x7, 0x7, 0x7, 0x7, 0x7, 0x7, 0x7, 0x7, 0x7, 0x7) = -1 (errno 38) 23190 syscall_1073741884(0x7f, 0x403c, 0x7f, 0xbfebfbff, 0x40e7, 0xf776d8cc, 0x7, 0x7, 0x7, 0x7, 0x7, 0x7, 0x7, 0x7, 0x7, 0x7, 0x7, 0x7, 0x7, 0x7, 0x7, 0x7, 0x7, 0x7, 0x7, 0x7, 0x7, 0x7, 0x7, 0x7, 0x7, 0x7) = -1 (errno 38) 23190 --- SIGSEGV (Segmentation fault) @ 0 (0) --- I wonder whether it may be a security bug. /libx32 is not necessarily a standard directory, and could for instance be NFS mounted, [...] What? It belongs to glibc; $ dpkg -S /libx32 libc6-x32: /libx32 Ben. -- Ben Hutchings Never put off till tomorrow what you can avoid all together. signature.asc Description: This is a digitally signed message part
Processed: Re: Bug#720735: initramfs-tools: mkinitramfs uses ldd, which is insecure and generates core dumps
Processing control commands: tag -1 - security Bug #720735 [initramfs-tools] initramfs-tools: mkinitramfs uses ldd, which is insecure and generates core dumps Removed tag(s) security. -- 720735: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=720735 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.b720735.13773880688270.transcr...@bugs.debian.org
Bug#720739: linux-image-3.10-2-amd64: autonomy loss with kernl 3.10
Package: src:linux Version: 3.10.7-1 Severity: normal Dear Maintainer, Since the update to kern 3.10 I've lost between 1h and 1h30 of autonomy on my Lenovo T420 model 4180AT9 Regards. -- Package-specific info: ** Version: Linux version 3.10-2-amd64 (debian-kernel@lists.debian.org) (gcc version 4.7.3 (Debian 4.7.3-6) ) #1 SMP Debian 3.10.7-1 (2013-08-17) ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.10-2-amd64 root=UUID=56341839-2550-45e7-bad3-f16c4244a68f ro quiet resume=UUID=56341839-2550-45e7-bad3-f16c4244a68f resume_offset=9574400 i915.i915_enable_fbc=1 i915.lvds_downclock=1 pcie_aspm=force ** Tainted: O (4096) * Out-of-tree module has been loaded. ** Kernel log: [ 8576.951713] ehci-pci :00:1d.0: power state changed by ACPI to D3hot [ 8576.951971] ehci-pci :00:1a.0: System wakeup enabled by ACPI [ 8576.967714] ehci-pci :00:1a.0: power state changed by ACPI to D3hot [ 8576.967744] e1000e :00:19.0: System wakeup enabled by ACPI [ 8576.999742] PM: noirq suspend of devices complete after 79.778 msecs [ 8576.20] ACPI: Preparing to enter system sleep state S3 [ 8577.002311] PM: Saving platform NVS memory [ 8577.003175] Disabling non-boot CPUs ... [ 8577.004596] smpboot: CPU 1 is now offline [ 8577.107740] smpboot: CPU 2 is now offline [ 8577.211756] smpboot: CPU 3 is now offline [ 8577.214139] ACPI: Low-level resume complete [ 8577.214213] PM: Restoring platform NVS memory [ 8577.216334] Enabling non-boot CPUs ... [ 8577.216574] smpboot: Booting Node 0 Processor 1 APIC 0x1 [ 8577.227959] Disabled fast string operations [ 8577.230549] Intel pstate controlling: cpu 1 [ 8577.230690] CPU1 is up [ 8577.230765] smpboot: Booting Node 0 Processor 2 APIC 0x2 [ 8577.241707] Disabled fast string operations [ 8577.243972] Intel pstate controlling: cpu 2 [ 8577.244026] CPU2 is up [ 8577.244103] smpboot: Booting Node 0 Processor 3 APIC 0x3 [ 8577.255044] Disabled fast string operations [ 8577.257361] Intel pstate controlling: cpu 3 [ 8577.257426] CPU3 is up [ 8577.260579] ACPI: Waking up from system sleep state S3 [ 8577.329861] i915 :00:02.0: power state changed by ACPI to D0 [ 8577.376073] ehci-pci :00:1a.0: power state changed by ACPI to D0 [ 8577.392073] ehci-pci :00:1a.0: System wakeup disabled by ACPI [ 8577.408464] ehci-pci :00:1d.0: power state changed by ACPI to D0 [ 8577.424072] ehci-pci :00:1d.0: System wakeup disabled by ACPI [ 8577.472162] sdhci-pci :0d:00.0: MMC controller base frequency changed to 50Mhz. [ 8577.472292] PM: noirq resume of devices complete after 142.439 msecs [ 8577.472571] PM: early resume of devices complete after 0.232 msecs [ 8577.472645] i915 :00:02.0: setting latency timer to 64 [ 8577.472707] mei_me :00:16.0: irq 42 for MSI/MSI-X [ 8577.472805] e1000e :00:19.0: System wakeup disabled by ACPI [ 8577.472814] e1000e :00:19.0: setting latency timer to 64 [ 8577.472822] ahci :00:1f.2: setting latency timer to 64 [ 8577.472888] e1000e :00:19.0: irq 44 for MSI/MSI-X [ 8577.473426] ehci-pci :00:1a.0: setting latency timer to 64 [ 8577.473502] snd_hda_intel :00:1b.0: irq 47 for MSI/MSI-X [ 8577.473527] ehci-pci :00:1d.0: setting latency timer to 64 [ 8577.489193] [drm] Wrong MCH_SSKPD value: 0x16040307 [ 8577.489194] [drm] This can cause pipe underruns and display issues. [ 8577.489194] [drm] Please upgrade your BIOS to fix this. [ 8577.684150] usb 1-1.6: reset high-speed USB device number 4 using ehci-pci [ 8577.808110] ata5: SATA link down (SStatus 0 SControl 300) [ 8577.816106] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 8577.818463] ata2.00: ACPI cmd e3/00:79:00:00:00:a0 (IDLE) succeeded [ 8577.818690] ata2.00: ACPI cmd e3/00:01:00:00:00:a0 (IDLE) succeeded [ 8577.818697] ata2.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out [ 8577.822720] ata2.00: ACPI cmd e3/00:79:00:00:00:a0 (IDLE) succeeded [ 8577.822913] ata2.00: ACPI cmd e3/00:01:00:00:00:a0 (IDLE) succeeded [ 8577.822918] ata2.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out [ 8577.824495] ata2.00: configured for UDMA/66 [ 8577.832106] ata4: SATA link down (SStatus 0 SControl 300) [ 8577.836149] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 8577.836705] ata3.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded [ 8577.836707] ata3.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out [ 8577.836708] ata3.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out [ 8577.837660] ata3.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded [ 8577.837661] ata3.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out [ 8577.837663] ata3.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out [ 8577.837999] ata3.00: configured for UDMA/100 [ 8577.852238] sd 2:0:0:0: [sdb] Starting disk [ 8579.360392] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [ 8579.616490] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 8579.617658] ata1.00:
Bug#720735: initramfs-tools: mkinitramfs uses ldd, which is insecure and generates core dumps
On 2013-08-25 00:47:36 +0100, Ben Hutchings wrote: What? It belongs to glibc; $ dpkg -S /libx32 libc6-x32: /libx32 If libc6-x32 is not installed, this directory doesn't belong to anything! $ dpkg -S /libx32 dpkg-query: no path found matching pattern /libx32 So, there's nothing wrong in mounting it via NFS, and the system mustn't use it! -- Vincent Lefèvre vinc...@vinc17.net - Web: http://www.vinc17.net/ 100% accessible validated (X)HTML - Blog: http://www.vinc17.net/blog/ Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130825001337.ga7...@xvii.vinc17.org
Bug#720743: [firmware-brcm80211] the firmware crashes kernel-3.10.9
Package: firmware-brcm80211 Version: 0.39~bpo70+1 Severity: normal --- Please enter the report below this line. --- The last firmware provided in unstable (should be 0.40) doesn't work with my 3.8.13 custom kernel, and what is worse, causes kernel opses in my custom 3.10.9 kernel locking it totally. Reverting to any previous version down to the one present in wheezy at least allows to connect with kernel 3.8.13, but all of them crashes the kernel 3.10.9. Best regards Valerio --- System information. --- Architecture: amd64 Kernel: Linux 3.8.13 Debian Release: jessie/sid 990 unstablemi.mirror.garr.it 990 unstableftp.uk.debian.org 990 unstableftp.it.debian.org 500 wheezy activsoftware.co.uk 500 testing mi.mirror.garr.it 500 testing ftp.uk.debian.org 500 stable deb.opera.com 1 experimentalmi.mirror.garr.it 1 experimentalftp.uk.debian.org --- Package information. --- Package's Depends field is empty. Package's Recommends field is empty. Suggests (Version) | Installed ==-+-=== initramfs-tools| 0.113 linux-image| Valerio -- 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/2738690.jtZ8c9SKF7@asterix
