[Bug 254341] igb hung every 5-20 hours. ifconfig down+up solves the problem for next N hours

2021-03-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254341

Li-Wen Hsu  changed:

   What|Removed |Added

 CC||e...@freebsd.org
   Keywords||IntelNetworking

-- 
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 254354] net/rsync --crtimes, -N: preserve creation/birth time is not supported

2021-03-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254354

Li-Wen Hsu  changed:

   What|Removed |Added

   Assignee|b...@freebsd.org|rodr...@freebsd.org
Summary|rsync --crtimes, -N:|net/rsync --crtimes, -N:
   |preserve creation/birth |preserve creation/birth
   |time is not supported   |time is not supported
 CC||lw...@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 252236] atp(4): Need EVDEV support for modern input stack

2021-03-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252236

Vladimir Kondratyev  changed:

   What|Removed |Added

 Attachment #223229|0   |1
is obsolete||

--- Comment #32 from Vladimir Kondratyev  ---
Created attachment 223347
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=223347=edit
wsp_evdev_support.patch

Non-tested version with hidbus attachment (Supports only WSP9 and may be WSP8
touchpads). Previous usbus-based variant is included too.

-- 
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 254341] igb hung every 5-20 hours. ifconfig down+up solves the problem for next N hours

2021-03-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254341

--- Comment #4 from Vladislav Shabanov  ---
$ ifconfig -a 
igb0: flags=...
   .
igb1: flags=
   .
lo0: flags=
   .
pflog0: flags=0
   .

I know that em and igb now are merged together. But the system names this
device igb0, igb1, ...
Technically it's I350.
I use this 'igb' in bug report title because other users with this problem
probably will search by this word.

$ pciconf -lBbceVv | grep igb0
igb0@pci0:4:0:0:class=0x02 card=0x152115d9 chip=0x15218086 rev=0x01
hdr=0x00
vendor = 'Intel Corporation'
device = 'I350 Gigabit Network Connection'
class  = network
subclass   = ethernet
bar   [10] = type Memory, range 32, base 0xfb12, size 131072, enabled
bar   [18] = type I/O Port, range 32, base 0xe020, size 32, enabled
bar   [1c] = type Memory, range 32, base 0xfb144000, size 16384, enabled
cap 01[40] = powerspec 3  supports D0 D3  current D0
cap 05[50] = MSI supports 1 message, 64 bit, vector masks enabled with 1
message
cap 11[70] = MSI-X supports 10 messages
 Table in map 0x1c[0x0], PBA in map 0x1c[0x2000]
cap 10[a0] = PCI-Express 2 endpoint max data 256(512) FLR NS
 link x4(x4) speed 5.0(5.0) ASPM disabled(L0s/L1)
ecap 0001[100] = AER 2 0 fatal 0 non-fatal 1 corrected
ecap 0003[140] = Serial 1 ac1f6b028ac4
ecap 000e[150] = ARI 1
ecap 0010[160] = SR-IOV 1 IOV disabled, Memory Space disabled, ARI disabled
 0 VFs configured out of 8 supported
 First VF RID Offset 0x0180, VF RID Stride 0x0004
 VF Device ID 0x1520
 Page Sizes: 4096 (enabled), 8192, 65536, 262144, 1048576,
4194304
ecap 0017[1a0] = TPH Requester 1
ecap 0018[1c0] = LTR 1
ecap 000d[1d0] = ACS 1

-- 
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 254354] rsync --crtimes, -N: preserve creation/birth time is not supported

2021-03-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254354

Bug ID: 254354
   Summary: rsync --crtimes, -N: preserve creation/birth time is
not supported
   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: fabiane49...@protonmail.com

Here you can see that FreeBSD generally supports crtime/btime see the stat
command.


stat -f "Access (atime): %Sa%nModify (mtime): %Sm%nChange (ctime): %Sc%nBirth 
(crtime/btime): %SB" /video.mkv

