Re: My PC is crashing
I suspect a bad IMG/ISO file. Have you checked its hash? or I suggest a redownload, rewrite / check and new install. Jadi On Sat, May 11, 2024 at 1:04 AM Daniel Hejduk wrote: > Hello again, > I tried memtest and it passed :D > But after some trying to debug it I found something the sudden shutdown > corrupts disk. > One particular file "/share/relink/kernel/GENERIC.MP/gap.o" was always > corrupted. > So it happens when kernel is relinking. > > How you told me I tried using i386 but it didn't boot by flashing it on > USB nor using Ventoy. > Ventoy will always prompt me "Maybe the image does not support X64 UEFI", > so I tried enabling legacy but again nothing. > Is there way to boot i386, or fix the relinking error? > > Thank you for helping me on my journey. > > Best regards, > Daniel Hejduk > > > 10. května 2024 9:33:59 SELČ, Stuart Henderson > napsal: > >> On 2024-05-10, Peter N. M. Hansteen wrote: >> >>> On Fri, May 10, 2024 at 08:48:56AM +0200, Anders Andersson wrote: >>> Missing from the FAQ is IMO step 0: Run memtest over night to rule out hard to debug hardware problems. It won't catch everything of course, but it usually finds RAM issues which is its main job. >>> >>> That is a very valid point. >>> >>> Bad RAM could very well be the cause of the problems described. And on >>> a side note, given that the memory allocation in OpenBSD is different than >>> what some other systems do, it is not unlikely that other systems never >>> or only rarely would hit the failing memory location while OpenBSD would, >>> more often. >>> >> >> Yet it was able to do an install and relink the kernel while in the >> installer. Also IME memory-related problems are more likely to result in >> crashes rather than the machine shutting down. This doesn't completely >> rule out memory problems, but it's more likely to result from a >> difference between RAMDISK and GENERIC.MP kernels. >> >> First things first, Daniel: >> >> - if you used i386, try amd64 instead. >> >> - if you configured to run X in the installer, try without that. >> >> - try going back a release or two, is there any difference? >> >>
Re: My PC is crashing
Hello again, I tried memtest and it passed :D But after some trying to debug it I found something the sudden shutdown corrupts disk. One particular file "/share/relink/kernel/GENERIC.MP/gap.o" was always corrupted. So it happens when kernel is relinking. How you told me I tried using i386 but it didn't boot by flashing it on USB nor using Ventoy. Ventoy will always prompt me "Maybe the image does not support X64 UEFI", so I tried enabling legacy but again nothing. Is there way to boot i386, or fix the relinking error? Thank you for helping me on my journey. Best regards, Daniel Hejduk 10. května 2024 9:33:59 SELČ, Stuart Henderson napsal: >On 2024-05-10, Peter N. M. Hansteen wrote: >> On Fri, May 10, 2024 at 08:48:56AM +0200, Anders Andersson wrote: >>> Missing from the FAQ is IMO step 0: Run memtest over night to rule out >>> hard to debug hardware problems. It won't catch everything of course, >>> but it usually finds RAM issues which is its main job. >> >> That is a very valid point. >> >> Bad RAM could very well be the cause of the problems described. And on >> a side note, given that the memory allocation in OpenBSD is different than >> what some other systems do, it is not unlikely that other systems never >> or only rarely would hit the failing memory location while OpenBSD would, >> more often. > >Yet it was able to do an install and relink the kernel while in the >installer. Also IME memory-related problems are more likely to result in >crashes rather than the machine shutting down. This doesn't completely >rule out memory problems, but it's more likely to result from a >difference between RAMDISK and GENERIC.MP kernels. > >First things first, Daniel: > >- if you used i386, try amd64 instead. > >- if you configured to run X in the installer, try without that. > >- try going back a release or two, is there any difference? > >-- >Please keep replies on the mailing list. >
Re: My PC is crashing
On 2024-05-10, Peter N. M. Hansteen wrote: > On Fri, May 10, 2024 at 08:48:56AM +0200, Anders Andersson wrote: >> Missing from the FAQ is IMO step 0: Run memtest over night to rule out >> hard to debug hardware problems. It won't catch everything of course, >> but it usually finds RAM issues which is its main job. > > That is a very valid point. > > Bad RAM could very well be the cause of the problems described. And on > a side note, given that the memory allocation in OpenBSD is different than > what some other systems do, it is not unlikely that other systems never > or only rarely would hit the failing memory location while OpenBSD would, > more often. Yet it was able to do an install and relink the kernel while in the installer. Also IME memory-related problems are more likely to result in crashes rather than the machine shutting down. This doesn't completely rule out memory problems, but it's more likely to result from a difference between RAMDISK and GENERIC.MP kernels. First things first, Daniel: - if you used i386, try amd64 instead. - if you configured to run X in the installer, try without that. - try going back a release or two, is there any difference? -- Please keep replies on the mailing list.
Re: My PC is crashing
On Fri, May 10, 2024 at 08:48:56AM +0200, Anders Andersson wrote: > Missing from the FAQ is IMO step 0: Run memtest over night to rule out > hard to debug hardware problems. It won't catch everything of course, > but it usually finds RAM issues which is its main job. That is a very valid point. Bad RAM could very well be the cause of the problems described. And on a side note, given that the memory allocation in OpenBSD is different than what some other systems do, it is not unlikely that other systems never or only rarely would hit the failing memory location while OpenBSD would, more often. -- Peter N. M. Hansteen, member of the first RFC 1149 implementation team https://bsdly.blogspot.com/ https://www.bsdly.net/ https://www.nuug.no/ "Remember to set the evil bit on all malicious network traffic" delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.
Re: My PC is crashing
On Fri, May 10, 2024 at 8:14 AM Peter N. M. Hansteen wrote: > > Hi Daniel, > > On Fri, May 10, 2024 at 07:57:31AM +0200, Daniel Hejduk wrote: > > Hello, > > I installed OBSD on my IdeaPad. > > Install went fine I installed offline using .iso file. > > But after rebooting it works for ~30 seconds and after that it shutdowns, > > without any errors kernel panics nothing. > > > > How can I debug it? I will send you more info if I found something. > > The FAQ has a reasonable description of how to debug and report observed > problems at https://www.openbsd.org/report.html > Missing from the FAQ is IMO step 0: Run memtest over night to rule out hard to debug hardware problems. It won't catch everything of course, but it usually finds RAM issues which is its main job.
Re: My PC is crashing
Hi Daniel, On Fri, May 10, 2024 at 07:57:31AM +0200, Daniel Hejduk wrote: > Hello, > I installed OBSD on my IdeaPad. > Install went fine I installed offline using .iso file. > But after rebooting it works for ~30 seconds and after that it shutdowns, > without any errors kernel panics nothing. > > How can I debug it? I will send you more info if I found something. The FAQ has a reasonable description of how to debug and report observed problems at https://www.openbsd.org/report.html That said, I would start with looking at the output of dmesg and any traces of what happened immediately before the incidents in the log files such as /var/log/messages (and any other possibly relevant log files). -- Peter N. M. Hansteen, member of the first RFC 1149 implementation team https://bsdly.blogspot.com/ https://www.bsdly.net/ https://www.nuug.no/ "Remember to set the evil bit on all malicious network traffic" delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.
