https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=223531
Wolfram Schneider changed:
What|Removed |Added
CC||wo...@freebsd.org
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=223531
Wolfram Schneider changed:
What|Removed |Added
CC||bry...@freebsd.org,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=223531
Wolfram Schneider changed:
What|Removed |Added
URL||https://reviews.freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=223531
--- Comment #14 from Conrad Meyer ---
(In reply to Wolfram Schneider from comment #12)
Yes, r305900 was introduced in CURRENT and never MFCed to 11.
--
You are receiving this mail because:
You are the assignee for the bug.
___
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=223531
Wolfram Schneider changed:
What|Removed |Added
Depends on||144736, 161912
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=223531
--- Comment #15 from Wolfram Schneider ---
Created attachment 188043
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=188043&action=edit
remove space check
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=223531
--- Comment #16 from Wolfram Schneider ---
I agree that spaces in filenames are not a good idea.
However, a kernel which is not booting due spaces is very bad. I removed the
space check in sys/kern/kern_conf.c and now I can boot my curren
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=223531
Wolfram Schneider changed:
What|Removed |Added
Status|New |In Progress
--
You are receiv
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=223531
--- Comment #17 from Conrad Meyer ---
I think a better solution might be to strip or replace unwanted characters from
the name we receive from virtio.
--
You are receiving this mail because:
You are the assignee for the bug.
_
On 14/11/2017 06:22, Anish wrote:
> Also ivhd has fault interrupt enabled which is very helpful in debugging:
>
> [root@ryzen /home/anish/FreeBSD/head]# vmstat -ia |grep ivh
> irq256: ivhd0:fault 0 0
> irq257: ivhd1:fault 0 0
>
Anish,
I ha
On 14/11/2017 06:22, Anish wrote:
> [root@ryzen /home/anish/FreeBSD/head]# vmstat -ia |grep ivh
> irq256: ivhd0:fault 0 0
> irq257: ivhd1:fault 0 0
After I fixed the MSI setup problem that I described in the previous email I was
finally able
Hi Andriy,
>After I fixed the MSI setup problem that I described in the previous email
I was
finally able to see the real problem.
Awesome! fault interrupt handler has been very helpful in debugging AMD-Vi.
>I've passed both of the PCI device to bhyve and everything started working.
Thanks!
Bhyve
12 matches
Mail list logo