[Bug 235549] [nullfs] panic: Don't call insmntque(foo, NULL)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235549 Bug ID: 235549 Summary: [nullfs] panic: Don't call insmntque(foo, NULL) Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Keywords: stress2 Severity: Affects Only Me Priority: --- Component: kern Assignee: b...@freebsd.org Reporter: p...@freebsd.org nullfs(5) stress test scenario. panic: Don't call insmntque(foo, NULL) cpuid = 1 time = 1549366443 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x47/frame 0xfe00b98fe610 vpanic() at vpanic+0x20c/frame 0xfe00b98fe670 panic() at panic+0x43/frame 0xfe00b98fe6d0 insmntque1() at insmntque1+0x306/frame 0xfe00b98fe720 null_nodeget() at null_nodeget+0x1a1/frame 0xfe00b98fe790 null_vptocnp() at null_vptocnp+0x15d/frame 0xfe00b98fe7f0 VOP_VPTOCNP_APV() at VOP_VPTOCNP_APV+0xee/frame 0xfe00b98fe820 vn_vptocnp() at vn_vptocnp+0x136/frame 0xfe00b98fe8b0 vn_fullpath1() at vn_fullpath1+0x1c0/frame 0xfe00b98fe920 kern___getcwd() at kern___getcwd+0xf9/frame 0xfe00b98fe980 amd64_syscall() at amd64_syscall+0x45e/frame 0xfe00b98feab0 https://people.freebsd.org/~pho/stress/log/crossmp4.txt -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 235550] i915kms.ko disables console view
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235550 Bug ID: 235550 Summary: i915kms.ko disables console view Product: Base System Version: 12.0-STABLE Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: b...@freebsd.org Reporter: b...@volki.at When i915kms.ko is loaded, no matter whether it is the one from the base system (/boot/kernel/i915kms.ko) or from the drm-legacy-kmod (version g20190109) port (/boot/modules/i915kms.ko), the system consoles can no more be seen. Apart from the display problem, the consoles remain functional. Text input is still possible. The error may be caused by either i915kms.ko or /boot/kernel/drm2.ko, which seems to be loaded automatically with i915kms.ko. When i915kms.ko is loaded manually from the console, the screen gets black. When it is loaded automatically on xinit, the console is hidden anyway. Switching to the console with ctrl-alt-F1/F2... leads to a distorted screen. Switching back to X works properly. When X terminates, the screen gets black. GPU is Intel Haswell 4600 (part of Intel Core i7-4790S CPU). See my comments in #217689 for further details. As opposed to the classification of that previous bug, the issue is not X11 related, as it can be observed without X11 as well. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 235550] i915kms.ko disables console view
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235550 Mark Linimon changed: What|Removed |Added See Also||https://bugs.freebsd.org/bu ||gzilla/show_bug.cgi?id=2176 ||89 -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 235550] i915kms.ko disables console view
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235550 Mark Linimon changed: What|Removed |Added Keywords||i915 -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 235549] [nullfs] panic: Don't call insmntque(foo, NULL)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235549 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. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 235489] llan driver causes fatal kernel trap: 0x300 (data storage interrupt) when system is low on memory
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235489 Leandro Lupori changed: What|Removed |Added Resolution|--- |FIXED Status|New |Closed -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 229745] ahcich: CAM status: Command timeout
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229745 sec changed: What|Removed |Added CC||szcze...@szczepan.net --- Comment #19 from sec --- Also having the same problem, before 11.2, my ZFS mirror was working fine. After upgrade, those CAM errors started to show up. I replaced PSU, replaced one of the drives, replaced cables - still the same. Checked smart for drives, did shoty/long tests - drives are fine. Even did memtest :) My observations: - when HDD's connected directly into motherboard - there are Timeout errors - when HDD's connected to pci-e sata controller - there are unrecoverable CRC errors I tried to disable NCQ and cache - nothing helps. Strange thing is, when mirror is broken (there's only one drive connected) - everything is fine. It's only when 2 drives are connected into same mirror, those start to show up. My drives are WD Gold 1TB: 1. WDC WD1005FBYZ-01YCBB2 RR07 2. WDC WD1005FBYZ-01YCBB1 RR04 Before I had two RR07 working fine, after upgrade, errors shows up, so I RMA one of them and got RR04 - which didn't fix the error. Also the problem only shows up only on one of the drives in mirror. Right now I'm the process of migrating data to 11.1 zfs pool, then I will downgrade my server back to releng/11.1 and check if pool is working fine. I also have two SAMSUNG HD642JJ 1AA01113 connected into other mirror - no issues with those. Tried to swap cables, ports, etc - problem is following those drives, together. Hope for some solution to this one, becuase it will block any upgrade to 12 :) -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 235550] i915kms.ko disables console view
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235550 Johannes Lundberg changed: What|Removed |Added CC||johal...@gmail.com --- Comment #1 from Johannes Lundberg --- When in doubt try, # pkg delete drm-kmod-legacy # pkg delete xf86-video-intel # pkg install drm-kmod Move away stuff that could cause issues # mv /boot/kernel/drm.ko /root/ # mv /boot/kernel/drm2.ko /root/ # mv /boot/kernel/i915kms.ko /root/ # mv /etc/X11/xorg.conf /root/xorg.conf # mv /etc/X11/xorg.d /root/ Clear any module loading and sysctl entries for graphics drivers from /boot/loader.conf and /etc/rc.conf. Disconnect external/multiple displays Reboot # kldload i915kms # kldstat -v (confirm that drm.ko and i915kms.ko are loaded from /boot/modules) # startx Haswell is definitely supported by the new drivers and a default, empty configuration should be sufficient to have functional X and VTs. In most cases, the error is due to conflicts with existing older drm drivers, intel ddx or misconfiguration. If this still doesn't work we need to troubleshoot further. Maybe some quirks with that specific GPU? -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 234094] 'make buildworld' fails because of ignored src.conf settings
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234094 o...@oz42.eu changed: What|Removed |Added Severity|Affects Only Me |Affects Some People -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 171811] [patch] rctl(8) cputime is too high
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=171811 --- Comment #12 from olev...@olevole.ru --- done https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235556 -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 235556] rctl(8) pcpu/cputime is too high
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235556 Bug ID: 235556 Summary: rctl(8) pcpu/cputime is too high Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Many People Priority: --- Component: kern Assignee: b...@freebsd.org Reporter: olev...@olevole.ru This is a duplicate of https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=171811 created at the request of gonzo@, so that we can close the old one from 2012. I don’t know how the original Issue maker lives (b...@desync.com), but I'm still alive. So, I'll do it. All information from the old issue is relevant and affects all the "supported" versions of FreeBSD in 2019: more info how to reproduce: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=171811#c3 -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 235500] [netgraph] tunnel nesting limit hard coded
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235500 Andrey V. Elsukov changed: What|Removed |Added CC||a...@freebsd.org, ||gleb...@freebsd.org --- Comment #1 from Andrey V. Elsukov --- Mentioned changes seems do not change the behavior. The previous limit in the ng_iface node was 1. But I'm not very familiar with this code. Gleb can you take a look? -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 235500] [netgraph] tunnel nesting limit hard coded
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235500 --- Comment #2 from Andrey V. Elsukov --- I think I see what happened. The previous code in the ng_iface did not count number of tags, it only could fail when ifnet pointer was the same. So, it doesn't fully match the behavior that if_tunnel_check_nesting() has. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 235559] 12.0-STABLE panics on mps drive problem (regression from 11.2 and double-regression from 11.1)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235559 Bug ID: 235559 Summary: 12.0-STABLE panics on mps drive problem (regression from 11.2 and double-regression from 11.1) Product: Base System Version: 12.0-STABLE Hardware: amd64 OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: b...@freebsd.org Reporter: k...@denninger.net Created attachment 201796 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=201796&action=edit Core from latest kernel panic On 11.1, this system was completely stable. I upgraded to 11.2 and started getting CAM timeouts / retries, which I started a thread on at https://lists.freebsd.org/pipermail/freebsd-stable/2019-February/090520.html Note that the card firmware is 19.00.00.00; running 20.00.07.00 (latest available) instead of CAM problems with individual drives I get controller resets, which are *far* worse as the impact is not local. In no case, however, has data been corrupted -- ZFS is happy with the data and shows no pack errors of any sort, nor do the disks themselves using smartctl. The retries are successful. The configuration is a LSI 8-port HBA with a Lenovo 24-port expander attached to one of the LSI connectors; the other has the boot drives on it, as the system and card firmware cannot boot from the expander. This configuration has been stable for the last several years and up to 11.1-STABLE was flawless. The drives themselves, backplanes to which they attach, power supply, HBA, SAS expander and cables have all been swapped out with spares here without any change in behavior. The motherboard itself is a XEON with ECC and no RAM errors are being logged. (It's thus reasonable to assume this isn't a hardware problem) The stall and retry itself looks an awful lot like a queued command is being missed or an interrupt lost, both under very heavy load. This typically occurs only when the drives in question are slammed at 100% utilization or nearly so for an extended period of time (e.g. during a scrub or resilver.) I have seen it on both HGST and Seagate drives of differing capacities, model and firmware revision numbers; it does not appear to be related to the disk model or firmware itself. In an attempt to see if this was related to something in 11.2 I rolled the machine forward to 12.0-STABLE. On 12.0-STABLE, r343809, this same condition rather than producing console logs and a successful retry instead results in a kernel panic in the driver. The disk I/O in process at the time is a ZFS scrub and the drive in question is pure data -- it has no executables on it, and in fact the pool has no mounted filesystems at the time of the panic (it's a backup pool that is imported to serve as a destination for zfs sends used as a means of backup.) I have ordered a pair of HBA 16i cards in order to get the expander out of the case in the hope that will stop the detach events, although I am completely lost in terms of why 11.2 and 12.0 will not run with that configuration where it was entirely stable over the last several releases up through 11.1 with uptimes measured in months; until 11.2 I had never seen even a single panic out of the disk subsystem on this configuration. Note that if you have all disks attached to the mps driver you can't take a kernel core dump when it happens; any attempt to do so results in a double-panic out of the driver. I have temporarily attached a drive to the onboard SATA ports and set it as dumpdev so as to be able to get the core file. The panic itself bodes poorly for the impact of potential disk problems (real ones) where a drive goes offline when attached to the mps driver in 12.0, thus this bug report in an attempt to figure out this regression. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 205707] Improve parsing of BDFs by vtfontcvt
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205707 --- Comment #20 from commit-h...@freebsd.org --- A commit references this bug: Author: emaste Date: Wed Feb 6 18:50:48 UTC 2019 New revision: 343842 URL: https://svnweb.freebsd.org/changeset/base/343842 Log: vtfontcvt: whitespace cleanup PR: 205707 Submitted by: Dmitry Wagin Changes: head/usr.bin/vtfontcvt/vtfontcvt.c -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 230172] FreeBSD 11.2 fails to boot on Celeron J1900 after upgrade from 11.1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230172 --- Comment #21 from Vicen Dominguez --- (In reply to mam from comment #20) Indeed mam! changing the driver to "sc" worked for me. As you said, perhaps my problem is a little different because I never could connect to the server via ssh (waiting for 2 hours). I am lost... no ideas. Anyway, thank you to everybody. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 230172] FreeBSD 11.2 fails to boot on Celeron J1900 after upgrade from 11.1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230172 --- Comment #22 from mam --- but now with the "sc" driver the network works again too??? that would be strange, but maybe now you can find a log entry that shines a light on you problem. Anyway, if it works again, all is fine :-) -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 230172] FreeBSD 11.2 fails to boot on Celeron J1900 after upgrade from 11.1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230172 --- Comment #23 from Ed Maste --- (In reply to mam from comment #22) Well, if vt used to work and now doesn't there's a regression we need to find. It seems there are several different reports in here - can someone confirm that the problem occurs under one (or both) of these cases: 11.1 to 11.2 upgrade with no monitor attached 11.1 to 11.2 upgrade with monitor attached Also please include the motherboard model, firmware version, and for the second case the monitor interface (VGA/HDMI/etc.) -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 230172] FreeBSD 11.2 fails to boot on Celeron J1900 after upgrade from 11.1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230172 --- Comment #24 from mam --- you are funny :-) How could somebody notice that the console does not work, if there is no monitor attached ??? As far as it looks for now, its always that AsRock Q1900-ITM Mobo, the connection to the monitor does not matter, there is nothing on either VGA, DVI or HDMI. It looks like the Intel GPU onboard is not supported in this particular processor. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 230172] FreeBSD 11.2 fails to boot on Celeron J1900 after upgrade from 11.1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230172 --- Comment #25 from Ed Maste --- (In reply to mam from comment #24) > How could somebody notice that the console does not work, if there is no > monitor attached ??? If they're using a serial console. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 230172] FreeBSD 11.2 fails to boot on Celeron J1900 after upgrade from 11.1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230172 --- Comment #26 from mam --- then they would not notice it either. Its only the monitor that blocks. Not sure about the keyboard, because you cant see anything, typing is not really responsive too. Thank god, everything else works, the machine boots up and you can login over the network. At the beginning everybody (including me) thought, it was a total crash, because Bios is ok, then the booloader shows the cute Demon and lets you change config and so on. But as soon as you try to boot the kernel, the rotating / | \ ... animations stops and from then on, nothing appears on screen anymore (but the current contents stays there visible until the cows come home). -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 230172] FreeBSD 11.2 fails to boot on Celeron J1900 after upgrade from 11.1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230172 --- Comment #27 from Bernhard Froehlich --- I can confirm the issue on an Supermicro X10SBA (FW 1.3a) with FreeBSD 12.0. That board also uses an Intel Celeron J1900. @ed: If I understand you correctly you want to check if this is a regression between 11.1 and 11.2 so it should be enough to verify by booting those with a usb stick. I should be able to provide that data. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 235559] 12.0-STABLE panics on mps drive problem (regression from 11.2 and double-regression from 11.1)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235559 Conrad Meyer changed: What|Removed |Added CC||c...@freebsd.org, ||sco...@freebsd.org Assignee|b...@freebsd.org|s...@freebsd.org -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
Bug report 235438
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235438 Is anyone watching bug reports? Best regards, Ioannis ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
Re: Bug report 235438
On Thu, Feb 07, 2019 at 12:24:29AM +0200, Ioannis Vranos wrote: > Is anyone watching bug reports? Yes, but we receive so many that we can't keep up. Reports that are problems with specific hardware tend to get more attention from developers than general problems such as this. There is no one dedicated full-time to working on bug reports. mcl ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 235538] [patch] freebsd-update: Try to avoid failing when network is unavailable
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235538 Mark Linimon changed: What|Removed |Added Keywords||patch -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 235438] cp -R command not working properly
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235438 Bob Bishop changed: What|Removed |Added CC||r...@gid.co.uk --- Comment #1 from Bob Bishop --- POSIX apparently allows the current behaviour but it does not seem sensible. The proposed alternative seems reasonable. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 235258] Selection something with vidfont -K and kbdmap -V does not work
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235258 --- Comment #1 from scootergri...@gmail.com --- It seems "kbdmap -V" tries to set a font file as a keymap. And that "vidfont -K" tries to set a keymap as a font. With syscons: Run "kbdmap -V" press enter to select the first font in the list: kbdcontrol: illegal definition line keymap="armscii8-8x8.fnt" Run "vidfont -K" press enter to select the first layout in the list: Which font size? /usr/share/syscons/keymaps/hy.armscii-8.kbd font8=hy.armscii-8.kbd With vt: Run "kbdmap -V" press enter to select the first font in the list: kbdcontrol: illegal definition line keymap="gallant.fnt" Run "vidfont -K" press enter to select the first layout in the list: vidcontrol: bad magic in font file -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 235564] INDEX.keymaps for vt contains "from-" keymaps but the files are missing
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235564 Bug ID: 235564 Summary: INDEX.keymaps for vt contains "from-" keymaps but the files are missing Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: misc Assignee: b...@freebsd.org Reporter: scootergri...@gmail.com It seems the following keymaps are listed in share/vt/keymaps/INDEX.keymaps but they do not exists in the share/vt/keymaps/ folder: ch-fr.kbd.from-cp850 ch.kbd.from-cp850 cz.kbd.from-ce cz.qwerty.kbd.from-ce de.kbd.from-cp850 dk.kbd.from-cp865 ee.kbd.from-cp850 ee.kbd.from-iso1 es.kbd.from-iso1 fi.kbd.from-cp850 ru.kbd.from-cp866 ru.kbd.from-iso5 se.kbd.from-cp850 ua.kbd.from-iso5 They all have "from-" in them. And for some reason the "from-*" part appear after the ".kbd". If the files need to exists i would guess they should all end with ".kbd" like the rest of the keymap files so: ch-fr.from-cp850.kbd ch.from-cp850.kbd cz.from-ce.kbd cz.qwerty.from-ce.kbd de.from-cp850.kbd dk.from-cp865.kbd ee.from-cp850.kbd ee.from-iso1.kbd es.from-iso1.kbd fi.from-cp850.kbd ru.from-cp866.kbd ru.from-iso5.kbd se.from-cp850.kbd ua.from-iso5.kbd If they should not exists then i suggest removing the lines from the share/vt/keymaps/INDEX.keymaps file. I also compared share/syscons/keymaps/INDEX.keymaps and the files in share/syscons/keymaps/ and there does not seem to be any missing files for syscons. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 235564] INDEX.keymaps for vt contains "from-" keymaps but the files are missing
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235564 --- Comment #1 from scootergri...@gmail.com --- I also checked the fonts: share/syscons/fonts/INDEX.fonts seems to be missing lines with: swiss-8x14.fnt swiss-8x16.fnt swiss-8x8.fnt Since the file names exists in share/syscons/fonts/. share/vt/fonts/INDEX.fonts contains: gallant.fnt terminus-b32.fnt tom-thumb.fnt vgarom-16x32.fnt vgarom-8x14.fnt vgarom-8x16.fnt vgarom-8x8.fnt vgarom-thin-8x16.fnt vgarom-thin-8x8.fnt But the file names in share/vt/fonts/ ends with .hex (not .fnt): gallant.hex terminus-b32.hex tom-thumb.hex vgarom-16x32.hex vgarom-8x14.hex vgarom-8x16.hex vgarom-8x8.hex vgarom-thin-8x16.hex vgarom-thin-8x8.hex So i guess either share/vt/fonts/INDEX.fonts should be changed from .hex to .fnt or the file names in share/vt/fonts/ should be changed from .fnt to .hex. Should they not be the same? https://github.com/freebsd/freebsd/blob/master/share/vt/fonts/Makefile says something about SUFFIXES but i dont know what it means. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 235565] share/vt/fonts/INDEX.fonts use 8x14 (others use 8x16)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235565 Bug ID: 235565 Summary: share/vt/fonts/INDEX.fonts use 8x14 (others use 8x16) Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: misc Assignee: b...@freebsd.org Reporter: scootergri...@gmail.com share/vt/fonts/INDEX.fonts contains: FONT:en:vgarom-8x14.fnt share/vt/keymaps/INDEX.keymaps contains: FONT:en:vgarom-8x16.hex Should they not use the same font (either 8x14 or 8x16)? share/syscons/fonts/INDEX.fonts and syscons/keymaps/INDEX.keymaps only use 8x16 use: FONT:en:cp437-8x16.fnt FONT:de,fr,es,is,it,sv,da,fi,nl,no,pt:iso-8x16.fnt FONT:ru:koi8-r-8x16.fnt FONT:hr,hu,pl,cs:iso02-8x16.fnt FONT:lt:iso04-8x16.fnt FONT:iw:iso08-8x16.fnt FONT:uk:koi8-u-8x16.fnt FONT:el:iso07-8x16.fnt FONT:hy:armscii8-8x16.fnt FONT:en:cp437-8x16.fnt FONT:de,fr,da,no,sv,pt,es:iso-8x16.fnt FONT:ru:koi8-r-8x16.fnt FONT:pl:iso02-8x16.fnt FONT:he:iso08-8x16.fnt FONT:uk:koi8-u-8x16.fnt FONT:el:iso07-8x16.fnt FONT:hy:haik8-8x16.fnt -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 201789] [panic] chrome causes page fault in syscall_thread_exit at sys/kern/kern_syscalls.c:95 in 10.1-RELEASE
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201789 Andriy Voskoboinyk changed: What|Removed |Added Keywords||panic CC||a...@freebsd.org Summary|[crash] Fatal trap 12: page |[panic] chrome causes page |fault while in kernel mode |fault in ||syscall_thread_exit at ||sys/kern/kern_syscalls.c:95 ||in 10.1-RELEASE -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 234374] [panic] page fault in softclock_call_cc -> __rw_wlock_hard on 12.0-RELEASE
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234374 Andriy Voskoboinyk changed: What|Removed |Added CC||a...@freebsd.org Summary|Fatal trap 12: page fault |[panic] page fault in |while in kernel mode|softclock_call_cc -> ||__rw_wlock_hard on ||12.0-RELEASE Keywords||panic -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 235500] [netgraph] tunnel nesting limit hard coded
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235500 --- Comment #3 from Gleb Smirnoff --- Created attachment 201808 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=201808&action=edit suggested patch Hi! Can you please test this patch and confirm that desired behavior is achieved? -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 235500] [netgraph] tunnel nesting limit hard coded
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235500 Gleb Smirnoff changed: What|Removed |Added Status|New |In Progress Assignee|b...@freebsd.org|gleb...@freebsd.org -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 235556] rctl(8) pcpu/cputime is too high
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235556 Allan Jude changed: What|Removed |Added CC||allanj...@freebsd.org --- Comment #1 from Allan Jude --- Can you freshly describe the problem and provide some reproduction steps? -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 235567] man physio(9) html page hyphen render break
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235567 Bug ID: 235567 Summary: man physio(9) html page hyphen render break Product: Documentation Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Manual Pages Assignee: b...@freebsd.org Reporter: michaelbuc...@gmail.com CC: d...@freebsd.org In the description section for physio(9) the html page renders a misleading: "dev-_si_iosize_max" instead of "dev->si_iosize_max". This happens in firefox and chrome. Link: https://www.freebsd.org/cgi/man.cgi?query=physio&sektion=9&manpath=FreeBSD+13-current I have seen this happen on occasional other man pages such as in the description of VFS_MOUNT(9): "mp-_mnt_flag". https://www.freebsd.org/cgi/man.cgi?query=VFS_MOUNT&sektion=9&manpath=FreeBSD+13-current -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 231760] FreeBSD 12.0-ALPHA7 Installations Halts at ACPI on 4 different AMD Ryzen Laptops (HP, DELL, Huawei)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231760 --- Comment #5 from Stanislas Leduc --- Infact, I think wrong implementation on motherboard / BIOS to PCI devices. With hw.pci.mcfg=0 to allow FreeBSD manage them, it's work perfectly. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 229745] ahcich: CAM status: Command timeout
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229745 --- Comment #20 from sec --- (In reply to sec from comment #19) Ok, so I tried to downgrade pool to 11.1 - didn't helped. Then I also started to get those errors with only one drive connected (which was fine before). Also tried to boot on 12.0R, same issue. Weird thing is, that sometimes drives are OK, they resilver without any problems, then after some read/write, timeout starts to show up: In the end I tried something I think I've tried before. I've added those to /boot/loader.conf and power cycle: vfs.zfs.cache_flush_disable=1 kern.cam.ada.write_cache=0 And started to stress test - no errors. Then I commented out the "write_cache" - no errors. Commented out "cache_flush" - errors back again (I think I've tried that one already, and got errors, but this time looks fine, fingers crossed). So right know I'm running with cache_flush disabled - hope this will get rid of those errors until some proper fix is done. Errors I was getting was something like that: (ada2:ahcich2:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 00 b0 00 20 40 4c 00 00 01 00 00 (ada2:ahcich2:0:0:0): CAM status: ATA Status Error (ada2:ahcich2:0:0:0): ATA status: 41 (DRDY ERR), error: 10 (IDNF ) (ada2:ahcich2:0:0:0): RES: 41 10 b0 00 20 00 4c 00 00 00 00 (ada2:ahcich2:0:0:0): Retrying command There were also READ and FLUSHCACHE48 errors - this depends on the load I was generating on the pool. If needed I can provide more debug output. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 223950] lower default kern.cam.da.X.delete_max to avoid ZFS TRIM timeouts
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=223950 Poul-Henning Kamp changed: What|Removed |Added Assignee|b...@freebsd.org|i...@freebsd.org -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 223950] lower default kern.cam.da.X.delete_max to avoid ZFS TRIM timeouts
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=223950 Poul-Henning Kamp changed: What|Removed |Added CC||p...@freebsd.org --- Comment #1 from Poul-Henning Kamp --- Seconded. I just triggered a driver panic because zpool create BIO_DELETED entire 2TB SSD drives. There is no relevant performance loss in clamping delete_max to something in the MB-GB range. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"