[Bug 259640] [sound] Sound not work on some Lenovo notebook

2021-11-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=259640

Bug ID: 259640
   Summary: [sound] Sound not work on some Lenovo notebook
   Product: Base System
   Version: Unspecified
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Some People
  Priority: ---
 Component: kern
  Assignee: b...@freebsd.org
  Reporter: dmitryluhtio...@gmail.com

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

Fix sound output in Lenovo Ideapad 330-15 and Lenovo ThinkPad X230

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


[Bug 259505] Bug in zfs receive - Mountpoint not changed

2021-11-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=259505

--- Comment #8 from ERM Consulting  ---
OK, solved!
I was not aware that we can switch of the "inherit mountpoint" functionality.
We used your recommended command on the old dataset:

   zfs inherit mountpoint DataStorage8/datasetVM

Then send->received the dataset to the new pool and now we have the correct
mountpoint:

storage8: ~# zfs list
NAME USED  AVAIL  REFER  MOUNTPOINT
zDataStorage8   6.67T  7.24T   139K  /zDataStorage8
zDataStorage8/datasetShares 2.16T  7.24T  2.11T 
/zDataStorage8/datasetShares
zDataStorage8/datasetVM 4.51T  7.24T  3.86T 
/zDataStorage8/datasetVM
zDataStorage8Backup26.31T  9.54T   104K  /zDataStorage8Backup2
zDataStorage8Backup2/datasetShares  2.15T  9.54T  2.09T 
/zDataStorage8Backup2/datasetShares
zDataStorage8Backup2/datasetVM  4.17T  9.54T  3.71T 
/zDataStorage8Backup2/datasetVM

Many thanks for your help!
No Bug, lag on knowledge!

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


[Bug 259642] CLOCK_* seems to default to CLOCK_*_PRECISE instead of CLOCK_*_FAST

2021-11-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=259642

Bug ID: 259642
   Summary: CLOCK_* seems to default to CLOCK_*_PRECISE instead of
CLOCK_*_FAST
   Product: Base System
   Version: CURRENT
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: bin
  Assignee: b...@freebsd.org
  Reporter: 0...@freebsd.org

The clock_gettime(2) manual page [1] documents that:

>The clock IDs CLOCK_REALTIME_FAST, CLOCK_MONOTONIC_FAST,
>CLOCK_UPTIME_FAST are analogs of corresponding IDs without _FAST suffix
>but do not perform a full time counter query, so their accuracy is one
>timer tick.

However, in the source code of kern_clock_gettime() in sys/kern/kern_time.c
[2], the clock IDs without a suffix default to PRECISE instead of FAST.

Is it the manual page or the source code that needs fixing?

[1]:
https://www.freebsd.org/cgi/man.cgi?query=clock_gettime&manpath=FreeBSD+13.0-RELEASE+and+Ports
[2]:
https://cgit.freebsd.org/src/tree/sys/kern/kern_time.c?h=releng%2F13.0#n323

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


[Bug 259642] CLOCK_* seems to default to CLOCK_*_PRECISE instead of CLOCK_*_FAST

2021-11-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=259642

Yuri  changed:

   What|Removed |Added

 CC||y...@aetern.org

--- Comment #1 from Yuri  ---
I am not sure what you are really asking, the excerpt you quoted does not say
anything about _FAST versions being default, and rather just describes the
difference between the _FAST and non-_FAST IDs.

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


[Bug 259642] CLOCK_* seems to default to CLOCK_*_PRECISE instead of CLOCK_*_FAST

2021-11-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=259642

