Hi,
> [CODE]
> Mar 26 14:48:07 localhost kernel: Kernel command line: ro root=LABEL=/1
> Mar 26 14:48:19 localhost kernel: usbcore: registered new driver speedtch
> Mar 26 14:48:19 localhost kernel: speedtch 1-2:1.0: speedtch_find_firmware: no
> stage 1 firmware found!
the usual reasons for this one are: root filesystem not yet mounted (this can
happen if the module is loaded from an initrd for example); sysfs not yet
mounted.
> ...
>
> Mar 26 16:16:18 localhost kernel: Kernel command line: ro root=LABEL=/1
> Mar 26 16:16:42 localhost kernel: usbcore: registered new driver speedtch
> Mar 26 16:16:42 localhost kernel: firmware_loading_store: unexpected value (0)
Did RH just change over to udev? Last time I saw this one, it was because
/proc/sys/kernel/hotplug contained /sbin/hotplug rather than
/sbin/udevsend, causing two copies of the firmware loader to be run in
parallel.
> Mar 26 16:16:42 localhost kernel: speedtch 1-2:1.0: speedtch_find_firmware: no
> stage 1 firmware found!
>
> ...
>
> Mar 26 19:21:39 localhost kernel: Kernel command line: ro root=LABEL=/1
> Mar 26 19:21:51 localhost kernel: speedtch 1-2:1.0: found stage 1 firmware
> speedtch-1.bin
> Mar 26 19:21:52 localhost kernel: speedtch 1-2:1.0: found stage 2 firmware
> speedtch-2.bin.4.00
> Mar 26 19:21:52 localhost kernel: speedtch 1-2:1.0: speedtch_upload_firmware:
> read BLOCK4 from modem failed (-110)!
The last time I saw this one, it was because of a bug in firmware_helper, fixed
by this patch:
http://marc.theaimsgroup.com/?l=linux-hotplug-devel&m=112625478704423&w=2
I'd be surprised if FC didn't have this fix though.
> Mar 26 19:21:52 localhost kernel: speedtch 1-2:1.0: speedtch_heavy_init:
> firmware
> upload failed (-110)!
>
> ...
>
> Mar 26 19:31:06 localhost kernel: Kernel command line: ro root=LABEL=/1
> acpi=off
> Mar 26 19:31:15 localhost kernel: speedtch 1-2:1.0: found stage 1 firmware
> speedtch-1.bin
> Mar 26 19:31:15 localhost kernel: speedtch 1-2:1.0: found stage 2 firmware
> speedtch-2.bin.4.00
> Mar 26 19:31:16 localhost kernel: speedtch 1-2:1.0: speedtch_upload_firmware:
> read BLOCK4 from modem failed (-110)!
> Mar 26 19:31:16 localhost kernel: speedtch 1-2:1.0: speedtch_heavy_init:
> firmware
> upload failed (-110)!
>
> ...
>
> Mar 26 20:05:20 localhost kernel: Kernel command line: ro root=LABEL=/1
> acpi=off
> Mar 26 20:05:30 localhost kernel: firmware_loading_store: unexpected value (0)
> Mar 26 20:05:30 localhost kernel: speedtch 1-2:1.0: speedtch_find_firmware: no
> stage 1 firmware found!
>
> ...
>
> Mar 26 20:22:43 localhost kernel: Kernel command line: ro root=LABEL=/1
> selinux=0
> Mar 26 20:22:43 localhost kernel: SELinux: Disabled at boot.
> Mar 26 20:22:50 localhost kernel: usb 1-2: reset full speed USB device using
> uhci_hcd and address 2
> Mar 26 20:22:50 localhost kernel: usbcore: registered new driver speedtch
> Mar 26 20:22:50 localhost kernel: speedtch 1-2:1.0: found stage 1 firmware
> speedtch-1.bin
> Mar 26 20:22:50 localhost kernel: ------------[ cut here ]------------
> Mar 26 20:22:50 localhost kernel: kernel BUG at
> drivers/base/firmware_class.c:231!
> Mar 26 20:22:50 localhost kernel: invalid opcode: 0000 [#1]
> Mar 26 20:22:50 localhost kernel: last sysfs file:
> /class/firmware/1-2:1.0/loading
> Mar 26 20:22:50 localhost kernel: Modules linked in: speedtch usbatm atm
> uhci_hcd
> snd_cmipci gameport snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq
> parport_pc snd_pcm_oss snd_mixer_oss parport snd_pcm snd_page_alloc
> snd_opl3_lib
> snd_timer snd_hwdep snd_mpu401_uart i2c_viapro snd_rawmidi via686a
> snd_seq_device
> hwmon snd i2c_isa soundcore i2c_core ext3 jbd
> Mar 26 20:22:50 localhost kernel: CPU: 0
> Mar 26 20:22:50 localhost kernel: EIP: 0060:[<c0228e82>] Not tainted VLI
> Mar 26 20:22:50 localhost kernel: EFLAGS: 00010206 (2.6.15-1.2054_FC5 #1)
> Mar 26 20:22:51 localhost kernel: EIP is at firmware_data_write+0xfe/0x152
> Mar 26 20:22:51 localhost kernel: eax: 00061000 ebx: e88ff000 ecx:
> ffffffff
> edx: e6931be0
> Mar 26 20:22:51 localhost kernel: esi: 00000000 edi: 00000000 ebp:
> 00060000
> esp: c1678f34
> Mar 26 20:22:51 localhost kernel: ds: 007b es: 007b ss: 0068
> Mar 26 20:22:51 localhost kernel: Process nash-hotplug (pid: 307,
> threadinfo=c1678000 task=c1725000)
> Mar 26 20:22:52 localhost kernel: Stack: <0>e7f61000 e6931be0 00061000
> e689aec0
> c0228d84 00060000 00000000 e6d61ae8
> Mar 26 20:22:52 localhost kernel: c018775e 00060000 00000000 00001000
> b7ec9000 e7f61000 e6caba78 00001000
> Mar 26 20:22:52 localhost kernel: c16e7720 c01876a4 b7ec9000 0005d579
> c0152b9b c1678fa4 c16e7720 fffffff7
> Mar 26 20:22:52 localhost kernel: Call Trace:
> Mar 26 20:22:52 localhost kernel: [<c0228d84>] firmware_data_write+0x0/0x152
>
> [<c018775e>] write+0xba/0xde
> Mar 26 20:22:53 localhost kernel: [<c01876a4>] write+0x0/0xde
> [<c0152b9b>]
> vfs_write+0xa1/0x140
> Mar 26 20:22:53 localhost kernel: [<c01530a3>] sys_write+0x3c/0x63
> [<c0102bc1>] syscall_call+0x7/0xb
> Mar 26 20:22:53 localhost kernel: Code: 89 df f3 a5 89 c1 83 e1 03 74 02 f3
> a4 8b
> 42 5c 8b 40 04 e8 45 06 f2 ff 8b 54 24 04 8b 42 5c 89 58 04 8b 44 24 08 3b 42
> 64
> 7e 08 <0f> 0b e7 00 02 10 31 c0 8b 4c 24 2c c1 e9 02 8b 54 24 0c 03 6a
> Mar 26 20:22:53 localhost kernel: Continuing in 120 seconds.
Report this Oops to redhat. The kernel should never Oops.
> ...
>
> Mar 26 20:27:36 localhost kernel: Kernel command line: ro root=LABEL=/1
> selinux=0
> Mar 26 20:27:50 localhost kernel: firmware_loading_store: unexpected value (0)
> Mar 26 20:27:51 localhost kernel: speedtch 1-2:1.0: speedtch_find_firmware: no
> stage 1 firmware found!
>
> ...
>
> Mar 26 20:58:29 localhost kernel: Kernel command line: ro root=LABEL=/1
> selinux=0
> Mar 26 20:58:42 localhost kernel: speedtch 1-2:1.0: found stage 1 firmware
> speedtch-1.bin
> Mar 26 20:58:42 localhost kernel: speedtch 1-2:1.0: found stage 2 firmware
> speedtch-2.bin.4.00
> Mar 26 20:58:44 localhost kernel: speedtch 1-2:1.0: speedtch_upload_firmware:
> read BLOCK4 from modem failed (-110)!
> Mar 26 20:58:44 localhost kernel: speedtch 1-2:1.0: speedtch_heavy_init:
> firmware
> upload failed (-110)!
> [/CODE]
>
> Sometimes the firmware is found sometimes not. Sometimes the load fails early.
> Sometimes a kernel BUG is reported. It does not seem to be dependent on ACPI
> or
> SELinux. It would seem to be either the kernel bug, as reported, or udev.
>
> I tried adding the line
> [CODE]
> ACTION="add", DRIVER="speedtch", PROGRAM="/sbin/firmware_helper"
> [/CODE]
> to /etc/udev/rules.d/50-udev.rules as recommended by an earlier version of
> http://www.linux-usb.org/SpeedTouch/firmware/index.html. That seemed to
> increase
> the likelyhood of getting the kernel BUG case but, on further investigation, I
> found that 05-udev-early.rules already contains the line
> [CODE]
> ACTION=="add", SUBSYSTEM=="firmware", ENV{FIRMWARE}=="*",
> RUN="/sbin/firmware_helper", OPTIONS="last_rule"
> [/CODE]
> which is much closer to that currently recommended by
> http://www.linux-usb.org/SpeedTouch/firmware/index.html.
>
> I am stuck with my old dialup modem until I can fix this, so if anyone has any
> suggestions I would be most gratefull.
All the best,
Duncan.
Liste de diffusion modem ALCATEL SpeedTouch USB
Pour se désinscrire : mailto:[EMAIL PROTECTED]