Access (atime): Nov 22 16:07:46 2018 
Modify (mtime): Nov 22 16:07:46 2018
Change (ctime): Nov 22 16:07:46 2018
Birth  (crtime/btime): Nov 01 01:19:02 2016



If the user uses rsync (3.2.3) to preserve the crtimes with --crtimes or -N 
for directories and files, it does not work. It says in the terminal that it is
not supported.

-- 
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 254349] cannot set bootfs on pool after removing a vdev

2021-03-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254349

Eric van Gyzen  changed:

   What|Removed |Added

 CC||m...@freebsd.org,
   ||m...@freebsd.org,
   ||mm...@freebsd.org
   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 254349] cannot set bootfs on pool after removing a vdev

2021-03-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254349

Bug ID: 254349
   Summary: cannot set bootfs on pool after removing a vdev
   Product: Base System
   Version: CURRENT
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Some People
  Priority: ---
 Component: kern
  Assignee: b...@freebsd.org
  Reporter: vangy...@freebsd.org

Created attachment 223341
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=223341=edit
unit test

After I removed a vdev from my root pool, I can no longer set the bootfs
property.  This makes Boot Environments unusable.

I'm attaching a unit test script to demonstrate the problem.  My output is:



# ./zfs_set_bootfs_after_vdev_removal.sh 
cannot set property for 'test_remove': operation not supported on this type of
pool
FAIL
NAME PROPERTY  VALUE  SOURCE
test_remove  bootfstest_remove/root0  local
  pool: test_remove
 state: ONLINE
remove: Removal of vdev 1 copied 276K in 0h0m, completed on Tue Mar 16 10:18:08
2021
216 memory used for removed device mappings
config:

NAME  STATE READ WRITE CKSUM
test_remove   ONLINE   0 0 0
  md0 ONLINE   0 0 0

errors: No known data errors

-- 
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 254343] 13.0-RC2: adding a vtnet (VirtIO network) interface to bridge fails

2021-03-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254343

Kristof Provost  changed:

   What|Removed |Added

 CC||k...@freebsd.org

--- Comment #1 from Kristof Provost  ---
I've had a brief look.

Adding the interface to the bridge fails because it can't enable promiscuous
mode on it.
It's not clear to me if setting promiscuous mode is supposed to work on vtnet
interfaces without CtrlRxMode.
Either way, it looks like the interface flag handling is somewhat buggy as
well, because vtnet interfaces which have been brought up cannot be added, but
those who have not can be.

tl;dr: Needs to be investigated by someone familiar with if_vtnet.

-- 
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 254341] igb hung every 5-20 hours. ifconfig down+up solves the problem for next N hours

2021-03-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254341

VVD  changed:

   What|Removed |Added

 CC||v...@unislabs.com

--- Comment #3 from VVD  ---
Where did you get igb in 12.2?

HISTORY
 The em device driver first appeared in FreeBSD 4.4.  em was merged with
 the igb device driver and converted to the iflib framework in
 FreeBSD 12.0.

-- 
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 254343] 13.0-RC2: adding a vtnet (VirtIO network) interface to bridge fails

2021-03-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254343

Felix Palmen  changed:

   What|Removed |Added

   Severity|Affects Only Me |Affects Many People

-- 
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 254343] 13.0-RC2: adding a vtnet (VirtIO network) interface to bridge fails

2021-03-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254343

Bug ID: 254343
   Summary: 13.0-RC2: adding a vtnet (VirtIO network) interface to
bridge fails
   Product: Base System
   Version: 13.0-STABLE
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: misc
  Assignee: b...@freebsd.org
  Reporter: fe...@palmen-it.de

On a freshly installed 13.0-RC2 in bhyve:

root@test:~ # ifconfig bridge0 create
root@test:~ # ifconfig bridge0 addm vtnet0
ifconfig: BRDGADD vtnet0: Operation not supported

-- 
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 254341] igb hung every 5-20 hours. ifconfig down+up solves the problem for next N hours

2021-03-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254341

