Thomas for you I guess ?

Assignee: bugsquad => tmb

Sorry, missed who was running before the trace.

Dec  8 13:21:58 localhost kernel: hda-intel: Enable sync_write for stable communication
Dec  8 13:21:58 localhost kernel: hda-intel: azx_get_response timeout, switching to polling mode: last cmd=0x000f0001
Dec  8 13:21:58 localhost kernel: HDMI status: Codec=0 Pin=3 Presence_Detect=0 ELD_Valid=0
Dec  8 13:21:58 localhost kernel: input: HDA ATI HDMI HDMI/DP as /devices/pci0000:00/0000:00:02.0/0000:01:00.1/sound/card1/input4
Dec  8 13:21:58 localhost kernel: irq 19: nobody cared (try booting with the "irqpoll" option)
Dec  8 13:21:58 localhost kernel: Pid: 585, comm: bash Not tainted 3.1.4-desktop-2.mga2 #1
Dec  8 13:21:58 localhost kernel: Call Trace:

boot line is
Dec  8 13:21:58 localhost kernel: Linux version 3.1.4-desktop-2.mga2 (iurt@ecosse.mageia.org) (gcc version 4.6.2 (GCC) ) #1 SMP Mon Dec 5 17:59:12 UTC 2011
Dec  8 13:21:58 localhost kernel: Command line: BOOT_IMAGE=Mageia_2_64_Alpha1 root=LABEL=cauldron hpet=force irqpoll init=/bin/systemd  vga=0x0324  3

 Warning! ehci_hcd should always be loaded before uhci_hcd and ohci_hcd, not after

This part of the problem's solution is to not have /etc/modprobe.conf.
I moved /etc/modprobe.conf /etc/modprobe.d/10_modprobe.conf
Next boot, the Warning no longer occurred.

Stack trace still happens. Even though three irq 19 are registered.

kernel: ehci_hcd 0000:00:13.2: PCI INT A -> GSI 19 (level, low) -> IRQ 19
kernel: ehci_hcd 0000:00:13.2: EHCI Host Controller
kernel: ehci_hcd 0000:00:13.2: new USB bus registered, assigned bus number 1
kernel: ehci_hcd 0000:00:13.2: irq 19, io mem 0xfe02c000
kernel: ehci_hcd 0000:00:13.2: USB 2.0 started, EHCI 1.00

kernel: ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
kernel: ohci_hcd 0000:00:13.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19
kernel: ohci_hcd 0000:00:13.0: OHCI Host Controller
kernel: ohci_hcd 0000:00:13.0: new USB bus registered, assigned bus number 2
kernel: ohci_hcd 0000:00:13.0: irq 19, io mem 0xfe02e000
kernel: firewire_ohci: Added fw-ohci device 0000:02:04.0, OHCI v1.10, 4 IR + 8 IT contexts, quirks 0x11

kernel: ohci_hcd 0000:00:13.1: PCI INT A -> GSI 19 (level, low) -> IRQ 19
kernel: ohci_hcd 0000:00:13.1: OHCI Host Controller
kernel: ohci_hcd 0000:00:13.1: new USB bus registered, assigned bus number 3
kernel: ohci_hcd 0000:00:13.1: irq 19, io mem 0xfe02d000

Work around solution for 
   Warning! ehci_hcd should always be loaded before uhci_hcd and ohci_hcd
is to remove all occurrences of any modprobe commands with uhci-hcd, ohci-hcd, ehci-hcd in /etc/modprobe.conf or in any files in /etc/modprobe.d



For the /etc/modprobe.conf is depreciated warning. I did a 
mv /etc/modprobe.conf /etc/modprobe.d/10_modprobe.conf
That seemed to improve boot time by a few seconds.

Downside of that is a second or more was added to numerous systemd service's completion time. Temporary solution, touch  /etc/modprobe.conf

