[Bug 269214] loader.efi(8) online: a space in an example command is misrepresented as a tab
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=269214 --- Comment #2 from Graham Perrin --- Initially, I copied from Firefox. The same problem (a tab character) is found with both pages when copying from Falkon. The tab is visible when pasting to e.g. Code - OSS. (In reply to Gordon Bergling from comment #1) Konsole, csh. With sh, the effect is different: root@mowa219-gjp4-8570p-freebsd:~ # mount | grep boot /dev/ada0p1 on /boot/efi (msdosfs, local) root@mowa219-gjp4-8570p-freebsd:~ # sh # cp/boot/loader.efi /boot/efi/efi/freebsd/loader.efi sh: cp/boot/loader.efi: not found # -- You are receiving this mail because: You are the assignee for the bug.
[Bug 269224] em(4): Intel I219-V (0x0DC8) is not detected by the driver
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=269224 Bug ID: 269224 Summary: em(4): Intel I219-V (0x0DC8) is not detected by the driver Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: b...@freebsd.org Reporter: osharo...@gmail.com One of the NICs on ASRosk Z790M-ITX, Intel I219-V specifically, is not detected by em(4) driver. The following patch makes it work though I didn't do much testing other than regular use and 20 minutes of iperf3. There are more device IDs in https://github.com/torvalds/linux/blob/master/drivers/net/ethernet/intel/e1000e/hw.h but I only have this specific device at hands to test. diff -ru /usr/src/sys/dev/e1000/e1000_api.c e1000/e1000_api.c --- /usr/src/sys/dev/e1000/e1000_api.c 2022-12-09 01:03:57.0 + +++ e1000/e1000_api.c 2023-01-26 00:33:49.0 + @@ -339,6 +339,7 @@ case E1000_DEV_ID_PCH_ADL_I219_V16: case E1000_DEV_ID_PCH_ADL_I219_LM17: case E1000_DEV_ID_PCH_ADL_I219_V17: + case E1000_DEV_ID_PCH_RPL_I219_V22: mac->type = e1000_pch_adp; break; case E1000_DEV_ID_PCH_MTP_I219_LM18: diff -ru /usr/src/sys/dev/e1000/e1000_hw.h e1000/e1000_hw.h --- /usr/src/sys/dev/e1000/e1000_hw.h 2022-12-09 01:03:57.0 + +++ e1000/e1000_hw.h2023-01-26 00:26:09.0 + @@ -175,6 +175,7 @@ #define E1000_DEV_ID_PCH_MTP_I219_V18 0x550B #define E1000_DEV_ID_PCH_MTP_I219_LM19 0x550C #define E1000_DEV_ID_PCH_MTP_I219_V19 0x550D +#define E1000_DEV_ID_PCH_RPL_I219_V22 0x0DC8 #define E1000_DEV_ID_82576 0x10C9 #define E1000_DEV_ID_82576_FIBER 0x10E6 #define E1000_DEV_ID_82576_SERDES 0x10E7 diff -ru /usr/src/sys/dev/e1000/if_em.c e1000/if_em.c --- /usr/src/sys/dev/e1000/if_em.c 2022-12-09 01:03:57.0 + +++ e1000/if_em.c 2023-01-26 00:27:29.0 + @@ -194,6 +194,7 @@ PVID(0x8086, E1000_DEV_ID_PCH_MTP_I219_V18, "Intel(R) I219-V MTP(18)"), PVID(0x8086, E1000_DEV_ID_PCH_MTP_I219_LM19, "Intel(R) I219-LM MTP(19)"), PVID(0x8086, E1000_DEV_ID_PCH_MTP_I219_V19, "Intel(R) I219-V MTP(19)"), + PVID(0x8086, E1000_DEV_ID_PCH_RPL_I219_V22, "Intel(R) I219-V RPL(22)"), /* required last entry */ PVID_END }; -- You are receiving this mail because: You are the assignee for the bug.
[Bug 269214] loader.efi(8) online: a space in an example command is misrepresented as a tab
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=269214 --- Comment #3 from Graham Perrin --- Created attachment 239782 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=239782&action=edit Screenshot: tab character copied from the web page, pasted to Notepad and Notepad++ (In reply to Gordon Bergling from comment #1) Reproducible at a different computer, running Windows 10. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 265383] FreeBSD 13.1 causes shutdown after upgrade ESXi VM TrueNAS CORE 12U8.1 to 13 - and then unable reboot
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265383 --- Comment #4 from alphe...@gmail.com --- There is thread regarding this issue on the TrueNAS forum: https://www.truenas.com/community/threads/truenas-will-not-boot-after-upgrade-to-13.101701/ The topic has had over 2k views so it seems that more than a handful of people could be impacted by this. Seems to happen with different HBAs across different ESXi versions where 12.x has been rock solid Wish that IXSystem Engineers would engage with the FreeBSD community to offer more help/info surrounding the issue. (Collecting logs pointing to a smoking gun is not that easy on TrueNAS) I've ran my current TrueNAS 12.x version for years without any issues. Steps to reproduce: - Install a VM with TrueNAS 12.x which has a passthrough HBA (I have a LSI SAS9211-8i). - Upgrade it to 13.x (I did a reinstall into a new boot environment and uploaded the save config ) - The VM crashes within a couple of minutes. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 269224] em(4): Intel I219-V (0x0DC8) is not detected by the driver
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=269224 --- Comment #1 from Oleg Sharoyko --- I also meant to add output of pciconf -lv em0@pci0:0:31:6:class=0x02 rev=0x11 hdr=0x00 vendor=0x8086 device=0x0dc8 subvendor=0x1849 subdevice=0x0dc8 vendor = 'Intel Corporation' class = network subclass = ethernet -- You are receiving this mail because: You are the assignee for the bug.
[Bug 269213] /etc/rc.d/cleanvar interaction with samba fdescfs mount causes file deletions outside of /var/run
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=269213 Graham Perrin changed: What|Removed |Added CC||grahamper...@freebsd.org Status|New |Open -- You are receiving this mail because: You are the assignee for the bug.
[Bug 265383] FreeBSD 13.1 causes shutdown after upgrade ESXi VM TrueNAS CORE 12U8.1 to 13 - and then unable reboot
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265383 --- Comment #5 from alphe...@gmail.com --- I also offer my setup: Running the TrueNAS Core VM on a SuperMicro X10SRA-F running ESXI 6.7 : Version: 6.7.0 Build: Releasebuild-20497097 Update: 3 Patch: 189 HBA installed in passthrough mode. view from the TrueNAS VM: sas2ircu 0 display LSI Corporation SAS2 IR Configuration Utility. Version 20.00.00.00 (2014.09.18) Copyright (c) 2008-2014 LSI Corporation. All rights reserved. Read configuration has been initiated for controller 0 Controller information Controller type : SAS2008 BIOS version: 7.37.00.00 Firmware version: 19.00.00.00 Channel description : 1 Serial Attached SCSI Initiator ID: 0 Maximum physical devices: 255 Concurrent commands supported : 3432 Slot: 238 Segment : 0 Bus : 11 Device : 0 Function: 0 RAID Support: No IR Volume information -- You are receiving this mail because: You are the assignee for the bug.
[Bug 269228] coretemp: incorrect tjmax for desktop and server Core 2 Duo/Xeon 51xx 2cores 65nm (Conroe, Woodcrest, possible Allendale): 85°C, but must be 100°C
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=269228
Bug ID: 269228
Summary: coretemp: incorrect tjmax for desktop and server Core
2 Duo/Xeon 51xx 2cores 65nm (Conroe, Woodcrest,
possible Allendale): 85°C, but must be 100°C
Product: Base System
Version: 13.1-RELEASE
Hardware: amd64
OS: Any
Status: New
Severity: Affects Some People
Priority: ---
Component: kern
Assignee: b...@freebsd.org
Reporter: v...@unislabs.com
FreeBSD 13.1-p amd64.
On some Core 2 Duo and "same" Xeons I found very low temperature.
For example 13°C on CPU cores in server room with 16°C air temperature, or 33°C
on desktop with 28°C in room. In same server room Core 2 Quad, Core i7 920/930,
Xeon X3430, Xeon 3104 have temperature from 24 to 50.
I started explore.
dev.cpu.X.temperature = dev.cpu.X.coretemp.tjmax - dev.cpu.X.coretemp.delta
For other Core 2 Quad Q6600 tjmax = 100, but for Core 2 Duo 85 - weird…
Check sources: https://cgit.freebsd.org/src/tree/sys/dev/coretemp/coretemp.c
if ((cpu_model == 0xf && cpu_stepping >= 2) || cpu_model == 0xe) {
/*
* On some Core 2 CPUs, there's an undocumented MSR that
* can tell us if Tj(max) is 100 or 85.
*
* The if-clause for CPUs having the MSR_IA32_EXT_CONFIG was
adapted
* from the Linux coretemp driver.
*/
msr = rdmsr(MSR_IA32_EXT_CONFIG);
if (msr & (1 << 30))
sc->sc_tjmax = 85;
} else if (cpu_model == 0x17) {
Open linux driver:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/hwmon/coretemp.c
/*
* Now we can detect the mobile CPU using Intel provided table
* http://softwarecommunity.intel.com/Wiki/Mobility/720.htm
* For Core2 cores, check MSR 0x17, bit 28 1 = Mobile CPU
*/
err = rdmsr_safe_on_cpu(id, 0x17, &eax, &edx);
if (err) {
dev_warn(dev,
"Unable to access MSR 0x17, assuming desktop"
" CPU\n");
usemsr_ee = 0;
} else if (c->x86_model < 0x17 && !(eax & 0x1000)) {
/*
* Trust bit 28 up to Penryn, I could not find any
* documentation on that; if you happen to know
* someone at Intel please ask
*/
usemsr_ee = 0;
} else {
Look like very different logic - use different MSR.
I think FreeBSD's coretemp have incorrect check of tjmax for Conroe.
I'll do more test a bit later with Linux and FreeBSD on different CPUs - Core 2
Duo E6xxx/E4xxx, Pentium Dual-Core E2xxx, and on Wolfdale Core 2 Duo E7xxx.
I want to try, but I can't promise to do this: apply Linux's logic with MSR
0x17 (MSR_IA32_PLATFORM_ID) to coretemp and test it on my hardware.
P.S. I hope my poor english won't hurt to understand me…
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 269228] coretemp: incorrect tjmax for desktop and server Core 2 Duo/Xeon 51xx 2cores 65nm (Conroe, Woodcrest, possible Allendale): 85°C, but must be 100°C
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=269228
--- Comment #1 from VVD ---
Oh, look here:
if (usemsr_ee) {
err = rdmsr_safe_on_cpu(id, 0xee, &eax, &edx);
if (err) {
dev_warn(dev,
"Unable to access MSR 0xEE, for Tjmax, left"
" at default\n");
} else if (eax & 0x4000) {
tjmax = tjmax_ee;
}
} else if (tjmax == 10) {
/*
* If we don't use msr EE it means we are desktop CPU
* (with exeception of Atom)
*/
dev_warn(dev, "Using relative temperature scale!\n");
}
So on desktop CPU not need to use MSR 0xEE (MSR_IA32_EXT_CONFIG) at all.
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 269233] Randomly is kernel is not rebooting
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=269233 Bug ID: 269233 Summary: Randomly is kernel is not rebooting Product: Base System Version: 12.2-STABLE Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: b...@freebsd.org Reporter: parulinux...@gmail.com I am calling a /bin/reboot -zn i have also set sysctl kern.force_kmod_shutdown=1 Randomly system is not rebooting.I see from the boot logs that below logs are NOT available in non working scenario kernel: <197.997519> Waiting (max 16 seconds) for system process `vnlru' to stop... done kernel: <197.997555> Waiting (max 16 seconds) for system thread `bufdaemon' to stop... done kernel: <198.002077> Waiting (max 16 seconds) for system thread `bufspacedaemon-0' to stop... done kernel: <198.550654> Waiting (max 16 seconds) for system thread `bufspacedaemon-1' to stop... done instead of "reboot -zn" will "shutdown -r now" might work consistently ?? -- You are receiving this mail because: You are the assignee for the bug.
Problem reports for b...@freebsd.org that need special attention
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 |198797 | [PATCH] Added an option to install BSDstats to bs 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 41 problems total for which you should take action.
[Bug 261657] stat(1) patch: Fix error message formatting
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261657 Xin LI changed: What|Removed |Added CC||delp...@freebsd.org Assignee|b...@freebsd.org|delp...@freebsd.org Status|New |In Progress -- You are receiving this mail because: You are the assignee for the bug.
[Bug 266224] Could some sort of file transfer program be put in /rescue?
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266224 Xin LI changed: What|Removed |Added CC||delp...@freebsd.org Assignee|b...@freebsd.org|delp...@freebsd.org -- You are receiving this mail because: You are the assignee for the bug.
[Bug 256902] libfetch breaks usage of certctl managed store when security/ca_root_nss is installed
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256902 Xin LI changed: What|Removed |Added Assignee|b...@freebsd.org|d...@freebsd.org CC||delp...@freebsd.org, ||s...@freebsd.org -- You are receiving this mail because: You are the assignee for the bug.
[Bug 269224] em(4): Intel I219-V (0x0DC8) is not detected by the driver
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=269224 Mark Linimon changed: What|Removed |Added Keywords||IntelNetworking Assignee|b...@freebsd.org|n...@freebsd.org -- You are receiving this mail because: You are the assignee for the bug.
[Bug 267782] AMD Ryzen 5 hangs on 13.1, fine on 12.3
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267782 Mark Linimon changed: What|Removed |Added Keywords||regression -- You are receiving this mail because: You are the assignee for the bug.
[Bug 269133] bnxt(4): BCM57416 - HWRM_CFA_L2_SET_RX_MASK command returned RESOURCE_ALLOC_ERROR error
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=269133 --- Comment #3 from Santiago Martinez --- Seems that the following commit is the one causing the issue. if_bnxt: Add support for VLAN on Thor: 2db35273502b3c35aa653effc5c97618567367ab Went back to 13.1 and started applying each of the commits on stable/13 for bnxt. After doing a cherry-pick on "if_bnxt: Add support for VLAN on Thor" the NIC stop working. Reverting it, make the card to work again. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 265923] freebsd-update: Fails to upgrade i386 13.0-p11 to 13.1-RELEASE: incorrect hash.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265923 Eugene Grosbein changed: What|Removed |Added CC||eu...@freebsd.org Status|New |Closed Resolution|--- |FIXED --- Comment #2 from Eugene Grosbein --- Reportedly fixed. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 264030] [tracking] 13.1-RELEASE issue reports
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264030 Bug 264030 depends on bug 265923, which changed state. Bug 265923 Summary: freebsd-update: Fails to upgrade i386 13.0-p11 to 13.1-RELEASE: incorrect hash. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265923 What|Removed |Added Status|New |Closed Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
