From: hdf3@comcast.net (don fisher)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Problem with netconsole and eth0 timing
Date: Thu, 27 Sep 2018 15:16:14 -0700 [thread overview]
Message-ID: <538fdb25-28fb-60b9-9924-c985b02084d7@comcast.net> (raw)
In-Reply-To: <117350.1538031686@turing-police.cc.vt.edu>
On 9/27/18 12:01 AM, valdis.kletnieks at vt.edu wrote:
> On Wed, 26 Sep 2018 21:38:27 -0700, don fisher said:
>
>> Thanks. I tried building with the driver embedded in the kernel, but the
>> compile failed with a halt. No crash is apparent, just a halt. It turned
>> out that this was repeated until I removed the netconsole command during
>> boot. System appears stable now. I will try tomorrow to embed the
>> driver, then add netconsole option in the command line.
>
> Wait, what? The *compile* "failed with a halt"? What the heck does that mean?
>
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
Don't know what it means. The compile just happened to be what I was
execution. The system just stopped with no output to screen, dmesg or
journal. With trial an error I discovered that if I eliminated the
netconsole command from the grub2 linux command line, the system
appeared stable again. I put that netconsole command in
/etc/default/grub, so it is sort of a pain to insert and remove it.
Don
next prev parent reply other threads:[~2018-09-27 22:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-26 1:26 Problem with netconsole and eth0 timing don fisher
2018-09-26 2:26 ` valdis.kletnieks at vt.edu
2018-09-26 20:25 ` don fisher
2018-09-26 21:33 ` valdis.kletnieks at vt.edu
2018-09-27 4:38 ` don fisher
2018-09-27 7:01 ` valdis.kletnieks at vt.edu
2018-09-27 22:16 ` don fisher [this message]
2018-09-27 23:52 ` don fisher
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=538fdb25-28fb-60b9-9924-c985b02084d7@comcast.net \
--to=hdf3@comcast.net \
--cc=kernelnewbies@lists.kernelnewbies.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).