[Bug 204521] [new driver] [request] Port rtsx from OpenBSD to FreeBSD
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204521 --- Comment #66 from Alexey Dokuchaev --- (In reply to hlh from comment #64) > git updated. Awesome! I can confirm my RTS5227 (card=0x1992103c chip=0x522710ec) is able to read the SD card successfully now. -- 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"
Научные публикации
___ 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 246748] feature wish: reply_from_interface and reply_src sysctl for IPv6
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246748 Bug ID: 246748 Summary: feature wish: reply_from_interface and reply_src sysctl for IPv6 Product: Base System Version: Unspecified Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: b...@freebsd.org Reporter: g...@greenie.muc.de IPv4 has the "net.inet.icmp.reply_from_interface" and "net.inet.icmp.reply_src" sysctls to influence source address selection for generated ICMP error responses (most typically, "administratively prohibited" or "ttl expired"). By default, these packets are sent with the source address of the interface where the generated ICMP packet is leaving out. In a router/firewall context, "many network devices" use the source address of the interface where the original packet (that triggered the ICMP reply) came *in* on - which makes, for example "traceroute" show up the ingress interface into the router. This is a very valuable tool. If you want FreeBSD to do the same thing, you set "net.inet.icmp.reply_from_interface=1" - which works very nicely. Here comes the feature request: IPv6 support does not have either sysctl today (at least up to 12.1). Building a dual-stack setup with "I can do this in IPv4 but not in IPv6" is not good. Can such functionality be added to the IPv6 ICMP generation as well? The IPv4 code path looks fairly simple (~30 lines of code), but I most certainly do not understand the networking code myself to contribute an IPv6 equivalent. Thanks :-) -- 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 246748] feature wish: reply_from_interface and reply_src sysctl for IPv6
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246748 Gert Doering changed: What|Removed |Added Keywords||feature, ipv6 -- 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 246750] ZFS: Confusing error message when creating ZFS pool on vdev
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246750 Bug ID: 246750 Summary: ZFS: Confusing error message when creating ZFS pool on vdev Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: b...@freebsd.org Reporter: kwia...@panic.pl On default FreeBSD configuration (vfs.zfs.vol.recursive == 0) it's impossible to create ZFS pools on vdevs. When users try to do this they see generic and confusing error message: ``` # zfs create -V 1G -s zroot/kwiat # zpool create -f kwiat /dev/zvol/zroot/kwiat cannot create 'kwiat': no such pool or dataset ``` For someone not experienced in ZFS it will take some time to learn how to workaround this as it seems it's not documented anywhere. What's more, on Linux it just works. My ideas how to improve this: 1) Better error message when vfs.zfs.vol.recursive==0 and backing device is zvol. Example: "cannot create 'kwiat': creating pool on zvol is dangerous. See man zpool(8) for more info." 2) Document it in the zpool(8) manpage in "zpool create" section -- 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 204521] [new driver] [request] Port rtsx from OpenBSD to FreeBSD
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204521 --- Comment #67 from h...@restart.be --- I complete/update the write code but when mounting a msdosfs I get: panic: general protection fault cpuid = 3 time = 1590504848 KDB: stack backtrace: #0 0x80695005 at kdb_backtrace+0x65 #1 0x8064a7ab at vpanic+0x17b #2 0x8064a623 at panic+0x43 #3 0x80a0b301 at trap_fatal+0x391 #4 0x80a0a787 at trap+0x67 #5 0x809e4728 at calltrap+0x8 #6 0x806f387e at bufwrite+0x1fe #7 0x807294c0 at vn_fsync_buf+0x250 #8 0x80aaa84b at VOP_FSYNC_APV+0x7b #9 0x806f3a0b at bufsync+0x3b #10 0x8071410d at bufobj_invalbuf+0x1ad #11 0x807173fe at vgonel+0x17e #12 0x80717a46 at vgone+0x36 #13 0x8052a7f7 at devfs_delete+0x177 #14 0x8052ad36 at devfs_populate_loop+0x1e6 #15 0x8052ab3a at devfs_populate+0x2a #16 0x8052fbbb at devfs_populate_vp+0x9b #17 0x8052dc0b at devfs_lookup+0x2b Uptime: 53m47s with sysctl debug.bootverbose=1 : rtsx0: rtsx_mmcbr_request(CMD17 arg 0x40001 flags 0x35 dlen 512 dflags 0x2) rtsx0: rtsx_xfer_short() - Read xfer: 512 bytes with block size 512 rtsx0: rtsx_send_cmd() rtsx0: Interrupt handler - enabled: 0x3200, status: 0xa001 rtsx0: rtsx_send_cmd() rtsx0: Interrupt handler - enabled: 0x3200, status: 0xa001 rtsx0: rtsx_send_cmd() rtsx0: Interrupt handler - enabled: 0x3200, status: 0xa001 rtsx0: rtsx_mmcbr_release_host() rtsx0: rtsx_mmcbr_acquire_host() rtsx0: rtsx_mmcbr_request(CMD17 arg 0x4 flags 0x35 dlen 512 dflags 0x2) rtsx0: rtsx_xfer_short() - Read xfer: 512 bytes with block size 512 rtsx0: rtsx_send_cmd() rtsx0: Interrupt handler - enabled: 0x3200, status: 0xa001 rtsx0: rtsx_send_cmd() rtsx0: Interrupt handler - enabled: 0x3200, status: 0xa001 rtsx0: rtsx_send_cmd() rtsx0: Interrupt handler - enabled: 0x3200, status: 0xa001 rtsx0: rtsx_mmcbr_release_host() rtsx0: rtsx_mmcbr_acquire_host() rtsx0: rtsx_mmcbr_request(CMD17 arg 0x40001 flags 0x35 dlen 512 dflags 0x2) rtsx0: rtsx_xfer_short() - Read xfer: 512 bytes with block size 512 rtsx0: rtsx_send_cmd() rtsx0: Interrupt handler - enabled: 0x3200, status: 0xa001 rtsx0: rtsx_send_cmd() rtsx0: Interrupt handler - enabled: 0x3200, status: 0xa001 rtsx0: rtsx_send_cmd() rtsx0: Interrupt handler - enabled: 0x3200, status: 0xa001 rtsx0: rtsx_mmcbr_release_host() rtsx0: rtsx_mmcbr_acquire_host() rtsx0: rtsx_mmcbr_request(CMD17 arg 0x4 flags 0x35 dlen 512 dflags 0x2) rtsx0: rtsx_xfer_short() - Read xfer: 512 bytes with block size 512 rtsx0: rtsx_send_cmd() rtsx0: Interrupt handler - enabled: 0x3200, status: 0xa001 rtsx0: rtsx_send_cmd() rtsx0: Interrupt handler - enabled: 0x3200, status: 0xa001 rtsx0: rtsx_send_cmd() rtsx0: Interrupt handler - enabled: 0x3200, status: 0xa001 rtsx0: rtsx_mmcbr_release_host() Fatal trap 9: general protection fault while in kernel mode -- 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 204521] [new driver] [request] Port rtsx from OpenBSD to FreeBSD
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204521 --- Comment #68 from Gary Jennejohn --- (In reply to hlh from comment #67) Is the code already in git? What happens if you mount read only? I ask that because the fault is happening in bufwrite. -- 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 246630] stable/11 regression: base.txz reproducibility depends on number of cpu cores
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246630 --- Comment #17 from Fabian Keil --- In the initial report I wrote: > I first saw the issue after rebasing ElectroBSD on > r360524 and confirmed that it still exists in r360986. As it turns out that wasn't entirely correct. While both revisions result in base.txz differences with different cpu cores, the rescue binaries in r360524 are reproducible but the /bin/sh differs. Presumably because of the printf.c issue found by Dimitry. In r360986 the /bin/sh issue is already gone. I'll continue bisecting ... -- 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 204521] [new driver] [request] Port rtsx from OpenBSD to FreeBSD
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204521 --- Comment #69 from h...@restart.be --- (In reply to Gary Jennejohn from comment #68) The code is already in git. I think that a mount read only _should_ work. To be sure see line 1681-1682 to enforce only read requests. Than you must mount read only. -- 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 246750] ZFS: Confusing error message when creating ZFS pool on vdev
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246750 --- Comment #1 from Mateusz Kwiatkowski --- After reboot, pool on zvol cannot be imported even with vfs.zfs.vol.recursive=1. zpool import command hangs indefinitely and ignores ^C. Output of procstat -k of that process: PIDTID COMMTDNAME KSTACK 49700 102119 zpool - mi_switch sleepq_switch _sx_xlock_hard _sx_xlock spa_all_configs zfs_ioc_pool_configs zfsdev_ioctl devfs_ioctl vn_ioctl devfs_ioctl_f kern_ioctl sys_ioctl amd64_syscall fast_syscall_common -- 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"
Réouverture respectant les gestes de sécurité !
___ 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 246750] ZFS: Confusing error message when creating ZFS pool on vdev
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246750 --- Comment #2 from Andriy Gapon --- (In reply to Mateusz Kwiatkowski from comment #1) That kind of a hang is exactly why vfs.zfs.vol.recursive is zero by default. -- 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"
