Re: LUA ERROR: memory allocation error: block too big
Hi all, to add to the argument made by Kyle: > Am 03.06.2020 um 14:56 schrieb Kyle Evans : > As an aside, I'd appreciate it if other folks in this thread could > simply stop dumping all over the many many many hours of work that > were put into getting lua into shape to replace the high-quality forth > that was already in place. The reality is that lua won a popularity > contest long ago [outside of a FreeBSD context][ and lowers the barrier > to being able to hack on our loader menus, which should be viewed as a > great thing. I was equally annoyed at first because I happen to know a good deal of Forth (and use HP calculators ;-) and my reasoning was like „Lua is just as exotic as Forth so people need to learn the basics of a new language, anyway - why make *me* relearn everything?“ But in private conversation at one EuroBSDCon I learned that the „bus factor“ of the old bootloader (i.e. how many people have to be overrun by a bus to make that part of the project unmaintainable because there is zero knowledge left) was probably 2. Which is a perfectly good reason to replace a piece of software with a new one that hopefully more people understand. As for the choice of language I am actually pretty agnostic and willing to learn whatever is needed to get a particular task done. Just my 2ct. Patrick -- punkt.de GmbH Patrick M. Hausen .infrastructure Kaiserallee 13a 76133 Karlsruhe Tel. +49 721 9109500 https://infrastructure.punkt.de [email protected] AG Mannheim 108285 Geschäftsführer: Jürgen Egeling, Daniel Lienert, Fabian Stein ___ [email protected] mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[email protected]"
Re: LUA ERROR: memory allocation error: block too big
On Thu, 4 Jun 2020, Kyle Evans wrote: Can you share a pointer to the problems you had? You can see here, long ago, a swap of the loader did help: https://forums.freebsd.org/threads/lua-error-can-not-open-boot-lua-loader-lua.68635/page-2#post-430461 And excuse me that I was furious. I never had problems with the loader before. And I see also a decrease of quality on the installation program. Installing FreeBSD is getting more difficult. Rodrigo ___ [email protected] mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[email protected]"
Re: LUA ERROR: memory allocation error: block too big
On Thu, Jun 4, 2020 at 5:53 AM Roderick wrote: > [...] > > OK, for putting LUA was invested many many hours, the FORTH was > done in 5 minutes and ist worst quality. > I'd easily debate this latter bit- the Forth is certainly higher quality. > But the booting and installation problems, that I had to solve in > a tricky way and with additional hardware, began with the LUA loader, > and are solved putting an old loader, as somenone in this thread noted. > Can you share a pointer to the problems you had? It would be highly unusual for swapping out the interpreter to cause problems of this nature. With the way loader is architected, most low-level details don't change with different interpreters, and it's incredibly likely you are looking at a problem that was caused way-independently of swapping out the interpreter. Plenty of things broke between FreeBSD 10/11 and 12 in loader-world as our loader universe got thoroughly rototilled and improved -- many of these things cannot be attributed to lua, but perhaps are because of the coincidental timing. Thanks, Kyle Evans ___ [email protected] mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[email protected]"
Re: LUA ERROR: memory allocation error: block too big
I do not want to be demoralizing, nor to hurt anyone. I am also thankfull to all developers. But the argumenentation used here does not convince and makes me think about the future of FreeBSD. OK, for putting LUA was invested many many hours, the FORTH was done in 5 minutes and ist worst quality. But the booting and installation problems, that I had to solve in a tricky way and with additional hardware, began with the LUA loader, and are solved putting an old loader, as somenone in this thread noted. And how many users did need lua there (and everywhere, also in the soup)? The last beat would be to remove the forth loader from the distribution, then a solution of the problems will become much more difficult. Rodrigo On Wed, 3 Jun 2020, Kyle Evans wrote: [...] As an aside, I'd appreciate it if other folks in this thread could simply stop dumping all over the many many many hours of work that were put into getting lua into shape to replace the high-quality forth that was already in place. The reality is that lua won a popularity contest long ago [outside of a FreeBSD context][ and lowers the barrier to being able to hack on our loader menus, which should be viewed as a great thing. These comments were highly demoralizing, and I almost didn't bother dropping into this thread because of them. Believe it or not, issues with underlying media can cause problems with 4thloader as well. Thanks, Kyle Evans ___ [email protected] mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[email protected]" ___ [email protected] mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[email protected]"
Re: LUA ERROR: memory allocation error: block too big
On Wed, Jun 3, 2020 at 10:12 AM Kyle Evans wrote: > On Wed, Jun 3, 2020 at 11:06 AM Budi Janto > wrote: > > > > > > > > On 6/3/20 6:50 PM, Kyle Evans wrote: > > > Can you post a sample of your /boot/lodaer.conf, please? Though, the > > > efipart_readwrite error smack dab in the middle leaves me a bit > > > worried; status=7 looks like EFI_DEVICE_ERROR, which is a bit > > > sinister. > > > > # cat /boot/loader.conf > > autoboot_delay="5" # Delay in seconds before autobooting. > > vfs.zfs.arc_max="5G"# Limit ZFS memory usage. > > coretemp_load="YES" # Intel CPU temperature. > > > > Thanks for confirming - this is relatively harmless, and the problem > is indeed later. > > > > > > Believe it or not, issues with underlying media can cause problems > > > with 4thloader as well. > > > > Could be, I' will replace as soon as possible SSD for system (My > > prediction SSD too old). I'am sorry, this's remote machine, so I can not > > give you more information (I can not access that machine anymore). > > Remote worker just send me two photo. > > > > First booting: https://ibb.co/NWbszqR > > After restart: https://ibb.co/dDsH0RD > > > > *nod* This isn't my domain, but I think the CAM errors after restart > tend to support the theory of aging/dying SSD or perhaps bad cable at > a minimum. > Those look like a bad sector on the disk / ssd. Rewriting it may mitigate the issue for a while, but for long term happiness, you'll want to replace. Warner ___ [email protected] mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[email protected]"
Re: LUA ERROR: memory allocation error: block too big
On Wed, Jun 3, 2020 at 11:06 AM Budi Janto wrote: > > > > On 6/3/20 6:50 PM, Kyle Evans wrote: > > Can you post a sample of your /boot/lodaer.conf, please? Though, the > > efipart_readwrite error smack dab in the middle leaves me a bit > > worried; status=7 looks like EFI_DEVICE_ERROR, which is a bit > > sinister. > > # cat /boot/loader.conf > autoboot_delay="5" # Delay in seconds before autobooting. > vfs.zfs.arc_max="5G"# Limit ZFS memory usage. > coretemp_load="YES" # Intel CPU temperature. > Thanks for confirming - this is relatively harmless, and the problem is indeed later. > > > Believe it or not, issues with underlying media can cause problems > > with 4thloader as well. > > Could be, I' will replace as soon as possible SSD for system (My > prediction SSD too old). I'am sorry, this's remote machine, so I can not > give you more information (I can not access that machine anymore). > Remote worker just send me two photo. > > First booting: https://ibb.co/NWbszqR > After restart: https://ibb.co/dDsH0RD > *nod* This isn't my domain, but I think the CAM errors after restart tend to support the theory of aging/dying SSD or perhaps bad cable at a minimum. Thanks, Kyle Evans ___ [email protected] mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[email protected]"
Re: LUA ERROR: memory allocation error: block too big
On 6/3/20 6:50 PM, Kyle Evans wrote: > Can you post a sample of your /boot/lodaer.conf, please? Though, the > efipart_readwrite error smack dab in the middle leaves me a bit > worried; status=7 looks like EFI_DEVICE_ERROR, which is a bit > sinister. # cat /boot/loader.conf autoboot_delay="5" # Delay in seconds before autobooting. vfs.zfs.arc_max="5G"# Limit ZFS memory usage. coretemp_load="YES" # Intel CPU temperature. > Believe it or not, issues with underlying media can cause problems > with 4thloader as well. Could be, I' will replace as soon as possible SSD for system (My prediction SSD too old). I'am sorry, this's remote machine, so I can not give you more information (I can not access that machine anymore). Remote worker just send me two photo. First booting: https://ibb.co/NWbszqR After restart: https://ibb.co/dDsH0RD Thank you. -- Regards, Budi Janto ___ [email protected] mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[email protected]"
Re: LUA ERROR: memory allocation error: block too big
[Resend because I failed to use the correct from address on the first one and it got rejected by the list; apologies] On Tue, Jun 2, 2020 at 9:04 AM Budi Janto wrote: > > Hi Folks, > > Now, I'am running FreeBSD 12.1-STABLE, suddenly after restart system can > not able to booting (boot to single user only). > > ... > Loading /boot/defaults/loader.conf > Loading /boot/device.hints > Loading /boot/loader.conf > efipart_readwrite: rw=1, blk=5656992 size=40 status=7 > Startup error in /boot/lua/loader.lua: > LUA ERROR: memory allocation error: block too big. > > can't load 'kernel' > > Type '?' for a list of commands. 'help' for more detailed help > OK > ... > > Anyone could give some clue to fixing this booting issue? -- Thank You. > Can you post a sample of your /boot/lodaer.conf, please? Though, the efipart_readwrite error smack dab in the middle leaves me a bit worried; status=7 looks like EFI_DEVICE_ERROR, which is a bit sinister. As an aside, I'd appreciate it if other folks in this thread could simply stop dumping all over the many many many hours of work that were put into getting lua into shape to replace the high-quality forth that was already in place. The reality is that lua won a popularity contest long ago [outside of a FreeBSD context][ and lowers the barrier to being able to hack on our loader menus, which should be viewed as a great thing. These comments were highly demoralizing, and I almost didn't bother dropping into this thread because of them. Believe it or not, issues with underlying media can cause problems with 4thloader as well. Thanks, Kyle Evans ___ [email protected] mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[email protected]"
Re: LUA ERROR: memory allocation error: block too big
- who wants to deal with something low level like the boot loader, should be also able to learn a simple programming language. - Now the whole bootloader had become riddled with problems that hinders booting and installation. - Unfortunately someone was willing to do the destructive work. The only possitive thing: only the bootloader was spoiled. One could spoil the whole system with this posture and argumentation. Rodrigo On Wed, 3 Jun 2020, Mark Linimon wrote: On Wed, Jun 03, 2020 at 05:00:13AM +, Roderick wrote: I would real want hear, why was the boat loader spoiled with Lua? Because lua is so cool? You are coming in several years late to a conversation. - Having a scripting language makes working with the boot loader code easier. - The number of people who can code in lua is far higher than the number who can code in Forth. - The Forth code had become riddled with problems. - Someone was willing to do the work. mcl ___ [email protected] mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[email protected]"
Re: LUA ERROR: memory allocation error: block too big
On Wed, 3 Jun 2020 05:00:13 + (UTC) Roderick [email protected] said LUA Error! I would real want hear, why was the boat loader spoiled with Lua? Bwcause lua is so cool? Rodrigo On Tue, 2 Jun 2020, Budi Janto wrote: > Hi Folks, > > Now, I'am running FreeBSD 12.1-STABLE, suddenly after restart system can > not able to booting (boot to single user only). > > ... > Loading /boot/defaults/loader.conf > Loading /boot/device.hints > Loading /boot/loader.conf > efipart_readwrite: rw=1, blk=5656992 size=40 status=7 > Startup error in /boot/lua/loader.lua: > LUA ERROR: memory allocation error: block too big. > > can't load 'kernel' > > Type '?' for a list of commands. 'help' for more detailed help > OK > ... > > Anyone could give some clue to fixing this booting issue? -- Thank You. Boot single user if possible, tho it's probably not. Failing that; boot from the install media. Mount the root slice of your failing system. cd to its /boot folder rm ./loader ln loader_4th loader cd / unmount the system remove the install media you just booted from, and reboot. It should (hopefully) work now. --Chris > > > -- > Regards, > > > Budi Janto > ___ > [email protected] mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "[email protected]" > ___ [email protected] mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[email protected]" ___ [email protected] mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[email protected]"
Re: LUA ERROR: memory allocation error: block too big
LUA Error! I would real want hear, why was the boat loader spoiled with Lua? Bwcause lua is so cool? Rodrigo On Tue, 2 Jun 2020, Budi Janto wrote: Hi Folks, Now, I'am running FreeBSD 12.1-STABLE, suddenly after restart system can not able to booting (boot to single user only). ... Loading /boot/defaults/loader.conf Loading /boot/device.hints Loading /boot/loader.conf efipart_readwrite: rw=1, blk=5656992 size=40 status=7 Startup error in /boot/lua/loader.lua: LUA ERROR: memory allocation error: block too big. can't load 'kernel' Type '?' for a list of commands. 'help' for more detailed help OK ... Anyone could give some clue to fixing this booting issue? -- Thank You. -- Regards, Budi Janto ___ [email protected] mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[email protected]" ___ [email protected] mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[email protected]"
