It worked with 2.6.20 from fedora 6. Is there any way to "patch" this for now, so I can get it working again? I need ftdi-sio for my usb-uirt as I am about to go out of town for quite some time and can't use myth without it. I mean, is there some hack I can use?
On 6/1/07, Andrew Morton <[EMAIL PROTECTED]> wrote: > On Fri, 1 Jun 2007 11:31:30 -0700 > [EMAIL PROTECTED] wrote: > > > > (please followup via emailed reply-to-all, not via the bugzilla web > interface) > > > http://bugzilla.kernel.org/show_bug.cgi?id=8564 > > > > Summary: ftdi_sio: BUG: unable to handle kernel NULL pointer > > dereference at virtual address > > Kernel Version: 2.6.21-1.3194.fc7 > > Status: NEW > > Severity: blocking > > Owner: [EMAIL PROTECTED] > > Submitter: [EMAIL PROTECTED] > > > > > > Fedora 7 > > USB-UIRT > > > > 1. > > drivers/usb/serial/usb-serial.c: USB Serial support registered for > > FTDI > > USB Serial Device > > 2. > > ftdi_sio 3-2:1.0: FTDI USB Serial Device converter detected > > 3. > > BUG: unable to handle kernel NULL pointer dereference at virtual > > address > > 00000014 > > 4. > > printing eip: > > 5. > > f8a1740a > > 6. > > *pde = 00000000 > > 7. > > Oops: 0002 [#1] > > 8. > > SMP > > 9. > > last sysfs file: /devices/pci0000:00/0000:00:1d.7/usb5/idVendor > > 10. > > Modules linked in: ftdi_sio bluetooth snd_seq snd_ac97_codec usblp > > v4l1_compat fw_core snd_rawmidi sr_mod snd_pcm_oss snd_mixer_oss ac97_bus > > snd_util_mem usbserial e100 serio_raw snd_seq_device snd_hwdep snd_pcm > > emu10k1_gp cdrom mii snd_timer gameport snd soundcore iTCO_wdt > > snd_page_alloc > > i2c_i801 iTCO_vendor_support pcspkr i2c_core floppy sg joydev usb_storage > > ata_piix ata_generic libata sd_mod scsi_mod ext3 jbd mbcache ehci_hcd > > ohci_hcd > > uhci_hcd > > 11. > > CPU: 0 > > 12. > > EIP: 0060:[<f8a1740a>] Not tainted VLI > > 13. > > EFLAGS: 00010246 (2.6.21-1.3194.fc7 #1) > > 14. > > EIP is at ftdi_USB_UIRT_setup+0x34/0x4e [ftdi_sio] > > 15. > > eax: 00000000 ebx: f583f400 ecx: f8a17b34 edx: f8a173d6 > > 16. > > esi: f8a1dae0 edi: 00000040 ebp: f8a1dae0 esp: f582acdc > > 17. > > ds: 007b es: 007b fs: 00d8 gs: 0033 ss: 0068 > > 18. > > Process modprobe (pid: 935, ti=f582a000 task=f5913150 > > task.ti=f582a000) > > 19. > > Stack: f791e464 00000246 f598fb00 f5e823c0 f8a160b5 f898690a f898855b > > f8a18f6f > > 20. > > f5ea06d0 f8a194fa f5ea0600 f5ea4800 f8a1dae0 00000000 00000000 > > 00000001 > > 21. > > 00000001 f583f400 00000000 c1806d60 00000001 00000001 00000001 > > 00000000 > > 22. > > Call Trace: > > 23. > > [<f8a160b5>] ftdi_sio_attach+0xf/0x12 [ftdi_sio] > > 24. > > [<f898690a>] usb_serial_probe+0x97b/0xdd1 [usbserial] > > 25. > > [<c042e748>] lock_timer_base+0x19/0x35 > > 26. > > [<c042e7a8>] try_to_del_timer_sync+0x44/0x4a > > 27. > > [<c05692c8>] usb_resume_both+0xa1/0xb7 > > 28. > > [<c056947c>] usb_autopm_do_device+0xb3/0xbd > > 29. > > [<c04ad4dd>] sysfs_create_link+0x128/0x13f > > 30. > > [<c0568fd2>] usb_match_one_id+0x1c/0x71 > > 31. > > [<c0569d2d>] usb_probe_interface+0x81/0xb2 > > 32. > > [<c05529ab>] really_probe+0xc6/0x14f > > 33. > > [<c0552a78>] driver_probe_device+0x44/0xa5 > > 34. > > [<c0552b72>] __driver_attach+0x0/0xa5 > > 35. > > [<c0552be2>] __driver_attach+0x70/0xa5 > > 36. > > [<c0551ffb>] bus_for_each_dev+0x37/0x59 > > 37. > > [<c055282a>] driver_attach+0x16/0x18 > > 38. > > [<c0552b72>] __driver_attach+0x0/0xa5 > > 39. > > [<c05522ad>] bus_add_driver+0x5e/0x15f > > 40. > > [<c056985c>] usb_register_driver+0x6d/0xd4 > > 41. > > [<f89857b5>] usb_serial_register+0x1ed/0x1f6 [usbserial] > > 42. > > [<f8806091>] ftdi_init+0x91/0xbe [ftdi_sio] > > 43. > > [<c04432e4>] sys_init_module+0x16c3/0x17fa > > 44. > > [<c04755f8>] do_sync_read+0xc7/0x10a > > 45. > > [<c0468484>] do_mmap_pgoff+0x593/0x6f3 > > 46. > > [<c05507e5>] device_remove_file+0x0/0x25 > > 47. > > [<c0475531>] do_sync_read+0x0/0x10a > > 48. > > [<c0475e85>] vfs_read+0xa6/0x152 > > 49. > > [<c0404f70>] syscall_call+0x7/0xb > > 50. > > ======================= > > 51. > > Code: ee a1 f8 00 74 1c c7 44 24 08 a4 86 a1 f8 c7 44 24 04 b7 88 a1 > > f8 c7 > > 04 24 d5 88 a1 f8 e8 49 03 a1 c7 8b 43 14 8b 80 8c 01 00 00 <83> 48 14 30 > > c7 40 > > 08 4d 00 00 00 c7 80 80 00 00 00 0f 00 00 00 > > 52. > > EIP: [<f8a1740a>] ftdi_USB_UIRT_setup+0x34/0x4e [ftdi_sio] SS:ESP > > 0068:f582acdc > > > > It looks like the `serial' argument to ftdi_HE_TIRA1_setup() is NULL, and > we went oops reading serial->port[0]). > > John, are you able to identify an earlier kernel version which did not > have this bug? > > Thanks. > ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