(In reply to comment #4)
> Work around solution for 
>    Warning! ehci_hcd should always be loaded before uhci_hcd and ohci_hcd
> is to remove all occurrences of any modprobe commands with uhci-hcd, ohci-hcd,
> ehci-hcd in /etc/modprobe.conf or in any files in /etc/modprobe.d

I swear I checked two reboot logs and the problem was not there. Third reboot and it is back. :(

By the way, I thought the module-init-tools with later kernels would load modules in the order specified in  /lib/modules/*/modules.order

Warning! ehci_hcd should always be loaded before uhci_hcd 
no longer shows up in /var/log/kernel logs

Resolution: (none) => FIXED
Status: NEW => RESOLVED

problem is back in latest round of updates with 3.3.0-desktop-0.rc6.1.mga2

Status: RESOLVED => REOPENED
Source RPM: (none) => kernel-3.3.0-0.rc6.1.mga2.src.rpm
Resolution: FIXED => (none)

*** Bug 5508 has been marked as a duplicate of this bug. ***

CC: (none) => epistemepromeneur

Hi,

This bug was filed against cauldron, but we do not have cauldron at the moment.

Please report whether this bug is still valid for Mageia 2.

Thanks :)

Cheers,
marja

Keywords: (none) => NEEDINFO

(In reply to comment #9)

> Please report whether this bug is still valid for Mageia 2.

still valid.

Keywords: NEEDINFO => (none)

Please look at the bottom of this mail to see whether you're the assignee of this  bug, if you don't already know whether you are.


If you're the assignee:

We'd like to know for sure whether this bug was assigned correctly. Please change status to ASSIGNED if it is, or put OK on the whiteboard instead.

If you don't have a clue and don't see a way to find out, then please put NEEDHELP on the whiteboard.

Please assign back to Bug Squad or to the correct person to solve this bug if we were wrong to assign it to you, and explain why.

Thanks :)

**************************** 

@ the reporter and persons in the cc of this bug:

If you have any new information that wasn't given before (like this bug being valid for another version of Mageia, too, or it being solved) please tell us.

@ the reporter of this bug

If you didn't reply yet to a request for more information, please do so within two weeks from now.

Thanks all :-D

mageia 2 x86_64

Warning! ehci_hcd should always be loaded before uhci_hcd and ohci_hcd, not after

is still there in dmesg

This message is a reminder that Mageia 2 is nearing its end of life.
Approximately one month from now Mageia will stop maintaining and issuing updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '2'.

Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 2's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 2 is end of life.  If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia.

Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete.

-- 
The Mageia Bugsquad

Mageia 2 changed to end-of-life (EOL) status on ''22 November''. Mageia 2 is no
longer maintained, which means that it will not receive any further security or
bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
The Mageia Bugsquad

Status: REOPENED => RESOLVED
Resolution: (none) => OLD

I can verify the problem still exists on a clean release 4 beta 2 install with all updates.

$ journalctl | grep ehci_hcd
Jan 17 01:33:59 wb.home.test kernel

: ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
: Warning! ehci_hcd should always be loaded before uhci_hcd and ohci_hcd, not after

Status: RESOLVED => REOPENED
CC: (none) => junknospam
Version: 2 => Cauldron
Resolution: OLD => (none)
Source RPM: kernel-3.3.0-0.rc6.1.mga2.src.rpm => kernel-3.12.7-1.mga4.src.rpm

still a problem on mga4 released... it may even be the cause of some missing USB2.0 devices

CC: (none) => alien

*** Bug 8430 has been marked as a duplicate of this bug. ***

CC: (none) => eeeemail

modprobe.conf contains:

[root@localhost ~]# cat /etc/modprobe.conf 
install usb-interface /sbin/modprobe ohci_hcd; /sbin/modprobe ehci_hcd; /sbin/modprobe xhci_hcd; /sbin/modprobe ohci_pci; /sbin/modprobe ehci_pci; /bin/true

the workaround above didn't work, so i put ehci_hcd in the dracut.d/50-mageia.conf file, next to the ahci ... then ran "dracut -f", that seemed to work

(In reply to AL13N from comment #19)
> the workaround above didn't work, so i put ehci_hcd in the
> dracut.d/50-mageia.conf file, next to the ahci ... then ran "dracut -f",
> that seemed to work

Could you show exactly what was changed? My attempt is not removing the warning.
# cat 00-my_ehci_hcd.conf
add_drivers+=" ehci_hcd "
add_drivers+=" ehci-pci "

dracut.d/50-mageia.conf has at some point:

add_drivers+=" ahci "


i changed it into:

add_drivers+=" ahci ehci_hcd "

and did "dracut -f", then rebooted

(In reply to AL13N from comment #21)
> dracut.d/50-mageia.conf has at some point:
> 
> add_drivers+=" ahci "
> 
> 
> i changed it into:
> 
> add_drivers+=" ahci ehci_hcd "
> 
> and did "dracut -f", then rebooted

Ok, I also tried that and still get the error.
looking in journalctl  
 ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
: Warning! ehci_hcd should always be loaded before uhci_hcd and ohci_hcd, not after
 ehci-pci: EHCI PCI platform driver
 ehci-pci 0000:00:12.2: EHCI Host Controller
 ehci-pci 0000:00:12.2: new USB bus registered, assigned bus number 1
 ehci-pci 0000:00:12.2: applying AMD SB700/SB800/Hudson-2/3 EHCI dummy qh workaround
 ehci-pci 0000:00:12.2: debug port 1
 ehci-pci 0000:00:12.2: irq 17, io mem 0xff609500
 ehci-pci 0000:00:12.2: USB 2.0 started, EHCI 1.00
 usb usb1: Product: EHCI Host Controller
 usb usb1: Manufacturer: Linux 3.15.2-desktop-2.mga5 ehci_hcd
 ehci-pci 0000:00:13.2: EHCI Host Controller
 ehci-pci 0000:00:13.2: new USB bus registered, assigned bus number 2
 ehci-pci 0000:00:13.2: applying AMD SB700/SB800/Hudson-2/3 EHCI dummy qh workaround
 ehci-pci 0000:00:13.2: debug port 1
 ehci-pci 0000:00:13.2: irq 19, io mem 0xff609400
 ehci-pci 0000:00:13.2: USB 2.0 started, EHCI 1.00
 usb usb2: Product: EHCI Host Controller
 usb usb2: Manufacturer: Linux 3.15.2-desktop-2.mga5 ehci_hcd
 usb 1-3: new high-speed USB device number 2 using ehci-pci

you sure that the initrd was actually redone? also, i didn't use ehci-pci and check if you don't have modprobe.conf that has the order, (i did remove that, even though it didn't appear to work)

check with rdinitdebug kernel parameter what kind of order is being done...

what also works, is booting with "rd.driver.pre=ehci_hcd"

(In reply to AL13N from comment #23)

> and check if you don't have modprobe.conf that has the order, (i did remove
> that, even though it didn't appear to work)

Yup, there lies the problem. You do need to remove the ehci line from modprobe.conf.

except that just removing that, didn't work yet...

(In reply to AL13N from comment #25)
> except that just removing that, didn't work yet...

Yes, that is correct. Bad news is removing line from /etc/modprobe.conf and creating my own 

#  cat /etc/dracut.conf.d/my_dracut.conf
# always include ahci_hcd driver (mga#3667)
add_drivers+=" ahci  ehci_hcd"

add_device+="LABEL=swap"
#******** end /etc/dracut.conf.d/my_dracut.conf *********

worked on my Lenovo system but is not fixing the problem on my HP Pavilion P6610F (Product number BM417AA) system.  :(

the way i see it, is that there's a race condition someplace... removing the modprobe.conf file (not recreating it) seems to work together with the dracut change

Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer 
maintained, which means that it will not receive any further security or bug 
fix updates.

Package Maintainer: If you wish for this bug to remain open because you plan to 
fix it in a currently maintained version, simply change the 'version' to a later 
Mageia version.

Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't 
able to fix it before Mageia 4's end of life. If you are able to reproduce it 
against a later version of Mageia, you are encouraged to click on "Version" and 
change it against that version of Mageia. If it's valid in several versions, 
select the highest and add MGAxTOO in whiteboard for each other valid release.
Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO.

Although we aim to fix as many bugs as possible during every release's lifetime, 
sometimes those efforts are overtaken by events. Often a more recent Mageia 
release includes newer upstream software that fixes bugs or makes them obsolete.

If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].

[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/

Mass-reassigning all bugs with "kernel" in the Source RPM field that are assigned to tmb, to the kernel packagers group, because tmb is currently MIA.

Assignee: tmb => kernel

This is module ordering issue that happens from times to times for ~15 years so...

Severity: critical => minor
Priority: High => Low
CC: (none) => thierry.vignaud

(In reply to Thierry Vignaud from comment #30)
> This is module ordering issue that happens from times to times for ~15 years
> so...

so probably still valid.... I'll set it to cauldron and MGA6TOO, then.

Source RPM: kernel-4.9.5-1.mga6.src.rpm => kernel
Status comment: 6_s2 => (none)
Whiteboard: (none) => MGA6TOO
Version: 5 => Cauldron
CC: (none) => marja11

(In reply to Marja van Waes from comment #31)
> (In reply to Thierry Vignaud from comment #30)
> > This is module ordering issue that happens from times to times for ~15 years
> > so...
> 
> so probably still valid.... I'll set it to cauldron and MGA6TOO, then.

Yep, I can confirm problem is still there on mga6 and mga7 on three of my desktops (ASUS, HP, Lenovo)

I am unable to dd iso file to a usb drive. I get a driver reload/timeout and usb no longer usable which I attribute to the out of ordering of the modules.

After bricking 5 or 6 usb thumb drives I have given up doing iso writing to usb.

Workaround fix:

Add "rd.driver.pre=ehci_hcd" to kernel boot line. For grub users you
can add it in the /etc/default/grub file and run update-grub.

Add it to GRUB_CMDLINE_LINUX_DEFAULT= or GRUB_CMDLINE_LINUX= line.
Copy of my settings:
$ grep GRUB_CMDLINE /etc/default/grub
GRUB_CMDLINE_LINUX_DEFAULT=" noiswmd audit=0"
GRUB_CMDLINE_LINUX="ipv6.disable=1 rd.driver.pre=ehci_hcd"


usb burn failure is still a problem. Opening a bug report for that since I can now do a small size burn.

is this bug still valid ?

CC: (none) => mageia

(In reply to Nicolas Lécureuil from comment #34)
> is this bug still valid ?

Apparently this journal snippet
applying AMD SB700/SB800/Hudson-2/3 EHCI dummy qh workaround
has resolved the problem.

Status: REOPENED => RESOLVED
Resolution: (none) => FIXED

I'm sorry, but I made this mistake too. For Mageia 7, and now for Mageia 8 as well.
With this solution, it is load the modules in the correct order.


cat /etc/modprobe.d/blacklist.ohci.conf
blacklist ohci_hcd
blacklist uhci_hcd


cat /etc/modprobe.d/00_modprobe.conf
...
alias parport_lowlevel	parport_pc
alias usbdevfs	usbcore

###########   csablak
# "Warning! ehci_hcd should always be loaded before uhci_hcd and ohci_hcd, not after"
softdep uhci-hcd pre: ehci-hcd
softdep ohci-hcd pre: ehci-hcd
########### csablak END

CC: (none) => pingvin

Is the workaround working also for initrd images, i.e. when booting from USB devices? I noticed also a strange behaviour when booting from an USB 3.0 device (and this happens on several machines, so I think ), which can either the Live or a plain installation made on a pendrive or another USB disk. Basically once boot every 2 or 3, the USB3.0 port is booted in USB2.0 mode. You detect, as being a boot device, you see application immediately starting a lot slower (doing a simple hdparm -t /dev/sdX would reveal a transfer rate of 30MB/s instead of typical 300MB/s).

Furthermore I noticed that most of distro (FC, opensuse, etc.) use CONFIG_USB=y instead of CONFIG_USB=m that we use. What are the advantages (in term of operativeness) in loading USB driver as a module rather than builtin in the kernel? Or viceversa what are the advantages having the USB driver builtin in the kernel, rather than modprobing at a later time?

CC: (none) => ghibomgx

(In reply to Giuseppe Ghibò from comment #37)
  The proof of the pudding is in the eating. 

For me perhaps the problem is was that a USB dvb stick, is always plugged in.