* Setting up to debug kernel @ 2019-10-17 1:14 Jerry DeLisle 2019-10-17 1:24 ` Valdis Klētnieks 0 siblings, 1 reply; 3+ messages in thread From: Jerry DeLisle @ 2019-10-17 1:14 UTC (permalink / raw) To: kernelnewbies@kernelnewbies.org I have a fairly new processor and motherboard. I recently upgraded the BIOS on this system and found that the kernel just locks up, everything freezes within a few minutes. I want to see if I can capture any data from the kernel as this happens. My first thought is to try to connect via a serial port or similarly a USB based port and get some sort of continuous stream of log data that I can capture on another machine. I also suppose that I could use SSH to login remotely and likewise grab logs. Regardless I am looking for recommended best approach here. I suspect a driver issue, so I am going to try to boot to runlevel 3 with just basic console (fancy graphics interface) and proceed from there. Any pointers would be appreciated. Jerry _______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies ^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Setting up to debug kernel 2019-10-17 1:14 Setting up to debug kernel Jerry DeLisle @ 2019-10-17 1:24 ` Valdis Klētnieks 2019-10-19 18:01 ` Jerry DeLisle 0 siblings, 1 reply; 3+ messages in thread From: Valdis Klētnieks @ 2019-10-17 1:24 UTC (permalink / raw) To: Jerry DeLisle; +Cc: kernelnewbies@kernelnewbies.org [-- Attachment #1.1: Type: text/plain, Size: 536 bytes --] On Wed, 16 Oct 2019 18:14:10 -0700, Jerry DeLisle said: > My first thought is to try to connect via a serial port or similarly a USB based > port and get some sort of continuous stream of log data that I can capture on > another machine. If you have a network, netconsole may be an option. If you are using UEFI boot, using pstore to save the panic message might work as well. > I also suppose that I could use SSH to login remotely and likewise grab logs. If your kernel is in fact locking up, SSH will probably not be an option. [-- Attachment #1.2: Type: application/pgp-signature, Size: 832 bytes --] [-- Attachment #2: Type: text/plain, Size: 170 bytes --] _______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies ^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Setting up to debug kernel 2019-10-17 1:24 ` Valdis Klētnieks @ 2019-10-19 18:01 ` Jerry DeLisle 0 siblings, 0 replies; 3+ messages in thread From: Jerry DeLisle @ 2019-10-19 18:01 UTC (permalink / raw) To: Valdis Klētnieks; +Cc: kernelnewbies@kernelnewbies.org On 10/16/19 6:24 PM, Valdis Klētnieks wrote: > On Wed, 16 Oct 2019 18:14:10 -0700, Jerry DeLisle said: > >> My first thought is to try to connect via a serial port or similarly a USB based >> port and get some sort of continuous stream of log data that I can capture on >> another machine. > > If you have a network, netconsole may be an option. If you are using UEFI > boot, using pstore to save the panic message might work as well. > >> I also suppose that I could use SSH to login remotely and likewise grab logs. > > If your kernel is in fact locking up, SSH will probably not be an option. > I managed to get a picture of the console. I posted everything here: https://bugzilla.kernel.org/show_bug.cgi?id=205017 _______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies ^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2019-10-19 18:02 UTC | newest] Thread overview: 3+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2019-10-17 1:14 Setting up to debug kernel Jerry DeLisle 2019-10-17 1:24 ` Valdis Klētnieks 2019-10-19 18:01 ` Jerry DeLisle
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).