Feedback and update to the upstream bug:
"The ACPI MADT table includes an interrupt source overridden entry for ACPI SCI:
[236h 0566 1] Subtable Type : 02 <Interrupt Source Override>
[237h 0567 1] Length : 0A
[238h 0568 1] Bus : 00
[239h 0569 1] Source : 09
[23Ah 0570 4] Interrupt : 00000009
[23Eh 0574 2] Flags (decoded below) : 000D
Polarity : 1
Trigger Mode : 3
That means ACPI SCI interrupt(Interrupt : 00000009) works in
level(Trigger Mode : 3), high(Polarity : 1) mode.
For more information, please refer to Table 5-50 in ACPI spec 5.a.
And in DSDT table, we have _PRT method to define PCI interrupts, which
eventually goes to:
Name (PRSA, ResourceTemplate ()
{
IRQ (Level, ActiveLow, Shared, )
{3,4,5,7,9,10,11,12,14,15}
})
Name (PRSB, ResourceTemplate ()
{
IRQ (Level, ActiveLow, Shared, )
{3,4,5,7,9,10,11,12,14,15}
})
Name (PRSC, ResourceTemplate ()
{
IRQ (Level, ActiveLow, Shared, )
{3,4,5,7,9,10,11,12,14,15}
})
Name (PRSD, ResourceTemplate ()
{
IRQ (Level, ActiveLow, Shared, )
{3,4,5,7,9,10,11,12,14,15}
})
which means it's also possible to use IRQ9 for PCI interrupt, but works in
Level, ActiveLow mode. And this conflicts with ACPI SCI definition.
So it's an ACPI BIOS bug. There may several ways out here:
1) Change ACPI SCI IRQ working mode to level, low.
2) Exclude IRQ9 from Interrupt Link Device A-D
3) Use acpi_sci=low to override BIOS configuration.
4) revert the patch
Thanks!
Gerry"
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1440072
Title:
[Hyper-V] Legacy network adapter is not detected
Status in Linux:
Unknown
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Vivid:
In Progress
Bug description:
Issue description:
Attaching a Legacy network adapter to a VM will not be detected on the VM
side.
This is not the case with synthetic adapters, which are properly identified.
Steps to Reproduce:
1. Add a Legacy Network adapter to the VM
2. Boot the vm
3. Verify the identified network adapter, the legacy NIC is missing
Versions details:
Windows Server Host Edition: Microsoft Windows Server 2012 R2 Datacenter
build 9600 and Microsoft Windows Server 2008 R2 Standard SP 1 build 7601
Distribution name and release: Ubuntu Vivid Vervet
Kernel version: Linux ubuntu31 3.19.0-11-generic #11lp14233432v201504021617
SMP
Hyper-V side:
PS> Get-VMNetworkAdapter -VMName vivid1
Name IsManagementOs VMName SwitchName MacAddress Status
IPAddresses
---- -------------- ------ ---------- ---------- ------
-----------
Network Adapter False vivid1 external 00155D06332D {Ok}
{IP, fe80::215:5dff:fe06:332d}
Legacy Network Adapter False vivid1 external 00155D063336 {Ok} {}
On the VM Side:
root@ubuntu31:~# ls /sys/class/net/
eth0 lo
eth0 has the MAC of the Network Adapter, which is the synthetic
interface.
This has been verified with also 1 vCPU or with irqbalancer daemon disabled,
as that is a common requirements when using legacy adapters.
---
AlsaDevices:
total 0
crw-rw---- 1 root audio 116, 1 May 6 08:17 seq
crw-rw---- 1 root audio 116, 33 May 6 08:17 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.17.2-0ubuntu1
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
DistroRelease: Ubuntu 15.04
HibernationDevice: RESUME=/dev/mapper/ubuntu1504--vg-swap_1
InstallationDate: Installed on 2015-04-23 (12 days ago)
InstallationMedia: Ubuntu-Server 15.04 "Vivid Vervet" - Release amd64
(20150422)
IwConfig:
eth0 no wireless extensions.
lo no wireless extensions.
Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize
libusb: -99
MachineType: Microsoft Corporation Virtual Machine
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 hyperv_fb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-15-generic
root=/dev/mapper/hostname--vg-root ro crashkernel=384M-:128M console=tty0
console=ttyS1
ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
RelatedPackageVersions:
linux-restricted-modules-3.19.0-15-generic N/A
linux-backports-modules-3.19.0-15-generic N/A
linux-firmware 1.143
RfKill: Error: [Errno 2] No such file or directory
Tags: vivid
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
Uname: Linux 3.19.0-15-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
_MarkForUpload: True
dmi.bios.date: 05/23/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 090006
dmi.board.name: Virtual Machine
dmi.board.vendor: Microsoft Corporation
dmi.board.version: 7.0
dmi.chassis.asset.tag: 6473-7986-1993-5777-7899-0719-77
dmi.chassis.type: 3
dmi.chassis.vendor: Microsoft Corporation
dmi.chassis.version: 7.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr090006:bd05/23/2012:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0:
dmi.product.name: Virtual Machine
dmi.product.version: 7.0
dmi.sys.vendor: Microsoft Corporation
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1440072/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
