[Bug 244906] kernel booted by loader.efi on VMware Fusion crashes in EFI firmware
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244906
--- Comment #11 from Yuri Pankov ---
(In reply to Hongbo He from comment #9)
It doesn't, that looks like completely different issue.
Still the same issue with VMware Workstation 16.{0,1} now and
FreeBSD-13.0-CURRENT-amd64-20201119-f2ea0734875-disc1.iso .
--
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 250580] VMware UEFI guests crash in virtual hardware after r366691
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250580 --- Comment #8 from Christian Ullrich --- It still fails with the same message on Workstation 16.1.0 build-17198959, released on the same day (2020-11-19) as 15.5.7 mentioned above. -- 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 250580] VMware UEFI guests crash in virtual hardware after r366691
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250580 --- Comment #9 from Warner Losh --- can someone share the error messages and/or a screen shot of the failure? -- 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 250580] VMware UEFI guests crash in virtual hardware after r366691
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250580 --- Comment #10 from Christian Ullrich --- Created attachment 219850 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=219850&action=edit Screenshot -- 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 250580] VMware UEFI guests crash in virtual hardware after r366691
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250580 --- Comment #11 from Christian Ullrich --- Created attachment 219851 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=219851&action=edit VMware workstation log, slightly edited -- 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 251149] SynPS/2 Synaptics TouchPad: Failed to create a device for ... after upgrade from 12.1 to 12.2
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251149 --- Comment #2 from Martin Birgmeier --- In issue #249987, kern.evdev.rcpt_mask is mentioned. In 12.2 it seems to be set to 0xc. Setting it to 0x3 makes all three pointer devices working again in X11 (touchpad, trackpoint, USB mouse). -- Martin -- 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 251149] SynPS/2 Synaptics TouchPad: Failed to create a device for ... after upgrade from 12.1 to 12.2
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251149 --- Comment #3 from Martin Birgmeier --- The issue reported by me is solved: In /var/log/Xorg.0.log, there were the following lines (with kern.evdev.rcpt_mask=12): (EE) synaptics: SynPS/2 Synaptics TouchPad: Synaptics driver unable to detect protocol (EE) PreInit returned 11 for "SynPS/2 Synaptics TouchPad" Also, I am compiling ports myself, and from ages ago the EVDEV option was still unset for the xf86-input-synaptics port. Enabling EVDEV support in x11-drivers/xf86-input-synaptics solved the issue for me. Sorry for spamming your bug report; I hope that nonetheless this information may be useful for someone. -- Martin -- 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 251149] SynPS/2 Synaptics TouchPad: Failed to create a device for ... after upgrade from 12.1 to 12.2
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251149 Jason W. Bacon changed: What|Removed |Added CC||j...@freebsd.org Severity|Affects Only Me |Affects Some People --- Comment #4 from Jason W. Bacon --- Same problem on a ThinkPad T61 using binary packages, so no unusual port options. Touchpad works in VT but not in X11. Setting kern.evdev.rcpt_mask=3 worked around it. -- 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 251149] SynPS/2 Synaptics TouchPad: Failed to create a device for ... after upgrade from 12.1 to 12.2
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251149 --- Comment #5 from Martin Birgmeier --- What I did to diagnose the issue: - Look in /var/log/Xorg.0.log - run "sysctl kern.evdev" and check that all input devices are shown in the output - run "sysctl hw.psm" and check that all mouse devices are in the output - run "xinput" and check that X sees all input devices (those from kern.evdev) - check that /etc/X11/xorg.conf is mostly empty - nowadays, the X server autoconfigures itself mostly completely - and of course, search the Internet for all error messages found... -- Martin -- 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 251291] sockstat(1) - use -w option to also make COMMAND column wider
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251291 Bug ID: 251291 Summary: sockstat(1) - use -w option to also make COMMAND column wider Product: Base System Version: 12.2-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: bin Assignee: b...@freebsd.org Reporter: verma...@interia.pl Just an idea. As -w option for sockstat(1) provides wider field size for displaying addresses it can also be used to increase the width of COMMAND column as process names are often cut. % sockstat -l -4 USER COMMANDPID FD PROTO LOCAL ADDRESS FOREIGN ADDRESS unbound local-unbo 26332 5 udp4 127.0.0.1:53 *:* unbound local-unbo 26332 6 tcp4 127.0.0.1:53 *:* root wpa_suppli 42380 4 udp4 *:* *:* Regards. -- 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 178231] [nfs] 8.3 nfsv4 client reports "nfsv4 client/server protocol prob err=10026"
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=178231 m...@netfence.it changed: What|Removed |Added CC||m...@netfence.it --- Comment #4 from m...@netfence.it --- Hello. I've got a 12.2 client connecting to a 12.2 server and I'm seeing this message a few times a day. I'm not sure it leads to consequences, though. I also rarely see the same message, but with error 10020 and "nfsv4 expired locks lost". I don't use the intr option. I'd be glad to help investigate this, but I need guidance. -- 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 251274] panic: recursive fpu_kern_enter while in PCB_FPUNOSAVE state
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251274 Konstantin Belousov changed: What|Removed |Added CC||k...@freebsd.org --- Comment #1 from Konstantin Belousov --- This is double of #250351. In both cases it sounds as if fpu_kern_exit() was forgotten. I do not see anything obvious in zfs code. -- 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"
