[opensuse] How to get eth0 up early in boot process
I am trying to use netconsole to examine some problems I am having booting certain laptops. I am running opensuse 42.3 with generic 4.18.7 kernel configured to include netconsole. After building my kernel and including the proper command (as shown below) in the linux boot string: netconsole=64001@192.168.7.60/eth0,64001@192.168.7.55/34:e6:d7:01:2a:dd I receive the following error message as shown by journalctl: sudo journalctl -b | grep netconsole Sep 24 22:01:25 dfpc60 kernel: netpoll: netconsole: local port 64001 Sep 24 22:01:25 dfpc60 kernel: netpoll: netconsole: local IPv4 address 192.168.7.60 Sep 24 22:01:25 dfpc60 kernel: netpoll: netconsole: interface 'eth0' Sep 24 22:01:25 dfpc60 kernel: netpoll: netconsole: remote port 64001 Sep 24 22:01:25 dfpc60 kernel: netpoll: netconsole: remote IPv4 address 192.168.7.55 Sep 24 22:01:25 dfpc60 kernel: netpoll: netconsole: remote ethernet address 34:e6:d7:01:2a:dd Sep 24 22:01:25 dfpc60 kernel: netpoll: netconsole: eth0 doesn't exist, aborting Sep 24 22:01:25 dfpc60 kernel: netconsole: cleaning up Sep 24 22:01:25 dfpc60 systemd-modules-load[185]: Module 'netconsole' is builtin From Google(netpoll is intended for monitoring multiple file descriptors to see if I/O is possible on any of them. It supports edge-triggered and level-triggered interfaces.) I looked at dmesg and netconsole is trying eth0: at 2.348515 sec after boot. The first other mention I see of eth0: is at 9.739663 sec. The message is: [ 9.739663] alx 0000:3c:00.0 eth0: Qualcomm Atheros AR816x/AR817x Ethernet [a4:4c:c8:5e:e0:12] which I assume is just recognition if loading the driver. From sudo journalctl -b | grep eth0: Sep 24 22:02:01 dfpc60 wicked[942]: eth0 up Wicked seems to appear about half a second after netconsole looks for eth0: Is there something I can do in systemd, the eth0: configuration, or elsewhere to get wicked to load eth0 earlier? I was a little surprised that netconsole did not go back and try again a little later. Thanks Don -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 9/25/18 4:21 PM, don fisher wrote:
I am trying to use netconsole to examine some problems I am having booting certain laptops. I am running opensuse 42.3 with generic 4.18.7 kernel configured to include netconsole. After building my kernel and including the proper command (as shown below) in the linux boot string: netconsole=64001@192.168.7.60/eth0,64001@192.168.7.55/34:e6:d7:01:2a:dd I receive the following error message as shown by journalctl:
sudo journalctl -b | grep netconsole Sep 24 22:01:25 dfpc60 kernel: netpoll: netconsole: local port 64001 Sep 24 22:01:25 dfpc60 kernel: netpoll: netconsole: local IPv4 address 192.168.7.60 Sep 24 22:01:25 dfpc60 kernel: netpoll: netconsole: interface 'eth0' Sep 24 22:01:25 dfpc60 kernel: netpoll: netconsole: remote port 64001 Sep 24 22:01:25 dfpc60 kernel: netpoll: netconsole: remote IPv4 address 192.168.7.55 Sep 24 22:01:25 dfpc60 kernel: netpoll: netconsole: remote ethernet address 34:e6:d7:01:2a:dd Sep 24 22:01:25 dfpc60 kernel: netpoll: netconsole: eth0 doesn't exist, aborting Sep 24 22:01:25 dfpc60 kernel: netconsole: cleaning up Sep 24 22:01:25 dfpc60 systemd-modules-load[185]: Module 'netconsole' is builtin
From Google(netpoll is intended for monitoring multiple file descriptors to see if I/O is possible on any of them. It supports edge-triggered and level-triggered interfaces.)
I looked at dmesg and netconsole is trying eth0: at 2.348515 sec after boot. The first other mention I see of eth0: is at 9.739663 sec. The message is:
[ 9.739663] alx 0000:3c:00.0 eth0: Qualcomm Atheros AR816x/AR817x Ethernet [a4:4c:c8:5e:e0:12] which I assume is just recognition if loading the driver.
From sudo journalctl -b | grep eth0: Sep 24 22:02:01 dfpc60 wicked[942]: eth0 up
Wicked seems to appear about half a second after netconsole looks for eth0:
Is there something I can do in systemd, the eth0: configuration, or elsewhere to get wicked to load eth0 earlier? I was a little surprised that netconsole did not go back and try again a little later.
Thanks Don
Sep 24 22:01:25.080603 Sep 24 22:01:34.112744 Additional data. I spent more time with journal ctl and obtained more accurate time stamps. netconsole Sep 24 22:01:25.080603 eth0: avail Sep 24 22:01:34.112744
difference is 9.032140 This is larger than I obtained before with rough time stamps. Don -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
26.09.2018 03:51, don fisher пишет:
On 9/25/18 4:21 PM, don fisher wrote:
I am trying to use netconsole to examine some problems I am having booting certain laptops. I am running opensuse 42.3 with generic 4.18.7 kernel configured to include netconsole. After building my kernel and including the proper command (as shown below) in the linux boot string: netconsole=64001@192.168.7.60/eth0,64001@192.168.7.55/34:e6:d7:01:2a:dd I receive the following error message as shown by journalctl:
sudo journalctl -b | grep netconsole Sep 24 22:01:25 dfpc60 kernel: netpoll: netconsole: local port 64001 Sep 24 22:01:25 dfpc60 kernel: netpoll: netconsole: local IPv4 address 192.168.7.60 Sep 24 22:01:25 dfpc60 kernel: netpoll: netconsole: interface 'eth0' Sep 24 22:01:25 dfpc60 kernel: netpoll: netconsole: remote port 64001 Sep 24 22:01:25 dfpc60 kernel: netpoll: netconsole: remote IPv4 address 192.168.7.55 Sep 24 22:01:25 dfpc60 kernel: netpoll: netconsole: remote ethernet address 34:e6:d7:01:2a:dd Sep 24 22:01:25 dfpc60 kernel: netpoll: netconsole: eth0 doesn't exist, aborting Sep 24 22:01:25 dfpc60 kernel: netconsole: cleaning up Sep 24 22:01:25 dfpc60 systemd-modules-load[185]: Module 'netconsole' is builtin
From Google(netpoll is intended for monitoring multiple file descriptors to see if I/O is possible on any of them. It supports edge-triggered and level-triggered interfaces.)
I looked at dmesg and netconsole is trying eth0: at 2.348515 sec after boot. The first other mention I see of eth0: is at 9.739663 sec. The message is:
[ 9.739663] alx 0000:3c:00.0 eth0: Qualcomm Atheros AR816x/AR817x Ethernet [a4:4c:c8:5e:e0:12] which I assume is just recognition if loading the driver.
From sudo journalctl -b | grep eth0: Sep 24 22:02:01 dfpc60 wicked[942]: eth0 up
Wicked seems to appear about half a second after netconsole looks for eth0:
Is there something I can do in systemd, the eth0: configuration, or elsewhere to get wicked to load eth0 earlier?
How do you imagine loading eth0 before kernel is loaded? You have two obvious choices a) if you insist on building netconsole into kernel, you need to build ethernet driver into kernel as well (including any firmware it requires) b) build netconsole as module and load it after ethernet driver is loaded
I was a little surprised
that netconsole did not go back and try again a little later.
Thanks Don
Sep 24 22:01:25.080603 Sep 24 22:01:34.112744 Additional data. I spent more time with journal ctl and obtained more accurate time stamps. netconsole Sep 24 22:01:25.080603 eth0: avail Sep 24 22:01:34.112744
difference is 9.032140
This is larger than I obtained before with rough time stamps.
Don
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 9/25/18 9:06 PM, Andrei Borzenkov wrote:
26.09.2018 03:51, don fisher пишет:
On 9/25/18 4:21 PM, don fisher wrote:
How do you imagine loading eth0 before kernel is loaded? You have two obvious choices
a) if you insist on building netconsole into kernel, you need to build ethernet driver into kernel as well (including any firmware it requires)
b) build netconsole as module and load it after ethernet driver is loaded
Thanks. I will try to include the driver in the kernel, not as a module. This is an experiment for me since I do not know how to tell it what ip address etc. to use. Can probably be done in kernel command line, but are unaware of any examples. I did try netconsole as a module, and tried loading in with a command in /etc/modprobe.d. I did not appear to work. Not sure why. I need to get netconsole loaded before the user login, and hopefully before the crash which I believe is related to the nouveau Nvidia driver. Thanks for the reply Don -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 09/26/2018 03:51 PM, don fisher wrote:
On 9/25/18 9:06 PM, Andrei Borzenkov wrote:
26.09.2018 03:51, don fisher пишет:
On 9/25/18 4:21 PM, don fisher wrote:
How do you imagine loading eth0 before kernel is loaded? You have two obvious choices
a) if you insist on building netconsole into kernel, you need to build ethernet driver into kernel as well (including any firmware it requires)
b) build netconsole as module and load it after ethernet driver is loaded
Thanks. I will try to include the driver in the kernel, not as a module. This is an experiment for me since I do not know how to tell it what ip address etc. to use. Can probably be done in kernel command line, but are unaware of any examples. I did try netconsole as a module, and tried loading in with a command in /etc/modprobe.d. I did not appear to work. Not sure why. I need to get netconsole loaded before the user login, and hopefully before the crash which I believe is related to the nouveau Nvidia driver.
Would a serial console be available earlier? Linux supports that. All you need is a computer running Miniterm and a serial port. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 9/26/18 3:06 PM, James Knott wrote:
On 09/26/2018 03:51 PM, don fisher wrote:
On 9/25/18 9:06 PM, Andrei Borzenkov wrote:
26.09.2018 03:51, don fisher пишет:
On 9/25/18 4:21 PM, don fisher wrote:
How do you imagine loading eth0 before kernel is loaded? You have two obvious choices
a) if you insist on building netconsole into kernel, you need to build ethernet driver into kernel as well (including any firmware it requires)
b) build netconsole as module and load it after ethernet driver is loaded
Thanks. I will try to include the driver in the kernel, not as a module. This is an experiment for me since I do not know how to tell it what ip address etc. to use. Can probably be done in kernel command line, but are unaware of any examples. I did try netconsole as a module, and tried loading in with a command in /etc/modprobe.d. I did not appear to work. Not sure why. I need to get netconsole loaded before the user login, and hopefully before the crash which I believe is related to the nouveau Nvidia driver.
Would a serial console be available earlier? Linux supports that. All you need is a computer running Miniterm and a serial port.
I cannot remember the last laptop I saw with a serial port, or a printer port. Modern laptops seem to have dispensed with all of those to become thinner and lighter. Don -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 09/26/2018 08:04 PM, don fisher wrote:
I cannot remember the last laptop I saw with a serial port, or a printer port. Modern laptops seem to have dispensed with all of those to become thinner and lighter.
I have a USB serial port I use with routers etc. They're cheap. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 26/09/2018 20.09, James Knott wrote:
On 09/26/2018 08:04 PM, don fisher wrote:
I cannot remember the last laptop I saw with a serial port, or a printer port. Modern laptops seem to have dispensed with all of those to become thinner and lighter.
I have a USB serial port I use with routers etc. They're cheap.
You need a real hardware serial port on the machine that is analyzed. An USB will not work, needs the USB stack to be loaded. The "rs232" stack is very low level. A direct CPU port. Some mainboards still have it. -- Cheers / Saludos, Carlos E. R. (from openSUSE 15.0 (Legolas))
On 09/26/2018 10:11 PM, Carlos E. R. wrote:
Some mainboards still have it.
On my momboard, which I bought a few years ago, the header is there but no connector on the back. That wouldn't be hard to make for someone who's technically inclined. BTW, I as I mentioned earlier, I'm rereading "The Cuckoo's Egg", by Clifford Stoll. There's one part there where he's getting a bunch of printers, to copy the attacker's traffic. I was sitting there thinking why not connect to serial ports and have the computer log the traffic, instead of wasting all that paper. Way back in the 80s, which is the period this book is written about, I was connecting serial ports to data circuits for monitoring purposes. Easy to do. All you need is serial ports and those mini-computers generally had several. We even had dedicated test sets to capture data and display on 2 lines at a time, one for each direction, for full duplex connections. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 26/09/2018 22.42, James Knott wrote:
On 09/26/2018 10:11 PM, Carlos E. R. wrote:
Some mainboards still have it.
On my momboard, which I bought a few years ago, the header is there but no connector on the back. That wouldn't be hard to make for someone who's technically inclined.
Yes, my board is like that. I grabbed an old connector from my old box of things and odds and just had to make it a bit longer.
BTW, I as I mentioned earlier, I'm rereading "The Cuckoo's Egg", by Clifford Stoll. There's one part there where he's getting a bunch of printers, to copy the attacker's traffic. I was sitting there thinking why not connect to serial ports and have the computer log the traffic, instead of wasting all that paper. Way back in the 80s, which is the period this book is written about, I was connecting serial ports to data circuits for monitoring purposes. Easy to do. All you need is serial ports and those mini-computers generally had several. We even had dedicated test sets to capture data and display on 2 lines at a time, one for each direction, for full duplex connections.
I saw serial printers used for monitoring big machines. -- Cheers / Saludos, Carlos E. R. (from openSUSE 15.0 (Legolas))
On 09/27/2018 07:29 AM, Carlos E. R. wrote:
BTW, I as I mentioned earlier, I'm rereading "The Cuckoo's Egg", by Clifford Stoll. There's one part there where he's getting a bunch of printers, to copy the attacker's traffic. I was sitting there thinking why not connect to serial ports and have the computer log the traffic, instead of wasting all that paper. Way back in the 80s, which is the period this book is written about, I was connecting serial ports to data circuits for monitoring purposes. Easy to do. All you need is serial ports and those mini-computers generally had several. We even had dedicated test sets to capture data and display on 2 lines at a time, one for each direction, for full duplex connections. I saw serial printers used for monitoring big machines.
As have I and that's what he was using. Regardless saving to a file makes it easier to search and save paper. I don't know what he was using for hardware, but if a VAX, a spare DZ11 board would provide 8 serial ports. As it was, they were using a spare computer, running Unix, to watch for the guy. If they were already doing that, it wouldn't be hard to capture the data. BTW, that book's an excellent read. It can be found for free download on the Internet. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 27/09/2018 08.55, James Knott wrote:
On 09/27/2018 07:29 AM, Carlos E. R. wrote:
BTW, that book's an excellent read. It can be found for free download on the Internet.
Oh? Guttemberg project, perhaps? I quick google search doesn't find it, except Amazon selling it. -- Cheers / Saludos, Carlos E. R. (from openSUSE 15.0 (Legolas))
On 09/27/2018 10:21 AM, Carlos E. R. wrote:
On 27/09/2018 08.55, James Knott wrote:
On 09/27/2018 07:29 AM, Carlos E. R. wrote:
BTW, that book's an excellent read. It can be found for free download on the Internet. Oh? Guttemberg project, perhaps?
I quick google search doesn't find it, except Amazon selling it.
This isn't where I found it, but you could try here: http://bayrampasamakina.com/tr/pdf_stoll_4_1.pdf -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 09/27/2018 10:29 AM, James Knott wrote:
I quick google search doesn't find it, except Amazon selling it.
This isn't where I found it, but you could try here: http://bayrampasamakina.com/tr/pdf_stoll_4_1.pdf
There's also this info about the story behind the book: http://pdf.textfiles.com/academics/wilyhacker.pdf -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 27/09/2018 10.36, James Knott wrote:
On 09/27/2018 10:29 AM, James Knott wrote:
I quick google search doesn't find it, except Amazon selling it.
This isn't where I found it, but you could try here: http://bayrampasamakina.com/tr/pdf_stoll_4_1.pdf
There's also this info about the story behind the book: http://pdf.textfiles.com/academics/wilyhacker.pdf
Thanks. I read the Wikipedia article on it. -- Cheers / Saludos, Carlos E. R. (from openSUSE 15.0 (Legolas))
On 2018-09-26 10:42 p.m., James Knott wrote:
There's one part there where he's getting a bunch of printers, to copy the attacker's traffic. I was sitting there thinking why not connect to serial ports and have the computer log the traffic, instead of wasting all that paper.
One word: EVIDENCE Peoeple, the courts, basses and managers, were not so computer savvy back then. As far as the courts and managers were concerned if it wasn't hard copy it wasn't real. towards the end of the 1970s I had a manager who didn't believe in compilers. He wanted to see assembly code. He diodn't believe in inkers either, we had to include all the library source in the assembly code. One hell of a large paper tape spool. Yes, PAPER tape. Mag tape wasn't real for him. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Op donderdag 27 september 2018 02:04:21 CEST schreef don fisher:
On 9/26/18 3:06 PM, James Knott wrote:
On 09/26/2018 03:51 PM, don fisher wrote:
On 9/25/18 9:06 PM, Andrei Borzenkov wrote:
26.09.2018 03:51, don fisher пишет:
On 9/25/18 4:21 PM, don fisher wrote: How do you imagine loading eth0 before kernel is loaded? You have two obvious choices
a) if you insist on building netconsole into kernel, you need to build ethernet driver into kernel as well (including any firmware it requires)
b) build netconsole as module and load it after ethernet driver is loaded
Thanks. I will try to include the driver in the kernel, not as a module. This is an experiment for me since I do not know how to tell it what ip address etc. to use. Can probably be done in kernel command line, but are unaware of any examples. I did try netconsole as a module, and tried loading in with a command in /etc/modprobe.d. I did not appear to work. Not sure why. I need to get netconsole loaded before the user login, and hopefully before the crash which I believe is related to the nouveau Nvidia driver.
Would a serial console be available earlier? Linux supports that. All you need is a computer running Miniterm and a serial port.
I cannot remember the last laptop I saw with a serial port, or a printer port. Modern laptops seem to have dispensed with all of those to become thinner and lighter.
Don Yep, a lot of these ultrabooks don't even have an ethernet port anymore
What's the reason for going this path, Don? -- Gertjan Lettink a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
James Knott wrote:
On 09/26/2018 08:11 PM, Knurpht-openSUSE wrote:
What's the reason for going this path, Don?
I was thinking a serial console might be available sooner than Ethernet.
Depending on the hardware, you get everything including POST. -- Per Jessen, Zürich (9.8°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 9/26/18 5:11 PM, Knurpht-openSUSE wrote:
Op donderdag 27 september 2018 02:04:21 CEST schreef don fisher:
On 9/26/18 3:06 PM, James Knott wrote:
On 09/26/2018 03:51 PM, don fisher wrote:
On 9/25/18 9:06 PM, Andrei Borzenkov wrote:
26.09.2018 03:51, don fisher пишет:
On 9/25/18 4:21 PM, don fisher wrote: How do you imagine loading eth0 before kernel is loaded? You have two obvious choices
a) if you insist on building netconsole into kernel, you need to build ethernet driver into kernel as well (including any firmware it requires)
b) build netconsole as module and load it after ethernet driver is loaded
Thanks. I will try to include the driver in the kernel, not as a module. This is an experiment for me since I do not know how to tell it what ip address etc. to use. Can probably be done in kernel command line, but are unaware of any examples. I did try netconsole as a module, and tried loading in with a command in /etc/modprobe.d. I did not appear to work. Not sure why. I need to get netconsole loaded before the user login, and hopefully before the crash which I believe is related to the nouveau Nvidia driver.
Would a serial console be available earlier? Linux supports that. All you need is a computer running Miniterm and a serial port.
I cannot remember the last laptop I saw with a serial port, or a printer port. Modern laptops seem to have dispensed with all of those to become thinner and lighter.
Don Yep, a lot of these ultrabooks don't even have an ethernet port anymore
What's the reason for going this path, Don?
My laptop crashes with the nouveau Nvidia driver loaded. I wanted to report the crash dump to the nouveau site to see if they were aware of the problem. I need the output during boot, before entering user mode. Don -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
don fisher wrote:
On 9/26/18 5:11 PM, Knurpht-openSUSE wrote:
What's the reason for going this path, Don?
My laptop crashes with the nouveau Nvidia driver loaded. I wanted to report the crash dump to the nouveau site to see if they were aware of the problem. I need the output during boot, before entering user mode.
I don't think you need a network or serial console for that - that happens quite late in the boot-process, the output ought to be in the journal or the kernel ring-buffer. -- Per Jessen, Zürich (9.9°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
26.09.2018 22:51, don fisher пишет:
On 9/25/18 9:06 PM, Andrei Borzenkov wrote:
26.09.2018 03:51, don fisher пишет:
On 9/25/18 4:21 PM, don fisher wrote:
How do you imagine loading eth0 before kernel is loaded? You have two obvious choices
a) if you insist on building netconsole into kernel, you need to build ethernet driver into kernel as well (including any firmware it requires)
b) build netconsole as module and load it after ethernet driver is loaded
Thanks. I will try to include the driver in the kernel, not as a module. This is an experiment for me since I do not know how to tell it what ip address etc. to use. Can probably be done in kernel command line, but are unaware of any examples.
You are banned by google? https://www.kernel.org/doc/Documentation/networking/netconsole.txt
I did try netconsole as a module, and tried loading in with a command in /etc/modprobe.d. I did not appear to work.
You forgot to show what you did so I take it it as rant instead of question.
Not sure why. I need to get netconsole loaded before the user login, and hopefully before the crash which I believe is related to the nouveau Nvidia driver.
Thanks for the reply Don
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 9/26/18 8:58 PM, Andrei Borzenkov wrote:
26.09.2018 22:51, don fisher пишет:
On 9/25/18 9:06 PM, Andrei Borzenkov wrote:
26.09.2018 03:51, don fisher пишет:
On 9/25/18 4:21 PM, don fisher wrote:
How do you imagine loading eth0 before kernel is loaded? You have two obvious choices
a) if you insist on building netconsole into kernel, you need to build ethernet driver into kernel as well (including any firmware it requires)
b) build netconsole as module and load it after ethernet driver is loaded
Thanks. I will try to include the driver in the kernel, not as a module. This is an experiment for me since I do not know how to tell it what ip address etc. to use. Can probably be done in kernel command line, but are unaware of any examples.
You are banned by google?
https://www.kernel.org/doc/Documentation/networking/netconsole.txt
I did try netconsole as a module, and tried loading in with a command in /etc/modprobe.d. I did not appear to work.
You forgot to show what you did so I take it it as rant instead of question.
What I did is: In /etc/modprobe.d/20-netconsole.conf, there is the line: options netconsole netconsole=64001@192.168.7.60/eth0,64001@192.168.7.55/34:e6:d7:01:2a:dd as described in the link you referenced. That is the same line I used with the native module netconsole. I also tried in user mode the route where you: CONFIGFS_FS NETCONSOLE NETCONSOLE_DYNAMIC and load parameters into /sys/kernel/config/netconsole/hostname/*. This works fine, but is not available early enough in the boot sequence to report the crash. My goal is to record the messages displayed on my screen at crash so that I can report the problem with some clarity. Don -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 09/26/2018 11:27 PM, don fisher wrote:
My goal is to record the messages displayed on my screen at crash so that I can report the problem with some clarity.
Don
Scroll-Lock and a cell-phone picture always worked in the past.... -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 9/27/18 12:32 AM, David C. Rankin wrote:
On 09/26/2018 11:27 PM, don fisher wrote:
My goal is to record the messages displayed on my screen at crash so that I can report the problem with some clarity.
Don
Scroll-Lock and a cell-phone picture always worked in the past....
I will try that. No scroll lock on my keyboard, but he code is 145 so I will hunt some combination of keys to generate that. Ctrl-s did not work! Don -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 27/09/2018 18.07, don fisher wrote:
On 9/27/18 12:32 AM, David C. Rankin wrote:
On 09/26/2018 11:27 PM, don fisher wrote:
My goal is to record the messages displayed on my screen at crash so that I can report the problem with some clarity.
Don
Scroll-Lock and a cell-phone picture always worked in the past....
I will try that. No scroll lock on my keyboard, but he code is 145 so I will hunt some combination of keys to generate that. Ctrl-s did not work!
Another option then is to do a video and capture stills from it. I've never done that, I think they may come out blurry. -- Cheers / Saludos, Carlos E. R. (from openSUSE 15.0 (Legolas))
Le 28/09/2018 à 16:22, Carlos E. R. a écrit :
Another option then is to do a video and capture stills from it. I've never done that, I think they may come out blurry.
it wotks, not nice but usable jdd -- http://dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
27.09.2018 07:27, don fisher пишет:
I did try netconsole as a module, and tried loading in with a command in /etc/modprobe.d. I did not appear to work.
You forgot to show what you did so I take it it as rant instead of question.
What I did is:
In /etc/modprobe.d/20-netconsole.conf, there is the line:
options netconsole netconsole=64001@192.168.7.60/eth0,64001@192.168.7.55/34:e6:d7:01:2a:dd
as described in the link you referenced.
This is not "command" and it does not load anything. It just provides options for module when (if) module is loaded. Did you load netconsole module at all?
That is the same line I used with the native module netconsole. I also tried in user mode the route where you: CONFIGFS_FS NETCONSOLE NETCONSOLE_DYNAMIC
and load parameters into /sys/kernel/config/netconsole/hostname/*. This works fine, but is not available early enough in the boot sequence to report the crash.
It is not clear again. You mean, crash happens before ethernet driver is loaded and you can configure netconsole to use it?
My goal is to record the messages displayed on my screen at crash so that I can report the problem with some clarity.
Don
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 9/27/18 9:08 PM, Andrei Borzenkov wrote:
27.09.2018 07:27, don fisher пишет:
I did try netconsole as a module, and tried loading in with a command in /etc/modprobe.d. I did not appear to work.
You forgot to show what you did so I take it it as rant instead of question.
What I did is:
In /etc/modprobe.d/20-netconsole.conf, there is the line:
options netconsole netconsole=64001@192.168.7.60/eth0,64001@192.168.7.55/34:e6:d7:01:2a:dd
as described in the link you referenced.
This is not "command" and it does not load anything. It just provides options for module when (if) module is loaded. Did you load netconsole module at all?
That is the same line I used with the native module netconsole. I also tried in user mode the route where you: CONFIGFS_FS NETCONSOLE NETCONSOLE_DYNAMIC
and load parameters into /sys/kernel/config/netconsole/hostname/*. This works fine, but is not available early enough in the boot sequence to report the crash.
It is not clear again. You mean, crash happens before ethernet driver is loaded and you can configure netconsole to use it?
The crash occurs rather early in the boot process. I did include a file /etc/modules-load.d/netconsole.conf that contains the line netconsole. I thought that would load the module. Then the file /etc/modprobe.d/20-netconsole.conf should add the parameters. Did not appear to work according to journalctl dump. I have now built both the netconsole interface and the alx driver native to the kernel. This works fine outputting a dmesg dump for about 12 seconds, then the output stops. That is about the same time it took for my Ethernet devices to come up. So there could be a conflict between the networks setup by netconsole and maybe being clobbered by wicked. The documentation claims that system messages may go over the net with the kernel messages. Don -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
28.09.2018 23:46, don fisher пишет:
I have now built both the netconsole interface and the alx driver native to the kernel. This works fine outputting a dmesg dump for about 12 seconds, then the output stops. That is about the same time it took for my Ethernet devices to come up. So there could be a conflict between the networks setup by netconsole and maybe being clobbered by wicked.
That's logical fallacy. Two events happening one after another does not imply two events are related. netconsole is exactly that - net*console*. It does not record all kernel output, only messages that would be printed on (local) console. This is controlled by console log level parameter. For kernel message to appear in netconsole output its priority must be higher than console log level. Default kernel console log level is DEBUG; when booting with "quiet" parameter it is WARNING meaning only errors appear on console. The value of console log level can be changed at any time. So most likely something in your case does it. Check the value after boot. In my case (pretty vanilla Leap 15 install) it is rsyslog which resets console log level to ALERT meaning only emergency messages are printed. I admit it was not straightforward to find out, I had to use kernel auditing to do it.
The documentation claims that system messages may go over the net with the kernel messages.
I do not know what documentation you mean nor what "system messages" means. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 9/30/18 1:31 AM, Andrei Borzenkov wrote:
28.09.2018 23:46, don fisher пишет:
I have now built both the netconsole interface and the alx driver native to the kernel. This works fine outputting a dmesg dump for about 12 seconds, then the output stops. That is about the same time it took for my Ethernet devices to come up. So there could be a conflict between the networks setup by netconsole and maybe being clobbered by wicked.
That's logical fallacy. Two events happening one after another does not imply two events are related.
netconsole is exactly that - net*console*. It does not record all kernel output, only messages that would be printed on (local) console. This is controlled by console log level parameter. For kernel message to appear in netconsole output its priority must be higher than console log level.
Default kernel console log level is DEBUG; when booting with "quiet" parameter it is WARNING meaning only errors appear on console.
The value of console log level can be changed at any time. So most likely something in your case does it. Check the value after boot. In my case (pretty vanilla Leap 15 install) it is rsyslog which resets console log level to ALERT meaning only emergency messages are printed.
I admit it was not straightforward to find out, I had to use kernel auditing to do it.
The documentation claims that system messages may go over the net with the kernel messages.
I do not know what documentation you mean nor what "system messages" means.
The documentation is in: /usr/src/linux-4.18.7/Documentation/networking/netconsole.txt My system is currently running at loglevel=8. By system messages I did mean the standard network traffic from the system. From the netconsole.txt, "the network device (eth1 in the above case) can run any kind of other network traffic, netconsole is not intrusive". I do now know enough about networking to diagnose the problem. I am not even sure if the problem is with the transmitter or receiver. I am sure that it stops at he same place every boot. The only exception is when I went into Yast2 and disabled wicked. Then it went a little further, but still not to completion. Is there a way to look at the receiver and see if it has messages in the queue, or some overflow, or something else? Any other lists to report to? This is almost working, so I hate to give up now. Don -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 30/09/2018 16.59, don fisher wrote:
On 9/30/18 1:31 AM, Andrei Borzenkov wrote:
28.09.2018 23:46, don fisher пишет:
I do not know what documentation you mean nor what "system messages" means.
The documentation is in: /usr/src/linux-4.18.7/Documentation/networking/netconsole.txt
My system is currently running at loglevel=8. By system messages I did mean the standard network traffic from the system. From the netconsole.txt, "the network device (eth1 in the above case) can run any kind of other network traffic, netconsole is not intrusive".
I do now know enough about networking to diagnose the problem. I am not even sure if the problem is with the transmitter or receiver. I am sure that it stops at he same place every boot. The only exception is when I went into Yast2 and disabled wicked. Then it went a little further, but still not to completion. Is there a way to look at the receiver and see if it has messages in the queue, or some overflow, or something else? Any other lists to report to? This is almost working, so I hate to give up now.
Sometime ago I had netconsole working. Then a month later it did not work for me, same configuration on my side. I did not investigate further, I could solve the problem I had somehow (other "how"). -- Cheers / Saludos, Carlos E. R. (from openSUSE 15.0 (Legolas))
On 9/30/18 2:20 PM, Carlos E. R. wrote:
On 30/09/2018 16.59, don fisher wrote:
On 9/30/18 1:31 AM, Andrei Borzenkov wrote:
28.09.2018 23:46, don fisher пишет:
I do not know what documentation you mean nor what "system messages" means.
The documentation is in: /usr/src/linux-4.18.7/Documentation/networking/netconsole.txt
My system is currently running at loglevel=8. By system messages I did mean the standard network traffic from the system. From the netconsole.txt, "the network device (eth1 in the above case) can run any kind of other network traffic, netconsole is not intrusive".
I do now know enough about networking to diagnose the problem. I am not even sure if the problem is with the transmitter or receiver. I am sure that it stops at he same place every boot. The only exception is when I went into Yast2 and disabled wicked. Then it went a little further, but still not to completion. Is there a way to look at the receiver and see if it has messages in the queue, or some overflow, or something else? Any other lists to report to? This is almost working, so I hate to give up now.
Sometime ago I had netconsole working. Then a month later it did not work for me, same configuration on my side. I did not investigate further, I could solve the problem I had somehow (other "how"). Is there any limit on the number, or total length, of messages that can be received by nc? I am concerned about the repeatable cutoff in the messages. Don
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 30/09/2018 19.04, don fisher wrote:
On 9/30/18 2:20 PM, Carlos E. R. wrote:
Sometime ago I had netconsole working. Then a month later it did not work for me, same configuration on my side. I did not investigate further, I could solve the problem I had somehow (other "how"). Is there any limit on the number, or total length, of messages that can be received by nc? I am concerned about the repeatable cutoff in the messages.
Not that I know. It should be capable of capturing months of logs. Gigabytes and gigabytes - nc doesn't store them, that's up to the pipe. -- Cheers / Saludos, Carlos E. R. (from openSUSE 15.0 (Legolas))
On 9/30/18 6:23 PM, Carlos E. R. wrote:
On 30/09/2018 19.04, don fisher wrote:
On 9/30/18 2:20 PM, Carlos E. R. wrote:
Sometime ago I had netconsole working. Then a month later it did not work for me, same configuration on my side. I did not investigate further, I could solve the problem I had somehow (other "how"). Is there any limit on the number, or total length, of messages that can be received by nc? I am concerned about the repeatable cutoff in the messages.
Not that I know.
It should be capable of capturing months of logs. Gigabytes and gigabytes - nc doesn't store them, that's up to the pipe.
Thanks. I could not find anything. I was looking for some reason for the termination. From a long time ago, I seem to recall a method to monitor the transmissions. Do you have a suggestion? Don -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 30/09/2018 21.35, don fisher wrote:
On 9/30/18 6:23 PM, Carlos E. R. wrote:
On 30/09/2018 19.04, don fisher wrote:
On 9/30/18 2:20 PM, Carlos E. R. wrote:
Sometime ago I had netconsole working. Then a month later it did not work for me, same configuration on my side. I did not investigate further, I could solve the problem I had somehow (other "how"). Is there any limit on the number, or total length, of messages that can be received by nc? I am concerned about the repeatable cutoff in the messages.
Not that I know.
It should be capable of capturing months of logs. Gigabytes and gigabytes - nc doesn't store them, that's up to the pipe.
Thanks. I could not find anything. I was looking for some reason for the termination. From a long time ago, I seem to recall a method to monitor the transmissions. Do you have a suggestion?
Well, yes, you can use Ethereal aka WireShark in the listening computer. Maybe on a third computer, with some routers aka switches. My bets are on the sending computer not sending. I can not check now, I can only play with one small laptop, not at home. But I found the notes I wrote at the time, I attach them. HTH. -- Cheers / Saludos, Carlos E. R. (from openSUSE 15.0 (Legolas))
On 10/01/2018 07:31 AM, Carlos E. R. wrote:
Well, yes, you can use Ethereal aka WireShark in the listening computer. Maybe on a third computer, with some routers aka switches.
I often use Wireshark and to facilitate using it, I bought a cheap 5 port Gb managed switch. I configured it so that port 1 mirrors port 2. I then connect a computer running Wireshark to port 1 and pass the circuit through port 2 and any other free port. Works well. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
James Knott wrote:
On 10/01/2018 07:31 AM, Carlos E. R. wrote:
Well, yes, you can use Ethereal aka WireShark in the listening computer. Maybe on a third computer, with some routers aka switches.
I often use Wireshark and to facilitate using it, I bought a cheap 5 port Gb managed switch. I configured it so that port 1 mirrors port 2. I then connect a computer running Wireshark to port 1 and pass the circuit through port 2 and any other free port.
I guess this is most useful when you can't run tcpdump on either system? I've never had the need, but it's good idea. -- Per Jessen, Zürich (7.6°C) http://www.cloudsuisse.com/ - your owncloud, hosted in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/10/2018 18.19, James Knott wrote:
On 10/01/2018 07:31 AM, Carlos E. R. wrote:
Well, yes, you can use Ethereal aka WireShark in the listening computer. Maybe on a third computer, with some routers aka switches.
I often use Wireshark and to facilitate using it, I bought a cheap 5 port Gb managed switch. I configured it so that port 1 mirrors port 2. I then connect a computer running Wireshark to port 1 and pass the circuit through port 2 and any other free port.
Works well.
Indeed. Once I wanted to investigate some thing I had to temporarily repurpose the computer room switch, and it was a pain. I want an extra switch :-) -- Cheers / Saludos, Carlos E. R. (from openSUSE 15.0 (Legolas))
On 10/02/2018 11:55 AM, Carlos E. R. wrote:
I often use Wireshark and to facilitate using it, I bought a cheap 5 port Gb managed switch. I configured it so that port 1 mirrors port 2. I then connect a computer running Wireshark to port 1 and pass the circuit through port 2 and any other free port.
Works well. Indeed. Once I wanted to investigate some thing I had to temporarily repurpose the computer room switch, and it was a pain. I want an extra switch :-)
Well, they're cheap. I paid $35 CDN for mine, a couple of years ago. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/10/2018 23.09, James Knott wrote:
On 10/02/2018 11:55 AM, Carlos E. R. wrote:
I often use Wireshark and to facilitate using it, I bought a cheap 5 port Gb managed switch. I configured it so that port 1 mirrors port 2. I then connect a computer running Wireshark to port 1 and pass the circuit through port 2 and any other free port.
Works well. Indeed. Once I wanted to investigate some thing I had to temporarily repurpose the computer room switch, and it was a pain. I want an extra switch :-)
Well, they're cheap. I paid $35 CDN for mine, a couple of years ago.
I paid 33.00 for mine (TP-LINK TL-SG108E Switch 8 Puertos Gigabit), Feb 2015. Cheap... depends :-) -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
On 10/06/2018 07:31 AM, Carlos E. R. wrote:
Well, they're cheap. I paid $35 CDN for mine, a couple of years ago. I paid 33.00 for mine (TP-LINK TL-SG108E Switch 8 Puertos Gigabit), Feb
I have the 5 port version of that switch. I bought it in Aug. 2016. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 10/06/2018 01:36 PM, James Knott wrote: > On 10/06/2018 07:31 AM, Carlos E. R. wrote: >>> Well, they're cheap. I paid $35 CDN for mine, a couple of years ago. >> I paid 33.00 for mine (TP-LINK TL-SG108E Switch 8 Puertos Gigabit), Feb >> 2015. > I have the 5 port version of that switch. I bought it in Aug. 2016. > Forgot to mention, those cheap TP-Link switches don't handle VLANs properly, so don't buy one for use with them. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 06/10/2018 19.37, James Knott wrote: > On 10/06/2018 01:36 PM, James Knott wrote: >> On 10/06/2018 07:31 AM, Carlos E. R. wrote: >>>> Well, they're cheap. I paid $35 CDN for mine, a couple of years ago. >>> I paid 33.00 for mine (TP-LINK TL-SG108E Switch 8 Puertos Gigabit), Feb >>> 2015. >> I have the 5 port version of that switch. I bought it in Aug. 2016. 5? Odd number. In two senses ;-) > > Forgot to mention, those cheap TP-Link switches don't handle VLANs > properly, so don't buy one for use with them. I don't use VLANs, but it is good to know :-) Configuration is only with Windows, by the way. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
On 10/06/2018 03:19 PM, Carlos E. R. wrote:
Configuration is only with Windows, by the way.
I have it running in Wine on Linux. However, once it's set up, you don't have to change it often. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 06/10/2018 22.41, James Knott wrote:
On 10/06/2018 03:19 PM, Carlos E. R. wrote:
Configuration is only with Windows, by the way.
I have it running in Wine on Linux. However, once it's set up, you don't have to change it often.
Well, I had to, to change one port to mirror traffic of another port. And later to undo, after getting the output I wanted. How did you get it to work in Wine, just run setup or something? -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
On 10/06/2018 04:55 PM, James Knott wrote:
On 10/06/2018 04:51 PM, Carlos E. R. wrote:
How did you get it to work in Wine, just run setup or something? Yes.
Forgot to mention, it works on my desktop, but not ThinkPad. The app runs on the ThinkPad but doesn't see the switch. I don't know why the difference. Perhaps it's because the desktop has a manual network configuration in Yast, but the ThinkPad uses network manager. Both computers are running 15.0 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 El 2018-10-06 a las 16:58 -0400, James Knott escribió:
On 10/06/2018 04:55 PM, James Knott wrote:
On 10/06/2018 04:51 PM, Carlos E. R. wrote:
How did you get it to work in Wine, just run setup or something? Yes.
Forgot to mention, it works on my desktop, but not ThinkPad. The app runs on the ThinkPad but doesn't see the switch. I don't know why the difference. Perhaps it's because the desktop has a manual network configuration in Yast, but the ThinkPad uses network manager. Both computers are running 15.0
Maybe the thinkpad is on WiFi? - -- Cheers Carlos E. R. (from openSUSE 15.0 (Legolas)) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCW7ky8xwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVtPoAn2lac+GnXDuhnl1Mx/Wg 07MMsN04AJ9My8Gdb26JD+kJfH/dWc7Zg/Lbrw== =XChx -----END PGP SIGNATURE-----
On 07/10/2018 00.49, James Knott wrote:
On 10/06/2018 06:10 PM, Carlos E. R. wrote:
Maybe the thinkpad is on WiFi?
I only use Ethernet to connect to the switch.
Then I can not imagine why it does not see the switch, except some obscure Windows reason. Well... how does it find the switch, by the way? I do not need to tell it the IP, it finds it reasonably fast. Some broadcast? -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
On 10/07/2018 08:31 AM, Carlos E.R. wrote:
I only use Ethernet to connect to the switch. Then I can not imagine why it does not see the switch, except some obscure Windows reason.
Well... how does it find the switch, by the way? I do not need to tell it the IP, it finds it reasonably fast. Some broadcast?
-
I haven't investigated that. I expect the app broadcasts and sees what responds. I haven't seen anything coming from the switch to announce itself to the app. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 9/25/2018 4:21 PM, don fisher wrote:
I am trying to use netconsole to examine some problems I am having booting certain laptops. I am running opensuse 42.3 with generic 4.18.7 kernel configured to include netconsole. After building my kernel and including the proper command (as shown below) in the linux boot string: netconsole=64001@192.168.7.60/eth0,64001@192.168.7.55/34:e6:d7:01:2a:dd I receive the following error message as shown by journalctl:
sudo journalctl -b | grep netconsole Sep 24 22:01:25 dfpc60 kernel: netpoll: netconsole: local port 64001 Sep 24 22:01:25 dfpc60 kernel: netpoll: netconsole: local IPv4 address 192.168.7.60 Sep 24 22:01:25 dfpc60 kernel: netpoll: netconsole: interface 'eth0' Sep 24 22:01:25 dfpc60 kernel: netpoll: netconsole: remote port 64001 Sep 24 22:01:25 dfpc60 kernel: netpoll: netconsole: remote IPv4 address 192.168.7.55 Sep 24 22:01:25 dfpc60 kernel: netpoll: netconsole: remote ethernet address 34:e6:d7:01:2a:dd Sep 24 22:01:25 dfpc60 kernel: netpoll: netconsole: eth0 doesn't exist, aborting Sep 24 22:01:25 dfpc60 kernel: netconsole: cleaning up Sep 24 22:01:25 dfpc60 systemd-modules-load[185]: Module 'netconsole' is builtin
From Google(netpoll is intended for monitoring multiple file descriptors to see if I/O is possible on any of them. It supports edge-triggered and level-triggered interfaces.)
I looked at dmesg and netconsole is trying eth0: at 2.348515 sec after boot. The first other mention I see of eth0: is at 9.739663 sec. The message is:
[ 9.739663] alx 0000:3c:00.0 eth0: Qualcomm Atheros AR816x/AR817x Ethernet [a4:4c:c8:5e:e0:12] which I assume is just recognition if loading the driver.
From sudo journalctl -b | grep eth0: Sep 24 22:02:01 dfpc60 wicked[942]: eth0 up
Wicked seems to appear about half a second after netconsole looks for eth0:
Is there something I can do in systemd, the eth0: configuration, or elsewhere to get wicked to load eth0 earlier? I was a little surprised that netconsole did not go back and try again a little later.
Doesn't sysd have a way to specify the order in which things come up? If this was sysv, you'd make one depend on the other in the headers which would alter it's run order. I find it odd that netconsole would load so soon, since I notice my builtin ethernet driver loads at about 4s, while my module-based ethernet drivers load at around 10-11s. Kernel finishes booting around 5.6-5.7s. The network interfaces are renamed about 11 seconds later and configured about 4-5 seconds after that. It is *MUCH* more likely you will be able to get a console on a serial device. If it is a laptop, doesn't it allow plugin cards? Then would build that devices driver into the kernel. Also of note -- there is an option under kernel hacking to enable "Remote debugging over FireWire early on boot" It sounds like it is before the kernel comes up. Dunno if that would be a usable device for logging.
Thanks Don
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 28/09/2018 13.10, L A Walsh wrote:
On 9/25/2018 4:21 PM, don fisher wrote:
Wicked seems to appear about half a second after netconsole looks for eth0:
Is there something I can do in systemd, the eth0: configuration, or elsewhere to get wicked to load eth0 earlier? I was a little surprised that netconsole did not go back and try again a little later.
Doesn't sysd have a way to specify the order in which things come up?
This should run before sysd is loaded, before services are loaded. -- Cheers / Saludos, Carlos E. R. (from openSUSE 15.0 (Legolas))
participants (12)
-
Andrei Borzenkov -
Anton Aylward -
Carlos E. R. -
Carlos E. R. -
Carlos E.R.
-
David C. Rankin -
don fisher -
James Knott -
jdd＠dodin.org -
Knurpht-openSUSE -
L A Walsh -
Per Jessen