Case #00013913 - Gobi Loader fails to load firmware on boot, but loads find when loaded from command line once the system is up

Bug #684890 reported by Philipp Morger
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Manual call always succeeds... just not at boot time.

--- 8< ---

--(root@serenity)-(2.27)-(4)-(pts/1)-(18:38:46/Thu Dec 02)--
--(#:/tmp)-- cat gobi_loader.log
Gobi Loader Wrapper initiated
Sleeping for 5 seconds...
...done
Gobi Device before Firmware loading attempt
Bus 001 Device 003: ID 03f0:201d Hewlett-Packard un2400 Gobi Wireless Modem (QDL mode)
Loading Firmware
Executing /lib/udev/gobi_loader.real /dev/ttyUSB0 /lib/firmware/gobi
Gobi Device after Firmware loading attempt
Bus 001 Device 003: ID 03f0:201d Hewlett-Packard un2400 Gobi Wireless Modem (QDL mode)
-----------------------------------------------------------------
--(root@serenity)-(2.08)-(5)-(pts/1)-(18:38:49/Thu Dec 02)--
--(#:/tmp)-- /lib/udev/gobi_loader.real /dev/ttyUSB0 /lib/firmware/gobi
--(root@serenity)-(1.62)-(6)-(pts/1)-(18:39:02/Thu Dec 02)--
--(#:/tmp)-- lsusb | grep Gobi
Bus 001 Device 009: ID 03f0:1f1d Hewlett-Packard un2400 Gobi Wireless Modem

--- 8< ---

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: linux-image-2.6.35-23-generic 2.6.35-23.41
Regression: Yes
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.35-23.41-generic 2.6.35.7
Uname: Linux 2.6.35-23-generic x86_64
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
   Subdevices: 2/2
   Subdevice #0: subdevice #0
   Subdevice #1: subdevice #1
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: phoenix 2246 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xd7320000 irq 46'
   Mixer name : 'Analog Devices AD1984A'
   Components : 'HDA:11d4194a,103c30e7,00100400'
   Controls : 18
   Simple ctrls : 11
Date: Fri Dec 3 19:27:54 2010
HibernationDevice: RESUME=UUID=22dda47f-9794-437a-bbed-1234fe962e36
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
MachineType: Hewlett-Packard HP EliteBook 8530w
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-23-generic root=UUID=8beae753-ec13-40dd-bb10-57cfa23c58da ro vga=773 elevator=noop quiet splash nomodeset
ProcEnviron:
 LC_CTYPE=en_US.UTF-8
 PATH=(custom, user)
 LANG=en_GB.utf8
 SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.38
SourcePackage: linux
dmi.bios.date: 12/08/2009
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68PDV Ver. F.11
dmi.board.name: 30E7
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 90.26
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvr68PDVVer.F.11:bd12/08/2009:svnHewlett-Packard:pnHPEliteBook8530w:pvrF.11:rvnHewlett-Packard:rn30E7:rvrKBCVersion90.26:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP EliteBook 8530w
dmi.product.version: F.11
dmi.sys.vendor: Hewlett-Packard

Revision history for this message
Philipp Morger (philipp-morger) wrote :
tags: added: kernel-series-unknown
Revision history for this message
Stefan Bader (smb) wrote :

When calling the real loader, is stderr also redirected to the log output? It would be best to add the wrapper script as well here.

Revision history for this message
Philipp Morger (philipp-morger) wrote :

As requested

Revision history for this message
Stefan Bader (smb) wrote :

Thanks for the file. So in theory all stderr output should be in the log file too. But there is nothing. Would running the real load under strace give some insight? Would there be a difference when repeating the call to the real loader a second time in the wrapper (after another little sleep)?

Revision history for this message
Philipp Morger (philipp-morger) wrote :

Attached the logs of the gobi loader with the script already attached to this log.

The firmware failed the 1st time to load, but succeeded the 2nd time.

I also changed the timers.

I did one run with 1 firmware load try, with 15 seconds sleep before load and 5 seonds sleep after load - FAIL.

I did one run with 2 firmware load tries, but no sleeps in the script. - FAIL

I dunno, it's not that it would just succeed on any second load, nor does any waiting help. Please report if you see any information in the strace - I don't have the sorcery to read them in depth.

Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

Philipp Morger, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.13-rc5

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

tags: added: bios-outdated-f.20
removed: kernel-series-unknown
Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.