--- Comment #2 from Mateusz Piotrowski <0...@freebsd.org> ---
(In reply to Yuri from comment #1)

Hmm, the way I read the manual page is that, e.g., CLOCK_REALTIME is just
CLOCK_REALTIME_FAST. However, the source code suggests that CLOCK_REALTIME is
not CLOCK_REALTIME_FAST but CLOCK_REALTIME_PRECISE instead.

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


[Bug 259642] CLOCK_* seems to default to CLOCK_*_PRECISE instead of CLOCK_*_FAST

2021-11-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=259642

--- Comment #3 from Yuri  ---
(In reply to Mateusz Piotrowski from comment #2)
It says that e.g. CLOCK_REALTIME_FAST is the *analog* of CLOCK_REALTIME, i.e.
both return wall clock, but CLOCK_REALTIME_FAST does it in less precise way.

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


[Bug 259230] Touching the touchpad on a frame.work laptop causes reboot or poweroff

2021-11-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=259230

--- Comment #9 from Vladimir Kondratyev  ---
You may try my hacked iichid driver: https://github.com/wulf7/iichid_gpio
But TigerLake is not tested yet.

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


[Bug 259642] CLOCK_* seems to default to CLOCK_*_PRECISE instead of CLOCK_*_FAST

2021-11-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=259642

Mateusz Piotrowski <0...@freebsd.org> changed:

   What|Removed |Added

 Status|New |Open
   Assignee|b...@freebsd.org|0...@freebsd.org

--- Comment #4 from Mateusz Piotrowski <0...@freebsd.org> ---
(In reply to Yuri from comment #3)
I see, I misunderstood that part.

So before I close this ticket, do you think we should mention that
CLOCK_REALTIME is currently CLOCK_REALTIME_PRECISE implemented as?

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


[Bug 259644] vxlan(4): interface does not come up when the local tunnel address appears

2021-11-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=259644

Bug ID: 259644
   Summary: vxlan(4): interface does not come up when the local
tunnel address appears
   Product: Base System
   Version: CURRENT
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: kern
  Assignee: b...@freebsd.org
  Reporter: zlei.hu...@gmail.com

Also when the local tunnel address disappears the interface is not brought
down.

Environment: FreeBSD-12.2-RELEASE-p7, FreeBSD-13.0-RELEASE-p4 and CURRENT/14.

Steps to repeat:

Scene 1:
# ifconfig vxlan0 create vxlanid 108 vxlanlocal 192.168.100.1 vxlanremote
192.168.100.2
# ifconfig vxlan0 inet 192.0.2.2/24
# ifconfig tap0 create inet 192.168.100.1/24

The vxlan0 keep not "RUNNING", can be verify by:
# ifconfig vxlan0 | grep RUNNING


Scene 2:
# ifconfig tap0 create inet 192.168.100.1/24
# ifconfig vxlan0 create vxlanid 108 vxlanlocal 192.168.100.1 vxlanremote
192.168.100.2
# ifconfig vxlan0 inet 192.0.2.2/24
# ifconfig vxlan0 | grep RUNNING
vxlan0: flags=8843 metric 0 mtu 1450

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


[Bug 259644] vxlan(4): interface does not come up when the local tunnel address appears

2021-11-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=259644

Zhenlei Huang  changed:

   What|Removed |Added

 CC||k...@freebsd.org

--- Comment #1 from Zhenlei Huang  ---
This is might be a design defect.
I checked GIF implementation and found that Andrey V. Elsukov has done it
right.

See:
https://cgit.freebsd.org/src/commit/sys/netinet/in_gif.c?id=009d82ee0fefdc797f55d25a50d3b6ebe61d56e4

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


[Bug 259505] Bug in zfs receive - Mountpoint not changed

2021-11-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=259505

Andriy Gapon  changed:

   What|Removed |Added

 Resolution|--- |Works As Intended
 Status|New |Closed

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


[Bug 259645] crash after updating to FreeBSD 13.0 p5

2021-11-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=259645

Bug ID: 259645
   Summary: crash after updating to FreeBSD 13.0 p5
   Product: Base System
   Version: 13.0-STABLE
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: kern
  Assignee: b...@freebsd.org
  Reporter: doc...@doctor.nl2k.ab.ca

Created attachment 229267
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=229267&action=edit
crash text

Attached are the details

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


[Bug 252532] ifconfig incorrectly displays stp roles

2021-11-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252532

Ed Maste  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|New |Closed
 CC||ema...@freebsd.org
   Assignee|b...@freebsd.org|k...@freebsd.org

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


[Bug 259636] multiple components: Change "Take Affect" to "Take Effect"

2021-11-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=259636

John Bentley  changed:

   What|Removed |Added

 Attachment #229257|0   |1
is obsolete||

--- Comment #2 from John Bentley  ---
Created attachment 229275
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=229275&action=edit
diff with edits to contrib files removed

Hi Kubilay,

Thanks for responding!

Makes sense to me to take the contrib changes out of this patch. I updated my
PR and have attached an updated diff.

I'm happy to alert the owners of the upstream projects if you think we should.
Those are just code comment edits though. Think it would matter to them?

The pared down diff I just attached will still fix all the user-facing menus I
believe.

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


[Bug 259230] Touching the touchpad on a frame.work laptop causes reboot or poweroff

2021-11-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=259230

--- Comment #10 from Vladimir Kondratyev  ---
Created attachment 229277
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=229277&action=edit
iichid.patch

Try attached patch. pause() value may require adjustment

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


[Bug 259645] crash in_cksumdata (sys/amd64/amd64/in_cksum.c:113) via in4_cksum (sys/netpfil/pf/in4_cksum.c:117) after FreeBSD 13.0 p5 update

2021-11-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=259645

Kubilay Kocak  changed:

   What|Removed |Added

Summary|crash after updating to |crash in_cksumdata
   |FreeBSD 13.0 p5 |(sys/amd64/amd64/in_cksum.c
   ||:113) via in4_cksum
   ||(sys/netpfil/pf/in4_cksum.c
   ||:117) after FreeBSD 13.0 p5
   ||update
   Keywords||crash, needs-qa
   Assignee|b...@freebsd.org|n...@freebsd.org
Version|13.0-STABLE |13.0-RELEASE
 CC||k...@freebsd.org,
   ||m...@freebsd.org,
   ||n...@freebsd.org
  Flags||maintainer-feedback?(mjg@Fr
   ||eeBSD.org),
   ||maintainer-feedback?(kp@fre
   ||ebsd.org), mfc-stable13?,
   ||mfc-stable12?
 Status|New |Open

--- Comment #1 from Kubilay Kocak  ---
Thank you for your report. Could you include additional information, including:

 - /var/run/dmesg.boot output (as an attachment)
 - /etc/rc.conf network configuration (as an attachment)
 - pciconf -lv output (as an attachment)
 - firewall (pf) configuration (as an attachment, sanitized where necessary)

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


[Bug 259640] snd_hda(4): Fix sound output in Lenovo Ideapad 330-15 and ThinkPad X230

2021-11-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=259640

Kubilay Kocak  changed:

   What|Removed |Added

 CC||a...@freebsd.org,
   ||delp...@freebsd.org
 Status|New |Open
   Keywords||easy, feature, needs-qa
  Flags||maintainer-feedback?(delphi
   ||j...@freebsd.org),
   ||maintainer-feedback?(avg@Fr
   ||eeBSD.org), mfc-stable13?,
   ||mfc-stable12?
Summary|[sound] Sound not work on   |snd_hda(4): Fix sound
   |some Lenovo notebook|output in Lenovo Ideapad
   ||330-15 and ThinkPad X230

--- Comment #1 from Kubilay Kocak  ---
Thank you for the report and patch Dmitry

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


[Bug 259631] pkgbase upgrade from 12 13 with root on zfs leaves system unbootable

2021-11-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=259631

Graham Perrin  changed:

   What|Removed |Added

 CC||grahamper...@gmail.com

--- Comment #1 from Graham Perrin  ---
bectl list -s

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


[Bug 259611] [smartpqi] file system checksum on blocks give errors on higher parallel loads

2021-11-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=259611

Graham Perrin  changed:

   What|Removed |Added

 CC||grahamper...@gmail.com

--- Comment #1 from Graham Perrin  ---
(In reply to Palle Girgensohn from comment #0)

How is the file system tuned? E.g. 

tunefs -p /

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


[Bug 160838] [acpi] ACPI Battery Monitor Non-Functional

2021-11-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=160838

Alexey Dokuchaev  changed:

   What|Removed |Added

 Status|Open|Closed
 CC||da...@freebsd.org
 Resolution|--- |Feedback Timeout

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


[Bug 259230] Touching the touchpad on a frame.work laptop causes reboot or poweroff

2021-11-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=259230

--- Comment #11 from Kyle Evans  ---
(In reply to Vladimir Kondratyev from comment #10)

With the attached patch, default iichid with sampling seems to work here.

With iichid_gpio, it ended up rebooting before I had a chance to touch the
touchpad or catch the console output.

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


[Bug 259640] snd_hda(4): Fix sound output in Lenovo Ideapad 330-15 and ThinkPad X230

2021-11-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=259640

Andriy Gapon  changed:

   What|Removed |Added

  Flags|maintainer-feedback?(avg@Fr |
   |eeBSD.org)  |

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