The tulip driver fails to initialize in a Linux VM running on Hyper-V. 
The following messages are logged in syslog when trying to load the tulip 
driver:

  tulip: Linux Tulip drivers version 1.1.15 (Feb 27, 2007)
  tulip: 0000:00:0a.0: PCI INT A: failed to register GSI
  tulip: Cannot enable tulip board #0, aborting
  tulip: probe of 0000:00:0a.0 failed with error -16

The tulip drivers initialization function tulip_init_one() calls 
pci_enable_device().  The call to pci_enable_device() eventually 
results in a call to alloc_isa_irq_from_domain(), which returns -EBUSY (-16)

The message "tulip: 0000:00:0a.0: PCI INT A: failed to register GSI" is
logged by acpi_pci_irq_enable().

The flow of calls to the error is returned is:

acpi_pci_irq_enable() - Logs the message "PCI INT A: failed to register GSI"
  acpi_register_gsi()
    __acpi_register_gsi() is afunction pointer -> acpi_register_gsi_ioapic()
    acpi_register_gsi_ioapic()
      mp_map_gsi_to_irq()
        mp_map_ppin_to_irq()
          alloc_isa_irq_from_domain()
            Returning -EBUSY when mp_check_pin_attr() returns false.

            mp_check_pin_attr()
              data->trigger  = 1
              data->polarity = 0
              info->ioapic_trigger  = 1
              info->ioapic_polarity = 1
        mp_check_pin_attr() returns false because the two polarity values do 
not match.

acpi_register_gsi_ioapic() is setting trigger and polarity to:
    trigger = 1
    polarity = 1
mp_check_pin_attr() is calling irq_get_chip_data(irq) which is returning a 
mp_chip_data structure with
    trigger  = 1
    polarity = 0
Since the two polarity values do not match, mp_check_pin_attr() returns false.

Broken in 3.19.0 kernel
Works in 3.17 kernel.

Using commits to arch/x86/kernel/acpi/boot.c as reference, the commit where the 
issue appears is
    cd68f6bd53cf89d1d5ed889b8aaf65e9c3574a079
    x86, irq, acpi: Git rid of special handling of GSI for ACPI SCI

-- 
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 package in Ubuntu:
  Confirmed

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/ubuntu/+source/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

Reply via email to