Bug#816157: marked as done (linux-image-4.4.0-1-amd64: Lenovo Ideapad Y700 failts to boot)
Your message dated Thu, 17 Mar 2016 12:35:54 + with message-id and subject line Bug#815125: fixed in linux 4.4.6-1 has caused the Debian Bug report #815125, regarding linux-image-4.4.0-1-amd64: Lenovo Ideapad Y700 failts to boot 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.) -- 815125: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815125 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Version: 4.4.2-3 Severity: important Dear Maintainer, I was asked to report again, for the but which appeared to be different issue, but was raised here https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815125 Boot parameter "efi=noruntime" allows kernel to boot, otherwise "ACPI Error: 1 table load failures, 8 sucessful (20150930/tbxload-214)" is the last line I was able to capture with full screen provided in 815125 but report. Kernel is not usable in that way, as it wont boot, unless this efi is disabled. -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information sys_vendor: LENOVO product_name: 80NV product_version: Lenovo ideapad Y700-15ISK chassis_vendor: LENOVO chassis_version: Lenovo ideapad Y700-15ISK bios_vendor: LENOVO bios_version: CDCN25WW board_vendor: LENOVO board_name: Allsparks 5A board_version: NO DPK ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation Sky Lake Host Bridge/DRAM Registers [8086:1910] (rev 07) Subsystem: Lenovo Skylake Host Bridge/DRAM Registers [17aa:3802] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 00:01.0 PCI bridge [0604]: Intel Corporation Sky Lake PCIe Controller (x16) [8086:1901] (rev 07) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport Kernel modules: shpchp 00:02.0 VGA compatible controller [0300]: Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo Skylake Integrated Graphics [17aa:3802] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- [disabled] Capabilities: Kernel driver in use: i915 Kernel modules: i915 00:14.0 USB controller [0c03]: Intel Corporation Sunrise Point-H USB 3.0 xHCI Controller [8086:a12f] (rev 31) (prog-if 30 [XHCI]) Subsystem: Lenovo Sunrise Point-H USB 3.0 xHCI Controller [17aa:3802] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Kernel driver in use: xhci_hcd Kernel modules: xhci_pci 00:16.0 Communication controller [0780]: Intel Corporation Sunrise Point-H CSME HECI #1 [8086:a13a] (rev 31) Subsystem: Lenovo Sunrise Point-H CSME HECI [17aa:3802] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: mei_me Kernel modules: mei_me 00:17.0 SATA controller [0106]: Intel Corporation Sunrise Point-H SATA Controller [AHCI mode] [8086:a103] (rev 31) (prog-if 01 [AHCI 1.0]) Subsystem: Lenovo Sunrise Point-H SATA Controller [AHCI mode] [17aa:3802] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Kernel driver in use: ahci Kernel modules: ahci 00:1c.0 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express Root Port #2 [8086:a111] (rev f1) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport Kernel modules: shpchp 00:1
Bug#815726: marked as done (initramfs-tools requires newer coreutils for ln -r)
Your message dated Sun, 20 Mar 2016 01:55:19 + with message-id <1458438919.2953.51.ca...@decadent.org.uk> and subject line Re: Bug#815726: initramfs-tools requires newer coreutils for ln -r has caused the Debian Bug report #815726, regarding initramfs-tools requires newer coreutils for ln -r 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.) -- 815726: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815726 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: initramfs-tools Version: 0.123 Upgrading initramfs-tools creates non working initrds if you don't upgrade coreutils; Adding config /etc/initramfs-tools/conf.d/resume Adding binary-link /sbin/modprobe ln: invalid option -- 'r' Try `ln --help' for more information. Adding binary /bin/kmod Adding library-link /lib/x86_64-linux-gnu/libc.so.6 (...) Fix was: Unpacking coreutils (8.24-1) over (8.13-3) ... But initramfs-tools should have a dependency on the minimal coreutils it needs to avoid such issues. Thanks, Marc -- "A mouse is a device used to point at the xterm you want to type in" - A.S.R. Microsoft is to operating systems what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ --- End Message --- --- Begin Message --- On Tue, 2016-02-23 at 21:03 -0800, Marc MERLIN wrote: > Package: initramfs-tools > Version: 0.123 > > Upgrading initramfs-tools creates non working initrds if you don't upgrade > coreutils; > Adding config /etc/initramfs-tools/conf.d/resume > Adding binary-link /sbin/modprobe > ln: invalid option -- 'r' > Try `ln --help' for more information. > Adding binary /bin/kmod > Adding library-link /lib/x86_64-linux-gnu/libc.so.6 > (...) > > Fix was: > Unpacking coreutils (8.24-1) over (8.13-3) ... > > But initramfs-tools should have a dependency on the minimal coreutils it > needs to avoid such issues. You must upgrade fully to stable before installing anything from unstable. There is no requirement in policy to add versioned dependencies in unstable when the minimum version is less than that in stable. Ben. -- Ben Hutchings Humans are not rational beings; they are rationalising beings. signature.asc Description: This is a digitally signed message part --- End Message ---
Bug#815977: marked as done (kernel-image-4.4.0-1-sparc64-di: Please add sunvnet and sunvdc for d-i)
Your message dated Sun, 20 Mar 2016 01:52:04 + with message-id <1458438724.2953.48.ca...@decadent.org.uk> and subject line Re: Bug#815977: kernel-image-4.4.0-1-sparc64-di: Please add sunvnet and sunvdc for d-i has caused the Debian Bug report #815977, regarding kernel-image-4.4.0-1-sparc64-di: Please add sunvnet and sunvdc for d-i 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.) -- 815977: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815977 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: linux Version: 4.4.2-3 Severity: normal User: debian-sp...@lists.debian.org Usertags: sparc64 Hi! Several sparc64 users recently reported that the sunvnet and sunvdc modules have been missing while installing with debian-installer and they had to load these manually [1]. As it turns out, these module have been missing in the past in the d-i kernel package on sparc [2], thus I guess the fix should be the same. If this is not directly a kernel issue but an issue with the installation images I am creating, please let me know. But since I couldn't anything in d-i which allows me to define a list of modules to be loaded, I assume it's something to be changed in the kernel package. Thanks, Adrian > [1] https://lists.debian.org/debian-sparc/2016/02/msg00054.html > [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=504702 -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 --- End Message --- --- Begin Message --- On Fri, 2016-02-26 at 10:37 +0100, John Paul Adrian Glaubitz wrote: > Source: linux > Version: 4.4.2-3 > Severity: normal > User: debian-sp...@lists.debian.org > Usertags: sparc64 > > Hi! > > Several sparc64 users recently reported that the sunvnet and sunvdc modules > have been missing while installing with debian-installer and they had to > load these manually [1]. > > As it turns out, these module have been missing in the past in the d-i > kernel package on sparc [2], thus I guess the fix should be the same. > > If this is not directly a kernel issue but an issue with the installation > images I am creating, please let me know. But since I couldn't anything > in d-i which allows me to define a list of modules to be loaded, I assume > it's something to be changed in the kernel package. $ git grep -E 'sunvdc|sunvnet' debian/installer/ debian/installer/sparc64/modules/sparc64/nic-modules:sunvnet ? debian/installer/sparc64/modules/sparc64/scsi-core-modules:sunvdc ? $ dpkg-deb -c /tmp/nic-modules-4.4.0-1-sparc64-di_4.4.6-1_sparc64.udeb | grep sunvnet -rw-r--r-- root/root 43488 2016-03-17 23:05 ./lib/modules/4.4.0-1-sparc64/kernel/drivers/net/ethernet/sun/sunvnet.ko $ dpkg-deb -c /tmp/scsi-core-modules-4.4.0-1-sparc64-di_4.4.6-1_sparc64.udeb | grep sunvdc -rw-r--r-- root/root 28680 2016-03-17 23:04 ./lib/modules/4.4.0-1-sparc64/kernel/drivers/block/sunvdc.ko All looks good to me. Sounds like you're not including the right packages in your installer image. Ben. -- Ben Hutchings Humans are not rational beings; they are rationalising beings. signature.asc Description: This is a digitally signed message part --- End Message ---
Processed: tagging 816094
Processing commands for cont...@bugs.debian.org: > tags 816094 - moreinfo Bug #816094 [src:linux] linux-image-4.4.0-1-amd64: Hangs (crashes ?) under xorg when an external screen is plugged in the VGA video output Ignoring request to alter tags of bug #816094 to the same tags previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 816094: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816094 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bug 818494 is forwarded to https://bugzilla.kernel.org/show_bug.cgi?id=98931
Processing commands for cont...@bugs.debian.org: > forwarded 818494 https://bugzilla.kernel.org/show_bug.cgi?id=98931 Bug #818494 [src:linux] linux-image-4.5.0-rc7-amd64: backlight control doesn't work on ASUS UX305 Set Bug forwarded-to-address to 'https://bugzilla.kernel.org/show_bug.cgi?id=98931'. > thanks Stopping processing here. Please contact me if you need assistance. -- 818494: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818494 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#818467: linux-image-4.4.0-1-amd64: Kernel oops after disconnecting an external USB disk
Package: src:linux Version: 4.4.4-2 Severity: important Dear Maintainer, After the installation of the Linux kernel 4.4.0-1-amd64, every time I disconnect an external USB disk the following lines appear in the syslog: Mar 16 18:23:23 gretux udisksd[2193]: Unmounted /dev/sdd1 on behalf of uid 1000 Mar 16 18:23:59 gretux kernel: [33259.500440] usb 2-2.4: USB disconnect, device number 3 Mar 16 18:24:03 gretux kernel: [33263.469332] colord-sane[17056]: segfault at 7fc5672ed648 ip 7fc5672ed648 sp 7fffbc373738 error 14 in librt-2.22.so[7fc56774f000+1ff000] Mar 16 18:24:24 gretux kernel: [33284.470340] INFO: rcu_sched self-detected stall on CPU Mar 16 18:24:24 gretux kernel: [33284.470344] 2-...: (5250 ticks this GP) idle=50b/141/0 softirq=2776730/2776730 fqs=3779 Mar 16 18:24:24 gretux kernel: [33284.470346](t=5250 jiffies g=770267 c=770266 q=985) Mar 16 18:24:24 gretux kernel: [33284.470347] Task dump for CPU 2: Mar 16 18:24:24 gretux kernel: [33284.470348] colord-sane R running task 0 17056932 0x0008 Mar 16 18:24:24 gretux kernel: [33284.470351] 0003 8988eeef 810d3b53 88022f316640 Mar 16 18:24:24 gretux kernel: [33284.470361] 81a506c0 81b004c0 810d Mar 16 18:24:24 gretux kernel: [33284.470363] 88026328 8801a470d280 8800c4ca4b08 815761c0 Mar 16 18:24:24 gretux kernel: [33284.470374] Call Trace: Mar 16 18:24:24 gretux kernel: [33284.470375][] ? rcu_dump_cpu_stacks+0x83/0xd0 Mar 16 18:24:24 gretux kernel: [33284.470382] [] ? rcu_check_callbacks+0x4d7/0x790 Mar 16 18:24:24 gretux kernel: [33284.470385] [] ? prb_retire_current_block+0x100/0x100 Mar 16 18:24:24 gretux kernel: [33284.470387] [] ? tick_sched_handle.isra.14+0x50/0x50 Mar 16 18:24:24 gretux kernel: [33284.470389] [] ? update_process_times+0x32/0x60 Mar 16 18:24:24 gretux kernel: [33284.470391] [] ? tick_sched_handle.isra.14+0x20/0x50 Mar 16 18:24:24 gretux kernel: [33284.470392] [] ? tick_sched_timer+0x38/0x70 Mar 16 18:24:24 gretux kernel: [33284.470393] [] ? __hrtimer_run_queues+0xfa/0x290 Mar 16 18:24:24 gretux kernel: [33284.470395] [] ? hrtimer_interrupt+0x99/0x190 Mar 16 18:24:24 gretux kernel: [33284.470399] [] ? smp_apic_timer_interrupt+0x39/0x50 Mar 16 18:24:24 gretux kernel: [33284.470400] [] ? apic_timer_interrupt+0x82/0x90 Mar 16 18:24:24 gretux kernel: [33284.470401][] ? acct_collect+0x56/0x1a0 Mar 16 18:24:24 gretux kernel: [33284.470404] [] ? acct_collect+0x42/0x1a0 Mar 16 18:24:24 gretux kernel: [33284.470406] [] ? do_exit+0x4cf/0xad0 Mar 16 18:24:24 gretux kernel: [33284.470408] [] ? do_group_exit+0x3a/0xa0 Mar 16 18:24:24 gretux kernel: [33284.470410] [] ? get_signal+0x298/0x620 Mar 16 18:24:24 gretux kernel: [33284.470412] [] ? do_signal+0x36/0x670 Mar 16 18:24:24 gretux kernel: [33284.470413] [] ? signal_wake_up_state+0x1a/0x30 Mar 16 18:24:24 gretux kernel: [33284.470414] [] ? __send_signal+0x1bb/0x420 Mar 16 18:24:24 gretux kernel: [33284.470416] [] ? force_sig_info+0xc0/0xd0 Mar 16 18:24:24 gretux kernel: [33284.470418] [] ? force_sig_info_fault+0x6e/0x90 Mar 16 18:24:24 gretux kernel: [33284.470420] [] ? exit_to_usermode_loop+0x85/0xc0 Mar 16 18:24:24 gretux kernel: [33284.470422] [] ? retint_user+0x8/0x10 Mar 16 18:24:46 gretux console-kit-daemon[1962]: (process:17078): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed Mar 16 18:24:46 gretux console-kit-daemon[1962]: missing action Mar 16 18:24:46 gretux org.kde.kaccessibleapp[6847]: kaccessibleapp: Fatal IO error: client killed Mar 16 18:24:46 gretux org.freedesktop.Notifications[6847]: xfce4-notifyd: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Mar 16 18:24:46 gretux org.a11y.atspi.Registry[6910]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0" Mar 16 18:24:46 gretux org.a11y.atspi.Registry[6910]: after 33013 requests (33013 known processed) with 0 events remaining. Mar 16 18:24:46 gretux org.gtk.vfs.Daemon[6847]: A connection to the bus can't be made Mar 16 18:24:46 gretux org.freedesktop.Tracker1[6847]: Received signal:15->'Terminated' Mar 16 18:24:46 gretux org.freedesktop.Tracker1[6847]: OK Mar 16 18:24:46 gretux org.gtk.vfs.Daemon[6847]: A connection to the bus can't be made ar 16 18:24:46 gretux org.gtk.vfs.Daemon[6847]: A connection to the bus can't be made Mar 16 18:24:46 gretux org.gtk.vfs.Daemon[6847]: A connection to the bus can't be made Mar 16 18:24:50 gretux kernel: [33311.109551] NMI watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [colord-sane:17056] Mar 16 18:24:50 gretux kernel: [33311.109553] Modules linked in: nvidia_modeset(PO) nvidia(PO) fuse xt_tcpudp xt_conntrack ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_filter ip_tables x_tables cpufreq_powersave cpufreq_conservative cpufreq_userspace cpufreq_stats binfmt_misc intel_r
Bug#815125: Boot failure with Debian linux 4.4.2 package
Hi Ben, Hi Matt, I can confirm as well that the latest package version 4.4.6-1 fixes the issue on a Lenovo ThinkPad Tablet 8. Thanks a lot, Jérôme
Can We Implement A String Delimiter That Cannot Be In A String
Please forgive me if this is the wrong forum for this topic. I am trying to understand why the delimiter problem remains unsolved. The delimiter problem is the complication created by using valid string characters as string delimiters, making a string like this Mary's statement was, "I'm happy with Jill's "Thank you's, which included 'personal comments' relevant to each guest's favorite charity." difficult to work with as a string to be handled by a computer program. I am familiar with escaping characters, but that can get complicated, such as when using regex at the command line where the string has to be delimited for the shell to know what to do and that can make the simultaneous delimiting of the regex command extremely challenging. The solution seems almost obvious: create a delimiter that can be inserted where programmers need them but are not part of human language. If the delimiter was different for the start of a string vs then end, strings could nested and there never would be any confusion. What would it take to implement something like this, and why has this not been done already? -- Dan Allen Houston-DATA.COM 215 Marshall Street Houston, Texas 77006 713-806-8783 d...@houston-data.com
Bug#818386: marked as done (Fix support for DRA7xx EVMs)
Your message dated Thu, 17 Mar 2016 12:35:54 + with message-id and subject line Bug#818386: fixed in linux 4.4.6-1 has caused the Debian Bug report #818386, regarding Fix support for DRA7xx EVMs 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.) -- 818386: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818386 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Version: 4.4.4-2 Severity: important The armmp kernel is supposed to support DRA7xx systems, but currently fails to boot on the EVM as it's missing the driver for the GPIO expanders. Ben. diff --git a/debian/changelog b/debian/changelog index 8626fbb297af..f39d46d900a2 100644 --- a/debian/changelog +++ b/debian/changelog @@ -78,6 +78,7 @@ linux (4.4.5-1) UNRELEASED; urgency=medium - efi: Fix boot crash by always mapping boot service regions into new EFI page tables (Closes: #815125) - mm/pat: Fix boot crash when 1GB pages are not supported by cpu + * [armhf] gpio: Enable GPIO_PCF857X as module, needed by TI DRA7xx EVMs [ Ian Campbell ] * [arm64] Enable ARCH_HISI (Hisilicon) and the set of currently available diff --git a/debian/config/armhf/config.armmp b/debian/config/armhf/config.armmp index 1c71d6d24a09..af73db29fefd 100644 --- a/debian/config/armhf/config.armmp +++ b/debian/config/armhf/config.armmp @@ -235,6 +235,7 @@ CONFIG_RASPBERRYPI_FIRMWARE=y CONFIG_GPIOLIB=y CONFIG_GPIO_GENERIC_PLATFORM=m CONFIG_GPIO_PCA953X=m +CONFIG_GPIO_PCF857X=m CONFIG_GPIO_DA9052=m CONFIG_GPIO_PALMAS=y CONFIG_GPIO_TWL4030=y -- 2.7.0 -- Ben Hutchings Software Developer, Codethink Ltd. --- End Message --- --- Begin Message --- Source: linux Source-Version: 4.4.6-1 We believe that the bug you reported is fixed in the latest version of linux, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 818...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ben Hutchings (supplier of updated linux package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 17 Mar 2016 01:25:23 + Source: linux Binary: linux-source-4.4 linux-support-4.4.0-1 linux-doc-4.4 linux-manual-4.4 linux-libc-dev linux-headers-4.4.0-1-all linux-headers-4.4.0-1-all-alpha kernel-image-4.4.0-1-alpha-generic-di nic-modules-4.4.0-1-alpha-generic-di nic-wireless-modules-4.4.0-1-alpha-generic-di nic-shared-modules-4.4.0-1-alpha-generic-di serial-modules-4.4.0-1-alpha-generic-di usb-serial-modules-4.4.0-1-alpha-generic-di ppp-modules-4.4.0-1-alpha-generic-di pata-modules-4.4.0-1-alpha-generic-di cdrom-core-modules-4.4.0-1-alpha-generic-di scsi-core-modules-4.4.0-1-alpha-generic-di scsi-modules-4.4.0-1-alpha-generic-di loop-modules-4.4.0-1-alpha-generic-di btrfs-modules-4.4.0-1-alpha-generic-di ext4-modules-4.4.0-1-alpha-generic-di isofs-modules-4.4.0-1-alpha-generic-di jfs-modules-4.4.0-1-alpha-generic-di xfs-modules-4.4.0-1-alpha-generic-di fat-modules-4.4.0-1-alpha-generic-di md-modules-4.4.0-1-alpha-generic-di multipath-modules-4.4.0-1-alpha-generic-di usb-modules-4.4.0-1-alpha-generic-di usb-storage-modules-4.4.0-1-alpha-generic-di fb-modules-4.4.0-1-alpha-generic-di input-modules-4.4.0-1-alpha-generic-di event-modules-4.4.0-1-alpha-generic-di mouse-modules-4.4.0-1-alpha-generic-di nic-pcmcia-modules-4.4.0-1-alpha-generic-di pcmcia-modules-4.4.0-1-alpha-generic-di nic-usb-modules-4.4.0-1-alpha-generic-di sata-modules-4.4.0-1-alpha-generic-di core-modules-4.4.0-1-alpha-generic-di crc-modules-4.4.0-1-alpha-generic-di crypto-modules-4.4.0-1-alpha-generic-di crypto-dm-modules-4.4.0-1-alpha-generic-di ata-modules-4.4.0-1-alpha-generic-di nbd-modules-4.4.0-1-alpha-generic-di squashfs-modules-4.4.0-1-alpha-generic-di virtio-modules-4.4.0-1-alpha-generic-di zlib-modules-4.4.0-1-alpha-generic-di fuse-modules-4.4.0-1-alpha-generic-di srm-modules-4.4.0-1-alpha-generic-di linux-headers-4.4.0-1-common linux-image-4.4.0-1-alpha-generic linux-headers-4.4.0-1-alpha-generic linux-image-4.4.0-1-alpha-smp linux-headers-4.4.0-1-alpha-smp linux-headers-4.4.0-1-all-amd64 kernel-image-4.4.0-1-amd64-di nic-modules-4.4.0-1-amd64-di nic-wireless-
Bug#818577: spelling mistakes
Package: debian-kernel-handbook Version: 1.0.15 Dear maintainer, I've been reading at http://kernel-handbook.alioth.debian.org/index.html which I believe is related to the package "debian-kernel-handbook" as addressed here. I found a few spelling mistakes as following: http://kernel-handbook.alioth.debian.org/ch-scope.html "... executed with superuser priviliges, either ..." -> privileges http://kernel-handbook.alioth.debian.org/ch-modules.html "... are detected and neccessary kernel modules ..." -> necessary http://kernel-handbook.alioth.debian.org/ch-initramfs.html "... performs other neccessary initialization ..." -> necessary Hope that helps. Regards, Olivier
Bug#818502: kernel 3.17 is probably OK
Hi, report from testing so far. apate:~# getSystemId Libsmbios version: 2.2.28 Product Name: PowerEdge 1950 Vendor: Dell Inc. BIOS Version: 2.3.1 System ID: 0x01B3 Service Tag:BYV0W3J Express Service Code: 26052565375 I tested using shell oneliner in VM: i=0; while :; do let i=i+1; echo; echo "run $i ..."; echo; sleep 5; apt install -y linux-source || break; sleep 5; apt remove --auto-remove -y linux-source || break; done I took current kernel version from stable Linux apate 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt20-1+deb8u4 (2016-02-29) x86_64 GNU/Linux and did it 10 runs till crash. Number of iterations needed to crash was: 18, 6, 22, 10, 28, 16, 9, 1, 1, 6 I took kernel version 3.17 Linux apate 3.17-1-amd64 #1 SMP Debian 3.17-1~exp1 (2014-10-14) x86_64 GNU/Linux http://snapshot.debian.org:/archive/debian/20141130T220818Z/pool/main/l/linux/linux-image-3.17-1-amd64_3.17-1~exp1_amd64.deb and after 179 iterations there was no crash in VM. I think this kernel version is OK. Any suggestions what to test now? Thanks -- Zito
Bug#814508: initramfs-tools: bluetooth/hci fails
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Il Thu, Feb 25, 2016 at 10:09:02AM +0100, To Ben Hutchings scrisse: > Il Sat, Feb 13, 2016 at 02:03:38AM +, Ben Hutchings scrisse: > > Control: reassign -1 src:linux 4.3.5-1 > > > [cut] > > > > Yes, this sounds like a bug in either the rfkill driver or the BIOS. > > Check whether there's a BIOS update available that mentions fixes to > > Bluetooth or flight mode. > > News > > I have upgraded to new kernel (version 4.4.0-1-amd64 = 4.4.2-3) and the > problem has came back. > > If I boot with old 4.3.0-1, the bluetooth still works. [cut] Hi... Today, I have upgraded to the last kernel but the bluetooth doesn't work again. Maybe I have found the problem. From the syslog: Mar 19 13:21:08 G5045 kernel: [1.926615] usbcore: registered new interface driver btusb Mar 19 13:21:08 G5045 kernel: [1.929443] usb 2-1.3: firmware: failed to load ar3k/AthrBT_0x3101.dfu (-2) Mar 19 13:21:08 G5045 kernel: [1.930796] usb 2-1.3: Direct firmware load for ar3k/AthrBT_0x3101.dfu failed with error -2 Mar 19 13:21:08 G5045 kernel: [1.932120] Bluetooth: Loading patch file failed Mar 19 13:21:08 G5045 kernel: [1.933478] ath3k: probe of 2-1.3:1.0 failed with error -2 ~ <-su> # lsusb Bus 002 Device 004: ID 0cf3:3004 Atheros Communications, Inc. AR3012 Bluetooth 4.0 It seems that there's an incompatibility with the kernel 4.4 series. I have tried also to reinstall the firmware-atheros package. There is an old bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773310 Thanks - -- Stefano Callegari -BEGIN PGP SIGNATURE- Version: GnuPG v1 iEYEARECAAYFAlbtVLoACgkQHecMbhqYKHF3IwCgrC4E2xUmsUZpdzfTRMXkW+Kq R58Anj2j/pr7M1wCh4Hf5LDKz/KWgddH =fKQm -END PGP SIGNATURE-
Bug#812540: marked as done (Add ARCH_HISI for Lemaker HiKey support)
Your message dated Thu, 17 Mar 2016 12:35:54 + with message-id and subject line Bug#812540: fixed in linux 4.4.6-1 has caused the Debian Bug report #812540, regarding Add ARCH_HISI for Lemaker HiKey support 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.) -- 812540: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812540 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux Version: 4.3.3-7 Severity: wishlist Tags: d-i Dear kernel maintainers, while trying to get a d-i booted on a Lemaker HiKey, tbm pointed out that ARCH_HISI is not (yet) activated on linux. Please enable it so we can add HiKey support to Debian. TIA! Best, Kilian --- End Message --- --- Begin Message --- Source: linux Source-Version: 4.4.6-1 We believe that the bug you reported is fixed in the latest version of linux, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 812...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ben Hutchings (supplier of updated linux package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 17 Mar 2016 01:25:23 + Source: linux Binary: linux-source-4.4 linux-support-4.4.0-1 linux-doc-4.4 linux-manual-4.4 linux-libc-dev linux-headers-4.4.0-1-all linux-headers-4.4.0-1-all-alpha kernel-image-4.4.0-1-alpha-generic-di nic-modules-4.4.0-1-alpha-generic-di nic-wireless-modules-4.4.0-1-alpha-generic-di nic-shared-modules-4.4.0-1-alpha-generic-di serial-modules-4.4.0-1-alpha-generic-di usb-serial-modules-4.4.0-1-alpha-generic-di ppp-modules-4.4.0-1-alpha-generic-di pata-modules-4.4.0-1-alpha-generic-di cdrom-core-modules-4.4.0-1-alpha-generic-di scsi-core-modules-4.4.0-1-alpha-generic-di scsi-modules-4.4.0-1-alpha-generic-di loop-modules-4.4.0-1-alpha-generic-di btrfs-modules-4.4.0-1-alpha-generic-di ext4-modules-4.4.0-1-alpha-generic-di isofs-modules-4.4.0-1-alpha-generic-di jfs-modules-4.4.0-1-alpha-generic-di xfs-modules-4.4.0-1-alpha-generic-di fat-modules-4.4.0-1-alpha-generic-di md-modules-4.4.0-1-alpha-generic-di multipath-modules-4.4.0-1-alpha-generic-di usb-modules-4.4.0-1-alpha-generic-di usb-storage-modules-4.4.0-1-alpha-generic-di fb-modules-4.4.0-1-alpha-generic-di input-modules-4.4.0-1-alpha-generic-di event-modules-4.4.0-1-alpha-generic-di mouse-modules-4.4.0-1-alpha-generic-di nic-pcmcia-modules-4.4.0-1-alpha-generic-di pcmcia-modules-4.4.0-1-alpha-generic-di nic-usb-modules-4.4.0-1-alpha-generic-di sata-modules-4.4.0-1-alpha-generic-di core-modules-4.4.0-1-alpha-generic-di crc-modules-4.4.0-1-alpha-generic-di crypto-modules-4.4.0-1-alpha-generic-di crypto-dm-modules-4.4.0-1-alpha-generic-di ata-modules-4.4.0-1-alpha-generic-di nbd-modules-4.4.0-1-alpha-generic-di squashfs-modules-4.4.0-1-alpha-generic-di virtio-modules-4.4.0-1-alpha-generic-di zlib-modules-4.4.0-1-alpha-generic-di fuse-modules-4.4.0-1-alpha-generic-di srm-modules-4.4.0-1-alpha-generic-di linux-headers-4.4.0-1-common linux-image-4.4.0-1-alpha-generic linux-headers-4.4.0-1-alpha-generic linux-image-4.4.0-1-alpha-smp linux-headers-4.4.0-1-alpha-smp linux-headers-4.4.0-1-all-amd64 kernel-image-4.4.0-1-amd64-di nic-modules-4.4.0-1-amd64-di nic-wireless-modules-4.4.0-1-amd64-di nic-shared-modules-4.4.0-1-amd64-di serial-modules-4.4.0-1-amd64-di usb-serial-modules-4.4.0-1-amd64-di ppp-modules-4.4.0-1-amd64-di pata-modules-4.4.0-1-amd64-di cdrom-core-modules-4.4.0-1-amd64-di firewire-core-modules-4.4.0-1-amd64-di scsi-core-modules-4.4.0-1-amd64-di scsi-modules-4.4.0-1-amd64-di loop-modules-4.4.0-1-amd64-di btrfs-modules-4.4.0-1-amd64-di ext4-modules-4.4.0-1-amd64-di isofs-modules-4.4.0-1-amd64-di jfs-modules-4.4.0-1-amd64-di ntfs-modules-4.4.0-1-amd64-di xfs-modules-4.4.0-1-amd64-di fat-modules-4.4.0-1-amd64-di md-modules-4.4.0-1-amd64-di multipath-modules-4.4.0-1-amd64-di usb-modules-4.4.0-1-amd64-di usb-storage-modules-4.4.0-1-amd64-di pcmcia-storage-modules-4.4.0-1-amd64-di fb-modules-4.4.0-1-amd64-di input-modules-4.4.0-1-amd64-di event-modules-4.4.0-1-amd64-di mouse-modules-4.4.0-1-amd64-di nic-pcmcia-modules-4.4.0-1-amd64-di pcmcia-modules-4.4.0-1-amd64-di nic-usb-mo
Bug#818502: linux-image-3.16.0-4-amd64: data corruption in KVM VM & hypervisor with Intel CPU with early IntelVT
Package: src:linux Version: 3.16.7-ckt20-1+deb8u4 Severity: normal Dear Maintainer, I have very ugly and probably hard to analyze problem with filesystem corruption on KVM virtual and the hypervisor running on hardware with CPU from early IntelVT era (Both hypervisor and VM are Debian Jessie of course). I can report this problem meantime for hypervisor on Intel Xeon E5410 [1](Dell PowerEdge 1950) Intel Xeon E5430 [2](Dell PowerEdge 1950) Intel Core2 Duo E8400 [3] (some PC) the problem is NOT with the newer HW/CPU: Intel Xeon X5650 [4](Dell PowerEdge R710) Intel Xeon L5520 [5](Dell PowerEdge R710) Until Jessie we had no problems. After migration to Debian Jessie there was several times filesystem corruption on VM running monitoring several hosts using Icinga and writing performance data into RRD files. The snippets from syslog are produced with zfgrep -h -i -e 'Linux version ' -e Memory: -e EXT4 syslog-20*gz >/tmp/mong.syslog.txt attached... Now I invent the method for reproducing the problem in reasonable time. 1) Prepare a new VM storage 2G, RAM 256MiB 2) Install Debian Jessie (PXE, CD...) 200MB swap, root fs the rest 3) Shutdown a new VM and decrease memory allocation to 90MiB for it 4) Start VM and do some package management torture :). I used: while :; do apt install -y linux-source; sleep 10; apt remove --auto-remove -y linux-source; sleep 10; done On "faulty" CPU you get after a while: Unpacking gcc-4.9 (4.9.2-10) ... dpkg: unrecoverable fatal error, aborting: unable to fsync updated status of `man-db': Read-only file system rm: cannot remove ‘/var/cache/etckeeper/packagelist.pre-install’: Read-only file system E: Sub-process /usr/bin/dpkg returned an error code (2) E: Problem executing scripts DPkg::Post-Invoke 'if [ -x /usr/bin/etckeeper ]; then etckeeper post-install; fi' E: Sub-process returned an error code W: Not using locking for read only lock file /var/lib/dpkg/lock E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem. W: Not using locking for read only lock file /var/lib/dpkg/lock E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem. ... and in another terminal running journalctl -f: Mar 17 15:19:49 keryvm1 ssh-audit[1159]: zito : root access using connection 10.0.156.88 34352 172.30.1.29 22 Mar 17 15:19:49 keryvm1 logger[1186]: [audit zito as root/1156 on pts/1/10.0.156.88:34352->172.30.1.29:22]: #=== session opened === Mar 17 15:19:50 keryvm1 logger[1190]: [audit zito as root/1156 on pts/1/10.0.156.88:34352->172.30.1.29:22] /root: journalctl -f Mar 17 15:22:31 keryvm1 kernel: EXT4-fs error (device vda2): ext4_mb_generate_buddy:757: group 5, block bitmap and bg descriptor inconsistent: 4196 vs 4194 f$ ee clusters Mar 17 15:22:31 keryvm1 kernel: Aborting journal on device vda2-8. Mar 17 15:22:31 keryvm1 kernel: EXT4-fs (vda2): Remounting filesystem read-only Mar 17 15:22:31 keryvm1 kernel: [ cut here ] Mar 17 15:22:31 keryvm1 kernel: WARNING: CPU: 0 PID: 6534 at /build/linux-U7H2aZ/linux-3.16.7-ckt20/fs/ext4/ext4_jbd2.c:266 __ext4_handle_dirty_metadata+0x18$ /0x1d0 [ext4]() Mar 17 15:22:31 keryvm1 kernel: Modules linked in: nfsd auth_rpcgss oid_registry nfs_acl nfs lockd fscache sunrpc snd_hda_codec_generic snd_hda_intel ppdev s$ d_hda_controller snd_hda_codec ttm drm_kms_helper snd_hwdep evdev psmouse joydev pcspkr serio_raw i2c_piix4 snd_pcm drm snd_timer snd pvpanic i2c_core parpor$ _pc soundcore virtio_balloon parport virtio_console processor thermal_sys button autofs4 ext4 crc16 mbcache jbd2 hid_generic usbhid hid virtio_net virtio_blk sg sr_mod cdrom ata_generic ehci_pci uhci_hcd ehci_hcd ata_piix libata floppy virtio_pci virtio_ring virtio usbcore usb_common scsi_mod Mar 17 15:22:31 keryvm1 kernel: CPU: 0 PID: 6534 Comm: dpkg Not tainted 3.16.0-4-amd64 #1 Debian 3.16.7-ckt20-1+deb8u4 Mar 17 15:22:31 keryvm1 kernel: Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.7.5-20140531_083030-gandalf 04/01/2014 Mar 17 15:22:31 keryvm1 kernel: 0009 8150dcff 810677d7 Mar 17 15:22:31 keryvm1 kernel: 8800027f2570 ffe2 88be0328 Mar 17 15:22:31 keryvm1 kernel: a023fde0 a022065e 8800031514b0 8800027f2570 Mar 17 15:22:31 keryvm1 kernel: Call Trace: Mar 17 15:22:31 keryvm1 kernel: [] ? dump_stack+0x41/0x51 Mar 17 15:22:31 keryvm1 kernel: [] ? warn_slowpath_common+0x77/0x90 Mar 17 15:22:31 keryvm1 kernel: [] ? __ext4_handle_dirty_metadata+0x18e/0x1d0 [ext4] Mar 17 15:22:31 keryvm1 kernel: [] ? ext4_dirty_inode+0x25/0x60 [ext4] Mar 17 15:22:31 keryvm1 kernel: [] ? ext4_free_blocks+0x602/0xb90 [ext4] Mar 17 15:22:31 keryvm1 kernel: [] ? jbd2_journal_extend+0x71/0x1a0 [jbd2
Bug#818467: (linux-image-4.4.0-1-amd64: Kernel oops after disconnecting an external USB disk)
Hello, I performed several tests on the subject of this bug and I found out that it happens only if a use a specific USB disk. It doesn't show if I use another USB device such as a pen drive or a different disk and it doesn't show if I don't run X11. When I use the USB disk responsible for the kernel oops, while not using X11, this is what I find in /var/log/syslog: Mar 18 18:05:02 gretux kernel: [31132.186145] usb 4-2.4: new SuperSpeed USB device number 3 using xhci_hcd Mar 18 18:05:02 gretux kernel: [31132.217142] usb 4-2.4: New USB device found, idVendor=1058, idProduct=10b8 Mar 18 18:05:02 gretux kernel: [31132.225409] usb 4-2.4: New USB device strings: Mfr=1, Product=2, SerialNumber=5 Mar 18 18:05:02 gretux kernel: [31132.233653] usb 4-2.4: Product: Elements 10B8 Mar 18 18:05:02 gretux kernel: [31132.241893] usb 4-2.4: Manufacturer: Western Digital Mar 18 18:05:02 gretux kernel: [31132.241895] usb 4-2.4: SerialNumber: 575850314537345735433741 Mar 18 18:05:02 gretux mtp-probe: checking bus 4, device 3: "/sys/devices/pci:00/:00:1c.6/:06:00.0/usb4/4-2/4-2.4" Mar 18 18:05:02 gretux mtp-probe: bus: 4, device: 3 was not an MTP device Mar 18 18:05:02 gretux kernel: [31132.242436] usb-storage 4-2.4:1.0: USB Mass Storage device detected Mar 18 18:05:02 gretux kernel: [31132.242866] scsi host7: usb-storage 4-2.4:1.0 Mar 18 18:05:03 gretux kernel: [31133.243079] scsi 7:0:0:0: Direct-Access WD Elements 10B81012 PQ: 0 ANSI: 6 Mar 18 18:05:03 gretux kernel: [31133.253656] sd 7:0:0:0: Attached scsi generic sg4 type 0 Mar 18 18:05:03 gretux kernel: [31133.255625] sd 7:0:0:0: [sdd] Spinning up disk... Mar 18 18:05:10 gretux kernel: [31134.258094] ...ready Mar 18 18:05:10 gretux kernel: [31140.293441] sd 7:0:0:0: [sdd] 3906963456 512-byte logical blocks: (2.00 TB/1.82 TiB) Mar 18 18:05:10 gretux kernel: [31140.305016] sd 7:0:0:0: [sdd] Write Protect is off Mar 18 18:05:10 gretux kernel: [31140.305019] sd 7:0:0:0: [sdd] Mode Sense: 47 00 10 08 Mar 18 18:05:10 gretux kernel: [31140.305485] sd 7:0:0:0: [sdd] No Caching mode page found Mar 18 18:05:10 gretux kernel: [31140.305487] sd 7:0:0:0: [sdd] Assuming drive cache: write through Mar 18 18:05:10 gretux kernel: [31140.368350] sdd: sdd1 Mar 18 18:05:10 gretux kernel: [31140.369729] sd 7:0:0:0: [sdd] Attached SCSI disk Mar 18 18:06:43 gretux kernel: [31233.150733] EXT4-fs (sdd1): mounted filesystem with ordered data mode. Opts: (null) I'm using an nvidia driver for my GeForce GTS 450. I hope this might help. -- Fernando Santagata
Bug#818487: linux-image-4.5.0-rc7-amd64: enable CONFIG_ASUS_WIRELESS=m
Package: src:linux Version: 4.5~rc7-1~exp1 Severity: normal Dear Maintainer, On my new Asus UX305, wireless control (rfkill) is handled by an 'airplane' button, which is handled through ASUS_WIRELESS. Please enable this module by default, so I don't have to rebuild te kernel to get it ;) Kind regards Jan -- Package-specific info: ** Version: Linux version 4.5.0-rc7-amd64 (debian-kernel@lists.debian.org) (gcc version 5.3.1 20160224 (Debian 5.3.1-10) ) #1 SMP Debian 4.5~rc7-1~exp1 (2016-03-07) ** Command line: BOOT_IMAGE=/boot/vmlinuz-4.5.0-rc7-amd64 root=/dev/mapper/hermes-root ro quiet ** Tainted: W (512) * Taint on warning. ** Kernel log: [2.419384] snd_hda_codec_conexant hdaudioC0D0: Internal Mic=0x1a [2.419392] snd_hda_codec_conexant hdaudioC0D0: Mic=0x19 [2.420540] snd_hda_codec_conexant hdaudioC0D0: Enable sync_write for stable communication [2.432287] input: HDA Digital PCBeep as /devices/pci:00/:00:1f.3/sound/card0/input9 [2.433741] input: HDA Intel PCH Mic as /devices/pci:00/:00:1f.3/sound/card0/input10 [2.433951] input: HDA Intel PCH Headphone as /devices/pci:00/:00:1f.3/sound/card0/input11 [2.434143] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci:00/:00:1f.3/sound/card0/input12 [2.434425] input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci:00/:00:1f.3/sound/card0/input13 [2.434724] input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci:00/:00:1f.3/sound/card0/input14 [2.529613] clocksource: Switched to clocksource tsc [3.705714] Console: switching to colour frame buffer device 240x67 [3.712613] i915 :00:02.0: fb0: inteldrmfb frame buffer device [3.813865] [drm] RC6 on [3.877190] random: nonblocking pool is initialized [3.939098] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [3.939100] Bluetooth: BNEP filters: protocol multicast [3.939105] Bluetooth: BNEP socket layer initialized [4.127325] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready [4.127702] iwlwifi :02:00.0: L1 Enabled - LTR Enabled [4.128291] iwlwifi :02:00.0: L1 Enabled - LTR Enabled [4.189637] iwlwifi :02:00.0: L1 Enabled - LTR Enabled [4.190191] iwlwifi :02:00.0: L1 Enabled - LTR Enabled [4.213233] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready [4.280561] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready [ 40.697353] wlp2s0: authenticate with 84:c9:b2:6a:7c:4c [ 40.704098] wlp2s0: send auth to 84:c9:b2:6a:7c:4c (try 1/3) [ 40.705328] wlp2s0: authenticated [ 40.708258] wlp2s0: associate with 84:c9:b2:6a:7c:4c (try 1/3) [ 40.709510] wlp2s0: RX AssocResp from 84:c9:b2:6a:7c:4c (capab=0x11 status=0 aid=3) [ 40.711243] wlp2s0: associated [ 40.711266] IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0: link becomes ready [ 46.018949] [ cut here ] [ 46.019059] WARNING: CPU: 0 PID: 1550 at /build/linux-SGKJnh/linux-4.5~rc7/drivers/gpu/drm/i915/intel_uncore.c:599 hsw_unclaimed_reg_debug+0x65/0x80 [i915]() [ 46.019067] Unclaimed register detected after reading register 0x65f10 [ 46.019071] Modules linked in: ctr ccm bnep snd_hda_codec_hdmi snd_hda_codec_conexant snd_hda_codec_generic joydev arc4 intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass i2c_designware_platform i2c_designware_core crct10dif_pclmul crc32_pclmul ghash_clmulni_intel nls_utf8 nls_cp437 vfat fat iwlmvm mac80211 asus_nb_wmi asus_wmi sparse_keymap jitterentropy_rng iwlwifi cfg80211 sha256_ssse3 sha256_generic hmac drbg ansi_cprng aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper snd_hda_intel efi_pstore cryptd snd_hda_codec idma64 uvcvideo videobuf2_vmalloc snd_hda_core videobuf2_memops i915 virt_dma snd_hwdep videobuf2_v4l2 evdev snd_pcm pcspkr videobuf2_core serio_raw snd_timer efivars videodev snd soundcore media drm_kms_helper i2c_i801 drm mei_me shpchp sg mei [ 46.019192] i2c_algo_bit processor_thermal_device intel_lpss_pci intel_soc_dts_iosf wmi elan_i2c int3403_thermal hci_uart intel_lpss_acpi battery btqca intel_lpss video mfd_core int3402_thermal int340x_thermal_zone ac int3400_thermal tpm_crb acpi_thermal_rel acpi_als kfifo_buf industrialio tpm_tis acpi_pad button tpm processor btusb btrtl btbcm btintel bluetooth rfkill crc16 parport_pc ppdev lp parport efivarfs autofs4 xfs libcrc32c dm_mod sd_mod crc32c_intel ahci libahci xhci_pci libata xhci_hcd scsi_mod usbcore usb_common thermal i2c_hid hid fjes [ 46.019288] CPU: 0 PID: 1550 Comm: TVGuiSlave.64 Not tainted 4.5.0-rc7-amd64 #1 Debian 4.5~rc7-1~exp1 [ 46.019292] Hardware name: ASUSTeK COMPUTER INC. UX305UA/UX305UA, BIOS UX305UA.201 10/12/2015 [ 46.019298] 0086 fcd7774d 81301585 88008111b9a8 [ 46.019308] a06fa538 8107900d 881b 88008111ba00 [ 46.019316] 881b0080 0206 8107909c [ 46.019325] Call T
Bug#818598: src:linux: MTD device probe failed after migrating kernel variant from -orion5x to -marvell
Package: src:linux Version: 4.4.6-1 Severity: normal Control: notfound -1 4.4-1~exp1 Control: found -1 4.4.1-1~exp1 X-Debbugs-Cc: rogershim...@gmail.com Dear Maintainer, I found my orion5x based Linkstation started to fail probing MTD device, which stores u-boot binary and environment, after variant migration from -orion5x to -marvell. Kernel log with version info is like the following: Linux LS-GL 4.4.0-trunk-orion5x #1 Debian 4.4-1~exp1 (2016-01-19) armv5tel GNU/Linux [1.838495] Found: SST 39LF020 [1.841662] f400.flash: Found 1 x8 devices at 0x0 in 8-bit bank [1.847985] number of JEDEC chips: 1 [1.868437] 3 ofpart partitions found on MTD device f400.flash [1.874705] Creating 3 MTD partitions on "f400.flash": [1.880288] 0x-0x0003 : "header" [1.06] 0x0003-0x0003f000 : "uboot" [1.897299] 0x0003f000-0x0004 : "uboot_env" Linux LS-GL 4.4.0-trunk-marvell #1 Debian 4.4.1-1~exp1 (2016-02-10) armv5tel GNU/Linux [1.716090] Found: SST 39LF020 [1.719184] f400.flash: Found 1 x8 devices at 0x0 in 8-bit bank [1.742133] Support for command set 0002 not present [1.747188] gen_probe: No supported Vendor Command Set found [1.752919] of-flash f400.flash: do_map_probe() failed for type jedec_probe [1.771450] of-flash f400.flash: do_map_probe() failed I uses the same DTB, which ships with latest sid kernel, to do previous test. (I put the DTB in /etc/flash-kernel/dtbs/) It with the patches I applied: - https://anonscm.debian.org/cgit/kernel/linux.git/tree/debian/patches/features/arm/device-tree?h=sid I also checked the diff of kernel config for the two kernels, but found no clue. And, the kirkwood based Linkstation doesn't have this issue. Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 17B3ACB1
Bug#818336: linux-image-4.3.0-1-amd64: `ulimit -c` not respected when kernel.core_pattern is a pipe
Control: tag -1 moreinfo On Tue, 2016-03-15 at 21:48 -0700, Ben Longbons wrote: > Package: src:linux > Version: 4.3.5-1 > Severity: normal > > Dear Maintainer, > > When the sysctl option kernel.core_pattern is a pipe (for example, the > default configuration on systemd-based systems), then `ulimit -c` is not > respected. [...] This behaviour is intentional. The command handling core dumps can apply a more sophisticated policy. Maybe the kernel should tell it what the task's limit is, though. Ben. -- Ben Hutchings If you seem to know what you are doing, you'll be given more to do. signature.asc Description: This is a digitally signed message part
Processed: forcibly merging 814855 818646
Processing commands for cont...@bugs.debian.org: > forcemerge 814855 818646 Bug #814855 [src:linux] linux-image-4.4.0-trunk-amd64: Please restore snd-emu10k1 module Bug #815787 [src:linux] pulseaudio: sound card no longer working Bug #818646 [src:linux] linux-image-4.4.0-1-amd64: CONFIG_ZONE_DMA is not set Marked as found in versions linux/4.4.2-2 and linux/4.4.1-1~exp1. Added tag(s) wontfix and moreinfo. Bug #815787 [src:linux] pulseaudio: sound card no longer working Marked as found in versions linux/4.4.6-1. Marked as found in versions linux/4.4.6-1. Merged 814855 815787 818646 > thanks Stopping processing here. Please contact me if you need assistance. -- 814855: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814855 815787: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815787 818646: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818646 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#818386: Fix support for DRA7xx EVMs
Package: src:linux Version: 4.4.4-2 Severity: important The armmp kernel is supposed to support DRA7xx systems, but currently fails to boot on the EVM as it's missing the driver for the GPIO expanders. Ben. diff --git a/debian/changelog b/debian/changelog index 8626fbb297af..f39d46d900a2 100644 --- a/debian/changelog +++ b/debian/changelog @@ -78,6 +78,7 @@ linux (4.4.5-1) UNRELEASED; urgency=medium - efi: Fix boot crash by always mapping boot service regions into new EFI page tables (Closes: #815125) - mm/pat: Fix boot crash when 1GB pages are not supported by cpu + * [armhf] gpio: Enable GPIO_PCF857X as module, needed by TI DRA7xx EVMs [ Ian Campbell ] * [arm64] Enable ARCH_HISI (Hisilicon) and the set of currently available diff --git a/debian/config/armhf/config.armmp b/debian/config/armhf/config.armmp index 1c71d6d24a09..af73db29fefd 100644 --- a/debian/config/armhf/config.armmp +++ b/debian/config/armhf/config.armmp @@ -235,6 +235,7 @@ CONFIG_RASPBERRYPI_FIRMWARE=y CONFIG_GPIOLIB=y CONFIG_GPIO_GENERIC_PLATFORM=m CONFIG_GPIO_PCA953X=m +CONFIG_GPIO_PCF857X=m CONFIG_GPIO_DA9052=m CONFIG_GPIO_PALMAS=y CONFIG_GPIO_TWL4030=y -- 2.7.0 -- Ben Hutchings Software Developer, Codethink Ltd.
Processed: src:linux: MTD device probe failed after migrating kernel variant from -orion5x to -marvell
Processing control commands: > notfound -1 4.4-1~exp1 Bug #818598 [src:linux] src:linux: MTD device probe failed after migrating kernel variant from -orion5x to -marvell Ignoring request to alter found versions of bug #818598 to the same values previously set > found -1 4.4.1-1~exp1 Bug #818598 [src:linux] src:linux: MTD device probe failed after migrating kernel variant from -orion5x to -marvell Marked as found in versions linux/4.4.1-1~exp1. -- 818598: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818598 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#818646: linux-image-4.4.0-1-amd64: CONFIG_ZONE_DMA is not set
Julien Cristau wrote on 19/03/16 20:09: On Sat, Mar 19, 2016 at 15:46:46 +1030, Arthur Marsh wrote: I usually run custom kernels based off the configuration of recent Debian kernels. I notice that as of 4.4.0-1-amd64 (and hence also linux-image-4.5.0-rc7-amd64) that CONFIG_ZONE_DMA is not set and that disables the EMU10K ALSA sound driver which is needed for a card that I was considering adding to this machine. I do not know if this was an upstream or Debian change, intentional or not, but it is an unpleasant surprise to discover hardware support removed especially as at least one ALSA developer runs this hardware himself. See bugs #814855 and #815787. Cheers, Julien Thanks, but the rationale was really deeply buried in the bug reports rather than in the Debian changelog, which would have been more helpful if it stated what the change was to support and what modules would no longer be in the Debian kernel package as a result. My Athlon64 machine's onboard sound had one of its inputs fail and I wanted to use the Soundblaster Audigy card from this machine. Although I like building custom kernels, it is also really helpful to be able to run a stock kernel to compare things if a custom kernel has a problem. Regards, Arthur.
Bug#818646: linux-image-4.4.0-1-amd64: CONFIG_ZONE_DMA is not set
On Sat, Mar 19, 2016 at 15:46:46 +1030, Arthur Marsh wrote: > I usually run custom kernels based off the configuration of recent > Debian kernels. > > I notice that as of 4.4.0-1-amd64 (and hence also linux-image-4.5.0-rc7-amd64) > that CONFIG_ZONE_DMA is not set and that disables the EMU10K ALSA sound driver > which is needed for a card that I was considering adding to this machine. > > I do not know if this was an upstream or Debian change, intentional or not, > but it is an unpleasant surprise to discover hardware support removed > especially as at least one ALSA developer runs this hardware himself. > See bugs #814855 and #815787. Cheers, Julien
Re: Reduce required age for src:linux
On Sat, Mar 19, 2016 at 03:19:20 +, Ben Hutchings wrote: > Linux 4.4 has been kept out of testing due to regressions, most notably > in EFI support on amd64. These should all be resolved in the current > unstable version, 4.4.6-1, and I would like to get this into testing as > soon as possible, making way for 4.5 in unstable. > > Please consider reducing the required age to 2 days. > Done. Cheers, Julien
Bug#811368: Illegal instriction on MIPS
On Fri, 2016-03-18 at 10:59 +0100, Ole Streicher wrote: > Hi, > > what is the status of this bug? It is now in "pending" since almost > two > months, but nothing happened since then. > > This bug causes FTBFS for some important packages on the MIPS buildd, > which therefore cannot migrate to testing. I think this was fixed by "[mips*] Backport math emulation fix from 4.5." in 3.16.7-ckt25-1 and in 4.3.5-1. Aurelien, please can you confirm or correct this. Ben. -- Ben Hutchings Absolutum obsoletum. (If it works, it's out of date.) - Stafford Beer signature.asc Description: This is a digitally signed message part
linux_4.4.6-1_source.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 17 Mar 2016 01:25:23 + Source: linux Binary: linux-source-4.4 linux-support-4.4.0-1 linux-doc-4.4 linux-manual-4.4 linux-libc-dev linux-headers-4.4.0-1-all linux-headers-4.4.0-1-all-alpha kernel-image-4.4.0-1-alpha-generic-di nic-modules-4.4.0-1-alpha-generic-di nic-wireless-modules-4.4.0-1-alpha-generic-di nic-shared-modules-4.4.0-1-alpha-generic-di serial-modules-4.4.0-1-alpha-generic-di usb-serial-modules-4.4.0-1-alpha-generic-di ppp-modules-4.4.0-1-alpha-generic-di pata-modules-4.4.0-1-alpha-generic-di cdrom-core-modules-4.4.0-1-alpha-generic-di scsi-core-modules-4.4.0-1-alpha-generic-di scsi-modules-4.4.0-1-alpha-generic-di loop-modules-4.4.0-1-alpha-generic-di btrfs-modules-4.4.0-1-alpha-generic-di ext4-modules-4.4.0-1-alpha-generic-di isofs-modules-4.4.0-1-alpha-generic-di jfs-modules-4.4.0-1-alpha-generic-di xfs-modules-4.4.0-1-alpha-generic-di fat-modules-4.4.0-1-alpha-generic-di md-modules-4.4.0-1-alpha-generic-di multipath-modules-4.4.0-1-alpha-generic-di usb-modules-4.4.0-1-alpha-generic-di usb-storage-modules-4.4.0-1-alpha-generic-di fb-modules-4.4.0-1-alpha-generic-di input-modules-4.4.0-1-alpha-generic-di event-modules-4.4.0-1-alpha-generic-di mouse-modules-4.4.0-1-alpha-generic-di nic-pcmcia-modules-4.4.0-1-alpha-generic-di pcmcia-modules-4.4.0-1-alpha-generic-di nic-usb-modules-4.4.0-1-alpha-generic-di sata-modules-4.4.0-1-alpha-generic-di core-modules-4.4.0-1-alpha-generic-di crc-modules-4.4.0-1-alpha-generic-di crypto-modules-4.4.0-1-alpha-generic-di crypto-dm-modules-4.4.0-1-alpha-generic-di ata-modules-4.4.0-1-alpha-generic-di nbd-modules-4.4.0-1-alpha-generic-di squashfs-modules-4.4.0-1-alpha-generic-di virtio-modules-4.4.0-1-alpha-generic-di zlib-modules-4.4.0-1-alpha-generic-di fuse-modules-4.4.0-1-alpha-generic-di srm-modules-4.4.0-1-alpha-generic-di linux-headers-4.4.0-1-common linux-image-4.4.0-1-alpha-generic linux-headers-4.4.0-1-alpha-generic linux-image-4.4.0-1-alpha-smp linux-headers-4.4.0-1-alpha-smp linux-headers-4.4.0-1-all-amd64 kernel-image-4.4.0-1-amd64-di nic-modules-4.4.0-1-amd64-di nic-wireless-modules-4.4.0-1-amd64-di nic-shared-modules-4.4.0-1-amd64-di serial-modules-4.4.0-1-amd64-di usb-serial-modules-4.4.0-1-amd64-di ppp-modules-4.4.0-1-amd64-di pata-modules-4.4.0-1-amd64-di cdrom-core-modules-4.4.0-1-amd64-di firewire-core-modules-4.4.0-1-amd64-di scsi-core-modules-4.4.0-1-amd64-di scsi-modules-4.4.0-1-amd64-di loop-modules-4.4.0-1-amd64-di btrfs-modules-4.4.0-1-amd64-di ext4-modules-4.4.0-1-amd64-di isofs-modules-4.4.0-1-amd64-di jfs-modules-4.4.0-1-amd64-di ntfs-modules-4.4.0-1-amd64-di xfs-modules-4.4.0-1-amd64-di fat-modules-4.4.0-1-amd64-di md-modules-4.4.0-1-amd64-di multipath-modules-4.4.0-1-amd64-di usb-modules-4.4.0-1-amd64-di usb-storage-modules-4.4.0-1-amd64-di pcmcia-storage-modules-4.4.0-1-amd64-di fb-modules-4.4.0-1-amd64-di input-modules-4.4.0-1-amd64-di event-modules-4.4.0-1-amd64-di mouse-modules-4.4.0-1-amd64-di nic-pcmcia-modules-4.4.0-1-amd64-di pcmcia-modules-4.4.0-1-amd64-di nic-usb-modules-4.4.0-1-amd64-di sata-modules-4.4.0-1-amd64-di core-modules-4.4.0-1-amd64-di acpi-modules-4.4.0-1-amd64-di i2c-modules-4.4.0-1-amd64-di crc-modules-4.4.0-1-amd64-di crypto-modules-4.4.0-1-amd64-di crypto-dm-modules-4.4.0-1-amd64-di efi-modules-4.4.0-1-amd64-di ata-modules-4.4.0-1-amd64-di mmc-core-modules-4.4.0-1-amd64-di mmc-modules-4.4.0-1-amd64-di nbd-modules-4.4.0-1-amd64-di squashfs-modules-4.4.0-1-amd64-di speakup-modules-4.4.0-1-amd64-di virtio-modules-4.4.0-1-amd64-di uinput-modules-4.4.0-1-amd64-di sound-modules-4.4.0-1-amd64-di hyperv-modules-4.4.0-1-amd64-di udf-modules-4.4.0-1-amd64-di fuse-modules-4.4.0-1-amd64-di linux-image-4.4.0-1-amd64 linux-headers-4.4.0-1-amd64 linux-image-4.4.0-1-amd64-dbg xen-linux-system-4.4.0-1-amd64 linux-headers-4.4.0-1-common-rt linux-image-4.4.0-1-rt-amd64 linux-headers-4.4.0-1-rt-amd64 linux-image-4.4.0-1-rt-amd64-dbg linux-headers-4.4.0-1-all-arm64 kernel-image-4.4.0-1-arm64-di nic-modules-4.4.0-1-arm64-di nic-wireless-modules-4.4.0-1-arm64-di nic-shared-modules-4.4.0-1-arm64-di ppp-modules-4.4.0-1-arm64-di cdrom-core-modules-4.4.0-1-arm64-di scsi-core-modules-4.4.0-1-arm64-di scsi-modules-4.4.0-1-arm64-di loop-modules-4.4.0-1-arm64-di btrfs-modules-4.4.0-1-arm64-di ext4-modules-4.4.0-1-arm64-di isofs-modules-4.4.0-1-arm64-di jfs-modules-4.4.0-1-arm64-di xfs-modules-4.4.0-1-arm64-di fat-modules-4.4.0-1-arm64-di md-modules-4.4.0-1-arm64-di multipath-modules-4.4.0-1-arm64-di usb-modules-4.4.0-1-arm64-di usb-storage-modules-4.4.0-1-arm64-di input-modules-4.4.0-1-arm64-di event-modules-4.4.0-1-arm64-di nic-usb-modules-4.4.0-1-arm64-di sata-modules-4.4.0-1-arm64-di core-modules-4.4.0-1-arm64-di i2c-modules-4.4.0-1-arm64-di crc-modules-4.4.0-1-arm64-di crypto-modules-4.4.0-1-arm64-di crypto-dm-modules-4.4.0-1-arm64-di efi-modules-4.4.0-1-arm64-di ata-m
Bug#811368: Illegal instriction on MIPS
Hi, what is the status of this bug? It is now in "pending" since almost two months, but nothing happened since then. This bug causes FTBFS for some important packages on the MIPS buildd, which therefore cannot migrate to testing. Best regards Ole
Bug#813327: linux-image-3.16.0-4-amd64: cryptroot + VIA padlock fails with message from testmgr.c
Hi Ben, On Friday 05 February 2016 16:54:59 Ben Hutchings wrote: > On Fri, 2016-02-05 at 16:58 +0100, Carsten Wolff wrote: > > At least, it does not fix the error > > I'm seeing. The message stays the same, including the 32 byte it dumps. > > Then I'm out of ideas. I'll pass this to the upstream developers. here's an update on the issue: apparently, the latest wheezy-security kernel somehow broke padlock, too. I don't see any of the error messages I get with the jessie kernel, but after entering the key at the cryptsetup prompt, it responds with "No key available with this passphrase". I now have no kernel left to successfully boot with padlock/dm-crypt. One might think "hardware issue" now, but I can rule this out, it did work before and is still working in userspace (patched openssl package, apache/ openvpn using the openssl padlock engine). Regards Carsten signature.asc Description: This is a digitally signed message part.
Bug#818494: linux-image-4.5.0-rc7-amd64: backlight control doesn't work on ASUS UX305
Package: src:linux Version: 4.5~rc7-1~exp1 Severity: normal Dear Maintainer, Backlight control is broken using the keys Fn+F5/F6/F7 on this particular machine. Discussion on linux-kernel on https://bugzilla.kernel.org/show_bug.cgi?id=98931 A possible (temporary) patch is suggested at comment 33 https://bugzilla.kernel.org/attachment.cgi?id=195071&action=diff would it be possible to include this for now in the kernel build? -- Package-specific info: ** Version: Linux version 4.5.0-rc7-amd64 (debian-kernel@lists.debian.org) (gcc version 5.3.1 20160224 (Debian 5.3.1-10) ) #1 SMP Debian 4.5~rc7-1~exp1 (2016-03-07) ** Command line: BOOT_IMAGE=/boot/vmlinuz-4.5.0-rc7-amd64 root=/dev/mapper/hermes-root ro quiet ** Tainted: W (512) * Taint on warning. ** Kernel log: [ 46.019059] WARNING: CPU: 0 PID: 1550 at /build/linux-SGKJnh/linux-4.5~rc7/drivers/gpu/drm/i915/intel_uncore.c:599 hsw_unclaimed_reg_debug+0x65/0x80 [i915]() [ 46.019067] Unclaimed register detected after reading register 0x65f10 [ 46.019071] Modules linked in: ctr ccm bnep snd_hda_codec_hdmi snd_hda_codec_conexant snd_hda_codec_generic joydev arc4 intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass i2c_designware_platform i2c_designware_core crct10dif_pclmul crc32_pclmul ghash_clmulni_intel nls_utf8 nls_cp437 vfat fat iwlmvm mac80211 asus_nb_wmi asus_wmi sparse_keymap jitterentropy_rng iwlwifi cfg80211 sha256_ssse3 sha256_generic hmac drbg ansi_cprng aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper snd_hda_intel efi_pstore cryptd snd_hda_codec idma64 uvcvideo videobuf2_vmalloc snd_hda_core videobuf2_memops i915 virt_dma snd_hwdep videobuf2_v4l2 evdev snd_pcm pcspkr videobuf2_core serio_raw snd_timer efivars videodev snd soundcore media drm_kms_helper i2c_i801 drm mei_me shpchp sg mei [ 46.019192] i2c_algo_bit processor_thermal_device intel_lpss_pci intel_soc_dts_iosf wmi elan_i2c int3403_thermal hci_uart intel_lpss_acpi battery btqca intel_lpss video mfd_core int3402_thermal int340x_thermal_zone ac int3400_thermal tpm_crb acpi_thermal_rel acpi_als kfifo_buf industrialio tpm_tis acpi_pad button tpm processor btusb btrtl btbcm btintel bluetooth rfkill crc16 parport_pc ppdev lp parport efivarfs autofs4 xfs libcrc32c dm_mod sd_mod crc32c_intel ahci libahci xhci_pci libata xhci_hcd scsi_mod usbcore usb_common thermal i2c_hid hid fjes [ 46.019288] CPU: 0 PID: 1550 Comm: TVGuiSlave.64 Not tainted 4.5.0-rc7-amd64 #1 Debian 4.5~rc7-1~exp1 [ 46.019292] Hardware name: ASUSTeK COMPUTER INC. UX305UA/UX305UA, BIOS UX305UA.201 10/12/2015 [ 46.019298] 0086 fcd7774d 81301585 88008111b9a8 [ 46.019308] a06fa538 8107900d 881b 88008111ba00 [ 46.019316] 881b0080 0206 8107909c [ 46.019325] Call Trace: [ 46.019341] [] ? dump_stack+0x5c/0x77 [ 46.019354] [] ? warn_slowpath_common+0x7d/0xb0 [ 46.019362] [] ? warn_slowpath_fmt+0x5c/0x80 [ 46.019375] [] ? __hrtimer_init+0x90/0x90 [ 46.019456] [] ? hsw_unclaimed_reg_debug+0x65/0x80 [i915] [ 46.019530] [] ? gen9_read32+0x114/0x320 [i915] [ 46.019607] [] ? i915_audio_component_codec_wake_override+0x75/0xa0 [i915] [ 46.019628] [] ? snd_hdac_set_codec_wakeup+0x39/0x90 [snd_hda_core] [ 46.019640] [] ? azx_runtime_resume+0x177/0x1a0 [snd_hda_intel] [ 46.019651] [] ? pci_pm_runtime_resume+0x78/0xa0 [ 46.019662] [] ? __rpm_callback+0x2e/0x70 [ 46.019671] [] ? pci_restore_standard_config+0x40/0x40 [ 46.019680] [] ? rpm_callback+0x1f/0x70 [ 46.019688] [] ? pci_restore_standard_config+0x40/0x40 [ 46.019697] [] ? rpm_resume+0x48e/0x690 [ 46.019706] [] ? rpm_resume+0x2e0/0x690 [ 46.019716] [] ? __pm_runtime_resume+0x47/0x70 [ 46.019737] [] ? snd_hdac_regmap_read_raw+0x3d/0x90 [snd_hda_core] [ 46.019760] [] ? query_amp_caps+0x52/0x90 [snd_hda_codec] [ 46.019780] [] ? snd_hda_mixer_amp_volume_info+0x67/0xb0 [snd_hda_codec] [ 46.019798] [] ? snd_ctl_elem_info+0x46/0x130 [snd] [ 46.019813] [] ? snd_ctl_elem_info_user+0x6b/0xe0 [snd] [ 46.019831] [] ? snd_ctl_ioctl+0x620/0x6f0 [snd] [ 46.019844] [] ? snd_card_file_remove+0x7a/0xe0 [snd] [ 46.019857] [] ? do_vfs_ioctl+0x9d/0x5c0 [ 46.019868] [] ? set_close_on_exec+0x31/0x70 [ 46.019877] [] ? SyS_ioctl+0x74/0x80 [ 46.019890] [] ? system_call_fast_compare_end+0xc/0x67 [ 46.019897] ---[ end trace 1330e0491d7fa466 ]--- [ 813.499494] [drm] RC6 on [ 841.463587] [drm] RC6 on [ 853.470277] [drm] RC6 on [ 863.729947] systemd-sysv-generator[16589]: Overwriting existing symlink /run/systemd/generator.late/console-setup.service with real service. [ 863.729987] systemd-sysv-generator[16589]: Overwriting existing symlink /run/systemd/generator.late/keyboard-setup.service with real service. [ 864.036364] systemd-sysv-generator[16626]: Overwriting existing symlink /run/systemd/generator.late/keyboard-setup.se
