[Bug 283218] Panic while writting on mdconfig file stored on ZFS panic since zfs: merge openzfs/zfs@b10992582
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283218 Bug ID: 283218 Summary: Panic while writting on mdconfig file stored on ZFS panic since zfs: merge openzfs/zfs@b10992582 Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: b...@freebsd.org Reporter: oliv...@freebsd.org Attachment #255733 text/plain mime type: Created attachment 255733 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=255733&action=edit script trying to reproduce the panic Since commit "7a7741af18d6c8a804cc643cb7ecda9d730c6aa6" (zfs: merge openzfs/zfs@b10992582), all my Jenkins builders are crashing while preparing bhyve VM for regression tests. The servers are using zpool, mdconfig mount disk image to patch it for regression tests and crash while writting on it. I’ve tried to wrote a regression test script, but this isn’t working at 100% rate, because it seems it need a zpool with "some" history. Was able to reproduce on x86 (hardware and VM) and ARM (VM) with any kind of zpool (non-raid, zmirror and raidz). Attached a shell script that should reproduce it, but this script is a lot more efficient to crash if pointing to an "existing" zpool (with some history): ./zfscrash.sh -z existing-zpool-name -- You are receiving this mail because: You are the assignee for the bug.
[Bug 283218] Panic while writting on mdconfig file stored on ZFS panic since zfs: merge openzfs/zfs@b10992582
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283218 Olivier Cochard changed: What|Removed |Added Assignee|b...@freebsd.org|m...@freebsd.org -- You are receiving this mail because: You are the assignee for the bug.
[Bug 283163] kill -SIG -1 does not work any more for host - which leads to inconsistent reboot
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283163 --- Comment #10 from Konstantin Belousov --- (In reply to vova from comment #9) prison_proc_iterate() iterates over all processes belonging to the argument prison. This implicitly includes all processes belonging to the children prisons. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 283214] Unable to reproduce release tarballs
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283214 Mark Linimon changed: What|Removed |Added Component|bin |misc CC||r...@freebsd.org -- You are receiving this mail because: You are the assignee for the bug.
[Bug 283163] kill -SIG -1 does not work any more for host - which leads to inconsistent reboot
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283163 --- Comment #9 from v...@fbsd.ru --- (In reply to Konstantin Belousov from comment #8) Yes, I understand it, but, prison0 is different from other jails, i.e. `ps ax` in prison0 - shows processes from all jails, and normaly kill from prison0 will successfuly send a signal to process in other jail. # sysctl security.jail.param.jid security.jail.param.jid: 0 # ps axJ4 -o jid,pid,tty,state,command JID PID TTY STAT COMMAND 4 10800 - SNsJ /usr/sbin/syslogd -ss -c 4 10833 - INsJ /usr/sbin/cron -s 4 10869 - INsJ nginx: master process /usr/local/sbin/nginx 4 55913 - INJ nginx: worker process (nginx) 4 55914 - INJ nginx: worker process (nginx) 4 55915 - INJ nginx: worker process (nginx) 4 55916 - INJ nginx: worker process (nginx) 4 55917 - INJ nginx: worker process (nginx) 4 55918 - INJ nginx: worker process (nginx) 4 55919 - INJ nginx: worker process (nginx) 4 55920 - INJ nginx: worker process (nginx) # kill -15 10869 # ps axJ4 -o jid,pid,tty,state,command JID PID TTY STAT COMMAND 4 10800 - INsJ /usr/sbin/syslogd -ss -c 4 10833 - SNsJ /usr/sbin/cron -s # so, for prison0, prison_proc_iterate() will go only through processes of prison0 or through all system processes? if the first, then kill(sig, -1) will not sent signal to processes in other jails, if the second, then I've confused with name prison_proc_iterate() (that is why I am askin) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 283123] loading i915kms causes black screen on Lenovo X1 carbon gen 8
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283123 Kevin Zheng changed: What|Removed |Added CC||kevinz5...@gmail.com --- Comment #11 from Kevin Zheng --- I just ran into this issue upgrading from 14.1 to 14.2 and was in for a surprise. It felt like the machine had hung on boot, even though now I realize that it was just a frozen text console. To solve this problem I tried to uninstall the packages and reinstall from ports, however I'm still getting this issue with the text console hanging. I ran: # pkg delete drm-kmod # pkg autoremove Then verified that the gpu-firmware* and drm-*-kmod packages were gone. I then reinstalled just drm-61-kmod and gpu-firmware-intel-kmod-kabylake by compiling from ports: # cd /usr/ports/graphics/drm-61-kmod && make install # cd /usr/ports/graphics/gpu-firmware-intel-kmod && make FLAVOR=kabylake install I rebooted but still run into the text console frozen issue. I can of course still bindly log in and startx. Is there another port that I forgot to rebuild? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 283090] kernel panic on kldload i915kms on clean 14.2-RELEASE install
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283090 --- Comment #3 from shivars --- (In reply to Ed Maste from comment #1) Hi, thank you. I had seen the posts about the 14.2 issues and didn't think it would apply - given I had the same crash on 14.1 before updating (before 1.42 was released); 14.1 was the vanilla unmodified install before upgrading to 14.2 to see if that would solve the problem (not realising at the time that this may further break things given the .X/EOL thing). I'll try it though, in case that's a later version of drm-kmod and perhaps the issue is solved there. Will report back. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 192839] Duplicate entries in an mtree file cause nmtree to coredump
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192839 Jose Luis Duran changed: What|Removed |Added Status|New |In Progress --- Comment #8 from Jose Luis Duran --- The bug has been reported upstream, with a very naive workaround that can be used in the meantime a real fix is issued. https://gnats.netbsd.org/cgi-bin/query-pr-single.pl?number=58887 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 199075] mtree -F freebsd9 not consistent with fmtree
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199075 Jose Luis Duran changed: What|Removed |Added Assignee|b...@freebsd.org|jldu...@freebsd.org -- You are receiving this mail because: You are the assignee for the bug.
[Bug 192839] Duplicate entries in an mtree file cause nmtree to coredump
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192839 Jose Luis Duran changed: What|Removed |Added Assignee|b...@freebsd.org|jldu...@freebsd.org -- You are receiving this mail because: You are the assignee for the bug.
[Bug 181636] mtree(8): mtree -U does not fix ownership of symbolic links
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=181636 Jose Luis Duran changed: What|Removed |Added Assignee|b...@freebsd.org|jldu...@freebsd.org -- You are receiving this mail because: You are the assignee for the bug.
[Bug 28424] mtree(8) fails to report directory hierarchy mismatch
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=28424 Jose Luis Duran changed: What|Removed |Added Assignee|b...@freebsd.org|jldu...@freebsd.org -- You are receiving this mail because: You are the assignee for the bug.
[Bug 28424] mtree(8) fails to report directory hierarchy mismatch
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=28424 Jose Luis Duran changed: What|Removed |Added CC||jldu...@freebsd.org Status|Open|In Progress --- Comment #10 from Jose Luis Duran --- This bug is still reproducible (with NetBSD's mtree (nmtree): # mkdir -p testdir/bar # mtree -cd -R time -p testdir >output # rm -fr testdir/bar # mtree -d -f output -p testdir && echo 'hierarchy matches spec' ./bar missing hierarchy matches spec A simple patch has been proposed upstream: https://gnats.netbsd.org/cgi-bin/query-pr-single.pl?number=58886 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 282156] page fault while in kernel mode after 14.0-Release to 14.1-Release upgrade
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282156 --- Comment #10 from tfag...@brozs.net --- (In reply to Rick Macklem from comment #9) Hello, I've disabled nfcbd and reupgraded the two nodes, it seems stable for now. Thanks for your help Regards Thomas -- You are receiving this mail because: You are the assignee for the bug.
[Bug 283214] Unable to reproduce release tarballs
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283214 --- Comment #3 from Ed Maste --- (In reply to Colin Percival from comment #2) > We can probably use `find | sort | tar -c -nT-` as an alternative to adding > functionality to bsdtar. That's a good suggestion and looks like a suitable interim solution. I'd still want the functionality in bsdtar though. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 199075] mtree -F freebsd9 not consistent with fmtree
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199075 Jose Luis Duran changed: What|Removed |Added Status|New |In Progress --- Comment #3 from Jose Luis Duran --- Submitted upstream: https://gnats.netbsd.org/cgi-bin/query-pr-single.pl?number=58885 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 283123] loading i915kms causes black screen on Lenovo X1 carbon gen 8
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283123 --- Comment #12 from Michael --- (In reply to Daniel Tameling from comment #10) I think I read somewhere that kernel modules need the kernel source for it to compile (don’t have them installed as I didn’t need them until upgrading to 14.2). Could that be the reason why I get the build errors when compiling drm-kmod? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 283214] Unable to reproduce release tarballs
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283214 Ed Maste changed: What|Removed |Added CC||ema...@freebsd.org --- Comment #1 from Ed Maste --- GNU tar supports a --sort option (--sort=name); bsdtar has no such option yet. There is an old proof-of-concept patch with some commentary: https://github.com/libarchive/libarchive/issues/602. We'll have to figure out how to add this functionality to bsdtar. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 267028] kernel panics when booting with both (zfs,ko or vboxnetflt,ko or acpi_wmi.ko) and amdgpu.ko
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267028 --- Comment #189 from George Mitchell --- ALL of the messages you cited occur all of the time. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 283214] Unable to reproduce release tarballs
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283214 Mark Linimon changed: What|Removed |Added Keywords||reproducible-builds -- You are receiving this mail because: You are the assignee for the bug.
[Bug 236081] [release][reproducibility] ISO images and memstick images are not build reproducible
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236081 Mark Linimon changed: What|Removed |Added Keywords||reproducible-builds -- You are receiving this mail because: You are the assignee for the bug.
[Bug 283214] Unable to reproduce release tarballs
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283214 Colin Percival changed: What|Removed |Added CC||cperc...@freebsd.org --- Comment #2 from Colin Percival --- We can probably use `find | sort | tar -c -nT-` as an alternative to adding functionality to bsdtar. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 211897] horrible time skew under 10.3-R-p7 (seen once, not reproduced since)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211897 Mark Linimon changed: What|Removed |Added Assignee|b...@freebsd.org|lini...@freebsd.org Status|New |Closed Resolution|--- |Overcome By Events --- Comment #9 from Mark Linimon --- ^Triage: I'm sorry that no one ever took a look at this PR. However, without a reproducer, and given that FreeBSD 10 is long out of support, I do not think there is anything we can do here. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 267028] kernel panics when booting with both (zfs,ko or vboxnetflt,ko or acpi_wmi.ko) and amdgpu.ko
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267028 --- Comment #191 from Mark Millard --- (In reply to John F. Carr from comment #190) Note the attachment named "Crash without any use of ZFS, with acpi_wmi" ( see also comment #107 and "Relevant part of /var/log/messages" ). There is not even the likes of: ZFS filesystem version: 5 ZFS storage pool version: features support (5000) in the log, much less a backtrace with zfs content. Also, "Latest crash dump" is one that makes no mention of ZFS in its backtraces, as I remember. Each exposes-failure context had a similar "does not need to be in the backtrace for a failure to occur" status, at least given other example failure-reporting code was involved. My memory of the history was that failure never happened without drm-510-kmod being in use but the initial exposure of the problem was never via a backtrace involving drm-510-kmod . -- You are receiving this mail because: You are the assignee for the bug.
[Bug 267028] kernel panics when booting with both (zfs,ko or vboxnetflt,ko or acpi_wmi.ko) and amdgpu.ko
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267028 --- Comment #190 from John F. Carr --- >From the stack trace: #7 #8 avl_destroy_nodes (tree=tree@entry=0xf8001b6c0420, cookie=cookie@entry=0xfe00b3bcddd0) at /usr/src/sys/contrib/openzfs/module/avl/avl.c:1023 I used to have a repeatable crash with a bad pointer in ZFS AVL code. See bug #268909. Eventually it went away, whether due to disk data changes or bug fixes I can't say. I did not have any graphics drivers loaded. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 283112] New Cache files packed into the FreeBSD14.2 release ISO file but not into Beta3 ISO files
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283112 --- Comment #6 from Mark Johnston --- We're getting an exception here: 1152 try: 1153 new_record.parent.track_child(new_record, 1154 self.logical_block_size) 1155 except pycdlibexception.PyCdlibInvalidInput: 1156 # dir_record.track_child() may throw a PyCdlibInvalidInput 1157 # if it was given a duplicate child. However, we allow 1158 # duplicate children if and only if this record is a file 1159 # and the last file has the same name; this represents a 1160 # very large file. 1161 if new_record.is_dir() or last_record is None or last_record.file_identifier() != new_record.file_identifier(): 1162 raise I reproduced the problem locally and found back-to-back duplicate names "WIFI_FIRMWARE_RTW88_KMOD_RTW87". Normally the exception would be ignored, but new_record.is_dir() is true. However, none of the files in var/cache/pkg in the ISO are directories, so I tend to suspect that there's a bug in pycdlib. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 283214] Unable to reproduce release tarballs
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283214 --- Comment #5 from Ed Maste --- GNU tar also supports --mtime to address that issue. The reproducible builds project has info on archive metadata in general: https://reproducible-builds.org/docs/archives/ -- You are receiving this mail because: You are the assignee for the bug.
[Bug 283214] Unable to reproduce release tarballs
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283214
--- Comment #4 from Pat Maddox ---
Yep, I was playing with find sort last night, and got that piece working. It
looks like this:
find -s . > ${WORLDTMP}/package-${dist}-files; \
${TAR_CMD} cnvf - --exclude usr/lib/debug -T
${WORLDTMP}/package-${dist}-files | \
mtimes are another source of non-determinism.
https://download.freebsd.org/releases/amd64/14.2-RELEASE/kernel.txz has 338
unique timestamps in it.
It wasn't clear to me how to adjust those. I put a `touch -A` in the places I
thought it should go, but I didn't get that working - and don't know if that
would be desirable anyway.
What I can do for now is determine what transformations are needed to make two
tarballs equivalent. I suspect it's only the order and times - I can't think of
what else there would be. But I can confirm that and report back, and then
figure out what comes next.
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 283214] Unable to reproduce release tarballs
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283214 --- Comment #6 from Colin Percival --- I'd suggest constructing an mtree file (aka METALOG) and then passing that to the tarball creation. That will let you specify the mtime you want. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 283224] zpool import concurrent imports will deadlock
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283224 Bug ID: 283224 Summary: zpool import concurrent imports will deadlock Product: Base System Version: 13.4-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: b...@freebsd.org Reporter: grau_s...@md5hashing.net Created attachment 255744 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=255744&action=edit procstat -kka with redacted mounts/zvols/pools A 'zpool import pool1 &' followed by 'zpool import pool2 &' resulted in neither returning and subsequent zpool commands also not returning. pool1 base dataset was mounted and accessible, but other datasets were not. pool2 did not seem to have gotten datasets mounted. Both pools were multiple disk pools, but the pool2 was a mirror with only 1 drive available, requiring a complete dev search. Kernel was 13.4p1 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 283226] [PUC] [PATCH] Add support for PUC devices
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283226 Bug ID: 283226 Summary: [PUC] [PATCH] Add support for PUC devices Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: b...@freebsd.org Reporter: ca...@live.co.uk Created attachment 255747 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=255747&action=edit Patch Add support for a range of PCI/PCIe serial cards. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 283214] Unable to reproduce release tarballs
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283214 Brooks Davis changed: What|Removed |Added CC||bro...@freebsd.org --- Comment #7 from Brooks Davis --- I wonder if we should (at least in the REPRODUCIBLE_BUILDS case) be inserting a fixed mtime into a METALOG regardless. We should not be relying on file system ownership or permissions for packaging anyway since we should not need root to make packages. (The word "should" may be carrying a long of load in that statement...) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 283110] freebsd-update IDS vs. installed permissions for kernels (444 vs 555)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283110 --- Comment #8 from w...@psr.com --- (In reply to John Baldwin from comment #7) > ... you'd have to have some way to know what the distribution metadata is ... My impression (possibly wrong, since I haven't read the code) is that freebsd-update pulls in copies of the distributions for both the old and new release, and that that's how UpdateIfUnmodified is able to determine whether the file has been modified. If distributions include permissions, then there's enough information for a permission comparison. Unfortunately, I now see that this won't work when KeepModifiedMetadata is true and >1 release has been installed since the permission/metadata change, since the distribution-change will then look like a user-change from the previous distribution. > Possibly this could just be handled as a special case in freebsd-update > though as files rarely change metadata like permissions. That may well turn out to be easier, faster, and work in more situations. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 144659] [pcm] The distortion of the sound playback of music at high volume levels.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=144659 --- Comment #9 from Christos Margiolis --- Testing on -CURRENT, as well as 14.2-RELEASE with snd_uaudio(4) and snd_hda(4), and I do not see this issue. Are you sure that the volume doesn't get so high after setting vpc0_db to 4, that your audio simply starts clipping because it's too loud? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 283214] Unable to reproduce release tarballs
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283214 --- Comment #8 from Pat Maddox --- Okay I have a proof of concept that I can put on Phab. I think it's appropriate to put WIP on Phab to get feedback, and iterate - correct? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 283110] freebsd-update IDS vs. installed permissions for kernels (444 vs 555)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283110 --- Comment #7 from John Baldwin --- I suspect some of the difficulty is that you'd have to have some way to know what the distribution metadata is so you can recognize what a difference is between the new file and the existing file, and we probably don't store that information locally on the host. Possibly this could just be handled as a special case in freebsd-update though as files rarely change metadata like permissions. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 283112] New Cache files packed into the FreeBSD14.2 release ISO file but not into Beta3 ISO files
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283112 --- Comment #10 from Yanhui He --- (In reply to Mark Johnston from comment #6) Hi Mark, https://github.com/clalancette/pycdlib/blob/master/CHANGELOG https://pypi.org/project/pycdlib/1.3.2/#history The latest version of pycvdlib is 1.14.0 and it was released on Jan 15, 2023. There is no change between FreeBSD 14.2 BETA3 and RC1 release. Thanks! Yanhui -- You are receiving this mail because: You are the assignee for the bug.
[Bug 283112] New Cache files packed into the FreeBSD14.2 release ISO file but not into Beta3 ISO files
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283112 Keira Zhang changed: What|Removed |Added CC||qi-keira.zh...@broadcom.com --- Comment #11 from Keira Zhang --- (In reply to Mark Johnston from comment #6) Hi Mark, Thanks for helping to address the issue. I found more clues. It was directory /usr/local/share/licenses/wifi-firmware-rtw88-kmod-rtw8723d-20241017_1 caused the exception. https://github.com/clalancette/pycdlib/blob/master/pycdlib/dr.py#L214 didn't return a correct file identifier length, which led to the file identifier be identified as WIFI_FIRMWARE_RTW88_KMOD_RTW87 for this directory. As /usr/local/share/licenses/wifi-firmware-rtw88-kmod-rtw8703b-20241017_1 had been identified as WIFI_FIRMWARE_RTW88_KMOD_RTW87 already, adding directory wifi-firmware-rtw88-kmod-rtw8723d-20241017_1 identifier caused the duplicate name exception. We are using pycdlib to inserting /etc/installerconfig to the FreeBSD ISO for unattended installation. This issue blocks our weekly regression testing for FreeBSD 14.2 GA release. Can you please give us some advice about how we can work around the issue? Thanks very much! -- You are receiving this mail because: You are the assignee for the bug.
[Bug 283112] New Cache files packed into the FreeBSD14.2 release ISO file but not into Beta3 ISO files
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283112 --- Comment #12 from Keira Zhang --- Sorry, it was not https://github.com/clalancette/pycdlib/blob/master/pycdlib/dr.py#L214 because the record used here is from https://github.com/clalancette/pycdlib/blob/master/pycdlib/pycdlib.py#L1051 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 283231] Intel Coffee Lake (Intel HD Graphics 630) + drm_kmod broken in 14.2
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283231 Bug ID: 283231 Summary: Intel Coffee Lake (Intel HD Graphics 630) + drm_kmod broken in 14.2 Product: Base System Version: 14.2-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: b...@freebsd.org Reporter: s...@seanmarkham.com Intel Coffee Lake (Intel HD Graphics 630) + drm_kmod broken in 14.2 I have been encountering some issues trying to run anything Xorg-related using the drm_kmod drivers (sysrc kld_list+=i915kms) on a brand-new install of FBSD 14.2-Release. Attempting to run startx or xinit produces an error "Cannot run in framebuffer mode" (instead of the X session starting). Said error code is similar to the one posted on this SE post (https://unix.stackexchange.com/questions/615263/cannot-run-in-framebuffer-mode-please-specify-busids), but I don't have the exact one because of the way I fixed it. Fix: reinstalling on FBSD 14.1-RELEASE seems to do the trick. ~~Technical Specs: (after reverting to 14.1) ````sean@seanBSDv ` `.---...--.``` -/ - +o .--` /y:` +.Host: 30C7001GUS (ThinkStation P330) yo`:.:o `+- Kernel: FreeBSD 14.1-RELEASE y/ -/` -o/ Uptime: 7 mins .- ::/sy+:. Packages: 680 (pkg) / `-- / Shell: zsh 5.9 `: :`Display (MSI MP223 E2): 1920x1080 @ 60 Hz i] `: :`DE: Mate 1.28.1 / / WM: Marco (X11) .--. WM Theme: TraditionalOk -- -. Theme: TraditionalOk [GTK2/3/4] `:` `:` Icons: mate [GTK2/3/4] .-- `--. Font: Sans (10pt) [GTK2/3/4] .---..Cursor: mate (24px) Terminal: mate-terminal 1.28.1 Terminal Font: Monospace (10pt) CPU: Intel(R) Core(TM) i5-8500 (6) @ 4.10 Gz GPU: Intel UHD Graphics 630 [Integrated] Memory: 4.34 GiB / 7.80 GiB (56%) Swap: 0 B / 8.00 GiB (0%) Disk (/): 3.57 GiB / 421.70 GiB (1%) - zfs Disk (/zroot): 96.00 KiB / 418.14 GiB (0%) s Local IP (em0): 192.168.1.161/24 Locale: C.UTF-8 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 283112] New Cache files packed into the FreeBSD14.2 release ISO file but not into Beta3 ISO files
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283112 --- Comment #8 from Yanhui He --- (In reply to Mark Johnston from comment #6) Hi Mark, AFAIK, PyCdlib doesn't have change in recent months. It's OK for FreeBSD 14.2 Beta3 ISO Image, and failed since FreeBSD 14.2 RC1 release. Thanks! Yanhui -- You are receiving this mail because: You are the assignee for the bug.
[Bug 283163] kill -SIG -1 does not work any more for host - which leads to inconsistent reboot
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283163 --- Comment #11 from commit-h...@freebsd.org --- A commit in branch stable/14 references this bug: URL: https://cgit.FreeBSD.org/src/commit/?id=b50851e8ebfa8acc77607a4ff1095ed6e4a56881 commit b50851e8ebfa8acc77607a4ff1095ed6e4a56881 Author: Konstantin Belousov AuthorDate: 2024-12-06 17:01:00 + Commit: Konstantin Belousov CommitDate: 2024-12-10 02:40:24 + prison_proc_iterate(): make it work for prison0 PR: 283163 (cherry picked from commit 831531a82e0f1d1d7b97e50c0587639322ed8d2e) sys/kern/kern_jail.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 283112] New Cache files packed into the FreeBSD14.2 release ISO file but not into Beta3 ISO files
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283112 --- Comment #9 from Yanhui He --- (In reply to Bjoern A. Zeeb from comment #7) Thanks Bjoern! If the change will be released, can we have a semi-rnaomd release DVD image without the var/cache files (not directories)? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 283112] New Cache files packed into the FreeBSD14.2 release ISO file but not into Beta3 ISO files
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283112 --- Comment #7 from Bjoern A. Zeeb --- (In reply to Yanhui He from comment #5) Not from me but people working on the cleanup at least: https://reviews.freebsd.org/D47942 Should be possible to quickly create a semi-rnaomd release DVD image without the var/cache files (not directories) to see if markj's theory holds up but given the names Mark got I would not be surprised by a bug somewhere else as well. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 283224] zpool import concurrent imports will deadlock
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283224 Mark Linimon changed: What|Removed |Added Assignee|b...@freebsd.org|f...@freebsd.org -- You are receiving this mail because: You are the assignee for the bug.
[Bug 283214] Unable to reproduce release tarballs
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283214 Pat Maddox changed: What|Removed |Added URL||https://reviews.freebsd.org ||/D48010 -- You are receiving this mail because: You are the assignee for the bug.
