[Bug 246008] Kernel Panic: vchan_trigger

2024-10-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246008

Christos Margiolis  changed:

   What|Removed |Added

 CC||chris...@freebsd.org
 Status|New |Open

--- Comment #2 from Christos Margiolis  ---
Is this panic still reproducible in current versions of FreeBSD?

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


[Bug 170847] [rc] static IPv6 addresses+vlans don't work ala rc(5)

2024-10-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=170847

Tatsuki Makino  changed:

   What|Removed |Added

 CC||tatsuki_mak...@hotmail.com

--- Comment #4 from Tatsuki Makino  ---
This will be a configuration for the 14.1-STABLE generation, but...

Since /etc/rc.conf is a configuration sh script, most sh syntax can be used.
However, it cannot use most external commands.
It's because it's read before the file system is mounted.

VLANs with 802.1Q seem to have a negative impact on link local addresses.
This is because, basically, there is only one MAC address of the parent.
The following has already happened

>inet6 fe80::207:43ff:fe07:3f71%cxgb1 prefixlen 64 scopeid 0x2 
>inet6 fe80::207:43ff:fe07:3f71%cxgb1.223 prefixlen 64 scopeid 0xe 

It seems that it is better to avoid this, and the configures to avoid it are as
follows.

vlans_cxgb1="vlan0" # for this explain clarity, it will be vlan0
if ! : ; then
  ifconfig_vlan0="inet6 fe80::589c:fcff:fe00:1 prefixlen 64 -ifdisabled
-auto_linklocal"
# however, it does not indicate that this interface is IPv6 interface.
  ifconfig_vlan0_alias0="inet6 2001:db8::589c:fcff:fe00:1 prefixlen 64"
elif : ; then
  ifconfig_vlan0="down"
  ifconfig_vlan0_ipv6="inet6 fe80::589c:fcff:fe00:1 prefixlen 64
-auto_linklocal"
  ifconfig_vlan0_alias0="inet6 2001:db8::589c:fcff:fe00:1 prefixlen 64"
else
  ifconfig_vlan0="down"
  ifconfig_vlan0_ipv6="inet6 down -auto_linklocal"
  ifconfig_vlan0_alias0="inet6 fe80::589c:fcff:fe00:1 prefixlen 64"
  ifconfig_vlan0_alias1="inet6 2001:db8::589c:fcff:fe00:1 prefixlen 64"
fi

I've written multiple examples using conditional branching.
The common denominator is that it does not automatically add a link-local
address, and that the interface is kept down until a link-local address is
assigned.
And the link-local address should be the first address to be assigned.

In my environment, this seems to stabilize neighbor discovery.

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


[Bug 278229] iconv mapping tables for ISO 8859-2 and 8859-3 contain garbage

2024-10-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278229

Mark Linimon  changed:

   What|Removed |Added

 Attachment #249799|application/x-gzip  |text/plain
  mime type||
 Attachment #249799|0   |1
   is patch||

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


[Bug 278229] iconv mapping tables for ISO 8859-2 and 8859-3 contain garbage

2024-10-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278229

Mark Linimon  changed:

   What|Removed |Added

   Keywords|patch   |

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


[Bug 216079] NTPD(8) interface command undocumented

2024-10-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216079

Mark Linimon  changed:

   What|Removed |Added

   Keywords|patch   |

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


[Bug 44034] Multiple sysctl variables are not documented

2024-10-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=44034

Alexander Ziaee  changed:

   What|Removed |Added

   Keywords||tracking
 CC||zi...@runbox.com

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


[Bug 109104] mac_bsdextended(4): documented sysctl appears to not exist

2024-10-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=109104

Alexander Ziaee  changed:

   What|Removed |Added

   Keywords||patch

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


[Bug 157234] nullfs(5): //proc/curproc/file returns "unknown" with a binary called via a nullfs mountpoint

2024-10-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=157234

Alexander Ziaee  changed:

   What|Removed |Added

 CC||zi...@runbox.com
Summary|[patch] nullfs(5):  |nullfs(5):
   |//proc/curproc/file returns |//proc/curproc/file returns
   |"unknown" with a binary |"unknown" with a binary
   |called via a nullfs |called via a nullfs
   |mountpoint  |mountpoint

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


[Bug 109104] mac_bsdextended(4): documented sysctl appears to not exist

2024-10-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=109104

Alexander Ziaee  changed:

   What|Removed |Added

Summary|man mac_bsdextended is not  |mac_bsdextended(4):
   |consistent with systl   |documented sysctl appears
   |output  |to not exist
 CC||zi...@runbox.com

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


[Bug 261357] man(1) cannot handle manual pages with spaces in file name

2024-10-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261357

Wolfram Schneider  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|New |Closed

--- Comment #1 from Wolfram Schneider  ---


*** This bug has been marked as a duplicate of bug 275978 ***

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


[Bug 282192] absolute symlink in /usr/bin

2024-10-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282192

Wolfram Schneider  changed:

   What|Removed |Added

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

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


