Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #51649 > unrolled thread

Bug#792910: "modprobe: module css:t0 not found in modules.dep" issued during boot

Back to article view | Back to linux.debian.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Bug#792910: "modprobe: module css:t0 not found in modules.dep" issued during boot Ben Hutchings <ben@decadent.org.uk> - 2015-12-10 00:20 +0100
    Processed: Re: "modprobe: module css:t0 not found in modules.dep"  issued during boot owner@bugs.debian.org (Debian Bug Tracking System) - 2015-12-10 00:20 +0100

#51649 — Bug#792910: "modprobe: module css:t0 not found in modules.dep" issued during boot

[Multipart message — attachments visible in raw view] — view raw

Control: retitle -1 Module aliases should be resolved at build time

On Sun, 19 Jul 2015 22:01:06 -0400 (EDT) Stephen Powell <zlinuxman@wowway.com> wrote:
> Package: initramfs-tools
> Version: 0.120
> Severity: minor
> 
> During boot of a jessie system on the s390x platform, I noticed the
> following error message on the console:
> 
> Begin: Loading essential drivers ...
> modprobe: module css:t0 not found in modules.dep
> 
> The error didn't seem to affect the ability of the system to boot,
> but I decided to investigate.  I traced the problem to the
> sys_walk_modalias function in /usr/share/initramfs-tools/hook-functions.
> The relevant code goes something like this:
> 
>    if [ -n "${modalias}" ]; then
>            force_load "${modalias}"
>    fi
> 
> The problem here is that the code does not distinguish between a regular
> module alias and what I call a udev alias.  (I'm not sure what the proper
> terminology is.  If you know please tell me.)

They're both module aliases.  The ones with colons in are generated at
kernel build time from the device ID tables in each module and at run-
time from the discovered device information.  Although udev handles the
uevents, it's always kmod that matches aliases against the installed
modules.

The specific problem here is that the driver that matches the module
alias 'css:t0' is ccw_device, which is built-in.

[...]
> Most of the udev aliases have asterisks in them.  All of them seem to have
> a colon in them.  I suggest the following code to replace the above:
> 
>    case "${modalias}" in
>            ""|*:*)
>                    :
>                    ;;
>            *)
>                    force_load "${modalias}"
>                    ;;
>    esac
> 
> The attached patch file fixes the problem on my system.

I think this is the wrong approach.  I don't think its make sense to
include *any* module aliases in /conf/modules; only the actual modules
should be listed there.

Ben.

-- 
Ben Hutchings
I'm always amazed by the number of people who take up solipsism because
they heard someone else explain it. - E*Borg on alt.fan.pratchett

[toc] | [next] | [standalone]

#51650 — Processed: Re: "modprobe: module css:t0 not found in modules.dep" issued during boot

Processing control commands:

> retitle -1 Module aliases should be resolved at build time
Bug #792910 [initramfs-tools] "modprobe: module css:t0 not found in modules.dep" issued during boot
Changed Bug title to 'Module aliases should be resolved at build time' from '"modprobe: module css:t0 not found in modules.dep" issued during boot'

-- 
792910: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792910
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web