On 5/4/21 7:13 PM, -pj wrote:

My apologies, this message was intended for the list. :|

-------- Forwarded Message -------- Subject: Re: Reporting saved kernel logs on system that stalls during boot? Date: Tue, 4 May 2021 19:12:13 -0500 From: -pj To: Carlos E. R.

On 5/4/21 3:26 PM, Carlos E. R. wrote:

...

On 04/05/2021 22.07, -pj wrote:

...

I am wondering if it would be possible to maybe get a couple of pointers on what to do next as far as a bug report. I don't know if it is correct to ask more questions in Bugzilla at this point.

First off the bug report is here: -> https://bugzilla.opensuse.org/show_bug.cgi?id=1185542

My computer was able to boot fine with kernel 5.11.16-1-pae

I was asked to install kernel-default for testing purposes 5.12.1-1.g9bb8944-default which I did. kernel-default failed to boot.

So now 3 kernels are installed/listed in the bootmenu as follows.

1. 5.12.1-1.g9bb8944-default 2. 5.12.0-2-pae 3. 5.12.0-1-pae

kernel 5.11.16-1-pae <- Is now gone. Computer is unable to boot to splash screen with any of the 3 above listed kernels. It makes little/some sense since in /etc/zypp/zypp.conf - line 554 multiversion.kernel the kernel 5.11.16-1-pae must have been removed <- I do not understand though because when I installed KOTD the 5.11.16-1-pae was the running kernel.

Quoting the bug report now as per Comment #7 is as follows: "OK, thanks, then it's a generic problem of 32bit Intel kernel. Feel free to uninstall kernel-default again.

Now, we need more details about the crash. Any chance that you have the relevant kernel Oops or panic in the saved kernel logs? Or if not, try to boot without quiet boot option, and check whether you get the stack traces on screen, and take a picture. That's often helpful as a start.".

What does the kernel Oops or saved kernel logs mean? I have the openSUSE https://en.opensuse.org/openSUSE:Report_a_YaST_bug#How_can_I_setup_network_c...

1. Is this y2logs? What is the best way to retrieve these logs that are needed?

No. Those are the YaST logs.

You first run:

journalctl --list-boots

For this to work, the directory "/var/log/journal/" must exist. If it doesn't, create it, for the next time.

Great..I see here: -> https://doc.opensuse.org/documentation/leap/reference/html/book-opensuse-ref... "section 11.1:". Which is the best way to perform this step (due to having kernels that are not allowing boot to Splash screen or desktop)? Will I need to create a Rescue-CD perhaps so that I can check for this "/var/log/journal" directory? I do see "C: Command Line  E: Edit Entry" at the bottom left corner of the "boot menu" screen.

1. Is it best in my reply here to snip off the remainder (bottom portion) of this message before sending?

Thanks.

...

Then select which of the listed boots you want. Then, request the log for that session:

journalctl -b 2

If that is the one you need, then:

journalctl -b 2 > somefilename.log

and attach it to the bugzilla.

Alternatively, you may have "/var/log/boot.msg" for the current boot and "/var/log/boot.omsg" for the previous boot.

However, as the boot crashed, there will be nothing. You have instead to remove "quiet" and take a photo with your camera.

I understand more now since I did not read the entire post before responding initially.  Sometimes the system hangs at the following:    Booting a command list linux Linux 5.12.0-2-pae ... Loading initial ramdisk ... I have now uploaded 3 image links to: -> https://bugzilla.opensuse.org/show_bug.cgi?id=1185542 Thank you for the explanation on "journalctl" usage. I just took a couple more additional photos to add to the Bugzilla report.

...

...

2. I do not want to install the operating system again as it will not help the situation at all most likely.

3. Sometimes I do get stack traces on the screen and am not booting with quiet boot option I believe.

4. I decided to take a photo of the "stack traces" and I have attached the image to this email.

Don't. Upload to susepaste.org, or upload to Bugzilla

It is ok to upload a susepaste.org weblink to Bugzilla correct? -Regards

...