Le jeudi 9 mai 2019 21:37:16 UTC+2, Hakkı Kurumahmut a écrit :
> 9 Mayıs 2019 Perşembe 12:14:15 UTC+3 tarihinde [email protected] yazdı:
> > > Hello everyone, 
> > > 
> > > Thanks for the help now I pass the hradware check ! Unfortunately the 
> > > enabling of the rootCell is not working yet. With Halli's configuration 
> > > everything is juste freezing without giving any error. When I use my 
> > > generated file (that is similar to Hakki's one) I got this error :
> > > 
> > > 
> > > [] Irq 16 : nobody cared (try booting with the "irqpoll" option) 
> > > [] Handlers :
> > > [] [<ffffffff81622fa0>] usb_hcd_irq
> > > [] [<ffffffffc025c360>] ilo_isr [hpilo]
> > > [] Disabling IRQ # 16
> > > [] NMI watchdog: BUG: soft lockup - CPU#7 stuck for 22s! [kworkers/...]
> > > [] NMI watchdog: BUG: soft lockup - CPU#6 stuck for 22s! [kworkers/...]
> > > [] NMI watchdog: BUG: soft lockup - CPU#8 stuck for 22s! [kworkers/...]
> > > [] NMI watchdog: BUG: soft lockup - CPU#9 stuck for 22s! [kworkers/...]
> > > [] NMI watchdog: BUG: soft lockup - CPU#11 stuck for 22s! [kworkers/...]
> > > [] NMI watchdog: BUG: soft lockup - CPU#12 stuck for 22s! [kworkers/...]
> > > [] NMI watchdog: BUG: soft lockup - CPU#13 stuck for 22s! [kworkers/...]
> > > [] NMI watchdog: BUG: soft lockup - CPU#14 stuck for 22s! [kworkers/...]
> > > [] NMI watchdog: BUG: soft lockup - CPU#15 stuck for 22s! [kworkers/...]
> > > [] NMI watchdog: BUG: soft lockup - CPU#17 stuck for 22s! [kworkers/...]
> > > 
> > > etc...
> > > 
> > > I don't know why there is this error. Do you have an idea ? 
> > > 
> > > 
> > > 
> > > @Hakki you can find in attachment the lspci command lines you requested
> > > 
> > > again : thanks for your help
> > 
> > Hello again, 
> > 
> > Actually my error is a kernel panic that is shutting down all the CPUs with 
> > NMI
> > 
> > best regards,
> 
> 
> 
> Hi Jeanne,
> 
> Your new problem is similar to the subject that below link.
> 
> https://groups.google.com/forum/#!topic/jailhouse-dev/xgpOci2wCDs
> 
> 
> In such cases, Jailhouse hypervisor console information is more important to 
> see root cause of the problem. If you do not get the console information, you 
> cannot get much help.
> 
> Open Hypervisor console on new terminal may be ssh connection more suitable 
> against Linux hang situations.
>  
> --sudo jailhouse console -f
> 
> If you have uart port, it is pretty. In FAQ.md file,
> 
> on real hardware, you'll need a serial cable. Connect it to the COM port on 
> your motherboard. Many modern motherboards come with no COM ports, but they 
> usually have a header you can attach the socket to. Servers often have serial 
> console available through IPMI.
> 
> In hypervisor-configuration.md file, 
> 
> #define CONFIG_CRASH_CELL_ON_PANIC 1
> 
> it is suitable for hang status. please add it to "cell-config.h". And rebuild 
> and reinstall jailhouse.
> 
> 
> For a quick test I would recommend the following.
>  
> Sometimes, it helps to set pio_bitmap to all zeros in sysconfig.c to solve if 
> there are any issues, but It is not recommended in production.  
> 
> Original fix pio_bitmap table :
>  
>       .pio_bitmap = {
>               [     0/8 ...   0x3f/8] = -1,
>               [  0x40/8 ...   0x47/8] = 0xf0, /* PIT */
>               [  0x48/8 ...   0x5f/8] = -1,
>               [  0x60/8 ...   0x67/8] = 0xec, /* HACK: NMI status/control */
>               [  0x68/8 ...   0x6f/8] = -1,
>               [  0x70/8 ...   0x77/8] = 0xfc, /* RTC */
>               [  0x78/8 ...  0x3af/8] = -1,
>               [ 0x3b0/8 ...  0x3df/8] = 0x00, /* VGA */
>               [ 0x3e0/8 ...  0xcff/8] = -1,
>               [ 0xd00/8 ... 0xffff/8] = 0, /* HACK: PCI bus */
>       },
> 
> Set all value to zero (cell accessible)
> 
> 
>       .pio_bitmap = {
>               [     0/8 ...   0x3f/8] = 0,
>               [  0x40/8 ...   0x47/8] = 0, /* PIT */
>               [  0x48/8 ...   0x5f/8] = 0,
>               [  0x60/8 ...   0x67/8] = 0, /* HACK: NMI status/control */
>               [  0x68/8 ...   0x6f/8] = 0,
>               [  0x70/8 ...   0x77/8] = 0, /* RTC */
>               [  0x78/8 ...  0x3af/8] = 0,
>               [ 0x3b0/8 ...  0x3df/8] = 0, /* VGA */
>               [ 0x3e0/8 ...  0xcff/8] = 0,
>               [ 0xd00/8 ... 0xffff/8] = 0, /* HACK: PCI bus */
>       },
> 
> Search in forum "pio_bitmap", you can see more advices...
> 
> Good luck.
> 
> HAKKI

Hello everyone, 

Thanks a lot for your help !

I am currently connected to my card via a VGA port. I thought that changing the 
console type to EFIFB would bring me slog jailhouse on my screen but obviously 
I was wrong... Is there a way to display them on a VGA port or is it totally 
over?

I changed the card because I didn't have two serial ports. However, my goal is 
to run several linuxes in parallel on my card and, if I don't have access to 
their console, their use is limited... That's why I switched to a card with a 
VGA port (which I thought I could dedicate to rott-cell) and a serial port 
(which I thought I could dedicate to inmate). What would you recommend for such 
a configuration?

Best regards,

Jeanne

-- 
You received this message because you are subscribed to the Google Groups 
"Jailhouse" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jailhouse-dev/63282997-5d5a-4c59-9d60-1d73fcfe49db%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to