Summary: | kernel can't handle lack of ueagle-atm firmware | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Matthieu Volat <vmatth> |
Component: | [OLD] Core system | Assignee: | Gentoo Kernel Bug Wranglers and Kernel Maintainers <kernel> |
Status: | RESOLVED UPSTREAM | ||
Severity: | normal | CC: | castet.matthieu |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Other | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Matthieu Volat
2006-04-29 10:46:25 UTC
Could you test again with debug=2 module parameter ? Could you post the trace in syslog (there will be timestamp for each message). On my board : - if there no firmware, the device fails on pre-firmware stage, but for some reasons (motherboard that keep usb powered on reboot), you could have a post-firmware device at boot. - when DSPep.bin is missing, the driver keep requesting the firmware, but with an interval on some seconds [1]. So the system don't become unstable. What's strange in your log is that there more "(re)booting started" than "requesting firmware ueagle-atm/DSPep.bin failed". May be there are a race on SMP processors. [1] May 8 00:00:00 localhost kernel: usb 1-2: [UEAGLE-ATM] requesting firmware ueag le-atm/DSPep.bin failed with error -2 May 8 00:00:04 localhost kernel: usb 1-2: [ueagle-atm] (re)booting started May 8 00:00:06 localhost kernel: usb 1-2: [UEAGLE-ATM] requesting firmware ueag le-atm/DSPep.bin failed with error -2 May 8 00:00:10 localhost kernel: usb 1-2: [ueagle-atm] (re)booting started May 8 00:00:11 localhost kernel: usb 1-2: [UEAGLE-ATM] requesting firmware ueag le-atm/DSPep.bin failed with error -2 May 8 00:00:15 localhost kernel: usb 1-2: [ueagle-atm] (re)booting started May 8 00:00:17 localhost kernel: usb 1-2: [UEAGLE-ATM] requesting firmware ueag le-atm/DSPep.bin failed with error -2 May 8 00:00:21 localhost kernel: usb 1-2: [ueagle-atm] (re)booting started May 8 00:00:22 localhost kernel: usb 1-2: [UEAGLE-ATM] requesting firmware ueag le-atm/DSPep.bin failed with error -2 May 8 00:00:26 localhost kernel: usb 1-2: [ueagle-atm] (re)booting started May 8 00:00:27 localhost kernel: usb 1-2: [UEAGLE-ATM] requesting firmware ueag le-atm/DSPep.bin failed with error -2 May 8 00:00:31 localhost kernel: usb 1-2: [ueagle-atm] (re)booting started May 8 00:00:33 localhost kernel: usb 1-2: [UEAGLE-ATM] requesting firmware ueag le-atm/DSPep.bin failed with error -2 May 8 00:00:37 localhost kernel: usb 1-2: [ueagle-atm] (re)booting started Matthieu, thanks for taking the time to look at this. I'm adding you to CC so that you are emailed responses. Reading through this again, I may have been wrong in my mail when I said the lack of firmware caused the system to slow to a crawl and be unresponsive. Actually what is probably happening is that badness in __vunmap is causing enough problems to make the input subsystem non-operational. So, the delay is probably fine, we just need to determine the reason for badness. Hopefully the debug parameter will help out there. The same thing is happening here too since I upgraded kernel from 2.6.16-gentoo-r3 to 2.6.16-gentoo-r6 : I can't now reproduce this bug... usbcore: registered new driver ueagle-atm usb 3-2: [UEAGLE-ATM] requesting firmware ueagle-atm/DSPep.bin failed with error -2 usb 3-2: [ueagle-atm] (re)booting started usb 3-2: [UEAGLE-ATM] requesting firmware ueagle-atm/DSPep.bin failed with error -2 usb 3-2: [ueagle-atm] (re)booting started usb 3-2: [UEAGLE-ATM] requesting firmware ueagle-atm/DSPep.bin failed with error -2 usb 3-2: [ueagle-atm] (re)booting started usb 3-2: [UEAGLE-ATM] requesting firmware ueagle-atm/DSPep.bin failed with error -2 usb 3-2: [ueagle-atm] (re)booting started usb 3-2: [UEAGLE-ATM] requesting firmware ueagle-atm/DSPep.bin failed with error -2 usb 3-2: [ueagle-atm] (re)booting started usb 3-2: [UEAGLE-ATM] requesting firmware ueagle-atm/DSPep.bin failed with error -2 usb 3-2: [ueagle-atm] (re)booting started usb 3-2: [UEAGLE-ATM] requesting firmware ueagle-atm/DSPep.bin failed with error -2 usb 3-2: [ueagle-atm] (re)booting started usb 3-2: [UEAGLE-ATM] requesting firmware ueagle-atm/DSPep.bin failed with error -2 I used exactly the same kernel configuration (actually, I used the .config file of the previous version and make oldconfig); and whenever I unmerge firmware or rename some files, I have the same output and the system doesn't go crazy... Matthieu, could you attach your .config ? Do you use hotplug or udev ? What happen if you unplug the modem when you boot, and you plug it only at the end of the boot ? With and without ueagle-atm/eagleIII.fw in your hotplug firmware dir. Yep, there is a great difference between the time I put this bug repport and now : in order to use my modem, I had to emerge hotplug. Yet, I boot with udev, but hotplug seems to not be used (ps -A | grep hotplug returns nothing). Whatever I tried, the modem wasn't working at all without hotplug : even with firmware installed, the kernel wasn't loading the DSPep.bin file : after emerging hotplug, it could. Anyway, my .config is at www.ensil.unilim.fr/~volat/config-2.6.16-gentoo-r6 ... The time I plug the modem doesn't seem to be a factor... I will try all the combinaison I could figure and report if I find something... If this is not reproducible I'll close this. If it does happen again, please reopen this bug. |