← Back to team overview

kernel-packages team mailing list archive

[Bug 1190120] Re: Unbind not working as expected

 

Christopher,

I downloaded and installed the mainline kerel v3.12 and tried the
sequence of commands leading to the unbind command.

This time the system hung, no kernel oops but the system was
unresponsive/locked up.  I was unable to use any keystroke to gain
control of my system Ctrl+c failed as did trying to change to the text
display.  This forced me to remove the power from the system. I have
done this twice so I could record my steps, same repeatable result.

bruzer@apocalypse:~$ uname -a
Linux apocalypse 3.12.0-031200-generic #201311071835 SMP Thu Nov 7 23:36:07 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
bruzer@apocalypse:~$ sudo su
[sudo] password for bruzer: 
root@apocalypse:/home/bruzer# dmesg | grep -e DMAR -e IOMMU
[    0.000000] ACPI: DMAR 00000000bc843878 000B8 (v01 INTEL      HSW  00000001 INTL 00000001)
[    0.020392] dmar: IOMMU 0: reg_base_addr fed90000 ver 1:0 cap c0000020660462 ecap f0101a
[    0.020396] dmar: IOMMU 1: reg_base_addr fed91000 ver 1:0 cap d2008020660462 ecap f010da
[    0.020466] IOAPIC id 2 under DRHD base  0xfed91000 IOMMU 1
root@apocalypse:/home/bruzer# modprobe pci_stub
root@apocalypse:/home/bruzer# lspci -n
...
01:00.0 0300: 10de:11c0 (rev a1)
01:00.1 0403: 10de:0e0b (rev a1)
root@apocalypse:/home/bruzer# echo "10de 11c0" > /sys/bus/pci/drivers/pci-stub/new_id
root@apocalypse:/home/bruzer# echo 0000:01:00.0 > /sys/bus/pci/devices/0000\:01\:00.0/driver/unbind

I believe the v3.12 behavior of this problem is much more troublesome
than a kernel oops or kicking out of superuser.

Was there anything specific in the v3.12 kernel that you thought would
fix this problem?  Or do I have to keep  trying all versions of the
kernel until the problem is fixed?

-- 
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:
  Incomplete

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