Hi Emad, your system logs are full of messages like this one: Jul 1 07:55:28 localhost kernel: Unable to handle kernel paging request at virtual address 6920678e Jul 1 07:55:28 localhost kernel: printing eip: Jul 1 07:55:28 localhost kernel: d882f2fb Jul 1 07:55:28 localhost kernel: *pde = 00000000 Jul 1 07:55:28 localhost kernel: Oops: 0002 Jul 1 07:55:28 localhost kernel: cs4281 soundcore parport_pc lp parport autofs ipt_REJECT iptable_filter ip_tables sg sr_mod ide-scsi scsi_mod ide-cd cdrom nls_iso8859-1 nls_cp437 vfat fat ke Jul 1 07:55:28 localhost kernel: CPU: 0 Jul 1 07:55:28 localhost kernel: EIP: 0060:[<d882f2fb>] Not tainted Jul 1 07:55:28 localhost kernel: EFLAGS: 00010296 Jul 1 07:55:28 localhost kernel: Jul 1 07:55:28 localhost kernel: EIP is at usb_free_dev_R41275f44 [usbcore] 0xb (2.4.20-18.9) Jul 1 07:55:28 localhost kernel: eax: 6920676e ebx: 6920676e ecx: d05a1ee4 edx: d05a1ed4 Jul 1 07:55:28 localhost kernel: esi: d05a0000 edi: d2da9800 ebp: 0000000a esp: d05a1eac Jul 1 07:55:28 localhost kernel: ds: 0068 es: 0068 ss: 0068 Jul 1 07:55:28 localhost kernel: Process modem_run (pid: 2098, stackpage=d05a1000) Jul 1 07:55:28 localhost kernel: Stack: d7e588e0 d7e588e0 d8843b71 6920676e c1eb6670 d05a0000 00000000 d05a0000 Jul 1 07:55:28 localhost kernel: 00000000 00000000 00000000 d05a0000 00000000 00000000 d05a1ee4 d05a1ee4 Jul 1 07:55:28 localhost kernel: d058f490 d059f420 00000282 d05a1f2c d7e585c0 00000286 d882f442 d7e588e0 Jul 1 07:55:28 localhost kernel: Call Trace: [<d8843b71>] sohci_unlink_urb [usb-ohci] 0x191 (0xd05a1eb4)) Jul 1 07:55:28 localhost kernel: [<d882f442>] usb_unlink_urb_R5e71a6fb [usbcore] 0x32 (0xd05a1f04)) Jul 1 07:55:28 localhost kernel: [<d8833db2>] destroy_async [usbcore] 0x72 (0xd05a1f0c)) Jul 1 07:55:28 localhost pppd[2102]: pppd 2.4.1 started by root, uid 0 Jul 1 07:55:28 localhost kernel: [<d8833e0f>] destroy_async_on_interface [usbcore] 0x4f (0xd05a1f20)) Jul 1 07:55:28 localhost kernel: [<d8835764>] proc_releaseinterface [usbcore] 0x64 (0xd05a1f44)) Jul 1 07:55:28 localhost pppoa3[2104]: pppoa3 version 1.2-beta1 started by root (uid 0) Jul 1 07:55:28 localhost kernel: [<d8835ba4>] usbdev_ioctl [usbcore] 0x1e4 (0xd05a1f58)) Jul 1 07:55:28 localhost pppoa3[2104]: Control thread ready Jul 1 07:55:29 localhost pppd[2102]: Using interface ppp0 Jul 1 07:55:29 localhost kernel: [<c0153b6d>] file_ioctl [kernel] 0x6d (0xd05a1f74)) Jul 1 07:55:29 localhost /etc/hotplug/net.agent: assuming ppp0 is already up Jul 1 07:55:29 localhost pppd[2102]: Connect: ppp0 <--> /dev/pts/2 Jul 1 07:55:29 localhost pppoa3[2104]: pusb_claim_interface 1 failed Jul 1 07:55:29 localhost kernel: [<c0153d64>] sys_ioctl [kernel] 0xd4 (0xd05a1f94)) Jul 1 07:55:29 localhost kernel: [<c010939f>] system_call [kernel] 0x33 (0xd05a1fc0)) Jul 1 07:55:29 localhost kernel: Jul 1 07:55:29 localhost kernel: Jul 1 07:55:29 localhost kernel: Code: ff 4b 20 0f 94 c0 84 c0 75 08 8b 5c 24 04 83 c4 08 c3 8b 83
This means that there is a bug in your kernel. If I recall correctly, this bug was introduced between 2.4.20 and 2.4.21 and corrected before 2.4.21 was released. It looks like redhat took some of the changes between 2.4.20 and 2.4.21 and added them to their kernel. Unfortunately they took the buggy code too! And additional funny (for me) point is that I wrote the destroy_async_on_interface code (see the above crash dump) to fix a previous kernel crash caused by modem_run, but now it is involved in a new modem_run inspired kernel crash! Anyway, look to see if redhat has introduced a new errata kernel - if so your problem may be fixed there. If not, try installing your own 2.4.21 kernel instead. All the best, Duncan. Liste de diffusion modem ALCATEL SpeedTouch USB Pour se d�sinscrire : mailto:[EMAIL PROTECTED]
