[Bug 240451] Boot problem from disk on older Intel hardware (kern.vty="vt")
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240451 --- Comment #1 from bart...@dssgmbh.de --- At last we found the culprit. There was a tunable set in loader.conf: debug.late_console="0" which caused this erroneuous behavior. After removing this line from loader.conf, the servers boot as expected with kern.vty unset. This PR can be 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 240451] Boot problem from disk on older Intel hardware (kern.vty="vt")
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240451 bart...@dssgmbh.de changed: What|Removed |Added Status|New |Closed Resolution|--- |Not A Bug -- 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 240487] Boot hangs at "Trying to mount root from ufs:/dev/da0p3 [rw]..." in recent 12-STABLE
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240487 Jack changed: What|Removed |Added CC||xxjack1...@gmail.com --- Comment #3 from Jack --- Also having the same issue except mine hangs at trying to mount gmirror and after successfully finding USB devices 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 237461] Serveral references to emmintrin.h fails
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237461 dewa...@heuristicsystems.com.au changed: What|Removed |Added CC||dewa...@heuristicsystems.co ||m.au --- Comment #10 from dewa...@heuristicsystems.com.au --- (In reply to Ed Maste from comment #3) To your question, I suspect that while folks perform a tidy-up of their environment, you know like "cd /usr/src && make delete-old" they proceed with something like "find -anewer /usr/lib/ -delete;" which inadvertently blows away the /usr/lib/clang/$VER/include - ta dah, kaput! I know, because its a curse being tidy! ;) If this happens to you, here's a hint do NOT copy /usr/src/contrib/llvm/tools/clang/lib/Headers/ into /usr/lib/clang/$VER/include because you'll duplicate things like stddef.h and the compile will fail. You might be able to get by with just copying *intrin.h, but I was impatient. I know this is tedious but much better to either: - read the Makefile to identify only what you need; or - /usr/obj/usr/src/i386.i386/tmp/usr/lib/clang/8.0.1/include/* It really threw me to find that the build required something outside either /usr/obj or /usr/src. Learning something new everyday... Hmm I wonder why pkg-static isn't part of a buildworld, I do after all build from source; perhaps, for tomorrow ;) -- 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 240487] Boot hangs at "Trying to mount root from ufs:/dev/da0p3 [rw]..." in recent 12-STABLE
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240487 --- Comment #4 from Terry Kennedy --- (In reply to Jack from comment #3) If I attach a USB device after the hang, it is reported on the console. Likewise for detach. It seems as though there's an infinite wait somewhere before starting init. -- 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 240487] Boot hangs at "Trying to mount root from ufs:/dev/da0p3 [rw]..." in recent 12-STABLE
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240487 --- Comment #5 from Jack --- (In reply to Terry Kennedy from comment #4) Yes, same behavior here also except it never actually mounts the filesystem as power cycling doesn't show the filesystem as dirty -- 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 240487] Boot hangs at "Trying to mount root from ufs:/dev/da0p3 [rw]..." in recent 12-STABLE
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240487 Herbert J. Skuhra changed: What|Removed |Added CC||herb...@mailbox.org --- Comment #6 from Herbert J. Skuhra --- I had the same problem last night on a remote ZFS system. :) I think the culprit is r352179. Can anyone confirm? -- 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 240487] Boot hangs at "Trying to mount root from ufs:/dev/da0p3 [rw]..." in recent 12-STABLE
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240487 --- Comment #7 from Jack --- Do you have /proc in /etc/fstab? I wanted to test commenting out /proc from fstab but didn't get around to it. I'm going to try that on a remote system and see if it comes back. -- 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 240487] Boot hangs at "Trying to mount root from ufs:/dev/da0p3 [rw]..." in recent 12-STABLE
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240487 --- Comment #8 from Terry Kennedy --- (In reply to Herbert J. Skuhra from comment #6) Reverting that one commit yields a bootable system. Looking at the MFC, it seems that an extra "sx_xlock(&proctree_lock);" came along when it shouldn't have, but I'm not going to bisect further. I'll send an out-of-band notification to the committer to ask them to look at this PR. -- 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 240487] Boot hangs at "Trying to mount root from ufs:/dev/da0p3 [rw]..." in recent 12-STABLE
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240487 --- Comment #9 from Jack --- Looks like not having /proc in fstab made no difference, still hangs on boot. -- 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 213856] Fatal trap12: page fault while in kernel mode; Supervisor read data, page not present
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213856 IPTRACE changed: What|Removed |Added Status|New |Closed Resolution|--- |Works As Intended -- 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 240487] Boot hangs at "Trying to mount root from ufs:/dev/da0p3 [rw]..." in recent 12-STABLE
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240487 Tomoaki AOKI changed: What|Removed |Added CC||junch...@dec.sakura.ne.jp --- Comment #10 from Tomoaki AOKI --- I had the same problem. Reverting r352179 alone (as Herbert J. Skuhra already noted) fixed the problem. Some details: r352118 was OK, and r352202 had problem. I went back to r352179 to bi-sect, and it DOES have problem, too. (The previous revision on stable/12 is r352118.) Updating source again to r352202 and manually reverting r352179 helped. -- 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 240506] picobsd build script not producing usable output
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240506 Bug ID: 240506 Summary: picobsd build script not producing usable output Product: Base System Version: 12.0-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: bin Assignee: b...@freebsd.org Reporter: ro...@herveybayaustralia.com.au Tried running the picobsd script for amd64 native building but no usable output is produced. ./picobsd --src /usr/src -n --init -v qemu find ./ -name \*.bin shows no picobsd.bin, nor does find /usr/obj-pico-amd64/ -name \*.bin. -- 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 240506] picobsd build script not producing usable output
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240506 Kyle Evans changed: What|Removed |Added Assignee|b...@freebsd.org|kev...@freebsd.org --- Comment #1 from Kyle Evans --- Take -- 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 240507] WITHOUT_CLANG=yes WITH_CLANG_BOOTSTRAP=yes does not work
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240507 Bug ID: 240507 Summary: WITHOUT_CLANG=yes WITH_CLANG_BOOTSTRAP=yes does not work Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: bin Assignee: b...@freebsd.org Reporter: kev...@freebsd.org The picobsd build script is trivially broken for CLANG_BOOTSTRAP archs because it wants to set WITHOUT_CLANG and that unsets all of the LLVM_TARGET knobs. It can be fixed to only set it for install phase because it presumably doesn't want clang installed. Can we consider enabling all LLVM_TARGET_* knobs for the bootstrap/cross-compiler clang, and leaving those user-controlled knobs to be purely for the clang that's getting installed. -- 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 240507] WITHOUT_CLANG=yes WITH_CLANG_BOOTSTRAP=yes does not work
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240507 Kyle Evans changed: What|Removed |Added CC||d...@freebsd.org Blocks||240506 Assignee|b...@freebsd.org|toolch...@freebsd.org --- Comment #1 from Kyle Evans --- Assign to -toolchain, CC dim@, part of the picobsd breakage on stable/12 and head. Referenced Bugs: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240506 [Bug 240506] picobsd build script not producing usable 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 240339] [ig4] I2C2 (touchpad bus) broken on the Google Pixelbook (Sunrise Point PCH)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240339 Greg V changed: What|Removed |Added Status|New |Closed Resolution|--- |Not A Bug --- Comment #12 from Greg V --- I think I found the culprit, it's the length retrieval in get_input_report. I changed it to just trust the given length — touchscreen works, touchpad doesn't receive evdev events yet (hmm) but doesn't crash the controller and I can see the reports changing with a debug print, and reload the module multiple times. Seems like ig4 is innocent and it's the touchpad firmware reacting to iichid that's causing the bus to get screwed up. Closing the bug here. -- 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 233361] mips build with BSD_CRTBEGIN, Clang, LLD fails
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233361 --- Comment #5 from Kyle Evans --- I use the following patch in my local mips-llvm branch: commit 9783fdf63c8a4e1775a494b47b7f3648b65779ab Author: Kyle Evans Date: Mon Aug 19 13:18:47 2019 -0500 Hack around .cprestore anger diff --git a/lib/csu/mips/crt.h b/lib/csu/mips/crt.h index 1d967b73ffe..a90d8661f34 100644 --- a/lib/csu/mips/crt.h +++ b/lib/csu/mips/crt.h @@ -29,12 +29,14 @@ #defineHAVE_CTORS #defineCTORS_CONSTRUCTORS #ifdef __mips_o32 +/* The .cprestore is bogus, as we do elsewhere */ #defineINIT_CALL_SEQ(func) \ ".set noreorder\n" \ "bal 1f \n" \ "nop \n" \ "1:\n" \ ".cpload $ra \n" \ +".cprestore 12 \n" \ ".set reorder \n" \ ".local" __STRING(func) "\n" \ "jal " __STRING(func) I fake the .cprestore based on what we do for _mcount in ^/sys/mips/include/profile.h. Whether this is wrong or not, I do not know, but it results in a functional world along with the rest of my mips-llvm patches (https://github.com/freebsd/freebsd/compare/master...kevans91:mips-llvm?expand=1), some of which were stolen from jhb. This branch results in a functional CLANG_BOOTSTRAP+LLD_BOOTSTRAP world and kernel for mips32, but mips64 kernel is horribly broken in weird ways with both llvm8 and projects/clang900-import and CLANG_BOOTSTRAP+LD_BOOTSTRAP. -- 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 239803] Problem with concurrent transfer of file descriptors
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239803 Stas Kelvich changed: What|Removed |Added CC||stas.kelv...@gmail.com --- Comment #2 from Stas Kelvich --- I've applied patch from bug #227285 on r352207 and it solves the problem. However dmesg is full of such messages: ``` uma_zalloc_arg: zone "16" with the following non-sleepable locks held: shared rw unp_link_rwlock (unp_link_rwlock) r = 0 (0x81f673f0) locked @ /usr/src/sys/kern/uipc_usrreq.c:2610 stack backtrace: #0 0x80c3f243 at witness_debugger+0x73 #1 0x80c40262 at witness_warn+0x442 #2 0x80f02afb at uma_zalloc_arg+0x3b #3 0x80bab2db at malloc+0x9b #4 0x80c7b23c at unp_gc+0x2dc #5 0x80c31cec at taskqueue_run_locked+0x10c #6 0x80c32c68 at taskqueue_thread_loop+0x88 #7 0x80b90ad4 at fork_exit+0x84 #8 0x8116c65e at fork_trampoline+0xe ``` -- 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 240509] segfault in basename(3)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240509 Bug ID: 240509 Summary: segfault in basename(3) Product: Base System Version: 12.0-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: bin Assignee: b...@freebsd.org Reporter: zeis...@freebsd.org Attachment #207388 text/plain mime type: Created attachment 207388 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=207388&action=edit reproducer I'm getting a segfault when calling basename(3) on FreeBSD 12.0 and CURRENT. See attached source for an easy to use reproducer. This might be a case of "don't do that", but the same code on Linux works. -- 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 240339] [ig4] I2C2 (touchpad bus) broken on the Google Pixelbook (Sunrise Point PCH)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240339 --- Comment #13 from Greg V --- (In reply to Greg V from comment #12) err, actually, it's the thing where it writes the wInputRegister, which I don't think is supposed to happen. // and it's currently reading mouse reports.. I'll try to fix this. -- 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 240509] segfault in basename(3)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240509
Mateusz Guzik changed:
What|Removed |Added
CC||m...@freebsd.org
--- Comment #1 from Mateusz Guzik ---
basename is allowed to modify the passes buffer. This is documented on both
FreeBSD and Linux. In the attached example the string is immutable, an attempt
to modify it is undefined behavior and a crash (as observed) the likely
outcome.
The FreeBSD implementation happens to always at least add a NUL-byte which
triggers the crash here, while Linux one does not modify the string if there is
nothing to do.
The program will trivially crash if the string is modified to get basename to
operate, e.g. by adding trailing slashes: "/home/tags///".
Finally, the Linux manpage explicitly shows usage with a copied buffer:
The following code snippet demonstrates the use of basename() and
dirname():
char *dirc, *basec, *bname, *dname;
char *path = "/etc/passwd";
dirc = strdup(path);
basec = strdup(path);
dname = dirname(dirc);
bname = basename(basec);
printf("dirname=%s, basename=%s\n", dname, bname);
That said, there is no bug in the FreeBSD version and the code does not crash
on Linux because of a combination of an artifact of the implementation and the
passed argument. FreeBSD variant can be modified to match but there is real
benefit to 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 240487] Boot hangs at "Trying to mount root from ufs:/dev/da0p3 [rw]..." in recent 12-STABLE
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240487 Alan Somers changed: What|Removed |Added Status|New |Open Assignee|b...@freebsd.org|osho...@freebsd.org --- Comment #11 from Alan Somers --- Assigning to the committer of r352179. -- 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 240509] segfault in basename(3)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240509 Conrad Meyer changed: What|Removed |Added Status|New |Closed Resolution|--- |Not A Bug -- 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 231457] Out of swap space on ZFS
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231457 Parashiva changed: What|Removed |Added CC||parash...@outlook.com --- Comment #16 from Parashiva --- Hello, My server also with same error "mysqld killed out of swap space" when I import an 70G+ mysql dump (mysqldump -u root -p database -r dump.sql). The server's hardware is 256G SSD*2, 32G RAM, CPU e3-1245 v3, with latest freebsd 12, zfs mirror, atime=off,primarycache=all,secondarycache=none. I tried below solutions: 1. trick learn from stackoverflow.com set global net_buffer_length=1048576; set global max_allowed_packet=1073741824; SET foreign_key_checks = 0; not working 2. disable swap not working 3. then I think it related to RAM or SWAP, should I disabled ARC? zfs set primarycache=none tank working!!! So I have my database working now. Hope my experience could help someone. Thank you, Best 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 231457] Out of swap space on ZFS
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231457 --- Comment #17 from Parashiva --- (In reply to Parashiva from comment #16) My zrc limit is: vfs.zfs.arc_max="4G" vfs.zfs.arc_min="2G" -- 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 240513] [PATCH]: sys/x86/x86/tsc.c: Use gender-neutral pronoun in comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240513 --- Comment #1 from Neel Chauhan --- *** Bug 240512 has been marked as a duplicate of this bug. *** -- 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 240513] [PATCH]: sys/x86/x86/tsc.c: Use gender-neutral pronoun in comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240513 Bug ID: 240513 Summary: [PATCH]: sys/x86/x86/tsc.c: Use gender-neutral pronoun in comment Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: misc Assignee: b...@freebsd.org Reporter: n...@neelc.org Created attachment 207393 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=207393&action=edit Patch (Revision 1) On line 283 in sys/x86/x86/tsc.c, I saw the following comment: * User did not give the order about calibration. * If he did, we do not try to guess. We can't assume all FreeBSD users are male. They could be female, non-binary, etc. I have a patch which changes the comment to: * User did not give the order about calibration. * If they did, we do not try to guess. -- 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 240513] [PATCH]: sys/x86/x86/tsc.c: Use gender-neutral pronoun in comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240513 Neel Chauhan changed: What|Removed |Added CC||n...@neelc.org Keywords||easy, 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 240513] [PATCH]: sys/x86/x86/tsc.c: Use gender-neutral pronoun in comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240513 Conrad Meyer changed: What|Removed |Added Status|New |Closed Resolution|--- |Not A Bug --- Comment #2 from Conrad Meyer --- We're not individually patching every single instance of pronouns in comments. -- 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 240339] [ig4] I2C2 (touchpad bus) broken on the Google Pixelbook (Sunrise Point PCH)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240339 --- Comment #14 from Vladimir Kondratyev --- (In reply to Greg V from comment #12) > Seems like ig4 is innocent Not so innocent. You are at least 5-th man who has tried iichid and has bitten by SDA_HOLD issue. Can you check and post here the value of this register right after IG4_REG_RESETS_SKL is written. In my case it is 0x0001 which is too low to allow normal I2C operation. I think setting SDA_HOLD to 28 is a good candidate to be committed just now with the aim to be MFC-ed before 12.1 branch is forked. -- 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 240339] [ig4] I2C2 (touchpad bus) broken on the Google Pixelbook (Sunrise Point PCH)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240339 --- Comment #15 from Vladimir Kondratyev --- (In reply to Greg V from comment #12) > I think I found the culprit, it's the length retrieval in get_input_report. I > changed it to just trust the given length — touchscreen works, That sounds strange. Length retrieval breaks read pipelining, but I dont think it can result in such an errors. > err, actually, it's the thing where it writes the wInputRegister, which I > don't think is supposed to happen. Write into wInputRegister can't result in any immediate errors as it is just a write into controller's FIFO. // and it's currently reading mouse reports.. I'll try to fix this. imt_set_input_mode() is responsible for converting mouse to touchpad -- 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 240339] [ig4] I2C2 (touchpad bus) broken on the Google Pixelbook (Sunrise Point PCH)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240339 --- Comment #16 from Greg V --- (In reply to Vladimir Kondratyev from comment #14) I meant innocent in the lockup case, that was indeed the touchpad firmware blowing up from the write. Yes, the reset changes the hold value to 1. Interesting how the other buses are fine with this, only the touchpad one was broken. -- 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 240506] picobsd build script not producing usable output
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240506
Kyle Evans changed:
What|Removed |Added
CC||b...@freebsd.org,
||r...@freebsd.org
--- Comment #2 from Kyle Evans ---
CC'ing re@, because I think this is technically their territory being in
release/, and CC'ing bugs@ to keep it on a list.
Here's a summary of the bugs I've encountered in picobsd so far, and I still
haven't gotten anything usable:
- Script unconditionally sets WITHOUT_CLANG/WITHOUT_CLANG_BOOTSTRAP [0] without
dealing with GCC_BOOTSTRAP. The libllvm build fails because WITHOUT_CLANG shuts
off all of the LLVM_TARGET_* -- build failure.
- Fixing that, native builds cannot work. The script does `set -e`, then [1] --
on a native build, ${o_arch} == `uname -m` and we don't descend down && path,
leaving the function with an erroneous exit code and the script bails out.
- Fixing that, native amd64 builds cannot work. None of these [2] are valid CPU
types for amd64 -- only i386. One can supply their own kernconf, so let's
ignore this for now.
What does work?
- Cross-builds -- kind of, for very primitive cases. [3] sets TARGET_ARCH and
ARCH to whatever was passed in via --arch. This assumes ARCH=TARGET_ARCH, which
rules out, e.g., arm.armv7, most mips flavors, most powerpc flavors, riscv,
arm64
- The i386 build probably does, but I had to fix the ${CONF}/${CONFFILE} target
in Makefile.conf to wrap [ -f ... ] && cpp in () || true in order to
continue... around here I ran out of patience to tolerate further failures for
the night, so I left the build running and detached for the night.
I think re@ should consider dropping this before 13.0, because:
1.) It has no active maintainer and has a lot of deferred maintenance that
needs handled (see: pretty broken by default, and it's been this way for a
while),
2.) It can't handle cross-builds,
3.) I think it fills a niche that's better fit for nanobsd or mfsbsd, which see
more active maintenance
[0]
https://svnweb.freebsd.org/base/head/release/picobsd/build/picobsd?view=markup&pathrev=349453#l975
[1]
https://svnweb.freebsd.org/base/head/release/picobsd/build/picobsd?view=markup&pathrev=349453#l186
[2]
https://svnweb.freebsd.org/base/head/release/picobsd/qemu/PICOBSD?revision=349253&view=markup&pathrev=349453#l17
[3]
https://svnweb.freebsd.org/base/head/release/picobsd/build/picobsd?view=markup&pathrev=349453#l972
--
You are receiving this mail because:
You are on the CC list 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"
