I have the same issue, using Ubuntu 20.10 with Linux 5.8 kernel. The Linux
NFS client will get unresponsive and it does not recover in my case, even
if I restart NFS on FreeBSD. I upgraded from FreeBSD 12.1-RELEASE though.
On Thu, Apr 15, 2021 at 8:36 PM Allan Jude wrote:
> On 4/15/2021 9:22
On Thu, Apr 15, 2021 at 4:19 AM Willem Jan Withagen via freebsd-current <
freebsd-current@freebsd.org> wrote:
> On 15-4-2021 12:44, Yuri Pankov wrote:
> > Willem Jan Withagen via freebsd-current wrote:
> >> On 15-4-2021 11:47, Gary Jennejohn wrote:
> >>> On Thu, 15 Apr 2021 10:51:39 +0200
> >>>
> On 15 Apr 2021, at 23:09, Juraj Lutter wrote:
>
> The machine it’s running on is definitely a slow or weak one (it’s dell
> r740xd with 2x CPU, 256GB RAM, 22xNVMe data zpool).
Is definitely *NOT* a slow or weak one :-)
otis
___
> On 15 Apr 2021, at 22:47, Rick Macklem wrote:
>
> Allan Jude wrote:
>> On 4/15/2021 9:22 AM, Chris Roose wrote:
>>> I posted this in -questions and someone suggested I post here as well.
>>>
>>> I'm having NFS availability issues between my Proxmox client and FreeBSD
>>> server (10G link)
Stupid Outlook...
I wrote:
[stuff snipped]
>- Alternately you can try rscheff@'s alternate proposed patch that is at
> https://reviews.freebsd.og/D29690.
Oops, that's
https:/reviews.freebsd.org/D29690
But you can figure out the link;-), rick
rick
I have not yet had time to test this one,
I wrote:
[stuff snipped]
>- Alternately you can try rscheff@'s alternate proposed patch that is at
> https://reviews.freebsd.og/D29690.
Oops, that's
https:/reviews.freebsd.org/D29690
rick
I have not yet had time to test this one, but since I cannot reproduce the
hang, I can
only do
Allan Jude wrote:
>On 4/15/2021 9:22 AM, Chris Roose wrote:
>> I posted this in -questions and someone suggested I post here as well.
>>
>> I'm having NFS availability issues between my Proxmox client and FreeBSD
>> server (10G link) since upgrading to 13->RELEASE. And unfortunately I
>>
On 15.04.2021 21:41, Dmitry Chagin wrote:
calltrap()
--- trap 0x9
run_interrupt_driven_config_hooks()
boot_run_interrupt_driven_config_hooks()
mi_startup()
It is 100% reproducible, and I cannot issue commands to kernel debugger,
keyboard is dead.
Enabling verbose boot helps, with
On 15.04.2021 21:41, Dmitry Chagin wrote:
Enabling verbose boot helps, with verbose boot it boots to installer.
Looks like some race condition.
try to boot verbose
It helps. Sometimes. And soemtimes even verbose boot gives same Fatal Trap
with same stacktrace.
It is why I think
On Thu, Apr 15, 2021 at 06:04:55PM +0300, Lev Serebryakov wrote:
>
> I'm trying to install CURRENT
> (FreeBSD-14.0-CURRENT-amd64-20210408-15dc713ceb5-245885-memstick.img)
> snapshot onto Lenovo Thinkpad T540p, i7-4700 based laptop.
>
> Kernel traps on boot with "Fatal trap 9" and this
On 4/15/2021 9:22 AM, Chris Roose wrote:
> I posted this in -questions and someone suggested I post here as well.
>
> I'm having NFS availability issues between my Proxmox client and FreeBSD
> server (10G link) since upgrading to 13-RELEASE. And unfortunately I upgraded
> my ZFS pool to v2.0.0
I posted this in -questions and someone suggested I post here as well.
I'm having NFS availability issues between my Proxmox client and FreeBSD server
(10G link) since upgrading to 13-RELEASE. And unfortunately I upgraded my ZFS
pool to v2.0.0 before I noticed the issue, so I'm kind of stuck.
Willem Jan Withagen via freebsd-current wrote:
> On 15-4-2021 11:47, Gary Jennejohn wrote:
>> On Thu, 15 Apr 2021 10:51:39 +0200
>> Willem Jan Withagen via freebsd-current
>> wrote:
>>
>>> Hi,
>>>
>>> I actually went completely back to the basic setup with directories
>>> /usr/src and /usr/obj
I just got this one:
0210415 17:01:45 all (458/755): callout_reset_on.sh
kernel trap 9 with interrupts disabled
Fatal trap 9: general protection fault while in kernel mode
cpuid = 10; apic id = 0a
instruction pointer = 0x20:0x80c7c286
stack pointer = 0x0:0xfe00e49b0730
frame
I'm trying to install CURRENT
(FreeBSD-14.0-CURRENT-amd64-20210408-15dc713ceb5-245885-memstick.img) snapshot
onto Lenovo Thinkpad T540p, i7-4700 based laptop.
Kernel traps on boot with "Fatal trap 9" and this stack trace (hand-copied):
calltrap()
--- trap 0x9
On 15-4-2021 14:20, Emmanuel Vadot wrote:
On Thu, 15 Apr 2021 10:51:39 +0200
Willem Jan Withagen via freebsd-current
wrote:
Hi,
I actually went completely back to the basic setup with directories
/usr/src and /usr/obj
But even then I do not manage to buildworld.
The process keeps bumping
On Thu, 15 Apr 2021 10:51:39 +0200
Willem Jan Withagen via freebsd-current
wrote:
> Hi,
>
> I actually went completely back to the basic setup with directories
> /usr/src and /usr/obj
> But even then I do not manage to buildworld.
> The process keeps bumping into missing bsm/audit.
>
> First
On 15-4-2021 12:44, Yuri Pankov wrote:
Willem Jan Withagen via freebsd-current wrote:
On 15-4-2021 11:47, Gary Jennejohn wrote:
On Thu, 15 Apr 2021 10:51:39 +0200
Willem Jan Withagen via freebsd-current
wrote:
Hi,
I actually went completely back to the basic setup with directories
/usr/src
On 15-4-2021 11:47, Gary Jennejohn wrote:
On Thu, 15 Apr 2021 10:51:39 +0200
Willem Jan Withagen via freebsd-current wrote:
Hi,
I actually went completely back to the basic setup with directories
/usr/src and /usr/obj
But even then I do not manage to buildworld.
The process keeps bumping
On Thu, 15 Apr 2021 10:51:39 +0200
Willem Jan Withagen via freebsd-current wrote:
> Hi,
>
> I actually went completely back to the basic setup with directories
> /usr/src and /usr/obj
> But even then I do not manage to buildworld.
> The process keeps bumping into missing bsm/audit.
>
> First
Hi,
I actually went completely back to the basic setup with directories
/usr/src and /usr/obj
But even then I do not manage to buildworld.
The process keeps bumping into missing bsm/audit.
First case was when it tried to build the 64bit libc.
I copied the bsm directory into
21 matches
Mail list logo
