Re: [Bugme-new] [Bug 8564] New: ftdi_sio: BUG: unable to handle kernel NULL pointer dereference at virtual address

:(
Here is what I did

/*      .port_probe =           ftdi_sio_port_probe,
        .port_remove =          ftdi_sio_port_remove,*/


On lines 638 and 639, and am using new module.  Here's what it said on boot...

drivers/usb/serial/usb-serial.c: USB Serial support registered for
FTDI USB Serial Device
ftdi_sio 4-2:1.0: FTDI USB Serial Device converter detected
BUG: unable to handle kernel NULL pointer dereference at virtual
address 00000014
 printing eip:
f8a57beb
*pde = 00000000
Oops: 0002 [#1]
SMP
last sysfs file: /devices/pci0000:00/0000:00:1d.7/usb5/idVendor
Modules linked in: ftdi_sio(U) snd_seq_dummy snd_emu10k1 snd_seq_oss
snd_ac97_codec ivtv(F)(U) i2c_algo_bit snd_seq_midi_event
snd_usb_audio e100 cx2341x snd_seq fw_ohci snd_usb_lib tveeprom
hci_usb gspca(F)(U) usbserial fw_core ac97_bus nvidia(PF)(U) bluetooth
videodev emu10k1_gp snd_util_mem snd_pcm_oss snd_mixer_oss mii
snd_rawmidi snd_seq_device usblp v4l2_common serio_raw gameport
v4l1_compat snd_hwdep snd_pcm snd_timer floppy snd i2c_i801 iTCO_wdt
soundcore iTCO_vendor_support snd_page_alloc sr_mod i2c_core cdrom
joydev pcspkr sg ata_piix ata_generic libata sd_mod scsi_mod ext3 jbd
mbcache ehci_hcd ohci_hcd uhci_hcd
CPU:    0
EIP:    0060:[<f8a57beb>]    Tainted: PF      VLI
EFLAGS: 00010246   (2.6.21-1.3194.fc7 #1)
EIP is at ftdi_USB_UIRT_setup+0x34/0x4e [ftdi_sio]
eax: 00000000   ebx: f1c855c0   ecx: f8a58268   edx: f8a57bb7
esi: f8a5dea0   edi: 00000040   ebp: f8a5dea0   esp: f23e5cdc
ds: 007b   es: 007b   fs: 00d8  gs: 0033  ss: 0068
Process modprobe (pid: 924, ti=f23e5000 task=f2327110 task.ti=f23e5000)
Stack: f7f993e4 00000246 f1c85d00 f1c85580 f8a570b5 f8a1a90a f8a1c55b f8a59692
       f2136cd0 f8a59ced f2136c00 f2bc6c00 f8a5dea0 00000000 00000000 00000001
       00000001 f1c855c0 ffffffff 00000000 00000001 00000001 00000001 00000000
Call Trace:
 [<f8a570b5>] ftdi_sio_attach+0xf/0x12 [ftdi_sio]
 [<f8a1a90a>] usb_serial_probe+0x97b/0xdd1 [usbserial]
 [<c043c220>] clockevents_program_event+0xb2/0xb9
 [<c042e748>] lock_timer_base+0x19/0x35
 [<c042e7a8>] try_to_del_timer_sync+0x44/0x4a
 [<c05692c8>] usb_resume_both+0xa1/0xb7
 [<c056947c>] usb_autopm_do_device+0xb3/0xbd
 [<c04ad4dd>] sysfs_create_link+0x128/0x13f
 [<c0568fd2>] usb_match_one_id+0x1c/0x71
 [<c0569d2d>] usb_probe_interface+0x81/0xb2
 [<c05529ab>] really_probe+0xc6/0x14f
 [<c0552a78>] driver_probe_device+0x44/0xa5
 [<c0552b72>] __driver_attach+0x0/0xa5
 [<c0552be2>] __driver_attach+0x70/0xa5
 [<c0551ffb>] bus_for_each_dev+0x37/0x59
 [<c055282a>] driver_attach+0x16/0x18
 [<c0552b72>] __driver_attach+0x0/0xa5
 [<c05522ad>] bus_add_driver+0x5e/0x15f
 [<c056985c>] usb_register_driver+0x6d/0xd4
 [<f8a197b5>] usb_serial_register+0x1ed/0x1f6 [usbserial]
 [<f8806091>] ftdi_init+0x91/0xbe [ftdi_sio]
 [<c04432e4>] sys_init_module+0x16c3/0x17fa
 [<c04755f8>] do_sync_read+0xc7/0x10a
 [<c0472227>] __kmalloc+0x0/0x7d
 [<c0475531>] do_sync_read+0x0/0x10a
 [<c0475e85>] vfs_read+0xa6/0x152
 [<c0404f70>] syscall_call+0x7/0xb
 [<c0600000>] __sched_text_start+0x6e8/0x89e
 =======================
Code: f2 a5 f8 00 74 1c c7 44 24 08 a0 90 a5 f8 c7 44 24 04 18 92 a5
f8 c7 04 24 6c 92 a5 f8 e8 68 fb 9c 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
EIP: [<f8a57beb>] ftdi_USB_UIRT_setup+0x34/0x4e [ftdi_sio] SS:ESP 0068:f23e5cdc
fw_core: created new fw device fw0 (0 config rom retries)



Any other ideas?
On 6/2/07, John H. <[email protected]> wrote:
> Did you mean 639?
>
>    .port_probe =           ftdi_sio_port_probe,
>         .port_remove =          ftdi_sio_port_remove,
>
> On 6/2/07, Andrew Morton <[email protected]> wrote:
> > On Sat, 2 Jun 2007 14:28:19 -0500 "John H." <[email protected]> wrote:
> >
> > > 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?
> > >
> >
> > Dunno.  You could perhaps try removing the .port_probe and .port_remove
> > fields from ftdi_sio_device (line 649) but that's just a random poke.
> >
> > I suspect you'll need to stick with 2.6.20 for now.
> >
> > I'm suspecting it was Jim's 12bdbe03c8db7139de1de5c622cb0609d259cece which
> > caused this regression..
> >
>

-------------------------------------------------------------------------
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/
_______________________________________________
[email protected]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel