Re: [DNG] Is it dead yet?
On Tue, 26 Oct 2021 23:15:15 -0400 Hendrik Boom via Dng wrote: > I'll have to replace the RAM, I guess. Or find out what memory bus > is failing. I know this sounds odd, but I had memory errors galore which were solved by a new power supply. Apparently a jackass flipping breakers off and on quickly had stressed it out. Linux worked without complaint but Windows 8.1 occasionally bluescreened. If you have a spare PSU, try that first. - This may be obvious, but a memory testing suggestion: Remove all but one stick With that one stick in a particular slot, memtest If failed, repeat with each single stick in that same slot If all fail, move up a slot and test each stick I know it's a pain, but it might determine if the any/all memory sticks or if the motherboard are bad. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Is it dead yet?
Chimaera didn't help, though the symptoms changed. I booted from the chimaera live desktop, and it started looking hopeful, but before much was running it had a kernel panic -- attempt to kill init. Yes, I checked the checksum on the download. And when I used chimaera to boot another computer (a Purism laptop) it worked flawlessly. I'm once more suspecting hardware. Next stop -- memtest. And memtest shows an enormous number of memory failures. Which makes me suspect something systemic, not just a bit here or there. I'll have to replace the RAM, I guess. Or find out what memory bus is failing. -- hendrik On Tue, Oct 26, 2021 at 11:26 AM tempforever wrote: > Download links are available on the devuan download page > https://www.devuan.org/get-devuan > > choose a mirror (for example, mirror.leaseweb.com/devuan/) then navigate > to the devuan_chimaera/ directory where you will hopefully find a > desktop-live/ directory which should contain > devuan_chimaera_4.0.0_[amd64|i386]_desktop-live.iso along with the > shasums files. If you prefer not to use http(s), there are ftp mirrors > and torrent on that same download page. > > Hendrik Boom via Dng wrote: > > Then I'd have to figure out how to get a new kernel into it while it > crashes during bootup, > which it now does quite consistently. > > If I had > made recent > changes (such as upgrades) I'd consider a kernel problem more likely. > > But it has been running for months with only occasional problems, and > now I get problems > every time I boot. Since I haven't done an upgrade > at all yet this month, I'll suspect hardware. > > Still, I will try, > say, a chimaera live CD if I can find one. Where are the Devuan live > CD's? > I seem to remember that they were called something other than > "devuan". > (Yes, I'm aware that the live CD will likely be a USB stick) > > > -- hendrik > > On Tue, Oct 26, 2021 at 7:47 AM Boian Bonev > mailto:bbo...@ipacct.com>> wrote: > > ___ > Dng mailing list > Dng@lists.dyne.org > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng > ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] Chimaera install: only low resolution video
I just installed Chimera RC on a Gigabyte Z590 machine (incidentally it looks like I could autoconfigure wireless with providing firmware). When I installed xorg and fluxobox, the display was low resolution. Apparently it is a low resolution default. lxrandr offers no other accessible resolution. I here paste the return of inxi on my current machine and then on the installation of Chimaera. Neighter machine has a v ideo card. I'm not sure that to make of this. The old machine with good resolution Graphics: Device-1: Intel HD Graphics 630 vendor: Gigabyte driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:5912 Display: server: X.Org 1.20.4 driver: loaded: modesetting unloaded: fbdev failed: vesa resolution: 1920x1080~60Hz s-dpi: 96 OpenGL: renderer: Mesa DRI Intel HD Graphics 630 (Kaby Lake GT2) v: 4.5 Mesa 18.3.6 compat-v: 3.0 direct render: Yes On new machine with poor revoltuion Graphics: Device-l: Intel vendor: Gigabyte driver: N/A bus ID 00:02.0 chip ID: 8886:4c8a Display: serve: X.Org 1.20.11 drive: loaded: vesa unloaded: fbdev,modesetting resolution: 1024x768-76Hz s-dpi: 96 OpenGL: renderer: llvmpipe (LLM 11.0.1 256 b its) v: 4.5 Mesa 20.3.5 compat-w 3.1 direct render: Yes Help intrpreting this would be much appreciated. -- Haines Brown ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Is it dead yet?
Download links are available on the devuan download page https://www.devuan.org/get-devuan choose a mirror (for example, mirror.leaseweb.com/devuan/) then navigate to the devuan_chimaera/ directory where you will hopefully find a desktop-live/ directory which should contain devuan_chimaera_4.0.0_[amd64|i386]_desktop-live.iso along with the shasums files. If you prefer not to use http(s), there are ftp mirrors and torrent on that same download page. Hendrik Boom via Dng wrote: > Then I'd have to figure out how to get a new kernel into it while it crashes > during bootup, > which it now does quite consistently. > > If I had made > recent changes (such as upgrades) I'd consider a kernel problem more likely. > But it has been running for months with only occasional problems, and now I get problems > every time I boot. Since I haven't done an upgrade at all yet this month, I'll suspect hardware. > > Still, I will try, say, a chimaera live CD if I can find one. Where are the Devuan live CD's? > I seem to remember that they were called something other than "devuan". > (Yes, I'm aware that the live CD will likely be a USB stick) > > -- hendrik > > On Tue, Oct 26, 2021 at 7:47 AM Boian Bonev mailto:bbo...@ipacct.com>> wrote: > ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Is it dead yet?
Then I'd have to figure out how to get a new kernel into it while it crashes during bootup, which it now does quite consistently. If I had made recent changes (such as upgrades) I'd consider a kernel problem more likely. But it has been running for months with only occasional problems, and now I get problems every time I boot. Since I haven't done an upgrade at all yet this month, I'll suspect hardware. Still, I will try, say, a chimaera live CD if I can find one. Where are the Devuan live CD's? I seem to remember that they were called something other than "devuan". (Yes, I'm aware that the live CD will likely be a USB stick) -- hendrik On Tue, Oct 26, 2021 at 7:47 AM Boian Bonev wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > Hi Hendrik, > > It is clearly saying that is a soft lockup, if it was a hardware problem it > would say hard lockup isn't it? > > That problem really does not indicate a hardware problem, most probably a > bug > in the kernel; it can also show when a kernel driver is waiting for e.g. > hard > drive that is slow to respond. Try upgrading to a more recent kernel (e.g. > 5.10.x or 5.14.x) - maybe the problem is already fixed there? It may also > be a > temporary condition - a very rare edge case that made the kernel lockup, > then a > reboot will help to clean the state... > > With best regards, > b. > > On Mon, 2021-10-25 at 20:28 -0400, Hendrik Boom via Dng wrote: > > I think I may have a clue to the mysterious stoppages of my server. > > I ssh'd into it today and got the following. It is time to give up on > this > > machine and replace it? > > > > -- hendrik > > > > > > hendrik@april:~$ su - > > Password: > > april:~# ps | grep lighttpd > > ^C^C > > Message from syslogd@april at Oct 25 20:15:48 ... > > kernel:[ 5700.156005] NMI watchdog: BUG: soft lockup - CPU#1 stuck for > 22s! > > [ps:9184] > > > > Message from syslogd@april at Oct 25 20:16:16 ... > > kernel:[ 5728.156005] NMI watchdog: BUG: soft lockup - CPU#1 stuck for > 22s! > > [ps:9184] > > > > Message from syslogd@april at Oct 25 20:16:52 ... > > kernel:[ 5764.156005] NMI watchdog: BUG: soft lockup - CPU#1 stuck for > 23s! > > [ps:9184] > > > > > > Message from syslogd@april at Oct 25 20:17:20 ... > > kernel:[ 5792.156005] NMI watchdog: BUG: soft lockup - CPU#1 stuck for > 22s! > > [ps:9184] > > > > Message from syslogd@april at Oct 25 20:17:56 ... > > kernel:[ 5828.156005] NMI watchdog: BUG: soft lockup - CPU#1 stuck for > 22s! > > [ps:9184] > > > > Message from syslogd@april at Oct 25 20:18:24 ... > > kernel:[ 5856.156005] NMI watchdog: BUG: soft lockup - CPU#1 stuck for > 22s! > > [ps:9184] > > > > Message from syslogd@april at Oct 25 20:18:56 ... > > kernel:[ 5888.156005] NMI watchdog: BUG: soft lockup - CPU#1 stuck for > 22s! > > [ps:9184] > > > > Message from syslogd@april at Oct 25 20:19:24 ... > > kernel:[ 5916.156005] NMI watchdog: BUG: soft lockup - CPU#1 stuck for > 22s! > > [ps:9184] > > > > Message from syslogd@april at Oct 25 20:20:00 ... > > kernel:[ 5952.156005] NMI watchdog: BUG: soft lockup - CPU#1 stuck for > 22s! > > [ps:9184] > > > > Message from syslogd@april at Oct 25 20:20:28 ... > > kernel:[ 5980.156005] NMI watchdog: BUG: soft lockup - CPU#1 stuck for > 22s! > > [ps:9184] > > > > -BEGIN PGP SIGNATURE- > > iQIzBAEBCgAdFiEEumC8IPN+WURNbSUAE2VyCRPS8i0FAmF36qsACgkQE2VyCRPS > 8i13tA//Yc6FzSg/wMjAm1am11kLHIzp31y0v+59ZGuXtHu7h1gatrYrnRAUwnRM > MlaSFkiLO0HWr03db/6GaI0IJsWUWg9hNHuWlbBiQ0fZifCU8zjLLA2nU947t25d > gBFshWFVqwZJ6rEBguZFZpg9AlGe/Ppslc//ONs2C3abvLzfVn/owWbH5Mx8+O6u > raqVYutH7D/qD04I3JNyPQsWURjpVxES579cI1uqG+9wZ6L946YDChH6s4B8an+u > QXLZZyPm4wLapSYuxjM4Es5UmtzN9QY59UtavTnrAPqNtudyuNBPtSfzHtycQsa8 > H0BgxYp2IQxwFQMzAaFTehpQ/eUTqt4DEta40LLK2GZkKs21259RTXTE8LM1Aqrn > T+WsBO5yg+UoxW/mzyipk7nUwzFYA1xUjYvVKyZEXsIyufrxPCvFCuPmV28XiVPu > q0x0hfp7/7vxN8khMBIOeWROM6cEC8CV9wPgVhj4Y7vmHJou7tokB/XD4ugvf5U6 > Ym5c+WQjXiDXVUoYMqLZNs75N5UV3AREq52mr8aPpu6FxCUDjKEywxSBpjuQu7Ch > 6u5B6BxfWw8i/nXb0lAVEYpCp0xHQcqZvVBidEnle2QQ0djV0vNaNUS6vBbsa8F2 > cJSIyWcmHDRkdCv1mj7ot1OpuxUmvBFbsl1sAaFWUCfwVMqqGSE= > =Bbpj > -END PGP SIGNATURE- > > ___ > Dng mailing list > Dng@lists.dyne.org > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng > ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Is it dead yet?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi Hendrik, It is clearly saying that is a soft lockup, if it was a hardware problem it would say hard lockup isn't it? That problem really does not indicate a hardware problem, most probably a bug in the kernel; it can also show when a kernel driver is waiting for e.g. hard drive that is slow to respond. Try upgrading to a more recent kernel (e.g. 5.10.x or 5.14.x) - maybe the problem is already fixed there? It may also be a temporary condition - a very rare edge case that made the kernel lockup, then a reboot will help to clean the state... With best regards, b. On Mon, 2021-10-25 at 20:28 -0400, Hendrik Boom via Dng wrote: > I think I may have a clue to the mysterious stoppages of my server. > I ssh'd into it today and got the following. It is time to give up on this > machine and replace it? > > -- hendrik > > > hendrik@april:~$ su - > Password: > april:~# ps | grep lighttpd > ^C^C > Message from syslogd@april at Oct 25 20:15:48 ... > kernel:[ 5700.156005] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! > [ps:9184] > > Message from syslogd@april at Oct 25 20:16:16 ... > kernel:[ 5728.156005] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! > [ps:9184] > > Message from syslogd@april at Oct 25 20:16:52 ... > kernel:[ 5764.156005] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 23s! > [ps:9184] > > > Message from syslogd@april at Oct 25 20:17:20 ... > kernel:[ 5792.156005] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! > [ps:9184] > > Message from syslogd@april at Oct 25 20:17:56 ... > kernel:[ 5828.156005] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! > [ps:9184] > > Message from syslogd@april at Oct 25 20:18:24 ... > kernel:[ 5856.156005] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! > [ps:9184] > > Message from syslogd@april at Oct 25 20:18:56 ... > kernel:[ 5888.156005] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! > [ps:9184] > > Message from syslogd@april at Oct 25 20:19:24 ... > kernel:[ 5916.156005] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! > [ps:9184] > > Message from syslogd@april at Oct 25 20:20:00 ... > kernel:[ 5952.156005] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! > [ps:9184] > > Message from syslogd@april at Oct 25 20:20:28 ... > kernel:[ 5980.156005] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! > [ps:9184] > -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEumC8IPN+WURNbSUAE2VyCRPS8i0FAmF36qsACgkQE2VyCRPS 8i13tA//Yc6FzSg/wMjAm1am11kLHIzp31y0v+59ZGuXtHu7h1gatrYrnRAUwnRM MlaSFkiLO0HWr03db/6GaI0IJsWUWg9hNHuWlbBiQ0fZifCU8zjLLA2nU947t25d gBFshWFVqwZJ6rEBguZFZpg9AlGe/Ppslc//ONs2C3abvLzfVn/owWbH5Mx8+O6u raqVYutH7D/qD04I3JNyPQsWURjpVxES579cI1uqG+9wZ6L946YDChH6s4B8an+u QXLZZyPm4wLapSYuxjM4Es5UmtzN9QY59UtavTnrAPqNtudyuNBPtSfzHtycQsa8 H0BgxYp2IQxwFQMzAaFTehpQ/eUTqt4DEta40LLK2GZkKs21259RTXTE8LM1Aqrn T+WsBO5yg+UoxW/mzyipk7nUwzFYA1xUjYvVKyZEXsIyufrxPCvFCuPmV28XiVPu q0x0hfp7/7vxN8khMBIOeWROM6cEC8CV9wPgVhj4Y7vmHJou7tokB/XD4ugvf5U6 Ym5c+WQjXiDXVUoYMqLZNs75N5UV3AREq52mr8aPpu6FxCUDjKEywxSBpjuQu7Ch 6u5B6BxfWw8i/nXb0lAVEYpCp0xHQcqZvVBidEnle2QQ0djV0vNaNUS6vBbsa8F2 cJSIyWcmHDRkdCv1mj7ot1OpuxUmvBFbsl1sAaFWUCfwVMqqGSE= =Bbpj -END PGP SIGNATURE- ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Is it dead yet?
On 26-10-2021 02:28, Hendrik Boom via Dng wrote: I think I may have a clue to the mysterious stoppages of my server. I ssh'd into it today and got the following. It is time to give up on this machine and replace it? -- hendrik hendrik@april:~$ su - Password: april:~# ps | grep lighttpd ^C^C Message from syslogd@april at Oct 25 20:15:48 ... kernel:[ 5700.156005] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [ps:9184] Message from syslogd@april at Oct 25 20:16:16 ... kernel:[ 5728.156005] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [ps:9184] Message from syslogd@april at Oct 25 20:16:52 ... kernel:[ 5764.156005] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [ps:9184] Message from syslogd@april at Oct 25 20:17:20 ... kernel:[ 5792.156005] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [ps:9184] Message from syslogd@april at Oct 25 20:17:56 ... kernel:[ 5828.156005] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [ps:9184] Message from syslogd@april at Oct 25 20:18:24 ... kernel:[ 5856.156005] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [ps:9184] Message from syslogd@april at Oct 25 20:18:56 ... kernel:[ 5888.156005] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [ps:9184] Message from syslogd@april at Oct 25 20:19:24 ... kernel:[ 5916.156005] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [ps:9184] Message from syslogd@april at Oct 25 20:20:00 ... kernel:[ 5952.156005] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [ps:9184] Message from syslogd@april at Oct 25 20:20:28 ... kernel:[ 5980.156005] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [ps:9184] ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng I would try another kernel version first that solved it on one of my desktops. Grtz Nick ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
