[Bug 259024] ext2_search_dirblock() loops forever if e2d_reclen is zero

[bugzilla-noreply]

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

Fedor Uporov  changed:

   What|Removed |Added

 Status|New |Closed
 Resolution|--- |FIXED

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 259041] ext2fs can read beyond the end of fs->e2fs_gd[] if a directory contains an invalid i-number

[bugzilla-noreply]

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

Fedor Uporov  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|New |Closed

--- Comment #1 from Fedor Uporov  ---
Fixed in:
https://cgit.FreeBSD.org/src/commit/?id=bb9f1ba4b55c1f566d59cc7c7d1d28dd37715984

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 259105] ext2fs would be more robust if it checked the type of inode 2

[bugzilla-noreply]

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

Fedor Uporov  changed:

   What|Removed |Added

 Status|New |Closed
 Resolution|--- |FIXED

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 260406] pfctl: Cannot allocate memory (after a time)

[bugzilla-noreply]

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

--- Comment #66 from tech-li...@zyxst.net ---
writing to say the pf on the rpi4 is still working without error

% uptime
10:50p.m.  up 12 days,  7:04, 7 users, load averages: 5.11, 4.85, 4.65

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 260958] pfctl: expand_rule: strlcpy

[bugzilla-noreply]

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

--- Comment #2 from Thomas Steen Rasmussen / Tykling  ---
Hello,

Yes, I should have mentioned that, of course.

It isn't a valid config, but normally we would get a message from pfctl with
the line number and a "syntax error" message, so this seemed like something
that should be fixed :)

Thanks!

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 260958] pfctl: expand_rule: strlcpy

[bugzilla-noreply]

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

Kristof Provost  changed:

   What|Removed |Added

 CC||k...@freebsd.org

--- Comment #1 from Kristof Provost  ---
I can reproduce the error, but my current thinking is that this is a
misconfiguration rather than a bug in pf. (Although arguably the error message
could be better).

Note that reply-to expects to be followed by a routehost (' routehost 
= "(" interface-name [ address [ "/" mask-bits ] ] ")"', which is supposed to
be an interface-name and optionally an address.

The pfctl parser code puts the string it finds after route-to in an ifname
field, which is IFNAMSIZ bytes long, so the IPv6 address you provide doesn't
fit and that's what produces the error message.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 260963] vt newcons: mouse paste incorrectly adds newlines

[bugzilla-noreply]

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

Bug ID: 260963
   Summary: vt newcons: mouse paste incorrectly adds newlines
   Product: Base System
   Version: Unspecified
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Many People
  Priority: ---
 Component: kern
  Assignee: b...@freebsd.org
  Reporter: sblachm...@gmail.com

In the freebsd-hackers mailing list there was recently a discussion about bugs
of vt.
At least another guy mentioned one of the most annoying vt bugs, so I think
there is proof am not the only one who uses sc because of things like this
issue:


Problem:
If one marks a line that goes across more than one screen line, vt *always*
inserts a newline at each physical screen line end of the copy source.
This is highly annoying, as it is impossible to copy/paste in one piece, say, a
command line.

Expected result:
The copied text gets pasted without newlines being inserted.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 225341] System locks up due to atkbd_timeout kludge when using /dev/atkbd0 directly

[bugzilla-noreply]

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

Alexander Motin  changed:

   What|Removed |Added

 Status|New |Closed
 Resolution|--- |FIXED

--- Comment #4 from Alexander Motin  ---
We can probably call it "fixed" for now.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 225341] System locks up due to atkbd_timeout kludge when using /dev/atkbd0 directly

[bugzilla-noreply]

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

Alexander Motin  changed:

   What|Removed |Added

 CC||m...@freebsd.org

--- Comment #3 from Alexander Motin  ---
I am not sure how can it cause your symptoms, but I've just disabled the
polling in head:
https://cgit.freebsd.org/src/commit/?id=ce881170088c4c98c036fe561f8ee8413c2e2585

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 260962] sysutils/openzfs fsck.zfs(8) does not detect OpenZFS pool degradation

[bugzilla-noreply]

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

Graham Perrin  changed:

   What|Removed |Added

  Component|bin |Individual Port(s)
