From: Andreas Mohr <andi@lisas.de>
To: Andreas Mohr <andi@lisas.de>
Cc: initramfs@vger.kernel.org, Maximilian Attems <maks@debian.org>,
Greg KH <gregkh@linuxfoundation.org>,
Alan Stern <stern@rowland.harvard.edu>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-usb@vger.kernel.org
Subject: Re: [REGRESSION] [nailed] USB boot failure: USB: EHCI: make ehci-pci a separate driver
Date: Wed, 13 Feb 2013 08:44:09 +0100 [thread overview]
Message-ID: <20130213074409.GA16043@rhlx01.hs-esslingen.de> (raw)
In-Reply-To: <20130213071628.GA4211@rhlx01.hs-esslingen.de>
[CC initramfs-tools]
On Wed, Feb 13, 2013 at 08:16:28AM +0100, Andreas Mohr wrote:
> Hi,
>
> On Wed, Feb 13, 2013 at 07:44:36AM +0100, Andreas Mohr wrote:
> > So, what to do? I'm now going to do some experimentation with git revert
> > on some revision, and I'm trying to establish the USB port dependency
> > (BIOS-owned handoff root hub invisible!?, as discussed in initial mail).
>
>
> After some bingo moment, seems the solution is easier than expected:
>
> andi@andinet:~$ ls /tmp/initrd_extracted/lib/modules/3.7.0-rc5+/kernel/drivers/usb/host/
> ehci-hcd.ko ohci-hcd.ko uhci-hcd.ko xhci-hcd.ko
> andi@andinet:~$ ls /lib/modules/3.7.0-rc5+/kernel/drivers/usb/host/
> ehci-hcd.ko isp116x-hcd.ko sl811_cs.ko uhci-hcd.ko
> ehci-pci.ko ohci-hcd.ko sl811-hcd.ko whci
> hwa-hc.ko r8a66597-hcd.ko u132-hcd.ko xhci-hcd.ko
>
> So it's probably only that the initrd simply fails to ship
> the ehci-pci.ko module (I could verify this by extending initrd content, BTW).
> Now the question would be:
> are modules listed in a static list on initramfs package/config side,
> or does the kernel fail to signal the list of required modules properly?
> (e.g. did some config-side files fail to get upgraded for this dependency??)
>
>
> So maybe it's not a "regression" per se, but it's at least a grave
> usability issue on kernel upgrade which should be handled as benignly as
> possible (i.e., without any disruption).
OK, initramfs-tools hook-functions file contains (even in git master):
for arg in "$@" ; do
case "$arg" in
base)
modules="$modules ehci-hcd ohci-hcd uhci-hcd
usbhid"
modules="$modules xhci xhci-hcd"
modules="$modules hid-apple hid-cherry
hid-generic"
modules="$modules hid-logitech hid-logitech-dj"
modules="$modules hid-microsoft hid-sunplus"
modules="$modules btrfs ext2 ext3 ext4 ext4dev "
modules="$modules isofs jfs nfs reiserfs udf
xfs"
modules="$modules af_packet atkbd i8042
virtio_pci"
;;
So it seems it actually *is* the user side (initramfs-tools) which has
to maintain knowledge of all dependencies in a painfully maintained
hard-coded list, and it seems this change is now making it croak,
due to not knowing about the newly split extra ehci-pci.ko.
Questions:
- is this mechanism how one would want things to be?
(is there a way to cleanly provide the accurately updated list
from the kernel side? Or is there a scripted mechanism to at least extract
all required *dependee* modules from the list of the ones that we
already know of? That would have saved our a** here...)
- was this module change properly communicated sufficiently in advance,
to (all/most of) some affected parties?
If not, might want to do better next time if that's possible...
- should ehci-pci be added to the literal list now (and does this work
properly on kernels which don't have it??), to get back to a working
state ASAP?
Thanks,
Andreas Mohr
next prev parent reply other threads:[~2013-02-13 7:44 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-08 21:51 Linux v3.8-rc7 Linus Torvalds
2013-02-10 0:14 ` [REGRESSION] -rc7/-rc4+: unable to USB boot - enumeration partially broken (was: Linux v3.8-rc7) Andreas Mohr
2013-02-10 14:05 ` Andreas Mohr
2013-02-12 16:07 ` Andreas Mohr
2013-02-12 16:16 ` Greg KH
2013-02-12 21:25 ` Andreas Mohr
2013-02-13 6:44 ` [REGRESSION] [nailed] USB boot failure: USB: EHCI: make ehci-pci a separate driver Andreas Mohr
2013-02-13 7:16 ` Andreas Mohr
2013-02-13 7:44 ` Andreas Mohr [this message]
2013-02-13 10:05 ` Andreas Mohr
2013-02-13 10:50 ` Colin Guthrie
2013-02-13 16:13 ` Andreas Mohr
2013-02-13 16:26 ` Colin Guthrie
2013-02-13 11:10 ` [-rc7 regression] Block IO/VFS/ext3/timer spinlock lockup? Ingo Molnar
2013-02-13 16:59 ` Linus Torvalds
2013-02-13 23:20 ` Thomas Gleixner
2013-02-14 14:45 ` Ingo Molnar
2013-02-14 14:54 ` Ingo Molnar
2013-02-14 15:08 ` Ingo Molnar
2013-02-14 17:28 ` Thomas Gleixner
2013-02-14 18:22 ` Yinghai Lu
2013-02-15 11:44 ` [-rc7 regression] Buggy commit: "mm: use aligned zone start for pfn_to_bitidx calculation" Ingo Molnar
2013-02-15 22:06 ` Greg KH
2013-02-16 8:29 ` Ingo Molnar
2013-03-01 16:50 ` Greg KH
2013-03-01 17:07 ` Linus Torvalds
2013-03-01 17:14 ` Greg KH
2013-02-16 8:25 ` Ingo Molnar
2013-02-16 18:26 ` Linus Torvalds
2013-02-16 19:38 ` Yinghai Lu
2013-02-16 19:51 ` Linus Torvalds
2013-02-18 8:49 ` Ingo Molnar
2013-02-18 14:46 ` Mel Gorman
2013-02-18 18:42 ` Laura Abbott
2013-02-14 23:05 ` [-rc7 regression] Block IO/VFS/ext3/timer spinlock lockup? Linus Torvalds
2013-02-15 11:39 ` [PATCH] spinlock/debugging: Print out lock name when available Ingo Molnar
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=20130213074409.GA16043@rhlx01.hs-esslingen.de \
--to=andi@lisas.de \
--cc=gregkh@linuxfoundation.org \
--cc=initramfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=maks@debian.org \
--cc=stern@rowland.harvard.edu \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).