[Bug 261437] outdated mktemp(1) examples

2024-10-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261437

--- Comment #1 from commit-h...@freebsd.org ---
A commit in branch main references this bug:

URL:
https://cgit.FreeBSD.org/src/commit/?id=93181e38342fc48eb95f83842156be478a4a6f01

commit 93181e38342fc48eb95f83842156be478a4a6f01
Author: Wolfram Schneider 
AuthorDate: 2024-10-27 16:33:39 +
Commit: Wolfram Schneider 
CommitDate: 2024-10-27 16:36:31 +

mktemp(1): bring the documentation up to date with best practice

Using short temp filenames as /tmp/temp. (4 or 6 X) was probably ok
20 years ago, but not anymore. Best practice is to use 10 X. Given that our
users often copy & paste examples from our manual pages we need to
update the documentation.

PR: 261437

 usr.bin/mktemp/mktemp.1 | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

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


[Bug 261437] outdated mktemp(1) examples

2024-10-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261437

--- Comment #2 from commit-h...@freebsd.org ---
A commit in branch main references this bug:

URL:
https://cgit.FreeBSD.org/src/commit/?id=95b17d3b1c5187d2630556eaa0f2107378ca3b4f

commit 95b17d3b1c5187d2630556eaa0f2107378ca3b4f
Author: Wolfram Schneider 
AuthorDate: 2024-10-27 16:41:01 +
Commit: Wolfram Schneider 
CommitDate: 2024-10-27 16:41:01 +

mktemp(3): bring the documentation up to date with best practice

Using short temp filenames as /tmp/temp. (4 or 6 X) was probably ok
20 years ago, but not anymore. Best practice is to use 10 X. Given that our
users often copy & paste examples from our manual pages we need to
update the documentation.

PR: 261437

 lib/libc/stdio/mktemp.3 | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

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


[Bug 261437] outdated mktemp(1) examples

2024-10-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261437

Wolfram Schneider  changed:

   What|Removed |Added

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

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


[Bug 282364] /bin/sh Adding new lines into PS1 causes visual glitches

2024-10-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282364

Bug ID: 282364
   Summary: /bin/sh Adding new lines into PS1 causes visual
glitches
   Product: Base System
   Version: 14.1-RELEASE
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: bin
  Assignee: b...@freebsd.org
  Reporter: adrie...@gmail.com

Adding new lines into PS1 causes visual glitches when using /bin/sh.


~/.shrc

```
export PS1='\[\n \] \u \[\n \] #  '

# csh like history on arrow up and down
bind "^[[A" ed-search-prev-history
bind "^[[B" ed-search-next-history
```

example commands:

type this and enter it into history

```
ls /var/log/
```

Now type ls and hit the up arrow, you will see a large gap between "ls" and
/var/log.

```
root
#  ls  /var/log/
```

It seems to me that the text before PS1 new lines are added to the the current
line which gives
a weird gap to the shells prompt output. If you modify the command after its
been inserted the spacing
glitch gets worse and worse and it becomes impossible to see what commands you
are typing.

expected behaviour:

New lines in PS1 should work as csh,bash, zsh and not have weird spacing and
visual glitches.

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


[Bug 280290] hms(4): Broken fresh after boot, fixed by resume

2024-10-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280290

--- Comment #29 from Mikael Urankar  ---
*** Bug 280972 has been marked as a duplicate of this bug. ***

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


[Bug 213026] ixgbe(4) driver name is now ix

2024-10-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213026

--- Comment #4 from commit-h...@freebsd.org ---
A commit in branch main references this bug:

URL:
https://cgit.FreeBSD.org/src/commit/?id=a340b4649621f0dbc0607115217889909ce33bd1

commit a340b4649621f0dbc0607115217889909ce33bd1
Author: Felix Johnson 
AuthorDate: 2024-10-27 00:46:41 +
Commit: Kevin Bowling 
CommitDate: 2024-10-27 09:01:35 +

ix.4: document LOADER TUNABLES

PR: 213026
MFC after:  3 days
Co-authored-by: Alexander Ziaee 

 share/man/man4/ix.4 | 39 ++-
 1 file changed, 38 insertions(+), 1 deletion(-)

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


[Bug 213026] ixgbe(4) driver name is now ix

2024-10-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213026

--- Comment #5 from commit-h...@freebsd.org ---
A commit in branch main references this bug:

URL:
https://cgit.FreeBSD.org/src/commit/?id=d8b48a267fc0f737a13cb52dc1071981ecb1e003

commit d8b48a267fc0f737a13cb52dc1071981ecb1e003
Author: Felix Johnson 
AuthorDate: 2024-10-27 00:26:34 +
Commit: Kevin Bowling 
CommitDate: 2024-10-27 09:00:43 +

ixgbe.4: rename to ix.4

