[Bug 272151] panic: use-after-free tty race condition

2023-06-25 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272151

Robert Wing  changed:

   What|Removed |Added

 CC||r...@freebsd.org

--- Comment #2 from Robert Wing  ---
The issue seems to be caused by knlist_clear() with the way it sets up the
knote with EV_ONESHOT. The event for the knote is triggered after the TTY is
revoked and the thread no longer holds the TTY lock when the knote event is
called.

I'd halfway assume that knotes shouldn't be triggered if the TTY was revoked,
which might look something like:
https://people.freebsd.org/~rew/tf-revoke.patch

or maybe it makes sense to delete the knotes when the TTY is not opened?
something like: https://people.freebsd.org/~rew/tty-knote.patch

or...some other behavior is expected? either way, both of the patches above
prevented the panic from occurring.

To reproduce, spin up a vm and execute the following:

- launch nvim
- suspend nvim (ctrl-z)
- poweroff (panic)

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


Problem reports for b...@freebsd.org that need special attention

2023-06-25 Thread bugzilla-noreply
To view an individual PR, use:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).

The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and obsolete releases.

Status  |Bug Id | Description
+---+---
New |197876 | [devfs] an error in devfs leads to data loss and  
New |202362 | ntp: restore refclocks selection (10.2-RELEASE re 
New |202740 | vi/ex string substitution problem when there is m 
New |204097 | witness_initialize() does not perform bound check 
New |206336 | [patch] usr.sbin/freebsd-update allow proxy confi 
New |209213 | UEFI Loader shows only black screen with Nvidia G 
New |210804 | installerconfig - using ZFS create in custom scri 
New |223470 | freebsd-update: Cannot identify running kernel (/ 
New |230620 | "install -d" issue
New |235085 | [PATCH] Option to make rc.d/sysctl more verbose ( 
New |252123 | fetch(3): Fix wrong usage of proxy when request i 
Open|177821 | sysctl: Some security.jail nodes are funky, dupli 
Open|182466 | [headers] [patch] make  self-contained  
Open|183618 | [panic] Dell PowerEdge R620 -- PERC H710 Mini (mf 
Open|192573 | Add ps(1) option: Print process start time in sec 
Open|194925 | [pf] [ifconfig] interface group keywords do not w 
Open|197921 | scheduler: Allow non-migratable threads to bind t 
Open|206528 | Emulex LPe 16002 FC HBA Not Recognized by oce(4)  
Open|206649 | cyapa(4): Add common gestures for Cypress APA I2C 
Open|212608 | sockstat(1) and lsof(8) can not identity the owne 
Open|220246 | syslogd does not send RFC3164-conformant messages 
Open|221305 | Mouse cursor loss when moving cursor while loadin 
Open|221550 | kern.bootfile returns only /kernel on mips64 (ERL 
Open|221854 | makefs: Reject UFS labels that are too long to fi 
Open|226893 | freebsd-update: Support patchlevel argument for f 
Open|231810 | [build] release always fails with "mkimg: partiti 
Open|233578 | Unprivileged local user can prevent other users l 
Open|233988 | freebsd-update: Improve progress output on termin 
Open|236718 | system panics with message: vm_fault_hold: fault  
Open|237287 | moused(8) ignores button release events in virtua 
Open|237924 | Possible infinite loop in function empty_aux_buff 
Open|238183 | cam/scsi/scsi_sa.c: warnings issued by static ana 
Open|238486 | Possible buffer overflow bug in sc_allocate_keybo 
Open|238550 | Touchpad (via SMBus) not working: Synaptics (SYN1 
Open|238638 | mfi: Remove unnecessary pointer printing in mfi.c 
Open|238837 | init: Remove P_SYSTEM flag from PID 1 to allow ea 
Open|241697 | i915kms: Kernel panic loading module on custom ke 
Open|247132 | Fix build error: use of undeclared identifier 'cp 
Open|248352 | mfi(4): Remove RAID map sync functionality
Open|257149 | CFLAGS not passed to whole build  

40 problems total for which you should take action.


[Bug 272206] Add support for Intel GMAC Ethernet controller

2023-06-25 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272206

Graham Perrin  changed:

   What|Removed |Added

 Status|New |Open
  Component|kern|conf
 CC||grahamper...@freebsd.org
   Severity|Affects Some People |Affects Only Me
   Assignee|b...@freebsd.org|n...@freebsd.org

--- Comment #1 from Graham Perrin  ---
^Triage: 

* severity reduced to the norm for a feature request
* assignment

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


[Bug 254343] 13.0-RC2: adding a vtnet (VirtIO network) interface to bridge fails

2023-06-25 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254343

Mina Galić  changed:

   What|Removed |Added

   Assignee|b...@freebsd.org|n...@freebsd.org
 Status|New |In Progress

--- Comment #12 from Mina Galić  ---
assigning this net@ and marking as in progress, until a new release or at least
the reporters confirm this working

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


[Bug 272206] Add support for Intel GMAC Ethernet controller

2023-06-25 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272206

Bug ID: 272206
   Summary: Add support for Intel GMAC Ethernet controller
   Product: Base System
   Version: 13.2-STABLE
  Hardware: amd64
OS: Any
Status: New
  Severity: Affects Some People
  Priority: ---
 Component: kern
  Assignee: b...@freebsd.org
  Reporter: dimitr...@gmail.com

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

Hello,

I recently acquired Fitlet3 miniPC from compulab. This is updated version of
Fitlet2 using Elkhart Lake Celeron and Atom SoC's.

details here;
http://fit-pc.com/wiki/index.php?title=Fitlet3_Specifications_and_block_diagram

It comes with onboard intel LAN with Marvell 88E1512 PHY for 2 onboard NIC's.
Unfortunate its not recognized under freeBSD (tried 13.2 and 14)

Im pretty new to freeBSD so please excuse my lack of knowledge regarding driver
support. On linux this is handled by compiling the kernel with;

CONFIG_NET_VENDOR_STMICRO=y
CONFIG_STMMAC_ETH=m
CONFIG_DWMAC_INTEL=m
CONFIG_STMMAC_PCI=m

and utilizing driver;
https://github.com/torvalds/linux/blob/master/drivers/net/ethernet/stmicro/stmmac/dwmac-intel.c
 

Maybe drivers could be reused?

I'm opening the ticket since I would appreciate the freeBSD support for this
device, since its perfect HW for EDGE firewall or gateway.

Thank you for looking into it.

Regards,

Attaching also some outputs from the box itself with FreeBSD 13.2 installed
(ignore igb0 and igb1 NIC's since these are on installed extension card)

dmesg output in attachement.

lcpci output  - onboard NIC's identified as:

00:1d.1 Ethernet controller: Intel Corporation Device 4ba1
00:1d.2 Ethernet controller: Intel Corporation Device 4bb1

/
00:00.0 Host bridge: Intel Corporation Device 4522
00:02.0 VGA compatible controller: Intel Corporation Elkhart Lake [UHD Graphics
Gen11 16EU]
00:08.0 System peripheral: Intel Corporation Elkhart Lake Gaussian and Neural
Accelerator
00:11.0 Communication controller: Intel Corporation Device 4b96
00:11.1 Communication controller: Intel Corporation Device 4b97
00:13.0 Serial bus controller: Intel Corporation Device 4b84
00:14.0 USB controller: Intel Corporation Elkhart Lake USB 3.10 XHCI
00:14.2 RAM memory: Intel Corporation Elkhart Lake PMC SRAM
00:15.0 Serial bus controller: Intel Corporation Device 4b78
00:15.2 Serial bus controller: Intel Corporation Device 4b7a
00:15.3 Serial bus controller: Intel Corporation Device 4b7b
00:16.0 Communication controller: Intel Corporation Elkhart Lake Management
Engine Interface
00:19.0 Serial bus controller: Intel Corporation Device 4b4b
00:19.2 Communication controller: Intel Corporation Device 4b4d
00:1b.0 Serial bus controller: Intel Corporation Device 4bb9
00:1b.1 Serial bus controller: Intel Corporation Device 4bba
00:1b.6 Serial bus controller: Intel Corporation Device 4bbf
00:1c.0 PCI bridge: Intel Corporation Elkhart Lake PCH PCI Express Root Port #0
00:1c.4 PCI bridge: Intel Corporation Device 4b3c
00:1c.6 PCI bridge: Intel Corporation Elkhart Lake PCH PCI Express Root Port #6
00:1d.0 System peripheral: Intel Corporation Device 4bb3
00:1d.1 Ethernet controller: Intel Corporation Device 4ba1
00:1d.2 Ethernet controller: Intel Corporation Device 4bb1
00:1e.0 Communication controller: Intel Corporation Device 4b28
00:1e.1 Communication controller: Intel Corporation Device 4b29
00:1f.0 ISA bridge: Intel Corporation Elkhart Lake eSPI Controller
00:1f.4 SMBus: Intel Corporation Elkhart Lake SMBus Controller
00:1f.5 Serial bus controller: Intel Corporation Elkhart Lake SPI (Flash)
Controller
01:00.0 Non-Volatile memory controller: Sandisk Corp WD Blue SN570 NVMe SSD
02:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network Connection
03:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network Connection
/

pciconf output;


///
hostb0@pci0:0:0:0:  class=0x06 rev=0x01 hdr=0x00 vendor=0x8086
device=0x4522 subvendor=0x8086 subdevice=0x7270
vgapci0@pci0:0:2:0: class=0x03 rev=0x01 hdr=0x00 vendor=0x8086
device=0x4555 subvendor=0x8086 subdevice=0x7270
none0@pci0:0:8:0:   class=0x088000 rev=0x01 hdr=0x00 vendor=0x8086
device=0x4511 subvendor=0x8086 subdevice=0x7270
none1@pci0:0:17:0:  class=0x078008 rev=0x11 hdr=0x00 vendor=0x8086
device=0x4b96 subvendor=0x8086 subdevice=0x7270
none2@pci0:0:17:1:  class=0x078009 rev=0x11 hdr=0x00 vendor=0x8086
device=0x4b97 subvendor=0x8086 subdevice=0x7270
none3@pci0:0:19:0:  class=0x0c8014 rev=0x11 hdr=0x00 vendor=0x8086
device=0x4b84 subvendor=0x8086 subdevice=0x7270
xhci0@pci0:0:20:0:  class=0x0c0330 rev=0x11 hdr=0x00 vendor=0x8086
device=0x4b7d subvendor=0x8086 subdevice=0x7270
none4@pci0:0:20:2:  class=0x05 rev=0x11 hdr=0x00 vendor=0x8086
device=0x4b7f subvendor=0x8086 subdevice=0x7270
none5@pci0:0:21:0:  class=0x0c8000 rev=0x11 

[Bug 252227] Default value of vm.max_wired is too low since 12.2

2023-06-25 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252227

Vladimir Druzenko  changed:

   What|Removed |Added

Summary|Default value of|Default value of
   |vm.max_wired is too low in  |vm.max_wired is too low
   |12.⋯|since 12.2

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


[Bug 252227] Default value of vm.max_wired is too low in 12.⋯

2023-06-25 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252227

Graham Perrin  changed:

   What|Removed |Added

Summary|Default value of|Default value of
   |vm.max_wired is too low in  |vm.max_wired is too low in
   |12.2|12.⋯
 CC||grahamper...@freebsd.org
 Status|New |Open

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


[Bug 260692] shutdown -r now stops the server, but it does not boot

2023-06-25 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260692

--- Comment #11 from Graham Perrin  ---
… assuming that you still have a 12.⋯ boot environment …

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


[Bug 260692] shutdown -r now stops the server, but it does not boot

2023-06-25 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260692

Graham Perrin  changed:

   What|Removed |Added

   Keywords||needs-qa
 Status|New |Open

--- Comment #10 from Graham Perrin  ---
(In reply to Tatsuki Makino from comment #9)

Claudio, do you find the same, if you wait the same length of time (or longer)?

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


[Bug 260692] shutdown -r now stops the server, but it does not boot

2023-06-25 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260692

Tatsuki Makino  changed:

   What|Removed |Added

 CC||tatsuki_mak...@hotmail.com

--- Comment #9 from Tatsuki Makino  ---
I didn't pay much attention to it :)

I have had this problem in my 12.x-STABLE environment since probably the same
time.
What I know is that we have to wait about 5-7 minutes for it to run, not that a
reboot or power off doesn't run.
Also, if we reboot or power off with little disk access, there is almost no
such waiting time. But this is unclear.

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


[Bug 272198] lzr application built by www/lzr makes OS unresponsive

2023-06-25 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272198

Yuri Victorovich  changed:

   What|Removed |Added

   Assignee|b...@freebsd.org|n...@freebsd.org

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


[Bug 272198] lzr application built by www/lzr makes OS unresponsive

2023-06-25 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272198

Bug ID: 272198
   Summary: lzr application built by www/lzr makes OS unresponsive
   Product: Base System
   Version: CURRENT
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: kern
  Assignee: b...@freebsd.org
  Reporter: y...@freebsd.org

This command:
> lzr -d -sendInterface 
causes the system to become completely unresponsive.

I think that it floods the network with a lot of requests.
But this shouldn't freeze the system.

13.2-STABLE stable/13-n255567-13cc2842304c

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