Публикации 2020 года
___ 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 252225] won't accept flash drive: "got CAM status 0x50" for Kingston DataTraveler G3
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252225 Mark Linimon changed: What|Removed |Added Component|kern|usb Assignee|b...@freebsd.org|u...@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 251906] autofs: automounter always only adds to /var/db/mounttab but never clears it
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251906 Robert Wing changed: What|Removed |Added CC||r...@freebsd.org URL||https://reviews.freebsd.org ||/D27801 -- 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 251906] autofs: automounter always only adds to /var/db/mounttab but never clears it
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251906 --- Comment #1 from Martin Birgmeier --- It seems there is also a similar issue with /var/db/mountdtab: On the NFS server, entries only accumulate in that file but are never cleared. -- Martin -- 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 244878] Kernel panic due to spin lock held too long
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244878 --- Comment #12 from Mark Johnston --- (In reply to Adam Jimerson from comment #11) Could you try enabling compression on the core dump? Add -Z to the dumpon(8) invocation, e.g., by adding dumpon_flags="-Z" to /etc/rc.conf. -- 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 244878] Kernel panic due to spin lock held too long
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244878 --- Comment #13 from Adam Jimerson --- (In reply to Mark Johnston from comment #12) I certainly can enable that and see if that helps. -- 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 251906] autofs: automounter always only adds to /var/db/mounttab but never clears it
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251906 --- Comment #2 from Robert Wing --- (In reply to Martin Birgmeier from comment #1) Hey Martin, This patch should also fix that. With this patch, `automount -u` will try to use umount(8) when unmounting filesystems. umount(8) does some additional work such as notifying the mountd server that a NFS mount has been unmounted, which will remove the /var/db/mountdtab entry on the mountd server. If the notification to the mountd server is successful, the /var/db/mounttab entry will also be removed. -Rob -- 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 252240] "zfs send -R -I | zfs receive -F" not destroying snapshots that don't exist on the sending side
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252240 Bug ID: 252240 Summary: "zfs send -R -I | zfs receive -F" not destroying snapshots that don't exist on the sending side Product: Base System Version: 12.2-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: b...@freebsd.org Reporter: l...@perftech.com This is similar to 169964, but that was due to lack of the -R option, so I'm submitting this as a new bug. This appears to be new to 12.2-RELEASE. If the receiving side is running 12.1 or 12.0, everything works properly, but if the receiving side is running 12.2, then snapshots that don't exist on the sending side are not destroyed on the receiving side. The version of the sending side doesn't appear to make any difference, the problem appears to be strictly on the receive side, and consistently fails with 12.2 and withs with 12.1 or prior. In fact, on a given system, running freebsd-update to upgrade from 12.1 to 12.2 causes the problem to appear, and reverting back to 12.1, the problem disappears. Sample commands: zfs create ds/test zfs snapshot ds/test@1 zfs snapshot ds/test@2 zfs snapshot ds/test@3 zfs snapshot ds/test@4 zfs snapshot ds/test@5 zfs send -R ds/test@5 | ssh desthost zfs receive -F ds/test desthost now has the filesystem and all snapshots. zfs snapshot ds/test@6 zfs send -R -I ds/test@5 ds/test@6 | ssh desthost zfs receive -F ds/test desthost now has the test@6 snapshot zfs destroy ds/test@2 zfs destroy ds/test@3 zfs send -R -I ds/test@5 ds/test@6 | ssh desthost zfs receive -F ds/test If desthost is running 12.2, then test@2 and test@3 remain. If desthost is running 12.1 or 12.0, then test@2 and test@3 are destroyed. And it doesn't matter whether the snapshot has previously synced or not, for example: zfs snapshot ds/test@7 zfs send -R -I ds/test@6 ds/test@7 | ssh desthost zfs receive -F ds/test still doesn't cause @2 and @3 to get destroyed. However, zfs send -R -I ds/test@1 ds/test@7 | ssh desthost zfs receive -F ds/test does cause @2 and @3 to get destroyed. But that's not an acceptable work-around, and this appears to be a regression from prior versions. -- 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 252240] "zfs send -R -I | zfs receive -F" not destroying snapshots that don't exist on the sending side
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252240 Mark Linimon changed: What|Removed |Added Assignee|b...@freebsd.org|f...@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 252241] MacBook Pro 8,3 17" black screen after suspend/resume
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252241 Bug ID: 252241 Summary: MacBook Pro 8,3 17" black screen after suspend/resume Product: Base System Version: 12.2-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: b...@freebsd.org Reporter: j...@freebsd.org System suspends and seems to resume fine except for the screen. I can ssh in after resume, but the console is unresponsive and I cannot switch to a vt. The system has two GPUs: vendor = 'Intel Corporation' device = '2nd Generation Core Processor Family Integrated Graphics Controller' class = display -- vendor = 'Advanced Micro Devices, Inc. [AMD/ATI]' device = 'Whistler [Radeon HD 6630M/6650M/6750M/7670M/7690M]' class = display Both work fine in general. Running auto-gpu-setup (called from desktop-installer), I first selected the modesetting driver + drm-kmod and got a full-functional desktop. 1.. For most modern Intel GPUs, use the modesetting driver which is part of the FreeBSD base. pkg install -y drm-kmod Add kld_list="/boot/modules/i915kms.ko" to /etc/rc.conf [snip] After testing the Intel GPU setup, ran auto-gpu-setup again and selected option 2, ati driver + drm0kmod: 1.. For recent AMD GPUs, you can try pkg install -y drm-kmod xf86-video-amdgpu Add "kld_list=amdgpu" to /etc/rc.conf 2.. For older AMD GPUs, you can try pkg install -y drm-kmod xf86-video-ati Add "kld_list=/boot/modules/radeonkms.ko" to /etc/rc.conf [snip] System booted into a working desktop, but using scfb rather than radeon. Adding the following got Xorg to use the radeon driver: <<>> /home/bacon 107 # cat /etc/X11/xorg.conf.d/radeon.conf Section "Device" Identifier "Card0" Driver "radeon" BusID "PCI:1:0:0" EndSection However, behavior after suspend/resume is the same with either modesetting or radeon. I reduced the system to nothing but generic kernel + ATP driver for the touchpad and this did not help. There are quite a few drivers auto-loaded, though. Seems doubtful to me that any of them are causing the issue since everything seems to work after resume except the screen. kldstat Id Refs AddressSize Name 1 101 0x8020 227ad00 kernel 21 0x8247b000 9080 atp.ko 31 0x82fdb000 1a20 fdescfs.ko 41 0x82fdd000103f0 fuse.ko 51 0x82fee000 152fd0 radeonkms.ko 62 0x8314100076570 drm.ko 75 0x831b800012d30 linuxkpi.ko 84 0x831cb00012f30 linuxkpi_gplv2.ko 92 0x831de000 6d0 debugfs.ko 101 0x831df000 f181 ttm.ko 111 0x831ef00033ee0 if_bwn.ko 12 14 0x8322300037e48 bhnd.ko 132 0x8325b000 3408 gpiobus.ko 144 0x8325f000 a1f0 bhndb.ko 151 0x8326a000 3c50 bhndb_pci.ko 161 0x8326e000 1a58 bhnd_pci_hostb.ko 172 0x8327 1b64 bhnd_pci.ko 181 0x83272000 598 bcma_bhndb.ko 191 0x83273000 4818 bcma.ko 201 0x83278000 ad4 siba_bhndb.ko 211 0x83279000 4ea8 siba.ko 221 0x8327e000 a160 if_lagg.ko 231 0x83289000 1860 uhid.ko 241 0x8328b000 1a40 wmt.ko 251 0x8328d000 2908 ums.ko 261 0x8329 4260 ng_ubt.ko 276 0x83295000 9bd0 netgraph.ko 282 0x8329f000 9128 ng_hci.ko 293 0x832a9000 9b0 ng_bluetooth.ko 301 0x832aa000 29e0 wsp.ko 311 0x832ad000 caf0 ng_l2cap.ko 321 0x832ba0001af20 ng_btsocket.ko 331 0x832d5000 2150 ng_socket.ko 341 0x832d8000 46f0 autofs.ko 351 0x832dd000 acf mac_ntpd.ko On the whole, this is a perfectly usable FreeBSD laptop for my purposes. I don't personally care about suspend/resume on this machine since I don't take it anywhere (I prefer to carry a smaller one), but I'm happy to help diagnose and fix this issue if possible. -- 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 252253] Intel vmd NVMe controller not detected on 13-CURRENT
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252253 Bug ID: 252253 Summary: Intel vmd NVMe controller not detected on 13-CURRENT Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Many People Priority: --- Component: kern Assignee: b...@freebsd.org Reporter: n...@neelc.org I recently got a HP Spectre x360 13-aw200, and am relegating my existing x360 13-ap0053dx for running RELEASE. Going forward, I will talk about the 13-aw200 I do not see any NVMe controller. These set of patches show the Linux implementation: https://lore.kernel.org/linux-pci/b07f1c8a3089f0b4aa43004ccf9131f407b63a7d.ca...@intel.com/T/#ma2e8cc45f20403aaf76a2a3fa26725e196ceadc1 -- 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 252253] Intel vmd NVMe controller not detected on 13-CURRENT
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252253
--- Comment #1 from Neel Chauhan ---
Pictures of the non-detection is here: https://imgur.com/a/ighTwHQ
A patch like this:
--- a/sys/dev/vmd/vmd.c
+++ b/sys/dev/vmd/vmd.c
@@ -66,13 +66,20 @@ struct vmd_type {
#define INTEL_VENDOR_ID0x8086
#define INTEL_DEVICE_ID_VMD0x201d
#define INTEL_DEVICE_ID_VMD2 0x28c0
+#define INTEL_DEVICE_ID_VMD3 0x9a0b
static struct vmd_type vmd_devs[] = {
{ INTEL_VENDOR_ID, INTEL_DEVICE_ID_VMD, "Intel Volume Management
Device" },
{ INTEL_VENDOR_ID, INTEL_DEVICE_ID_VMD2, "Intel Volume Management
Device" },
+{ INTEL_VENDOR_ID, INTEL_DEVICE_ID_VMD3, "Intel Volume Management
Device" },
{ 0, 0, NULL }
gave a kernel panic, showing more needs to be done to support NVMe.
--
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"