PR: 213026
MFC after:  3 days
Reported by:Sergey Akhmatov 
Co-authored-by: Alexander Ziaee 

 share/man/man4/Makefile  |  8 
 share/man/man4/{ixgbe.4 => ix.4} | 14 +++---
 2 files changed, 11 insertions(+), 11 deletions(-)

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


[Bug 213026] ixgbe(4) driver name is now ix

2024-10-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213026

Kevin Bowling  changed:

   What|Removed |Added

   Assignee|b...@freebsd.org|kbowl...@freebsd.org
 CC||kbowl...@freebsd.org
 Status|Open|In Progress

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


[Bug 282269] /etc/rc.d/kld: print the kernel modules being loaded

2024-10-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282269

Mark Johnston  changed:

   What|Removed |Added

   Assignee|b...@freebsd.org|ma...@freebsd.org
 CC||ma...@freebsd.org
 Status|New |In Progress

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


[Bug 58012] [patch] tftpd(8) Multihomed tftpd enhancement

2024-10-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=58012

Mark Linimon  changed:

   What|Removed |Added

   Keywords|patch   |

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


[Bug 58012] [patch] tftpd(8) Multihomed tftpd enhancement

2024-10-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=58012

Mark Linimon  changed:

   What|Removed |Added

  Attachment #36095|0   |1
   is patch||

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


[Bug 282373] kernel panic on boot with Chelsio T320 installed

2024-10-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282373

Bug ID: 282373
   Summary: kernel panic on boot with Chelsio T320 installed
   Product: Base System
   Version: 14.1-RELEASE
  Hardware: amd64
OS: Any
Status: New
  Severity: Affects Some People
  Priority: ---
 Component: kern
  Assignee: b...@freebsd.org
  Reporter: biscuits.carry...@icloud.com

Both " 14.1-RELEASE releng/14.1-n267679-10e31f0946d8 GENERIC amd64" and
"14.2-PRERELEASE stable/14-n269296-5ae76ff5138e GENERIC amd64" kernels panic at
the same point during startup on a system with a Chelsio T320 NIC installed,
with two 10Gbase-SR SFP+ installed.

This crash appears to be triggered by something in the OPNSense 24.7 startup,
but userspace doesn't appear to be doing anything unreasonable at the time.

Starting device manager...
acpi_wmi0:  on acpi0
acpi_wmi0: Embedded MOF found
ACPI: \_SB.WMIB.WQZZ: 1 arguments were passed to a non-method ACPI object
(Buffer) (20221020/nsarguments-361)
acpi_wmi1:  on acpi0
acpi_wmi1: Embedded MOF found
ACPI: \_SB.WMIV.WQZZ: 1 arguments were passed to a non-method ACPI object
(Buffer) (20221020/nsarguments-361)
acpi_wmi2:  on acpi0
acpi_wmi2: Embedded MOF found
cxgbc0:  mem 0xd100-0xd1000fff,0xd1001000-0xd1001fff
irq 16 at device 0.0 on pci1
cxgbc0: using MSI-X interrupts (9 vectors)
cxgb0:  on cxgbc0
Fatal trap 12: page fault while in kernel mode

I am not able to reproduce the panic when booting from a FreeBSD 14.1 or
FreeBSD 14.2-PRERELEASE memstick, although I have not tried an install.

Here's the backtrace from the latest 14.2 PRERELEASE kernel:

Fatal trap 12: page fault while in kernel mode
cpuid = 2; apic id = 04
fault virtual address   = 0x0
fault code  = supervisor read instruction, page not present
instruction pointer = 0x20:0x0
stack pointer   = 0x28:0xfe00aab0b6f8
frame pointer   = 0x28:0xfe00aab0b720
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 367 (devctl)
rdi: f80024451000 rsi: fe00aab0b770 rdx: fe00acbb9ed8
rcx: c0306938  r8:   r9: 
rax:  rbx: fe00aab0b770 rbp: fe00aab0b720
r10: f8003bb06800 r11: 0800 r12: 8802
r13: f8003bb06810 r14: fe00acbb9ed8 r15: 
trap number = 12
panic: page fault
cpuid = 2
time = 1730034648
KDB: stack backtrace:
#0 0x80b8b9bd at kdb_backtrace+0x5d
#1 0x80b3e101 at vpanic+0x131
#2 0x80b3dfc3 at panic+0x43
#3 0x81024a0b at trap_fatal+0x40b
#4 0x81024a56 at trap_pfault+0x46
#5 0x80ffb538 at calltrap+0x8
#6 0x80d897e5 at dump_iface+0x145
#7 0x80d891a9 at rtnl_handle_ifevent+0xa9
#8 0x80c5c75f at if_attach_internal+0x3df
#9 0x80c6784c at ether_ifattach+0x2c
#10 0x83327b53 at cxgb_port_attach+0x1d3
#11 0x80b7abac at device_attach+0x3ac
#12 0x80b7be7b at bus_generic_attach+0x4b
#13 0x83326ab6 at cxgb_controller_attach+0x926
#14 0x80b7abac at device_attach+0x3ac
#15 0x80b7a7e1 at device_probe_and_attach+0x41
#16 0x80818382 at pci_driver_added+0xf2
#17 0x80b78269 at devclass_driver_added+0x29

