[Bug 230722] [nvme][resume] Delay and possible deadlock after resume

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230722

Alexandr Krivulya  changed:

   What|Removed |Added

 CC||shur...@shurik.kiev.ua

--- Comment #4 from Alexandr Krivulya  ---
I have not any data corruptions, but I prefer to shutdown system instead of
suspend until we do not have any progress on it.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 225911] [asmc] [patch] Add support for mid-2011 Macmini 5,2

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225911

David Bright  changed:

   What|Removed |Added

   Assignee|b...@freebsd.org|d...@freebsd.org

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 203431] [asmc] [patch] Add support for 2006 MacPro1,1 to the device driver for the Apple System Management Console (SMC)

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203431

David Bright  changed:

   What|Removed |Added

   Assignee|b...@freebsd.org|d...@freebsd.org

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 211513] [patch] [asmc] Patch to add MacBook Pro 9,2 support

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211513

David Bright  changed:

   What|Removed |Added

   Assignee|b...@freebsd.org|d...@freebsd.org

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 208117] regex(3): implement equivalence classes

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208117

Yuri Pankov  changed:

   What|Removed |Added

 CC||yur...@freebsd.org
Summary|/usr/bin/grep: implement|regex(3): implement
   |equivalence classes |equivalence classes
   Assignee|b...@freebsd.org|yur...@freebsd.org
 Status|New |In Progress

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 233960] Add Volume Management Device (VMD) stub driver

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233960

Bug ID: 233960
   Summary: Add Volume Management Device (VMD) stub driver
   Product: Base System
   Version: CURRENT
  Hardware: amd64
OS: Any
Status: New
  Severity: Affects Many People
  Priority: ---
 Component: kern
  Assignee: b...@freebsd.org
  Reporter: dave.fug...@gmail.com

Created attachment 200058
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=200058&action=edit
VMD Driver Patch

At a high-level, "Intel® VMD enables hot swap replacement of NVMe* SSDs from
the PCIe* bus without shutting down the system while standardized LED
management helps provide quick identification of SSD status."  

This is realized through the addition of a VMD controller on the PCIe bus of
high-end systems (e.g., Xeon) which "hides" 1 to N PCIe ports underneath it. 
As you might imagine, this implies the need for a VMD driver which either
delegates incoming NVMe requests to the appropriate drivers (e.g., NVMe,
hot-plug, etc.) or a VMD driver which incorporates the NVMe, hot-plug, etc.
functionality all on its own.

FreeBSD is missing either such type of VMD driver today, and consequently
end-users like Netflix are getting the mistaken impression FreeBSD doesn't have
a driver for their invisible NVMe devices or the NVMe devices are broken...

Attached to this bug report is a patch adding a VMD stub driver informing the
end-user they should disable the VMD feature in their BIOS.  This stub driver
is a stop-gap measure to eventually be replaced with a full-fledged VMD driver
(I work for the NVMe/VMD OSS driver team at Intel).

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 230722] [nvme][resume] Delay and possible deadlock after resume

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230722

--- Comment #5 from Warner Losh  ---
I have some code in my https://github.com/bsdimp/freebsd in the nvme-suspend
branch you might want to test. I've not had time to test it out, so I'm looking
for help testing it out.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 233960] Add Volume Management Device (VMD) stub driver

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233960

--- Comment #1 from David Fugate  ---
BTW, this patch was tested in a system with VMD enabled:
root@midnight-freebsd:/usr/src # dmesg | grep vmd
vmd0: Unsupported Volume Management Device (VMD) controller enabled.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 232921] freebsd-update upgrade does not execute pwd_mkdb for ntpd

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232921

Michael Laß  changed:

   What|Removed |Added

 CC||be...@bi-co.net

--- Comment #3 from Michael Laß  ---
I also encountered this issue doing a binary upgrade and it can cause a bit of
trouble:

If pwd_mkdb is not run, ntpd will still run as root since the user ntpd is
unknown. On the very first start, the rc.d script will move the drift file to
/var/db/ntp and also place the .pid file there. Both files will be owned by
root at this point. If you now run pwd_mkdb to create user ntpd, the daemon
won't be properly started next time since user ntpd cannot write to the drift
and the .pid file.

This can be solved by simply removing the files or fixing the permissions but
it may be worth noting this in the release notes or upgrade instructions.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 233853] 12.0-RC3 ntpd leap second file expired

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233853

Michael Laß  changed:

   What|Removed |Added

 CC||be...@bi-co.net

--- Comment #1 from Michael Laß  ---
Could this have been solved in the final release of 12.0 or be a local problem
with your installation? For me, ntpd shows the following during startup on
12.0-RELEASE:

ntpd[802]: leapsecond file ('/var/db/ntpd.leap-seconds.list'): good hash
signature
ntpd[802]: leapsecond file ('/var/db/ntpd.leap-seconds.list'): loaded,
expire=2019-06-28T00:00:00Z last=2017-01-01T00:00:00Z ofs=37

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 233969] Improve performance of Dell Intel P4600 NVMe SSDs

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233969

Bug ID: 233969
   Summary: Improve performance of Dell Intel P4600 NVMe SSDs
   Product: Base System
   Version: CURRENT
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Some People
  Priority: ---
 Component: kern
  Assignee: b...@freebsd.org
  Reporter: dave.fug...@gmail.com

Created attachment 200070
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=200070&action=edit
Patch to sys/dev/nvme/nvme_ns.c

Dell-branded Intel P4600 NVMe drives benefit from NVMe 1.3's NOIOB feature.
Unfortunately just like Intel DC P4500s, they don't advertise themselves as
benefiting from this...

The attached patch adds P4600s to the existing list of old drives which benefit
from striping.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 233969] Improve performance of Dell Intel P4600 NVMe SSDs

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233969

Conrad Meyer  changed:

   What|Removed |Added

 CC||c...@freebsd.org
   Assignee|b...@freebsd.org|s...@freebsd.org

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 219399] System panics after several hours of 14-threads-compilation orgies using poudriere on AMD Ryzen...

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399

--- Comment #279 from Sara Taylor  ---
root@asbach:/var/crash/#kgdb7121 /boot/kernel/kernel /var/crash/vmcore.3
GNU gdb (GDB) 7.12.1 [GDB v7.12.1 for FreeBSD]
Copyright (C) 2017 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-portbld-freebsd11.0".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /boot/kernel/kernel...Reading symbols from
/usr/lib/debug//boot/kernel/kernel.debug...done.
done.
Reading symbols from /boot/kernel/kernel...Reading symbols from
/usr/lib/debug//boot/kernel/kernel.debug...done.
done.
Reading symbols from /boot/kernel/zfs.ko...Reading symbols from
/usr/lib/debug//boot/kernel/zfs.ko.debug...done.
done.
Reading symbols from /boot/kernel/opensolaris.ko...Reading symbols from
/usr/lib/debug//boot/kernel/opensolaris.ko.debug...done.
done.
Reading symbols from /boot/kernel/vmm.ko...Reading symbols from
/usr/lib/debug//boot/kernel/vmm.ko.debug...done.
done.
Reading symbols from /boot/kernel/ums.ko...Reading symbols from
/usr/lib/debug//boot/kernel/ums.ko.debug...done.
done.
Reading symbols from /boot/kernel/pflog.ko...Reading symbols from
/usr/lib/debug//boot/kernel/pflog.ko.debug...done.
done.
Reading symbols from /boot/kernel/pf.ko...Reading symbols from
/usr/lib/debug//boot/kernel/pf.ko.debug...done.
done.
Reading symbols from /boot/kernel/linux.ko...Reading symbols from
/usr/lib/debug//boot/kernel/linux.ko.debug...done.
done.
Reading symbols from /boot/kernel/linux_common.ko...Reading symbols from
/usr/lib/debug//boot/kernel/linux_common.ko.debug...done.
done.
Reading symbols from /boot/kernel/linux64.ko...Reading symbols from
/usr/lib/debug//boot/kernel/linux64.ko.debug...done.
done.
Reading symbols from /boot/modules/nvidia.ko...(no debugging symbols
found)...done.
Reading symbols from /boot/kernel/nullfs.ko...Reading symbols from
/usr/lib/debug//boot/kernel/nullfs.ko.debug...done.
done.
Reading symbols from /boot/kernel/linprocfs.ko...Reading symbols from
/usr/lib/debug//boot/kernel/linprocfs.ko.debug...done.
done.
Reading symbols from /boot/kernel/tmpfs.ko...Reading symbols from
/usr/lib/debug//boot/kernel/tmpfs.ko.debug...done.
done.
Reading symbols from /boot/kernel/fdescfs.ko...Reading symbols from
/usr/lib/debug//boot/kernel/fdescfs.ko.debug...done.
done.
No thread selected.
(kgdb) info threads
No threads.