Version|CURRENT |Latest
Summary|fsck.zfs(8) does not detect |sysutils/openzfs
   |OpenZFS pool degradation|fsck.zfs(8) does not detect
   ||OpenZFS pool degradation
Product|Base System |Ports & Packages

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 260962] fsck.zfs(8) does not detect OpenZFS pool degradation

[bugzilla-noreply]

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

--- Comment #1 from Graham Perrin  ---


-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 260962] fsck.zfs(8) does not detect OpenZFS pool degradation

[bugzilla-noreply]

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

Bug ID: 260962
   Summary: fsck.zfs(8) does not detect OpenZFS pool degradation
   Product: Base System
   Version: CURRENT
  Hardware: Any
   URL: https://cgit.freebsd.org/src/commit/sys/contrib/openzf
s/cmd/fsck_zfs?id=1603881667360c015f6685131f2f25474fa6
7a72
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: bin
  Assignee: b...@freebsd.org
  Reporter: grahamper...@gmail.com



Maybe not a bug, but what's below is not consistent with the installed manual
page. 



root@mowa219-gjp4-8570p-freebsd:~ # zfs --version
zfs-2.1.99-FreeBSD_gf291fa658
zfs-kmod-2.1.99-FreeBSD_gf291fa658
root@mowa219-gjp4-8570p-freebsd:~ # /usr/local/sbin/fsck.zfs
Transcend/VirtualBox
root@mowa219-gjp4-8570p-freebsd:~ # zpool status -x
  pool: Transcend
 state: ONLINE
status: One or more devices could not be opened.  Sufficient replicas exist for
the pool to continue functioning in a degraded state.
action: Attach the missing device and online it using 'zpool online'.
   see: https://openzfs.github.io/openzfs-docs/msg/ZFS-8000-2Q
  scan: scrub repaired 0B in 01:32:30 with 0 errors on Sun Dec 12 16:25:35 2021
config:

NAME   STATE READ WRITE CKSUM
Transcend  ONLINE   0 0 0
  gpt/TranscendONLINE   0 0 0
cache
  gpt/cache-transcend  UNAVAIL  0 0 0  cannot open

errors: No known data errors
root@mowa219-gjp4-8570p-freebsd:~ # date ; uname -aKU
Wed Jan  5 20:36:28 GMT 2022
FreeBSD mowa219-gjp4-8570p-freebsd 14.0-CURRENT FreeBSD 14.0-CURRENT #118
main-n251923-4bae154fe8c: Sat Dec 25 08:03:37 GMT 2021
root@mowa219-gjp4-8570p-freebsd:/usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG
 amd64 1400045 1400045
root@mowa219-gjp4-8570p-freebsd:~ # 



>Fromman 8 fsck.zfs

> … checks the status of a dataset's container pool.  It is installed 
> by OpenZFS because some Linux distributions expect a fsck helper for 
> all filesystems. …

> … if the dataset is in a degraded pool, then fsck.zfs will return 
> exit code 4 to indicate an uncorrected filesystem error. …

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 260793] 'swapon -a' can crash the system

[bugzilla-noreply]

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

Mark Johnston  changed:

   What|Removed |Added

 Status|New |Open

--- Comment #3 from Mark Johnston  ---
(In reply to Peter Much from comment #2)
I think swapoff should handle this scenario.  swapon -a already silently
ignores EBUSY from swapon(), which occurs when the file is already a swap
device, so it shouldn't also discard blocks in a file that is already a swap
device.  Normally the kernel wouldn't allow this, but we have:
https://github.com/freebsd/freebsd-src/blob/main/sys/vm/swap_pager.c#L3006

Perhaps swapon's swapon_trim() can check to see if a file at the path is
already in use as a swap device.  I don't think we have a good way to do that
though.  For devfs files we can compare the device number with the ones
available from the vm.swap_info sysctl, but this won't work for regular files,
I think.

Perhaps we can extend the swapon() syscall to let the kernel perform the
trimming.  Or add an IS_THIS_A_SWAP_DEVICE ioctl that swapon can check before
trying to erase the file blocks.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 260257] CAM_IO_STATS does not track MEDIUM ERRORs

[bugzilla-noreply]

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

Robert Wing  changed:

   What|Removed |Added

 CC||r...@freebsd.org

--- Comment #7 from Robert Wing  ---
Wonder if the counter should be bumped when CAM_SCSI_STATUS_ERROR?

