1 |
On Thursday, February 18, 2016 12:05:14 PM Peter Humphrey wrote: |
2 |
> On Thursday 18 February 2016 11:23:42 I wrote: |
3 |
> > On Thursday 18 February 2016 11:51:19 J. Roeleveld wrote: |
4 |
> > > On Thursday, February 18, 2016 10:06:25 AM Peter Humphrey wrote: |
5 |
> > --->8 |
6 |
> > |
7 |
> > > > I still can't shake the idea that I don't have my kernel set up right. |
8 |
> > > > Do |
9 |
> > > > I |
10 |
> > > > need anything particular in control groups, or name spaces, or |
11 |
> > > > anything? |
12 |
> > > |
13 |
> > > About the kernel: I don't have anything special. |
14 |
> > > |
15 |
> > > USE-flags: |
16 |
> > > |
17 |
> > > [I] app-emulation/virtualbox |
18 |
> > > |
19 |
> > > Installed versions: 4.3.32{tbz2}(03:46:09 PM 11/25/2015)(additions |
20 |
> > > |
21 |
> > > alsa extensions java opengl pam pulseaudio qt4 sdk udev -doc -headless |
22 |
> > > -libressl - python -vboxwebsrv -vnc ELIBC="-FreeBSD" |
23 |
> > > PYTHON_TARGETS="python2_7") |
24 |
> > |
25 |
> > My USE flags: |
26 |
> > Installed versions: 4.3.32{tbz2}(10:25:28 18/02/16)(additions alsa |
27 |
> > |
28 |
> > extensions opengl pam qt4 sdk udev -doc -headless -java -libressl |
29 |
> > -pulseaudio -python -vboxwebsrv -vnc ELIBC="-FreeBSD" |
30 |
> > PYTHON_TARGETS="python2_7") |
31 |
> > |
32 |
> > I don't have pulseaudio here, but do I need java for virtualbox? |
33 |
> > |
34 |
> > > What does " dmesg " have to say? |
35 |
> > > |
36 |
> > > For me: |
37 |
> > > % dmesg | grep -i vbox |
38 |
> > > [ 165.950507] vboxdrv: Found 8 processor cores. |
39 |
> > > [ 165.950787] vboxdrv: fAsync=0 offMin=0x1fe offMax=0xa4f9 |
40 |
> > > [ 165.950828] vboxdrv: TSC mode is 'synchronous', kernel timer mode is |
41 |
> > > 'normal'. |
42 |
> > > [ 165.950829] vboxdrv: Successfully loaded version 4.3.32 (interface |
43 |
> > > 0x001a000b). |
44 |
> > > [ 165.978641] vboxpci: pci-stub module not available, cannot detach PCI |
45 |
> > > devices |
46 |
> > > [ 165.978643] vboxpci: IOMMU found |
47 |
> > |
48 |
> > $ dmesg | grep -i vbox |
49 |
> > [ 4.163645] vboxdrv: Found 4 processor cores. |
50 |
> > [ 4.163748] vboxdrv: fAsync=0 offMin=0x1d8 offMax=0xd44 |
51 |
> > [ 4.163792] vboxdrv: TSC mode is 'synchronous', kernel timer mode is |
52 |
> > 'normal'. |
53 |
> > [ 4.163793] vboxdrv: Successfully loaded version 4.3.32 (interface |
54 |
> > 0x001a000b). |
55 |
> > [ 4.173458] vboxpci: pci-stub module not available, cannot detach PCI |
56 |
> > devices |
57 |
> > [ 4.173461] vboxpci: IOMMU not found (not registered) |
58 |
> > |
59 |
> > That last one is suspicious, presumably connected with this: |
60 |
> > |
61 |
> > $ dmesg | grep IOMMU |
62 |
> > [ 0.119875] dmar: IOMMU: failed to map dmar0 |
63 |
> > [ 4.173461] vboxpci: IOMMU not found (not registered) |
64 |
> > |
65 |
> > I wonder what dmar0 is. |
66 |
> |
67 |
> While exploring that, I found advice to add iommu=soft to the kernel |
68 |
> options. Then I got this: |
69 |
> |
70 |
> # dmesg | grep -i dmar |
71 |
> [ 0.000000] ACPI: DMAR 0x00000000BFE880C0 000090 (v01 AMI OEMDMAR |
72 |
> 00000001 MSFT 00000097) |
73 |
> [ 0.119714] dmar: Host address width 36 |
74 |
> [ 0.119873] dmar: DRHD base: 0x000000fed90000 flags: 0x1 |
75 |
> [ 0.120202] WARNING: CPU: 0 PID: 1 at drivers/iommu/dmar.c:829 |
76 |
> warn_invalid_dmar+0x7c/0x90() |
77 |
> [ 0.120481] Your BIOS is broken; DMAR reported at address fed90000 |
78 |
> returns all ones! |
79 |
> [ 0.123772] [<ffffffff813f12bc>] warn_invalid_dmar+0x7c/0x90 |
80 |
> [ 0.123934] [<ffffffff813f2549>] dmar_parse_one_drhd+0x4f9/0x550 |
81 |
> [ 0.124096] [<ffffffff813f1129>] dmar_walk_remapping_entries+0x29/0x140 |
82 |
> [ 0.124260] [<ffffffff81907be6>] dmar_table_init+0xb9/0x138 |
83 |
> [ 0.124421] [<ffffffff813f2050>] ? dmar_free_dev_scope+0xb0/0xb0 |
84 |
> [ 0.124918] [<ffffffff813f12d0>] ? warn_invalid_dmar+0x90/0x90 |
85 |
> [ 0.127042] dmar: IOMMU: failed to map dmar0 |
86 |
> [ 0.127201] dmar: parse DMAR table failure. |
87 |
> |
88 |
> Without that kernel option: |
89 |
> |
90 |
> [ 0.000000] ACPI: DMAR 0x00000000BFE880C0 000090 (v01 AMI OEMDMAR |
91 |
> 00000001 MSFT 00000097) |
92 |
> [ 0.000000] WARNING: CPU: 0 PID: 0 at drivers/iommu/dmar.c:829 |
93 |
> warn_invalid_dmar+0x7c/0x90() |
94 |
> [ 0.000000] Your BIOS is broken; DMAR reported at address fed90000 |
95 |
> returns all ones! |
96 |
> [ 0.000000] [<ffffffff813f12bc>] warn_invalid_dmar+0x7c/0x90 |
97 |
> [ 0.000000] [<ffffffff815749a0>] dmar_validate_one_drhd+0xb0/0xf0 |
98 |
> [ 0.000000] [<ffffffff813f1129>] dmar_walk_remapping_entries+0x29/0x140 |
99 |
> [ 0.120132] dmar: Host address width 36 |
100 |
> [ 0.120291] dmar: DRHD base: 0x000000fed90000 flags: 0x1 |
101 |
> [ 0.120472] dmar: IOMMU: failed to map dmar0 |
102 |
> [ 0.120631] dmar: parse DMAR table failure. |
103 |
> |
104 |
> So all the kernel option adds is some extra debug info. ATLAS@home still |
105 |
> can't communicate with VirtualBox. |
106 |
> |
107 |
> Now that I think about it, I did update the AMI BIOS several weeks ago. It |
108 |
> went from 1102 to 2101 - a bit of a step. Maybe that's what's broken my |
109 |
> system - well, this bit of it, anyway. |
110 |
|
111 |
Could very well be the case. |
112 |
|
113 |
I get the following in my dmesg: |
114 |
|
115 |
# dmesg | grep -i iomm |
116 |
[ 0.344602] dmar: IOMMU 0: reg_base_addr fed90000 ver 1:0 cap |
117 |
c0000020660462 ecap f0101a |
118 |
[ 0.344607] dmar: IOMMU 1: reg_base_addr fed91000 ver 1:0 cap |
119 |
d2008020660462 ecap f010da |
120 |
[ 0.344688] IOMMU: dmar0 using Queued invalidation |
121 |
[ 0.344690] IOMMU: dmar1 using Queued invalidation |
122 |
[ 0.344691] IOMMU: Setting RMRR: |
123 |
[ 0.344700] IOMMU: Setting identity map for device 0000:00:02.0 [0xcd000000 |
124 |
- 0xcf1fffff] |
125 |
[ 0.344887] IOMMU: Setting identity map for device 0000:00:14.0 [0xcbea9000 |
126 |
- 0xcbeb7fff] |
127 |
[ 0.344908] IOMMU: Setting identity map for device 0000:00:1a.0 [0xcbea9000 |
128 |
- 0xcbeb7fff] |
129 |
[ 0.344926] IOMMU: Setting identity map for device 0000:00:1d.0 [0xcbea9000 |
130 |
- 0xcbeb7fff] |
131 |
[ 0.344939] IOMMU: Prepare 0-16MiB unity mapping for LPC |
132 |
[ 0.344946] IOMMU: Setting identity map for device 0000:00:1f.0 [0x0 - |
133 |
0xffffff] |
134 |
[ 165.978643] vboxpci: IOMMU found |
135 |
[14502.509549] created IOMMU domain ffff88009d275748 |
136 |
|
137 |
|
138 |
Also, not sure if the following might help: |
139 |
# zgrep -i iomm /proc/config.gz |
140 |
CONFIG_GART_IOMMU=y |
141 |
# CONFIG_CALGARY_IOMMU is not set |
142 |
CONFIG_IOMMU_HELPER=y |
143 |
CONFIG_IOMMU_API=y |
144 |
CONFIG_IOMMU_SUPPORT=y |
145 |
# Generic IOMMU Pagetable Support |
146 |
CONFIG_IOMMU_IOVA=y |
147 |
# CONFIG_AMD_IOMMU is not set |
148 |
CONFIG_INTEL_IOMMU=y |
149 |
CONFIG_INTEL_IOMMU_DEFAULT_ON=y |
150 |
CONFIG_INTEL_IOMMU_FLOPPY_WA=y |
151 |
# CONFIG_IOMMU_DEBUG is not set |
152 |
# CONFIG_IOMMU_STRESS is not set |
153 |
|
154 |
# zgrep -i dmar /proc/config.gz |
155 |
CONFIG_DMAR_TABLE=y |
156 |
|
157 |
|
158 |
-- |
159 |
Joost |