--- Comment #2 from Vladislav Shabanov  ---
Created attachment 223332
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=223332=edit
watchdog dump right after the hung (before ifconfig down/up)

-- 
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 254341] igb hung every 5-20 hours. ifconfig down+up solves the problem for next N hours

2021-03-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254341

--- Comment #1 from Vladislav Shabanov  ---
Created attachment 223331
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=223331=edit
watchdog dump just before the network hung

-- 
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 254341] igb hung every 5-20 hours. ifconfig down+up solves the problem for next N hours

2021-03-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254341

Bug ID: 254341
   Summary: igb hung every 5-20 hours. ifconfig down+up solves the
problem for next N hours
   Product: Base System
   Version: 12.2-RELEASE
  Hardware: arm64
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: kern
  Assignee: b...@freebsd.org
  Reporter: vlad.shaba...@gmail.com

Created attachment 223330
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=223330=edit
full dmesg.boot

I have problem with FreeBSD 12.2p1 The problem started on FreeBSD 12.0 and
persists till now.

The network hung just after the boot. Ifconfig down+up solves the problem for
next 5-20 hours. I don’t know how to force NIC to hung immediately. Just do
ifconfig up/down and wait for next N hours.

MBoard: SuperMicro X10SRI-F
NIC:  port 0xe020-0xe03f mem
0xfb12-0xfb13,0xfb144000-0xfb147fff irq 43 at device 0.0 on pci5
firewall: pf 
There is no vlan, only jails working on 10.0.0.1/16

Now I use simple watchdog script staring every minute. The script pings the
gateway and do ifconfig down/up on error.
The script dumps these values every minute:
/sbin/pfctl -si > /root/WATCHDOG/failure.txt
/usr/bin/netstat -m >> /root/WATCHDOG/failure.txt
/sbin/sysctl -a | /usr/bin/grep dev.igb >> /root/WATCHDOG/failure.txt

I have two files: one before the hung, the second one just after the hung. Hope
that some values inside can help.


———
- from dmesg.boot
igb0:  port 0xe020-0xe03f mem
0xfb12-0xfb13,0xfb144000-0xfb147fff 
igb0: Using 1024 TX descriptors and 1024 RX descriptors
igb0: Using an MSI interrupt
igb0: Ethernet address: ac:1f:6b:02:8a:c4
igb0: netmap queues/slots: TX 1/1024, RX 1/1024

———
$ ifconfig igb0
igb0: flags=8843 metric 0 mtu 1500
   
options=e507bb
ether ac:1f:6b:02:8a:c4
inet IP-ADDR netmask 0xff00 broadcast IP-ADDR
media: Ethernet 100baseTX 
status: active
nd6 options=29

———
- /etc/rc.conf:
-
zfs_enable="YES"
sshd_enable="YES"
ntpd_enable="YES"
powerd_enable="YES"
local_unbound_enable="YES"
hostname="..."
ifconfig_igb0="inet IP-ADDR netmask 255.255.255.0"
defaultrouter="IP-ADDR"
ifconfig_lo0_alias0="inet 10.0.0.1 netmask 0x"
pf_enable="YES"
pflog_enable="YES"

-- 
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 203349] [META] FreeBSD Foundation sponsored project dependencies

2021-03-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203349
Bug 203349 depends on bug 223917, which changed state.

Bug 223917 Summary: arm64: serial console unresponsive after debug.kdb.enter=1 
then ddb 'c'ontinue
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=223917

   What|Removed |Added

 Status|In Progress |Closed
 Resolution|--- |FIXED

-- 
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 231027] [META] FreeBSD-Foundation sponsored issues for FreeBSD 13-CURRENT

2021-03-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231027
Bug 231027 depends on bug 223917, which changed state.

Bug 223917 Summary: arm64: serial console unresponsive after debug.kdb.enter=1 
then ddb 'c'ontinue
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=223917

   What|Removed |Added

 Status|In Progress |Closed
 Resolution|--- |FIXED