something for context:

diff --git a/sys/cam/scsi/scsi_da.c b/sys/cam/scsi/scsi_da.c
index df8791e4b23e..2d78c00dbb60 100644
--- a/sys/cam/scsi/scsi_da.c
+++ b/sys/cam/scsi/scsi_da.c
@@ -5994,20 +5994,21 @@ daerror(union ccb *ccb, u_int32_t cam_flags, u_int32_t
sense_flags)
 #ifdef CAM_IO_STATS
switch (ccb->ccb_h.status & CAM_STATUS_MASK) {
case CAM_CMD_TIMEOUT:
softc->timeouts++;
break;
case CAM_REQ_ABORTED:
case CAM_REQ_CMP_ERR:
case CAM_REQ_TERMIO:
case CAM_UNREC_HBA_ERROR:
case CAM_DATA_RUN_ERR:
+   case CAM_SCSI_STATUS_ERROR:
softc->errors++;
break;
default:
break;
}
 #endif

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 260793] 'swapon -a' can crash the system

[bugzilla-noreply]

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

--- Comment #2 from Peter Much  ---
 @markj
You're great. That explains it.

So, indeed, one shouldn't re-run "swapon -a" when trimonce is set. 
Or, maybe, we could catch the issue?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 260896] The 14-CURRENT system hangs if kern.vt.splash_cpu is set to 1 in loader.conf

[bugzilla-noreply]

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

--- Comment #2 from Oleg  ---
I just compiled the latest kernel from the main branch and the problem is still
there. If I boot into the single-user mode, then I am able to login, but the
system will become fully unresponsive a few seconds later (I said "a few
minutes later" in my first post, but that was incorrect).
As far as I know, the single-user mode ignores /etc/rc.conf completely, so
stuff such as i915kms.ko never gets loaded.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 260793] 'swapon -a' can crash the system

[bugzilla-noreply]

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

Mark Johnston  changed:

   What|Removed |Added

 CC||ma...@freebsd.org

--- Comment #1 from Mark Johnston  ---
Do you have "trimonce" in your fstab options by any chance?  Can you show the
full fstab entries for the swap devices?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 260958] pfctl: expand_rule: strlcpy

[bugzilla-noreply]

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

Bug ID: 260958
   Summary: pfctl: expand_rule: strlcpy
   Product: Base System
   Version: 13.0-STABLE
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Many People
  Priority: ---
 Component: kern
  Assignee: b...@freebsd.org
  Reporter: tho...@gibfest.dk

Hello :)

A fun bug where a long-ish ipv6 address used in a reply-to in a pf ruleset
results in pfctl being unable to parse the ruleset.

The issue boiled down to a one line ruleset, one with a 16 byte address (which
fails) and the other with a 15 byte address (which works).

[tykling@nuc1 ~]$ cat trigger 
pass in reply-to { 2001:DB8:1234::5 }
[tykling@nuc1 ~]$ pfctl -nf trigger 
pfctl: expand_rule: strlcpy
[tykling@nuc1 ~]$ echo $?
1
[tykling@nuc1 ~]$ cat notrigger 
pass in reply-to { 2001:DB8:1234:: }
[tykling@nuc1 ~]$ pfctl -nf notrigger 
[tykling@nuc1 ~]$ echo $?
0
[tykling@nuc1 ~]$ uname -a
FreeBSD nuc1.servers.bornhack.org 13.0-STABLE FreeBSD 13.0-STABLE #1
stable/13-d208638c5: Wed Jan  5 13:32:08 UTC 2022
r...@nuc1.servers.bornhack.org:/usr/obj/usr/src/amd64.amd64/sys/GENERIC  amd64
[tykling@nuc1 ~]$ 

We first observed this on 12.2-STABLE a while back but I didn't get around to
reporting it until now, so I've just confirmed it is still an issue on a fresh
13-STABLE.

Thanks! :)

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 260868] possible i386 regression after ce35a3bc852d25cb989bc1f3dc4ddb723d7d5117

[bugzilla-noreply]

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

Mark Johnston  changed:

   What|Removed |Added

 Status|Open|In Progress
   Assignee|b...@freebsd.org|ma...@freebsd.org

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 260896] The 14-CURRENT system hangs if kern.vt.splash_cpu is set to 1 in loader.conf

