From: Michael Ellerman <mpe@ellerman•id.au>
To: Paul Menzel <pmenzel@molgen•mpg.de>,
Benjamin Herrenschmidt <benh@kernel•crashing.org>,
Paul Mackerras <paulus@samba•org>
Cc: linuxppc-dev@lists•ozlabs.org
Subject: Re: VIO bus not initialized
Date: Tue, 16 Mar 2021 12:10:50 +1100 [thread overview]
Message-ID: <87k0q752ed.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <90e6a559-0908-684c-9156-5f3da2b02e38@molgen.mpg.de>
Paul Menzel <pmenzel@molgen•mpg.de> writes:
> 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”?
Yeah, in fact we are already skipping the registration of the bus,
that's why we're seeing these messages. We need to also skip the
registration of the drivers to avoid those warnings.
See the patch I just sent.
cheers
prev parent reply other threads:[~2021-03-16 1: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
2021-03-16 1:10 ` Michael Ellerman [this message]
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=87k0q752ed.fsf@mpe.ellerman.id.au \
--to=mpe@ellerman$(echo .)id.au \
--cc=benh@kernel$(echo .)crashing.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=paulus@samba$(echo .)org \
--cc=pmenzel@molgen$(echo .)mpg.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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