[Bug 449853] New: Kernel log shows ehci on uhci/ohci load ordering problem
https://bugzilla.novell.com/show_bug.cgi?id=449853 Summary: Kernel log shows ehci on uhci/ohci load ordering problem Product: openSUSE 11.1 Version: RC 1 Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: tvrtko@ursulin.net QAContact: qa@suse.de Found By: Community User Summary says it all. Actual message is: Warning! ehci_hcd should always be loaded before uhci_hcd and ohci_hcd, not after lsmod output: tvrtko@sol:~$ lsmod Module Size Used by coretemp 7768 0 it87 26160 0 hwmon_vid 3336 1 it87 binfmt_misc 10340 1 snd_pcm_oss 49184 0 snd_mixer_oss 16888 1 snd_pcm_oss snd_seq 62400 0 nls_utf8 2240 4 cifs 261560 4 ipv6 294744 36 af_packet 20792 0 cpufreq_conservative 8368 0 cpufreq_userspace 4284 0 cpufreq_powersave 2328 0 acpi_cpufreq 9016 0 fuse 61280 1 loop 17988 0 dm_mod 74320 0 snd_usb_audio 98048 3 snd_usb_lib 18936 1 snd_usb_audio snd_rawmidi 26848 1 snd_usb_lib snd_seq_device 8684 2 snd_seq,snd_rawmidi snd_hda_intel 546004 3 snd_pcm 95680 3 snd_pcm_oss,snd_usb_audio,snd_hda_intel snd_timer 26728 2 snd_seq,snd_pcm snd_page_alloc 9928 2 snd_hda_intel,snd_pcm snd_hwdep 9136 2 snd_usb_audio,snd_hda_intel ohci1394 31444 0 sr_mod 16340 0 snd 75032 23 snd_pcm_oss,snd_mixer_oss,snd_seq,snd_usb_audio,snd_usb_lib,snd_rawmidi,snd_seq_device,snd_hda_intel,snd_pcm,snd_timer,snd_hwdep ppdev 8272 0 wmi 8224 0 parport_pc 40472 0 ieee1394 99280 1 ohci1394 parport 41808 2 ppdev,parport_pc soundcore 8880 1 snd joydev 12192 0 forcedeth 60376 0 pcspkr 3144 0 cdrom 36264 1 sr_mod rtc_cmos 14040 0 rtc_core 22628 1 rtc_cmos button 8392 0 rtc_lib 3624 1 rtc_core sg 35408 0 usbhid 53248 0 hid 41744 1 usbhid ff_memless 8992 1 usbhid ehci_hcd 55108 0 sd_mod 35176 6 crc_t10dif 2232 1 sd_mod ohci_hcd 36628 0 usbcore 199280 6 snd_usb_audio,snd_usb_lib,usbhid,ehci_hcd,ohci_hcd edd 10336 0 ext3 142632 4 mbcache 10492 1 ext3 jbd 69032 1 ext3 fan 6080 0 ide_pci_generic 4732 0 ata_generic 6124 0 pata_amd 13772 0 amd74xx 7216 0 ide_core 118524 2 ide_pci_generic,amd74xx ahci 34692 5 libata 183088 3 ata_generic,pata_amd,ahci scsi_mod 179688 4 sr_mod,sg,sd_mod,libata dock 14628 1 libata thermal 24296 0 processor 50160 2 acpi_cpufreq,thermal thermal_sys 14416 3 fan,thermal,processor hwmon 4120 3 coretemp,it87,thermal_sys tvrtko@sol:~$ /sbin/lspci 00:00.0 Host bridge: nVidia Corporation MCP73 Host Bridge (rev a2) 00:00.1 RAM memory: nVidia Corporation nForce 630i memory controller (rev a2) 00:01.0 RAM memory: nVidia Corporation nForce 630i memory controller (rev a1) 00:01.1 RAM memory: nVidia Corporation nForce 630i memory controller (rev a1) 00:01.2 RAM memory: nVidia Corporation nForce 630i memory controller (rev a1) 00:01.3 RAM memory: nVidia Corporation nForce 630i memory controller (rev a1) 00:01.4 RAM memory: nVidia Corporation nForce 630i memory controller (rev a1) 00:01.5 RAM memory: nVidia Corporation nForce 630i memory controller (rev a1) 00:01.6 RAM memory: nVidia Corporation nForce 630i memory controller (rev a1) 00:02.0 RAM memory: nVidia Corporation nForce 630i memory controller (rev a1) 00:03.0 ISA bridge: nVidia Corporation MCP73 LPC Bridge (rev a2) 00:03.1 SMBus: nVidia Corporation MCP73 SMBus (rev a1) 00:03.2 RAM memory: nVidia Corporation MCP73 Memory Controller (rev a1) 00:03.4 RAM memory: nVidia Corporation MCP73 Memory Controller (rev a1) 00:04.0 USB Controller: nVidia Corporation GeForce 7100/nForce 630i (rev a1) 00:04.1 USB Controller: nVidia Corporation MCP73 [nForce 630i] USB 2.0 Controller (EHCI) (rev a1) 00:08.0 IDE interface: nVidia Corporation MCP73 IDE (rev a1) 00:09.0 Audio device: nVidia Corporation MCP73 High Definition Audio (rev a1) 00:0a.0 PCI bridge: nVidia Corporation MCP73 PCI Express bridge (rev a1) 00:0e.0 SATA controller: nVidia Corporation GeForce 7100/nForce 630i (rev a2) 00:0f.0 Ethernet controller: nVidia Corporation MCP73 Ethernet (rev a2) 00:10.0 VGA compatible controller: nVidia Corporation GeForce 7100/nForce 630i (rev a2) 01:07.0 FireWire (IEEE 1394): Texas Instruments TSB43AB23 IEEE-1394a-2000 Controller (PHY/Link) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=449853
Andreas Jaeger
https://bugzilla.novell.com/show_bug.cgi?id=449853
User mmarek@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=449853#c1
Michal Marek
https://bugzilla.novell.com/show_bug.cgi?id=449853
User oneukum@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=449853#c3
Oliver Neukum
https://bugzilla.novell.com/show_bug.cgi?id=449853
Jeff Mahoney
https://bugzilla.novell.com/show_bug.cgi?id=449853
User mmarek@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=449853#c4
Michal Marek
https://bugzilla.novell.com/show_bug.cgi?id=449853
Michal Marek
https://bugzilla.novell.com/show_bug.cgi?id=449853
User mmarek@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=449853#c5
Michal Marek
https://bugzilla.novell.com/show_bug.cgi?id=449853
User hare@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=449853#c6
Hannes Reinecke
https://bugzilla.novell.com/show_bug.cgi?id=449853
User bwalle@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=449853#c7
--- Comment #7 from Bernhard Walle
https://bugzilla.novell.com/show_bug.cgi?id=449853
User oneukum@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=449853#c8
Oliver Neukum
https://bugzilla.novell.com/show_bug.cgi?id=449853
User mmarek@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=449853#c9
--- Comment #9 from Michal Marek
We add install lines again.
What about a generic
# SUSE INITRD: foo REQUIRES bar
If you are going to implement that, why not. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=449853
User bwalle@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=449853#c10
--- Comment #10 from Bernhard Walle
https://bugzilla.novell.com/show_bug.cgi?id=449853
User mmarek@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=449853#c11
Michal Marek
https://bugzilla.novell.com/show_bug.cgi?id=449853
User bwalle@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=449853#c12
--- Comment #12 from Bernhard Walle
https://bugzilla.novell.com/show_bug.cgi?id=449853
User tvrtko@ursulin.net added comment
https://bugzilla.novell.com/show_bug.cgi?id=449853#c13
Tvrtko Ursulin
https://bugzilla.novell.com/show_bug.cgi?id=449853
User bwalle@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=449853#c14
--- Comment #14 from Bernhard Walle
"Online update only" means post release? It is not clear to me (from above discussion) whether until then we get full USB 2.0 speed or not? If not then rather than shipping with a serious performance issue (just to release an update effectively immediately?) I would rather delay the product and have it shipped in a better shape.
And in the end we will never ship. Because there will be always a bug that causes the delay. But I can only give recommendations. The decision will be made by the project manager (Stephan Kulow).
Also, from what is is worth, I don't really think dependency data in comments is a good and robust solution. Why the whole problem with initrd and modprobe.conf if I may ask? It would make most sense if initrd would use modprobe.conf in the same way "full system" does. Single point of configuration, single rules, single behaviour.
We use the same configuration. But we need to decide which programs and modules we include in initrd (or do you think we should include the hole hard disk in initrd). There are four options 1) Hard-code such things in initrd. 2) Use the comments I implemented. 3) Express dependencies not in install lines but with an additional mechanism (which may be done for 11.2). 4) Try to parse the install lines. That is error-prone. I don't want that. I used (2). Point. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=449853
User tvrtko@ursulin.net added comment
https://bugzilla.novell.com/show_bug.cgi?id=449853#c15
--- Comment #15 from Tvrtko Ursulin
(In reply to comment #13 from Tvrtko Ursulin)
"Online update only" means post release? It is not clear to me (from above discussion) whether until then we get full USB 2.0 speed or not? If not then rather than shipping with a serious performance issue (just to release an update effectively immediately?) I would rather delay the product and have it shipped in a better shape.
And in the end we will never ship. Because there will be always a bug that causes the delay. But I can only give recommendations. The decision will be made by the project manager (Stephan Kulow).
This is still under the assumption that with this setup we don't get USB 2.0 full speed? I wanted to check that myself but found out my external HDD does not work any more (raised another bug about that) so I don't know. But I would be surprised because that would mean no one tested the betas with USB 2.0. I hoped there are more early adopters than that... But my point is that I don't think it is that much less risky to push an update after the release if it is so quickly after that it still won't get wide testing coverage. If it's broken you still break a lot of systems (except those who don't update) and the only way you can get wider testing is to push it in the wild (slight assumption here again). Think of the bad press - openSUSE 11.1 is out but USB 2.0 does not work? So what's another RC.. make it done when it's ready.
Also, from what is is worth, I don't really think dependency data in comments is a good and robust solution. Why the whole problem with initrd and modprobe.conf if I may ask? It would make most sense if initrd would use modprobe.conf in the same way "full system" does. Single point of configuration, single rules, single behaviour.
We use the same configuration. But we need to decide which programs and modules we include in initrd (or do you think we should include the hole hard disk in initrd). There are four options
1) Hard-code such things in initrd. 2) Use the comments I implemented. 3) Express dependencies not in install lines but with an additional mechanism (which may be done for 11.2). 4) Try to parse the install lines. That is error-prone. I don't want that.
I used (2). Point.
I don't think we should put everything into initrd, just that there must be a better way than the one chosen, because it is redundant, and that is usually a bad sign. I was thinking about teaching modprobe to dump desired information and now I see what you mean with not wanting to parse install lines, they seem to be shell code snipets. Maybe extending modprobe to support more verbose operation so it prints out what modules would it load so you can do something like: # modprobe -v -n --show-insmod ohci_hcd WOULD-INSMOD: usbcore.ko install ohci_hcd /sbin/modprobe ehci_hcd WOULD-INSMOD: ehci_hcd.ko WOULD-INSMOD: ohci_hcd.ko Or some other special output formatting.. I see that this could work, no? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=449853
User bwalle@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=449853#c16
--- Comment #16 from Bernhard Walle
Maybe extending modprobe to support more verbose operation so it prints out what modules would it load so you can do something like:
In last RCs, sure. ... But I have no problem when you work upstream with module-init-tools authors to extend modprobe. Any help is appreciated there! But for openSUSE 11.1 we use that comments. POINT. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=449853
User mmarek@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=449853#c17
--- Comment #17 from Michal Marek
(In reply to comment #15 from Tvrtko Ursulin)
Maybe extending modprobe to support more verbose operation so it prints out what modules would it load so you can do something like:
In last RCs, sure. ... But I have no problem when you work upstream with module-init-tools authors to extend modprobe. Any help is appreciated there!
FYI - we do plan to fix this better, see bug 450411. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=449853
User mmarek@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=449853#c18
--- Comment #18 from Michal Marek
https://bugzilla.novell.com/show_bug.cgi?id=449853
User oneukum@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=449853#c19
--- Comment #19 from Oliver Neukum
https://bugzilla.novell.com/show_bug.cgi?id=449853
User mmarek@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=449853#c20
--- Comment #20 from Michal Marek
https://bugzilla.novell.com/show_bug.cgi?id=449853
User udo1@udo.hu added comment
https://bugzilla.novell.com/show_bug.cgi?id=449853#c21
Udo Attila Fischer
https://bugzilla.novell.com/show_bug.cgi?id=449853
User mmarek@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=449853#c22
--- Comment #22 from Michal Marek
https://bugzilla.novell.com/show_bug.cgi?id=449853
User swamp@suse.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=449853#c23
Swamp Script User
https://bugzilla.novell.com/show_bug.cgi?id=449853
User mmarek@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=449853#c24
Michal Marek
participants (1)
-
bugzilla_noreply@novell.com