[bugzilla-noreply]

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

Mark Johnston  changed:

   What|Removed |Added

 CC||ma...@freebsd.org

--- Comment #1 from Mark Johnston  ---
I can't reproduce any problems like this on my laptop running a fresh kernel.

Where during boot does the hang occur?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 260406] pfctl: Cannot allocate memory (after a time)

[bugzilla-noreply]

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

Kajetan Staszkiewicz  changed:

   What|Removed |Added

 CC||veg...@tuxpowered.net

--- Comment #65 from Kajetan Staszkiewicz  ---
I'm observing the same thing happening on amd64. In the beginning I thought it
might be due to my own patches on pf. Then I thought it only happens on systems
which are high on inactive memory (my systems behave differently regarding
inactive, some have lot of free memory, some bloat the inactive memory, no idea
why) which gave me the idea that maybe inactive memory can't be freed when
allocating memory with M_NOWAIT. However today I finally got the same issue on
a system running a nonpatched 13.0-RELEASE GENERIC kernel on a system without
bloated inactive memory.

[17:02:34] al-router01 ~/ # vmstat -z | grep pf
pf mtags:48,  0,   0,2520,12630497,   0,   0,   0
pf tags:104,  0,   0,   0,   0,   0,   0,   0
pf states:  296, 400,7038,   39177,3739030613,   0,   0,  
0
pf state keys:   88,  0,7038,   85008,3739030613,   0,   0,   0
pf source nodes:136, 40,   0,   0,   0,   0,   0,   0
pf table entry counters: 64,  0,   0,   0,   0,   0,   0,  
0
pf table entries:   160, 100,  320952,  310548,259049528,180913,   0,  
0
pf frags:   248,  0,   0,  96,10783117,   0,   0,   0
pf frag entries: 40,  32000,   0, 606,50033469,   0,   0,   0
pf state scrubs: 40,  0,   0,   0,   0,   0,   0,   0

So there is a limit of 1M entries, 320k are used, 310k are free. When I reload
pf.conf, I need double the entries, yes? So the new pf.conf won't load. But
where is the missing 370k entries?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 260955] pkg 1.17: keywords "preunexec" and "postexec" no longer recognized

[bugzilla-noreply]

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

Bug ID: 260955
   Summary: pkg 1.17: keywords "preunexec" and "postexec" no
longer recognized
   Product: Base System
   Version: Unspecified
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Some People
  Priority: ---
 Component: kern
  Assignee: b...@freebsd.org
  Reporter: sblachm...@gmail.com

There seems to be a problem after there were removed some keywords with pkg
1.17.

Porters handbook does not mention keywords "preunexec" and "postexec" being
either deprecated or removed.
See https://docs.freebsd.org/en/books/porters-handbook/plist/#plist-keywords
(cf section 8.6.13.2.)

But these keywords seem to no longer work.

Question now is: is it a problem with pkg, the handbook or apache24 pkg
scripts?

Because the latter fails to install when built from ports, with pkg-static
complaining of these keywords being "unknown".
Please see https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260928 for further
details.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 260954] waiting for runnimg MySQL

[bugzilla-noreply]

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

--- Comment #7 from Aleks  ---
In a naive attempt, I just added the hw.pagesize=... to my /etc/sysctl config
file, without any success. Now, when I run pagesize I get my sad 4096 bytes
value:

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 260954] waiting for runnimg MySQL

[bugzilla-noreply]

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

--- Comment #6 from Aleks  ---
./mysql-server status
mysql is running as pid 2047.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 260954] waiting for runnimg MySQL

[bugzilla-noreply]

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

--- Comment #5 from Aleks  ---
sysctl hw.pagesize=8192
sysctl: oid 'hw.pagesize' is read only

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 260954] waiting for runnimg MySQL

[bugzilla-noreply]

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

--- Comment #4 from Aleks  ---
sysctl hw.pagesize 
hw.pagesize: 4096

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 260954] waiting for runnimg MySQL

[bugzilla-noreply]

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

--- Comment #3 from Aleks  ---
error

[ERROR] InnoDB: The Auto-extending innodb_system data file
'/var/db/mysql/ibdata1' is of a different size 4864 pages (rounded down to MB)
than specified in the .cnf file: initial 8192 pages, max 0

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 260954] waiting for runnimg MySQL