I can provide vmcore files from 14.1-RELEASE or 14.2-PRERELEASE, and am happy
to test with other kernels if necessary.

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


[Bug 162181] [snd_emu10k1] The kernel sound driver module snd_emu10k1.ko hangs when loaded.

2024-10-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=162181

Mark Linimon  changed:

   What|Removed |Added

Summary|[snd_emu10k1] [patch] The   |[snd_emu10k1] The kernel
   |kernel sound driver module  |sound driver module
   |snd_emu10k1.ko hangs when   |snd_emu10k1.ko hangs when
   |loaded. |loaded.
   Keywords|patch   |

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


[Bug 282373] kernel panic on boot with Chelsio T320 installed

2024-10-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282373

Mark Linimon  changed:

   What|Removed |Added

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

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


[Bug 282374] kernel panic on boot with Chelsio T320 installed

2024-10-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282374

Mark Linimon  changed:

   What|Removed |Added

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

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


[Bug 282374] kernel panic on boot with Chelsio T320 installed

2024-10-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282374

--- Comment #2 from Mark Linimon  ---
*** Bug 282373 has been marked as a duplicate of this bug. ***

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


[Bug 282374] kernel panic on boot with Chelsio T320 installed

2024-10-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282374

--- Comment #1 from ScottD  ---
Here's the last few lines of the message buffer before the panic:

Starting device manager...
acpi_wmi0:  on acpi0
acpi_wmi0: Embedded MOF found
ACPI: \_SB.WMIB.WQZZ: 1 arguments were passed to a non-method ACPI object
(Buffer) (20221020/nsarguments-361)
acpi_wmi1:  on acpi0
acpi_wmi1: Embedded MOF found
ACPI: \_SB.WMIV.WQZZ: 1 arguments were passed to a non-method ACPI object
(Buffer) (20221020/nsarguments-361)
acpi_wmi2:  on acpi0
acpi_wmi2: Embedded MOF found
cxgbc0:  mem 0xd100-0xd1000fff,0xd1001000-0xd1001fff
irq 16 at device 0.0 on pci1
cxgbc0: using MSI-X interrupts (9 vectors)
cxgb0:  on cxgbc0
Fatal trap 12: page fault while in kernel mode

I am not able to reproduce the panic when booting from a FreeBSD 14.1 or
FreeBSD 14.2-PRERELEASE memstick, although I have not tried an install.

Here's the backtrace from the latest 14.2 PRERELEASE kernel:

Fatal trap 12: page fault while in kernel mode
cpuid = 2; apic id = 04
fault virtual address   = 0x0
fault code  = supervisor read instruction, page not present
instruction pointer = 0x20:0x0
stack pointer   = 0x28:0xfe00aab0b6f8
frame pointer   = 0x28:0xfe00aab0b720
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 367 (devctl)
rdi: f80024451000 rsi: fe00aab0b770 rdx: fe00acbb9ed8
rcx: c0306938  r8:   r9: 
rax:  rbx: fe00aab0b770 rbp: fe00aab0b720
r10: f8003bb06800 r11: 0800 r12: 8802
r13: f8003bb06810 r14: fe00acbb9ed8 r15: 
trap number = 12
panic: page fault
cpuid = 2
time = 1730034648
KDB: stack backtrace:
#0 0x80b8b9bd at kdb_backtrace+0x5d
#1 0x80b3e101 at vpanic+0x131
#2 0x80b3dfc3 at panic+0x43
#3 0x81024a0b at trap_fatal+0x40b
#4 0x81024a56 at trap_pfault+0x46
#5 0x80ffb538 at calltrap+0x8
#6 0x80d897e5 at dump_iface+0x145
#7 0x80d891a9 at rtnl_handle_ifevent+0xa9
#8 0x80c5c75f at if_attach_internal+0x3df
#9 0x80c6784c at ether_ifattach+0x2c
#10 0x83327b53 at cxgb_port_attach+0x1d3
#11 0x80b7abac at device_attach+0x3ac
#12 0x80b7be7b at bus_generic_attach+0x4b
#13 0x83326ab6 at cxgb_controller_attach+0x926
#14 0x80b7abac at device_attach+0x3ac
#15 0x80b7a7e1 at device_probe_and_attach+0x41
#16 0x80818382 at pci_driver_added+0xf2
#17 0x80b78269 at devclass_driver_added+0x29

I can provide vmcore files from 14.1-RELEASE or 14.2-PRERELEASE, and am happy
to test with other kernels if necessary.

The information below is from a vmcore on "FreeBSD 14.2-PRERELEASE
stable/14-n269296-5ae76ff5138e GENERIC amd64"

In kgdb, the backtrace is slightly different, with the page fault in
ifmedia_ioctl due to a null pointer in ifm->ifm_status - the ifm_status
callback pointer is null.

