Your message dated Sun, 25 Apr 2021 08:49:25 +0200 with message-id <yiuq9zxm2gafr...@eldamar.lan> and subject line Re: Bug#748609: Info received (Bug#748609: Acknowledgement (linux-image-3.14-0.bpo.1-amd64: Hyper-V netvsc no networking)) has caused the Debian Bug report #748609, regarding linux-image-3.14-0.bpo.1-amd64: Hyper-V netvsc no networking 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.) -- 748609: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748609 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: src:linux Version: 3.14.4-1~bpo70+1 Severity: normal Tags: upstream Dear Maintainers, I've kept running some systems on wheezy as guests on Windows Server 2008 R2 Hyper-V hosts (german if it matters) to check out upstream changes and see if regressions are happening. I've been running both base 3.2 and the previous 3.13 backport kernel for wheezy without issues. However booting into this next (as of writing current) version makes the wheezy guest boot with error messages and the guest ends up without paravirtualized network interfaces. The other paravirtualized drivers like storage or graphics seem to be OK. Here is the messages that I was able to catch during boot phase: [ <timestamp> ] tsc: Fast TSC calibration failed [ <timestamp> ] hv_netvsc vmbus_0_9 (unregistered net_device): Unable to complete receive buffer initialization with NetVsp - status 2 [ <timestamp> ] hv_netvsc vmbus_0_9 (unregistered net_device): unable to connect to NetVSP - -22) [ <timestamp> ] hv_netvsc vmbus_0_9 (unregistered net_device): unable to add netwvsc device (red -22) [ <timestamp> ] hv_vmbus: probe failed for device vmbus_0_9 (-22) I'm currently uncertain whether this is a regression in upstream with host systems running this release of this Hypervisor. I could make a comparison on a 2012 R2 in the coming days which is the latest version I have access to. Should I notify upstream authors? -- Mathieu -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information sys_vendor: Microsoft Corporation product_name: Virtual Machine product_version: 7.0 chassis_vendor: Microsoft Corporation chassis_version: 7.0 bios_vendor: American Megatrends Inc. bios_version: 090004 board_vendor: Microsoft Corporation board_name: Virtual Machine board_version: 7.0 ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge (AGP disabled) [8086:7192] (rev 03) Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0 00:07.0 ISA bridge [0601]: Intel Corporation 82371AB/EB/MB PIIX4 ISA [8086:7110] (rev 01) Subsystem: Microsoft Corporation Device [1414:0000] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0 00:07.1 IDE interface [0101]: Intel Corporation 82371AB/EB/MB PIIX4 IDE [8086:7111] (rev 01) (prog-if 80 [Master]) Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0 Region 0: [virtual] Memory at 000001f0 (32-bit, non-prefetchable) [size=8] Region 1: [virtual] Memory at 000003f0 (type 3, non-prefetchable) [size=1] Region 2: [virtual] Memory at 00000170 (32-bit, non-prefetchable) [size=8] Region 3: [virtual] Memory at 00000370 (type 3, non-prefetchable) [size=1] Region 4: I/O ports at ffa0 [size=16] Kernel driver in use: ata_piix 00:07.3 Bridge [0680]: Intel Corporation 82371AB/EB/MB PIIX4 ACPI [8086:7113] (rev 02) Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Interrupt: pin A routed to IRQ 9 00:08.0 VGA compatible controller [0300]: Microsoft Corporation Hyper-V virtual VGA [1414:5353] (prog-if 00 [VGA controller]) Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV+ VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 11 Region 0: Memory at f8000000 (32-bit, non-prefetchable) [size=64M] Expansion ROM at <unassigned> [disabled] Kernel driver in use: hyperv_fb ** USB devices: not available -- System Information: Debian Release: 7.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.13-0.bpo.1-amd64 (SMP w/1 CPU core) Locale: LANG=de_CH.UTF-8, LC_CTYPE=de_CH.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages linux-image-3.14-0.bpo.1-amd64 depends on: ii debconf [debconf-2.0] 1.5.49 ii initramfs-tools [linux-initramfs-tool] 0.115~bpo70+1 ii kmod 9-3 ii linux-base 3.5 ii module-init-tools 9-3 Versions of packages linux-image-3.14-0.bpo.1-amd64 recommends: ii firmware-linux-free 3.2 Versions of packages linux-image-3.14-0.bpo.1-amd64 suggests: pn debian-kernel-handbook <none> ii grub-pc 1.99-27+deb7u2 pn linux-doc-3.14 <none> Versions of packages linux-image-3.14-0.bpo.1-amd64 is related to: pn firmware-atheros <none> pn firmware-bnx2 <none> pn firmware-bnx2x <none> pn firmware-brcm80211 <none> pn firmware-intelwimax <none> pn firmware-ipw2x00 <none> pn firmware-ivtv <none> pn firmware-iwlwifi <none> pn firmware-libertas <none> pn firmware-linux <none> pn firmware-linux-nonfree <none> pn firmware-myricom <none> pn firmware-netxen <none> pn firmware-qlogic <none> pn firmware-ralink <none> pn firmware-realtek <none> pn xen-hypervisor <none> -- debconf information: linux-image-3.14-0.bpo.1-amd64/postinst/depmod-error-initrd-3.14-0.bpo.1-amd64: false linux-image-3.14-0.bpo.1-amd64/prerm/removing-running-kernel-3.14-0.bpo.1-amd64: true
--- End Message ---
--- Begin Message ---Source: linux Source-Version: 3.15~rc5-1~exp1 Hi On Mon, May 19, 2014 at 08:13:21AM +0200, Mathieu Simon wrote: > Hi > > TL;DR: Bug is known upstream and fixed in anything after 3.15-rc1. And closing it for versions back then, as the bug was still open. Regards, Salvatore
--- End Message ---