[bugzilla-noreply]

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

--- Comment #2 from Aleks  ---
https://forums.freebsd.org/threads/ibdata1-page-size-diffrent-after-upgrading-mysql-5-6-to-5-7.72289/

my.cnf="

# For advice on how to change settings please see
# http://dev.mysql.com/doc/refman/5.6/en/server-configuration-defaults.html
# *** DO NOT EDIT THIS FILE. It's a template which will be copied to the
# *** default location during install, and will be replaced if you
# *** upgrade to a newer version of MySQL.

[mysqld]

# Remove leading # and set to the amount of RAM for the most important data
# cache in MySQL. Start at 70% of total RAM for dedicated server, else 10%.
# innodb_buffer_pool_size = 128M

# Remove leading # to turn on a very important data integrity option: logging
# changes to the binary log between backups.
# log_bin

# These are commonly set, remove the # and set as required.
# basedir = .
# datadir = .
# port = .
# server_id = .
# socket = .

# Remove leading # to set options mainly useful for reporting servers.
# The server defaults are faster for transactions and fast SELECTs.
# Adjust sizes as needed, experiment to find the optimal values.
# join_buffer_size = 128M
# sort_buffer_size = 2M
# read_rnd_buffer_size = 2M.

sql_mode=NO_ENGINE_SUBSTITUTION,STRICT_TRANS_TABLES.


"

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 260954] waiting for runnimg MySQL

[bugzilla-noreply]

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

--- Comment #1 from Aleks  ---
Update mysql56-server mysql56-client

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 260954] waiting for runnimg MySQL

[bugzilla-noreply]

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

Bug ID: 260954
   Summary: waiting for runnimg MySQL
   Product: Base System
   Version: 13.0-STABLE
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: bin
  Assignee: b...@freebsd.org
  Reporter: z462v...@mail.lviv.ua

reboot

On the screen
waiting for runnimg MySQL
waiting for runnimg MySQL
waiting for runnimg MySQL
waiting for runnimg MySQL
waiting for runnimg MySQL
...
.
waiting for runnimg MySQL

Then do not load
Control+C 

Then loaded
13.0-STABLE FreeBSD 13.0-STABLE #1 stable/13-17ef4736e:
/usr/obj/usr/src/amd64.amd64/sys/GENERIC  amd64

pkg install mysql57-server mysql57-client

Mysql  Ver 14.14 Distrib 5.7.36, for FreeBSD13.0 (amd64) using  EditLine
wrapper

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 260952] Add usbids for EDIMAX EW-7811UN V2

[bugzilla-noreply]

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

Tilman Keskinoz  changed:

   What|Removed |Added

   Keywords||easy
  Component|kern|usb
   Assignee|b...@freebsd.org|u...@freebsd.org

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 260952] Add usbids for EDIMAX EW-7811UN V2

[bugzilla-noreply]

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

Bug ID: 260952
   Summary: Add usbids for EDIMAX EW-7811UN V2
   Product: Base System
   Version: CURRENT
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Some People
  Priority: ---
 Component: kern
  Assignee: b...@freebsd.org
  Reporter: ar...@freebsd.org

Created attachment 230732
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=230732=edit
usbids for 7811UN V2

The EW-7811UN V2 uses a different chipset than the V1.

First report
https://forums.freebsd.org/threads/cannot-detect-wifi-edimax-ew7811un-v2.78349/

This Bugreport was submitted via the EW-7811UN V2 dongle so it works.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 260949] fsck(8): Fix typo

[bugzilla-noreply]

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

Kubilay Kocak  changed:

   What|Removed |Added

 Status|New |Open
   See Also||https://bugs.freebsd.org/bu
   ||gzilla/show_bug.cgi?id=1882
   ||14
   Keywords||easy, needs-patch
  Flags||maintainer-feedback?(trhode
   ||s...@freebsd.org),
   ||mfc-stable13?,
   ||mfc-stable12?
Summary|Minor corrections to the|fsck(8): Fix typo
   |manual page for fsck(8) |
 CC||d...@freebsd.org,
   ||trho...@freebsd.org
   Assignee|b...@freebsd.org|d...@freebsd.org

-- 
You are receiving this mail because:
You are the assignee for the bug.