-- 
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 254338] Typo in geom_uzip(4) manpage

2021-03-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254338

Guangyuan Yang  changed:

   What|Removed |Added

   Assignee|b...@freebsd.org|y...@freebsd.org
 CC||y...@freebsd.org
 Status|New |Open

-- 
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 254338] Typo in geom_uzip(4) manpage

2021-03-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254338

Bug ID: 254338
   Summary: Typo in geom_uzip(4) manpage
   Product: Documentation
   Version: Latest
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: Manual Pages
  Assignee: b...@freebsd.org
  Reporter: c...@submonkey.net
CC: d...@freebsd.org

Created attachment 223326
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=223326=edit
patch

"at the expense of a some CPU time"

-- 
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 254318] [panic] when a specific sequence of read requests is issued to a geom_uzip device the kernel panics

2021-03-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254318

Mark Linimon  changed:

   What|Removed |Added

   Assignee|b...@freebsd.org|g...@freebsd.org
   Keywords||panic

-- 
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 253797] i915 drm error after update to FreeBSD 13.0-BETA3, BETA4

2021-03-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253797

Igor Osminin  changed:

   What|Removed |Added

   See Also||https://bugs.freebsd.org/bu
   ||gzilla/show_bug.cgi?id=2538
   ||01

-- 
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 253797] i915 drm error after update to FreeBSD 13.0-BETA3, BETA4

2021-03-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253797

Igor Osminin  changed:

   What|Removed |Added

   Severity|Affects Only Me |Affects Some People

-- 
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 254333] sysctl net.inet.tcp.hostcache.list hangs

2021-03-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254333

Mark Linimon  changed:

   What|Removed |Added

   Assignee|b...@freebsd.org|n...@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 254333] sysctl net.inet.tcp.hostcache.list hangs

2021-03-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254333

Bug ID: 254333
   Summary: sysctl net.inet.tcp.hostcache.list hangs
   Product: Base System
   Version: 11.4-STABLE
  Hardware: amd64
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: kern
  Assignee: b...@freebsd.org
  Reporter: maxim.shalomik...@kaspersky.com

I'm running 'sysctl net.inet.tcp.hostcache.list' from operator's crontab every
5 minutes for gathering tcp statistics. 

After 3 or 4 months of work sysctl hangs. Kill (and kill -9) doesn't help.
Running one more "sysctl net.inet.tcp.hostcache.list" command gives the same
result - it hangs forever with no output. Other "sysctl SOMETHING" commands
works fine. 

# ps ax| grep sysctl
operator 7870.0  0.04236  1004  -  DTue16 2:42.96
/sbin/sysctl net.inet.tcp.hostcache.list
operator19080.0  0.04236  1004  -  DMon02 2:45.74
/sbin/sysctl net.inet.tcp.hostcache.list
operator23580.0  0.04236  1004  -  DWed10 1:33.93
/sbin/sysctl net.inet.tcp.hostcache.list
operator32700.0  0.04236  1004  -  DSun16 2:47.22
/sbin/sysctl net.inet.tcp.hostcache.list


After rebot 'sysctl net.inet.tcp.hostcache.list' works again as expected for
another 3 or 4 months.

The issue is reproducing on about 60 hevy loaded http(s) servers with different
hw specs.

-- 
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 140156] [linux] cdparanoia fails to read drive data

2021-03-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=140156

Dmitry Chagin  changed:

   What|Removed |Added

   Assignee|b...@freebsd.org|emulat...@freebsd.org
 CC||dcha...@freebsd.org

--- Comment #4 from Dmitry Chagin  ---
Over to maintainer(s).

-- 
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 179488] wrong encoding of error messages in tcsh(1)

2021-03-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=179488

Dmitry Chagin  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 CC||dcha...@freebsd.org
 Status|Open|Closed

--- Comment #2 from Dmitry Chagin  ---
Fixed by ume@ by r295204 (e4b59b10f8aebe45f87939a9703638f4130908c0)

-- 
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"