From: Matthew J. <lyd...@gm...> - 2008-04-29 17:25:20
|
Thanks. I guess I just assumed a fail f/w load wouldn't leave the pointer non-null :-). On Mon, Apr 28, 2008 at 7:56 AM, Stanislaw Gruszka <sta...@op...> wrote: > swapnil ingle wrote: > > > > > > > Hello, > > I tried using qla_isp at my end, but it gives following oops at the time > of rmmod > > > > > > Apr 25 15:10:58kernel: CPU: 0 > > Apr 25 15:10:58 kernel: EIP: 0060:[<c023bcbe>] Tainted: PF VLI > > Apr 25 15:10:58 kernel: EFLAGS: 00010202 (2.6.23-ndisks #1) > > Apr 25 15:10:58 kernel: EIP is at release_firmware+0x7/0x19 > > Apr 25 15:10:58 kernel: eax: 6b6b6b6b ebx: 6b6b6b6b ecx: 00000000 > edx: 00000001 > > Apr 25 15:10:58 kernel: esi: f8a54aa0 edi: e7a3643c ebp: e7a36000 > esp: df351f00 > > Apr 25 15:10:58 kernel: ds: 007b es: 007b fs: 0000 gs: 0033 ss: 0068 > > Apr 25 15:10:58 kernel: Process rmmod (pid: 4265, ti=df351000 > task=c18e1250 task.ti=df351000) > > Apr 25 15:10:58kernel: Stack: e7a36344 f8a41784 00000000 c1914040 00000246 > c1914040 f8a547f0 c1914088 > > Apr 25 15:10:58 kernel: f8a547f0 c01d0583 c1914088 c0238068 > c190e6e0 c19140d8 c0238169 f8a547f0 > > Apr 25 15:10:58 kernel: 00000003 00000000 df351000 c02378c9 > f8a547c0 c01d0775 f8a54c80 f8a45668 > > Apr 25 15:10:58 kernel: Call Trace: > > Apr 25 15:10:58 kernel: [<f8a41784>] isplinux_pci_remove+0x159/0x176 > [isp_mod] > > Apr 25 15:10:58 kernel: [<c01d0583>] pci_device_remove+0x16/0x35 > > Apr 25 15:10:58 kernel: [<c0238068>] __device_release_driver+0x71/0x8e > > Apr 25 15:10:58 kernel: [<c0238169>] driver_detach+0x9e/0xdd > > Apr 25 15:10:58 kernel: [<c02378c9>] bus_remove_driver+0x27/0x41 > > Apr 25 15:10:58 kernel: [<c01d0775>] pci_unregister_driver+0xb/0x13 > > Apr 25 15:10:58 kernel: [<f8a45668>] isplinux_pci_exit+0xa/0x2d [isp_mod] > > Apr 25 15:10:58 kernel: [<c0131c8a>] sys_delete_module+0x124/0x14a > > Apr 25 15:10:58 kernel: [<c010246e>] sysenter_past_esp+0x5f/0x85 > > Apr 25 15:10:58 kernel: [<c0300000>] wait_for_completion+0x8e/0xbd > > > > > > The reason for this is, " request_firmware(&isp->isp_osinfo.fwp, fwname, > &pdev->dev)" is returning error and it gets oops during release_firmware. > > > > while loading the module it gives following message > > isp0: unable to load firmware set "ql2400_fw.bin" > > > > > Thanks for reporting, does attached patch works for you? > > |