https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213370
--- Comment #2 from Andrey ---
Hello.
This is maybe actual for FreeBSD-10.3.
I stopped using FreeBSD after that.
--
You are receiving this mail because:
You are the assignee for the bug.
[The USB I/O problem.]
On 2022-Mar-13, at 13:46, Mark Millard wrote:
>> FreeBSD pelorus.zefox.org 13.1-STABLE FreeBSD 13.1-STABLE #24
>> stable/13-n249989-b85d0d603c5: Sat Mar 12 17:47:19 PST 2022
>> b...@pelorus.zefox.org:/usr/obj/usr/src/arm64.aarch64/sys/GENERIC arm64
>
>> . . .
>>
>>
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and ob
On 2022-Mar-13, at 12:34, bob prohaska wrote:
> It looks as if things are somewhat altered, but not really
> improved, after updating to
>
> FreeBSD pelorus.zefox.org 13.1-STABLE FreeBSD 13.1-STABLE #24
> stable/13-n249989-b85d0d603c5: Sat Mar 12 17:47:19 PST 2022
> b...@pelorus.zefox.or
It looks as if things are somewhat altered, but not really
improved, after updating to
FreeBSD pelorus.zefox.org 13.1-STABLE FreeBSD 13.1-STABLE #24
stable/13-n249989-b85d0d603c5: Sat Mar 12 17:47:19 PST 2022
b...@pelorus.zefox.org:/usr/obj/usr/src/arm64.aarch64/sys/GENERIC arm64
on the P
On 13 Mar 2022, at 17:45, Michael Gmelin wrote:
On 13. Mar 2022, at 18:16, Bjoern A. Zeeb
wrote:
On 13 Mar 2022, at 16:33, Michael Gmelin wrote:
It's important to point out that this only happens with kern.ncpu>1.
With kern.ncpu==1 nothing gets stuck.
This perfectly fits into the picture,
> On 13. Mar 2022, at 18:16, Bjoern A. Zeeb
> wrote:
>
> On 13 Mar 2022, at 16:33, Michael Gmelin wrote:
>> It's important to point out that this only happens with kern.ncpu>1.
>> With kern.ncpu==1 nothing gets stuck.
>>
>> This perfectly fits into the picture, since, as pointed out by Joha
On 13 Mar 2022, at 16:33, Michael Gmelin wrote:
It's important to point out that this only happens with kern.ncpu>1.
With kern.ncpu==1 nothing gets stuck.
This perfectly fits into the picture, since, as pointed out by Johan,
the first commit that is affected[0] is about multicore support.
Igno
On Sun, 13 Mar 2022 14:32:50 +0100
Johan Hendriks wrote:
> On 13/03/2022 14:06, Patrick M. Hausen wrote:
> > Hi all,
> >
> > i was a bit puzzled by Michael using bhyve trying to reproduce.
> > Up until now I thought bhyve uses tap and not epair?
> >
> > Anyway ...
> >
> >> Am 13.03.2022 um 1
On 13/03/2022 14:06, Patrick M. Hausen wrote:
Hi all,
i was a bit puzzled by Michael using bhyve trying to reproduce.
Up until now I thought bhyve uses tap and not epair?
Anyway ...
Am 13.03.2022 um 14:01 schrieb Johan Hendriks :
I have no idea why it does not work on my setup, which is not
> On 13. Mar 2022, at 14:07, Patrick M. Hausen wrote:
>
> Hi all,
>
> i was a bit puzzled by Michael using bhyve trying to reproduce.
> Up until now I thought bhyve uses tap and not epair?
>
In my setup, FreeBSD 14 runs on a bhyve vm, hosting the jails, which use vnet.
Bare metal -> FreeB
> On 13 Mar 2022, at 08:01, Johan Hendriks wrote:
>
>
>> On 13/03/2022 13:37, Kristof Provost wrote:
>>> On 13 Mar 2022, at 5:26, Johan Hendriks wrote:
>>> Copyd my haproxy en web01 jail to this machine and have the same problem.
>>>
>> Do you mean you can or cannot reproduce it on the seco
Hi all,
i was a bit puzzled by Michael using bhyve trying to reproduce.
Up until now I thought bhyve uses tap and not epair?
Anyway ...
> Am 13.03.2022 um 14:01 schrieb Johan Hendriks :
> I have no idea why it does not work on my setup, which is nothing out of the
> ordinary i think, basic full
On 13/03/2022 13:37, Kristof Provost wrote:
On 13 Mar 2022, at 5:26, Johan Hendriks wrote:
Copyd my haproxy en web01 jail to this machine and have the same problem.
Do you mean you can or cannot reproduce it on the second machine?
I have the same problem.
Could it be a sysctl i use? or b
On 13 Mar 2022, at 5:26, Johan Hendriks wrote:
> Copyd my haproxy en web01 jail to this machine and have the same problem.
>
Do you mean you can or cannot reproduce it on the second machine?
> Could it be a sysctl i use? or boot/loader.conf setting.
>
None of those settings strike me as likely to
> On 13. Mar 2022, at 11:27, Johan Hendriks wrote:
>
>
>
> Op zo 13 mrt. 2022 01:17 schreef Michael Gmelin :
>> I also gave it another go (this time with multiple CPUs assigned to the vm),
>> still works just fine - so I think we would need more details about the
>> setup.
>>
>> Would it
Op zo 13 mrt. 2022 01:17 schreef Michael Gmelin :
> I also gave it another go (this time with multiple CPUs assigned to the
> vm), still works just fine - so I think we would need more details about
> the setup.
>
> Would it make sense to share our test setups, so Johan can try to
> reproduce with
17 matches
Mail list logo