I had some more time to work on this problem.  After more research and
reading more information I discovered that IOMMU was not enabled on my
system.  To enable IOMMU I performed the following steps on my Ubuntu
Linux server:

sudo vi /etc/default/grub
Add “intel_iommu=on” to the GRUB_CMDLINE_LINUX variable
:wq
sudo update-grub
Reboot the system.

The results of these commands is adding intel_iommu=on as a boot
parameter to the grub Linux boot commands.

After performing those steps I was able to get much more information in the 
command:
bruzer@apocalypse:~$ dmesg | grep -e DMAR -e IOMMU
[    0.000000] ACPI: DMAR 00000000bc843878 000B8 (v01 INTEL      HSW  00000001 
INTL 00000001)
[    0.000000] Intel-IOMMU: enabled
[    0.020485] dmar: IOMMU 0: reg_base_addr fed90000 ver 1:0 cap c0000020660462 
ecap f0101a
[    0.020489] dmar: IOMMU 1: reg_base_addr fed91000 ver 1:0 cap d2008020660462 
ecap f010da
[    0.020556] IOAPIC id 2 under DRHD base  0xfed91000 IOMMU 1
[    0.394459] DMAR: No ATSR found
[    0.394479] IOMMU 0 0xfed90000: using Queued invalidation
[    0.394480] IOMMU 1 0xfed91000: using Queued invalidation
[    0.394481] IOMMU: Setting RMRR:
[    0.394489] IOMMU: Setting identity map for device 0000:00:02.0 [0xbf800000 
- 0xcf9fffff]
[    0.395687] IOMMU: Setting identity map for device 0000:00:1d.0 [0xbc6fa000 
- 0xbc706fff]
[    0.395708] IOMMU: Setting identity map for device 0000:00:1a.0 [0xbc6fa000 
- 0xbc706fff]
[    0.395726] IOMMU: Setting identity map for device 0000:00:14.0 [0xbc6fa000 
- 0xbc706fff]
[    0.395740] IOMMU: Prepare 0-16MiB unity mapping for LPC
[    0.395745] IOMMU: Setting identity map for device 0000:00:1f.0 [0x0 – 
0xffffff]

Now I am able to successfully run the commands that unbind and bind to
the pci-stub module.

# echo "10de 11c0" > /sys/bus/pci/drivers/pci-stub/new_id
# echo "0000:01:00.0" > /sys/bus/pci/devices/0000\:01\:00.0/driver/unbind
# echo "0000:01:00.0" > /sys/bus/pci/drivers/pci-stub/bind

These commands have no problems now that I am using the additional boot
parameter.  I believe we can close this bug report because there does
not seem to be a problem with the unbind command.

The PCI passthrough of the video card is still not working, but I do not
believe that is related to anything in this bug report.

-- 
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/1190120

Title:
  Unbind not working as expected

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  I am trying to unbind a PCI device I received a kernel Oops. I was following 
instructions described in this KVM document:
  http://www.linux-kvm.org/page/How_to_assign_devices_with_VT-d_in_KVM

  When I get to the unbind step:
  echo 0000:01:00.0 > /sys/bus/pci/devices/0000:01:00.0/driver/unbind

  In Raring I got a kernel Oops. Please note at this point I am not
  running the kvm guest, just trying to unbind the PCI device. I do have
  VT-d enabled in the bios and a processor that supports IOMMU. This
  problem is repeatable and appears to be isolated to the unbind
  command.

  However, in Saucy, I do not get a kernel oops, but executing unbind as
  root puts back into non-root user account. After going back as root, I
  am not able to perform the next step to bind the device.

  root@ubuntu:/home/ubuntu# echo 0000:01:00.0 > 
/sys/bus/pci/drivers/pci-stub/bind
  bash: echo: write error: No such device

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: linux-image-3.8.0-23-generic 3.8.0-23.34
  ProcVersionSignature: Ubuntu 3.8.0-23.34-generic 3.8.11
  Uname: Linux 3.8.0-23-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USER        PID ACCESS COMMAND
   /dev/snd/controlC2:  bruzer     2169 F.... pulseaudio
   /dev/snd/controlC1:  bruzer     2169 F.... pulseaudio
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Tue Jun 11 21:43:14 2013
  HibernationDevice: RESUME=UUID=4b6b5242-2b8c-46e6-9d91-3168bcee1249
  InstallationDate: Installed on 2013-06-07 (4 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  IwConfig:
   eth0      no wireless extensions.

   lo        no wireless extensions.

   virbr0    no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   0 inteldrmfb
   1 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-23-generic 
root=UUID=3ee858ac-5064-4c88-b187-2629fedf6f9c ro intel_iommu=on quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-23-generic N/A
   linux-backports-modules-3.8.0-23-generic  N/A
   linux-firmware                            1.106
  RfKill:

  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/03/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.20
  dmi.board.name: Z87M Extreme4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.20:bd05/03/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ87MExtreme4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  ---
  ApportVersion: 2.12.1-0ubuntu3
  Architecture: amd64
  CasperVersion: 1.336
  DistroRelease: Ubuntu 13.10
  IwConfig:
   eth0      no wireless extensions.

   lo        no wireless extensions.
  LiveMediaBuild: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130904)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  MarkForUpload: True
  Package: linux (not installed)
  ProcFB: 1 inteldrmfb
  ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper 
initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity
  ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon 
not responding.
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-4-generic N/A
   linux-backports-modules-3.11.0-4-generic  N/A
   linux-firmware                            1.113
  RfKill:

  Tags:  saucy
  Uname: Linux 3.11.0-4-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  dmi.bios.date: 07/05/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.60
  dmi.board.name: Z87M Extreme4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.60:bd07/05/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ87MExtreme4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1190120/+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