[Bug 273289] smartpqi: fix panic on removal of SAS drive

2023-08-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273289

--- Comment #9 from Warner Losh  ---
I may have a simple power switch I can connect to my direct attached storage
that would let me semi easily add remove the drive. Would that be enough to
trigger this? I have a spartpqi card here but due to the vagaries of the lab
env it has now drives right now... I could juggle though if you think that
would trigger it on my system...

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


[Bug 273289] smartpqi: fix panic on removal of SAS drive

2023-08-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273289

Mark Linimon  changed:

   What|Removed |Added

   Keywords||needs-qa

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


[Bug 273303] 5 sec delay happening intermenatingly from a customized web server on freebsd 11.2

2023-08-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273303

Ed Maste  changed:

   What|Removed |Added

 CC||ema...@freebsd.org

--- Comment #1 from Ed Maste  ---
11.2 is past EOL. Is this problem reproducible on a current release (12.4 or
13.2)?

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


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

2023-08-27 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 273289] smartpqi: fix panic on removal of SAS drive

2023-08-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273289

--- Comment #8 from John F. Carr  ---
Created attachment 244386
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=244386=edit
move free out of spinlock (new driver)

Because pqisrc_free_device has changed in the new driver a new patch is needed.
 I tested this by copying the new driver to 13.2-CURRENT, the version I am
running on my HPE server.  The new driver is very chatty, see below.  Instead
of a compile-time constant the variable logging_level in smartpqi_defines.h
should be a tunable and the default value should not include PQISRC_FLAGS_NOTE.

The driver appears to be trying to delete the drive twice.  See the "Invalid
device" note.

The following is the dmesg output triggered by removing and replacing a drive,
which would have caused a panic with the unpatched old driver.

[NOTE]:[ pqisrc_display_device_info ] [ 274 ]removed scsi BTL 0:8:0:  SEAGATE 
XS960SE70004 Physical SSDSmartPathCap- En- Exp+ qd=65535
[NOTE]:[ pqisrc_remove_device ] [ 1443 ]vendor: SEAGATE XS960SE70004 model:
XS960SE70004 bus:0 target:8 lun:0 is_physical_device:0x1 expose_device:0x1
volume_offline 0x0 volume_status 0x0 
[WARN]:[67:655.0][0,8,0][CPU
0][pqisrc_wait_for_device_commands_to_complete][430]:Device Outstanding IO
count = 0
[NOTE]:[ pqisrc_free_device ] [ 1643 ]Giving back target 8 
[NOTE]:[ pqisrc_delete_softs_entry ] [ 363 ]Invalid device, either it was
already removed or never added
[NOTE]:[ pqisrc_free_device ] [ 1673 ]Removed memory for device : B 0: T 8: L 0
da7 at smartpqi0 bus 0 scbus0 target 8 lun 0
da7:   s/n HLJ03TL8822150Z3 detached
(da7:smartpqi0:0:8:0): Periph destroyed
[NOTE]:[ pqisrc_add_softs_entry ] [ 288 ]Added device [7 of 10]: B 0: T 8: L 0
[NOTE]:[ pqisrc_add_device ] [ 1420 ]vendor: SEAGATE XS960SE70004 model:
XS960SE70004 bus:0 target:8 lun:0 is_physical_device:0x1 expose_device:0x1
volume_offline 0x0 volume_status 0x0 
[NOTE]:[ pqisrc_display_device_info ] [ 274 ]added scsi BTL 0:8:0:  SEAGATE 
XS960SE70004 Physical SSDSmartPathCap- En- Exp+ qd=65535
ses0: da7,pass8 in 'ArrayElement0007', SAS Slot: 1 phys at slot 8
ses0:  phy 0: SAS device type 1 phy 7 Target ( SSP )
ses0:  phy 0: parent 51402ec013d6a5b4 addr 5000c5003e85f2bd
da7 at smartpqi0 bus 0 scbus0 target 8 lun 0
da7:  Fixed Direct Access SPC-5 SCSI device

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


[Bug 270460] i386 CURRENT guest boot time panics in emulators/virtualbox-ose on amd64 host (FreeBSD 13.1, Windows 10, FreeBSD 13.2-RELEASE-p1)

2023-08-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270460

Paul Floyd  changed:

   What|Removed |Added

 Resolution|--- |Overcome By Events
 Status|Open|Closed

--- Comment #15 from Paul Floyd  ---
Not sure exactly when this changed, but I can now successfully install and boot
14.0 i386 alpha 3

FreeBSD freebsd 14.0-ALPHA3 FreeBSD 14.0-ALPHA3 i386 1400097 #0
stable/14-n265022-2af9390e54ed: Fri Aug 25 05:38:58 UTC 2023
r...@releng1.nyi.freebsd.org:/usr/obj/usr/src/i386.i386/sys/GENERIC i386

Marking this closed / overcome by events.

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


[Bug 269277] On 12.3, process-shared mutex may fail locking operations after usage of ANOTHER process-shared mutex.

2023-08-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=269277

Xin LI  changed:

   What|Removed |Added

 CC||delp...@freebsd.org
   Assignee|b...@freebsd.org|k...@freebsd.org

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