WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: Kernel panic when using SSHD  (Read 1482 times)

Offline clauder

  • Newbie
  • *
  • Posts: 11
Kernel panic when using SSHD
« on: February 21, 2020, 11:13:26 AM »
I am trying to test a very basic system where I can ssh into tc. The minute I try to connect from another (Ubuntu 18.04) machine I get a kernel panic. I did try multiple times....

The setup is are follow
- Core (version 10.1) - so no GUI
- Boot in Virtualbox (6.1.4), using the ISO (1G RAM, 1 CPU core)
- Install from the net openssl and then openssh (so networking is good)

At this point I can ssh out to my bare-metal machine

- Copy /usr/local/etc/ssh/sshd_config.orig to /usr/local/etc/ssh/sshd_config
- Start the SSH daemon (sudo /usr/locao/etc/init.d/openssh start)

ssh from my bare-metal - Kernel panic in tc

The bare-metal is Ubuntu 18.04 on a Ryzen CPU

Is this a known issue? Should I simply move to a newer TC?

PS I can not cut and paste the kernel output, I could only take a screen shot of the window. Will post it later if needed; but there is not much interesting thing on it

Offline curaga

  • Administrator
  • Hero Member
  • *****
  • Posts: 10992
Re: Kernel panic when using SSHD
« Reply #1 on: February 21, 2020, 01:12:16 PM »
No, not a known issue. Could be virtualbox-related though, maybe you can try on bare metal or qemu?
The only barriers that can stop you are the ones you create yourself.

Offline clauder

  • Newbie
  • *
  • Posts: 11
Re: Kernel panic when using SSHD
« Reply #2 on: February 22, 2020, 11:01:56 AM »
I am using a Usb-C stick has my root FS so I moved to another physical machine and there is no crash. So virtualbox is not the culprit, unless there is an interaction with the physical machine (which has a ryzen).

I also have another ryzen machine (thread-ripper and different MB). No problem there.

So, in conclusion, I should try the first machine bare-metal.....