Bug#867358: mips/mipsel: mips-linux-gnu-gccgo-7: waitid: bad address
On Mon, 2017-07-17 at 15:24 +0100, James Cowgill wrote: > Hi, > > On 16/07/17 23:31, Ben Hutchings wrote: > > Control: tag -1 upstream patch > > > > On Sun, 2017-07-16 at 23:21 +0100, Ben Hutchings wrote: > > > On Thu, 2017-07-06 at 13:10 +0300, Adrian Bunk wrote: [...] > > > > James Cowgill told me that this is actually a kernel bug: > > > > https://www.linux-mips.org/archives/linux-mips/2017-03/msg00580.html > > > > > > That's now a 404, strangely. Did you mean "[PATCH 0/2] Fix indirect > > > syscall handler for syscalls with > 4 args"? > > Hmm, I may have made a typo with that link. Here's the real one: > https://www.linux-mips.org/archives/linux-mips/2017-03/msg00575.html > > > James - assuming I guessed correctly above, why is it that the second > > patch "MIPS: Remove pt_regs adjustments in indirect syscall handler" > > hasn't been applied? Was this fixed some other way upstream? > > I've just tried with v4.13-rc1 and the bug is still not fixed there. My > guess is that the first patch is more obviously correct than the second > one so was applied first. I have never received any feedback on these > patches so I don't actually know why only one of them was applied. I'm certainly not able to review this patch, so I won't apply it until it's either accepted upstream or reviewed by Aurelien or another MIPS porter. 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#868771: linux: Enable building the dummy_hcd module
Processing control commands: > tag -1 moreinfo Bug #868771 [linux] linux: Enable building the dummy_hcd module Added tag(s) moreinfo. -- 868771: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868771 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#868771: linux: Enable building the dummy_hcd module
Control: tag -1 moreinfo On Tue, 2017-07-18 at 13:26 +0200, Domenico Andreoli wrote: > Package: linux > Version: 4.11.11-1 > Severity: wishlist > > Hi, > > please enable CONFIG_USB_DUMMY_HCD so to build dummy_hcd.ko module. > > It would really help me "[...] in some stages of creating a driver to > embed in a Linux device, since it lets you debug several parts of the > gadget driver without its hardware or drivers being involved." If you're doing kernel development, you can enable this in the kernel you build. Am I missing something? 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: reassign 869090 to src:linux, affects 869090, affects 869090
Processing commands for cont...@bugs.debian.org: > reassign 869090 src:linux 4.11.11-1 Bug #869090 [gcc-6] gcc-6: Address sanitizer: Shadow memory range interleaves Bug reassigned from package 'gcc-6' to 'src:linux'. No longer marked as found in versions gcc-6/6.4.0-1. Ignoring request to alter fixed versions of bug #869090 to the same values previously set Bug #869090 [src:linux] gcc-6: Address sanitizer: Shadow memory range interleaves Marked as found in versions linux/4.11.11-1. > affects 869090 gcc-6 Bug #869090 [src:linux] gcc-6: Address sanitizer: Shadow memory range interleaves Added indication that 869090 affects gcc-6 > affects 869090 gcc-7 Bug #869090 [src:linux] gcc-6: Address sanitizer: Shadow memory range interleaves Added indication that 869090 affects gcc-7 > thanks Stopping processing here. Please contact me if you need assistance. -- 869090: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869090 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#858125: marked as done (TX watchdog fires on e1000e interface with flow control enabled)
Your message dated Sat, 12 Aug 2017 21:37:51 +0100 with message-id <1502570271.3944.3.ca...@decadent.org.uk> and subject line Re: Bug#858125: e1000: ethernet interface hangs occasionally, kernel reports hang has caused the Debian Bug report #858125, regarding TX watchdog fires on e1000e interface with flow control enabled 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.) -- 858125: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858125 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Version: 3.16.39-1 Severity: critical File: e1000 Justification: breaks unrelated software Dear Maintainer, I have had intermittent hangs of my two built-in ethernet interfaces since switching from 100Mb ethernet to 1Gb ethernet. During the hangs, no traffic passes through the port. This has been happening since August 2016 and the hangs are 20-60 seconds. Sometimes the hangs happen every half hour, other times I can go days with no hang, but the hangs are becoming more frequent. Sometimes the hangs report this kernel message: kernel: [96085.866650] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx but other times there is more detail: Mar 18 11:20:13 momjian kernel: [ 2537.679019] [ cut here ] Mar 18 11:20:13 momjian kernel: [ 2537.679031] WARNING: CPU: 0 PID: 0 at /build/linux-GU1w8g/linux-3.16.39/net/sched/sch_generic.c:264 dev_watchdog+0x236/0x240() Mar 18 11:20:13 momjian kernel: [ 2537.679034] NETDEV WATCHDOG: eth1 (e1000e): transmit queue 0 timed out Mar 18 11:20:13 momjian kernel: [ 2537.679035] Modules linked in: cpufreq_stats cpufreq_conservative cpufreq_powersave cpufreq_userspace cfg80211 rfkill binfmt_misc nfsd auth_rpcgss oid_registry nfs_acl nfs lockd fscache sunrpc pl2303 usbserial iTCO_wdt iTCO_vendor_support nvidia(PO) intel_powerclamp coretemp pcspkr kvm_intel i2c_i801 kvm snd_hda_codec_realtek drm snd_hda_codec_generic snd_hda_intel snd_hda_controller snd_hda_codec evdev serio_raw i2c_core snd_hwdep lpc_ich snd_pcm mfd_core snd_timer button i7core_edac snd ioatdma soundcore edac_core shpchp acpi_cpufreq dca processor thermal_sys loop firewire_sbp2 fuse parport_pc ppdev lp parport autofs4 ext4 crc16 mbcache jbd2 hid_generic usbhid usb_storage hid sg sr_mod cdrom sd_mod crc_t10dif crct10dif_generic crct10dif_common ata_generic crc32c_intel ata_piix ehci_pci uhci_hcd psmouse libata ehci_hcd firewire_ohci e1000e usbcore ptp firewire_core scsi_mod pps_core crc_itu_t usb_common Mar 18 11:20:13 momjian kernel: [ 2537.679107] CPU: 0 PID: 0 Comm: swapper/0 Tainted: P O 3.16.0-4-amd64 #1 Debian 3.16.39-1 Mar 18 11:20:13 momjian kernel: [ 2537.679109] Hardware name: Supermicro X8DA3/X8DA3, BIOS 2.1a04/06/2012 Mar 18 11:20:13 momjian kernel: [ 2537.679111] 81514c11 88033fc03e28 0009 Mar 18 11:20:13 momjian kernel: [ 2537.679114] 81068867 88033fc03e78 0001 Mar 18 11:20:13 momjian kernel: [ 2537.679117] 880330d2 810688cc 81777e40 Mar 18 11:20:13 momjian kernel: [ 2537.679121] Call Trace: Mar 18 11:20:13 momjian kernel: [ 2537.679123] [] ? dump_stack+0x5d/0x78 Mar 18 11:20:13 momjian kernel: [ 2537.679133] [] ? warn_slowpath_common+0x77/0x90 Mar 18 11:20:13 momjian kernel: [ 2537.679137] [] ? warn_slowpath_fmt+0x4c/0x50 Mar 18 11:20:13 momjian kernel: [ 2537.679141] [] ? mod_timer+0xf5/0x200 Mar 18 11:20:13 momjian kernel: [ 2537.679148] [] ? dev_watchdog+0x236/0x240 Mar 18 11:20:13 momjian kernel: [ 2537.679152] [] ? dev_graft_qdisc+0x70/0x70 Mar 18 11:20:13 momjian kernel: [ 2537.679155] [] ? call_timer_fn+0x31/0x140 Mar 18 11:20:13 momjian kernel: [ 2537.679158] [] ? dev_graft_qdisc+0x70/0x70 Mar 18 11:20:13 momjian kernel: [ 2537.679162] [] ? run_timer_softirq+0x1e9/0x2f0 Mar 18 11:20:13 momjian kernel: [ 2537.679165] [] ? __do_softirq+0xf1/0x2d0 Mar 18 11:20:13 momjian kernel: [ 2537.679168] [] ? irq_exit+0x95/0xa0 Mar 18 11:20:13 momjian kernel: [ 2537.679172] [] ? smp_apic_timer_interrupt+0x40/0x50 Mar 18 11:20:13 momjian kernel: [ 2537.679177] [] ? apic_timer_interrupt+0x6d/0x80 Mar 18 11:20:13 momjian kernel: [ 2537.679178] [] ? get_next_timer_interrupt+0x1d6/0x250 Mar 18 11:20:13 momjian kernel: [ 2537.679185] [] ?
Bug#871351: marked as done (linux: FTBFS: usbip.c:178:4: error: this statement may fall through [-Werror=implicit-fallthrough=])
Your message dated Sat, 12 Aug 2017 21:40:21 +0100
with message-id <1502570421.3944.4.ca...@decadent.org.uk>
and subject line Re: Bug#871351: linux: FTBFS: usbip.c:178:4: error: this
statement may fall through [-Werror=implicit-fallthrough=]
has caused the Debian Bug report #871351,
regarding linux: FTBFS: usbip.c:178:4: error: this statement may fall through
[-Werror=implicit-fallthrough=]
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.)
--
871351: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871351
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: linux
Version: 4.11.11-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170807 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
> make[8]: Entering directory
> '/<>/debian/build/build-tools/tools/usb/usbip/src'
> CC usbip.o
> usbip.c: In function ‘main’:
> usbip.c:178:4: error: this statement may fall through
> [-Werror=implicit-fallthrough=]
> printf("usbip: invalid option\n");
> ^
> usbip.c:179:3: note: here
>default:
>^~~
> cc1: all warnings being treated as errors
> Makefile:418: recipe for target 'usbip.o' failed
> make[8]: *** [usbip.o] Error 1
The full build log is available from:
http://aws-logs.debian.net/2017/08/07/linux_4.11.11-1_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Version: 4.12.2-1~exp1
Fixed upstream in 4.12-rc1.
Ben.
--
Ben Hutchings
Never put off till tomorrow what you can avoid all together.
signature.asc
Description: This is a digitally signed message part
--- End Message ---
Bug#870185: FATAL: kernel 4.11.0-0.bpo.1-marvell does not boot on QNAP TS-219P II
On Mon, 2017-07-31 at 18:10 +0200, Robert Schlabbach wrote: > Ok, I figured it out. I noticed that the 4.11 kernel has a more > "generous" memory layout than the 4.9 one: > > kernel 4.9: > > [0.00] Memory: 504492K/524288K available (3777K kernel code, 371K > rwdata, 1128K rodata, 296K init, 247K bss, 19796K reserved, 0K cma-reserved, > 0K highmem) > > kernel 4.11: > > [0.00] Memory: 502648K/524288K available (4096K kernel code, 398K > rwdata, 1132K rodata, 1024K init, 248K bss, 21640K reserved, 0K cma-reserved, > 0K highmem) > > So I suspected that the 4.11 kernel might be overwriting/corrupting > the initrd.img provided in memory before it gets to unpack it, and > changed the memory location from 0xa0 to 0xc0: [...] > Voila! It's finally booting! > > So, was the 4.11 kernel compiled/linked with a wrong alignment > padding setting? Or should the bootloader environment be changed to > permanently use the higher address for passing initrd.img to the > kernel? Should this be assigned to flash-kernel? 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: reassign 860534 to src:linux
Processing commands for cont...@bugs.debian.org: > reassign 860534 src:linux 4.9.30-2+deb9u2 Bug #860534 [firmware-amd-graphics] firmware-amd-graphics: Random system freezes with AMD GPU Bug reassigned from package 'firmware-amd-graphics' to 'src:linux'. No longer marked as found in versions firmware-nonfree/20161130-3 and firmware-nonfree/20161130-2. Ignoring request to alter fixed versions of bug #860534 to the same values previously set Bug #860534 [src:linux] firmware-amd-graphics: Random system freezes with AMD GPU Marked as found in versions linux/4.9.30-2+deb9u2. > thanks Stopping processing here. Please contact me if you need assistance. -- 860534: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860534 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassign 869824 to src:linux, forcibly merging 869511 869824
Processing commands for cont...@bugs.debian.org: > reassign 869824 src:linux Bug #869824 [linux-headers-amd64] missing package Bug reassigned from package 'linux-headers-amd64' to 'src:linux'. No longer marked as found in versions 4.11.0-2-amd64. Ignoring request to alter fixed versions of bug #869824 to the same values previously set > forcemerge 869511 869824 Bug #869511 [src:linux] linux: binNMU-unsafe dependency on linux-headers-*-common Bug #869670 [src:linux] Depends: linux-headers-4.11.0-2-common ... but it is not going to be installed Bug #870132 [src:linux] linux-headers-amd64 broken, can't install Bug #870298 [src:linux] 4.11.0-2-amd64 headers cannot be installed Bug #869670 [src:linux] Depends: linux-headers-4.11.0-2-common ... but it is not going to be installed The source linux and version 4.11.11-1+b1 do not appear to match any binary packages Marked as found in versions linux/4.11.11-1+b1. Marked as found in versions linux/4.11.11-1+b1. Marked as found in versions linux/4.11.11-1+b1. Ignoring request to alter found versions of bug #870298 to the same values previously set Bug #869824 [src:linux] missing package Severity set to 'grave' from 'normal' 866389 was blocked by: 866317 869578 867210 869383 869583 866315 867213 869579 865224 827640 865477 869670 865033 826502 869433 869576 826473 865893 826489 867046 865045 809352 869511 865020 866978 866934 869357 869504 870298 867984 826505 865888 866944 865034 869418 867514 826497 865380 865898 869580 869602 865482 826471 869139 870132 869436 866389 was not blocking any bugs. Added blocking bug(s) of 866389: 869824 865614 was blocked by: 869511 869670 870132 867257 870298 865614 was not blocking any bugs. Added blocking bug(s) of 865614: 869824 The source linux and version 4.11.11-1+b1 do not appear to match any binary packages Marked as found in versions linux/4.11.11-1+b1 and linux/4.11.11-1. Added tag(s) newcomer and pending. Bug #870132 [src:linux] linux-headers-amd64 broken, can't install Bug #870298 [src:linux] 4.11.0-2-amd64 headers cannot be installed Merged 869511 869670 869824 870132 870298 > thanks Stopping processing here. Please contact me if you need assistance. -- 865614: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865614 866389: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866389 869511: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869511 869670: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869670 869824: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869824 870132: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870132 870298: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870298 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
☢yay some interesting facts
Hello, I've found that interesting article with a whole lot of surprising reality, simply take a look http://songynghia.com/principal.php?0e0f Thanks for your consideration, Jonas Meurer
Bug#864529: firmware-amd-graphics: missing firmware for AMD Radeon RX 560,570,580
I am confirming this affects me as well, installing the kernel from stretch-backports, using an AMD RX 580. The workaround is to clone https://git.kernel.org/pub/scm/linux/kernel/ git/firmware/linux-firmware.git/, and copy the missing files to their proper place using rsync -a -v --ignore-existing source /lib/firmware/amdgpu/. After that, the system boots fine. I am hoping the appropriate firmware files will be added soon in backports.
Bug#870523: 4.9.30-2+deb9u3 broken too (Was: [...] linux-image-4.11.0-1-amd64 [...] broken [...])
On Sat, Aug 05, 2017 at 08:53:24PM +0200, Bastian Blank wrote: > On Sat, Aug 05, 2017 at 08:22:36PM +0200, Gilles Sadowski wrote: > > I've just upgraded another computer from "jessie" to "stretch"; this > > installed 4.11.0-1 by default, and on that machine the problem immediately > > No, it does not and never will. 4.11.0-1 is testing and unstable, aka > Buster and Sid. > > > $ uname -a > > Linux night 4.9.0-3-amd64 #1 SMP Debian 4.9.30-2+deb9u2 (2017-06-26) x86_64 > > GNU/Linux > > That one seems to work, for now... > > This is the kernel from Stretch, so you are good. It doesn't look like it, unfortunately; below is the contents of "kern.log": ---CUT--- Aug 7 11:18:36 eccen kernel: Bluetooth: Core ver 2.22 Aug 7 11:18:36 eccen kernel: NET: Registered protocol family 31 Aug 7 11:18:36 eccen kernel: Bluetooth: HCI device and connection manager initialized Aug 7 11:18:36 eccen kernel: Bluetooth: HCI socket layer initialized Aug 7 11:18:36 eccen kernel: Bluetooth: L2CAP socket layer initialized Aug 7 11:18:36 eccen kernel: Bluetooth: SCO socket layer initialized Aug 7 11:18:36 eccen kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3 Aug 7 11:18:36 eccen kernel: Bluetooth: BNEP filters: protocol multicast Aug 7 11:18:36 eccen kernel: Bluetooth: BNEP socket layer initialized Aug 7 11:18:40 eccen kernel: NET: Registered protocol family 4 Aug 7 11:18:40 eccen kernel: NET: Registered protocol family 3 Aug 7 11:18:40 eccen kernel: NET: Registered protocol family 5 Aug 7 11:19:10 eccen kernel: fuse init (API version 7.26) Aug 7 18:03:37 eccen kernel: NET: Registered protocol family 38 Aug 7 18:03:41 eccen kernel: EXT4-fs (dm-13): recovery complete Aug 7 18:03:41 eccen kernel: EXT4-fs (dm-13): mounted filesystem with ordered data mode. Opts: (null) Aug 9 14:07:34 eccen kernel: perf: interrupt took too long (2506 > 2500), lowering kernel.perf_event_max_sample_rate to 79750 Aug 10 04:29:39 eccen kernel: perf: interrupt took too long (3141 > 3132), lowering kernel.perf_event_max_sample_rate to 63500 Aug 12 07:39:53 eccen kernel: INFO: task kswapd0:75 blocked for more than 120 seconds. Aug 12 07:39:53 eccen kernel: Not tainted 4.9.0-3-amd64 #1 Debian 4.9.30-2+deb9u3 Aug 12 07:39:53 eccen kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Aug 12 07:39:53 eccen kernel: kswapd0 D075 2 0x Aug 12 07:39:53 eccen kernel: 9635d3f92000 9635d48d1100 9635dec98240 Aug 12 07:39:53 eccen kernel: 9635d525f040 b8f3410d3b58 b8c015d3 96358b2e08a0 Aug 12 07:39:53 eccen kernel: 0246 9635dec98240 96358b2e0888 9635d48d1100 Aug 12 07:39:53 eccen kernel: Call Trace: Aug 12 07:39:53 eccen kernel: [] ? __schedule+0x233/0x6d0 Aug 12 07:39:53 eccen kernel: [] ? schedule+0x32/0x80 Aug 12 07:39:53 eccen kernel: [] ? jbd2_log_wait_commit+0x93/0x110 [jbd2] Aug 12 07:39:53 eccen kernel: [] ? prepare_to_wait_event+0xf0/0xf0 Aug 12 07:39:53 eccen kernel: [] ? ext4_evict_inode+0x2c1/0x460 [ext4] Aug 12 07:39:53 eccen kernel: [] ? evict+0xb6/0x180 Aug 12 07:39:53 eccen kernel: [] ? dispose_list+0x36/0x50 Aug 12 07:39:53 eccen kernel: [] ? prune_icache_sb+0x52/0x70 Aug 12 07:39:53 eccen kernel: [] ? super_cache_scan+0x13b/0x190 Aug 12 07:39:53 eccen kernel: [] ? shrink_slab.part.38+0x210/0x430 Aug 12 07:39:53 eccen kernel: [] ? shrink_node+0x10a/0x320 Aug 12 07:39:53 eccen kernel: [] ? kswapd+0x2e8/0x6b0 Aug 12 07:39:53 eccen kernel: [] ? mem_cgroup_shrink_node+0x170/0x170 Aug 12 07:39:53 eccen kernel: [] ? kthread+0xd7/0xf0 Aug 12 07:39:53 eccen kernel: [] ? kthread_park+0x60/0x60 Aug 12 07:39:53 eccen kernel: [] ? ret_from_fork+0x25/0x30 Aug 12 07:39:53 eccen kernel: INFO: task cinnamon:4112 blocked for more than 120 seconds. Aug 12 07:39:53 eccen kernel: Not tainted 4.9.0-3-amd64 #1 Debian 4.9.30-2+deb9u3 Aug 12 07:39:53 eccen kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Aug 12 07:39:53 eccen kernel: cinnamonD0 4112 4099 0x Aug 12 07:39:53 eccen kernel: 9635d3f92400 9635d183d140 9635dec18240 Aug 12 07:39:53 eccen kernel: b920e500 b8f34322b540 b8c015d3 96358b2e08a0 Aug 12 07:39:53 eccen kernel: 0246 9635dec18240 96358b2e0888 9635d183d140 Aug 12 07:39:53 eccen kernel: Call Trace: Aug 12 07:39:53 eccen kernel: [] ? __schedule+0x233/0x6d0 Aug 12 07:39:53 eccen kernel: [] ? schedule+0x32/0x80 Aug 12 07:39:53 eccen kernel: [] ? jbd2_log_wait_commit+0x93/0x110 [jbd2] Aug 12 07:39:53 eccen kernel: [] ? prepare_to_wait_event+0xf0/0xf0 Aug 12 07:39:53 eccen kernel: [] ? ext4_evict_inode+0x2c1/0x460 [ext4] Aug 12 07:39:53 eccen kernel: [] ? evict+0xb6/0x180 Aug 12 07:39:53 eccen kernel: [] ? dispose_list+0x36/0x50 Aug 12 07:39:53 eccen kernel: [] ? prune_icache_sb+0x52/0x70 Aug 12 07:39:53 eccen kernel: [] ?
Bug#870298: 4.11.0-2-amd64 headers cannot be installed
Package: src:linux Version: 4.11.11-1+b1 Followup-For: Bug #870298 Dear Maintainer, I have the exact same issue. Would be realy nice if there where recent header files. Regards Matthias -- Package-specific info: ** Version: Linux version 4.11.0-2-amd64 (debian-kernel@lists.debian.org) (gcc version 6.4.0 20170704 (Debian 6.4.0-1) ) #1 SMP Debian 4.11.11-1 (2017-07-22) ** Command line: BOOT_IMAGE=/vmlinuz-4.11.0-2-amd64 root=/dev/mapper/orinoco-root ro quiet ** Not tainted ** Kernel log: Unable to read kernel log; any relevant messages should be attached ** Model information sys_vendor: ASUSTeK COMPUTER INC. product_name: V-P8H77E product_version: System Version chassis_vendor: Chassis Manufacture chassis_version: Chassis Version bios_vendor: American Megatrends Inc. bios_version: 0404 board_vendor: ASUSTeK COMPUTER INC. board_name: V-P8H77E board_version: Rev X.0x ** Loaded modules: fuse ebtable_filter ebtables twofish_generic twofish_avx_x86_64 twofish_x86_64_3way twofish_x86_64 twofish_common serpent_avx_x86_64 serpent_sse2_x86_64 serpent_generic blowfish_generic blowfish_x86_64 blowfish_common cast5_avx_x86_64 cast5_generic cast_common ctr des_generic cbc algif_skcipher camellia_generic camellia_aesni_avx_x86_64 ablk_helper camellia_x86_64 xts lrw gf128mul xcbc sha512_ssse3 sha512_generic algif_hash af_alg xfrm_user xfrm4_tunnel tunnel4 ipcomp xfrm_ipcomp esp4 ah4 af_key xfrm_algo arc4 md4 nls_utf8 cifs ccm dns_resolver fscache tun binfmt_misc ext4 crc16 jbd2 fscrypto ecb mbcache joydev intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic iTCO_wdt iTCO_vendor_support crct10dif_pclmul crc32_pclmul ghash_clmulni_intel eeepc_wmi asus_wmi snd_hda_intel sparse_keymap snd_hda_codec snd_hda_core rfkill evdev snd_hwdep nf_conntrack_ipv6 nf_defrag_ipv6 snd_pcm ip6table_filter intel_cstate ip6_tables snd_timer snd soundcore i915 intel_uncore xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 drm_kms_helper drm tpm_infineon intel_rapl_perf sg shpchp mei_me mei ie31200_edac edac_core lpc_ich mfd_core battery video serio_raw pcspkr intel_smartconnect wmi xt_conntrack nf_conntrack button iptable_filter sch_fq_codel loop parport_pc ppdev sunrpc lp parport ip_tables x_tables autofs4 xfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor hid_logitech_hidpp hid_logitech_dj raid6_pq libcrc32c crc32c_generic raid0 multipath linear hid_generic usbhid hid uas usb_storage dm_mod raid1 md_mod sr_mod cdrom sd_mod crc32c_intel aesni_intel aes_x86_64 crypto_simd cryptd glue_helper psmouse ahci i2c_i801 libahci libata ehci_pci xhci_pci igb xhci_hcd ehci_hcd i2c_algo_bit dca r8169 scsi_mod mii ptp pps_core usbcore usb_common fan thermal ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor DRAM Controller [8086:0150] (rev 09) Subsystem: ASUSTeK Computer Inc. P8 series motherboard [1043:84ca] 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: ivb_uncore Kernel modules: ie31200_edac 00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor PCI Express Root Port [8086:0151] (rev 09) (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 Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0162] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. P8 series motherboard [1043:84ca] 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: i915 Kernel modules: i915 00:14.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller [8086:1e31] (rev 04) (prog-if 30 [XHCI]) Subsystem: ASUSTeK Computer Inc. P8 series motherboard [1043:84ca] 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 7 Series/C216 Chipset Family MEI Controller #1 [8086:1e3a] (rev 04) Subsystem: ASUSTeK Computer Inc. P8 series motherboard [1043:84ca]
