2025/freebsd-arm/20251124.freebsd-arm
Messages: 54, sorted by subject
|
Last update: Mon Nov 24 0:07:06 2025
|
|
home | up | archive sorted by: subject | author | date | reverse date
1. Nov 17 bugzilla-noreply@freebsd.o [Bug 246865] c++: error: unable to execute command: Killed 2. Nov 18 bugzilla-noreply@freebsd.o [Bug 269726] kern.msgbufsize=4587520 in loader.conf, kernel never boots 3. Nov 18 void Re: Arm v7 RPi2 -current unresponsive to debugger escape during buildworld 4. Nov 22 titus bug in sys/dev/[extres]/nvmem/nvmem.c 5. Nov 22 Adrian Chadd Re: bug in sys/dev/[extres]/nvmem/nvmem.c 6. Nov 23 Emmanuel Vadot Re: bug in sys/dev/[extres]/nvmem/nvmem.c 7. Nov 23 titus Re: bug in sys/dev/[extres]/nvmem/nvmem.c 8. Nov 23 titus Re: bug in sys/dev/[extres]/nvmem/nvmem.c 9. Nov 20 qroxana eqos on Panther X2 RK3566 10. Nov 20 Milan Obuch Re: eqos on Panther X2 RK3566 11. Nov 20 qroxana Re: eqos on Panther X2 RK3566 12. Nov 20 Milan Obuch Re: eqos on Panther X2 RK3566 13. Nov 20 =?UTF-8?Q?S=C3=B8ren_Schmi Re: eqos on Panther X2 RK3566 14. Nov 17 Mark Millard FYI: linux 6.18 arm64 update: Use load LSE atomics for the non-return per-CPU atomic operations 15. Nov 17 Mark Millard FYI: RPi5 power consumption reply [Not on topic for original "Future of armv7" message] 16. Nov 17 Tomek CEDRO Re: FYI: RPi5 power consumption reply [Not on topic for original "Future of armv7" message] 17. Nov 20 Mark Millard Re: Still seeing Failed assertion: "p[i] == 0" [ *** i386 chroot on amd64 can get the failure on main 16 too *** ] 18. Nov 21 Mark Millard Re: Still seeing Failed assertion: "p[i] == 0" [ *** i386 chroot on amd64 can get the failure on main 16 too *** ] 19. Nov 21 Mark Millard Re: Still seeing Failed assertion: "p[i] == 0" [ *** i386 chroot on amd64 can get the failure on main 16 too *** ] 20. Nov 21 Mark Millard Re: Still seeing Failed assertion: "p[i] == 0" [ *** i386 chroot on amd64 can get the failure on main 16 too *** ] [failed without new kernel
21. Nov 21 Mark Millard Re: Still seeing Failed assertion: "p[i] == 0" [ *** i386 chroot on amd64 can get the failure on main 16 too *** ] [failed without new kernel 22. Nov 22 Mark Millard Re: Still seeing Failed assertion: "p[i] == 0" [ junk:true vs. junk:alloc,zero:true ] 23. Nov 17 Konstantin Belousov Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld 24. Nov 17 Mark Millard Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld 25. Nov 17 Mark Millard Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld 26. Nov 17 Mark Millard Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld 27. Nov 17 bob prohaska Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld 28. Nov 18 Adrian Chadd Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld 29. Nov 18 Mark Millard Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld 30. Nov 21 bob prohaska Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld 31. Nov 21 Mark Millard Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld 32. Nov 21 bob prohaska Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld 33. Nov 18 Mark Millard Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld [gdb backtrace! End of area has 0x5a5a5a5a sequence] 34. Nov 18 Mark Millard Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld [gdb backtrace! End of area has 0x5a5a5a5a sequence] 35. Nov 18 Mark Millard Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld [gdb backtrace!] 36. Nov 19 Mark Millard Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld [Notes from another example core dump: #1] 37. Nov 19 Mark Millard Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld [Notes from another example core dump: #1] 38. Nov 19 Mark Millard Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld [Notes from another example core dump: #1] 39. Nov 19 Mark Millard Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld [Notes from another example core dump: #2] 40. Nov 19 Mark Millard Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld [Notes from another example core dump: #3]
41. Nov 19 Mark Millard Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld [Notes from another example core dump: #4] [New common range #0..#10 __je_ 42. Nov 19 Mark Millard Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld [Notes from another example core dump: #5] [Common range #0..#10 __je_pa_a 43. Nov 19 Mark Millard Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld [Notes from another example core dump: #5] [Common range #0..#10 __je_pa_a 44. Nov 19 Mark Millard Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld [Notes from another example core dump: #5] [Common range #0..#10 __je_pa_a 45. Nov 17 Mark Millard Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld [only main 16 does the check] 46. Nov 17 void WITHOUT_CLEAN confusion in -current 47. Nov 17 Herbert J. Skuhra Re: WITHOUT_CLEAN confusion in -current 48. Nov 17 Mark Millard RE: WITHOUT_CLEAN confusion in -current 49. Nov 17 Warner Losh Re: WITHOUT_CLEAN confusion in -current 50. Nov 17 void Re: WITHOUT_CLEAN confusion in -current 51. Nov 23 bob prohaska wlan0 goes down but system doesn't notice 52. Nov 23 Adrian Chadd Re: wlan0 goes down but system doesn't notice 53. Nov 23 bob prohaska Re: wlan0 goes down but system doesn't notice 54. Nov 23 Adrian Chadd Re: wlan0 goes down but system doesn't notice
home | up | archive sorted by: subject | author | date | reverse date