LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Menzel <pmenzel@molgen.mpg.de>
To: Michael Ellerman <mpe@ellerman.id.au>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Paul Mackerras <paulus@samba.org>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: VIO bus not initialized
Date: Mon, 15 Mar 2021 09:11:13 +0100	[thread overview]
Message-ID: <90e6a559-0908-684c-9156-5f3da2b02e38@molgen.mpg.de> (raw)
In-Reply-To: <87mtv44zut.fsf@mpe.ellerman.id.au>

Dear Michael,


Thank you very much for your response.


Am 15.03.21 um 08:53 schrieb Michael Ellerman:
> Paul Menzel writes:

>> On the POWER8 system IBM S822LC, Linux 5.12-rc2+ logs the errors below.
> 
> That's a bare metal system, you can see that from the line "Using
> PowerNV machine description" in the boot log.
> 
>>       $ dmesg --level=err
>>       [    1.555668] Driver 'hvc_console' was unable to register with bus_type 'vio' because the bus was not initialized.
>>       [    1.558434] Driver 'tpm_ibmvtpm' was unable to register with bus_type 'vio' because the bus was not initialized.
>>       $ grep VIO /boot/config-5.12.0-rc2+
>>       CONFIG_IBMVIO=y
> 
> The "vio" bus is not a real bus, it's a fake bus we use for hypervisor
> provided devices in LPARs (guests).
> 
> So on bare metal machines there is no vio bus, the devices that would
> appear on the vio bus are found via other mechanisms.

Thank you for the explanation. Two questions:

1.  Could a bare metal system be detected, and the VIO “be skipped”?
2.  Should the log level be changed to notice or info then, as it’s an 
expected failure?

[…]


Kind regards,

Paul

  reply	other threads:[~2021-03-15  8:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-10 12:05 VIO bus not initialized Paul Menzel
2021-03-15  7:53 ` Michael Ellerman
2021-03-15  8:11   ` Paul Menzel [this message]
2021-03-16  1:10     ` Michael Ellerman

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=90e6a559-0908-684c-9156-5f3da2b02e38@molgen.mpg.de \
    --to=pmenzel@molgen.mpg.de \
    --cc=benh@kernel.crashing.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mpe@ellerman.id.au \
    --cc=paulus@samba.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