From: Michael Ellerman <mpe@ellerman.id.au> Date: 2021-03-16 01:10:22
The vio bus is a fake bus, which we use on pseries LPARs (guests) to
discover devices provided by the hypervisor. There's no need or sense
in creating the vio bus on bare metal systems.
Which is why commit 4336b9337824 ("powerpc/pseries: Make vio and
ibmebus initcalls pseries specific") made the initialisation of the
vio bus only happen in LPARs.
However as a result of that commit we now see errors at boot on bare
metal systems:
Driver 'hvc_console' was unable to register with bus_type 'vio' because the bus was not initialized.
Driver 'tpm_ibmvtpm' was unable to register with bus_type 'vio' because the bus was not initialized.
This happens because those drivers are built-in, and are calling
vio_register_driver(). It in turn calls driver_register() with a
reference to vio_bus_type, but we haven't registered vio_bus_type with
the driver core.
Fix it by also guarding vio_register_driver() with a check to see if
we are on pseries.
Fixes: 4336b9337824 ("powerpc/pseries: Make vio and ibmebus initcalls pseries specific")
Reported-by: Paul Menzel <redacted>
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
---
arch/powerpc/platforms/pseries/vio.c | 4 ++++
1 file changed, 4 insertions(+)
@@ -1285,6 +1285,10 @@ static int vio_bus_remove(struct device *dev)int__vio_register_driver(structvio_driver*viodrv,structmodule*owner,constchar*mod_name){+// vio_bus_type is only initialised for pseries+if(!machine_is(pseries))+return-ENODEV;+pr_debug("%s: driver %s registering\n",__func__,viodrv->name);/* fill in 'struct driver' fields */
From: Paul Menzel <hidden> Date: 2021-03-30 10:32:35
Dear Michael,
Am 16.03.21 um 02:09 schrieb Michael Ellerman:
quoted hunk
The vio bus is a fake bus, which we use on pseries LPARs (guests) to
discover devices provided by the hypervisor. There's no need or sense
in creating the vio bus on bare metal systems.
Which is why commit 4336b9337824 ("powerpc/pseries: Make vio and
ibmebus initcalls pseries specific") made the initialisation of the
vio bus only happen in LPARs.
However as a result of that commit we now see errors at boot on bare
metal systems:
Driver 'hvc_console' was unable to register with bus_type 'vio' because the bus was not initialized.
Driver 'tpm_ibmvtpm' was unable to register with bus_type 'vio' because the bus was not initialized.
This happens because those drivers are built-in, and are calling
vio_register_driver(). It in turn calls driver_register() with a
reference to vio_bus_type, but we haven't registered vio_bus_type with
the driver core.
Fix it by also guarding vio_register_driver() with a check to see if
we are on pseries.
Fixes: 4336b9337824 ("powerpc/pseries: Make vio and ibmebus initcalls pseries specific")
Reported-by: Paul Menzel <redacted>
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
---
arch/powerpc/platforms/pseries/vio.c | 4 ++++
1 file changed, 4 insertions(+)
@@ -1285,6 +1285,10 @@ static int vio_bus_remove(struct device *dev)int__vio_register_driver(structvio_driver*viodrv,structmodule*owner,constchar*mod_name){+// vio_bus_type is only initialised for pseries+if(!machine_is(pseries))+return-ENODEV;+pr_debug("%s: driver %s registering\n",__func__,viodrv->name);/* fill in 'struct driver' fields */
Thank you. The errors are gone now.
Tested-by: Paul Menzel <redacted> # IBM S822L (POWER8)
As it fixes a commit from Linux 5.8, should it be tagged for the stable
releases, or is it going to be picked up automatically due to the Fixes tag?
Kind regards,
Paul
The vio bus is a fake bus, which we use on pseries LPARs (guests) to
discover devices provided by the hypervisor. There's no need or sense
in creating the vio bus on bare metal systems.
Which is why commit 4336b9337824 ("powerpc/pseries: Make vio and
ibmebus initcalls pseries specific") made the initialisation of the
vio bus only happen in LPARs.
However as a result of that commit we now see errors at boot on bare
metal systems:
Driver 'hvc_console' was unable to register with bus_type 'vio' because the bus was not initialized.
Driver 'tpm_ibmvtpm' was unable to register with bus_type 'vio' because the bus was not initialized.
This happens because those drivers are built-in, and are calling
vio_register_driver(). It in turn calls driver_register() with a
reference to vio_bus_type, but we haven't registered vio_bus_type with
the driver core.
Fix it by also guarding vio_register_driver() with a check to see if
we are on pseries.
Fixes: 4336b9337824 ("powerpc/pseries: Make vio and ibmebus initcalls pseries specific")
Reported-by: Paul Menzel <redacted>
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
---
From: Michael Ellerman <mpe@ellerman.id.au> Date: 2021-03-31 04:38:42
Paul Menzel [off-list ref] writes:
Am 16.03.21 um 02:09 schrieb Michael Ellerman:
quoted
The vio bus is a fake bus, which we use on pseries LPARs (guests) to
discover devices provided by the hypervisor. There's no need or sense
in creating the vio bus on bare metal systems.
Which is why commit 4336b9337824 ("powerpc/pseries: Make vio and
ibmebus initcalls pseries specific") made the initialisation of the
vio bus only happen in LPARs.
However as a result of that commit we now see errors at boot on bare
metal systems:
Driver 'hvc_console' was unable to register with bus_type 'vio' because the bus was not initialized.
Driver 'tpm_ibmvtpm' was unable to register with bus_type 'vio' because the bus was not initialized.
This happens because those drivers are built-in, and are calling
vio_register_driver(). It in turn calls driver_register() with a
reference to vio_bus_type, but we haven't registered vio_bus_type with
the driver core.
Fix it by also guarding vio_register_driver() with a check to see if
we are on pseries.
Fixes: 4336b9337824 ("powerpc/pseries: Make vio and ibmebus initcalls pseries specific")
Reported-by: Paul Menzel <redacted>
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
---
arch/powerpc/platforms/pseries/vio.c | 4 ++++
1 file changed, 4 insertions(+)
@@ -1285,6 +1285,10 @@ static int vio_bus_remove(struct device *dev)int__vio_register_driver(structvio_driver*viodrv,structmodule*owner,constchar*mod_name){+// vio_bus_type is only initialised for pseries+if(!machine_is(pseries))+return-ENODEV;+pr_debug("%s: driver %s registering\n",__func__,viodrv->name);/* fill in 'struct driver' fields */
Thank you. The errors are gone now.
Tested-by: Paul Menzel <redacted> # IBM S822L (POWER8)
As it fixes a commit from Linux 5.8, should it be tagged for the stable
releases, or is it going to be picked up automatically due to the Fixes tag?
It's not what I'd describe as a bad bug, so I'm not that inclined to
tag it for stable.
But given it has a Fixes tag, and is quite small, the bots will probably
backport it automatically.
cheers
From: Michael Ellerman <hidden> Date: 2021-04-10 14:33:51
On Tue, 16 Mar 2021 12:09:38 +1100, Michael Ellerman wrote:
The vio bus is a fake bus, which we use on pseries LPARs (guests) to
discover devices provided by the hypervisor. There's no need or sense
in creating the vio bus on bare metal systems.
Which is why commit 4336b9337824 ("powerpc/pseries: Make vio and
ibmebus initcalls pseries specific") made the initialisation of the
vio bus only happen in LPARs.
[...]