hey! when i am going to reboot my system the bug is clear but when i again
login and start my system the bug will still appear. Whats happening with me.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 230722] [nvme][resume] Delay and possible deadlock after resume

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230722

--- Comment #6 from Alexandr Krivulya  ---
Do I need to build a whole tree or just patch these files?

sys/dev/nvme/nvme.c
sys/dev/nvme/nvme_ctrlr.c
sys/dev/nvme/nvme_private.h

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 83761] [panic] vm-related panic: blst_radix_free: freeing free block

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=83761

Conrad Meyer  changed:

   What|Removed |Added

Version|4.11-STABLE |CURRENT
 CC||c...@freebsd.org,
   ||ma...@freebsd.org
 Status|Closed  |Open
 Resolution|FIXED   |---

--- Comment #3 from Conrad Meyer  ---
I hit apparently the same stack and panic in FreeBSD-CURRENT 13.x, r340866.

panic: freeing free block
panic() at panic+0x3c/frame 0xfe00b4a59600
blst_meta_free() at blst_meta_free+0x12a/frame 0xfe00b4a59640
blst_meta_free() at blst_meta_free+0xd3/frame 0xfe00b4a59680
blst_meta_free() at blst_meta_free+0xd3/frame 0xfe00b4a596c0
blst_meta_free() at blst_meta_free+0xd3/frame 0xfe00b4a59700
blist_free() at blist_free+0x28/frame 0xfe00b4a59720
swp_pager_freeswapspace() at swp_pager_freeswapspace+0x102/frame
0xfe00b4a59740
swap_pager_dealloc() at swap_pager_dealloc+0x150/frame 0xfe00b4a59760
vm_object_terminate() at vm_object_terminate+0x58/frame 0xfe00b4a597a0
vm_object_deallocate() at vm_object_deallocate+0x588/frame 0xfe00b4a59820
vm_map_entry_deallocate() at vm_map_entry_deallocate+0x44/frame
0xfe00b4a59850
vm_map_process_deferred() at vm_map_process_deferred+0x3d/frame
0xfe00b4a59870
vm_map_remove() at vm_map_remove+0x48/frame 0xfe00b4a598a0
vmspace_exit() at vmspace_exit+0x1c4/frame 0xfe00b4a598f0
exit1() at exit1+0x4b5/frame 0xfe00b4a59970
sigexit() at sigexit+0x7f/frame 0xfe00b4a599a0
postsig() at postsig+0x31d/frame 0xfe00b4a59a70
ast() at ast+0x2e7/frame 0xfe00b4a59ab0
doreti_ast() at doreti_ast+0x1f/frame 0x7ffe0a70

For what it's worth, the system was out of memory at the time and the OOM
killer may have been involved.  Still, this is probably not an acceptable
outcome.  I have a core and can provide GDB information as-needed, but probably
not the core unredacted contents.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"