#9  0x80c6c329 in ifmedia_ioctl (ifp=0xf80024451000,
ifr=0xfe00aab0b770, ifm=0xfe00acbb9ed8,
cmd=) at /usr/src/sys/net/if_media.c:293
warning: Source file is more recent than executable.
293 (*ifm->ifm_status)(ifp, ifmr);
(kgdb) p ifm
$1 = (struct ifmedia *) 0xfe00acbb9ed8
(kgdb) p ifm->ifm_status
$2 = (ifm_stat_cb_t) 0x0

And here's the more complete backtrace as shown in kgdb:

#0  __curthread () at /usr/src/sys/amd64/include/pcpu_aux.h:57
#1  doadump (textdump=) at /usr/src/sys/kern/kern_shutdown.c:405
#2  0x80b3dc97 in kern_reboot (howto=260) at
/usr/src/sys/kern/kern_shutdown.c:523
#3  0x80b3e16e in vpanic (fmt=0x81174043 "%s",
ap=ap@entry=0xfe00aab0b550)
at /usr/src/sys/kern/kern_shutdown.c:967
#4  0x80b3dfc3 in panic (fmt=) at
/usr/src/sys/kern/kern_shutdown.c:891
#5  0x81024a0b in trap_fatal (frame=0xfe00aab0b630, eva=0) at
/usr/src/sys/amd64/amd64/trap.c:952
#6  0x81024a56 in trap_pfault (frame=, usermode=false,
signo=,
ucode=) at /usr/src/sys/amd64/amd64/trap.c:760
#7  
#8  0x in ?? ()
#9  0x80c6c329 in ifmedia_ioctl (ifp=0xf80024451000,
ifr=0xfe00aab0b770, ifm=0xfe00acbb9ed8,
cmd=) at /usr/src/sys/net/if_media.c:293
#10 0x80d897e5 in get_operstate_ether (ifp=0xf80024451000,
pstate=)
at /usr/src/sys/netlink/route/iface.c:124
#11 get_operstate (ifp=0xf80024451000, pstate=) at
/usr/src/sys/netlink/route/iface.c:181
#12 dump_iface (nw=nw@entry=0xfe00aab0b7e8,
ifp=ifp@entry=0xf80024451000,
hdr=hdr@entry=0xfe00aab0b828, if_flags_mask=if_flags_mask@entry=0)
at /usr/src/sys/netlink/route/iface.c:310
#13 0x80d891a9 in rtnl_handle_ifevent (ifp=0xf80024451000,
nlmsg_type=,
if_flags_mask=0) at /usr/src/sys/netl

[Bug 282374] kernel panic on boot with Chelsio T320 installed

2024-10-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282374

Bug ID: 282374
   Summary: kernel panic on boot with Chelsio T320 installed
   Product: Base System
   Version: 14.1-RELEASE
  Hardware: amd64
OS: Any
Status: New
  Severity: Affects Some People
  Priority: ---
 Component: kern
  Assignee: b...@freebsd.org
  Reporter: biscuits.carry...@icloud.com

Both "14.1-RELEASE releng/14.1-n267679-10e31f0946d8 GENERIC amd64" and
"14.2-PRERELEASE stable/14-n269296-5ae76ff5138e GENERIC amd64" kernels panic at
the same point during startup on a system with a Chelsio T320 NIC installed,
with two 10Gbase-SR SFP+ installed.

This crash appears to be triggered by something in the OPNSense 24.7 startup,
but userspace doesn't appear to be doing anything unreasonable at the time.

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


[Bug 197921] scheduler: Allow non-migratable threads to bind to their current CPU

2024-10-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197921

Mark Linimon  changed:

   What|Removed |Added

   Keywords|needs-patch |

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


[Bug 269653] src/sys/dev/an/if_an_pci.c : error: a function definition without a prototype is deprecated in all versions of C and is not supported in C2x [-Werror,-Wdeprecated-non-prototype]

2024-10-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=269653

Mark Johnston  changed:

   What|Removed |Added

 Resolution|--- |Overcome By Events
 Status|New |Closed
 CC||ma...@freebsd.org

--- Comment #1 from Mark Johnston  ---
I can't reproduce this by building a GENERIC kernel without "device an" on
stable/13.  (The driver is removed in main.)  Please re-open if you can
reproduce this, and please provide the kernel configuration you're using.

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


[Bug 269919] Cannot boot GENERIC-KASAN kernel

2024-10-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=269919

Mark Johnston  changed:

   What|Removed |Added

 Status|Open|Closed
 Resolution|--- |Feedback Timeout

--- Comment #2 from Mark Johnston  ---
I believe this problem is gone with a sufficiently new loader.  Please re-open
if that's not the case.

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


[Bug 280290] hms(4): Broken fresh after boot, fixed by resume

2024-10-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280290

--- Comment #26 from Edward Tomasz Napierala  ---
Okay, I think I know what's going on.  I've added some strategic printfs, and
it looks like this:

iichid_attach: start
hidbus0:  on iichid0
hkbd0:  on hidbus0
kbd2 at hkbd0
iichid_intr_start: done
iichid_attach: done

What seems to happen is that iichid_intr_start() sets the power correctly, but
then iichid_attach() sets it back off, just before returning.

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


[Bug 271038] "posixshmcontrol ls" gets an error when another user restricts some shared memory

2024-10-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271038

Mark Johnston  changed:

   What|Removed |Added

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

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


[Bug 272762] zone_timeout / bucket_drain : Fatal trap 9: general protection fault while in kernel mode

2024-10-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272762

Mark Johnston  changed:

   What|Removed |Added

 Status|New |Open
 CC||ma...@freebsd.org

--- Comment #2 from Mark Johnston  ---
Sorry that this didn't get attention when it was submitted.  Did the panic turn
out to be reproducible?  I don't believe there have been any recent bug fixes
to that part of UMA, so a hardware error seems like a possible cause.

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


[Bug 273171] tcpdump is vulnerable

2024-10-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273171

Mark Johnston  changed:

   What|Removed |Added

 CC||ma...@freebsd.org

--- Comment #3 from Mark Johnston  ---
(In reply to Ed Maste from comment #2)
stable/13 still has 4.9.3.

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


[Bug 270399] lock order reversal /usr/src/sys/net/bpf.c:1519

2024-10-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270399

Mark Johnston  changed:

   What|Removed |Added

 Status|New |Closed
 CC||ma...@freebsd.org
 Resolution|--- |FIXED

--- Comment #1 from Mark Johnston  ---
I believe this is now fixed by commit a52f23f4c49e4.  In particular, iflib no
longer holds its ctx lock while calling ether_ifattach(), so the iflib ctx ->
bpf global lock order isn't established.

I also don't see any LORs when enabling promiscuous mode on an igb interface,
and witness reports a lock order "bpf global lock" -> "iflib ctx lock".

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


[Bug 280290] hms(4): Broken fresh after boot, fixed by resume

2024-10-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280290

--- Comment #27 from da...@catwhisker.org ---
(In reply to Edward Tomasz Napierala from comment #24)
OK; I just tried your patch on my laptop.  It works for me -- both in head:

g1-48(15.0-C)[1] uname -aUK
FreeBSD g1-48.catwhisker.org 15.0-CURRENT FreeBSD 15.0-CURRENT #118
main-n273270-cadb71e4b013: Sun Oct 27 11:14:36 UTC 2024
r...@g1-48.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/sys/CANARY amd64
1500026 1500026


and in stable/14:

g1-48(14.2-P)[1] uname -aUK
FreeBSD g1-48.catwhisker.org 14.2-PRERELEASE FreeBSD 14.2-PRERELEASE #265
stable/14-n269315-b21c677ed28a: Sun Oct 27 10:42:50 UTC 2024
r...@g1-48.catwhisker.org:/common/S1/obj/usr/src/amd64.amd64/sys/CANARY amd64
1401503 1401503

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


[Bug 166626] [build] sio.c driver won't compile -- error in include file

2024-10-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166626

Mark Johnston  changed:

   What|Removed |Added

 Resolution|--- |Overcome By Events
 CC||ma...@freebsd.org
 Status|Open|Closed

--- Comment #5 from Mark Johnston  ---
sio(4) has been removed from the tree.  Sorry that this didn't get attention
when it was submitted.

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


[Bug 280290] hms(4): Broken fresh after boot, fixed by resume

2024-10-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280290

--- Comment #25 from da...@catwhisker.org ---
(In reply to Edward Tomasz Napierala from comment #24)
Oh, excellent!  [Got lucky -- 7 decades or so of "breaking stuff" does come in
handy, at times]

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


[Bug 280290] hms(4): Broken fresh after boot, fixed by resume

2024-10-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280290

--- Comment #24 from Edward Tomasz Napierala  ---
Hah, good call with that ACPI thing.  This patch fixes it for me:

diff --git a/sys/dev/iicbus/iichid.c b/sys/dev/iicbus/iichid.c
index fc9f5c2a68b3..03b951b22878 100644
--- a/sys/dev/iicbus/iichid.c
+++ b/sys/dev/iicbus/iichid.c
@@ -1207,6 +1207,13 @@ iichid_attach(device_t dev)
 done:
(void)iichid_set_power(sc, I2C_HID_POWER_OFF);
sc->power_on = false;
+
+   error = iichid_set_power_state(sc, IICHID_PS_NULL, IICHID_PS_ON);
+   if (error != 0)
+   DPRINTF(sc, "Could not set power_state, error: %d\n", error);
+   else
+   DPRINTF(sc, "Successfully set power_state\n");
+
return (error);
 }

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


[Bug 238828] Possible build race: lib/libsysdecode/tables.h:948: error: 'IPV6_MIN_MEMBERSHIPS' undeclared

2024-10-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238828

Mark Johnston  changed:

   What|Removed |Added

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

--- Comment #8 from Mark Johnston  ---
I believe we haven't seen this particular build failure in a long time.

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


[Bug 149609] [panic] reboot after adding second default route

2024-10-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=149609

Mark Johnston  changed:

   What|Removed |Added

 CC||ma...@freebsd.org
 Status|Open|Closed
 Resolution|--- |Overcome By Events

--- Comment #4 from Mark Johnston  ---
Sorry that this didn't get attention when it was submitted.  I can't reproduce
any panics or reboots on main by adding multiple default routes (the second
route command always returns an error), and the RADIX_MPATH option is gone.  If
you can reproduce it on a supported FreeBSD release, please re-open.

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


[Bug 268736] FreeBSD boot stuck with comconsole in x86 Hyper-V Gen2

2024-10-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268736

Mark Johnston  changed:

   What|Removed |Added

 CC||ma...@freebsd.org

--- Comment #3 from Mark Johnston  ---
Is this still a problem with recent FreeBSD releases?

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


[Bug 269454] kernel fails to build when IPv6 disabled

2024-10-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=269454

Mark Johnston  changed:

   What|Removed |Added

 Resolution|--- |Overcome By Events
 Status|New |Closed
 CC||ma...@freebsd.org

--- Comment #1 from Mark Johnston  ---
This is worked around for now by not building irdma if INET6 support is
disabled in the kernel.  In particular, a "nooptions INET6" kernel builds
cleanly on stable/13.

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


[Bug 269521] split(1): add '-c' to continue creating files

2024-10-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=269521

Mark Johnston  changed:

   What|Removed |Added

 CC||ma...@freebsd.org
 Status|New |Closed
   Assignee|b...@freebsd.org|chris...@freebsd.org
 Resolution|--- |FIXED

--- Comment #2 from Mark Johnston  ---
(In reply to jschauma from comment #1)
This patch was committed as ac17fc816e67a4e5e2e481b5001577a8d589f8b6.

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


[Bug 269250] split(1): auto-extend suffix length if required

2024-10-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=269250

Mark Johnston  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 CC||ma...@freebsd.org
   Assignee|b...@freebsd.org|chris...@freebsd.org
 Status|New |Closed

--- Comment #2 from Mark Johnston  ---
This was committed as c4f7198f47c15eece849d06e8fdd1fb46ed43bba.

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


[Bug 269576] dtrace arm64: error on enabled probe ID 1 (ID 51902: vfs:vop:vop_read:entry): invalid address (0x0) in action #2 (IMPLEMENT ME: dtrace_getarg)

2024-10-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=269576

Mark Johnston  changed:

   What|Removed |Added

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

--- Comment #3 from Mark Johnston  ---
I believe this is fixed now, dtrace_getarg() was implemented in commit
bae00433f013c, and ustack() works properly on arm64 in my testing.

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


[Bug 254778] usr.sbin/pmc make buildworld error

2024-10-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254778

Mark Johnston  changed:

   What|Removed |Added

 Resolution|--- |Overcome By Events
 CC||ma...@freebsd.org
 Status|New |Closed

--- Comment #3 from Mark Johnston  ---
Sorry that this didn't get any attention.  The reproducer doesn't work for me
on main with llvm 19.  If you're still able to reproduce this on a supported
FreeBSD release, please reopen the bug with an updated reproducer.

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


[Bug 280290] hms(4): Broken fresh after boot, fixed by resume

2024-10-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280290

Mikael Urankar  changed:

   What|Removed |Added

 CC||mik...@freebsd.org

--- Comment #28 from Mikael Urankar  ---
(In reply to Edward Tomasz Napierala from comment #24)
it also fixes the issue for me.
Thank you.

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


WPI not working in i386 14.1 (and previously 14.0)

2024-10-27 Thread Christophe Prévotaux
Hello,


Some time ago I notice 2 of my laptops using WPI Intel(R) PRO/Wireless 3945ABG
Wifi interface ( old ) stopped working in versions 14.0 and 14.1 ( maybe before
but I had not noticed it before).


The Laptops are ACER TravelMate series.

Below are dmesg and dmidecode output if it can help 

---<>---
Copyright (c) 1992-2023 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 14.1-RELEASE releng/14.1-n267679-10e31f0946d8 GENERIC i386
FreeBSD clang version 18.1.5 (https://github.com/llvm/llvm-project.git
llvmorg-18.1.5-0-g617a15a9eac9) WARNING: 32-bit kernels are deprecated and may
be removed in FreeBSD 15.0. VT(vga): resolution 640x480
CPU: Genuine Intel(R) CPU   T2300  @ 1.66GHz (1666.87-MHz 686-class CPU)
  Origin="GenuineIntel"  Id=0x6e8  Family=0x6  Model=0xe  Stepping=8
  
Features=0xbfe9fbff
  Features2=0xc189
  AMD Features=0x10
  TSC: P-state invariant, performance statistics
real memory  = 2147483648 (2048 MB)
avail memory = 2071318528 (1975 MB)
Event timer "LAPIC" quality 100
ACPI APIC Table: 
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
FreeBSD/SMP: 1 package(s) x 2 core(s)
random: unblocking device.
ioapic0: MADT APIC ID 1 != hw id 2
ioapic0  irqs 0-23
Launching APs: 1
random: entropy device external interface
kbd1 at kbdmux0
vtvga0: 
smbios0:  at iomem 0xf67e0-0xf67fe
smbios0: Version: 2.4
aesni0: No AES or SHA support.
acpi0: 
ACPI Error: AE_NOT_FOUND, While resolving a named reference package element -
Z006 (20221020/dspkginit-605) ACPI Error: AE_NOT_FOUND, While resolving a named
reference package element - Z006 (20221020/dspkginit-605) acpi0: Power Button
(fixed) unknown: I/O range not supported
hpet0:  iomem 0xfed0-0xfed003ff irq 0,8 on acpi0
Timecounter "HPET" frequency 14318180 Hz quality 950
Event timer "HPET" frequency 14318180 Hz quality 450
Event timer "HPET1" frequency 14318180 Hz quality 440
Event timer "HPET2" frequency 14318180 Hz quality 440
cpu0:  on acpi0
atrtc0:  port 0x70-0x77 on acpi0
atrtc0: Warning: Couldn't map I/O.
atrtc0: registered as a time-of-day clock, resolution 1.00s
Event timer "RTC" frequency 32768 Hz quality 0
attimer0:  port 0x40-0x43,0x50-0x53 on acpi0
Timecounter "i8254" frequency 1193182 Hz quality 0
Event timer "i8254" frequency 1193182 Hz quality 100
Timecounter "ACPI-fast" frequency 3579545 Hz quality 900
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0
acpi_ec0:  port 0x62,0x66 on acpi0
pcib0:  port 0xcf8-0xcff on acpi0
pci0:  on pcib0
vgapci0:  port 0x1800-0x1807 mem
0xb008-0xb00f,0xc000-0xcfff,0xb004-0xb007 irq 16 at
device 2.0 on pci0 agp0:  on
vgapci0 WARNING: Device "agp" is Giant locked and may be deleted before FreeBSD
15.0. agp0: aperture size is 256M, detected 7932k stolen memory vgapci0: Boot
video device vgapci1:  mem 0xb010-0xb017 at
device 2.1 on pci0 hdac0:  mem
0xb000-0xb0003fff irq 22 at device 27.0 on pci0 pcib1:  at device 28.0 on pci0 pcib1: failed to allocate initial I/O port
bridge> window: 0-0xfff  
pcib1: failed to allocate initial memory window: 0-0xf
pcib1: failed to allocate initial prefetch window: 0-0xf
pci1:  on pcib1
wpi0:  at device 0.0 on pci1
pcib2:  irq 17 at device 28.1 on pci0
pcib2: failed to allocate initial I/O port window: 0-0xfff
pcib2: failed to allocate initial memory window: 0-0xf
pcib2: failed to allocate initial prefetch window: 0-0xf
pci2:  on pcib2
pci0:3:0:0: invalid VPD checksum 0xe
pci0:3:0:0: error accessing read-only VPD data
bge0: <, ASIC rev. 0x004101> irq 17 at device 0.0 on pci2
bge0: CHIP ID 0x4101; ASIC REV 0x04; CHIP REV 0x41; PCI-E
miibus0:  on bge0
brgphy0:  PHY 1 on miibus0
brgphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT,
1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto, auto-flow bge0:
Ethernet address: 00:16:36:5d:7c:65 pcib3:  at device 28.2
on pci0 pcib3: failed to allocate initial I/O port window: 0-0xfff
pcib3: failed to allocate initial memory window: 0-0xf
pcib3: failed to allocate initial prefetch window: 0-0xf
pcib4:  at device 28.3 on pci0
pcib4: failed to allocate initial I/O port window: 0-0xfff
pcib4: failed to allocate initial memory window: 0-0xf
pcib4: failed to allocate initial prefetch window: 0-0xf
uhci0:  port 0x1820-0x183f irq 23 at
device 29.0 on pci0 usbus0 on uhci0
usbus0: 12Mbps Full Speed USB v1.0
uhci1:  port 0x1840-0x185f irq 19 at
device 29.1 on pci0 usbus1 on uhci1
usbus1: 12Mbps Full Speed USB v1.0
uhci2:  port 0x1860-0x187f irq 18 at
device 29.2 on pci0 usbus2 on uhci2
usbus2: 12Mbps Full Speed USB v1.0
uhci3:  port 0x1880-0x189f irq 16 at
device 29.3 on pci0 usbus3 on uhci3
usbus3: 12Mbps Full Speed USB v1.0
ehci0:  mem 0xb0004000-0xb00043ff
irq 23 at device 29.7 on pci0 usbus4: EHCI version 1.0
usbus4 on ehci0
usbus4: 4